[jira] (MCHECKSTYLE-138) Checkstyle plugin is @threadSafe if checkstyle itself is threadsafe
[ https://jira.codehaus.org/browse/MCHECKSTYLE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MCHECKSTYLE-138: -- Fix Version/s: 2.13 > Checkstyle plugin is @threadSafe if checkstyle itself is threadsafe > --- > > Key: MCHECKSTYLE-138 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-138 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold > Fix For: 2.13 > > > The checkstyle plugin can be marked as threadSafe if checkstyle itself can be > verified to be thread safe. > "Someone" should ask the checkstyle community if this is the case. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-170) Better document the usage of options for Maven
Karl-Heinz Marbaise created MINVOKER-170:
Summary: Better document the usage of options for Maven
Key: MINVOKER-170
URL: https://jira.codehaus.org/browse/MINVOKER-170
Project: Maven Invoker Plugin
Issue Type: Improvement
Affects Versions: 1.9
Reporter: Karl-Heinz Marbaise
Priority: Minor
We should document that it's possible to use opitons like {{-T}} within the
invoker.properties.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-170) Better document the usage of options for Maven
[
https://jira.codehaus.org/browse/MINVOKER-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MINVOKER-170:
-
Fix Version/s: 1.9.1
> Better document the usage of options for Maven
> --
>
> Key: MINVOKER-170
> URL: https://jira.codehaus.org/browse/MINVOKER-170
> Project: Maven Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.9.1
>
>
> We should document that it's possible to use opitons like {{-T}} within the
> invoker.properties.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-171) Usage of full path in local repository of artifacts
Karl-Heinz Marbaise created MINVOKER-171:
Summary: Usage of full path in local repository of artifacts
Key: MINVOKER-171
URL: https://jira.codehaus.org/browse/MINVOKER-171
Project: Maven Invoker Plugin
Issue Type: Improvement
Affects Versions: 1.9
Reporter: Karl-Heinz Marbaise
Priority: Minor
If you like to write a test for things like EventSpy it might be helpfull
having a possibility to use a kind artifact path within the invoker.properties
Instead of writing something like this (which is a bit clumsy):
{code}
invoker.mavenOpts=-Dmaven.ext.class.path=${localRepositoryPath}/xyz/abc/${project.version}/${project.build.finalName}.jar
{code}
Something like this would be more convenient:
{code}
invoker.mavenOpts=-Dmaven.ext.class.path=@project.artifact.path@
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-171) Usage of full path in invoker.propertier for artifacts from local repository
[
https://jira.codehaus.org/browse/MINVOKER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MINVOKER-171:
-
Summary: Usage of full path in invoker.propertier for artifacts from local
repository (was: Usage of full path in local repository of artifacts)
> Usage of full path in invoker.propertier for artifacts from local repository
>
>
> Key: MINVOKER-171
> URL: https://jira.codehaus.org/browse/MINVOKER-171
> Project: Maven Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
>
> If you like to write a test for things like EventSpy it might be helpfull
> having a possibility to use a kind artifact path within the invoker.properties
> Instead of writing something like this (which is a bit clumsy):
> {code}
> invoker.mavenOpts=-Dmaven.ext.class.path=${localRepositoryPath}/xyz/abc/${project.version}/${project.build.finalName}.jar
> {code}
> Something like this would be more convenient:
> {code}
> invoker.mavenOpts=-Dmaven.ext.class.path=@project.artifact.path@
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5605) ssh-wagon hangs
[ https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349188#comment-349188 ] Frank Cornelis commented on MNG-5605: - The problem still occurs on Maven 3.2.2. > ssh-wagon hangs > --- > > Key: MNG-5605 > URL: https://jira.codehaus.org/browse/MNG-5605 > Project: Maven > Issue Type: Bug > Components: Deployment >Affects Versions: 3.2.1 >Reporter: Frank Cornelis >Priority: Blocker > > When releasing (using maven-release-plugin) via Maven 3.1.1 everything works > as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden > hangs on the second ssh upload. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-172) Settings MAVEN_OPTS will prevent usage of invoker.mavenOpts in invoker properties
Karl-Heinz Marbaise created MINVOKER-172:
Summary: Settings MAVEN_OPTS will prevent usage of
invoker.mavenOpts in invoker properties
Key: MINVOKER-172
URL: https://jira.codehaus.org/browse/MINVOKER-172
Project: Maven Invoker Plugin
Issue Type: Bug
Affects Versions: 1.9
Reporter: Karl-Heinz Marbaise
Priority: Minor
If i set MAVEN_OPTS with things like {{export MAVEN_OPTS="-Xmx1024m -Xms1024m
-Djava.awt.headless=true"}} in my {{.mavenrc}} it prevents the usage of
{{invoker.mavenOpts}} within a invoker.properties file.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5605) ssh-wagon hangs
[ https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349189#comment-349189 ] Michael Osipov edited comment on MNG-5605 at 7/5/14 4:20 AM: - Has anyone tried to downgrade/upgrade Wagon SSH or another JSch version? I doubt that this is a Maven problem but solely a plugin problem. I could be wrong, though. was (Author: michael-o): Has anyone tried to downgrade Wagon SSH or another JSch version? I doubt that this is a Maven problem but solely a plugin problem. I could be wrong, though. > ssh-wagon hangs > --- > > Key: MNG-5605 > URL: https://jira.codehaus.org/browse/MNG-5605 > Project: Maven > Issue Type: Bug > Components: Deployment >Affects Versions: 3.2.1 >Reporter: Frank Cornelis >Priority: Blocker > > When releasing (using maven-release-plugin) via Maven 3.1.1 everything works > as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden > hangs on the second ssh upload. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5605) ssh-wagon hangs
[ https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349189#comment-349189 ] Michael Osipov commented on MNG-5605: - Has anyone tried to downgrade Wagon SSH or another JSch version? I doubt that this is a Maven problem but solely a plugin problem. I could be wrong, though. > ssh-wagon hangs > --- > > Key: MNG-5605 > URL: https://jira.codehaus.org/browse/MNG-5605 > Project: Maven > Issue Type: Bug > Components: Deployment >Affects Versions: 3.2.1 >Reporter: Frank Cornelis >Priority: Blocker > > When releasing (using maven-release-plugin) via Maven 3.1.1 everything works > as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden > hangs on the second ssh upload. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5501) Prerequisites don't work against Maven-3.1.0
[
https://jira.codehaus.org/browse/MNG-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349190#comment-349190
]
Alan Mehio edited comment on MNG-5501 at 7/5/14 4:21 AM:
-
As per maven pom specification from
http://maven.apache.org/pom.html#Prerequisites
it states the following:
"The POM may have certain prerequisites in order to execute correctly. For
example, perhaps there was a fix in Maven 2.0.3 that you need in order to
deploy using sftp. Here is where you give the prerequisites to building. If
these are not met, Maven will fail the build before even starting. The only
element that exists as a prerequisite in POM 4.0 is the maven element, which
takes a minimum version number."
It is still not working on maven 3.2.2 for invoking appengine-maven-plugin
which states the below in its pom
3.1.0
Regards,
Alan Mehio
London,UK
was (Author: alanmehio):
As per maven pom specification from
http://maven.apache.org/pom.html#Prerequisites
it states the following:
"The POM may have certain prerequisites in order to execute correctly. For
example, perhaps there was a fix in Maven 2.0.3 that you need in order to
deploy using sftp. Here is where you give the prerequisites to building. If
these are not met, Maven will fail the build before even starting. The only
element that exists as a prerequisite in POM 4.0 is the maven element, which
takes a minimum version number."
It is still not working on maven 3.2.2 for invoking appengine-maven-plugin
which states the below in its pom
3.1.0
> Prerequisites don't work against Maven-3.1.0
>
>
> Key: MNG-5501
> URL: https://jira.codehaus.org/browse/MNG-5501
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4, 3.0.5, 3.1.0
>Reporter: Michael Semb Wever
>
> adding
> {code}3.1.0{code}
> does not stop the project from being built with mvn-3.0.4 or mvn-3.0.5
> Is Prerequisites suppose to work or not?
> Because there is no sign of it being deprecated throughout the documentation.
> (I don't want to use the enforcer plugin).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5501) Prerequisites don't work against Maven-3.1.0
[
https://jira.codehaus.org/browse/MNG-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349190#comment-349190
]
Alan Mehio commented on MNG-5501:
-
As per maven pom specification from
http://maven.apache.org/pom.html#Prerequisites
it states the following:
"The POM may have certain prerequisites in order to execute correctly. For
example, perhaps there was a fix in Maven 2.0.3 that you need in order to
deploy using sftp. Here is where you give the prerequisites to building. If
these are not met, Maven will fail the build before even starting. The only
element that exists as a prerequisite in POM 4.0 is the maven element, which
takes a minimum version number."
It is still not working on maven 3.2.2 for invoking appengine-maven-plugin
which states the below in its pom
3.1.0
> Prerequisites don't work against Maven-3.1.0
>
>
> Key: MNG-5501
> URL: https://jira.codehaus.org/browse/MNG-5501
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4, 3.0.5, 3.1.0
>Reporter: Michael Semb Wever
>
> adding
> {code}3.1.0{code}
> does not stop the project from being built with mvn-3.0.4 or mvn-3.0.5
> Is Prerequisites suppose to work or not?
> Because there is no sign of it being deprecated throughout the documentation.
> (I don't want to use the enforcer plugin).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5501) Prerequisites don't work against Maven-3.1.0
[
https://jira.codehaus.org/browse/MNG-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349191#comment-349191
]
Michael Osipov commented on MNG-5501:
-
That field depricated and is only intended for plugins. Please use Maven
Enforcer Plugin for that.
> Prerequisites don't work against Maven-3.1.0
>
>
> Key: MNG-5501
> URL: https://jira.codehaus.org/browse/MNG-5501
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4, 3.0.5, 3.1.0
>Reporter: Michael Semb Wever
>
> adding
> {code}3.1.0{code}
> does not stop the project from being built with mvn-3.0.4 or mvn-3.0.5
> Is Prerequisites suppose to work or not?
> Because there is no sign of it being deprecated throughout the documentation.
> (I don't want to use the enforcer plugin).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5660) prerequisites element in pom does not work on maven 3.2.2
Alan Mehio created MNG-5660: --- Summary: prerequisites element in pom does not work on maven 3.2.2 Key: MNG-5660 URL: https://jira.codehaus.org/browse/MNG-5660 Project: Maven Issue Type: Bug Components: Command Line, Errors Affects Versions: 3.2.2 Environment: java 1.7 Reporter: Alan Mehio Priority: Minor Failed to execute goal com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on project guestbook: The plugin com.google .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> It should work on a min version of 3.1.0 and not exact same version as explained in maven pom specification below: http://maven.apache.org/pom.html#Prerequisites "The POM may have certain prerequisites in order to execute correctly. For example, perhaps there was a fix in Maven 2.0.3 that you need in order to deploy using sftp. Here is where you give the prerequisites to building. If these are not met, Maven will fail the build before even starting. The only element that exists as a prerequisite in POM 4.0 is the maven element, which takes a minimum version number." look at the project https://code.google.com/p/appengine-maven-plugin/ and its usage https://developers.google.com/appengine/docs/java/gettingstarted/ui_and_code and the command line which cause the issue "mvn appengine:devserver" error message : Failed to execute goal com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on project guestbook: The plugin com.google .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> [Help 1] the pom file from the google app engine maven plugin 3.1.0 . -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-235) improve difference between rules with and without violations
Herve Boutemy created MCHECKSTYLE-235: - Summary: improve difference between rules with and without violations Key: MCHECKSTYLE-235 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-235 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.12.1 Reporter: Herve Boutemy rules with violations should be more easily seen -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-235) improve difference between rules with and without violations
[ https://jira.codehaus.org/browse/MCHECKSTYLE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349192#comment-349192 ] Herve Boutemy commented on MCHECKSTYLE-235: --- done in [r1608057|http://svn.apache.org/r1608057] the "severity" column is now the first column, and the violation columns displays an icon for rules with violations only: this icon helps people find which rule has violations > improve difference between rules with and without violations > > > Key: MCHECKSTYLE-235 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-235 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.12.1 >Reporter: Herve Boutemy > > rules with violations should be more easily seen -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-235) improve difference between rules with and without violations
[ https://jira.codehaus.org/browse/MCHECKSTYLE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MCHECKSTYLE-235: -- Attachment: MCHECKSTYLE-235.png > improve difference between rules with and without violations > > > Key: MCHECKSTYLE-235 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-235 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.12.1 >Reporter: Herve Boutemy > Fix For: 2.13 > > Attachments: MCHECKSTYLE-235.png > > > rules with violations should be more easily seen -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-235) improve difference between rules with and without violations
[ https://jira.codehaus.org/browse/MCHECKSTYLE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MCHECKSTYLE-235. - Resolution: Fixed Fix Version/s: 2.13 Assignee: Herve Boutemy > improve difference between rules with and without violations > > > Key: MCHECKSTYLE-235 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-235 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.12.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.13 > > Attachments: MCHECKSTYLE-235.png > > > rules with violations should be more easily seen -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-217) Add parameter which skips rule rows which do not have any violations
[
https://jira.codehaus.org/browse/MCHECKSTYLE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349193#comment-349193
]
Herve Boutemy commented on MCHECKSTYLE-217:
---
I just did some change in MCHECKSTYLE-235 to better show the difference between
rules with and without violations
please have a look and see if this is sufficient
> Add parameter which skips rule rows which do not have any violations
>
>
> Key: MCHECKSTYLE-217
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-217
> Project: Maven Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.11
>Reporter: Michael Osipov
>
> The rules report shows all available rules even if they do not have any
> violations. For the sake of conciseness, we should add a parameter (e.g.
> {{skipEmptyViolationRules}}) we omits them from output.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-105) Three enhancements to dependency-convergence report
[ https://jira.codehaus.org/browse/MPIR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-105. --- Resolution: Duplicate > Three enhancements to dependency-convergence report > --- > > Key: MPIR-105 > URL: https://jira.codehaus.org/browse/MPIR-105 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-convergence >Affects Versions: 2.1 >Reporter: Espen Wiborg > Attachments: dependency-convergence-enhancements.patch > > > The attached patch adds three enhancements to the dependency-convergence > report: > 1. Optionally include transitive dependencies in report; see MPIR-71 > 2. Optionally only include dependencies in error state in report (cuts down > the clutter, especially when including transitive dependencies) > 3. Optionally exclude dependencies from report if they only occur in one of > the reactor projects (again, to cut clutter) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-71) Include transitive dependencies in convergence report
[ https://jira.codehaus.org/browse/MPIR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-71: --- Fix Version/s: (was: 2.x) > Include transitive dependencies in convergence report > - > > Key: MPIR-71 > URL: https://jira.codehaus.org/browse/MPIR-71 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-convergence >Reporter: Dennis Lundberg > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-71) Include transitive dependencies in convergence report
[ https://jira.codehaus.org/browse/MPIR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-71. -- Resolution: Duplicate > Include transitive dependencies in convergence report > - > > Key: MPIR-71 > URL: https://jira.codehaus.org/browse/MPIR-71 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-convergence >Reporter: Dennis Lundberg > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-240) NullPointerException thrown during Dependencies report
[
https://jira.codehaus.org/browse/MPIR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-240.
---
Resolution: Cannot Reproduce
Assignee: Michael Osipov
Cannot reproduce with Maven 3.2.2, Site Plugin 3.4.1-SNAPSHOT and MPIR 2.7.
> NullPointerException thrown during Dependencies report
> --
>
> Key: MPIR-240
> URL: https://jira.codehaus.org/browse/MPIR-240
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.4
> Environment: MacOS 10.7.3, Oracle JDK 7u4 Preview, Maven 3.0.4,
> maven-site-plugin 3.0
>Reporter: Coda Hale
>Assignee: Michael Osipov
>
> This POM:
> {code:title=pom.xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> com.example
> maven-dependencies-bug
> 0.0.1-SNAPSHOT
>
>
> com.sun.jersey
> jersey-server
> 1.12
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-site-plugin
> 3.0
>
>
>
> org.apache.maven.plugins
>
> maven-project-info-reports-plugin
> 2.4
>
>
>
>
>
>
>
> {code}
> Throws this exception:
> {noformat}
> $ mvn -e clean site
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building maven-dependencies-bug 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> maven-dependencies-bug ---
> [INFO] Deleting /private/tmp/maven-jersey-poop/target
> [INFO]
> [INFO] --- maven-site-plugin:3.0:site (default-site) @ maven-dependencies-bug
> ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.4
> [WARNING] No project URL defined - decoration links will not be relativized!
> [INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
> skin.
> [INFO] Generating "Distribution Management" report---
> maven-project-info-reports-plugin:2.4
> [INFO] Generating "About" report--- maven-project-info-reports-plugin:2.4
> [INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.4
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.978s
> [INFO] Finished at: Fri Feb 24 14:05:06 PST 2012
> [INFO] Final Memory: 13M/75M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project
> maven-dependencies-bug: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project maven-dependencies-bug: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 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:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.
[jira] (MINVOKER-173) The default values of parameters are not set as described.
[
https://jira.codehaus.org/browse/MINVOKER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MINVOKER-173:
-
Fix Version/s: 1.9.1
> The default values of parameters are not set as described.
> --
>
> Key: MINVOKER-173
> URL: https://jira.codehaus.org/browse/MINVOKER-173
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Karl-Heinz Marbaise
>Priority: Critical
> Fix For: 1.9.1
>
>
> The default values for the following parameters {{setupIncludes}}, {{goals}}
> are not set according to the documented default values.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-173) The default values of parameters are not set as described.
Karl-Heinz Marbaise created MINVOKER-173:
Summary: The default values of parameters are not set as described.
Key: MINVOKER-173
URL: https://jira.codehaus.org/browse/MINVOKER-173
Project: Maven Invoker Plugin
Issue Type: Bug
Affects Versions: 1.9
Reporter: Karl-Heinz Marbaise
Priority: Critical
The default values for the following parameters {{setupIncludes}}, {{goals}}
are not set according to the documented default values.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-240) NullPointerException thrown during Dependencies report
[
https://jira.codehaus.org/browse/MPIR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349194#comment-349194
]
Michael Osipov edited comment on MPIR-240 at 7/5/14 1:07 PM:
-
Cannot reproduce with Maven 3.2.2, Site Plugin 3.4.1-SNAPSHOT and MPIR 2.7.
{noformat}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building maven-dependencies-bug 0.0.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
maven-dependencies-bug ---
[INFO] Deleting /home/mosipov/Projekte/MPIR-240/target
[INFO]
[INFO] --- maven-site-plugin:3.4.1-SNAPSHOT:site (default-site) @
maven-dependencies-bug ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.7
[WARNING] No project URL defined - decoration links will not be relativized!
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[INFO] Generating "About" report---
maven-project-info-reports-plugin:2.7:index
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:2.7:plugin-management
[INFO] Generating "Distribution Management" report ---
maven-project-info-reports-plugin:2.7:distribution-management
[INFO] Generating "Dependency Information" report ---
maven-project-info-reports-plugin:2.7:dependency-info
[INFO] Generating "Source Repository" report---
maven-project-info-reports-plugin:2.7:scm
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:2.7:mailing-list
[INFO] Generating "Issue Tracking" report ---
maven-project-info-reports-plugin:2.7:issue-tracking
[INFO] Generating "Continuous Integration" report ---
maven-project-info-reports-plugin:2.7:cim
[INFO] Generating "Project Plugins" report ---
maven-project-info-reports-plugin:2.7:plugins
[INFO] Generating "Project License" report ---
maven-project-info-reports-plugin:2.7:license
[INFO] Generating "Project Team" report ---
maven-project-info-reports-plugin:2.7:project-team
[INFO] Generating "Project Summary" report ---
maven-project-info-reports-plugin:2.7:summary
[INFO] Generating "Dependencies" report ---
maven-project-info-reports-plugin:2.7:dependencies
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 18.300 s
[INFO] Finished at: 2014-07-05T20:07:01+02:00
[INFO] Final Memory: 15M/46M
[INFO]
{noformat}
was (Author: michael-o):
Cannot reproduce with Maven 3.2.2, Site Plugin 3.4.1-SNAPSHOT and MPIR 2.7.
> NullPointerException thrown during Dependencies report
> --
>
> Key: MPIR-240
> URL: https://jira.codehaus.org/browse/MPIR-240
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.4
> Environment: MacOS 10.7.3, Oracle JDK 7u4 Preview, Maven 3.0.4,
> maven-site-plugin 3.0
>Reporter: Coda Hale
>Assignee: Michael Osipov
>
> This POM:
> {code:title=pom.xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> com.example
> maven-dependencies-bug
> 0.0.1-SNAPSHOT
>
>
> com.sun.jersey
> jersey-server
> 1.12
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-site-plugin
> 3.0
>
>
>
> org.apache.maven.plugins
>
> maven-project-info-reports-plugin
> 2.4
>
>
>
>
>
>
>
> {code}
> Throws this exception:
> {noformat}
> $ mvn -e clean site
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building maven-dependencies-bug 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> ma
[jira] (MINVOKER-173) The default values of parameters are not set as described.
[
https://jira.codehaus.org/browse/MINVOKER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MINVOKER-173:
-
Description: The default values for the following parameters
{{setupIncludes}}, {{goals}}, {{pomIncludes}} are not set according to the
documented default values. (was: The default values for the following
parameters {{setupIncludes}}, {{goals}} are not set according to the documented
default values.)
> The default values of parameters are not set as described.
> --
>
> Key: MINVOKER-173
> URL: https://jira.codehaus.org/browse/MINVOKER-173
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Karl-Heinz Marbaise
>Priority: Critical
> Fix For: 1.9.1
>
>
> The default values for the following parameters {{setupIncludes}}, {{goals}},
> {{pomIncludes}} are not set according to the documented default values.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-235) Generating Dependencies report generates ERROR Unable to determine if resource xxx exists in https://maven-repository.dev.java.net/nonav/repository/
[
https://jira.codehaus.org/browse/MPIR-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-235.
---
Resolution: Incomplete
That repo is dead for quite some time and should not be used. All Java.net
artifacts have been pushed to Central
> Generating Dependencies report generates ERROR Unable to determine if
> resource xxx exists in https://maven-repository.dev.java.net/nonav/repository/
>
>
> Key: MPIR-235
> URL: https://jira.codehaus.org/browse/MPIR-235
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.4
> Environment: Windows 7
>Reporter: Fredrik Andersson
>
> While running mvn site using {{mvn version 3.0.3}}, {{maven-site-plugin
> version 3.0}} and {{maven-project-info-reports-plugin:2.4}}
> the Generating "Dependencies" report generates many of these:
> {noformat}
> [ERROR] Unable to determine if resource OWASP:ESAPI:jar:2.0:compile exists in
> https://maven-repository.dev.java.net/nonav/repository/
> [ERROR] Unable to determine if resource annogen:annogen:jar:0.1.0:compile
> exists in https://maven-repository.dev.java.net/nonav/repository/
> [ERROR] Unable to determine if resource ant:ant:jar:1.5:compile exists in
> https://maven-repository.dev.java.net/nonav/repository/
> {noformat}
> The report is generated but very slowly.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-269) (optionally) create dependency convergence also for single module projects
[ https://jira.codehaus.org/browse/MPIR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-269. --- Resolution: Duplicate > (optionally) create dependency convergence also for single module projects > -- > > Key: MPIR-269 > URL: https://jira.codehaus.org/browse/MPIR-269 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-convergence >Affects Versions: 2.6 >Reporter: Michael Wenig > > We are using the dependency convergence report for a quick check if a project > could be released or not. Unfortunately the report is not created for single > module projects. > MPIR-10 mentions that it is useful for multi module and therefore disabled by > default for single module projects. Unfortunately "by default" is not correct > as there is no option to activate it. > At our site the report also makes sense for single modules. The report shows > if there are snapshot versions of other projects used. > Of course someone could take a look into the dependency report and search for > SNAPSHOT. But it is a lot easier for the developers to follow a simple rule > "look into this report" - and it could be used programmatically if the report > is alway present. > Is there any reason against activating this report also for single module (an > option which is false per default would be sufficient)? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-173) The default values of parameters are not set as described.
[
https://jira.codehaus.org/browse/MINVOKER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reassigned MINVOKER-173:
Assignee: Karl-Heinz Marbaise
> The default values of parameters are not set as described.
> --
>
> Key: MINVOKER-173
> URL: https://jira.codehaus.org/browse/MINVOKER-173
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Critical
> Fix For: 1.9.1
>
>
> The default values for the following parameters {{setupIncludes}}, {{goals}},
> {{pomIncludes}} are not set according to the documented default values.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-182) Make order of reports shown in "Project Reports" configurable
[
https://jira.codehaus.org/browse/MPIR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-182.
---
Resolution: Fixed
Closing since Maven 2.x is EOL and this works in Maven 3.x.
> Make order of reports shown in "Project Reports" configurable
> -
>
> Key: MPIR-182
> URL: https://jira.codehaus.org/browse/MPIR-182
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.1.2
>Reporter: Andreas Sewe
>Assignee: Robert Scholte
>Priority: Minor
> Fix For: 2.7
>
>
> As far as I can tell the plugin's reports are presented in alphabetical order
> in the "Project Reports" menu. While having "About" come first seems natural,
> some of the other menu items (in particular, "Source Repository") are placed
> less than optimally. Why not make this configurable, e.g., by making the
> order significant in which the {{report}} elements occur in the plugin's
> configuration?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-236) add Rule name to violation message
Herve Boutemy created MCHECKSTYLE-236: - Summary: add Rule name to violation message Key: MCHECKSTYLE-236 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-236 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.12.1 Reporter: Herve Boutemy having only the violation message without the rule name makes difficult to match rules summary with file details -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-174) The execution order of setupIncludes can't be predicted
Karl-Heinz Marbaise created MINVOKER-174: Summary: The execution order of setupIncludes can't be predicted Key: MINVOKER-174 URL: https://jira.codehaus.org/browse/MINVOKER-174 Project: Maven Invoker Plugin Issue Type: Bug Affects Versions: 1.9 Reporter: Karl-Heinz Marbaise Priority: Critical It is really necessary to have at least one criteria which gives the possibility to define the order of executions of the setup projects which can be given by setupIncludes. Currently there is no such possibility. It should be at least possible to define the order by sorting in some way. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5660) prerequisites element in pom does not work on maven 3.2.2
[ https://jira.codehaus.org/browse/MNG-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349197#comment-349197 ] Jason van Zyl commented on MNG-5660: I cannot reproduce with a test plugin being built with 3.1.0 and then run with 3.2.2. Everything works here. I'll make a case and ask another Maven dev to validate. > prerequisites element in pom does not work on maven 3.2.2 > - > > Key: MNG-5660 > URL: https://jira.codehaus.org/browse/MNG-5660 > Project: Maven > Issue Type: Bug > Components: Command Line, Errors >Affects Versions: 3.2.2 > Environment: java 1.7 >Reporter: Alan Mehio >Priority: Minor > > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> > It should work on a min version of 3.1.0 and not exact same version as > explained in maven pom specification below: > http://maven.apache.org/pom.html#Prerequisites > "The POM may have certain prerequisites in order to execute correctly. For > example, perhaps there was a fix in Maven 2.0.3 that you need in order to > deploy using sftp. Here is where you give the prerequisites to building. If > these are not met, Maven will fail the build before even starting. The only > element that exists as a prerequisite in POM 4.0 is the maven element, which > takes a minimum version number." > look at the project > https://code.google.com/p/appengine-maven-plugin/ > and its usage > https://developers.google.com/appengine/docs/java/gettingstarted/ui_and_code > and the command line which cause the issue > "mvn appengine:devserver" > error message : > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> [Help > 1] > the pom file from the google app engine maven plugin > > > 3.1.0 > > . -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5605) ssh-wagon hangs
[ https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349198#comment-349198 ] Jason van Zyl commented on MNG-5605: Anyone with the issue needs to try Maven 3.2.2 with Wagon 2.4 which is what 3.1.1 uses. None of the resolver code has changed as we are still at Aether 0.0.9.M2. It can't be fixed in Maven 3.2.2 if it's a Wagon issue. > ssh-wagon hangs > --- > > Key: MNG-5605 > URL: https://jira.codehaus.org/browse/MNG-5605 > Project: Maven > Issue Type: Bug > Components: Deployment >Affects Versions: 3.2.1 >Reporter: Frank Cornelis >Priority: Blocker > > When releasing (using maven-release-plugin) via Maven 3.1.1 everything works > as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden > hangs on the second ssh upload. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5661) Make MavenProject instances immutable after initial construction
Jason van Zyl created MNG-5661: -- Summary: Make MavenProject instances immutable after initial construction Key: MNG-5661 URL: https://jira.codehaus.org/browse/MNG-5661 Project: Maven Issue Type: New Feature Reporter: Jason van Zyl When a MavenProject is initially constructed it is not immutable and requires subsequent mutation to be complete in different circumstance. This makes the logic in MavenProject complex and makes MavenProject hard to understand. We need to move toward being complete and immutable after construction. This not being the case has a number of consequences two of which are: 1) Components are required in MavenProject in order to lazily construct certain values. This complicates MavenProject when it simply should be a configuration, or data. The logic to construct anything should be moved to the ProjectBuilder, take the small hit in performance, and all construction should happen up-front. 2) The lifecycle needs to be executed in order for a MavenProject instance to be fully populated with respect to source directories and project resources. This makes it particularly hard for systems like IDEs to integrate without resorting to weird tricks to figure out generated source directories without executing Maven itself. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5661) Make MavenProject instances immutable after initial construction
[ https://jira.codehaus.org/browse/MNG-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5661: --- Assignee: Jason van Zyl > Make MavenProject instances immutable after initial construction > > > Key: MNG-5661 > URL: https://jira.codehaus.org/browse/MNG-5661 > Project: Maven > Issue Type: New Feature >Reporter: Jason van Zyl >Assignee: Jason van Zyl > > When a MavenProject is initially constructed it is not immutable and > requires subsequent mutation to be complete in different circumstance. This > makes the logic in MavenProject complex and makes MavenProject hard to > understand. We need to move toward being complete and immutable after > construction. > This not being the case has a number of consequences two of which are: > 1) Components are required in MavenProject in order to lazily construct > certain values. This complicates MavenProject when it simply should be a > configuration, or data. The logic to construct anything should be moved to > the ProjectBuilder, take the small hit in performance, and all construction > should happen up-front. > 2) The lifecycle needs to be executed in order for a MavenProject instance to > be fully populated with respect to source directories and project resources. > This makes it particularly hard for systems like IDEs to integrate without > resorting to weird tricks to figure out generated source directories without > executing Maven itself. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5661) Make MavenProject instances immutable after initial construction
[ https://jira.codehaus.org/browse/MNG-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349199#comment-349199 ] Jason van Zyl commented on MNG-5661: First step of the work has been completed to remove all the componentry from MavenProject. Work done on 6cf9320942c34bc68205425ab696b1712ace9ba4 > Make MavenProject instances immutable after initial construction > > > Key: MNG-5661 > URL: https://jira.codehaus.org/browse/MNG-5661 > Project: Maven > Issue Type: New Feature >Reporter: Jason van Zyl >Assignee: Jason van Zyl > > When a MavenProject is initially constructed it is not immutable and > requires subsequent mutation to be complete in different circumstance. This > makes the logic in MavenProject complex and makes MavenProject hard to > understand. We need to move toward being complete and immutable after > construction. > This not being the case has a number of consequences two of which are: > 1) Components are required in MavenProject in order to lazily construct > certain values. This complicates MavenProject when it simply should be a > configuration, or data. The logic to construct anything should be moved to > the ProjectBuilder, take the small hit in performance, and all construction > should happen up-front. > 2) The lifecycle needs to be executed in order for a MavenProject instance to > be fully populated with respect to source directories and project resources. > This makes it particularly hard for systems like IDEs to integrate without > resorting to weird tricks to figure out generated source directories without > executing Maven itself. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5349) NullPointerException if missing id in org.apache.maven.lifecycle.Lifecycle
[
https://jira.codehaus.org/browse/MNG-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349200#comment-349200
]
Jason van Zyl commented on MNG-5349:
Check has been added on 1a4c003a2bbe04cb18a61adc1bae09133066a116
> NullPointerException if missing id in org.apache.maven.lifecycle.Lifecycle
> --
>
> Key: MNG-5349
> URL: https://jira.codehaus.org/browse/MNG-5349
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0.4
> Environment: Ubuntu Precise, Maven 3.0.4
>Reporter: John Riedl
>Priority: Minor
> Attachments: components.xml, lifecycles.xml, phase-test.tar, pom.xml
>
>
> I've been working with custom lifecycles, and accidentally left the "id" out
> of one of them. You can see it in this example where I commented out the key
> line (everything works fine if this line is uncommented):
> {code:xml}
>
>
>
> org.apache.maven.lifecycle.mapping.LifecycleMapping
> phase-test
>
> org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
>
>
>
> org.apache.maven.lifecycle.Lifecycle
> phase-test
> org.apache.maven.lifecycle.Lifecycle
>
>
>
> tp-pre-new-phase
> tp-new-phase
> tp-post-new-phase
>
>
>
> org.riedl:phase-test-maven-plugin:greet
>
>
>
>
>
> ~
> {code}
> Here's most of the stack trace:
> {noformat}
> (macro: ~/Src/lenskit-projects/tryout-phase-test-plugin) mvn tp-post-new-phase
> [INFO] Scanning for projects...
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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: java.lang.NullPointerException
> at java.lang.String.compareTo(String.java:1167)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer$1.compare(DefaultLifecyclePluginAnalyzer.java:144)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer$1.compare(DefaultLifecyclePluginAnalyzer.java:140)
> at java.util.Arrays.mergeSort(Arrays.java:1270)
> at java.util.Arrays.sort(Arrays.java:1210)
> at java.util.Collections.sort(Collections.java:159)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getOrderedLifecycles(DefaultLifecyclePluginAnalyzer.java:139)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:96)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:63)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:397)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:371)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:560)
> {noformat}
> The NullPointerException happens with most attempts to run the project, such
> as "mvn foo". I've attached the pom.xml, lifecycles.xml, components.xml, and
> the Java for the plugin. I think only components.xml is relevant.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5349) NullPointerException if missing id in org.apache.maven.lifecycle.Lifecycle
[
https://jira.codehaus.org/browse/MNG-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-5349.
--
Resolution: Fixed
Fix Version/s: 3.2.3
> NullPointerException if missing id in org.apache.maven.lifecycle.Lifecycle
> --
>
> Key: MNG-5349
> URL: https://jira.codehaus.org/browse/MNG-5349
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0.4
> Environment: Ubuntu Precise, Maven 3.0.4
>Reporter: John Riedl
>Priority: Minor
> Fix For: 3.2.3
>
> Attachments: components.xml, lifecycles.xml, phase-test.tar, pom.xml
>
>
> I've been working with custom lifecycles, and accidentally left the "id" out
> of one of them. You can see it in this example where I commented out the key
> line (everything works fine if this line is uncommented):
> {code:xml}
>
>
>
> org.apache.maven.lifecycle.mapping.LifecycleMapping
> phase-test
>
> org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
>
>
>
> org.apache.maven.lifecycle.Lifecycle
> phase-test
> org.apache.maven.lifecycle.Lifecycle
>
>
>
> tp-pre-new-phase
> tp-new-phase
> tp-post-new-phase
>
>
>
> org.riedl:phase-test-maven-plugin:greet
>
>
>
>
>
> ~
> {code}
> Here's most of the stack trace:
> {noformat}
> (macro: ~/Src/lenskit-projects/tryout-phase-test-plugin) mvn tp-post-new-phase
> [INFO] Scanning for projects...
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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: java.lang.NullPointerException
> at java.lang.String.compareTo(String.java:1167)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer$1.compare(DefaultLifecyclePluginAnalyzer.java:144)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer$1.compare(DefaultLifecyclePluginAnalyzer.java:140)
> at java.util.Arrays.mergeSort(Arrays.java:1270)
> at java.util.Arrays.sort(Arrays.java:1210)
> at java.util.Collections.sort(Collections.java:159)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getOrderedLifecycles(DefaultLifecyclePluginAnalyzer.java:139)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:96)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:63)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:397)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:371)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:560)
> {noformat}
> The NullPointerException happens with most attempts to run the project, such
> as "mvn foo". I've attached the pom.xml, lifecycles.xml, components.xml, and
> the Java for the plugin. I think only components.xml is relevant.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5349) NullPointerException if missing id in org.apache.maven.lifecycle.Lifecycle
[
https://jira.codehaus.org/browse/MNG-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349201#comment-349201
]
Jason van Zyl commented on MNG-5349:
Fixed on 1a4c003a2bbe04cb18a61adc1bae09133066a116
> NullPointerException if missing id in org.apache.maven.lifecycle.Lifecycle
> --
>
> Key: MNG-5349
> URL: https://jira.codehaus.org/browse/MNG-5349
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0.4
> Environment: Ubuntu Precise, Maven 3.0.4
>Reporter: John Riedl
>Priority: Minor
> Fix For: 3.2.3
>
> Attachments: components.xml, lifecycles.xml, phase-test.tar, pom.xml
>
>
> I've been working with custom lifecycles, and accidentally left the "id" out
> of one of them. You can see it in this example where I commented out the key
> line (everything works fine if this line is uncommented):
> {code:xml}
>
>
>
> org.apache.maven.lifecycle.mapping.LifecycleMapping
> phase-test
>
> org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
>
>
>
> org.apache.maven.lifecycle.Lifecycle
> phase-test
> org.apache.maven.lifecycle.Lifecycle
>
>
>
> tp-pre-new-phase
> tp-new-phase
> tp-post-new-phase
>
>
>
> org.riedl:phase-test-maven-plugin:greet
>
>
>
>
>
> ~
> {code}
> Here's most of the stack trace:
> {noformat}
> (macro: ~/Src/lenskit-projects/tryout-phase-test-plugin) mvn tp-post-new-phase
> [INFO] Scanning for projects...
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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: java.lang.NullPointerException
> at java.lang.String.compareTo(String.java:1167)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer$1.compare(DefaultLifecyclePluginAnalyzer.java:144)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer$1.compare(DefaultLifecyclePluginAnalyzer.java:140)
> at java.util.Arrays.mergeSort(Arrays.java:1270)
> at java.util.Arrays.sort(Arrays.java:1210)
> at java.util.Collections.sort(Collections.java:159)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getOrderedLifecycles(DefaultLifecyclePluginAnalyzer.java:139)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:96)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:63)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:397)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:371)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:560)
> {noformat}
> The NullPointerException happens with most attempts to run the project, such
> as "mvn foo". I've attached the pom.xml, lifecycles.xml, components.xml, and
> the Java for the plugin. I think only components.xml is relevant.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
