[jira] Commented: (MCOMPILER-125) Maven should not set default Java source target level
[ http://jira.codehaus.org/browse/MCOMPILER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217545#action_217545 ] redstun commented on MCOMPILER-125: --- As the issue reporter, I'd like to add a note. I'm not saying it's unnecessary to have specified source/target levels. On the contrary, this is very necessary or a must. Just that, the source/target levels should be decided by its owners/developers, NOT BY Maven. It's the project owner/developer's responsibility to decided the expected source/target levels and set the values in the project POM. Thus to have reproducible builds across computers/jdks. There has been a similar issue about how to handle the resource encoding in Maven, which had also gone through a lot of discussions. It finally become clear that there should be a place in project POM to let the project owner/developers configure the desired project level source encoding, instead of allowing each Maven plugin to have its own default encoding. We can learn from the conclusion there. For this please refer to http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding Thanks > Maven should not set default Java source target level > - > > Key: MCOMPILER-125 > URL: http://jira.codehaus.org/browse/MCOMPILER-125 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Affects Versions: 2.0, 2.0.1, 2.0.2, 2.1, 2.2 >Reporter: redstun > > Expectation: > The Maven Compiler Plugin, as it is just a wrapper of the underlying > compiler (javac by default), should not change the default source/target > levels of the underlying compiler, or specifying any hard coded values, FOR > the user. > Fact: > As described in the plugin homepage > (http://maven.apache.org/plugins/maven-compiler-plugin/index.html), "The > default source setting is 1.3 and the default target setting is 1.1, > independently of the JDK you run Maven with." > And people have been complaining against this, For that the default > source/target levels are either inappropriate or outdated. See MCOMPILER-80, > MCOMPILER-46, MCOMPILER-124. Plus that MCOMPILER-80 has been re-opened > recently soon after it's fixed. > Up to now, the filed issues are all about to change the default > source/target levels to more 'current' values, but whatever the values are > set to, they will sooner or later fall out of date, this is why we have > several requests like this over time, as listed above. They all represent a > resolution for 'now', not for all the time. > On the contrary, Ant is doing this as expected, As in > http://ant.apache.org/manual/CoreTasks/javac.html, it always defaults the > source/target levels to the javac in use, and clarifies that the users are > "highly recommended to always specify them". > And As a result, Ant never gets complaints regarding the issues we filed > against Maven Compiler Plugin. > Additionally, Eclipse is using the default values from the JDK in use as > well. if we create a project with mvn archetype:generate, then mvn > eclipse:eclipse and import it into Eclipse, you'll see that Eclipse does it > like Ant. Keep the project open in Eclipse and do a mvn compile outside (or > phases that depend on it, such as mvn package), you'll see a weird compile > error in Eclipse with no obvious clue. At the beginning you won't 'see' that > the problem is caused by Maven, to be specific, the source/target levels set > by Maven FOR you. -- 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
[jira] Commented: (MCOMPILER-125) Maven should not set default Java source target level
[ http://jira.codehaus.org/browse/MCOMPILER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217546#action_217546 ] redstun commented on MCOMPILER-125: --- The subject of this issue should have been - Maven should respect platform default source/target levels and warn the user to explicitly set them. :-) > Maven should not set default Java source target level > - > > Key: MCOMPILER-125 > URL: http://jira.codehaus.org/browse/MCOMPILER-125 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Affects Versions: 2.0, 2.0.1, 2.0.2, 2.1, 2.2 >Reporter: redstun > > Expectation: > The Maven Compiler Plugin, as it is just a wrapper of the underlying > compiler (javac by default), should not change the default source/target > levels of the underlying compiler, or specifying any hard coded values, FOR > the user. > Fact: > As described in the plugin homepage > (http://maven.apache.org/plugins/maven-compiler-plugin/index.html), "The > default source setting is 1.3 and the default target setting is 1.1, > independently of the JDK you run Maven with." > And people have been complaining against this, For that the default > source/target levels are either inappropriate or outdated. See MCOMPILER-80, > MCOMPILER-46, MCOMPILER-124. Plus that MCOMPILER-80 has been re-opened > recently soon after it's fixed. > Up to now, the filed issues are all about to change the default > source/target levels to more 'current' values, but whatever the values are > set to, they will sooner or later fall out of date, this is why we have > several requests like this over time, as listed above. They all represent a > resolution for 'now', not for all the time. > On the contrary, Ant is doing this as expected, As in > http://ant.apache.org/manual/CoreTasks/javac.html, it always defaults the > source/target levels to the javac in use, and clarifies that the users are > "highly recommended to always specify them". > And As a result, Ant never gets complaints regarding the issues we filed > against Maven Compiler Plugin. > Additionally, Eclipse is using the default values from the JDK in use as > well. if we create a project with mvn archetype:generate, then mvn > eclipse:eclipse and import it into Eclipse, you'll see that Eclipse does it > like Ant. Keep the project open in Eclipse and do a mvn compile outside (or > phases that depend on it, such as mvn package), you'll see a weird compile > error in Eclipse with no obvious clue. At the beginning you won't 'see' that > the problem is caused by Maven, to be specific, the source/target levels set > by Maven FOR you. -- 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
[jira] Commented: (DOXIA-78) Doxia XDOC parser and XHTML renderer ignore "rowspan" and "colspan" attributes for tables
[ http://jira.codehaus.org/browse/DOXIA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217547#action_217547 ] Razan Abbass commented on DOXIA-78: --- [cheap dress|http://www.facts11.com/download/attachments/1048855/hpd1.html] [cheap dress pants|http://www.facts11.com/download/attachments/1048855/hpd2.html] [cheap dress shops|http://www.facts11.com/download/attachments/1048855/hpd3.html] [cheap dresses for juniors|http://www.facts11.com/download/attachments/1048855/hpd4.html] [cheap dress shoes|http://www.facts11.com/download/attachments/1048855/hpd5.html] [cheap dress for a wedding|http://www.facts11.com/download/attachments/1048855/hpd6.html] [cheap dress rentals|http://www.facts11.com/download/attachments/1048855/hpd7.html] [cheap dress for prom|http://www.facts11.com/download/attachments/1048855/hpd8.html] [cheap dresses for prom|http://www.facts11.com/download/attachments/1048855/hpd9.html] [cheap dress clothes|http://www.facts11.com/download/attachments/1048855/hpd10.html] [cheap dresses for juniors|http://www.facts11.com/download/attachments/1048855/hpd11.html] [cheap dress clothes|https://wiki.luc.edu/download/attachments/21266444/hpd12.html] [cheap dresses for women|https://wiki.luc.edu/download/attachments/21266444/hpd13.html] [cheap dress up|https://wiki.luc.edu/download/attachments/21266444/hpd14.html] [cheap dress websites|https://wiki.luc.edu/download/attachments/21266444/hpd15.html] [cheap dress online|https://wiki.luc.edu/download/attachments/21266444/hpd16.html] [cheap dress shops|https://wiki.luc.edu/download/attachments/21266444/hpd17.html] [cheap dresses for homecoming|https://wiki.luc.edu/download/attachments/21266444/hpd18.html] [cheap dress shirts for men|https://wiki.luc.edu/download/attachments/21266444/hpd19.html] [cheap dress for sale|https://wiki.luc.edu/download/attachments/21266444/hpd20.html] [cheap dress stores|https://wiki.luc.edu/download/attachments/21266444/hpd21.html] [cheap dress suits|https://wiki.luc.edu/download/attachments/21266444/hpd22.html] [cheap dress forms|https://wiki.luc.edu/download/attachments/21266444/hpd23.html] [cheap dress boots|http://www.inventiondb.com/view.php?id=545] [cheap dress for prom|http://www.inventiondb.com/view.php?id=546] [cheap dressing tables|http://www.inventiondb.com/view.php?id=547] [cheap dress fabric|http://www.inventiondb.com/view.php?id=548] [cheap dress for wedding|http://www.inventiondb.com/view.php?id=549] [cheap dress for sale|http://www.inventiondb.com/view.php?id=550] [cheap dressage saddles|http://www.inventiondb.com/view.php?id=551] [cheap dress hire|http://www.inventiondb.com/view.php?id=552] [cheap dressing mirror|http://www.inventiondb.com/view.php?id=553] [cheap dressmakers|http://www.inventiondb.com/view.php?id=554] [cheap dress shirts for men|http://www.inventiondb.com/view.php?id=555] [cheap dress sandals|http://risd.openprojectdb.org/view.php?id=18] [cheap dress patterns|http://risd.openprojectdb.org/view.php?id=19] [cheap dress up clothes|http://risd.openprojectdb.org/view.php?id=20] [cheap dress watches|http://risd.openprojectdb.org/view.php?id=21] [cheap dress fabric|http://risd.openprojectdb.org/view.php?id=22] [cheap dress shoes for men|http://risd.openprojectdb.org/view.php?id=23] [cheap dressy dresses|http://risd.openprojectdb.org/view.php?id=24] [cheap dressy shoes|http://risd.openprojectdb.org/view.php?id=25] [cheap dressy tops|http://risd.openprojectdb.org/view.php?id=26] [cheap dressing up costumes|http://risd.openprojectdb.org/view.php?id=27] [cheap dresses for prom|http://opdb.risd.edu/view.php?id=28] [cheap dress up costumes|http://opdb.risd.edu/view.php?id=29] [cheap dress patterns|http://opdb.risd.edu/view.php?id=30] [cheap dress socks|http://opdb.risd.edu/view.php?id=31] [cheap dress tops|http://opdb.risd.edu/view.php?id=32] [cheap dress up clothes for kids|http://opdb.risd.edu/view.php?id=33] [cheap dress watch|http://opdb.risd.edu/view.php?id=34] [cheap dress ties|http://opdb.risd.edu/view.php?id=35] [cheap dress wear|http://opdb.risd.edu/view.php?id=36] [cheap dressage saddles|http://opdb.risd.edu/view.php?id=37] [cheap dress material|http://opdb.risd.edu/view.php?id=38] [cheap dresses to wear to a wedding|http://opdb.risd.edu/view.php?id=39] [cheap dressing tables with mirror|http://opdb.risd.edu/view.php?id=40] [cheap dressmakers dummy|http://opdb.risd.edu/view.php?id=41] [cheap dress pumps|http://opdb.risd.edu/view.php?id=42] [cheap dress makers|http://opdb.risd.edu/view.php?id=43] [cheap dress heels|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre1] [cheap dress material|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre2] [cheap dressmaking fabric|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre3] [cheap dress makers|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre
[jira] Updated: (DOXIA-78) Doxia XDOC parser and XHTML renderer ignore "rowspan" and "colspan" attributes for tables
[ http://jira.codehaus.org/browse/DOXIA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-78: --- Comment: was deleted (was: [cheap dress|http://www.facts11.com/download/attachments/1048855/hpd1.html] [cheap dress pants|http://www.facts11.com/download/attachments/1048855/hpd2.html] [cheap dress shops|http://www.facts11.com/download/attachments/1048855/hpd3.html] [cheap dresses for juniors|http://www.facts11.com/download/attachments/1048855/hpd4.html] [cheap dress shoes|http://www.facts11.com/download/attachments/1048855/hpd5.html] [cheap dress for a wedding|http://www.facts11.com/download/attachments/1048855/hpd6.html] [cheap dress rentals|http://www.facts11.com/download/attachments/1048855/hpd7.html] [cheap dress for prom|http://www.facts11.com/download/attachments/1048855/hpd8.html] [cheap dresses for prom|http://www.facts11.com/download/attachments/1048855/hpd9.html] [cheap dress clothes|http://www.facts11.com/download/attachments/1048855/hpd10.html] [cheap dresses for juniors|http://www.facts11.com/download/attachments/1048855/hpd11.html] [cheap dress clothes|https://wiki.luc.edu/download/attachments/21266444/hpd12.html] [cheap dresses for women|https://wiki.luc.edu/download/attachments/21266444/hpd13.html] [cheap dress up|https://wiki.luc.edu/download/attachments/21266444/hpd14.html] [cheap dress websites|https://wiki.luc.edu/download/attachments/21266444/hpd15.html] [cheap dress online|https://wiki.luc.edu/download/attachments/21266444/hpd16.html] [cheap dress shops|https://wiki.luc.edu/download/attachments/21266444/hpd17.html] [cheap dresses for homecoming|https://wiki.luc.edu/download/attachments/21266444/hpd18.html] [cheap dress shirts for men|https://wiki.luc.edu/download/attachments/21266444/hpd19.html] [cheap dress for sale|https://wiki.luc.edu/download/attachments/21266444/hpd20.html] [cheap dress stores|https://wiki.luc.edu/download/attachments/21266444/hpd21.html] [cheap dress suits|https://wiki.luc.edu/download/attachments/21266444/hpd22.html] [cheap dress forms|https://wiki.luc.edu/download/attachments/21266444/hpd23.html] [cheap dress boots|http://www.inventiondb.com/view.php?id=545] [cheap dress for prom|http://www.inventiondb.com/view.php?id=546] [cheap dressing tables|http://www.inventiondb.com/view.php?id=547] [cheap dress fabric|http://www.inventiondb.com/view.php?id=548] [cheap dress for wedding|http://www.inventiondb.com/view.php?id=549] [cheap dress for sale|http://www.inventiondb.com/view.php?id=550] [cheap dressage saddles|http://www.inventiondb.com/view.php?id=551] [cheap dress hire|http://www.inventiondb.com/view.php?id=552] [cheap dressing mirror|http://www.inventiondb.com/view.php?id=553] [cheap dressmakers|http://www.inventiondb.com/view.php?id=554] [cheap dress shirts for men|http://www.inventiondb.com/view.php?id=555] [cheap dress sandals|http://risd.openprojectdb.org/view.php?id=18] [cheap dress patterns|http://risd.openprojectdb.org/view.php?id=19] [cheap dress up clothes|http://risd.openprojectdb.org/view.php?id=20] [cheap dress watches|http://risd.openprojectdb.org/view.php?id=21] [cheap dress fabric|http://risd.openprojectdb.org/view.php?id=22] [cheap dress shoes for men|http://risd.openprojectdb.org/view.php?id=23] [cheap dressy dresses|http://risd.openprojectdb.org/view.php?id=24] [cheap dressy shoes|http://risd.openprojectdb.org/view.php?id=25] [cheap dressy tops|http://risd.openprojectdb.org/view.php?id=26] [cheap dressing up costumes|http://risd.openprojectdb.org/view.php?id=27] [cheap dresses for prom|http://opdb.risd.edu/view.php?id=28] [cheap dress up costumes|http://opdb.risd.edu/view.php?id=29] [cheap dress patterns|http://opdb.risd.edu/view.php?id=30] [cheap dress socks|http://opdb.risd.edu/view.php?id=31] [cheap dress tops|http://opdb.risd.edu/view.php?id=32] [cheap dress up clothes for kids|http://opdb.risd.edu/view.php?id=33] [cheap dress watch|http://opdb.risd.edu/view.php?id=34] [cheap dress ties|http://opdb.risd.edu/view.php?id=35] [cheap dress wear|http://opdb.risd.edu/view.php?id=36] [cheap dressage saddles|http://opdb.risd.edu/view.php?id=37] [cheap dress material|http://opdb.risd.edu/view.php?id=38] [cheap dresses to wear to a wedding|http://opdb.risd.edu/view.php?id=39] [cheap dressing tables with mirror|http://opdb.risd.edu/view.php?id=40] [cheap dressmakers dummy|http://opdb.risd.edu/view.php?id=41] [cheap dress pumps|http://opdb.risd.edu/view.php?id=42] [cheap dress makers|http://opdb.risd.edu/view.php?id=43] [cheap dress heels|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre1] [cheap dress material|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre2] [cheap dressmaking fabric|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre3] [cheap dress makers|https://gaia.lbl.gov/bcvtb/Abbass%20Razan?action=AttachFile&do=get&target=sdre4] [cheap dress
[jira] Commented: (MWAR-82) setting archiveClasses to true create the jar in WEB-INF/lib but does not remove WEB-INF/classes
[
http://jira.codehaus.org/browse/MWAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217553#action_217553
]
John Baker commented on MWAR-82:
Hello,
This bug still seems to exist in this version of the war task:
[DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:13
for project: null:maven-war-plugin:maven-plugin:2.1-beta-1 from the repository.
I have defined:
org.apache.maven.plugins
maven-war-plugin
war
true
In my pom and run mvn clean package. I see the classes and the jar file in
WEB-INF/lib.
Would be great so solve this issue so if someone wants to get in touch then I'm
happy to help where I can.
> setting archiveClasses to true create the jar in WEB-INF/lib but does not
> remove WEB-INF/classes
>
>
> Key: MWAR-82
> URL: http://jira.codehaus.org/browse/MWAR-82
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Sebastien Brunot
>Assignee: Stephane Nicoll
> Fix For: 2.0.1
>
>
> This bug has been explained on the maven users mailing list:
> Hi Sebastien
> It seems to be a bug.
> In the code [1] we have :
> if ( archiveClasses )
> {
> createJarArchive( libDirectory );
> }
> else
> {
> copyDirectoryStructureIfModified( classesDirectory,
> webappClassesDirectory );
> }
> The content of the classes directory is never removed (neither in
> createJarArchive nor somewhere else).
> Can you create an issue please ?
> Thx
> Arnaud
> [1]
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java?revision=471624
> Sebastien Brunot wrote:
> >
> > Hi all,
> >
> > i've got a war project which pom build section contains the following
> > statements:
> >
> >
> >
> > org.apache.maven.plugins
> > maven-war-plugin
> >
> >
> >
> >war
> >
> >
> >true
> >
> >
> >
> >
> >
> > As a result, all the classes and resources from my war project are
> > packaged in a jar that is copied in the WEB-INF/lib directory of the
> > war artifact.
> >
> > But i don't understand why the war artifact still contains copy of the
> > classes and resources under WEB-INF/classes... Does anybody think that
> > i've misconfigured the war plugin ?
> >
> > Thanks for your help,
> >
> > Sebastien
> >
> >
> --
> View this message in context:
> http://www.nabble.com/Configuring-war-plugin-for-using-a-jar-instead-of-WEB-INF-classes-tf2589199s177.html#a7219855
> Sent from the Maven - Users mailing list archive at Nabble.com.
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
--
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
[jira] Created: (ARCHETYPE-293) generated archetype pom.xml should reference POM XML Schema
generated archetype pom.xml should reference POM XML Schema --- Key: ARCHETYPE-293 URL: http://jira.codehaus.org/browse/ARCHETYPE-293 Project: Maven Archetype Issue Type: Improvement Components: Creator Affects Versions: 2.0-alpha-4 Reporter: Herve Boutemy -- 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
[jira] Commented: (MWAR-82) setting archiveClasses to true create the jar in WEB-INF/lib but does not remove WEB-INF/classes
[
http://jira.codehaus.org/browse/MWAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217554#action_217554
]
John Baker commented on MWAR-82:
Hello,
Also, I would expect this to work when the exploded goal is included, but in
this instance, the task does not even create the jar file.
I've looked at the source:
http://svn.apache.org/viewvc/maven/plugins/tags/maven-war-plugin-2.1-beta-1/src/main/java/org/apache/maven/plugin/war/packaging/ClassesPackagingTask.java?revision=754916&view=markup
(I know nothing about task development for maven) and I can't see any obvious
code that would remove/mask the classes.
John
> setting archiveClasses to true create the jar in WEB-INF/lib but does not
> remove WEB-INF/classes
>
>
> Key: MWAR-82
> URL: http://jira.codehaus.org/browse/MWAR-82
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Sebastien Brunot
>Assignee: Stephane Nicoll
> Fix For: 2.0.1
>
>
> This bug has been explained on the maven users mailing list:
> Hi Sebastien
> It seems to be a bug.
> In the code [1] we have :
> if ( archiveClasses )
> {
> createJarArchive( libDirectory );
> }
> else
> {
> copyDirectoryStructureIfModified( classesDirectory,
> webappClassesDirectory );
> }
> The content of the classes directory is never removed (neither in
> createJarArchive nor somewhere else).
> Can you create an issue please ?
> Thx
> Arnaud
> [1]
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java?revision=471624
> Sebastien Brunot wrote:
> >
> > Hi all,
> >
> > i've got a war project which pom build section contains the following
> > statements:
> >
> >
> >
> > org.apache.maven.plugins
> > maven-war-plugin
> >
> >
> >
> >war
> >
> >
> >true
> >
> >
> >
> >
> >
> > As a result, all the classes and resources from my war project are
> > packaged in a jar that is copied in the WEB-INF/lib directory of the
> > war artifact.
> >
> > But i don't understand why the war artifact still contains copy of the
> > classes and resources under WEB-INF/classes... Does anybody think that
> > i've misconfigured the war plugin ?
> >
> > Thanks for your help,
> >
> > Sebastien
> >
> >
> --
> View this message in context:
> http://www.nabble.com/Configuring-war-plugin-for-using-a-jar-instead-of-WEB-INF-classes-tf2589199s177.html#a7219855
> Sent from the Maven - Users mailing list archive at Nabble.com.
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
--
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
[jira] Closed: (ARCHETYPE-293) generated archetype pom.xml should reference POM XML Schema
[ http://jira.codehaus.org/browse/ARCHETYPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed ARCHETYPE-293. --- Resolution: Fixed Fix Version/s: 2.0-alpha-5 Assignee: Herve Boutemy done in r932858. > generated archetype pom.xml should reference POM XML Schema > --- > > Key: ARCHETYPE-293 > URL: http://jira.codehaus.org/browse/ARCHETYPE-293 > Project: Maven Archetype > Issue Type: Improvement > Components: Creator >Affects Versions: 2.0-alpha-4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.0-alpha-5 > > -- 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
[jira] Commented: (MASSEMBLY-449) Permissions on directories in a zipped archive incorrect
[
http://jira.codehaus.org/browse/MASSEMBLY-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217561#action_217561
]
Klaus Reimer commented on MASSEMBLY-449:
Any news here? This bug is quite old and now I also stumbled over it when I
tried to access the generated ZIP files with Midnight Commander. It gives me
the error message "Inconsistent extfs archive". Midnight commander uses "unzip
-Z" to get info about the ZIP. If I do this manually then I see broken
directory permissions like this:
?rwsrwsrwt 2.0 unx0 b- stor 10-Apr-11 15:41 ltray-1.0.0-SNAPSHOT/
Plugin Version 2.2-beta3 generates ZIP files with these permissions (And they
are correct and working):
drwxr-xr-x 2.0 unx0 b- stor 10-Apr-11 15:55 ltray-1.0.0-SNAPSHOT/
So I reverted back to beta3, too, because I don't like it at all when Maven
generates broken ZIP files.
> Permissions on directories in a zipped archive incorrect
>
>
> Key: MASSEMBLY-449
> URL: http://jira.codehaus.org/browse/MASSEMBLY-449
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-4
>Reporter: James Kavanagh
>
> Using the following assembly plugin:
> {code:xml}
>
> target-packaged
>
> zip
>
> false
>
>
>
> *:core-env
>
>
> env
> false
> true
>
>
>
>
> *:data-bridge
>
>
> target
> false
> true
>
>
>
>
> *:web
>
>
> web
> false
> true
>
>
>
>
> {code}
> When unzipping the result on a Linux host all the directory permissions have
> been set to 777.
> If I revert the plugin version to 2.2-beta-3 the issue goes away.
--
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
[jira] Created: (MECLIPSE-652) Ability to map a webapp to the root context
Ability to map a webapp to the root context
---
Key: MECLIPSE-652
URL: http://jira.codehaus.org/browse/MECLIPSE-652
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: WTP support
Affects Versions: 2.8
Reporter: fabrizio giustina
Priority: Trivial
There is no way at the moment to map a webapp to the root context.
A root context is configured in the org.eclipse.wst.common.component file using:
{code}
{code}
However, setting an empty wtpContextName in pom.xml makes the eclipse plugin
default to the artifact id for the context root, giving no way to set it to an
empty value.
In order to make it configurable without breaking the old behavior we could use
the magic word "ROOT" to map the webapp to the root context, just like tomcat
commonly does (in order to map a webapp to the root context a common option in
tomcat is to name it "ROOT")
{code}
maven-eclipse-plugin
ROOT
{code}
--
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
[jira] Updated: (MECLIPSE-652) Ability to map a webapp to the root context
[
http://jira.codehaus.org/browse/MECLIPSE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated MECLIPSE-652:
---
Fix Version/s: 2.9
Assignee: fabrizio giustina
> Ability to map a webapp to the root context
> ---
>
> Key: MECLIPSE-652
> URL: http://jira.codehaus.org/browse/MECLIPSE-652
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: WTP support
>Affects Versions: 2.8
>Reporter: fabrizio giustina
>Assignee: fabrizio giustina
>Priority: Trivial
> Fix For: 2.9
>
>
> There is no way at the moment to map a webapp to the root context.
> A root context is configured in the org.eclipse.wst.common.component file
> using:
> {code}
>
> {code}
> However, setting an empty wtpContextName in pom.xml makes the eclipse plugin
> default to the artifact id for the context root, giving no way to set it to
> an empty value.
> In order to make it configurable without breaking the old behavior we could
> use the magic word "ROOT" to map the webapp to the root context, just like
> tomcat commonly does (in order to map a webapp to the root context a common
> option in tomcat is to name it "ROOT")
>
> {code}
>
> maven-eclipse-plugin
>
> ROOT
>
>
> {code}
--
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
[jira] Closed: (MECLIPSE-652) Ability to map a webapp to the root context
[
http://jira.codehaus.org/browse/MECLIPSE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina closed MECLIPSE-652.
--
Resolution: Fixed
added in version 2.9
> Ability to map a webapp to the root context
> ---
>
> Key: MECLIPSE-652
> URL: http://jira.codehaus.org/browse/MECLIPSE-652
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: WTP support
>Affects Versions: 2.8
>Reporter: fabrizio giustina
>Assignee: fabrizio giustina
>Priority: Trivial
> Fix For: 2.9
>
>
> There is no way at the moment to map a webapp to the root context.
> A root context is configured in the org.eclipse.wst.common.component file
> using:
> {code}
>
> {code}
> However, setting an empty wtpContextName in pom.xml makes the eclipse plugin
> default to the artifact id for the context root, giving no way to set it to
> an empty value.
> In order to make it configurable without breaking the old behavior we could
> use the magic word "ROOT" to map the webapp to the root context, just like
> tomcat commonly does (in order to map a webapp to the root context a common
> option in tomcat is to name it "ROOT")
>
> {code}
>
> maven-eclipse-plugin
>
> ROOT
>
>
> {code}
--
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
[jira] Created: (MANTTASKS-183) Property not evaluated in pom/project/parent/version
Property not evaluated in pom/project/parent/version
Key: MANTTASKS-183
URL: http://jira.codehaus.org/browse/MANTTASKS-183
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: pom task
Affects Versions: 2.1.0
Environment: Ant 1.7.1
Reporter: Marcin Wisnicki
I'm trying to define parent version in pom by property:
{code:xml|title=hamcrest-integration.pom}
http://maven.apache.org/POM/4.0.0";>
4.0.0
org.hamcrest
hamcrest-parent
${hamcrest.version}
org.hamcrest
hamcrest-integration
${hamcrest.version}
{code}
And using something like following in build.xml:
{code:xml|title=build.xml}
{code}
Unfortunately generated pom (via writepom/install/deploy) has
{{project.version}} resolved, but {{project.parent.version}} remains unresolved.
--
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
[jira] Created: (MANTTASKS-184) No easy way to use parent pom
No easy way to use parent pom
-
Key: MANTTASKS-184
URL: http://jira.codehaus.org/browse/MANTTASKS-184
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: deploy task, install task
Affects Versions: 2.1.0
Environment: Ant 1.7.1
Reporter: Marcin Wisnicki
There is no proper way to install or deploy parent pom.
It is not possible to install it directly:
{code:xml}
{code}
Resulting pom will be unprocessed. It's kind of expected but I can't omit file
attribute.
I had to workaround it with additional {{writepom}} step:
{code:xml}
{code}
Possible solutions:
# Make {{file}} attribute completely optional, if not present assume
installation of pom artifact
# Add {{type}} attribute to {{install}} task
# Add separate install-pom task
--
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
[jira] Created: (MSITE-470) Classpath (ex/im)plosion with site plugin 2.1
Classpath (ex/im)plosion with site plugin 2.1
-
Key: MSITE-470
URL: http://jira.codehaus.org/browse/MSITE-470
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Benson Margulies
I'm not sure how to chase this. I got here with mvn javadoc:javadoc
javadoc:test-javadoc site:site site:deploy
{noformat}
[INFO]
[INFO] Building Manifest jar for training jobs
[INFO]
[WARNING] Removing: check from forked lifecycle, to prevent recursive
invocation.
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Preparing javadoc:javadoc
[WARNING] Removing: check from forked lifecycle, to prevent recursive
invocation.
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Starting audit...
Audit done.
[INFO] [site:site]
[INFO] Parent project loaded from repository.
[INFO] Generating "Dependency Convergence" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Project License" report.
[INFO] Generating "Project Team" report.
[INFO] Generating "Project Summary" report.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "About" report.
[INFO] Generating "Issue Tracking" report.
[INFO] Generating "Dependency Management" report.
[INFO] Generating "Source Repository" report.
[INFO] Generating "Plugin Management" report.
[INFO] Generating "Mailing Lists" report.
[INFO] Generating "Dependencies" report.
[INFO] Generating "JavaDocs" report.
[WARNING] Are you sure about the parameter? It seems to be 1.6
[FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a linkage
error (java.lang.ExceptionInInitializerError) and may be out-of-date. Check the
realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1]
urls[0] =
file:/Users/benson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
urls[1] =
file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] =
file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
urls[3] =
file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2/doxia-core-1.1.2.jar
urls[4] =
file:/Users/benson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] =
file:/Users/benson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] =
file:/Users/benson/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
urls[7] =
file:/Users/benson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] =
file:/Users/benson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] =
file:/Users/benson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] =
file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
urls[11] =
file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
urls[12] =
file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
urls[13] =
file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
urls[14] =
file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
urls[15] =
file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] =
file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
urls[17] =
file:/Users/benson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[18] =
file:/Users/benson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/Users/benson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[20] =
file:/Users/benson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.2/maven-doxia-tools-1.2.jar
urls[21] =
file:/Users/benson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[22] =
file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] =
file:/Users/benson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
urls[24] =
file:/Users/benson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] =
file:/Users/benson/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] =
file:/Users/benson/x/trunk/third-party-tools/maven/lib/maven-2.1.0-uber.jar
[INFO] -
[jira] Created: (ARCHETYPE-294) provide a basic it in created archetype
provide a basic it in created archetype --- Key: ARCHETYPE-294 URL: http://jira.codehaus.org/browse/ARCHETYPE-294 Project: Maven Archetype Issue Type: Improvement Components: Creator Affects Versions: 2.0-alpha-4 Reporter: Herve Boutemy archetype:integration-test is easy to use and permits automatic test of an archetype. generated archetype should contain a basic it. -- 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
[jira] Updated: (MSITE-470) Classpath (ex/im)plosion with site plugin 2.1
[
http://jira.codehaus.org/browse/MSITE-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MSITE-470:
---
Attachment: mvn.log
> Classpath (ex/im)plosion with site plugin 2.1
> -
>
> Key: MSITE-470
> URL: http://jira.codehaus.org/browse/MSITE-470
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Benson Margulies
> Attachments: mvn.log
>
>
> I'm not sure how to chase this. I got here with mvn javadoc:javadoc
> javadoc:test-javadoc site:site site:deploy
> {noformat}
> [INFO]
>
> [INFO] Building Manifest jar for training jobs
> [INFO]
>
> [WARNING] Removing: check from forked lifecycle, to prevent recursive
> invocation.
> [INFO] [checkstyle:checkstyle {execution: validate}]
> [INFO] Preparing javadoc:javadoc
> [WARNING] Removing: check from forked lifecycle, to prevent recursive
> invocation.
> [INFO] [checkstyle:checkstyle {execution: validate}]
> [INFO] Starting audit...
> Audit done.
> [INFO] [site:site]
> [INFO] Parent project loaded from repository.
> [INFO] Generating "Dependency Convergence" report.
> [INFO] Generating "Project Plugins" report.
> [INFO] Generating "Project License" report.
> [INFO] Generating "Project Team" report.
> [INFO] Generating "Project Summary" report.
> [INFO] Generating "Continuous Integration" report.
> [INFO] Generating "About" report.
> [INFO] Generating "Issue Tracking" report.
> [INFO] Generating "Dependency Management" report.
> [INFO] Generating "Source Repository" report.
> [INFO] Generating "Plugin Management" report.
> [INFO] Generating "Mailing Lists" report.
> [INFO] Generating "Dependencies" report.
> [INFO] Generating "JavaDocs" report.
> [WARNING] Are you sure about the parameter? It seems to be
> 1.6
> [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a
> linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date.
> Check the realms:
> [FATAL ERROR] Plugin realm =
> app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1]
> urls[0] =
> file:/Users/benson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
> urls[1] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
> urls[2] =
> file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
> urls[3] =
> file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2/doxia-core-1.1.2.jar
> urls[4] =
> file:/Users/benson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
> urls[5] =
> file:/Users/benson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
> urls[6] =
> file:/Users/benson/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
> urls[7] =
> file:/Users/benson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
> urls[8] =
> file:/Users/benson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
> urls[9] =
> file:/Users/benson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
> urls[10] =
> file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
> urls[11] =
> file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
> urls[12] =
> file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
> urls[13] =
> file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
> urls[14] =
> file:/Users/benson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
> urls[15] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> urls[16] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
> urls[17] =
> file:/Users/benson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
> urls[18] =
> file:/Users/benson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
> urls[19] = file:/Users/benson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
> urls[20] =
> file:/Users/benson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.2/maven-doxia-tools-1.2.jar
> urls[21] =
> file:/Users/benson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
> urls[22] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
> urls[23] =
> file:/Users/benson/
[jira] Closed: (ARCHETYPE-294) provide a basic it in created archetype
[ http://jira.codehaus.org/browse/ARCHETYPE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed ARCHETYPE-294. --- Resolution: Fixed Fix Version/s: 2.0-alpha-5 Assignee: Herve Boutemy done in r932994. > provide a basic it in created archetype > --- > > Key: ARCHETYPE-294 > URL: http://jira.codehaus.org/browse/ARCHETYPE-294 > Project: Maven Archetype > Issue Type: Improvement > Components: Creator >Affects Versions: 2.0-alpha-4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.0-alpha-5 > > > archetype:integration-test is easy to use and permits automatic test of an > archetype. > generated archetype should contain a basic it. -- 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
[jira] Commented: (MNG-2258) Wrong execution order of plugins in same phase
[
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217593#action_217593
]
Daniel Zardi Fernandes commented on MNG-2258:
-
I found this bug while looking for a solution to the taglist-maven-plugin issue
with the maven-jxr-plugin, so I have no knowledge about the execution order
bug, but I managed to get the taglist plugin working without a second run of
jxr.
I noticed that when running jxr in the pre-site phase the output where
generated in the reports directory, not in the site directory, so it's probably
an issue of the taglist-maven-plugin.
Try adding the following to the taglist-maven-plugin configuration, it worked
for me (don't forget to change the directories to match your configuration if
needed).
{code:xml}
target/site/xref
target/site/xref-test
{code}
Probably it won't help with this bug, but it's a better workaround than running
jxr twice.
By the way, I'm using Maven 2.2.1 too and got the "Taglist plugin MUST be
executed after the JXR plugin." message too.
> Wrong execution order of plugins in same phase
> --
>
> Key: MNG-2258
> URL: http://jira.codehaus.org/browse/MNG-2258
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 2.0.4
> Environment: N/A
>Reporter: David J. M. Karlsen
>Priority: Blocker
> Attachments: mavenTest.zip
>
>
> AFAIK plugins should be execute in the same order as they are listed in the
> POM, when bound to the same phase. This does not happen, the execution order
> is arbitrary.
--
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
[jira] Issue Comment Edited: (MNG-2258) Wrong execution order of plugins in same phase
[
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217593#action_217593
]
Daniel Zardi Fernandes edited comment on MNG-2258 at 4/11/10 5:54 PM:
--
I found this bug while looking for a solution to the taglist-maven-plugin issue
with the maven-jxr-plugin, so I have no knowledge about the execution order
bug, but I managed to get the taglist plugin working without a second run of
jxr.
I noticed that when running jxr in the pre-site phase the output where
generated in the reports directory, not in the site directory, so it's probably
an issue of the taglist-maven-plugin.
Try adding the following to the taglist-maven-plugin configuration, it worked
for me (don't forget to change the directories to match your configuration if
needed).
{code:xml}
target/site/xref
target/site/xref-test
{code}
Probably it won't help with this bug, but it's a better workaround than running
jxr twice.
By the way, I'm using Maven 2.2.1 and got the "Taglist plugin MUST be executed
after the JXR plugin." message too.
was (Author: zardi):
I found this bug while looking for a solution to the taglist-maven-plugin
issue with the maven-jxr-plugin, so I have no knowledge about the execution
order bug, but I managed to get the taglist plugin working without a second run
of jxr.
I noticed that when running jxr in the pre-site phase the output where
generated in the reports directory, not in the site directory, so it's probably
an issue of the taglist-maven-plugin.
Try adding the following to the taglist-maven-plugin configuration, it worked
for me (don't forget to change the directories to match your configuration if
needed).
{code:xml}
target/site/xref
target/site/xref-test
{code}
Probably it won't help with this bug, but it's a better workaround than running
jxr twice.
By the way, I'm using Maven 2.2.1 too and got the "Taglist plugin MUST be
executed after the JXR plugin." message too.
> Wrong execution order of plugins in same phase
> --
>
> Key: MNG-2258
> URL: http://jira.codehaus.org/browse/MNG-2258
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 2.0.4
> Environment: N/A
>Reporter: David J. M. Karlsen
>Priority: Blocker
> Attachments: mavenTest.zip
>
>
> AFAIK plugins should be execute in the same order as they are listed in the
> POM, when bound to the same phase. This does not happen, the execution order
> is arbitrary.
--
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
[jira] Commented: (MEV-657) maven2/colt/colt/1.2.0 POM needs fix
[ http://jira.codehaus.org/browse/MEV-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217597#action_217597 ] Roy Liu commented on MEV-657: - Is there any way I can have commit privileges to fix this myself? It really is as simple as changing 3 characters. > maven2/colt/colt/1.2.0 POM needs fix > > > Key: MEV-657 > URL: http://jira.codehaus.org/browse/MEV-657 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Roy Liu > > The POM for colt-1.2.0 is not correct. It should have version 1.2.0 instead > of 1.0.3. I suspect someone just copied the 1.0.3 POM over. -- 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
[jira] Created: (MNG-4630) POMs that inherit from an aggregating POM should also inherit modules/reactors
POMs that inherit from an aggregating POM should also inherit modules/reactors -- Key: MNG-4630 URL: http://jira.codehaus.org/browse/MNG-4630 Project: Maven 2 & 3 Issue Type: Improvement Components: Dependencies Reporter: Emil Sit I have a simple use case where I use both inheritance and aggregation across several modules. When I run "mvn -pl subproject2 -am package" in the top-level, there is no need to 'mvn install' for subproject1, because both subprojects are aggregated at the top-level and the build reactor knows to build subproject1 first and stick it in the classpath for subproject2. However, when I am in the subproject2 directory and run 'mvn package', the build reactor does not. I don't know if this is a bug or by design, but it seems to me that through inheritance, subproject2's invocation should be aware of the other modules that it is being aggregated with and be able to calculate dependencies without requiring installation into the local repository. -- 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
