|
||||||||
|
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 |
||||||||
- [mojo-dev] [jira] (MOJO-1116) atg-maven-plugin Slam Han (JIRA)
- [mojo-dev] [jira] (MOJO-1116) atg-maven-plugin Stevo Slavic (JIRA)
- [mojo-dev] [jira] (MOJO-1116) atg-maven-plugin Slam Han (JIRA)
- [mojo-dev] [jira] (MOJO-1116) atg-maven-plugin Slam Han (JIRA)
- [mojo-dev] [jira] (MOJO-1116) atg-maven-plugin David M. Karr (JIRA)
- [mojo-dev] [jira] (MOJO-1116) atg-maven-plugin Slam Han (JIRA)

I would suggest that this plugin, and the build surrounding it, needs to work somewhat differently for a Maven build to really be that viable. Specifically, the way the ATG maven plugin specifies the modules to assemble really needs to work just like normal Maven dependencies. Without this, you still have to build locally all of the modules you are trying to assemble. Ideally, you want to be able to only build locally the modules that you're making changes to, and you want to pull the other modules from a Maven repository, using standard Maven artifact references.