What is a plugin plugin for resources and resources? What is the difference between the two?

Question

What is a plugin plugin for resources and resources?

What is the difference between the two?

What are the advantages and disadvantages?

Is it mandatory to work with different js and css framework?

Answer 1

What is a resource plugin and resource plugin?

Both of them are the grails plugin, which allows the programmer to use the web interface associated with resources or assets such as stylesheets, js, etc. and effective way.

This plug-in reduces the overhead of developers working with dependencies, the load order and many other issues, as well as the efficient use of resources or assets by compressing or deleting duplicates and reducing load times

What is the difference between the two?

There are many differences between them, for example, how they load resources, how they store resources, how they find duplicates, the organization’s file system, etc.

What are the advantages and disadvantages?

Resource plugin benefits over the standard grails resource plugin:

File dependencies are in the top of your assets. (No Resources.groovy) Assets in plugins become level with your app. On the fly processing in Development mode (No more waiting for reloads) Coffeescript, LESS, and others become first class citizens ( debuggable ) Require entire folder trees with one line Better minification (UglifyJs) , and compiling before the WAR is built Faster application startup time Easy extensibility 

Is it mandatory to work with different js and css framework?

No, you can directly use resources or assets, but that would be dirty and inefficient.

Ref:

http://grails-plugins.imtqy.com/grails-resources/guide/

https://github.com/efficiently/larasset/wiki/Asset-pipeline

https://github.com/bertramdev/grails-asset-pipeline/wiki/Why-asset-pipeline-over-grails-resources-plugin

Answer 2

Simply put, a pipeline asset plugin replaces a resource plugin and should be used to manage your assets (such as js and css).

The resource plugin existed before the pipeline plugin. It was used to facilitate and standardize the use of assets in the Grails application. It was later replaced by a plugin for connecting to resources.

The plugin for connecting to resources is a very capable, multifunctional and extensible plugin for managing your assets (mainly js, css). It also has several other additional plugins that allow you to pre-process assets (e.g. LESS).

While using the plugin for the pipeline does not match recommended and default for later versions of Grails.