[jira] Updated: (MNG-4869) Parent POM is not evaluated as expected, regression in Maven 3
[
http://jira.codehaus.org/browse/MNG-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4869:
---
Attachment: MNG-4869.zip
>From the information given, I'm not able to reproduce the issue using the
>attached example project. So please re-open with a complete/runnable project
>that exhibits the problem and allows its analysis.
> Parent POM is not evaluated as expected, regression in Maven 3
> --
>
> Key: MNG-4869
> URL: http://jira.codehaus.org/browse/MNG-4869
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_20
> Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac"
>Reporter: Joern Huxhorn
>Priority: Critical
> Attachments: MNG-4869.zip
>
>
> We have the following situation in our project:
> A parent pom containing the following infos:
>
> 6.1.9
>
>
>
>
> org.mortbay.jetty
> maven-jetty-plugin
> ${jettyVersion}
>
>
>
> A child module with the following configuration:
>
>
>
> org.mortbay.jetty
> maven-jetty-plugin
>
>
> org.mortbay.jetty
> jetty-plus
> ${jettyVersion}
>
>
> org.mortbay.jetty
> jetty-naming
> ${jettyVersion}
>
>
>
>
>
> The property jettyVersion was added during the latest. The parent pom is the
> first sub-module in the master pom, followed by the other sub-modules
> including the child-module above. All definitions include correct
> entries.
> Previously, it worked perfectly well to simply build the master pom, which in
> turn built the parent followed by all other sub-modules.
> Since Maven 3, however, this didn't work anymore. Right after the addition of
> the jettyVersion property, Maven 3 complained with the following error:
> [ERROR] The build could not read 24 projects -> [Help 1]
> [ERROR]
> [ERROR] The project xyz:2.0.0-SNAPSHOT (/path/to/child/pom.xml) has 2 errors
> [ERROR]
> 'build.plugins.plugin[org.mortbay.jetty:maven-jetty-plugin].dependencies.dependency.version'
> for org.mortbay.jetty:jetty-plus:jar must be a valid version but is
> '${jettyVersion}'. @ line 28, column 28
> [ERROR]
> 'build.plugins.plugin[org.mortbay.jetty:maven-jetty-plugin].dependencies.dependency.version'
> for org.mortbay.jetty:jetty-naming:jar must be a valid version but is
> '${jettyVersion}'. @ line 33, column 28
> Building the parent manually fixed this issue.
> To be precise, our actual project involved another parent level, i.e. the
> parent described above was the parent of parent2 while parent2 was the parent
> of the child module - but I don't think that this is relevant. I'm just
> mentioning it just in case. Again, all definitions include correct
> entries.
> This worked in Maven 2 so I think it's a regression.
--
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: (MNG-4864) npe when transferring artifacts
[
http://jira.codehaus.org/browse/MNG-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4864.
--
Resolution: Fixed
Fix Version/s: 3.0.1
Assignee: Benjamin Bentmann
That the update from 1.5.0_12 to 1.5.0_22 solves the issue puzzles me as I
don't see any changes in the source code for {{ConcurrentHashMap}} nor any
relevant bug mentioned in the release notes.
According to the API doc for
[{{ConcurrentHashMap.entrySet()}}|http://download.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ConcurrentHashMap.html#entrySet%28%29]:
bq. The view's returned iterator is a "weakly consistent" iterator that will
never throw ConcurrentModificationException, and guarantees to traverse
elements as they existed upon construction of the iterator, and may (but is not
guaranteed to) reflect any modifications subsequent to construction.
To my understanding, this means simple iterating over {{ConcurrentHashMap}} as
excercised in our code should be safe (i.e. return sane values) despite
concurrent updates even without higher-level locking.
The best explanation I can imagine is [JRE bug
#6312056|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6312056] for which
a guard has been added in
[r1023501|http://svn.apache.org/viewvc?view=revision&revision=1023501].
> npe when transferring artifacts
> ---
>
> Key: MNG-4864
> URL: http://jira.codehaus.org/browse/MNG-4864
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: jgon2
>Assignee: Benjamin Bentmann
> Fix For: 3.0.1
>
>
> I get the following NPE when running a mvn clean install with an empty local
> repository. The two stracktraces below show that the build breaks with
> different artifacts but always at the same place.
> If I relaunch the build several times, it finally succeeds.
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.cli.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:60)
>
> [ERROR] Failed to execute goal on project stdlib-core: Could not resolve
> dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project stdlib-core: Could not resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:190)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus
[jira] Closed: (MREACTOR-18) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MREACTOR-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MREACTOR-18. - Resolution: Fixed Fix Version/s: 1.1 Assignee: Benjamin Bentmann Applied in [r1023486|http://svn.apache.org/viewvc?view=revision&revision=1023486]. > Plugin documentation refers to "Maven 2" > > > Key: MREACTOR-18 > URL: http://jira.codehaus.org/browse/MREACTOR-18 > Project: Maven 2.x Reactor Plugin > Issue Type: Improvement >Affects Versions: 1.0 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 1.1 > > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MCOMPILER-137) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MCOMPILER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCOMPILER-137. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Benjamin Bentmann Applied in [r1023485|http://svn.apache.org/viewvc?view=revision&revision=1023485]. > Plugin documentation refers to "Maven 2" > > > Key: MCOMPILER-137 > URL: http://jira.codehaus.org/browse/MCOMPILER-137 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Affects Versions: 2.3.2 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.4 > > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MASSEMBLY-512) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MASSEMBLY-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MASSEMBLY-512. --- Resolution: Fixed Fix Version/s: 2.3 Assignee: Benjamin Bentmann Applied in [r1023484|http://svn.apache.org/viewvc?view=revision&revision=1023484]. > Plugin documentation refers to "Maven 2" > > > Key: MASSEMBLY-512 > URL: http://jira.codehaus.org/browse/MASSEMBLY-512 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.3 > > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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-336) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/ARCHETYPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed ARCHETYPE-336. --- Resolution: Fixed Fix Version/s: 2.0 Assignee: Benjamin Bentmann Applied in [r1023482|http://svn.apache.org/viewvc?view=revision&revision=1023482]. > Plugin documentation refers to "Maven 2" > > > Key: ARCHETYPE-336 > URL: http://jira.codehaus.org/browse/ARCHETYPE-336 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-5 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.0 > > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MANTRUN-156) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MANTRUN-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MANTRUN-156. - Resolution: Fixed Fix Version/s: 1.7 Assignee: Benjamin Bentmann Applied in [r1023480|http://svn.apache.org/viewvc?view=revision&revision=1023480]. > Plugin documentation refers to "Maven 2" > > > Key: MANTRUN-156 > URL: http://jira.codehaus.org/browse/MANTRUN-156 > Project: Maven 2.x Antrun Plugin > Issue Type: Improvement >Affects Versions: 1.6 >Reporter: Edward Staub >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 1.7 > > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MREACTOR-19) Plugin documentation refers to "Maven 2"
Plugin documentation refers to "Maven 2" Key: MREACTOR-19 URL: http://jira.codehaus.org/browse/MREACTOR-19 Project: Maven 2.x Reactor Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Benjamin Bentmann Priority: Minor Attachments: MNG-4868-maven-antrun-plugin.patch, MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch Documentation for these plugins makes them appear specific to Maven 2 - which at this point in time, makes them appear to NOT be for Maven 3. Plugins: antrun, archetype, assembly, compiler, reactor -- 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] Moved: (ARCHETYPE-336) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/ARCHETYPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MREACTOR-19 to ARCHETYPE-336: - Affects Version/s: (was: 1.0) 2.0-alpha-5 Key: ARCHETYPE-336 (was: MREACTOR-19) Project: Maven Archetype (was: Maven 2.x Reactor Plugin) > Plugin documentation refers to "Maven 2" > > > Key: ARCHETYPE-336 > URL: http://jira.codehaus.org/browse/ARCHETYPE-336 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-5 >Reporter: Benjamin Bentmann >Priority: Minor > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MCOMPILER-138) Plugin documentation refers to "Maven 2"
Plugin documentation refers to "Maven 2" Key: MCOMPILER-138 URL: http://jira.codehaus.org/browse/MCOMPILER-138 Project: Maven 2.x Compiler Plugin Issue Type: Improvement Affects Versions: 2.3.2 Reporter: Benjamin Bentmann Priority: Minor Attachments: MNG-4868-maven-antrun-plugin.patch, MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch Documentation for these plugins makes them appear specific to Maven 2 - which at this point in time, makes them appear to NOT be for Maven 3. Plugins: antrun, archetype, assembly, compiler, reactor -- 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] Moved: (MREACTOR-18) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MREACTOR-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MCOMPILER-138 to MREACTOR-18: - Affects Version/s: (was: 2.3.2) 1.0 Key: MREACTOR-18 (was: MCOMPILER-138) Project: Maven 2.x Reactor Plugin (was: Maven 2.x Compiler Plugin) > Plugin documentation refers to "Maven 2" > > > Key: MREACTOR-18 > URL: http://jira.codehaus.org/browse/MREACTOR-18 > Project: Maven 2.x Reactor Plugin > Issue Type: Improvement >Affects Versions: 1.0 >Reporter: Benjamin Bentmann >Priority: Minor > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MASSEMBLY-513) Plugin documentation refers to "Maven 2"
Plugin documentation refers to "Maven 2" Key: MASSEMBLY-513 URL: http://jira.codehaus.org/browse/MASSEMBLY-513 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Benjamin Bentmann Priority: Minor Attachments: MNG-4868-maven-antrun-plugin.patch, MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch Documentation for these plugins makes them appear specific to Maven 2 - which at this point in time, makes them appear to NOT be for Maven 3. Plugins: antrun, archetype, assembly, compiler, reactor -- 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] Moved: (MCOMPILER-137) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MCOMPILER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MASSEMBLY-513 to MCOMPILER-137: --- Affects Version/s: (was: 2.2) 2.3.2 Key: MCOMPILER-137 (was: MASSEMBLY-513) Project: Maven 2.x Compiler Plugin (was: Maven 2.x Assembly Plugin) > Plugin documentation refers to "Maven 2" > > > Key: MCOMPILER-137 > URL: http://jira.codehaus.org/browse/MCOMPILER-137 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Affects Versions: 2.3.2 >Reporter: Benjamin Bentmann >Priority: Minor > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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] Moved: (MANTRUN-156) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MANTRUN-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4868 to MANTRUN-156: Complexity: (was: Intermediate) Component/s: (was: Documentation: Introductions) (was: Documentation: Faqs) (was: Documentation: General) Affects Version/s: (was: 3.0) 1.6 Key: MANTRUN-156 (was: MNG-4868) Project: Maven 2.x Antrun Plugin (was: Maven 2 & 3) > Plugin documentation refers to "Maven 2" > > > Key: MANTRUN-156 > URL: http://jira.codehaus.org/browse/MANTRUN-156 > Project: Maven 2.x Antrun Plugin > Issue Type: Improvement >Affects Versions: 1.6 >Reporter: Edward Staub >Priority: Minor > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MANTRUN-157) Plugin documentation refers to "Maven 2"
Plugin documentation refers to "Maven 2" Key: MANTRUN-157 URL: http://jira.codehaus.org/browse/MANTRUN-157 Project: Maven 2.x Antrun Plugin Issue Type: Improvement Affects Versions: 1.6 Reporter: Benjamin Bentmann Priority: Minor Attachments: MNG-4868-maven-antrun-plugin.patch, MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch Documentation for these plugins makes them appear specific to Maven 2 - which at this point in time, makes them appear to NOT be for Maven 3. Plugins: antrun, archetype, assembly, compiler, reactor -- 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] Moved: (MASSEMBLY-512) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MASSEMBLY-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MANTRUN-157 to MASSEMBLY-512: - Affects Version/s: (was: 1.6) 2.2 Key: MASSEMBLY-512 (was: MANTRUN-157) Project: Maven 2.x Assembly Plugin (was: Maven 2.x Antrun Plugin) > Plugin documentation refers to "Maven 2" > > > Key: MASSEMBLY-512 > URL: http://jira.codehaus.org/browse/MASSEMBLY-512 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Benjamin Bentmann >Priority: Minor > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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-4868) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MNG-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239923#action_239923 ] Benjamin Bentmann commented on MNG-4868: Those issues should be filled against the plugin projects, not the Maven core. > Plugin documentation refers to "Maven 2" > > > Key: MNG-4868 > URL: http://jira.codehaus.org/browse/MNG-4868 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Documentation: General, Documentation: Faqs, > Documentation: Introductions >Affects Versions: 3.0 >Reporter: Edward Staub >Priority: Minor > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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: (MNGSITE-120) Archetype misspelled as Achetype
[ http://jira.codehaus.org/browse/MNGSITE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNGSITE-120. - Resolution: Fixed Assignee: Benjamin Bentmann Fixed in [r1023252|http://svn.apache.org/viewvc?view=revision&revision=1023252]. > Archetype misspelled as Achetype > > > Key: MNGSITE-120 > URL: http://jira.codehaus.org/browse/MNGSITE-120 > Project: Maven 2 Project Web Site > Issue Type: Bug > Environment: > http://maven.apache.org/guides/introduction/introduction-to-archetypes.html >Reporter: Adam Koch >Assignee: Benjamin Bentmann >Priority: Trivial > > There's a typo on > http://maven.apache.org/guides/introduction/introduction-to-archetypes.html. > Instead of "Maven provides several Achetype artifacts:" it should be "Maven > provides several Archetype artifacts:". -- 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: (MNG-4867) incorrect namespace in settings.xml
[ http://jira.codehaus.org/browse/MNG-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4867. -- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Benjamin Bentmann Fixed in [r1023249|http://svn.apache.org/viewvc?view=revision&revision=1023249]. > incorrect namespace in settings.xml > --- > > Key: MNG-4867 > URL: http://jira.codehaus.org/browse/MNG-4867 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Settings >Affects Versions: 3.0 >Reporter: Geert Schuring >Assignee: Benjamin Bentmann > Fix For: 3.0.1 > > Attachments: settings.xml.patch > > > The namespace used in 'xsd:schemaLocation' is not equal to the namespace used > by the root element, which means that editors will not assist when editing > the document, and will also not be able to validate the document. -- 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: (MNG-4865) mvn fails because of null property
[ http://jira.codehaus.org/browse/MNG-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4865. -- Resolution: Not A Bug Fix Version/s: (was: 2.2.1) > mvn fails because of null property > -- > > Key: MNG-4865 > URL: http://jira.codehaus.org/browse/MNG-4865 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.2.1 > Environment: windows vista32 >Reporter: eric zhu > > I downloaded maven and ran 'maven -version' under > 'C:\workplace\apache-maven-2.2.1\bin' > Got the error: > java.lang.NullPointerException: key can't be null > at java.lang.System.checkKey(System.java:771) > at java.lang.System.getProperty(System.java:647) > at > org.codehaus.classworlds.Configurator.configure(Configurator.java:240) > at org.codehaus.classworlds.Launcher.configure(Launcher.java:156) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:426) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > I ran the same on another XP PC with the same source, everything worked fine -- 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] Reopened: (MNG-4865) mvn fails because of null property
[ http://jira.codehaus.org/browse/MNG-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reopened MNG-4865: > mvn fails because of null property > -- > > Key: MNG-4865 > URL: http://jira.codehaus.org/browse/MNG-4865 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.2.1 > Environment: windows vista32 >Reporter: eric zhu > > I downloaded maven and ran 'maven -version' under > 'C:\workplace\apache-maven-2.2.1\bin' > Got the error: > java.lang.NullPointerException: key can't be null > at java.lang.System.checkKey(System.java:771) > at java.lang.System.getProperty(System.java:647) > at > org.codehaus.classworlds.Configurator.configure(Configurator.java:240) > at org.codehaus.classworlds.Launcher.configure(Launcher.java:156) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:426) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > I ran the same on another XP PC with the same source, everything worked fine -- 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-4864) npe when transferring artifacts
[
http://jira.codehaus.org/browse/MNG-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239689#action_239689
]
Benjamin Bentmann commented on MNG-4864:
bq. Java home: C:\bea923\jdk150_12\jre
Could you please retry this with a Sun/Oracle JRE as this looks like a JRE bug.
> npe when transferring artifacts
> ---
>
> Key: MNG-4864
> URL: http://jira.codehaus.org/browse/MNG-4864
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: jgon2
>
> I get the following NPE when running a mvn clean install with an empty local
> repository. The two stracktraces below show that the build breaks with
> different artifacts but always at the same place.
> If I relaunch the build several times, it finally succeeds.
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.cli.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:60)
>
> [ERROR] Failed to execute goal on project stdlib-core: Could not resolve
> dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project stdlib-core: Could not resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:190)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:156)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165)
>
> ... 22 more
> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.sonatype.aether.impl.internal.DefaultArtifactRe
[jira] Commented: (MNG-4864) npe when transferring artifacts
[
http://jira.codehaus.org/browse/MNG-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239497#action_239497
]
Benjamin Bentmann commented on MNG-4864:
The code in question:
{noformat}
for ( Map.Entry entry : downloads.entrySet() )
{
long total = entry.getKey().getContentLength();
long complete = entry.getValue().longValue(); // line 60
{noformat}
which suggests {{entry.getValue()}} is {{null}} which is interesting given that
we iterate a {{ConcurrentHashMap}} here which doesn't allow {{null}} values.
What JRE version/vendor are you using?
> npe when transferring artifacts
> ---
>
> Key: MNG-4864
> URL: http://jira.codehaus.org/browse/MNG-4864
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: jgon2
>
> I get the following NPE when running a mvn clean install with an empty local
> repository. The two stracktraces below show that the build breaks with
> different artifacts but always at the same place.
> If I relaunch the build several times, it finally succeeds.
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.cli.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:60)
>
> [ERROR] Failed to execute goal on project stdlib-core: Could not resolve
> dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project stdlib-core: Could not resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:190)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:156)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165)
>
> ... 22 more
> Caused by:
[jira] Closed: (MNG-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.
[ http://jira.codehaus.org/browse/MNG-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4863. -- Resolution: Won't Fix Assignee: Benjamin Bentmann > Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. > Getting ClasCastException. > -- > > Key: MNG-4863 > URL: http://jira.codehaus.org/browse/MNG-4863 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0 > Environment: Windows XP, Jdk 1.6.0_20 >Reporter: Bodhayan Chakraborty >Assignee: Benjamin Bentmann > > Hi, > I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. > ... > [ERROR] Failed to execute goal > org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) > on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 > cannot be cast to groovy.lang.GroovyObject -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > ... > This is the plugin that I am using. > > org.codehaus.groovy.maven > gmaven-plugin > > > > But if I change the plugin like below, it is working. > > org.codehaus.gmaven > gmaven-plugin > 1.3 > > > > Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to > 3.0? > Please let me know, > Thanks, > Bodhayan. -- 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: (MNG-4862) ConfigurationContainer.configuration should be of type Xpp3Dom, not Object
[
http://jira.codehaus.org/browse/MNG-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4862:
---
Issue Type: Improvement (was: Bug)
Yes, while ultimately a stronger typed signature is desired, this shouldn't be
based on {{Xpp3Dom}} but something from the Maven domain. {{Xpp3Dom}} is an
implementation detail, that ideally gets properly abstracted by means of an
interface.
> ConfigurationContainer.configuration should be of type Xpp3Dom, not Object
> --
>
> Key: MNG-4862
> URL: http://jira.codehaus.org/browse/MNG-4862
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Embedding
>Affects Versions: 3.0
>Reporter: Jesse Glick
>Priority: Minor
>
> All references to ConfigurationContainer.configuration, including the
> get/setConfiguration methods, treat it as a
> org.codehaus.plexus.util.xml.Xpp3Dom instance. Yet the signature is Object,
> and the Javadoc does not even mention the actual type. This is confusing and
> error-prone.
> Suggest changing the signature throughout to Xpp3Dom. If this cannot be done
> for reasons of binary compatibility, I would suggest: change the signature of
> the field; introduce a new setConfiguration(Xpp3Dom); @Deprecate
> setConfiguration(Object) and make it just call setConfiguration(Xpp3Dom)
> after casting; and update the Javadoc of getConfiguration to specify that it
> will always return an Xpp3Dom instance (or maybe null). (While the JVM is
> happy to have two no-arg methods with the same name but different return
> types, javac will not allow it; possible only by postprocessing bytecode.)
> Could also introduce new method names, e.g. get/setConfigurationDom.
> It seems that the bug may ultimately be in modello-plugin-java for handling
> DOM poorly. (JavaModelloGenerator, introduced by brett,
> commented on by demers.)
--
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: (MNG-4860) Allow management of project building request kept inside MavenProject instances
[
http://jira.codehaus.org/browse/MNG-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4860.
--
Resolution: Fixed
Fix Version/s: 3.0.1
Assignee: Benjamin Bentmann
Done in [r1021500|http://svn.apache.org/viewvc?view=revision&revision=1021500].
> Allow management of project building request kept inside MavenProject
> instances
> ---
>
> Key: MNG-4860
> URL: http://jira.codehaus.org/browse/MNG-4860
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Embedding, IDEs
>Affects Versions: 3.0
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 3.0.1
>
>
> For lazy construction/loading of some bits, {{MavenProject}} instances
> currently hold a reference to the {{ProjectBuildingRequest}} from which they
> were created. This proves to be problematic for IDE integration where those
> requests
> a) hold a fair amount of memory (in particular the repo system cache)
> b) hold references to potentially obsolete objects like GUI-backed transfer
> listeners
> As such IDE integrators have the need to either nullify or update this
> request.
--
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-4860) Allow management of project building request kept inside MavenProject instances
Allow management of project building request kept inside MavenProject instances
---
Key: MNG-4860
URL: http://jira.codehaus.org/browse/MNG-4860
Project: Maven 2 & 3
Issue Type: Improvement
Components: Embedding, IDEs
Affects Versions: 3.0
Reporter: Benjamin Bentmann
For lazy construction/loading of some bits, {{MavenProject}} instances
currently hold a reference to the {{ProjectBuildingRequest}} from which they
were created. This proves to be problematic for IDE integration where those
requests
a) hold a fair amount of memory (in particular the repo system cache)
b) hold references to potentially obsolete objects like GUI-backed transfer
listeners
As such IDE integrators have the need to either nullify or update this request.
--
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: (MNG-4854) [regression] ProjectSorter neglects conflicted versions
[
http://jira.codehaus.org/browse/MNG-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4854.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
If {{project:1.0}} depends on {{dependency:2.0}} then it doesn't depend on
{{dependency:1.0}}. See MNG-3814 for more details why versions matter.
> [regression] ProjectSorter neglects conflicted versions
> ---
>
> Key: MNG-4854
> URL: http://jira.codehaus.org/browse/MNG-4854
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.0-alpha-6
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 12:50:56+0100)
> Java version: 1.5.0_22
> Java home: C:\Program Files (x86)\Java\jdk1.5.0_22\jre
> Default locale: en_GB, platform encoding: Cp1252
> OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"
>Reporter: Mark Hobson
>Assignee: Benjamin Bentmann
> Attachments: MNG-4854-test.patch
>
>
> [ProjectSorter|http://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/project/ProjectSorter.java]
> skips vertexes where versions don't match and thus produces incorrect
> results.
> For example, if A depends on B:1.0 but B is resolved to 1.1 (via conflict
> resolution or dependency management) then A->B:1.0 is lost. One suspect
> could be {{isSpecificVersion}} which returns true for 1.0, which isn't a
> specific version like [1.0], so this vertex gets lost as B:1.0 doesn't exist.
--
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-4853) Make location of settings-security.xml configurable
[
http://jira.codehaus.org/browse/MNG-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237574#action_237574
]
Benjamin Bentmann commented on MNG-4853:
You should already be able to do so with the system property
{{settings.security}}.
> Make location of settings-security.xml configurable
> ---
>
> Key: MNG-4853
> URL: http://jira.codehaus.org/browse/MNG-4853
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Command Line
>Reporter: Alexander Syedin
>Priority: Minor
>
> Are there any reasons why we can't specify name and location of the
> settings-security.xml file exactly in the same we do with settings.xml?
> It would be nice to be able to specify it from command line, like:
> {code:none}
> mvn -ss path/to/security-settings.xml
> {code}
> This is essential in some environments, where user don't have control over
> home directory (like continuous integration farm, where each project may have
> it's own settings, but not settings-security.xml).
--
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] Moved: (MSITE-512) [Regression] Configuration of m-javadoc-p at reportSet level is not taken into account
[
http://jira.codehaus.org/browse/MSITE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-4852 to MSITE-512:
--
Complexity: (was: Intermediate)
Affects Version/s: (was: 3.0)
3.0-beta-2
Key: MSITE-512 (was: MNG-4852)
Project: Maven 2.x Site Plugin (was: Maven 2 & 3)
> [Regression] Configuration of m-javadoc-p at reportSet level is not taken
> into account
> --
>
> Key: MSITE-512
> URL: http://jira.codehaus.org/browse/MSITE-512
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 3.0-beta-2
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_21
>Reporter: Julien HENRY
>
> In the JWebUnit project I am using Javadoc aggregation and I put
> configuration at the level. But after upgrading to Maven 3 the
> configuration is not taken into account. Moving the configuration to the top
> level/common section works but may not be acceptable for all project
> especially when a different configuration for each reportSet is needed.
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.7
>
>
>
>
>
> aggregate
>
>
>
>
> aggregate
>
>
>
>
>
>
> {code}
> - with Maven 2 I am using m-site-p 2.1.1
> - with Maven 3 I am using m-site-p 3.0-beta-2
> I don't know if this is a M3 or a m-site-p regression.
--
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: (MSITE-512) [Regression] Configuration of m-javadoc-p at reportSet level is not taken into account
[
http://jira.codehaus.org/browse/MSITE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237523#action_237523
]
Benjamin Bentmann commented on MSITE-512:
-
The effective POM has the configuration:
{code:xml}
D:\z - Kopie\target\site
org.apache.maven.plugins
maven-javadoc-plugin
2.7
aggregate
bar
aggregate
org.apache.maven.plugins
maven-project-info-reports-plugin
{code}
> [Regression] Configuration of m-javadoc-p at reportSet level is not taken
> into account
> --
>
> Key: MSITE-512
> URL: http://jira.codehaus.org/browse/MSITE-512
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 3.0-beta-2
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_21
>Reporter: Julien HENRY
>
> In the JWebUnit project I am using Javadoc aggregation and I put
> configuration at the level. But after upgrading to Maven 3 the
> configuration is not taken into account. Moving the configuration to the top
> level/common section works but may not be acceptable for all project
> especially when a different configuration for each reportSet is needed.
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.7
>
>
>
>
>
> aggregate
>
>
>
>
> aggregate
>
>
>
>
>
>
> {code}
> - with Maven 2 I am using m-site-p 2.1.1
> - with Maven 3 I am using m-site-p 3.0-beta-2
> I don't know if this is a M3 or a m-site-p regression.
--
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: (MNG-4849) Use of version ranges triggers download of poms for *every* version
[ http://jira.codehaus.org/browse/MNG-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4849. -- Resolution: Not A Bug Assignee: Benjamin Bentmann This is by design, sophisticated conflict resolution strategies need to be able to see all allowed dependencies. > Use of version ranges triggers download of poms for *every* version > --- > > Key: MNG-4849 > URL: http://jira.codehaus.org/browse/MNG-4849 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 >Reporter: Vincent Latombe >Assignee: Benjamin Bentmann > Attachments: pom.xml, pom.xml > > > With beta-3, the following pom triggers the download of *every* version > between 2.0 and 3.0, whereas with previous version only the relevant version > (3.0-beta-3) was downloaded -- 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] Moved: (MASSEMBLY-508) finalName not taken into account for attached assemblies
[
http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-4848 to MASSEMBLY-508:
--
Complexity: (was: Intermediate)
Affects Version/s: (was: 2.2.1)
Key: MASSEMBLY-508 (was: MNG-4848)
Project: Maven 2.x Assembly Plugin (was: Maven 2 & 3)
> finalName not taken into account for attached assemblies
>
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the
> project. Whatever I define in
> {code}
>
> ...
> [The name I want it to be]
> ...
>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of
> the artifacts?!
--
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: (MNG-4846) Profile activated accidentially
[
http://jira.codehaus.org/browse/MNG-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4846.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
This works as designed, since {{"Value".equals( System.getProperty(
"somePropertyName" ) ) == false}}.
> Profile activated accidentially
> ---
>
> Key: MNG-4846
> URL: http://jira.codehaus.org/browse/MNG-4846
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
>Reporter: Maik Richey
>Assignee: Benjamin Bentmann
>Priority: Critical
>
> When you define a profile activated like
> {code}
> ...
>
>
> someCase
>
> false
>
> somePropertyName
> !Value
>
>
> ...
>
>
> ...
> {code}
> this profile will also be activated when no property/profile is defined on
> the command line. I expected that profile beeing activated only when you
> supply -DsomePropertyName=NotTheValue.
--
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-4846) Profile activated accidentially
[
http://jira.codehaus.org/browse/MNG-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237370#action_237370
]
Benjamin Bentmann edited comment on MNG-4846 at 10/4/10 5:30 AM:
-
This works as designed, since {{"Value".equals( System.getProperty(
"somePropertyName" ) ) == false}} when {{somePropertyName}} has not been
specified.
was (Author: bentmann):
This works as designed, since {{"Value".equals( System.getProperty(
"somePropertyName" ) ) == false}}.
> Profile activated accidentially
> ---
>
> Key: MNG-4846
> URL: http://jira.codehaus.org/browse/MNG-4846
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.2.1
>Reporter: Maik Richey
>Assignee: Benjamin Bentmann
>Priority: Critical
>
> When you define a profile activated like
> {code}
> ...
>
>
> someCase
>
> false
>
> somePropertyName
> !Value
>
>
> ...
>
>
> ...
> {code}
> this profile will also be activated when no property/profile is defined on
> the command line. I expected that profile beeing activated only when you
> supply -DsomePropertyName=NotTheValue.
--
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: (MASSEMBLY-508) finalName not taken into account for attached assemblies
[
http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237364#action_237364
]
Benjamin Bentmann edited comment on MASSEMBLY-508 at 10/4/10 4:28 AM:
--
The name of an artifact in the local/remote repo is exclusively controlled by
the repository layout. How the assemblies created in the project output
directory are named, is controlled by the plugin creating those assemblies.
was (Author: bentmann):
The name of an artifact in the local/remote repo is exclusively controlled
by the repository layout. How the assembly created in the project output
directory are named, is controlled by the plugin creating those assemblies.
> finalName not taken into account for attached assemblies
>
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the
> project. Whatever I define in
> {code}
>
> ...
> [The name I want it to be]
> ...
>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of
> the artifacts?!
--
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-508) finalName not taken into account for attached assemblies
[
http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237364#action_237364
]
Benjamin Bentmann commented on MASSEMBLY-508:
-
The name of an artifact in the local/remote repo is exclusively controlled by
the repository layout. How the assembly created in the project output directory
are named, is controlled by the plugin creating those assemblies.
> finalName not taken into account for attached assemblies
>
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the
> project. Whatever I define in
> {code}
>
> ...
> [The name I want it to be]
> ...
>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of
> the artifacts?!
--
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-4847) The skin does not exist: Unable to determine the release version
[
http://jira.codehaus.org/browse/MNG-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237367#action_237367
]
Benjamin Bentmann commented on MNG-4847:
The crucial piece here is the contents of the files
{{org/apache/maven/skins/maven-default-skin/maven-metadata-*.xml}} in the local
repository and logs that would explain why in particular
{{maven-metadata-central.xml}} doesn't match the [remote copy of this
file|http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml].
Unless somebody starts to provide those information, we have quite nothing to
try and analyze this.
> The skin does not exist: Unable to determine the release version
>
>
> Key: MNG-4847
> URL: http://jira.codehaus.org/browse/MNG-4847
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Sites & Reporting
>Reporter: Tobias Budde
>Assignee: John Casey
> Fix For: 2.0.11
>
>
> hi I have problem generating site when im using the command mvn site
> it performs all stagegs and when it came to site generation the message is
> shown :
> The skin does not exist: Unable to determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven
> -default-skin \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
> do u have an idea what is the problem ?
> p.s the jar is registered in my local repository and in the remote repository
> thank u
--
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-508) attach-descriptor goals leaks file handlers, causing sporadic build failures when gpg tries to sign descriptor during release
attach-descriptor goals leaks file handlers, causing sporadic build failures
when gpg tries to sign descriptor during release
-
Key: MSITE-508
URL: http://jira.codehaus.org/browse/MSITE-508
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: site descriptor
Affects Versions: 3.0-beta-2, 2.1.1
Reporter: Benjamin Bentmann
An excerpt from a debug log:
{noformat}
[INFO] --- maven-site-plugin:3.0-beta-2:attach-descriptor (attach-descriptor) @
mojo-parent ---
[INFO] Parent project loaded from repository.
[DEBUG] Attaching the site descriptor
'D:\codehaus\mojo\mojo\mojo-parent\target\mojo-parent-27-SNAPSHOT-site.xml'
with classifier 'site' to the project.
[INFO]
[INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent ---
[DEBUG] Generating signature for
D:\codehaus\mojo\mojo\mojo-parent\target\mojo-parent-27-SNAPSHOT.pom
[DEBUG] Generating signature for
D:\codehaus\mojo\mojo\mojo-parent\target\mojo-parent-27-SNAPSHOT-source-release.zip
[DEBUG] Generating signature for
D:\codehaus\mojo\mojo\mojo-parent\target\mojo-parent-27-SNAPSHOT-site.xml
gpg: can't open
`D:\codehaus\mojo\mojo\mojo-parent\target\mojo-parent-27-SNAPSHOT-site.xml': No
error
gpg: signing failed: file open error
{noformat}
The cause for this is that {{site:attach-descriptor}} leaks at least two file
handles, once in the call {{IOUtil.toString( ReaderFactory.newXmlReader(
descriptorFile ) );}} and more importantly in {{Writer writer =
WriterFactory.newXmlWriter( interpolatedDescriptorFile );}}. Those
readers/writers get never closed, and can prevent other mojos from properly
accessing those files.
--
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: (MNG-4845) [regression] MavenProject.getDependencyArtifact() returns artifacts without version for dependency with version range
[
http://jira.codehaus.org/browse/MNG-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4845.
--
Resolution: Fixed
Fix Version/s: 3.0
Assignee: Benjamin Bentmann
Fixed in [r1003537|http://svn.apache.org/viewvc?view=revision&revision=1003537].
> [regression] MavenProject.getDependencyArtifact() returns artifacts without
> version for dependency with version range
> -
>
> Key: MNG-4845
> URL: http://jira.codehaus.org/browse/MNG-4845
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.0-beta-3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> For a dependency using a version range, the corresponding artifact in
> {{MavenProject.getDependencyArtifacts()}} has no resolved version.
> Concrete case that exhibits this bug is {{mvn versions:resolve-ranges}}.
--
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-4845) [regression] MavenProject.getDependencyArtifact() returns artifacts without version for dependency with version range
[regression] MavenProject.getDependencyArtifact() returns artifacts without
version for dependency with version range
-
Key: MNG-4845
URL: http://jira.codehaus.org/browse/MNG-4845
Project: Maven 2 & 3
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.0-beta-3
Reporter: Benjamin Bentmann
For a dependency using a version range, the corresponding artifact in
{{MavenProject.getDependencyArtifacts()}} has no resolved version.
--
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: (MNG-4845) [regression] MavenProject.getDependencyArtifact() returns artifacts without version for dependency with version range
[
http://jira.codehaus.org/browse/MNG-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4845:
---
Description:
For a dependency using a version range, the corresponding artifact in
{{MavenProject.getDependencyArtifacts()}} has no resolved version.
Concrete case that exhibits this bug is {{mvn versions:resolve-ranges}}.
was:For a dependency using a version range, the corresponding artifact in
{{MavenProject.getDependencyArtifacts()}} has no resolved version.
> [regression] MavenProject.getDependencyArtifact() returns artifacts without
> version for dependency with version range
> -
>
> Key: MNG-4845
> URL: http://jira.codehaus.org/browse/MNG-4845
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.0-beta-3
>Reporter: Benjamin Bentmann
>
> For a dependency using a version range, the corresponding artifact in
> {{MavenProject.getDependencyArtifacts()}} has no resolved version.
> Concrete case that exhibits this bug is {{mvn versions:resolve-ranges}}.
--
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: (MNG-4844) Maven 3 RC1 crashes with IBM JDK 6
[ http://jira.codehaus.org/browse/MNG-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4844. -- Resolution: Duplicate Assignee: Benjamin Bentmann Known bug in the IBM/Harmony class library, please try [3.0-RC3|https://repository.apache.org/content/repositories/maven-014/org/apache/maven/apache-maven/3.0-RC3/] where we added a workaround. > Maven 3 RC1 crashes with IBM JDK 6 > -- > > Key: MNG-4844 > URL: http://jira.codehaus.org/browse/MNG-4844 > Project: Maven 2 & 3 > Issue Type: Bug > Environment: Apache Maven 3.0-RC1 (r997478; 2010-09-15 21:57:55+0200) > Java version: 1.6.0 > Java home: C:\Dev\ibm_jdk1.6.0_8\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" > Family: "windows" > IBM JDK 6: > java version "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: Julian Payne >Assignee: Benjamin Bentmann >Priority: Blocker > Attachments: mvn3-crash.zip > > > Running the minimal project that is provided crashes maven with this error: > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at > org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:600) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: java.lang.NullPointerException > at > org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.getInheritedScopes(JavaEffectiveScopeCalculator.java:149) > at > org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.resolve(JavaEffectiveScopeCalculator.java:126) > at > org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.transformGraph(JavaEffectiveScopeCalculator.java:80) > at > org.sonatype.aether.util.graph.transformer.ChainedDependencyGraphTransformer.transformGraph(ChainedDependencyGraphTransformer.java:76) > at > org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:246) > at > org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:265) > at > org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104) > at > org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > All the details are in the readme.txt in the attached zip file. -- This message is a
[jira] Issue Comment Edited: (MNG-4843) maven-glassfish-plugin does not work with maven 3.0-RC3 (works with 2.2.1)
[
http://jira.codehaus.org/browse/MNG-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236942#action_236942
]
Benjamin Bentmann edited comment on MNG-4843 at 9/30/10 4:30 AM:
-
The plugin depends on several Maven APIs using the unbounded version range
{{[2.0,)}}. Apart from the fact that this itself is a bad idea, in your
environment the range happens to select an unofficial release of
maven-plugin-api which inherits from maven-parent:9-SNAPSHOT which is
apparently mising in your repo manager.
So either get the plugin maintainers to use a specific version for their
dependencies, override the plugin dependencies in your project with proper
versions or ensure your repo mananager doesn't expose broken artifacts to the
build.
was (Author: bentmann):
The plugin depends on several Maven APIs using the unbounded version range
{{[2.0,)}}. Apart from the fact that this itself is a bad idea, in your
environment the range happens to select an unofficial release of
maven-plugin-api which inherits from maven-parent:9-SNAPSHOT which is
apparently mising in your repo manager.
So either get the plugin maintainer to use a specific version for their
dependencies or ensure your repo mananager doesn't expose broken artifacts to
the build.
> maven-glassfish-plugin does not work with maven 3.0-RC3 (works with 2.2.1)
> --
>
> Key: MNG-4843
> URL: http://jira.codehaus.org/browse/MNG-4843
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0-beta-3
> Environment: maven 3.0-RC3
> Ubuntu Linux
>Reporter: Ulli Hafner
>Assignee: Benjamin Bentmann
>
> Deployments to glassfish don't work with maven 3 (the same steps work with
> maven 2.2.1). Seems that there is a dependency missing.
> I'm using the following plugin:
>
>
>
> org.glassfish.maven.plugin
> maven-glassfish-plugin
> 2.1
> ...
> (URL:
> http://download.java.net/maven/2/org/glassfish/maven/plugin/maven-glassfish-plugin/2.1/)
> mvn org.glassfish.maven.plugin:maven-glassfish-plugin:deploy
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building FIPS 4 FSPM Product Data Service EAR 1.0.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-glassfish-plugin:2.1:deploy (default-cli) @
> com.f10.ips4fspm.connect.prdservices.ear ---
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC4-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC5-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC6-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC7-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC8-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC9-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC3-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC4-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC5-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC6-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC7-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.12-SNAPSHOT
> is missing, no dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT
> is missing, no dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.1-SNAPSHOT is
> missing, no dependency information available
> [WARNING] The POM for
> org.apache.maven.artifact:maven-artifact:jar:3.0-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.xbean:xbean-reflect:jar:3.4-20080418.173627-4 is missing, no
> dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-ap
[jira] Closed: (MNG-4843) maven-glassfish-plugin does not work with maven 3.0-RC3 (works with 2.2.1)
[
http://jira.codehaus.org/browse/MNG-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4843.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
The plugin depends on several Maven APIs using the unbounded version range
{{[2.0,)}}. Apart from the fact that this itself is a bad idea, in your
environment the range happens to select an unofficial release of
maven-plugin-api which inherits from maven-parent:9-SNAPSHOT which is
apparently mising in your repo manager.
So either get the plugin maintainer to use a specific version for their
dependencies or ensure your repo mananager doesn't expose broken artifacts to
the build.
> maven-glassfish-plugin does not work with maven 3.0-RC3 (works with 2.2.1)
> --
>
> Key: MNG-4843
> URL: http://jira.codehaus.org/browse/MNG-4843
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0-beta-3
> Environment: maven 3.0-RC3
> Ubuntu Linux
>Reporter: Ulli Hafner
>Assignee: Benjamin Bentmann
>
> Deployments to glassfish don't work with maven 3 (the same steps work with
> maven 2.2.1). Seems that there is a dependency missing.
> I'm using the following plugin:
>
>
>
> org.glassfish.maven.plugin
> maven-glassfish-plugin
> 2.1
> ...
> (URL:
> http://download.java.net/maven/2/org/glassfish/maven/plugin/maven-glassfish-plugin/2.1/)
> mvn org.glassfish.maven.plugin:maven-glassfish-plugin:deploy
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building FIPS 4 FSPM Product Data Service EAR 1.0.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-glassfish-plugin:2.1:deploy (default-cli) @
> com.f10.ips4fspm.connect.prdservices.ear ---
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC4-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC5-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC6-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC7-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC8-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.9-RC9-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC3-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC4-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC5-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC6-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.maven:maven-plugin-api:jar:2.0.10-RC7-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.0.12-SNAPSHOT
> is missing, no dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.1.0-M2-SNAPSHOT
> is missing, no dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:2.1-SNAPSHOT is
> missing, no dependency information available
> [WARNING] The POM for
> org.apache.maven.artifact:maven-artifact:jar:3.0-SNAPSHOT is missing, no
> dependency information available
> [WARNING] The POM for
> org.apache.xbean:xbean-reflect:jar:3.4-20080418.173627-4 is missing, no
> dependency information available
> [WARNING] The POM for org.apache.maven:maven-plugin-api:jar:3.0-SNAPSHOT is
> missing, no dependency information available
> [WARNING] The POM for
> org.codehaus.plexus:plexus-component-annotations:jar:1.2.1-SNAPSHOT is
> missing, no dependency information available
> [WARNING] The POM for
> org.codehaus.plexus:plexus-container-default:jar:1.2.1-SNAPSHOT is missing,
> no dependency information available
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4.227s
> [INFO] Finished at: Thu Sep 30 10:23:21 CEST 2010
> [INFO] Fi
[jira] Commented: (MNG-4002) ComponentConfigurationException When Trying to Build Nexus With Maven
[ http://jira.codehaus.org/browse/MNG-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236903#action_236903 ] Benjamin Bentmann commented on MNG-4002: Suresh, be sure to specify the implementation attribute as shown in the [examples|http://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html]. This still failing, you would have to provide an example project to demonstrate the issue or nobody can tell why it doesn't work for you but works for others. > ComponentConfigurationException When Trying to Build Nexus With Maven > - > > Key: MNG-4002 > URL: http://jira.codehaus.org/browse/MNG-4002 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-alpha-2 >Reporter: Shane Isbell > Fix For: 3.0-alpha-2 > > Attachments: out.txt > > > During source:jar phase, receive the following error when building > nexus-indexer with maven: > [ERROR] > org.codehaus.plexus.component.configurator.ComponentConfigurationException: > Class 'org.apache.maven.plugins.shade.resource.ResourceTransformer' cannot be > instantiated -- 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: (MNG-4842) [regression] Repositories discovered in dependency POMs override repositories configured for original resolution request of POM
[ http://jira.codehaus.org/browse/MNG-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4842. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Fixed in [r1002852|http://svn.apache.org/viewvc?view=revision&revision=1002852]. > [regression] Repositories discovered in dependency POMs override repositories > configured for original resolution request of POM > --- > > Key: MNG-4842 > URL: http://jira.codehaus.org/browse/MNG-4842 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.0-beta-3 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann > Fix For: 3.0 > > > When processing/building a dependency POM during transitive resolution, the > repos declared in that POM erroneously take precedence over the repos > specified for the original request when parent POMs of said POM need to be > resolved. The potential results of this bug are network trips to wrong repos > or resolution failures due to wrong repo policies being applied. -- 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-4842) [regression] Repositories discovered in dependency POMs override repositories configured for original resolution request of POM
[regression] Repositories discovered in dependency POMs override repositories configured for original resolution request of POM --- Key: MNG-4842 URL: http://jira.codehaus.org/browse/MNG-4842 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories, Dependencies Affects Versions: 3.0-beta-3 Reporter: Benjamin Bentmann When processing/building a dependency POM during transitive resolution, the repos declared in that POM erroneously take precedence over the repos specified for the original request when parent POMs of said POM need to be resolved. The potential results of this bug are network trips to wrong repos or resolution failures due to wrong repo policies being applied. -- 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: (MNG-4839) plugin dependencies not resolved form repositories
[
http://jira.codehaus.org/browse/MNG-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4839.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
Misunderstanding, {{hibernate-tools}} is a plugin dependency and hence must be
resolvable from the {{ plugin dependencies not resolved form repositories
> --
>
> Key: MNG-4839
> URL: http://jira.codehaus.org/browse/MNG-4839
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0-beta-1, 3.0-beta-3
> Environment: Apache Maven 3.0-RC3 (r1001464; 2010-09-26 18:14:28+0200)
> Java version: 1.6.0_21
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>Reporter: Michael Brackx
>Assignee: Benjamin Bentmann
> Attachments: pom.xml
>
>
> plugin dependencies are not resolved from repositories in
> regression from 2.2.1
> the
> [wiki|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginRepositories]
> mentions
> "For clarity, this rule only applies to the resolution of the root artifact.
> In other words, while a plugin is only resolved from a ,
> the dependencies of the plugin are resolved from the original
> and any specified in the plugin's POM."
> example pom is attached
> error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.3:run (process-classes) on
> project bug: Execution process-classes of goal
> org.apache.maven.plugins:maven-antrun-plugin:1.3:run failed: Plugin
> org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies
> could not be resolved: Could not find artifact
> org.hibernate:hibernate-tools:jar:3.2.4.GA in central
> (http://repo1.maven.org/maven2) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
--
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: (MNG-4798) NullPointerException at NearestVersionConflictResolver.selectVersion()
[ http://jira.codehaus.org/browse/MNG-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4798. -- Resolution: Duplicate > NullPointerException at NearestVersionConflictResolver.selectVersion() > -- > > Key: MNG-4798 > URL: http://jira.codehaus.org/browse/MNG-4798 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: Maven 3 beta-3, Linux, Java 1.6.0_21 >Reporter: Jochen Stiepel >Assignee: Benjamin Bentmann > > this error only occurs with Maven 3 beta-3 but not Maven 3 beta-2. > Maby it is related to this error, but has a different stacktrace: MNG-4779 > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at > org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:141) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:99) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:600) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: java.lang.NullPointerException > at > org.sonatype.aether.util.graph.transformer.NearestVersionConflictResolver.selectVersion(NearestVersionConflictResolver.java:218) > at > org.sonatype.aether.util.graph.transformer.NearestVersionConflictResolver.transformGraph(NearestVersionConflictResolver.java:81) > at > org.sonatype.aether.util.graph.transformer.ChainedDependencyGraphTransformer.transformGraph(ChainedDependencyGraphTransformer.java:76) > at > org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:246) > at > org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:265) > at > org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:202) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:141) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveDependencies(LifecycleDependencyResolver.java:118) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveDependencies(LifecycleDependencyResolver.java:82) > at > org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:130) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:83) > ... 16 more -- 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] Reopened: (MNG-4798) NullPointerException at NearestVersionConflictResolver.selectVersion()
[ http://jira.codehaus.org/browse/MNG-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reopened MNG-4798: > NullPointerException at NearestVersionConflictResolver.selectVersion() > -- > > Key: MNG-4798 > URL: http://jira.codehaus.org/browse/MNG-4798 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: Maven 3 beta-3, Linux, Java 1.6.0_21 >Reporter: Jochen Stiepel >Assignee: Benjamin Bentmann > > this error only occurs with Maven 3 beta-3 but not Maven 3 beta-2. > Maby it is related to this error, but has a different stacktrace: MNG-4779 > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at > org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:141) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:99) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:600) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: java.lang.NullPointerException > at > org.sonatype.aether.util.graph.transformer.NearestVersionConflictResolver.selectVersion(NearestVersionConflictResolver.java:218) > at > org.sonatype.aether.util.graph.transformer.NearestVersionConflictResolver.transformGraph(NearestVersionConflictResolver.java:81) > at > org.sonatype.aether.util.graph.transformer.ChainedDependencyGraphTransformer.transformGraph(ChainedDependencyGraphTransformer.java:76) > at > org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:246) > at > org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:265) > at > org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:202) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:141) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveDependencies(LifecycleDependencyResolver.java:118) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveDependencies(LifecycleDependencyResolver.java:82) > at > org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:130) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:83) > ... 16 more -- 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: (MNG-4794) 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is missing: org.codehaus.plexus.digest.Digester
[ http://jira.codehaus.org/browse/MNG-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4794. -- Resolution: Fixed Fix Version/s: 3.0 Installed workaround for JRE bug in [r1001459|http://svn.apache.org/viewvc?view=revision&revision=1001459]. > 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is > missing: org.codehaus.plexus.digest.Digester > --- > > Key: MNG-4794 > URL: http://jira.codehaus.org/browse/MNG-4794 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: Linux 2.6.27.48-0.6-pae #1 SMP 686 athlon i386 GNU/Linux > - SUSE Linux Enterprise Server 11. > Java 1.6.0_21 Sun >Reporter: Jochen Stiepel >Assignee: Benjamin Bentmann >Priority: Blocker > Fix For: 3.0 > > > This error doesn't show up on Windows with maven 3 beta-3, Java 1.6.0_21 !!! > This error also doesn't show up with maven 3 beta-2 on Linux and Windows, > both Java 1.6.0_21. > I switched from maven 3 beta-2 to beta-3 and got this error. > I deleted the complete .m2/repository/ but nothing changed. > Only on Linux with maven 3 beta-3 I can reproduce this error: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install) > on project nivadis: Execution default-install of goal > org.apache.maven.plugins:maven-install-plugin:2.3.1:install failed: Unable to > load the mojo 'install' in the plugin > 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is > missing: org.codehaus.plexus.digest.Digester > - > realm =plugin>org.apache.maven.plugins:maven-install-plugin:2.3.1 > strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > urls[0] = > file:/home/vbs/.m2/repository/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar > urls[1] = > file:/home/vbs/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > Number of foreign imports: 4 > import: Entry[import org.codehaus.plexus.util.xml.pull.XmlSerializer from > realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.util.xml.pull.XmlPullParserException > from realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.util.xml.pull.XmlPullParser from > realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.util.xml.Xpp3Dom from realm > ClassRealm[plexus.core, parent: null]] > realm =maven.api > strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > Number of foreign imports: 21 > import: Entry[import org.sonatype.aether from realm ClassRealm[plexus.core, > parent: null]] > import: Entry[import org.codehaus.plexus.personality from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.logging from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.lifecycle from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.context from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.container from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.configuration from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.component from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.classworlds from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.PlexusContainerException from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.PlexusContainer from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.PlexusConstants from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.MutablePlexusContainer from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DuplicateChildContainerException > from realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DefaultPlexusContainer from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DefaultContainerConfiguration from > realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DefaultComponentRegistry from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.ContainerConfiguration from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codeha
[jira] Reopened: (MNG-4794) 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is missing: org.codehaus.plexus.digest.Digester
[ http://jira.codehaus.org/browse/MNG-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reopened MNG-4794: > 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is > missing: org.codehaus.plexus.digest.Digester > --- > > Key: MNG-4794 > URL: http://jira.codehaus.org/browse/MNG-4794 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: Linux 2.6.27.48-0.6-pae #1 SMP 686 athlon i386 GNU/Linux > - SUSE Linux Enterprise Server 11. > Java 1.6.0_21 Sun >Reporter: Jochen Stiepel >Assignee: Benjamin Bentmann >Priority: Blocker > Fix For: 3.0 > > > This error doesn't show up on Windows with maven 3 beta-3, Java 1.6.0_21 !!! > This error also doesn't show up with maven 3 beta-2 on Linux and Windows, > both Java 1.6.0_21. > I switched from maven 3 beta-2 to beta-3 and got this error. > I deleted the complete .m2/repository/ but nothing changed. > Only on Linux with maven 3 beta-3 I can reproduce this error: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install) > on project nivadis: Execution default-install of goal > org.apache.maven.plugins:maven-install-plugin:2.3.1:install failed: Unable to > load the mojo 'install' in the plugin > 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is > missing: org.codehaus.plexus.digest.Digester > - > realm =plugin>org.apache.maven.plugins:maven-install-plugin:2.3.1 > strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > urls[0] = > file:/home/vbs/.m2/repository/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar > urls[1] = > file:/home/vbs/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > Number of foreign imports: 4 > import: Entry[import org.codehaus.plexus.util.xml.pull.XmlSerializer from > realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.util.xml.pull.XmlPullParserException > from realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.util.xml.pull.XmlPullParser from > realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.util.xml.Xpp3Dom from realm > ClassRealm[plexus.core, parent: null]] > realm =maven.api > strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > Number of foreign imports: 21 > import: Entry[import org.sonatype.aether from realm ClassRealm[plexus.core, > parent: null]] > import: Entry[import org.codehaus.plexus.personality from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.logging from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.lifecycle from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.context from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.container from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.configuration from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.component from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.classworlds from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.PlexusContainerException from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.PlexusContainer from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.PlexusConstants from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.MutablePlexusContainer from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DuplicateChildContainerException > from realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DefaultPlexusContainer from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DefaultContainerConfiguration from > realm ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.DefaultComponentRegistry from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.ContainerConfiguration from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.plexus.ComponentRegistry from realm > ClassRealm[plexus.core, parent: null]] > import: Entry[import org.codehaus.classworlds from realm > ClassRealm[
[jira] Closed: (MNG-4834) [regression] MavenProject.getParent() ignores configured repositories
[ http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4834. -- Resolution: Fixed Fix Version/s: 3.0 Fixed in [r1001236|http://svn.apache.org/viewvc?view=revision&revision=1001236]. Note that your example project continues to suffer from MSHARED-164. > [regression] MavenProject.getParent() ignores configured repositories > - > > Key: MNG-4834 > URL: http://jira.codehaus.org/browse/MNG-4834 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: $ mvn -v > Apache Maven 3.0-RC2 (r1000119; 2010-09-22 20:23:26+0200) > Java version: 1.6.0_21 > Java home: /opt/sun-jdk-1.6.0.21/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.34-gentoo-r6" arch: "i386" Family: "unix" >Reporter: Joerg Schaible >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 3.0 > > Attachments: MNG-4834-remote-repo.tgz, MNG-4834.tgz, MNG-settings.xml > > > The site descriptor from the parent project is no longer found in the local > repository. The site plugin tries always to resolve the artifact from the > remote repository using the attach-descriptor goal. This is nasty if that > repo is not reachable and Maven will wait always until the connection times > out before continuing. With M2 this descriptor is found in the local repo: > "Parent project loaded from repository.". In both cases version 2.1.1 of the > site plugin is used. There's no change in behavior for M3 if the site plugin > is upgraded to 3.x. -- 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: (MNG-4834) [regression] MavenProject.getParent() ignores configured repositories
[ http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4834: --- Summary: [regression] MavenProject.getParent() ignores configured repositories (was: Site descriptor of parent is no longer found in local repository) > [regression] MavenProject.getParent() ignores configured repositories > - > > Key: MNG-4834 > URL: http://jira.codehaus.org/browse/MNG-4834 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: $ mvn -v > Apache Maven 3.0-RC2 (r1000119; 2010-09-22 20:23:26+0200) > Java version: 1.6.0_21 > Java home: /opt/sun-jdk-1.6.0.21/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.34-gentoo-r6" arch: "i386" Family: "unix" >Reporter: Joerg Schaible >Assignee: Benjamin Bentmann >Priority: Minor > Attachments: MNG-4834-remote-repo.tgz, MNG-4834.tgz, MNG-settings.xml > > > The site descriptor from the parent project is no longer found in the local > repository. The site plugin tries always to resolve the artifact from the > remote repository using the attach-descriptor goal. This is nasty if that > repo is not reachable and Maven will wait always until the connection times > out before continuing. With M2 this descriptor is found in the local repo: > "Parent project loaded from repository.". In both cases version 2.1.1 of the > site plugin is used. There's no change in behavior for M3 if the site plugin > is upgraded to 3.x. -- 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: (MSHARED-164) Avoid needless resolution of local parent POM if relativePath is empty
[
http://jira.codehaus.org/browse/MSHARED-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MSHARED-164.
-
Resolution: Fixed
Fix Version/s: maven-doxia-tools 1.3
Assignee: Benjamin Bentmann
Fixed in [r1001223|http://svn.apache.org/viewvc?view=revision&revision=1001223].
> Avoid needless resolution of local parent POM if relativePath is empty
> --
>
> Key: MSHARED-164
> URL: http://jira.codehaus.org/browse/MSHARED-164
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-doxia-tools
>Affects Versions: maven-doxia-tools 1.2.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Trivial
> Fix For: maven-doxia-tools 1.3
>
>
> For {{parent.relativePath=""}} {{DefaultSiteTool.getParentProject()}}
> effectively re-builds the current project instead of its parent. Instead, the
> tool should directly build it from the remote repo.
--
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: (MSHARED-164) Avoid needless resolution of local parent POM if relativePath is empty
Avoid needless resolution of local parent POM if relativePath is empty
--
Key: MSHARED-164
URL: http://jira.codehaus.org/browse/MSHARED-164
Project: Maven Shared Components
Issue Type: Improvement
Components: maven-doxia-tools
Affects Versions: maven-doxia-tools 1.2.1
Reporter: Benjamin Bentmann
Priority: Trivial
For {{parent.relativePath=""}} {{DefaultSiteTool.getParentProject()}}
effectively re-builds the current project instead of its parent. Instead, the
tool should directly build it from the remote repo.
--
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: (MNG-4834) Site descriptor of parent is no longer found in local repository
[
http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4834.
--
Resolution: Cannot Reproduce
Assignee: Benjamin Bentmann
I grabbed your projects and the settings and aranged those like this:
{noformat}
MNG-4834
+- main
+- parent
+- MNG-settings.xml
{noformat}
>From within {{MNG-4834}}, I ran {{mvn3 -s MNG-settings.xml clean install -f
>parent/pom.xml}} and next {{mvn -s MNG-settings.xml clean site -f
>main/pom.xml}} which yields
{noformat}
[INFO] --- maven-site-plugin:2.1.1:site (default-site) @ mng-main-4834 ---
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
{noformat}
i.e. I don't see a download attempt from any remote repo here.
Feel free to reopen with more precise steps to reproduce and actual logs that
show what you observe.
> Site descriptor of parent is no longer found in local repository
>
>
> Key: MNG-4834
> URL: http://jira.codehaus.org/browse/MNG-4834
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0-beta-3
> Environment: $ mvn -v
> Apache Maven 3.0-RC2 (r1000119; 2010-09-22 20:23:26+0200)
> Java version: 1.6.0_21
> Java home: /opt/sun-jdk-1.6.0.21/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.34-gentoo-r6" arch: "i386" Family: "unix"
>Reporter: Joerg Schaible
>Assignee: Benjamin Bentmann
>Priority: Minor
> Attachments: MNG-4834-remote-repo.tgz, MNG-4834.tgz, MNG-settings.xml
>
>
> The site descriptor from the parent project is no longer found in the local
> repository. The site plugin tries always to resolve the artifact from the
> remote repository using the attach-descriptor goal. This is nasty if that
> repo is not reachable and Maven will wait always until the connection times
> out before continuing. With M2 this descriptor is found in the local repo:
> "Parent project loaded from repository.". In both cases version 2.1.1 of the
> site plugin is used. There's no change in behavior for M3 if the site plugin
> is upgraded to 3.x.
--
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: (MNG-4832) Maven 3 Regression: Missing constructor of org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter
[ http://jira.codehaus.org/browse/MNG-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4832. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Fixed in [r1001090|http://svn.apache.org/viewvc?view=revision&revision=1001090]. > Maven 3 Regression: Missing constructor of > org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter > > > Key: MNG-4832 > URL: http://jira.codehaus.org/browse/MNG-4832 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Brian Jackson >Assignee: Benjamin Bentmann >Priority: Blocker > Fix For: 3.0 > > > I reported MNG-4811 and it was fixed for 3.0-RC2 but introduced a new error. > The source for > com.espn.maven.plugins.espnservice.IncludeProjectDependenciesComponentConfigurator > is attached to MNG-4811. The exception I'm seeing is below: > Caused by: java.lang.NoSuchMethodError: > org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V > at > com.espn.maven.plugins.espnservice.IncludeProjectDependenciesComponentConfigurator.configureComponent(IncludeProjectDependenciesComponentConfigurator.java:43) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent(AbstractComponentConfigurator.java:90) > at > org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:505) > ... 22 more -- 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-4798) NullPointerException at NearestVersionConflictResolver.selectVersion()
[
http://jira.codehaus.org/browse/MNG-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236367#action_236367
]
Benjamin Bentmann commented on MNG-4798:
Stuart McCulloch debugged this and tracked it down to
[HARMONY-6419|https://issues.apache.org/jira/browse/HARMONY-6419] which affects
the {{ConflictMarker.mark()}} method from Aether.
> NullPointerException at NearestVersionConflictResolver.selectVersion()
> --
>
> Key: MNG-4798
> URL: http://jira.codehaus.org/browse/MNG-4798
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0-beta-3
> Environment: Maven 3 beta-3, Linux, Java 1.6.0_21
>Reporter: Jochen Stiepel
>Assignee: Benjamin Bentmann
>
> this error only occurs with Maven 3 beta-3 but not Maven 3 beta-2.
> Maby it is related to this error, but has a different stacktrace: MNG-4779
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:141)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:99)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:600)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: java.lang.NullPointerException
> at
> org.sonatype.aether.util.graph.transformer.NearestVersionConflictResolver.selectVersion(NearestVersionConflictResolver.java:218)
> at
> org.sonatype.aether.util.graph.transformer.NearestVersionConflictResolver.transformGraph(NearestVersionConflictResolver.java:81)
> at
> org.sonatype.aether.util.graph.transformer.ChainedDependencyGraphTransformer.transformGraph(ChainedDependencyGraphTransformer.java:76)
> at
> org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:246)
> at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:265)
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:202)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:141)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveDependencies(LifecycleDependencyResolver.java:118)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveDependencies(LifecycleDependencyResolver.java:82)
> at
> org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:130)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:83)
> ... 16 more
--
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-4832) Maven 3 Regression: Missing constructor of org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter
[
http://jira.codehaus.org/browse/MNG-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236348#action_236348
]
Benjamin Bentmann commented on MNG-4832:
Another side note about your converter or any other custom converter you write:
You very likely don't need the following line for your mojo:
{code:java}
converterLookup.registerConverter(new ClassRealmConverter(containerRealm));
{code}
In the basic converter, it exists only for backward-compat and I'm not aware of
any valid use case that requires it.
> Maven 3 Regression: Missing constructor of
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter
>
>
> Key: MNG-4832
> URL: http://jira.codehaus.org/browse/MNG-4832
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Brian Jackson
>Priority: Blocker
>
> I reported MNG-4811 and it was fixed for 3.0-RC2 but introduced a new error.
> The source for
> com.espn.maven.plugins.espnservice.IncludeProjectDependenciesComponentConfigurator
> is attached to MNG-4811. The exception I'm seeing is below:
> Caused by: java.lang.NoSuchMethodError:
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V
> at
> com.espn.maven.plugins.espnservice.IncludeProjectDependenciesComponentConfigurator.configureComponent(IncludeProjectDependenciesComponentConfigurator.java:43)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent(AbstractComponentConfigurator.java:90)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:505)
> ... 22 more
--
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: (MINSTALL-78) install:install should remove leftovers from local repository
[
http://jira.codehaus.org/browse/MINSTALL-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINSTALL-78.
-
Resolution: Won't Fix
Assignee: Benjamin Bentmann
The assumption that artifacts produced by former installs/deploys but not the
most recent one aren't needed is in general not true (e.g. platform-specific
builds). CI in combination with tasks to purge the local repo and to purge old
snapshots via a repository manager can be used to detect projects with wrong
dependencies.
> install:install should remove leftovers from local repository
> -
>
> Key: MINSTALL-78
> URL: http://jira.codehaus.org/browse/MINSTALL-78
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install
>Affects Versions: 2.3.1
>Reporter: Petr Kozelka
>Assignee: Benjamin Bentmann
> Attachments: pom.xml
>
>
> It sometimes happens that we need to change the set of output artifacts. When
> this happens, the install mojo does not bother to remove older artifacts that
> are no longer produced by this module.
> The bad effect is, that other modules depending on the obsolete artifacts can
> still use it - and later there comes a surprise.
> Much better behavior in this situation would be, to remove the obsolete files
> from the local repository's directory dedicated for given module.
> h4. reproducing the problem
> # download the sample pom to an empty directory
> # execute {{mvn clean install -Dc=obsolete-demo}} - this represents the
> "older version" of a module
> # execute {{mvn clean install}} - this represents the "newer version" of a
> module, after changing the classifier
> # now, look in the local repo using {{ls -1
> $HOME/.m2/repository/demo/sample-zip-module/1-SNAPSHOT}} - you will see this:
> {quote}
> maven-metadata-local.xml
> sample-zip-module-1-SNAPSHOT-demo.zip
> {color:red}sample-zip-module-1-SNAPSHOT-obsolete-demo.zip{color}
> sample-zip-module-1-SNAPSHOT.pom
> {quote}
> h4. possible solutions
> I see two approaches
> # *drop the installdir first* - straightforward
> # *list installdir, install, drop leftovers* - slightly more complicated but
> maximizes the time of installed module existence (if that matters)
--
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: (MSITE-507) Site generation fails for small project
[ http://jira.codehaus.org/browse/MSITE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236287#action_236287 ] Benjamin Bentmann commented on MSITE-507: - A workaround for now seems to be to add cedarsoft-skin as a plugin dependency for the maven-site-plugin. Apparently the Site Plugin's class path leaks completely into the reports, which probably should also be fixed sometime. > Site generation fails for small project > --- > > Key: MSITE-507 > URL: http://jira.codehaus.org/browse/MSITE-507 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-2 >Reporter: Johannes Schneider >Priority: Critical > Attachments: proj.zip > > > I get that exception for my project and really don't know what is going on. > I am sure this is a fault on my side, but I think there should be a better > error message: > [INFO] Generating "JavaNCSS Report" report--- javancss-maven-plugin:2.0 > [INFO] Generating "Source Xref" report--- maven-jxr-plugin:2.1 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 9.623s > [INFO] Finished at: Thu Sep 23 17:05:11 CEST 2010 > [INFO] Final Memory: 31M/233M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-site) on > project my-artifact-id: Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site > (default-site) on project my-artifact-id: Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:211) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:116) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) > ... 19 more > Caused by: java.lang.NullPointerException > at org.codehaus.plexus.util.FileUtils.copyURLToFile(FileUtils.java:820) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.copyRequiredResources(AbstractJxrReport.java:330) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(AbstractJxrReport.java:265) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJxrReport.java:409) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:170) > at > org.apache
[jira] Moved: (MSITE-507) Site generation fails for small project
[ http://jira.codehaus.org/browse/MSITE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4835 to MSITE-507: -- Complexity: (was: Intermediate) Affects Version/s: (was: 3.0-beta-3) 3.0-beta-2 Key: MSITE-507 (was: MNG-4835) Project: Maven 2.x Site Plugin (was: Maven 2 & 3) > Site generation fails for small project > --- > > Key: MSITE-507 > URL: http://jira.codehaus.org/browse/MSITE-507 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-2 >Reporter: Johannes Schneider >Priority: Critical > Attachments: proj.zip > > > I get that exception for my project and really don't know what is going on. > I am sure this is a fault on my side, but I think there should be a better > error message: > [INFO] Generating "JavaNCSS Report" report--- javancss-maven-plugin:2.0 > [INFO] Generating "Source Xref" report--- maven-jxr-plugin:2.1 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 9.623s > [INFO] Finished at: Thu Sep 23 17:05:11 CEST 2010 > [INFO] Final Memory: 31M/233M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-site) on > project my-artifact-id: Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site > (default-site) on project my-artifact-id: Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:211) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:116) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) > ... 19 more > Caused by: java.lang.NullPointerException > at org.codehaus.plexus.util.FileUtils.copyURLToFile(FileUtils.java:820) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.copyRequiredResources(AbstractJxrReport.java:330) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(AbstractJxrReport.java:265) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJxrReport.java:409) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:170) > at > org.apache.maven.doxia.siterend
[jira] Commented: (MNG-4835) Site generation fails for small project
[
http://jira.codehaus.org/browse/MNG-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236286#action_236286
]
Benjamin Bentmann commented on MNG-4835:
The relevant pieces from the effective POM:
{code:xml}
maven-jxr-plugin
2.2
com.cedarsoft.maven
cedarsoft-skin
1.1.8
true
utf-8
utf-8
xref/cedarsoft.css
maven-jxr-plugin
2.1
true
utf-8
utf-8
xref/cedarsoft.css
{code}
i.e. the maven-jxr-plugin is expected to load a "xref/cedarsoft.css" from its
classpath and the required library cedarsoft-skin is only configured for the
build section. This is something the new Site Plugin needs to address when it
creates the class realm for the report plugin.
> Site generation fails for small project
> ---
>
> Key: MNG-4835
> URL: http://jira.codehaus.org/browse/MNG-4835
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0-beta-2
>Reporter: Johannes Schneider
>Priority: Critical
> Attachments: proj.zip
>
>
> I get that exception for my project and really don't know what is going on.
> I am sure this is a fault on my side, but I think there should be a better
> error message:
> [INFO] Generating "JavaNCSS Report" report--- javancss-maven-plugin:2.0
> [INFO] Generating "Source Xref" report--- maven-jxr-plugin:2.1
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.623s
> [INFO] Finished at: Thu Sep 23 17:05:11 CEST 2010
> [INFO] Final Memory: 31M/233M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-site) on
> project my-artifact-id: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site
> (default-site) on project my-artifact-id: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:211)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:116)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
> ... 19 more
> Caused by: java.lang.NullPointerException
> at org.codehaus.plexus.util.FileUtils.copyURLToF
[jira] Closed: (MNG-4836) Incorrect recursive expression cycle errors (update plexus-interpolation)
[
http://jira.codehaus.org/browse/MNG-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4836.
--
Resolution: Fixed
Fix Version/s: 3.0
Assignee: Benjamin Bentmann
Fixed in [r1000611|http://svn.apache.org/viewvc?view=revision&revision=1000611].
> Incorrect recursive expression cycle errors (update plexus-interpolation)
> -
>
> Key: MNG-4836
> URL: http://jira.codehaus.org/browse/MNG-4836
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-beta-3
> Environment: JDK 6u21, Ubuntu
>Reporter: Jesse Glick
>Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> Actual:
> {noformat}
> $ mvn -f
> .../mojo-archetypes/ear-javaee6/src/main/resources/archetype-resources/pom.xml
> versions:help
> ...
> [ERROR] Resolving expression: '${version}': Detected the following
> recursive expression cycle: [version] -> [Help 2]
> [ERROR] Resolving expression: '${artifactId}': Detected the following
> recursive expression cycle: [artifactId, version] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId, artifactId, version] -> [Help 2]
> ...
> {noformat}
> Expected:
> {noformat}
> ...
> [ERROR] Resolving expression: '${version}': Detected the following
> recursive expression cycle: [version] -> [Help 2]
> [ERROR] Resolving expression: '${artifactId}': Detected the following
> recursive expression cycle: [artifactId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> ...
> {noformat}
> PLXCOMP-159 is responsible (confirmed by substituting patched JAR). I am not
> positive but I believe this is also the cause of a critical (if sporadic)
> error in the NetBeans embedder, starting to appear I think when RC1 was
> integrated (maybe RC2): https://netbeans.org/bugzilla/show_bug.cgi?id=190530
> PLXCOMP-158 is also related.
> Please consider producing a new release of plexus-interpolation containing
> these two patches and using it in Maven 3.0 RC3.
--
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: (MNG-4394) Configure same proxy for multiple protocols
[ http://jira.codehaus.org/browse/MNG-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4394. -- Resolution: Duplicate Fix Version/s: (was: Issues to be reviewed for 3.x) Assignee: Benjamin Bentmann > Configure same proxy for multiple protocols > --- > > Key: MNG-4394 > URL: http://jira.codehaus.org/browse/MNG-4394 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Settings >Affects Versions: 2.2.1 >Reporter: Hugo Palma >Assignee: Benjamin Bentmann > Attachments: MNG-4394.patch, MNG-4394.patch > > > It seems that it's not possible to configure a proxy for more than one > protocol. > I would think that it's a very common requirement to use a proxy for both > http and https. > It would be great if this was possible. -- 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: (MNG-4837) Interpolation error due to cyclic expression for one of the POM coordinates gets needlessly repeated
[
http://jira.codehaus.org/browse/MNG-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4837.
--
Resolution: Fixed
Fix Version/s: 3.0
Assignee: Benjamin Bentmann
Fixed in [r1000601|http://svn.apache.org/viewvc?view=revision&revision=1000601].
> Interpolation error due to cyclic expression for one of the POM coordinates
> gets needlessly repeated
>
>
> Key: MNG-4837
> URL: http://jira.codehaus.org/browse/MNG-4837
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-beta-3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0
>
>
> This simple POM
> {code:xml}
>
> 4.0.0
> ${groupId}
> test
> 0.1
> jar
>
>
> maven-core-it
> file:///${basedir}/repo
>
>
>
> {code}
> causes the following model errors:
> {noformat}
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] Resolving expression: '${groupId}': Detected the following
> recursive expression cycle: [groupId] -> [Help 2]
> [ERROR] 'groupId' with value '${groupId}' does not match a valid id
> pattern. @ line 25, column 12
> {noformat}
> Note the excessive repetition of the groupId related cycle although this
> expression actually appears only once in the POM.
--
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-4837) Interpolation error due to cyclic expression for one of the POM coordinates gets needlessly repeated
Interpolation error due to cyclic expression for one of the POM coordinates
gets needlessly repeated
Key: MNG-4837
URL: http://jira.codehaus.org/browse/MNG-4837
Project: Maven 2 & 3
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 3.0-beta-3
Reporter: Benjamin Bentmann
Priority: Minor
This simple POM
{code:xml}
4.0.0
${groupId}
test
0.1
jar
maven-core-it
file:///${basedir}/repo
{code}
causes the following model errors:
{noformat}
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] Resolving expression: '${groupId}': Detected the following
recursive expression cycle: [groupId] -> [Help 2]
[ERROR] 'groupId' with value '${groupId}' does not match a valid id
pattern. @ line 25, column 12
{noformat}
Note the excessive repetition of the groupId related cycle although this
expression actually appears only once in the POM.
--
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] Moved: (MSITE-506) Maven3 conflict with plexus-archiver
[ http://jira.codehaus.org/browse/MSITE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4833 to MSITE-506: -- Complexity: (was: Intermediate) Affects Version/s: (was: 3.0-beta-3) 3.0-beta-2 Key: MSITE-506 (was: MNG-4833) Project: Maven 2.x Site Plugin (was: Maven 2 & 3) > Maven3 conflict with plexus-archiver > > > Key: MSITE-506 > URL: http://jira.codehaus.org/browse/MSITE-506 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-2 > Environment: Apache Maven 3.0-SNAPSHOT (r999839; 2010-09-22 > 11:43:26+0200) > Java version: 1.7.0-ea > Java home: /home/pether/tools/jdk1.7.0/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-25-generic" arch: "amd64" Family: "unix" >Reporter: Pether Sorling > Attachments: testmaven3.zip > > > Verson 2.7 and 2.8-SNAPSHOT have some issues with maven3. Works with 2.6.1, > different version of plexus archiver conflicts with maven. > failed to get Reports: > org.codehaus.plexus.archiver.zip.ZipUnArchiver$__plexus5 cannot be cast to > org.codehaus.plexus.archiver.UnArchiver -- 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] Moved: (MNG-4833) Maven3 conflict with plexus-archiver
[ http://jira.codehaus.org/browse/MNG-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MJAVADOC-293 to MNG-4833: - Complexity: Intermediate Affects Version/s: (was: 2.8) (was: 2.7) 3.0-beta-3 Key: MNG-4833 (was: MJAVADOC-293) Project: Maven 2 & 3 (was: Maven 2.x Javadoc Plugin) > Maven3 conflict with plexus-archiver > > > Key: MNG-4833 > URL: http://jira.codehaus.org/browse/MNG-4833 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: Apache Maven 3.0-SNAPSHOT (r999839; 2010-09-22 > 11:43:26+0200) > Java version: 1.7.0-ea > Java home: /home/pether/tools/jdk1.7.0/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-25-generic" arch: "amd64" Family: "unix" >Reporter: Pether Sorling > Attachments: testmaven3.zip > > > Verson 2.7 and 2.8-SNAPSHOT have some issues with maven3. Works with 2.6.1, > different version of plexus archiver conflicts with maven. > failed to get Reports: > org.codehaus.plexus.archiver.zip.ZipUnArchiver$__plexus5 cannot be cast to > org.codehaus.plexus.archiver.UnArchiver -- 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: (MNG-4815) (3.0-RC1) Maven Java API does not give nice error messages when improperly configured
[
http://jira.codehaus.org/browse/MNG-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4815.
--
Resolution: Fixed
Fix Version/s: 3.0
Assignee: Benjamin Bentmann
Improved in
[r191|http://svn.apache.org/viewvc?view=revision&revision=191].
> (3.0-RC1) Maven Java API does not give nice error messages when improperly
> configured
> -
>
> Key: MNG-4815
> URL: http://jira.codehaus.org/browse/MNG-4815
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Errors
>Affects Versions: 3.0-beta-3
> Environment: Maven 3.0-RC1
>Reporter: Lincoln Baxter, III
>Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> I get nullpointers all over the place if I do not set up the configuration
> options exactly as maven requires them. This is fine, but not a very friendly
> experience for developers trying to figure out how to use the API.
> This is a correct/simple bootstrap (see below,) but if any or many of the
> methods are not called "just so" a nullpointer will result. Better error
> messages should be provided, such as:
> "No LocalRepositoryManager was configured in the RespositorySession - this
> may not be null."
> Etc...
> {noformat}
> /*
> * JBoss, Home of Professional Open Source
> * Copyright 2010, Red Hat, Inc., and individual contributors
> * by the @authors tag. See the copyright.txt in the distribution for a
> * full listing of individual contributors.
> *
> * This is free software; you can redistribute it and/or modify it
> * under the terms of the GNU Lesser General Public License as
> * published by the Free Software Foundation; either version 2.1 of
> * the License, or (at your option) any later version.
> *
> * This software is distributed in the hope that it will be useful,
> * but WITHOUT ANY WARRANTY; without even the implied warranty of
> * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> * Lesser General Public License for more details.
> *
> * You should have received a copy of the GNU Lesser General Public
> * License along with this software; if not, write to the Free
> * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
> * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
> */
> package org.jboss.arqmvn;
> import java.io.File;
> import java.util.ArrayList;
> import org.apache.maven.artifact.repository.ArtifactRepository;
> import org.apache.maven.artifact.repository.ArtifactRepositoryPolicy;
> import org.apache.maven.artifact.repository.MavenArtifactRepository;
> import org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout;
> import org.apache.maven.project.DefaultProjectBuildingRequest;
> import org.apache.maven.project.ProjectBuilder;
> import org.apache.maven.project.ProjectBuildingException;
> import org.apache.maven.project.ProjectBuildingRequest;
> import org.apache.maven.project.ProjectBuildingResult;
> import org.codehaus.plexus.DefaultPlexusContainer;
> import org.codehaus.plexus.logging.console.ConsoleLoggerManager;
> import org.sonatype.aether.impl.internal.SimpleLocalRepositoryManager;
> import org.sonatype.aether.util.DefaultRepositorySystemSession;
> /**
> * @author mailto:lincolnbax...@gmail.com";>Lincoln Baxter, III
> */
> public class MavenFacet
> {
>private final ProjectBuildingRequest request = new
> DefaultProjectBuildingRequest();
>private DefaultPlexusContainer container = null;
>private ProjectBuilder builder = null;
>private void bootstrapMaven()
>{
> if (!initialized())
> {
> try
> {
> container = new DefaultPlexusContainer();
> ConsoleLoggerManager loggerManager = new ConsoleLoggerManager();
> loggerManager.setThreshold("ERROR");
> container.setLoggerManager(loggerManager);
> builder = container.lookup(ProjectBuilder.class);
> // TODO this needs to be configurable via the project/.sidekick
> file.
> String localRepository = getUserHomeDir().getAbsolutePath() +
> "/.m2/repository";
> request.setLocalRepository(new MavenArtifactRepository(
> "local", new
> File(localRepository).toURI().toURL().toString(),
> container.lookup(ArtifactRepositoryLayout.class),
> new ArtifactRepositoryPolicy(true,
> ArtifactRepositoryPolicy.UPDATE_POLICY_NEVER,
> ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN),
> new ArtifactRepositoryPolicy(true,
> ArtifactRepositoryPolicy.UPDATE_POLICY_NEVER,
>
> ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN)));
> request.setRemoteRepositories(new
> ArrayLis
[jira] Commented: (MJAVADOC-293) Maven3 conflict with plexus-archiver
[ http://jira.codehaus.org/browse/MJAVADOC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236053#action_236053 ] Benjamin Bentmann commented on MJAVADOC-293: This looks more like an issue with the Guice-based Plexus shim, can you share some more details like the full build log or an example project to reproduce it? > Maven3 conflict with plexus-archiver > > > Key: MJAVADOC-293 > URL: http://jira.codehaus.org/browse/MJAVADOC-293 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.7, 2.8 > Environment: Apache Maven 3.0-SNAPSHOT (r999839; 2010-09-22 > 11:43:26+0200) > Java version: 1.7.0-ea > Java home: /home/pether/tools/jdk1.7.0/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-25-generic" arch: "amd64" Family: "unix" >Reporter: Pether Sorling > > Verson 2.7 and 2.8-SNAPSHOT have some issues with maven3. Works with 2.6.1, > different version of plexus archiver conflicts with maven. > failed to get Reports: > org.codehaus.plexus.archiver.zip.ZipUnArchiver$__plexus5 cannot be cast to > org.codehaus.plexus.archiver.UnArchiver -- 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: (MNG-4829) [regression] Checksum failures aren't logged
[ http://jira.codehaus.org/browse/MNG-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4829. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Fixed in [r998895|http://svn.apache.org/viewvc?view=revision&revision=998895]. > [regression] Checksum failures aren't logged > > > Key: MNG-4829 > URL: http://jira.codehaus.org/browse/MNG-4829 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0-beta-3 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann > Fix For: 3.0 > > > For checksumPolicy=warn and broken artifacts, no warning is emitted during > the build. -- 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-4829) [regression] Checksum failures aren't logged
[regression] Checksum failures aren't logged Key: MNG-4829 URL: http://jira.codehaus.org/browse/MNG-4829 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0-beta-3 Reporter: Benjamin Bentmann For checksumPolicy=warn and broken artifacts, no warning is emitted during the build. -- 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: (MNG-4824) multiple failures need additional whitespace
[
http://jira.codehaus.org/browse/MNG-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4824.
--
Resolution: Fixed
Fix Version/s: 3.0
Assignee: Benjamin Bentmann
Improved in
[r998878|http://svn.apache.org/viewvc?view=revision&revision=998878].
> multiple failures need additional whitespace
>
>
> Key: MNG-4824
> URL: http://jira.codehaus.org/browse/MNG-4824
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Logging
>Affects Versions: 3.0-beta-3
>Reporter: Brett Porter
>Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> I got 3 resolution errors. On a smaller console width, they were very hard to
> read:
> {code}
> [ERROR] The build could not read 3 projects -> [Help 1]
> [ERROR] The project
> org.codehaus.redback:redback-authorization-rbac:1.3-SNAPSHOT
> (/Users/brett/scm/redback/redback-rbac/redback-authorization-rbac/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM
> org.codehaus.redback:redback-authorization-providers:1.3-SNAPSHOT for
> org.codehaus.redback:redback-authorization-rbac:1.3-SNAPSHOT: Failed to
> resolve POM for
> org.codehaus.redback:redback-authorization-providers:1.3-SNAPSHOT due to The
> following artifacts could not be resolved:
> org.codehaus.redback:redback-authorization-providers:pom:1.3-SNAPSHOT: Could
> not find artifact
> org.codehaus.redback:redback-authorization-providers:pom:1.3-SNAPSHOT ->
> [Help 2]
> [ERROR] The project
> org.codehaus.redback:redback-authentication-keys:1.3-SNAPSHOT
> (/Users/brett/scm/redback/redback-keys/redback-authentication-keys/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM
> org.codehaus.redback:redback-authentication-providers:1.3-SNAPSHOT for
> org.codehaus.redback:redback-authentication-keys:1.3-SNAPSHOT: Failed to
> resolve POM for
> org.codehaus.redback:redback-authentication-providers:1.3-SNAPSHOT due to The
> following artifacts could not be resolved:
> org.codehaus.redback:redback-authentication-providers:pom:1.3-SNAPSHOT: Could
> not find artifact
> org.codehaus.redback:redback-authentication-providers:pom:1.3-SNAPSHOT ->
> [Help 2]
> [ERROR] The project
> org.codehaus.redback:redback-authentication-users:1.3-SNAPSHOT
> (/Users/brett/scm/redback/redback-users/redback-authentication-users/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM
> org.codehaus.redback:redback-authentication-providers:1.3-SNAPSHOT for
> org.codehaus.redback:redback-authentication-users:1.3-SNAPSHOT: Failed to
> resolve POM for
> org.codehaus.redback:redback-authentication-providers:1.3-SNAPSHOT due to The
> following artifacts could not be resolved:
> org.codehaus.redback:redback-authentication-providers:pom:1.3-SNAPSHOT: Could
> not find artifact
> org.codehaus.redback:redback-authentication-providers:pom:1.3-SNAPSHOT ->
> [Help 2]
> {code}
> I suggest adding a number to the front of each, and a new line between them.
--
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: (MNG-4818) NPE in legacy.DefaultWagonManager.getArtifact
[ http://jira.codehaus.org/browse/MNG-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4818. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Fixed in [r998861|http://svn.apache.org/viewvc?view=revision&revision=998861]. Actually caused by a bad component which asked for injection into clashing private fields. > NPE in legacy.DefaultWagonManager.getArtifact > - > > Key: MNG-4818 > URL: http://jira.codehaus.org/browse/MNG-4818 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0 > Environment: At revision 998131; 1.6.0_21 (32-bit); win7ent-x64 >Reporter: Matthew Daniel >Assignee: Benjamin Bentmann > Fix For: 3.0 > > Attachments: bug.log > > > 1. mvn archetype:create (with your favorite -DgroupId etc) > 2. add some non-local dependency to the pom (I used commons-jexl:2.0.1) > 3. mvn idea:idea > 4. kaboom > The problem is that the Logger is declared as @Requirement but it is > evidently not being provided (any path leading to a logging statement yields > the NPE) > I regret that I don't know enough plexus-voodoo to even create a TestCase for > this. -- 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: (MNG-4825) Relative path errors could be more explicit
[ http://jira.codehaus.org/browse/MNG-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4825. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Improved in [r998850|http://svn.apache.org/viewvc?view=revision&revision=998850]. > Relative path errors could be more explicit > --- > > Key: MNG-4825 > URL: http://jira.codehaus.org/browse/MNG-4825 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Logging >Affects Versions: 3.0-beta-3 >Reporter: Brett Porter >Assignee: Benjamin Bentmann > Fix For: 3.0 > > > See the exceptions in MNG-4824. > This was caused by a default relative path of '../pom.xml' which was not > correct. Maven 2.x ignored it and went to the repository, but as specified in > the compatibility notes Maven 3 fails. The exception should state that it was > a non-resolvable parent because it is not in the repository and not found at > the relative path of '../pom.xml' -- 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-4805) Update default plugin versions used for built-in lifecycle mappings
[ http://jira.codehaus.org/browse/MNG-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234878#action_234878 ] Benjamin Bentmann edited comment on MNG-4805 at 9/19/10 7:24 AM: - Done in [r995733|http://svn.apache.org/viewvc?view=revision&revision=995733] and [r998642|http://svn.apache.org/viewvc?view=revision&revision=998642]. was (Author: bentmann): Done in [r995733|http://svn.apache.org/viewvc?view=revision&revision=995733]. > Update default plugin versions used for built-in lifecycle mappings > --- > > Key: MNG-4805 > URL: http://jira.codehaus.org/browse/MNG-4805 > Project: Maven 2 & 3 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-beta-3 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Trivial > Fix For: 3.0 > > > Some of the common plugins have had new releases with bugfixes, in particular > regarding parallel build support, we should pick those as defaults. -- 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: (MNG-4822) Invalid wiki page reference for dependency resolutions problems
[
http://jira.codehaus.org/browse/MNG-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4822.
--
Resolution: Fixed
Assignee: Benjamin Bentmann
> Invalid wiki page reference for dependency resolutions problems
> ---
>
> Key: MNG-4822
> URL: http://jira.codehaus.org/browse/MNG-4822
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Douglas Jose
>Assignee: Benjamin Bentmann
>
> When Maven cannot resolve a dependency, an invalid link to the project's wiki
> is displayed.
> {noformat}
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> {noformat}
--
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: (MNG-4821) Wrong spring-context version resolved when depending on artifact with dependency management and jersey-spring dependency
[
http://jira.codehaus.org/browse/MNG-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4821.
--
Resolution: Duplicate
Assignee: Benjamin Bentmann
Thanks for the example projects. When building A, B's dependencyManagement is
ignored (MNG-3038) such that the dependeny graph for A contains the original
{{spring-context:[2.5.2,3)}} dependency as given by {{jersey-spring:1.2}}.
Futhermore, a version range overrules any soft version recommendations like the
{{3.0.1.RELEASE}} given in A's POM. That's why A ends up with
{{spring-context:jar:2.5.x}}.
For now, you need to use dependency management in A to enforce the version of
{{spring-context}} you want.
bq. When A is built, maven 2 uses org.springframework:spring-context:jar:2.5.6,
and maven 3 uses version 2.5.6.SEC02.
This minor difference is the effect of improved version comparision in Maven 3
which properly recognizes {{2.5.6}} < {{2.5.6.SEC01}} < {{2.5.6.SEC02}}.
> Wrong spring-context version resolved when depending on artifact with
> dependency management and jersey-spring dependency
>
>
> Key: MNG-4821
> URL: http://jira.codehaus.org/browse/MNG-4821
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.2.1
> Environment: Ubuntu 10.04 64-bit, jdk6
> Windows 7 64-bit, Cygwin, jdk6
> Windows XP SP3 32-bit, Cygwin, jdk5
>Reporter: Ryan Stewart
>Assignee: Benjamin Bentmann
> Attachments: dependency-versions.zip
>
>
> Given two artifacts, A and B:
> - A depends on B and on org.springframework:spring-context:3.0.1.RELEASE
> - B depends on com.sun.jersey.contribs:jersey-spring:1.2 and has a dependency
> management entry that sets the version for org.springframework:spring-context
> to 3.0.2.RELEASE
> - com.sun.jersey.contribs:jersey-spring:1.2 depends on
> org.springframework:spring-context:[2.5.2,3)
> When B is built, maven uses
> org.springframework:spring-context:jar:3.0.2.RELEASE, as expected.
> When A is built, maven 2 uses org.springframework:spring-context:jar:2.5.6,
> and maven 3 uses version 2.5.6.SEC02.
> I'm attaching a sample project that demonstrates the bug. There are two poms:
> dependent and dependee. These correspond to A and B above, respectively. The
> top-level pom just includes the other two for ease of building. In the
> real-life situation where I found the problem, the two artifacts are from
> separate projects. There is no unit test, since I don't even know how I'd
> write a test for this, but there is a bash script called test.sh that checks
> for the problem.
--
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: (MNG-4491) Maven3 reports warnings about POM problems in very spurious way
[
http://jira.codehaus.org/browse/MNG-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4491.
--
Resolution: Won't Fix
Assignee: Benjamin Bentmann
Invalid = existent but unusuable, for any more details the debug log can be
consulted.
> Maven3 reports warnings about POM problems in very spurious way
> ---
>
> Key: MNG-4491
> URL: http://jira.codehaus.org/browse/MNG-4491
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Errors
>Affects Versions: 3.0-alpha-5
>Reporter: Tamás Cservenák
>Assignee: Benjamin Bentmann
>
> In relation to issue MNG-4490, Maven3 reported the following on CLI:
> {noformat}
> [WARNING] Invalid artifact metadata for
> org.sonatype.nexus:nexus-proxy:jar:1.4.1-SNAPSHOT, transitive dependencies
> (if any) will not be available, enable debug logging for more details
> {noformat}
> This is due to the issue above (the branch i worked on completely revamped
> the dependencies in aggregator poms, hence the module pom became "invalid",
> since it contained dependencies that would be "filled in" from dependency
> management section, but they were not, hence by Maven3 they were considered
> "invalid").
> What I was thinking, that maybe we should distinguish between "corrupt" POMs
> in way like:
> * syntactical broken, which is like unparseable POM (usually corrupted during
> transport or proxy issues)
> * semantically broken -- this is what Maven3 tried to tell me -- a POM that
> was not "correct" in validation sense (in this case, depepndency had no
> "version" declared)
--
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: (MNG-4490) Inconsistent handling of POMs
[
http://jira.codehaus.org/browse/MNG-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4490.
--
Resolution: Fixed
Fix Version/s: 3.0-beta-3
Assignee: Benjamin Bentmann
Fixed by [r988749|http://svn.apache.org/viewvc?view=revision&revision=988749],
POMs are consequently treated as artifacts.
> Inconsistent handling of POMs
> -
>
> Key: MNG-4490
> URL: http://jira.codehaus.org/browse/MNG-4490
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-5
>Reporter: Tamás Cservenák
>Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-3
>
>
> As we learned from discussion happened in issue MNG-4368, Maven3 -- depending
> on packaging ("pom" vs anything else) -- handles the POM installation in
> different ways.
> When packaging is "pom", the POM is _handled as artifact_, and MNG-4368 (and
> any other future "optimization") interferes with it's installation. When
> packaging is not "pom", the POM is _handled as repository metadata in Maven3
> internals.
> IMHO, the latter should be _always_ the case, regardless of the packaging
> type.
--
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-4819) Inheritance Error in Object List Configuration for Custom Plugin
[ http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235666#action_235666 ] Benjamin Bentmann commented on MNG-4819: Yes, that attribute can in general be applied on any element within a plugin configuration block. > Inheritance Error in Object List Configuration for Custom Plugin > > > Key: MNG-4819 > URL: http://jira.codehaus.org/browse/MNG-4819 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.2.1 > Environment: Windows XP SP3, running under Cygwin bash shell >Reporter: Jonathan Pearson >Assignee: Benjamin Bentmann > Attachments: bugdemo.tgz, build.log > > > When a parent defines an object list in a plugin configuration, and then a > child of that parent also defines an object list for the same plugin leaving > some values undefined (so as to use defaults), the object list is loaded into > the plugin in an unpredictable manner, sometimes using parent-defined > properties instead of defaults, and sometimes not. > The attached plugin/parent/child projects produce this incorrect output: > $ mvn inherit_bug_demo:bugdemo > ... > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] > The expected output would either be: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], > [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 > Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent > Object 3 Property 2]]'] > Or: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Property 1', prop2='Child Object 2 Property 2']]'] > See attached build log, demonstration plugin, and parent/child project for > details. > Usage: > $ cd inherit_bug_demo > $ mvn deploy > $ cd ../child > $ mvn inherit_bug_demo:bugdemo -- 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: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[
http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4819.
--
Resolution: Duplicate
Assignee: Benjamin Bentmann
Thanks for the example project!
The default behavior is merging at any depth such that the effective plugin
configuration in the child now looks like:
{code:xml}
Child Object 1 Property 1
Parent Object 1 Property 2
Child Object 2 Property 2
Parent Object 2 Property 1
{code}
i.e. the parent objects get merged to the proper locations in the child list.
To achieve the result that you mention in your last comment, the child POM
needs to be changed like this:
{code:xml}
Child Object 1 Property 1
Child Object 2 Property 2
{code}
i.e. the attribute {{combine.self="override"}} disables merging of parent
values for that node.
> Inheritance Error in Object List Configuration for Custom Plugin
>
>
> Key: MNG-4819
> URL: http://jira.codehaus.org/browse/MNG-4819
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.2.1
> Environment: Windows XP SP3, running under Cygwin bash shell
>Reporter: Jonathan Pearson
>Assignee: Benjamin Bentmann
> Attachments: bugdemo.tgz, build.log
>
>
> When a parent defines an object list in a plugin configuration, and then a
> child of that parent also defines an object list for the same plugin leaving
> some values undefined (so as to use defaults), the object list is loaded into
> the plugin in an unpredictable manner, sometimes using parent-defined
> properties instead of defaults, and sometimes not.
> The attached plugin/parent/child projects produce this incorrect output:
> $ mvn inherit_bug_demo:bugdemo
> ...
> [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject:
> prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject:
> prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]']
> The expected output would either be:
> [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject:
> prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'],
> [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2
> Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent
> Object 3 Property 2]]']
> Or:
> [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject:
> prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject:
> prop1='Property 1', prop2='Child Object 2 Property 2']]']
> See attached build log, demonstration plugin, and parent/child project for
> details.
> Usage:
> $ cd inherit_bug_demo
> $ mvn deploy
> $ cd ../child
> $ mvn inherit_bug_demo:bugdemo
--
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: (MRELEASE-568) Release plugin (in perform phase) ignore -f directive (non-default pom.xml file)
[ http://jira.codehaus.org/browse/MRELEASE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MRELEASE-568: --- Affects Version/s: 2.0 > Release plugin (in perform phase) ignore -f directive (non-default pom.xml > file) > > > Key: MRELEASE-568 > URL: http://jira.codehaus.org/browse/MRELEASE-568 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Paul Hammant > > mvn -f alternate-pom.xml release:perform > [ time passes ] > [INFO] Working directory: /scm/oss/atinject/target > [INFO] Executing goals 'deploy'... > [INFO] Executing: /bin/sh -c cd /scm/oss/atinject/target/checkout && > /Installed/apache-maven-2.2.1/bin/mvn deploy --no-plugin-updates > -DperformRelease=true -f pom.xml -- 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] Moved: (MRELEASE-597) Releasing a renamed pom file using the -f option does release to wrong pom file
[ http://jira.codehaus.org/browse/MRELEASE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4820 to MRELEASE-597: - Complexity: (was: Intermediate) Affects Version/s: (was: 3.0-beta-3) 2.0 Key: MRELEASE-597 (was: MNG-4820) Project: Maven 2.x Release Plugin (was: Maven 2 & 3) > Releasing a renamed pom file using the -f option does release to wrong pom > file > > > Key: MRELEASE-597 > URL: http://jira.codehaus.org/browse/MRELEASE-597 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Release is 3.0-RC1, Linux Ubuntu 32 >Reporter: Ulli Hafner > Attachments: bundle-pom.xml, maven.log, pom.xml > > > I have a directory containing 2 pom files that are used as our parent pom's: > de.faktorlogik.pom/ > - pom.xml > - bundle-pom.xml > When I go into this folder and release the 'pom.xml' file using 'mvn > release:prepare', and 'mvn release:perform' then everything is ok. However, > when I try to release the 'bundle-pom.xml' then the 'mvn -f bundle-pom.xml > release:prepare' process works, but the 'mvn f bundle-pom.xml > release:perform' process releases the snapshot version of 'pom.xml' rather > than the new version of the bundle-pom.xml file. Seems that the -f parameter > is ignored in the latter case. -- 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: (MRELEASE-597) Releasing a renamed pom file using the -f option does release to wrong pom file
[ http://jira.codehaus.org/browse/MRELEASE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MRELEASE-597. -- Resolution: Duplicate Assignee: Benjamin Bentmann > Releasing a renamed pom file using the -f option does release to wrong pom > file > > > Key: MRELEASE-597 > URL: http://jira.codehaus.org/browse/MRELEASE-597 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Release is 3.0-RC1, Linux Ubuntu 32 >Reporter: Ulli Hafner >Assignee: Benjamin Bentmann > Attachments: bundle-pom.xml, maven.log, pom.xml > > > I have a directory containing 2 pom files that are used as our parent pom's: > de.faktorlogik.pom/ > - pom.xml > - bundle-pom.xml > When I go into this folder and release the 'pom.xml' file using 'mvn > release:prepare', and 'mvn release:perform' then everything is ok. However, > when I try to release the 'bundle-pom.xml' then the 'mvn -f bundle-pom.xml > release:prepare' process works, but the 'mvn f bundle-pom.xml > release:perform' process releases the snapshot version of 'pom.xml' rather > than the new version of the bundle-pom.xml file. Seems that the -f parameter > is ignored in the latter case. -- 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-4813) org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1
[
http://jira.codehaus.org/browse/MNG-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235622#action_235622
]
Benjamin Bentmann commented on MNG-4813:
Because Maven 2.x employs unusual class loaders.
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven
> 3.0-RC1
> -
>
> Key: MNG-4813
> URL: http://jira.codehaus.org/browse/MNG-4813
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1, 3.0-beta-2,
> 3.0-beta-3
>Reporter: Arnaud Heritier
>Assignee: Benjamin Bentmann
>
> Module to reproduce :
> https://anonsvn.jboss.org/repos/exo-jcr/jcr/trunk/docs/reference/en
> You'll probably need this repo to build :
> http://repository.exoplatform.org/public
> The error :
> {code}
> [INFO] --- maven-jdocbook-plugin:2.1.1:generate (default-generate) @
> reference-docs-en ---
> Error at xsl:import on line 12 of
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl:
> Malformed URL classpath:/xslt/org/jboss/xhtml.xsl(base
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl):
> unknown protocol: classpath
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.898s
> [INFO] Finished at: Thu Sep 16 22:13:39 CEST 2010
> [INFO] Final Memory: 7M/125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem: unable to
> build transformer [null] : Failed to compile stylesheet. 1 error detected. ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: XSLT problem
> at
> org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:285)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
> ... 19 more
> Caused by: org.jboss.jdocbook.xslt.XSLTException: unable to build transformer
> [null] : Failed to compile stylesheet. 1 error detected.
> at
> org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:94)
> at
> org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:78)
> at
> org.jboss.jdocbook.render.impl.BasicRenderer.buildTra
[jira] Commented: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235617#action_235617
]
Benjamin Bentmann commented on MNG-4817:
Forgot to mention, your local repository contains garbage by now (HTML files)
which will continue to cause build failures unless manually removed.
> Unable to use gwt-maven-plugin 1.3-SNAPSHOT
> ---
>
> Key: MNG-4817
> URL: http://jira.codehaus.org/browse/MNG-4817
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0
> Environment: Ubuntu 10.10
>Reporter: Jacek Furmankiewicz
>Assignee: Benjamin Bentmann
>
> Tried to create a project using the gwt-maven plugin. After generating the
> archetype using the current 1.2 version I attempted to update it to
> 1.3-SNAPSHOT
> {code:xml}
>
> org.codehaus.mojo
> gwt-maven-plugin
> 1.3-SNAPSHOT
>
>
>
> compile
>
> generateAsync
> test
>
>
>
>
>
> com.rp.portal.campaign.Application/Application.html
>
>
> {code}
> Added the repo for the plugin:
> {code:xml}
>
>
> Codehaus
> Codehaus Maven Plugin Repository
>
> http://repository.codehaus.org/org/codehaus/mojo
>
> true
>
>
>
> [code}
> Got this repeatedly:
> {code}
> jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [WARNING] Failed to retrieve plugin descriptor for
> org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
> descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
> (/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
> error in opening zip file
> [WARNING] Error reading plugin group metadata: end tag name must
> match start tag name from line 7 (position: TEXT seen
> ...\n... @9:8)
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> Downloaded:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> (437 B at 1.6 KB/sec)
> [WARNING] Failed to read metadata
> /home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
> end tag name must match start tag name from line 7 (position:
> TEXT seen ...\n... @9:8)
> {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: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4817.
--
Resolution: Duplicate
Assignee: Benjamin Bentmann
Consequence of inability to follow HTTP->HTTPS redirects (MNG-4428), use
{{https://}} for the plugin repository instead to workaround that.
> Unable to use gwt-maven-plugin 1.3-SNAPSHOT
> ---
>
> Key: MNG-4817
> URL: http://jira.codehaus.org/browse/MNG-4817
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0
> Environment: Ubuntu 10.10
>Reporter: Jacek Furmankiewicz
>Assignee: Benjamin Bentmann
>
> Tried to create a project using the gwt-maven plugin. After generating the
> archetype using the current 1.2 version I attempted to update it to
> 1.3-SNAPSHOT
> {code:xml}
>
> org.codehaus.mojo
> gwt-maven-plugin
> 1.3-SNAPSHOT
>
>
>
> compile
>
> generateAsync
> test
>
>
>
>
>
> com.rp.portal.campaign.Application/Application.html
>
>
> {code}
> Added the repo for the plugin:
> {code:xml}
>
>
> Codehaus
> Codehaus Maven Plugin Repository
>
> http://repository.codehaus.org/org/codehaus/mojo
>
> true
>
>
>
> [code}
> Got this repeatedly:
> {code}
> jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [WARNING] Failed to retrieve plugin descriptor for
> org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
> descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
> (/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
> error in opening zip file
> [WARNING] Error reading plugin group metadata: end tag name must
> match start tag name from line 7 (position: TEXT seen
> ...\n... @9:8)
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> Downloaded:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> (437 B at 1.6 KB/sec)
> [WARNING] Failed to read metadata
> /home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
> end tag name must match start tag name from line 7 (position:
> TEXT seen ...\n... @9:8)
> {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: (MNG-4813) org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1
[
http://jira.codehaus.org/browse/MNG-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4813.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
Turns out to be a bug in {{org.jboss.jdocbook.xslt.resolve.ClasspathResolver}}
which passes invalid resource names into {{ClassLoader.getResource()}}:
{noformat}
public Source resolve(String href, String base) throws TransformerException {
// href would need to start with classpath:
if ( !href.startsWith( "classpath:" ) ) {
return null;
}
try {
URL url = classLoader.getResource( href.substring(10) );
return new StreamSource( url.openStream(), url.toExternalForm() );
}
catch ( Throwable t ) {
return null;
}
}
{noformat}
e.g. for "classpath:/xslt/org/jboss/xhtml-single.xsl", the class loader is
asked for "/xslt/org/jboss/xhtml-single.xsl" (note the leading slash) instead
of "xslt/org/jboss/xhtml-single.xsl".
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven
> 3.0-RC1
> -
>
> Key: MNG-4813
> URL: http://jira.codehaus.org/browse/MNG-4813
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1, 3.0-beta-2,
> 3.0-beta-3
>Reporter: Arnaud Heritier
>Assignee: Benjamin Bentmann
>
> Module to reproduce :
> https://anonsvn.jboss.org/repos/exo-jcr/jcr/trunk/docs/reference/en
> You'll probably need this repo to build :
> http://repository.exoplatform.org/public
> The error :
> {code}
> [INFO] --- maven-jdocbook-plugin:2.1.1:generate (default-generate) @
> reference-docs-en ---
> Error at xsl:import on line 12 of
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl:
> Malformed URL classpath:/xslt/org/jboss/xhtml.xsl(base
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl):
> unknown protocol: classpath
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.898s
> [INFO] Finished at: Thu Sep 16 22:13:39 CEST 2010
> [INFO] Final Memory: 7M/125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem: unable to
> build transformer [null] : Failed to compile stylesheet. 1 error detected. ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: XSLT problem
> at
> org.jboss.maven.pl
[jira] Updated: (MNG-4815) (3.0-RC1) Maven Java API does not give nice error messages when improperly configured
[
http://jira.codehaus.org/browse/MNG-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4815:
---
Description:
I get nullpointers all over the place if I do not set up the configuration
options exactly as maven requires them. This is fine, but not a very friendly
experience for developers trying to figure out how to use the API.
This is a correct/simple bootstrap (see below,) but if any or many of the
methods are not called "just so" a nullpointer will result. Better error
messages should be provided, such as:
"No LocalRepositoryManager was configured in the RespositorySession - this may
not be null."
Etc...
{noformat}
/*
* JBoss, Home of Professional Open Source
* Copyright 2010, Red Hat, Inc., and individual contributors
* by the @authors tag. See the copyright.txt in the distribution for a
* full listing of individual contributors.
*
* This is free software; you can redistribute it and/or modify it
* under the terms of the GNU Lesser General Public License as
* published by the Free Software Foundation; either version 2.1 of
* the License, or (at your option) any later version.
*
* This software is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this software; if not, write to the Free
* Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
* 02110-1301 USA, or see the FSF site: http://www.fsf.org.
*/
package org.jboss.arqmvn;
import java.io.File;
import java.util.ArrayList;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.artifact.repository.ArtifactRepositoryPolicy;
import org.apache.maven.artifact.repository.MavenArtifactRepository;
import org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout;
import org.apache.maven.project.DefaultProjectBuildingRequest;
import org.apache.maven.project.ProjectBuilder;
import org.apache.maven.project.ProjectBuildingException;
import org.apache.maven.project.ProjectBuildingRequest;
import org.apache.maven.project.ProjectBuildingResult;
import org.codehaus.plexus.DefaultPlexusContainer;
import org.codehaus.plexus.logging.console.ConsoleLoggerManager;
import org.sonatype.aether.impl.internal.SimpleLocalRepositoryManager;
import org.sonatype.aether.util.DefaultRepositorySystemSession;
/**
* @author mailto:lincolnbax...@gmail.com";>Lincoln Baxter, III
*/
public class MavenFacet
{
private final ProjectBuildingRequest request = new
DefaultProjectBuildingRequest();
private DefaultPlexusContainer container = null;
private ProjectBuilder builder = null;
private void bootstrapMaven()
{
if (!initialized())
{
try
{
container = new DefaultPlexusContainer();
ConsoleLoggerManager loggerManager = new ConsoleLoggerManager();
loggerManager.setThreshold("ERROR");
container.setLoggerManager(loggerManager);
builder = container.lookup(ProjectBuilder.class);
// TODO this needs to be configurable via the project/.sidekick
file.
String localRepository = getUserHomeDir().getAbsolutePath() +
"/.m2/repository";
request.setLocalRepository(new MavenArtifactRepository(
"local", new
File(localRepository).toURI().toURL().toString(),
container.lookup(ArtifactRepositoryLayout.class),
new ArtifactRepositoryPolicy(true,
ArtifactRepositoryPolicy.UPDATE_POLICY_NEVER,
ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN),
new ArtifactRepositoryPolicy(true,
ArtifactRepositoryPolicy.UPDATE_POLICY_NEVER,
ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN)));
request.setRemoteRepositories(new ArrayList());
DefaultRepositorySystemSession repositorySession = new
DefaultRepositorySystemSession();
repositorySession.setLocalRepositoryManager(new
SimpleLocalRepositoryManager(localRepository));
repositorySession.setOffline(true);
request.setRepositorySession(repositorySession);
request.setProcessPlugins(true);
request.setResolveDependencies(true);
// request.setOffline(true);
}
catch (Exception e)
{
throw new RuntimeException(e);
}
}
}
private boolean initialized()
{
return request == null;
}
/*
* POM manipulation methods
*/
public ProjectBuildingResult getProjectBuildingResult()
{
bootstrapMaven();
try
{
ProjectBuildingResult buildingResult = builder.build(getP
[jira] Closed: (MARCHETYPES-36) Version 1.1. of the web and EE archetypes broken
[ http://jira.codehaus.org/browse/MARCHETYPES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MARCHETYPES-36. Resolution: Not A Bug Assignee: Benjamin Bentmann As investigated by Jesse, classified as side effect of MNG-4428. > Version 1.1. of the web and EE archetypes broken > > > Key: MARCHETYPES-36 > URL: http://jira.codehaus.org/browse/MARCHETYPES-36 > Project: Maven Archetype Bundles > Issue Type: Bug > Components: Maven Webapp Archetype >Affects Versions: 1.1 >Reporter: Antonin Nebuzelsky >Assignee: Benjamin Bentmann > > When executing maven-archetype-plugin:generate on version 1.1 of the > following archetypes > webapp-javaee6 > ejb-javaee6 > ear-javaee6 > ear-jee5 > ear-j2ee14 > it fails with > Failed to execute goal > org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate > (default-cli) on project standalone-pom: The defined artifact is not an > archetype > See also https://netbeans.org/bugzilla/show_bug.cgi?id=190033 -- 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: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath
[
http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4810.
--
Resolution: Fixed
Fix Version/s: 3.0
Assignee: Benjamin Bentmann
Fixed by [r997467|http://svn.apache.org/viewvc?view=revision&revision=997467].
> Maven cannot build if loaded in a classloader that is not backed by a real
> JAR file / classpath
> ---
>
> Key: MNG-4810
> URL: http://jira.codehaus.org/browse/MNG-4810
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.0-beta-3
> Environment: Mac OSX & Linux, Java 1.6, Maven 3 beta 3
>Reporter: Lincoln Baxter, III
>Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: arquillian-maven-bug.tar.gz
>
>
> Maven fails to find required class files (resulting in null pointer
> exceptions) because the ClassLoader implementation in which it was loaded
> does not meet maven's assumptions of what type of information a ClassLoader
> URL should return.
> (From another perspective, that ClassLoader does not behave like a normal
> ClassLoader, but maven should probably not be contstrained to classloaders
> that provide their information as if they were backed by a JAR file; not all
> classloaders are going to use those semantics, as provided in this example,
> when the URLClassSpace instance loaded by the DefaultPlexusContainer attempts
> to read the "/MANIFEST.ML" out of a non-jar-based classloader.
> Please run example tests in attached project.
> I attempted to patch this by ignoring exceptions when attempting to pull
> manifests, but it appears that maven uses those manifests to populate some
> kind of bean container (I'm guessing guice which is abstracted via a plexus
> facade.)
> Then I attempted to modify the URLClassLoader instance in which the
> application was actually running, in order to provide a manifest, but it
> appears that maven is still just processing "Class-Path" elements and
> attempting to source those files directly, which might not work (but I had
> trouble getting this to work, so it may just have been something I was doing
> wrong.)
> If I knew more about why maven was trying to use the classloader in this way,
> I might be able to give more insightful thought into the nature/potential
> solutions of/for this issue. I do know that maven is making some assumptions
> about how the internals of classloaders are working, here in URLClassSpace:
> `
> private static String[] getClassPathEntries( final URL url )
> throws IOException
> {
> final URL manifestURL;
> if ( url.getPath().endsWith( "/" ) )
> {
> manifestURL = new URL( url, MANIFEST_ENTRY );
> }
> else
> {
> manifestURL = new URL( "jar:" + url + "!/" + MANIFEST_ENTRY );
> }
> final InputStream in = manifestURL.openStream();
> try
> {
> final String classPath = new Manifest( in
> ).getMainAttributes().getValue( "Class-Path" );
> return null != classPath ? classPath.split( " " ) : NO_ENTRIES;
> }
> finally
> {
> in.close();
> }
> }
> `
> I hope I have provided enough information, and that the attached test-case
> provides useful.
> Just run the attached project via 'mvn test' or 'mvn package' and you'll see
> the issue.
> Thanks.
--
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: (MNG-4814) Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor
[ http://jira.codehaus.org/browse/MNG-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4814. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Fixed in [r997938|http://svn.apache.org/viewvc?view=revision&revision=997938]. > Eary dependency resolution attempts for reactor projects prevent their later > resolution from the reactor > > > Key: MNG-4814 > URL: http://jira.codehaus.org/browse/MNG-4814 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.11, 2.2.1, 3.0-beta-3 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann > Fix For: 3.0 > > Attachments: MNG-4814.zip > > > If some code triggers dependency resolution for an artifact in the reactor > when that project artifact hasn't been built yet and the resolution reaches > out to a remote repo instead, any later resolution attempts will stick to the > artifact from the repo even if the reactor produced the artifact in the > meantime. -- 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: (MNG-4814) Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor
[ http://jira.codehaus.org/browse/MNG-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4814: --- Affects Version/s: 2.0.11 2.2.1 Summary: Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor (was: [regression] Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor) > Eary dependency resolution attempts for reactor projects prevent their later > resolution from the reactor > > > Key: MNG-4814 > URL: http://jira.codehaus.org/browse/MNG-4814 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.11, 2.2.1, 3.0-beta-3 >Reporter: Benjamin Bentmann > Attachments: MNG-4814.zip > > > If some code triggers dependency resolution for an artifact in the reactor > when that project artifact hasn't been built yet and the resolution reaches > out to a remote repo instead, any later resolution attempts will stick to the > artifact from the repo even if the reactor produced the artifact in the > meantime. -- 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: (MNG-4814) [regression] Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor
[
http://jira.codehaus.org/browse/MNG-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4814:
---
Attachment: MNG-4814.zip
A demo project which exhibits the issue upon running {{mvn
org.apache.maven.plugins:maven-javadoc-plugin:2.7:aggregate package -X}}. Here,
the javadoc plugin will cause dependency resolution for the entire reactor
(before anyhing has been actually built) and resolves the {{producer}} artifact
from the remote repo. When performing the {{package}} lifecycle next, the
classpaths of {{consumer}} still use the {{producer}} artifact from the local
repo instead from the now populated reactor.
> [regression] Eary dependency resolution attempts for reactor projects prevent
> their later resolution from the reactor
> -
>
> Key: MNG-4814
> URL: http://jira.codehaus.org/browse/MNG-4814
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0-beta-3
>Reporter: Benjamin Bentmann
> Attachments: MNG-4814.zip
>
>
> If some code triggers dependency resolution for an artifact in the reactor
> when that project artifact hasn't been built yet and the resolution reaches
> out to a remote repo instead, any later resolution attempts will stick to the
> artifact from the repo even if the reactor produced the artifact in the
> meantime.
--
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-4814) [regression] Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor
[regression] Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor - Key: MNG-4814 URL: http://jira.codehaus.org/browse/MNG-4814 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0-beta-3 Reporter: Benjamin Bentmann If some code triggers dependency resolution for an artifact in the reactor when that project artifact hasn't been built yet and the resolution reaches out to a remote repo instead, any later resolution attempts will stick to the artifact from the repo even if the reactor produced the artifact in the meantime. -- 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-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath
[
http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235533#action_235533
]
Benjamin Bentmann commented on MNG-4810:
Source and binary bundles of RC1 are available from:
https://repository.apache.org/content/repositories/maven-030/org/apache/maven/apache-maven/3.0-RC1/
> Maven cannot build if loaded in a classloader that is not backed by a real
> JAR file / classpath
> ---
>
> Key: MNG-4810
> URL: http://jira.codehaus.org/browse/MNG-4810
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.0-beta-3
> Environment: Mac OSX & Linux, Java 1.6, Maven 3 beta 3
>Reporter: Lincoln Baxter, III
> Attachments: arquillian-maven-bug.tar.gz
>
>
> Maven fails to find required class files (resulting in null pointer
> exceptions) because the ClassLoader implementation in which it was loaded
> does not meet maven's assumptions of what type of information a ClassLoader
> URL should return.
> (From another perspective, that ClassLoader does not behave like a normal
> ClassLoader, but maven should probably not be contstrained to classloaders
> that provide their information as if they were backed by a JAR file; not all
> classloaders are going to use those semantics, as provided in this example,
> when the URLClassSpace instance loaded by the DefaultPlexusContainer attempts
> to read the "/MANIFEST.ML" out of a non-jar-based classloader.
> Please run example tests in attached project.
> I attempted to patch this by ignoring exceptions when attempting to pull
> manifests, but it appears that maven uses those manifests to populate some
> kind of bean container (I'm guessing guice which is abstracted via a plexus
> facade.)
> Then I attempted to modify the URLClassLoader instance in which the
> application was actually running, in order to provide a manifest, but it
> appears that maven is still just processing "Class-Path" elements and
> attempting to source those files directly, which might not work (but I had
> trouble getting this to work, so it may just have been something I was doing
> wrong.)
> If I knew more about why maven was trying to use the classloader in this way,
> I might be able to give more insightful thought into the nature/potential
> solutions of/for this issue. I do know that maven is making some assumptions
> about how the internals of classloaders are working, here in URLClassSpace:
> `
> private static String[] getClassPathEntries( final URL url )
> throws IOException
> {
> final URL manifestURL;
> if ( url.getPath().endsWith( "/" ) )
> {
> manifestURL = new URL( url, MANIFEST_ENTRY );
> }
> else
> {
> manifestURL = new URL( "jar:" + url + "!/" + MANIFEST_ENTRY );
> }
> final InputStream in = manifestURL.openStream();
> try
> {
> final String classPath = new Manifest( in
> ).getMainAttributes().getValue( "Class-Path" );
> return null != classPath ? classPath.split( " " ) : NO_ENTRIES;
> }
> finally
> {
> in.close();
> }
> }
> `
> I hope I have provided enough information, and that the attached test-case
> provides useful.
> Just run the attached project via 'mvn test' or 'mvn package' and you'll see
> the issue.
> Thanks.
--
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
