[jira] (MRELEASE-746) SCM URL being mangled
[
https://jira.codehaus.org/browse/MRELEASE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354810#comment-354810
]
Ralph Goers commented on MRELEASE-746:
--
Quite horribly I was able to get
scm:git:g...@git.phx1.unitedweb.com::~rgoers/nextivaall/rgoerss-nextivabillsoft.git
to work. One of the ':' is stripped out and the other is left which causes git
to function properly.
> SCM URL being mangled
> -
>
> Key: MRELEASE-746
> URL: https://jira.codehaus.org/browse/MRELEASE-746
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2, 2.5.1
> Environment: Windows 7 SP1, Java SDK 1.6.0_03, Maven 3.0.4
>Reporter: Logan McGrath
>Assignee: Mark Struberg
>
> When performing {{mvn release:prepare}}, the plugin is removing colons from
> my GIT URL. My project is hosted on Beanstalk.
> Here's the [redacted] URL specified in the POM's SCM element:
> git@[account].beanstalkapp.com:/[project].git
> Here's the [redacted] URL the plugin ends up using:
> git@[account].beanstalkapp.com/[project].git
> Notice the missing colon.
> The specific error I get using {{mvn release:prepare}} is:
> {noformat}
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear
> to be a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> {noformat}
> Running the command {{mvn release:prepare -X}} gives me:
> Command output:
> {noformat}
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> 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.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: org.apache.maven.plugin.MojoFailureException: Unable to commit
> files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:310)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
> Unable to commit files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:168)
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:148)
> at
> org.apache.
[jira] (MRELEASE-746) SCM URL being mangled
[
https://jira.codehaus.org/browse/MRELEASE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354807#comment-354807
]
Ralph Goers commented on MRELEASE-746:
--
trying with
scm:git://g...@git.phx1.unitedweb.com:~rgoers/nextivaall/rgoerss-nextivabillsoft.git
results in
fatal:
'%2f%2f...@git.phx1.unitedweb.com~rgoers/nextivaall/rgoerss-nextivabillsoft.git'
does not appear to be a git repository
> SCM URL being mangled
> -
>
> Key: MRELEASE-746
> URL: https://jira.codehaus.org/browse/MRELEASE-746
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2, 2.5.1
> Environment: Windows 7 SP1, Java SDK 1.6.0_03, Maven 3.0.4
>Reporter: Logan McGrath
>Assignee: Mark Struberg
>
> When performing {{mvn release:prepare}}, the plugin is removing colons from
> my GIT URL. My project is hosted on Beanstalk.
> Here's the [redacted] URL specified in the POM's SCM element:
> git@[account].beanstalkapp.com:/[project].git
> Here's the [redacted] URL the plugin ends up using:
> git@[account].beanstalkapp.com/[project].git
> Notice the missing colon.
> The specific error I get using {{mvn release:prepare}} is:
> {noformat}
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear
> to be a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> {noformat}
> Running the command {{mvn release:prepare -X}} gives me:
> Command output:
> {noformat}
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> 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.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: org.apache.maven.plugin.MojoFailureException: Unable to commit
> files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:310)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
> Unable to commit files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:168)
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:148)
>
[jira] (MRELEASE-746) SCM URL being mangled
[
https://jira.codehaus.org/browse/MRELEASE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated MRELEASE-746:
-
Affects Version/s: 2.5.1
> SCM URL being mangled
> -
>
> Key: MRELEASE-746
> URL: https://jira.codehaus.org/browse/MRELEASE-746
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2, 2.5.1
> Environment: Windows 7 SP1, Java SDK 1.6.0_03, Maven 3.0.4
>Reporter: Logan McGrath
>Assignee: Mark Struberg
>
> When performing {{mvn release:prepare}}, the plugin is removing colons from
> my GIT URL. My project is hosted on Beanstalk.
> Here's the [redacted] URL specified in the POM's SCM element:
> git@[account].beanstalkapp.com:/[project].git
> Here's the [redacted] URL the plugin ends up using:
> git@[account].beanstalkapp.com/[project].git
> Notice the missing colon.
> The specific error I get using {{mvn release:prepare}} is:
> {noformat}
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear
> to be a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> {noformat}
> Running the command {{mvn release:prepare -X}} gives me:
> Command output:
> {noformat}
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> 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.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: org.apache.maven.plugin.MojoFailureException: Unable to commit
> files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:310)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
> Unable to commit files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:168)
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:148)
> at
> org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.java:75)
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:79)
> at
> org.apache.mave
[jira] (MRELEASE-746) SCM URL being mangled
[
https://jira.codehaus.org/browse/MRELEASE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354806#comment-354806
]
Ralph Goers commented on MRELEASE-746:
--
I am also seeing this error with version 2.5.1 of the release plugin. In my
case the actual url in the configuration is
scm:git:g...@git.phx1.unitedweb.com:~rgoers/nextivaall/rgoerss-nextivabillsoft.git
but the error message is:
fatal:
'g...@git.phx1.unitedweb.com~rgoers/nextivaall/rgoerss-nextivabillsoft.git'
does not appear to be a git repository
Notice that the ':' between the server and the project was lost. For me this
only seems to happen when the project starts with a '~', which is what
gitorious does when you clone a project to your personal area.
> SCM URL being mangled
> -
>
> Key: MRELEASE-746
> URL: https://jira.codehaus.org/browse/MRELEASE-746
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2
> Environment: Windows 7 SP1, Java SDK 1.6.0_03, Maven 3.0.4
>Reporter: Logan McGrath
>Assignee: Mark Struberg
>
> When performing {{mvn release:prepare}}, the plugin is removing colons from
> my GIT URL. My project is hosted on Beanstalk.
> Here's the [redacted] URL specified in the POM's SCM element:
> git@[account].beanstalkapp.com:/[project].git
> Here's the [redacted] URL the plugin ends up using:
> git@[account].beanstalkapp.com/[project].git
> Notice the missing colon.
> The specific error I get using {{mvn release:prepare}} is:
> {noformat}
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear
> to be a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> {noformat}
> Running the command {{mvn release:prepare -X}} gives me:
> Command output:
> {noformat}
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> 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.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: org.apache.maven.plugin.MojoFailureException: Unable to commit
> files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:310)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
> Unable to commit files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not app
[jira] (MASSEMBLY-691) dependencySet with filtered option has differents behaviors
[ https://jira.codehaus.org/browse/MASSEMBLY-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MASSEMBLY-691: - Fix Version/s: (was: 2.5) > dependencySet with filtered option has differents behaviors > --- > > Key: MASSEMBLY-691 > URL: https://jira.codehaus.org/browse/MASSEMBLY-691 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: dependencySet >Affects Versions: 2.4 >Reporter: Arnaud Brunet > Attachments: sample.zip > > > Hello, > In the sample projet, there are two artifacts : > - "bug:assembly" contains an assembly descriptor which includes the other > artifact. > - "bug:assembly-dependency" is a simple artifact with a properties file. > In the assembly description, I want to unpack the artifact > "bug:assembly-dependency". > In the unpack options, > - if I put parameter "filtered" on false, my properties file is put in conf > directory, > - but if I put "filtered" on true, my properties file is in > conf/assembly-dependency-0.0.1-SNAPSHOT.jar directory. > I expected that only my properties file exchange between the two options. Why > am I getting the "assembly-dependency-0.0.1-SNAPSHOT.jar " directory ? > Regards, > Arnaud -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-674) escapeString using \ does not work correctly
[
https://jira.codehaus.org/browse/MASSEMBLY-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated MASSEMBLY-674:
-
Fix Version/s: (was: 2.5)
> escapeString using \ does not work correctly
>
>
> Key: MASSEMBLY-674
> URL: https://jira.codehaus.org/browse/MASSEMBLY-674
> Project: Maven Assembly Plugin
> Issue Type: Improvement
> Components: filtering
>Affects Versions: 2.4
>Reporter: Iain Coulter
>Priority: Minor
> Attachments: escapeStringBug.zip
>
>
> Using \ does not correctly when dealing with
> case where previous text is also a \.
> attached pom,test and assembly.xml show what happens. The follwoing scenario
> is currently fail: (varible=Hello)
> {code}
> C:\path\\${variable}
> {code}
> converted to
> {code}
> C:\path\\Hello
> {code}
> I would of expected:
> {code}
> C:\path\${variable}
> {code}
> The following does work but is not exactly as required as it means you get
> get two \'s
> {code}
> C:\path\\\${variable}
> {code}
> converted to
> {code}
> C:\path\\${variable}
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-720) Fixed Checkstyle reported errors / warnings
[ https://jira.codehaus.org/browse/MASSEMBLY-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MASSEMBLY-720: - Fix Version/s: (was: 2.5) > Fixed Checkstyle reported errors / warnings > --- > > Key: MASSEMBLY-720 > URL: https://jira.codehaus.org/browse/MASSEMBLY-720 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Priority: Minor > > Reduce the checkstyle reported issues. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-963) Unable to set empty environment variables
[
https://jira.codehaus.org/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354803#comment-354803
]
Tibor Digana commented on SUREFIRE-963:
---
>> When do you plan to release the version 2.18 ?
In few weeks -:)
@Christophe DENEUX
Do you have some spare time to investigate and fix one more interesting bug ?
> Unable to set empty environment variables
> -
>
> Key: SUREFIRE-963
> URL: https://jira.codehaus.org/browse/SUREFIRE-963
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Linux Ubuntu 12.10,Maven 3.0.4
>Reporter: Christophe DENEUX
>Assignee: Tibor Digana
> Fix For: 2.18
>
> Attachments: SUREFIRE-963.txt
>
>
> With the following configuration of the maven-surefire-plugin:
> {code}
>
>
>
>
>
> {code}
> I get the String "null" instead of "" as value of my env var in my unit test.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-677) NPE using includeMetadata true for repository in a descriptor.
[
https://jira.codehaus.org/browse/MASSEMBLY-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated MASSEMBLY-677:
-
Fix Version/s: (was: 2.5)
> NPE using includeMetadata true for repository in a descriptor.
> --
>
> Key: MASSEMBLY-677
> URL: https://jira.codehaus.org/browse/MASSEMBLY-677
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.4
> Environment: Apache Maven 3.1.1
> (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 17:22:22+0200)
> Maven home: /usr/share/maven
> Java version: 1.7.0_21, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"
>Reporter: Karl-Heinz Marbaise
> Attachments: assemblies-repository-failure.zip
>
>
> I'm trying to create a repository via Maven assembly plugin and used the
> includeMetadata option. If i use false everything is ok (or just remove
> completely cause false is the default). If i change it to true i got the
> following failure:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single (make-bundles) on
> project dist: Execution make-bundles of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (make-bundles)
> on project dist: Execution make-bundles of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> make-bundles of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.getLocalFilename(AbstractRepositoryMetadata.java:60)
> at
> org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout.pathOfLocalRepositoryMetadata(DefaultRepositoryLayout.java:72)
> at
> org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfLocalRepositoryMetadata(DefaultArtifactRepository.java:128)
> at
> org.apache.maven.shared.repository.DefaultRepositoryAssembler.assembleRepositoryMetadata(DefaultRepositoryAssembler.java:487)
> at
> org.apache.maven.shared.repository.DefaultRepositoryAssembler.buildRemoteRepository(DefaultRepositoryAssembler.java:231)
> at
> org.apache.maven.plugin.assembly.archive.phase.RepositoryAssemblyPhase.execute(RepositoryAssemblyPhase.java:99)
> at
> org.apache.mave
[jira] (MASSEMBLY-474) Assembly is duplicating dependecies in the output
[
https://jira.codehaus.org/browse/MASSEMBLY-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated MASSEMBLY-474:
-
Fix Version/s: (was: 2.5)
> Assembly is duplicating dependecies in the output
> --
>
> Key: MASSEMBLY-474
> URL: https://jira.codehaus.org/browse/MASSEMBLY-474
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: moduleSet
>Affects Versions: 2.2
>Reporter: Andrew Rampulla
>Assignee: Kristian Rosenvold
> Attachments: assembly-test-mulit-project.zip
>
>
> When I have an assembly descriptor that contains 2 modules that both have the
> same dependencies, those dependencies are duplicated instead of
> skipped/overwritten in the target zip file. This is very similiar to
> MASSEMBLY-285, but is a problem on the dependencies and not the modules
> themselves. This is only a problem when
> {code:xml}
>
>
> aaa:
> aaa:
>
>
> true
> false
> lib
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MECLIPSE-756) Fix RAT Report
[ https://jira.codehaus.org/browse/MECLIPSE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MECLIPSE-756. Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1633698|http://svn.apache.org/r1633698]. > Fix RAT Report > -- > > Key: MECLIPSE-756 > URL: https://jira.codehaus.org/browse/MECLIPSE-756 > Project: Maven Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.10 > > > Clean up RAT report warnings / issues -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MECLIPSE-756) Fix RAT Report
[ https://jira.codehaus.org/browse/MECLIPSE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354801#comment-354801 ] Karl-Heinz Marbaise commented on MECLIPSE-756: -- Fixed in [r1633696|http://svn.apache.org/r1633696]. > Fix RAT Report > -- > > Key: MECLIPSE-756 > URL: https://jira.codehaus.org/browse/MECLIPSE-756 > Project: Maven Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.10 > > > Clean up RAT report warnings / issues -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-775) Request for new optional parameter RTC (workItem) with release:prepare to associate workitem with changesets got created during build process
[
https://jira.codehaus.org/browse/SCM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354794#comment-354794
]
AShit Shah commented on SCM-775:
Hi Chris,
Any update on this issue?
Thanks.
> Request for new optional parameter RTC (workItem) with release:prepare to
> associate workitem with changesets got created during build process
> -
>
> Key: SCM-775
> URL: https://jira.codehaus.org/browse/SCM-775
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-jazz
>Affects Versions: 1.9.1
>Reporter: AShit Shah
>
> Maven {{release:prepare}} command is failing with below error while
> delivering updated pom.xml to the stream due to Preconditions configured in
> RTC to have comments and associated work item with every delivery.
> {noformat}
> [ERROR] Name: Deliver
> [ERROR] Participant Reports:
> [ERROR] Name: Require Work items and Comments
> [ERROR] A work item must be associated with the change set.`
> [ERROR] At least one of the associated work items must specify that the work
> is planned for the current iteration.
> [ERROR] At least one of the associated work items must be assigned to you.
> [ERROR] Problem running 'deliver':
> [ERROR] 'Deliver' failed. Preconditions have not been met: A work item must
> be associated with the change set.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli)
> on project junit-ext: Unable to commit files
> Provider message:
> Error code for Jazz SCM deliver command - 17
> {noformat}
> I can not find any optional parameters on
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html
> for release:prepare command which I can use and pass the RTC workitem number
> on command line.
> Suggestion:
> It will be great if you can provide optional parameters like "workItem" which
> I can use and pass RTC workitem number with release:prepare at command line.
> Example: {{mvn -PmyProfile release:prepare -DworkItem=123456}}
> So build process should associate change sets created by {{release:prepare}}
> with work item 123456 and deliver change sets to the stream.
> As of now I have to use "{{-DpushChanges=false}}" parameter to block delivery
> process and I have to manually find the change sets, associate them with work
> item and deliver them before I run {{release:perform}}.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-716) Update plexus-io from 2.0.9 to 2.3.1
[ https://jira.codehaus.org/browse/MASSEMBLY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MASSEMBLY-716: - Description: Release Notes - Plexus Components - Version plexus-io-2.3 ** Improvement * [PLXCOMP-260] - Make plexus io collections iterable ** New Feature * [PLXCOMP-261] - Make plexus io collections support on-the-fly filtering Release Notes - Plexus Components - Version plexus-io-2.2 ** Bug * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale dependencies * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are used Release Notes - Plexus Components - Version plexus-io-2.1.4 ** Bug * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . Release Notes - Plexus Components - Version plexus-io-2.1.3 * [PLXCOMP-247] - Bug with windows AND java5 Release Notes - Plexus Components - Version plexus-io-2.1.2 * [PLXCOMP-244] - Don't try to set attributes of symbolic links * [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux Release Notes - Plexus Components - Version plexus-io-2.1.1 ** Bug * [PLXCOMP-243] - Restore JDK1.5 compatibility Release Notes - Plexus Components - Version plexus-io-2.0.12 * [PLXCOMP-249] - Add support for java7 chmod Release Notes - Plexus Components - Version plexus-io-2.0.10 * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled was: Release Notes - Plexus Components - Version plexus-io-2.2 ** Bug * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale dependencies * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are used Release Notes - Plexus Components - Version plexus-io-2.1.4 ** Bug * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . Release Notes - Plexus Components - Version plexus-io-2.1.3 * [PLXCOMP-247] - Bug with windows AND java5 Release Notes - Plexus Components - Version plexus-io-2.1.2 * [PLXCOMP-244] - Don't try to set attributes of symbolic links * [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux Release Notes - Plexus Components - Version plexus-io-2.1.1 ** Bug * [PLXCOMP-243] - Restore JDK1.5 compatibility Release Notes - Plexus Components - Version plexus-io-2.0.12 * [PLXCOMP-249] - Add support for java7 chmod Release Notes - Plexus Components - Version plexus-io-2.0.10 * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled > Update plexus-io from 2.0.9 to 2.3.1 > > > Key: MASSEMBLY-716 > URL: https://jira.codehaus.org/browse/MASSEMBLY-716 > Project: Maven Assembly Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 2.5 > > > Release Notes - Plexus Components - Version plexus-io-2.3 > ** Improvement > * [PLXCOMP-260] - Make plexus io collections iterable > ** New Feature > * [PLXCOMP-261] - Make plexus io collections support on-the-fly filtering > Release Notes - Plexus Components - Version plexus-io-2.2 > ** Bug > * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale > dependencies > * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are > used > Release Notes - Plexus Components - Version plexus-io-2.1.4 > ** Bug > * [PLXCOMP-107] - Fail to unzip archive, which contains file with name > 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . > Release Notes - Plexus Components - Version plexus-io-2.1.3 > * [PLXCOMP-247] - Bug with windows AND java5 > Release Notes - Plexus Components - Version plexus-io-2.1.2 > * [PLXCOMP-244] - Don't try to set attributes of symbolic links > * [PLXCOMP-245] - Archives created on windows get zero permissions, > creates malformed permissions on linux > Release Notes - Plexus Components - Version plexus-io-2.1.1 > ** Bug > * [PLXCOMP-243] - Restore JDK1.5 compatibility > Release Notes - Plexus Components - Version plexus-io-2.0.12 > * [PLXCOMP-249] - Add support for java7 chmod > Release Notes - Plexus Components - Version plexus-io-2.0.10 > * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-716) Update plexus-io from 2.0.9 to 2.3.1
[ https://jira.codehaus.org/browse/MASSEMBLY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MASSEMBLY-716: - Description: Release Notes - Plexus Components - Version plexus-io-2.3.1 ** Bug * [PLXCOMP-264] - Thread safety issue in streamconsumer Release Notes - Plexus Components - Version plexus-io-2.3 ** Improvement * [PLXCOMP-260] - Make plexus io collections iterable ** New Feature * [PLXCOMP-261] - Make plexus io collections support on-the-fly filtering Release Notes - Plexus Components - Version plexus-io-2.2 ** Bug * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale dependencies * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are used Release Notes - Plexus Components - Version plexus-io-2.1.4 ** Bug * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . Release Notes - Plexus Components - Version plexus-io-2.1.3 * [PLXCOMP-247] - Bug with windows AND java5 Release Notes - Plexus Components - Version plexus-io-2.1.2 * [PLXCOMP-244] - Don't try to set attributes of symbolic links * [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux Release Notes - Plexus Components - Version plexus-io-2.1.1 ** Bug * [PLXCOMP-243] - Restore JDK1.5 compatibility Release Notes - Plexus Components - Version plexus-io-2.0.12 * [PLXCOMP-249] - Add support for java7 chmod Release Notes - Plexus Components - Version plexus-io-2.0.10 * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled was: Release Notes - Plexus Components - Version plexus-io-2.3 ** Improvement * [PLXCOMP-260] - Make plexus io collections iterable ** New Feature * [PLXCOMP-261] - Make plexus io collections support on-the-fly filtering Release Notes - Plexus Components - Version plexus-io-2.2 ** Bug * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale dependencies * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are used Release Notes - Plexus Components - Version plexus-io-2.1.4 ** Bug * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . Release Notes - Plexus Components - Version plexus-io-2.1.3 * [PLXCOMP-247] - Bug with windows AND java5 Release Notes - Plexus Components - Version plexus-io-2.1.2 * [PLXCOMP-244] - Don't try to set attributes of symbolic links * [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux Release Notes - Plexus Components - Version plexus-io-2.1.1 ** Bug * [PLXCOMP-243] - Restore JDK1.5 compatibility Release Notes - Plexus Components - Version plexus-io-2.0.12 * [PLXCOMP-249] - Add support for java7 chmod Release Notes - Plexus Components - Version plexus-io-2.0.10 * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled > Update plexus-io from 2.0.9 to 2.3.1 > > > Key: MASSEMBLY-716 > URL: https://jira.codehaus.org/browse/MASSEMBLY-716 > Project: Maven Assembly Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 2.5 > > > Release Notes - Plexus Components - Version plexus-io-2.3.1 > ** Bug > * [PLXCOMP-264] - Thread safety issue in streamconsumer > Release Notes - Plexus Components - Version plexus-io-2.3 > ** Improvement > * [PLXCOMP-260] - Make plexus io collections iterable > ** New Feature > * [PLXCOMP-261] - Make plexus io collections support on-the-fly filtering > Release Notes - Plexus Components - Version plexus-io-2.2 > ** Bug > * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale > dependencies > * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are > used > Release Notes - Plexus Components - Version plexus-io-2.1.4 > ** Bug > * [PLXCOMP-107] - Fail to unzip archive, which contains file with name > 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . > Release Notes - Plexus Components - Version plexus-io-2.1.3 > * [PLXCOMP-247] - Bug with windows AND java5 > Release Notes - Plexus Components - Version plexus-io-2.1.2 > * [PLXCOMP-244] - Don't try to set attributes of symbolic links > * [PLXCOMP-245] - Archives created on windows get zero permissions, > creates malformed permissions on linux > Release Notes - Plexus Components - Version plexus-io-2.1.1 > ** Bug > * [PLXCOMP-243] - Restore JDK1.5 compatibility > Release Notes - Plexus Components - Version plexus-io-2.0.12 > * [PLXCOMP-249] - Add support for java7 chmod > Release Notes - Plexus Components - Version plexus-io-2.0.10 > * [PLXCOMP-228] -
[jira] (MASSEMBLY-716) Update plexus-io from 2.0.9 to 2.3.1
[ https://jira.codehaus.org/browse/MASSEMBLY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MASSEMBLY-716: - Description: Release Notes - Plexus Components - Version plexus-io-2.2 ** Bug * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale dependencies * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are used Release Notes - Plexus Components - Version plexus-io-2.1.4 ** Bug * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . Release Notes - Plexus Components - Version plexus-io-2.1.3 * [PLXCOMP-247] - Bug with windows AND java5 Release Notes - Plexus Components - Version plexus-io-2.1.2 * [PLXCOMP-244] - Don't try to set attributes of symbolic links * [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux Release Notes - Plexus Components - Version plexus-io-2.1.1 ** Bug * [PLXCOMP-243] - Restore JDK1.5 compatibility Release Notes - Plexus Components - Version plexus-io-2.0.12 * [PLXCOMP-249] - Add support for java7 chmod Release Notes - Plexus Components - Version plexus-io-2.0.10 * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled was: Release Notes - Plexus Components - Version plexus-io-2.2 ** Bug * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale dependencies * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are used Release Notes - Plexus Components - Version plexus-io-2.1.4 ** Bug * [PLXCOMP-107] - Fail to unzip archive, which contains file with name 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . Release Notes - Plexus Components - Version plexus-io-2.1.3 * [PLXCOMP-247] - Bug with windows AND java5 Release Notes - Plexus Components - Version plexus-io-2.1.2 * [PLXCOMP-244] - Don't try to set attributes of symbolic links * [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux Release Notes - Plexus Components - Version plexus-io-2.1.1 ** Bug * [PLXCOMP-243] - Restore JDK1.5 compatibility Release Notes - Plexus Components - Version plexus-io-2.0.12 * [PLXCOMP-249] - Add support for java7 chmod Release Notes - Plexus Components - Version plexus-io-2.0.10 * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled Summary: Update plexus-io from 2.0.9 to 2.3.1 (was: Update plexus-io from 2.0.9 to 2.2) > Update plexus-io from 2.0.9 to 2.3.1 > > > Key: MASSEMBLY-716 > URL: https://jira.codehaus.org/browse/MASSEMBLY-716 > Project: Maven Assembly Plugin > Issue Type: Improvement >Reporter: Kristian Rosenvold >Assignee: Kristian Rosenvold > Fix For: 2.5 > > > Release Notes - Plexus Components - Version plexus-io-2.2 > ** Bug > * [PLXCOMP-251] - Date parsing in "ls" screenscraping has locale > dependencies > * [PLXCOMP-254] - Fix File.separatorChar normalization when prefixes are > used > Release Notes - Plexus Components - Version plexus-io-2.1.4 > ** Bug > * [PLXCOMP-107] - Fail to unzip archive, which contains file with name > 'How_can_I_annotate_a_part_in_the_AAM%3F.Help' . > Release Notes - Plexus Components - Version plexus-io-2.1.3 > * [PLXCOMP-247] - Bug with windows AND java5 > Release Notes - Plexus Components - Version plexus-io-2.1.2 > * [PLXCOMP-244] - Don't try to set attributes of symbolic links > * [PLXCOMP-245] - Archives created on windows get zero permissions, > creates malformed permissions on linux > Release Notes - Plexus Components - Version plexus-io-2.1.1 > ** Bug > * [PLXCOMP-243] - Restore JDK1.5 compatibility > Release Notes - Plexus Components - Version plexus-io-2.0.12 > * [PLXCOMP-249] - Add support for java7 chmod > Release Notes - Plexus Components - Version plexus-io-2.0.10 > * [PLXCOMP-228] - PlexusIoFileResource lastModified fix was bungled -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5705) NPE on parallel build in BuilderCommon.handleBuildError(BuilderCommon.java:147)
[
https://jira.codehaus.org/browse/MNG-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondrej Zizka updated MNG-5705:
--
Description:
STR:
{code}
git clone g...@github.com:OndraZizka/windup.git
cd windup
git checkout 91a454b # MavenNPE2
mvn -T 1C clean javadoc:aggregate -PjavadocDist
{code}
{code}
[INFO]
[INFO] Windup Parent . SUCCESS [ 0.132 s]
[INFO] Windup Engine - Frames SUCCESS [ 0.009 s]
[INFO] Windup Engine - Utils . SUCCESS [ 0.035 s]
[INFO] Windup Engine - Graph Parent .. SUCCESS [ 0.004 s]
[INFO] Windup Engine - Graph API . FAILURE [ 0.003 s]
[INFO] Windup Engine - Graph Impl SKIPPED
[INFO] Windup Engine - Graph Addon ... SKIPPED
[INFO] Windup Engine - Graph Tests ... SKIPPED
[INFO] Windup Engine - Config Parent . SUCCESS [ 0.008 s]
[INFO] Windup Engine - Config API SKIPPED
[INFO] Windup Engine - Config Impl ... SKIPPED
[INFO] Windup Engine - Config Addon .. SKIPPED
[INFO] Windup Engine - Decompiler SUCCESS [ 0.011 s]
[INFO] Windup Engine - Decompiler API SUCCESS [ 0.039 s]
[INFO] Windup Engine - Decompiler Procyon SKIPPED
[INFO] Windup Extension - Config - XML ... SKIPPED
[INFO] Windup Engine - Reporting Parent .. SUCCESS [ 0.016 s]
[INFO] Windup Engine - Reporting API . SKIPPED
[INFO] Windup Engine - Reporting Impl SKIPPED
[INFO] Windup Engine - Reporting Addon ... SKIPPED
[INFO] Windup Engine - Execution API Parent .. SUCCESS [ 0.003 s]
[INFO] Windup Engine - Execution API . SKIPPED
[INFO] Windup Engine - Execution API Impl SKIPPED
[INFO] Windup Engine - Execution API Addon ... SKIPPED
[INFO] Windup Rules - XML - Basic SKIPPED
[INFO] Windup Extension - Config - Groovy SKIPPED
[INFO] Windup Rules - Java - Basic ... SKIPPED
[INFO] Windup Engine - Config Tests .. SKIPPED
[INFO] Windup Rules - Java EE - Basic SKIPPED
[INFO] Windup Engine - Execution API Tests ... SKIPPED
[INFO] Windup Engine - Reporting Tests ... SKIPPED
[INFO] Windup Engine - UI SKIPPED
[INFO] Windup Engine - Test Utilities SUCCESS [ 0.004 s]
[INFO] Windup Engine - Tests . SKIPPED
[INFO] Windup - Bootstrap module . SUCCESS [ 0.002 s]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ decompiler-api ---
[INFO] Windup - Distribution Build ... FAILURE [ 0.008 s]
[INFO] Windup Rulesets BOM ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.721 s (Wall Clock)
[INFO] Finished at: 2014-10-22T16:39:30+01:00
[INFO] Final Memory: 21M/211M
[INFO]
[ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at
org.apache.maven.lifecycle.internal.builder.BuilderCommon.handleBuildError(BuilderCommon.java:147)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:121)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at
org.apache.maven.execution.MavenSession.getPluginContext(MavenSession.java:314)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:504)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:12
[jira] (MNG-5705) NPE on parallel build in BuilderCommon.handleBuildError(BuilderCommon.java:147)
[
https://jira.codehaus.org/browse/MNG-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondrej Zizka updated MNG-5705:
--
Summary: NPE on parallel build in
BuilderCommon.handleBuildError(BuilderCommon.java:147) (was: NPE in
BuilderCommon.handleBuildError(BuilderCommon.java:147))
> NPE on parallel build in
> BuilderCommon.handleBuildError(BuilderCommon.java:147)
> ---
>
> Key: MNG-5705
> URL: https://jira.codehaus.org/browse/MNG-5705
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.2.1
>Reporter: Ondrej Zizka
>
> STR:
> {code}
> git clone g...@github.com:windup/windup.git
> cd windup
> git checkout 91a454b # MavenNPE2
> mvn -T 1C clean javadoc:aggregate -PjavadocDist
> {code}
> {code}
> [INFO]
>
> [INFO] Windup Parent . SUCCESS [ 0.132 s]
> [INFO] Windup Engine - Frames SUCCESS [ 0.009 s]
> [INFO] Windup Engine - Utils . SUCCESS [ 0.035 s]
> [INFO] Windup Engine - Graph Parent .. SUCCESS [ 0.004 s]
> [INFO] Windup Engine - Graph API . FAILURE [ 0.003 s]
> [INFO] Windup Engine - Graph Impl SKIPPED
> [INFO] Windup Engine - Graph Addon ... SKIPPED
> [INFO] Windup Engine - Graph Tests ... SKIPPED
> [INFO] Windup Engine - Config Parent . SUCCESS [ 0.008 s]
> [INFO] Windup Engine - Config API SKIPPED
> [INFO] Windup Engine - Config Impl ... SKIPPED
> [INFO] Windup Engine - Config Addon .. SKIPPED
> [INFO] Windup Engine - Decompiler SUCCESS [ 0.011 s]
> [INFO] Windup Engine - Decompiler API SUCCESS [ 0.039 s]
> [INFO] Windup Engine - Decompiler Procyon SKIPPED
> [INFO] Windup Extension - Config - XML ... SKIPPED
> [INFO] Windup Engine - Reporting Parent .. SUCCESS [ 0.016 s]
> [INFO] Windup Engine - Reporting API . SKIPPED
> [INFO] Windup Engine - Reporting Impl SKIPPED
> [INFO] Windup Engine - Reporting Addon ... SKIPPED
> [INFO] Windup Engine - Execution API Parent .. SUCCESS [ 0.003 s]
> [INFO] Windup Engine - Execution API . SKIPPED
> [INFO] Windup Engine - Execution API Impl SKIPPED
> [INFO] Windup Engine - Execution API Addon ... SKIPPED
> [INFO] Windup Rules - XML - Basic SKIPPED
> [INFO] Windup Extension - Config - Groovy SKIPPED
> [INFO] Windup Rules - Java - Basic ... SKIPPED
> [INFO] Windup Engine - Config Tests .. SKIPPED
> [INFO] Windup Rules - Java EE - Basic SKIPPED
> [INFO] Windup Engine - Execution API Tests ... SKIPPED
> [INFO] Windup Engine - Reporting Tests ... SKIPPED
> [INFO] Windup Engine - UI SKIPPED
> [INFO] Windup Engine - Test Utilities SUCCESS [ 0.004 s]
> [INFO] Windup Engine - Tests . SKIPPED
> [INFO] Windup - Bootstrap module . SUCCESS [ 0.002 s]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ decompiler-api ---
> [INFO] Windup - Distribution Build ... FAILURE [ 0.008 s]
> [INFO] Windup Rulesets BOM ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.721 s (Wall Clock)
> [INFO] Finished at: 2014-10-22T16:39:30+01:00
> [INFO] Final Memory: 21M/211M
> [INFO]
>
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.internal.builder.BuilderCommon.handleBuildError(BuilderCommon.java:147)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:121)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurre
[jira] (MNG-5705) NPE in BuilderCommon.handleBuildError(BuilderCommon.java:147)
[
https://jira.codehaus.org/browse/MNG-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondrej Zizka updated MNG-5705:
--
Affects Version/s: 3.2.1
> NPE in BuilderCommon.handleBuildError(BuilderCommon.java:147)
> -
>
> Key: MNG-5705
> URL: https://jira.codehaus.org/browse/MNG-5705
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.2.1
>Reporter: Ondrej Zizka
>
> STR:
> {code}
> git clone g...@github.com:windup/windup.git
> cd windup
> git checkout 91a454b # MavenNPE2
> mvn -T 1C clean javadoc:aggregate -PjavadocDist
> {code}
> {code}
> [INFO]
>
> [INFO] Windup Parent . SUCCESS [ 0.132 s]
> [INFO] Windup Engine - Frames SUCCESS [ 0.009 s]
> [INFO] Windup Engine - Utils . SUCCESS [ 0.035 s]
> [INFO] Windup Engine - Graph Parent .. SUCCESS [ 0.004 s]
> [INFO] Windup Engine - Graph API . FAILURE [ 0.003 s]
> [INFO] Windup Engine - Graph Impl SKIPPED
> [INFO] Windup Engine - Graph Addon ... SKIPPED
> [INFO] Windup Engine - Graph Tests ... SKIPPED
> [INFO] Windup Engine - Config Parent . SUCCESS [ 0.008 s]
> [INFO] Windup Engine - Config API SKIPPED
> [INFO] Windup Engine - Config Impl ... SKIPPED
> [INFO] Windup Engine - Config Addon .. SKIPPED
> [INFO] Windup Engine - Decompiler SUCCESS [ 0.011 s]
> [INFO] Windup Engine - Decompiler API SUCCESS [ 0.039 s]
> [INFO] Windup Engine - Decompiler Procyon SKIPPED
> [INFO] Windup Extension - Config - XML ... SKIPPED
> [INFO] Windup Engine - Reporting Parent .. SUCCESS [ 0.016 s]
> [INFO] Windup Engine - Reporting API . SKIPPED
> [INFO] Windup Engine - Reporting Impl SKIPPED
> [INFO] Windup Engine - Reporting Addon ... SKIPPED
> [INFO] Windup Engine - Execution API Parent .. SUCCESS [ 0.003 s]
> [INFO] Windup Engine - Execution API . SKIPPED
> [INFO] Windup Engine - Execution API Impl SKIPPED
> [INFO] Windup Engine - Execution API Addon ... SKIPPED
> [INFO] Windup Rules - XML - Basic SKIPPED
> [INFO] Windup Extension - Config - Groovy SKIPPED
> [INFO] Windup Rules - Java - Basic ... SKIPPED
> [INFO] Windup Engine - Config Tests .. SKIPPED
> [INFO] Windup Rules - Java EE - Basic SKIPPED
> [INFO] Windup Engine - Execution API Tests ... SKIPPED
> [INFO] Windup Engine - Reporting Tests ... SKIPPED
> [INFO] Windup Engine - UI SKIPPED
> [INFO] Windup Engine - Test Utilities SUCCESS [ 0.004 s]
> [INFO] Windup Engine - Tests . SKIPPED
> [INFO] Windup - Bootstrap module . SUCCESS [ 0.002 s]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ decompiler-api ---
> [INFO] Windup - Distribution Build ... FAILURE [ 0.008 s]
> [INFO] Windup Rulesets BOM ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.721 s (Wall Clock)
> [INFO] Finished at: 2014-10-22T16:39:30+01:00
> [INFO] Final Memory: 21M/211M
> [INFO]
>
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.internal.builder.BuilderCommon.handleBuildError(BuilderCommon.java:147)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:121)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExec
[jira] (MNG-5705) NPE in BuilderCommon.handleBuildError(BuilderCommon.java:147)
[
https://jira.codehaus.org/browse/MNG-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondrej Zizka updated MNG-5705:
--
Component/s: Bootstrap & Build
> NPE in BuilderCommon.handleBuildError(BuilderCommon.java:147)
> -
>
> Key: MNG-5705
> URL: https://jira.codehaus.org/browse/MNG-5705
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.2.1
>Reporter: Ondrej Zizka
>
> STR:
> {code}
> git clone g...@github.com:windup/windup.git
> cd windup
> git checkout 91a454b # MavenNPE2
> mvn -T 1C clean javadoc:aggregate -PjavadocDist
> {code}
> {code}
> [INFO]
>
> [INFO] Windup Parent . SUCCESS [ 0.132 s]
> [INFO] Windup Engine - Frames SUCCESS [ 0.009 s]
> [INFO] Windup Engine - Utils . SUCCESS [ 0.035 s]
> [INFO] Windup Engine - Graph Parent .. SUCCESS [ 0.004 s]
> [INFO] Windup Engine - Graph API . FAILURE [ 0.003 s]
> [INFO] Windup Engine - Graph Impl SKIPPED
> [INFO] Windup Engine - Graph Addon ... SKIPPED
> [INFO] Windup Engine - Graph Tests ... SKIPPED
> [INFO] Windup Engine - Config Parent . SUCCESS [ 0.008 s]
> [INFO] Windup Engine - Config API SKIPPED
> [INFO] Windup Engine - Config Impl ... SKIPPED
> [INFO] Windup Engine - Config Addon .. SKIPPED
> [INFO] Windup Engine - Decompiler SUCCESS [ 0.011 s]
> [INFO] Windup Engine - Decompiler API SUCCESS [ 0.039 s]
> [INFO] Windup Engine - Decompiler Procyon SKIPPED
> [INFO] Windup Extension - Config - XML ... SKIPPED
> [INFO] Windup Engine - Reporting Parent .. SUCCESS [ 0.016 s]
> [INFO] Windup Engine - Reporting API . SKIPPED
> [INFO] Windup Engine - Reporting Impl SKIPPED
> [INFO] Windup Engine - Reporting Addon ... SKIPPED
> [INFO] Windup Engine - Execution API Parent .. SUCCESS [ 0.003 s]
> [INFO] Windup Engine - Execution API . SKIPPED
> [INFO] Windup Engine - Execution API Impl SKIPPED
> [INFO] Windup Engine - Execution API Addon ... SKIPPED
> [INFO] Windup Rules - XML - Basic SKIPPED
> [INFO] Windup Extension - Config - Groovy SKIPPED
> [INFO] Windup Rules - Java - Basic ... SKIPPED
> [INFO] Windup Engine - Config Tests .. SKIPPED
> [INFO] Windup Rules - Java EE - Basic SKIPPED
> [INFO] Windup Engine - Execution API Tests ... SKIPPED
> [INFO] Windup Engine - Reporting Tests ... SKIPPED
> [INFO] Windup Engine - UI SKIPPED
> [INFO] Windup Engine - Test Utilities SUCCESS [ 0.004 s]
> [INFO] Windup Engine - Tests . SKIPPED
> [INFO] Windup - Bootstrap module . SUCCESS [ 0.002 s]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ decompiler-api ---
> [INFO] Windup - Distribution Build ... FAILURE [ 0.008 s]
> [INFO] Windup Rulesets BOM ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.721 s (Wall Clock)
> [INFO] Finished at: 2014-10-22T16:39:30+01:00
> [INFO] Final Memory: 21M/211M
> [INFO]
>
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.internal.builder.BuilderCommon.handleBuildError(BuilderCommon.java:147)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:121)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPo
[jira] (MNG-5705) NPE in BuilderCommon.handleBuildError(BuilderCommon.java:147)
Ondrej Zizka created MNG-5705:
-
Summary: NPE in
BuilderCommon.handleBuildError(BuilderCommon.java:147)
Key: MNG-5705
URL: https://jira.codehaus.org/browse/MNG-5705
Project: Maven
Issue Type: Bug
Reporter: Ondrej Zizka
STR:
{code}
git clone g...@github.com:windup/windup.git
cd windup
git checkout 91a454b # MavenNPE2
mvn -T 1C clean javadoc:aggregate -PjavadocDist
{code}
{code}
[INFO]
[INFO] Windup Parent . SUCCESS [ 0.132 s]
[INFO] Windup Engine - Frames SUCCESS [ 0.009 s]
[INFO] Windup Engine - Utils . SUCCESS [ 0.035 s]
[INFO] Windup Engine - Graph Parent .. SUCCESS [ 0.004 s]
[INFO] Windup Engine - Graph API . FAILURE [ 0.003 s]
[INFO] Windup Engine - Graph Impl SKIPPED
[INFO] Windup Engine - Graph Addon ... SKIPPED
[INFO] Windup Engine - Graph Tests ... SKIPPED
[INFO] Windup Engine - Config Parent . SUCCESS [ 0.008 s]
[INFO] Windup Engine - Config API SKIPPED
[INFO] Windup Engine - Config Impl ... SKIPPED
[INFO] Windup Engine - Config Addon .. SKIPPED
[INFO] Windup Engine - Decompiler SUCCESS [ 0.011 s]
[INFO] Windup Engine - Decompiler API SUCCESS [ 0.039 s]
[INFO] Windup Engine - Decompiler Procyon SKIPPED
[INFO] Windup Extension - Config - XML ... SKIPPED
[INFO] Windup Engine - Reporting Parent .. SUCCESS [ 0.016 s]
[INFO] Windup Engine - Reporting API . SKIPPED
[INFO] Windup Engine - Reporting Impl SKIPPED
[INFO] Windup Engine - Reporting Addon ... SKIPPED
[INFO] Windup Engine - Execution API Parent .. SUCCESS [ 0.003 s]
[INFO] Windup Engine - Execution API . SKIPPED
[INFO] Windup Engine - Execution API Impl SKIPPED
[INFO] Windup Engine - Execution API Addon ... SKIPPED
[INFO] Windup Rules - XML - Basic SKIPPED
[INFO] Windup Extension - Config - Groovy SKIPPED
[INFO] Windup Rules - Java - Basic ... SKIPPED
[INFO] Windup Engine - Config Tests .. SKIPPED
[INFO] Windup Rules - Java EE - Basic SKIPPED
[INFO] Windup Engine - Execution API Tests ... SKIPPED
[INFO] Windup Engine - Reporting Tests ... SKIPPED
[INFO] Windup Engine - UI SKIPPED
[INFO] Windup Engine - Test Utilities SUCCESS [ 0.004 s]
[INFO] Windup Engine - Tests . SKIPPED
[INFO] Windup - Bootstrap module . SUCCESS [ 0.002 s]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ decompiler-api ---
[INFO] Windup - Distribution Build ... FAILURE [ 0.008 s]
[INFO] Windup Rulesets BOM ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.721 s (Wall Clock)
[INFO] Finished at: 2014-10-22T16:39:30+01:00
[INFO] Final Memory: 21M/211M
[INFO]
[ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at
org.apache.maven.lifecycle.internal.builder.BuilderCommon.handleBuildError(BuilderCommon.java:147)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:121)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at
org.apache.maven.execution.MavenSession.getPluginContext(MavenSession.java:314)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMaven
[jira] (SUREFIRE-1071) LinkageError org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil
[ https://jira.codehaus.org/browse/SUREFIRE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1071: --- Fix Version/s: (was: 2.18) > LinkageError > org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil > > > Key: SUREFIRE-1071 > URL: https://jira.codehaus.org/browse/SUREFIRE-1071 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.16 > Environment: Maven 3.1.1 and Maven 3.2.1 >Reporter: Julian Payne >Priority: Blocker > > Every so often when I am running the unit tests on a standard Maven project I > get a linkage error: > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ > asf-maven- > plugin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ > asf-maven-plugi > n --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ > as > f-maven-plugin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > d:\rtc-workspace-asf-10\asf-build-sys > tem\maven-plugins\asf-maven-plugin\src\test-resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ > asf-mav > en-plugin --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.16:test (default-test) @ asf-maven-plugin > --- > [INFO] Surefire report directory: > d:\rtc-workspace-asf-10\asf-build-system\maven > -plugins\asf-maven-plugin\target\surefire-reports > --- > T E S T S > --- > Exception in thread "Thread-7" java.lang.LinkageError: > org.apache.maven.surefire > .shade.org.apache.maven.shared.utils.io.IOUtil > at java.lang.ClassLoader.defineClassImpl(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:306) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14 > 3) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:700) > at java.net.URLClassLoader.access$400(URLClassLoader.java:81) > at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1148) > at > java.security.AccessController.doPrivileged(AccessController.java:366 > ) > at java.net.URLClassLoader.findClass(URLClassLoader.java:583) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(Cl > assRealm.java:389) > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass( > SelfFirstStrategy.java:42) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCl > ass(ClassRealm.java:259) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm > .java:235) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm > .java:227) > at > org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.Str > eamPumper.run(StreamPumper.java:95) > Terminate batch job (Y/N)? y > This error is not reproducible but I am getting it from time to time when > running maven on the command line as well as in my Jenkins jobs that are > running Maven jobs. > When this LinkageError occurs the maven run blocks. > This is what I have in the effective pom for the run above that blocked: > > maven-surefire-plugin > 2.16 > true > > -Xms768m -Xmx768m > true > false > > > org.dom4j:dom4j > > > > Thanks, > Julian Payne -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1071) LinkageError org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil
[ https://jira.codehaus.org/browse/SUREFIRE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1071: --- Fix Version/s: 2.18 > LinkageError > org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil > > > Key: SUREFIRE-1071 > URL: https://jira.codehaus.org/browse/SUREFIRE-1071 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.16 > Environment: Maven 3.1.1 and Maven 3.2.1 >Reporter: Julian Payne >Priority: Blocker > Fix For: 2.18 > > > Every so often when I am running the unit tests on a standard Maven project I > get a linkage error: > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ > asf-maven- > plugin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ > asf-maven-plugi > n --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ > as > f-maven-plugin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > d:\rtc-workspace-asf-10\asf-build-sys > tem\maven-plugins\asf-maven-plugin\src\test-resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ > asf-mav > en-plugin --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.16:test (default-test) @ asf-maven-plugin > --- > [INFO] Surefire report directory: > d:\rtc-workspace-asf-10\asf-build-system\maven > -plugins\asf-maven-plugin\target\surefire-reports > --- > T E S T S > --- > Exception in thread "Thread-7" java.lang.LinkageError: > org.apache.maven.surefire > .shade.org.apache.maven.shared.utils.io.IOUtil > at java.lang.ClassLoader.defineClassImpl(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:306) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14 > 3) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:700) > at java.net.URLClassLoader.access$400(URLClassLoader.java:81) > at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1148) > at > java.security.AccessController.doPrivileged(AccessController.java:366 > ) > at java.net.URLClassLoader.findClass(URLClassLoader.java:583) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(Cl > assRealm.java:389) > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass( > SelfFirstStrategy.java:42) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCl > ass(ClassRealm.java:259) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm > .java:235) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm > .java:227) > at > org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.Str > eamPumper.run(StreamPumper.java:95) > Terminate batch job (Y/N)? y > This error is not reproducible but I am getting it from time to time when > running maven on the command line as well as in my Jenkins jobs that are > running Maven jobs. > When this LinkageError occurs the maven run blocks. > This is what I have in the effective pom for the run above that blocked: > > maven-surefire-plugin > 2.16 > true > > -Xms768m -Xmx768m > true > false > > > org.dom4j:dom4j > > > > Thanks, > Julian Payne -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-963) Unable to set empty environment variables
[
https://jira.codehaus.org/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354766#comment-354766
]
Christophe DENEUX commented on SUREFIRE-963:
The maven-surefire-plugin:2.18-SNAPSHOT available in the Apache Snapshot
repository works fine about this issue.
When do you plan to release the version 2.18 ?
> Unable to set empty environment variables
> -
>
> Key: SUREFIRE-963
> URL: https://jira.codehaus.org/browse/SUREFIRE-963
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.13
> Environment: Linux Ubuntu 12.10,Maven 3.0.4
>Reporter: Christophe DENEUX
>Assignee: Tibor Digana
> Fix For: 2.18
>
> Attachments: SUREFIRE-963.txt
>
>
> With the following configuration of the maven-surefire-plugin:
> {code}
>
>
>
>
>
> {code}
> I get the String "null" instead of "" as value of my env var in my unit test.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-253) Upgrade to checkstyle 5.9 for Java 8 compatibility
[ https://jira.codehaus.org/browse/MCHECKSTYLE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354762#comment-354762 ] Sergei Ivanov commented on MCHECKSTYLE-253: --- Is 2.14 release planned any time soon? It would be great to have the latest checkstyle bundled with the plugin. Thanks. > Upgrade to checkstyle 5.9 for Java 8 compatibility > -- > > Key: MCHECKSTYLE-253 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-253 > Project: Maven Checkstyle Plugin > Issue Type: New Feature >Reporter: Zlika >Assignee: Mirko Friedenhagen > Fix For: 2.14 > > > Checkstyle 5.9 has just been released and adds support for Java 8. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-207) requirePluginVersions does not apply when plugin defined in parent or profile ?
[ https://jira.codehaus.org/browse/MENFORCER-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph closed MENFORCER-207. Resolution: Not A Bug H nevermind, this is me being stupid. Explanation for my misunderstanding: * The version-less plugin I had in my setup was bound to the clean phase. * Naturally, to try an detect the problem, I called for the clean phase and the profile where the plugin is bound (tried w/ and w/o profile) * The enforcer plugin, on the other hand is bound to the validate phase of the default lifecycle. * I only just realized that executing the clean lifecycle does _not_ execute the validate phase ! > requirePluginVersions does not apply when plugin defined in parent or profile > ? > --- > > Key: MENFORCER-207 > URL: https://jira.codehaus.org/browse/MENFORCER-207 > Project: Maven Enforcer Plugin > Issue Type: Bug >Affects Versions: 1.3.1 >Reporter: Grégory Joseph > > I see two cases where the rule doesn't seem to be applied: > * a version-less plugin is declared in a parent pom outside the current > reactor (for the sake of the exercise, the parent pom is released with > -Denforcer.skip) > * a version-less plugin is declared in a profile of the parent pom; the > profile is activated in the child pom. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MENFORCER-207) requirePluginVersions does not apply when plugin defined in parent or profile ?
Grégory Joseph created MENFORCER-207: Summary: requirePluginVersions does not apply when plugin defined in parent or profile ? Key: MENFORCER-207 URL: https://jira.codehaus.org/browse/MENFORCER-207 Project: Maven Enforcer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Grégory Joseph I see two cases where the rule doesn't seem to be applied: * a version-less plugin is declared in a parent pom outside the current reactor (for the sake of the exercise, the parent pom is released with -Denforcer.skip) * a version-less plugin is declared in a profile of the parent pom; the profile is activated in the child pom. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation
[
https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354753#comment-354753
]
Andrew Phillips commented on SUREFIRE-654:
--
Hi [~tibor17]:
Thanks for the hints! At this point, I am not able to investigate *why* exactly
the test case I attached is failing - I just wanted to point out that, for me
at least, the patch doesn't seem to be working.
I hope this will help whoever will review the patch determine whether it's
correct or not.
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation
> ---
>
> Key: SUREFIRE-654
> URL: https://jira.codehaus.org/browse/SUREFIRE-654
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.6
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0-18
> Java home: /usr/lib/jvm/java-6-openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
> Ubuntu 10.10
>Reporter: Steve Stodola
> Attachments: bugtest.tar.gz, surefire654.diff,
> surefire-fix-test-build-output.txt, surefire-fix-test.zip
>
>
> Surefire does not recognize successful tests using TestNG with the
> invocationCount and successPercentage parameters on the @Test annotation.
> BugTest.java in the attached file has an invocationCount = 100 with a
> successPercentage = 1. 1 test in 100 needs to pass for the test to be
> considered successful. However when running *{{mvn clean test}}* Surefire
> reports the tests as failed. The generated report shows the tests as passing.
> Surefire should be identifying this test as passing.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
