[jira] Commented: (MECLIPSE-132) "Class not found" when run/debug JUnit tests

2008-08-12 Thread Antony Stubbs (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144890#action_144890 ] Antony Stubbs commented on MECLIPSE-132: ok, problems back and the work around didn't work

[jira] Commented: (MANTTASKS-116) NPE if installing pom with type pom

2008-08-12 Thread Antony Stubbs (JIRA)
[ http://jira.codehaus.org/browse/MANTTASKS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144889#action_144889 ] Antony Stubbs commented on MANTTASKS-116: - ok my bad. actually forgot to change the type t

[jira] Created: (MANTTASKS-116) NPE if installing pom with type pom

2008-08-12 Thread Antony Stubbs (JIRA)
NPE if installing pom with type pom --- Key: MANTTASKS-116 URL: http://jira.codehaus.org/browse/MANTTASKS-116 Project: Maven 2.x Ant Tasks Issue Type: Bug Reporter: Antony Stubbs {code} maven-rep

[jira] Commented: (SUREFIRE-511) Proposal to use java Map for surefire's systemProperties

2008-08-12 Thread Dan Tran (JIRA)
[ http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144888#action_144888 ] Dan Tran commented on SUREFIRE-511: --- Given no object on the switch, I'd like to go head with co

[jira] Created: (MAVENUPLOAD-2174) Synchronizing the org.kohsuke repository to central

2008-08-12 Thread Kohsuke Kawaguchi (JIRA)
Synchronizing the org.kohsuke repository to central --- Key: MAVENUPLOAD-2174 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2174 Project: Maven Upload Requests Issue Type: Wish R

[jira] Commented: (MINVOKER-51) NPE when packaging is pom

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/MINVOKER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144887#action_144887 ] Benjamin Bentmann commented on MINVOKER-51: --- To run the ITs, you only need to activate the

[jira] Commented: (MECLIPSE-132) "Class not found" when run/debug JUnit tests

2008-08-12 Thread Antony Stubbs (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144885#action_144885 ] Antony Stubbs commented on MECLIPSE-132: Wow - I was about to stress out when this started

[jira] Created: (MINVOKER-51) NPE when packaging is pom

2008-08-12 Thread Peter Janes (JIRA)
NPE when packaging is pom - Key: MINVOKER-51 URL: http://jira.codehaus.org/browse/MINVOKER-51 Project: Maven 2.x Invoker Plugin Issue Type: Bug Affects Versions: 1.2.1 Environment: Linux x86_64, Java 1.6,

[jira] Closed: (MNG-3703) ExecutionProject contains relative paths in compileSourceRoots

2008-08-12 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3703. --- Resolution: Fixed > ExecutionProject contains relative paths in compileSourceRoots >

[jira] Closed: (MNG-3705) Expression: ${executedProject} doesn't work in reports

2008-08-12 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3705. --- Resolution: Fixed verification is currently contained in the integration test for MNG-3703 > Expression: ${executedP

[jira] Updated: (MNG-3705) Expression: ${executedProject} doesn't work in reports

2008-08-12 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3705: Fix Version/s: 2.0.10 > Expression: ${executedProject} doesn't work in reports > --

[jira] Created: (MNG-3705) Expression: ${executedProject} doesn't work in reports

2008-08-12 Thread John Casey (JIRA)
Expression: ${executedProject} doesn't work in reports -- Key: MNG-3705 URL: http://jira.codehaus.org/browse/MNG-3705 Project: Maven 2 Issue Type: Bug Components: Plugins and Life

[jira] Work started: (MNG-3705) Expression: ${executedProject} doesn't work in reports

2008-08-12 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3705 started by John Casey. > Expression: ${executedProject} doesn't work in reports > -- > > Key:

[jira] Work started: (MNG-3703) ExecutionProject contains relative paths in compileSourceRoots

2008-08-12 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3703 started by John Casey. > ExecutionProject contains relative paths in compileSourceRoots > -- > >

[jira] Reopened: (MNG-3703) ExecutionProject contains relative paths in compileSourceRoots

2008-08-12 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey reopened MNG-3703: - This is still happening for reports that execute a forked lifecycle. The executedProject contains non-concrete value

[jira] Closed: (MNG-3704) NPE in DefaultLIfecycleExecutor when run from within Hudson builds

2008-08-12 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3704. --- Resolution: Fixed > NPE in DefaultLIfecycleExecutor when run from within Hudson builds >

[jira] Commented: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144847#action_144847 ] Benjamin Bentmann commented on MJAVADOC-212: Considering the penalty of the forked life

[jira] Issue Comment Edited: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144846#action_144846 ] bentmann edited comment on MJAVADOC-212 at 8/12/08 1:44 PM: - An

[jira] Updated: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MJAVADOC-212: --- Attachment: javadoc-aggregation.patch Another idea: Currently, the parameter "aggregate"

[jira] Updated: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-212: - Attachment: MJAVADOC-212.patch Proposed patch. By default, AggregatorJavadocReport/Aggregato

[jira] Commented: (SUREFIRE-512) Provided Properties no longer visible in Surefire-Tests

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/SUREFIRE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144821#action_144821 ] Benjamin Bentmann commented on SUREFIRE-512: This change was introduced to fix SUREFIRE

[jira] Created: (SUREFIRE-512) Provided Properties no longer visible in Surefire-Tests

2008-08-12 Thread Jerome Waibel (JIRA)
Provided Properties no longer visible in Surefire-Tests --- Key: SUREFIRE-512 URL: http://jira.codehaus.org/browse/SUREFIRE-512 Project: Maven Surefire Issue Type: Bug Affects Versions:

[jira] Commented: (ARCHETYPE-199) Missing archetypes for Struts2

2008-08-12 Thread Lukasz Lenart (JIRA)
[ http://jira.codehaus.org/browse/ARCHETYPE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144812#action_144812 ] Lukasz Lenart commented on ARCHETYPE-199: - When I am using the latest version of this plug

[jira] Commented: (ARCHETYPE-199) Missing archetypes for Struts2

2008-08-12 Thread Wendy Smoak (JIRA)
[ http://jira.codehaus.org/browse/ARCHETYPE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144811#action_144811 ] Wendy Smoak commented on ARCHETYPE-199: --- I'm not sure where the list in the archetype plugin

[jira] Created: (ARCHETYPE-199) Missing archetypes for Struts2

2008-08-12 Thread Lukasz Lenart (JIRA)
Missing archetypes for Struts2 -- Key: ARCHETYPE-199 URL: http://jira.codehaus.org/browse/ARCHETYPE-199 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 2.0-alpha-1

[jira] Commented: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144792#action_144792 ] Vincent Siveton commented on MJAVADOC-212: -- A solution could be to move the aggregate para

[jira] Commented: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144786#action_144786 ] Vincent Siveton commented on MJAVADOC-212: -- In fact, I noticed some warn like the followin

[jira] Commented: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144785#action_144785 ] Vincent Siveton commented on MJAVADOC-212: -- To reproduce it, go to plugin-tools or plugin-

[jira] Updated: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-212: - Fix Version/s: 2.5 > AggregatorJavadocReport/AggregatorTestJavadocReport are used by default

[jira] Created: (MJAVADOC-212) AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated

2008-08-12 Thread Vincent Siveton (JIRA)
AggregatorJavadocReport/AggregatorTestJavadocReport are used by default in aggregator and no reports are generated -- Key: MJAVADOC-212 URL: http://jir

[jira] Closed: (MPLUGIN-133) JavaMojoDescriptorExtractor doesn't handle @requiresReport

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MPLUGIN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-133. --- Resolution: Fixed fixed in [r684956|http://svn.apache.org/viewvc?rev=684956&view=rev] > JavaMojoD

[jira] Closed: (MPLUGIN-134) Review the support of Mojo's annotations

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MPLUGIN-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-134. --- Resolution: Fixed Fix Version/s: 2.4.3 > Review the support of Mojo's annotations > ---

[jira] Commented: (MPLUGIN-133) JavaMojoDescriptorExtractor doesn't handle @requiresReport

2008-08-12 Thread Vincent Siveton (JIRA)
[ http://jira.codehaus.org/browse/MPLUGIN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144782#action_144782 ] Vincent Siveton commented on MPLUGIN-133: - bq. From your commit, I guess this meant "@requir

[jira] Commented: (MCHECKSTYLE-42) checkstyle does not take into account proxy settings from settings.xml

2008-08-12 Thread Stephen Connolly (JIRA)
[ http://jira.codehaus.org/browse/MCHECKSTYLE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144776#action_144776 ] Stephen Connolly commented on MCHECKSTYLE-42: - It makes publishing a org.codehaus.moj

[jira] Commented: (MPLUGIN-133) JavaMojoDescriptorExtractor doesn't handle @requiresReport

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/MPLUGIN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144773#action_144773 ] Benjamin Bentmann commented on MPLUGIN-133: --- Final note: This annotation shouldn't be stri

[jira] Updated: (MPLUGIN-133) JavaMojoDescriptorExtractor doesn't handle @requiresReport

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/MPLUGIN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MPLUGIN-133: -- Summary: JavaMojoDescriptorExtractor doesn't handle @requiresReport (was: JavaMojoDescripto

[jira] Commented: (MPLUGIN-133) JavaMojoDescriptorExtractor doesn't handle @requiresProject

2008-08-12 Thread Benjamin Bentmann (JIRA)
[ http://jira.codehaus.org/browse/MPLUGIN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144768#action_144768 ] Benjamin Bentmann commented on MPLUGIN-133: --- You're sure? Near line 301 it says {code:java

[jira] Commented: (MASSEMBLY-327) Using filtered within dependencySet unpackOptions

2008-08-12 Thread gotama (JIRA)
[ http://jira.codehaus.org/browse/MASSEMBLY-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144766#action_144766 ] gotama commented on MASSEMBLY-327: -- In analyzing the Maven Assembly Plugin code base, from what