[
https://issues.jboss.org/browse/RF-13258?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-13258:
------------------------------------
Some potential build tools to consider:
* [
yeoman-maven-plugin|https://github.com/trecloux/yeoman-maven-plugin]
** Pros:
*** Invokes "npm install; bower install; grunt"
** Cons:
*** requires a local npm install
*** imposes a non-traditional folder layout (src tree is fixed, compiled code is not in
target)
* [
NodeJsMaven|https://github.com/ClearboxSystems/NodeJsMaven]
** Pros:
*** Self-downloads npm
** Cons:
*** Only offers node integration
**** Need to invesitgate running the build via a custom node script
* [
nodejs-maven-plugin|https://github.com/sirrapa/nodejs-maven-plugin]
** Pros:
*** Self-downloads npm
** Cons:
*** requires custom maven repositories
* maven-antrun-plugin / exec-maven-plugin
** See this blog for details:
http://addyosmani.com/blog/making-maven-grunt/
** Cons
*** Requires a local npm install
Build RichWidgets dist with maven
---------------------------------
Key: RF-13258
URL:
https://issues.jboss.org/browse/RF-13258
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: build/distribution
Reporter: Brian Leathem
Fix For: 5.0.0.Alpha2
Currently RichWidgets keeps it's dist folder in version control to allow RichFaces to
consume the compiled widgets. It would be better if the RichFaces build built the widgets
itself, and we could remove the dist folder from RichWidgets version control.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira