[ http://jira.codehaus.org/browse/MAVEN-1741?page=comments#action_70089 ] Lukas Theussl commented on MAVEN-1741: --------------------------------------
This is _not_ the same as MAVEN-1638. However, I am a bit confused by the attached test case, running war:install in the war project does not generate the attributes, just like in the multiproject case. Maybe something has changed, can someone confirm that with the latest versions of the plugins? > maven 1.1 fails to run commons-attributes in mutliproject mode on a war > project > ------------------------------------------------------------------------------- > > Key: MAVEN-1741 > URL: http://jira.codehaus.org/browse/MAVEN-1741 > Project: Maven > Issue Type: Bug > Affects Versions: 1.1-beta-2 > Reporter: nicolas de loof > Assigned To: Lukas Theussl > Priority: Minor > Fix For: 1.1-beta-3 > > Attachments: test_maven11_commons-attributes.zip > > > Attached zip contains a minimalist multiproject using commons-attributes that > demonstrates the bug. > - head (top level project) > - jar (minimalist jar project) : Sample.java has a "java.util.Date" attribute > - war (minimalist war project) : Sample.java has a "java.util.Date" attribute > When runing "maven war:install" on war project, attributes are generated as > expected. > When running from "head" project using "maven multiproject:install", > commons-attributes are > - generated as expected for the jar > - NOT generated in the war (no log from plugin) > I don't know if this is a maven, multiproject-plugin, war-plugin or > commons-attributes-plugin bug. > Please notice commons-attributes plugin uses a preGoal to automatically > register itself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
