[jira] [Commented] (MDEP-484) NullPointerException when using tree goal with include parameter
[
https://issues.apache.org/jira/browse/MDEP-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536278#comment-14536278
]
Karl Heinz Marbaise commented on MDEP-484:
--
It looks like there is a problem on the file system:
I have found in the log files the following:
{code}
..
[DEBUG] Error releasing shared lock for resolution tracking file:
C:\Users\user\.m2\repository\com\sun\jai\jai-core\resolver-status.properties
..
{code}
which could be a symptom for virus checkers etc. which hold a lock on windows
systems...
furthermore i found in the Maven 2 log:
{code}
java.lang.NullPointerException: version was null for com.sun.jai:jai-codec
{code}
Apart from that i don't find the given dependency in any repository i have
access to...Can reproduce this with an artifact which exists in a repository so
i can try to reproduce this?
> NullPointerException when using tree goal with include parameter
>
>
> Key: MDEP-484
> URL: https://issues.apache.org/jira/browse/MDEP-484
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 2.10
>Reporter: Marvin Lütgenau
> Attachments: mdep484-m2.log, mdep484-m3.log, pom.xml
>
>
> The tree goal aborts with a NullPointerException when using the includes
> parameter, if there is any dependency to an artifact that uses a range
> version.
> Example call:
> mvn dependency:tree -Dverbose -Dincludes=:::*-SNAPSHOT
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MANTRUN-194) Incorrect handling of NUL username and group Tar.gz entries
[
https://issues.apache.org/jira/browse/MANTRUN-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536303#comment-14536303
]
Michael Osipov commented on MANTRUN-194:
This is not a bug in this plugin. This has to be fixed in Ant:
https://bz.apache.org/bugzilla/show_bug.cgi?id=56641
As soon as 1.9.5 is available add this to your dependencies section of the
plugin.
I am inclined to close this.
> Incorrect handling of NUL username and group Tar.gz entries
> ---
>
> Key: MANTRUN-194
> URL: https://issues.apache.org/jira/browse/MANTRUN-194
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Riccardo Sirchia
> Labels: close-pending
>
> This issue is most likely related to the issue described in COMPRESS-278
> When using version 1.8 of the maven-antrun-plugin to untar for example the
> artifact
> [apache-activemq-5.11.1-bin.tar.gz|http://search.maven.org/remotecontent?filepath=org/apache/activemq/apache-activemq/5.11.1/apache-activemq-5.11.1-bin.tar.gz]
> artifact from maven central, I get the following stacktrace:
> {code}
> java.io.IOException: Error detected parsing the header
> at org.apache.tools.ant.taskdefs.Untar.expandFile(Untar.java:116)
> at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:132)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:313)
> ... 21 more
> Caused by: java.io.IOException: Error detected parsing the header
> at
> org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:292)
> at org.apache.tools.ant.taskdefs.Untar.expandStream(Untar.java:165)
> at org.apache.tools.ant.taskdefs.Untar.expandFile(Untar.java:114)
> ... 34 more
> Caused by: java.lang.IllegalArgumentException: Invalid byte 32 at offset 7 in
> ' {NUL}' len=8
> at org.apache.tools.tar.TarUtils.parseOctal(TarUtils.java:134)
> at org.apache.tools.tar.TarUtils.parseOctalOrBinary(TarUtils.java:172)
> at org.apache.tools.tar.TarEntry.parseTarHeader(TarEntry.java:912)
> at org.apache.tools.tar.TarEntry.parseTarHeader(TarEntry.java:899)
> at org.apache.tools.tar.TarEntry.(TarEntry.java:323)
> at
> org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:290)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MANTRUN-194) Incorrect handling of NUL username and group Tar.gz entries
[
https://issues.apache.org/jira/browse/MANTRUN-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MANTRUN-194:
---
Labels: close-pending (was: )
> Incorrect handling of NUL username and group Tar.gz entries
> ---
>
> Key: MANTRUN-194
> URL: https://issues.apache.org/jira/browse/MANTRUN-194
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Riccardo Sirchia
> Labels: close-pending
>
> This issue is most likely related to the issue described in COMPRESS-278
> When using version 1.8 of the maven-antrun-plugin to untar for example the
> artifact
> [apache-activemq-5.11.1-bin.tar.gz|http://search.maven.org/remotecontent?filepath=org/apache/activemq/apache-activemq/5.11.1/apache-activemq-5.11.1-bin.tar.gz]
> artifact from maven central, I get the following stacktrace:
> {code}
> java.io.IOException: Error detected parsing the header
> at org.apache.tools.ant.taskdefs.Untar.expandFile(Untar.java:116)
> at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:132)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:313)
> ... 21 more
> Caused by: java.io.IOException: Error detected parsing the header
> at
> org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:292)
> at org.apache.tools.ant.taskdefs.Untar.expandStream(Untar.java:165)
> at org.apache.tools.ant.taskdefs.Untar.expandFile(Untar.java:114)
> ... 34 more
> Caused by: java.lang.IllegalArgumentException: Invalid byte 32 at offset 7 in
> ' {NUL}' len=8
> at org.apache.tools.tar.TarUtils.parseOctal(TarUtils.java:134)
> at org.apache.tools.tar.TarUtils.parseOctalOrBinary(TarUtils.java:172)
> at org.apache.tools.tar.TarEntry.parseTarHeader(TarEntry.java:912)
> at org.apache.tools.tar.TarEntry.parseTarHeader(TarEntry.java:899)
> at org.apache.tools.tar.TarEntry.(TarEntry.java:323)
> at
> org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:290)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SCM-795) scm output parsing is too aggressive on stderr
[ https://issues.apache.org/jira/browse/SCM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536337#comment-14536337 ] ASF GitHub Bot commented on SCM-795: GitHub user ChrisGWarp opened a pull request: https://github.com/apache/maven-scm/pull/34 [SCM-795] Fixed. Content on stderr will no longer raise an exception. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ChrisGWarp/maven-scm SCM-795 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-scm/pull/34.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #34 commit 2d7502077559d46f8009e45311b8ce5ab79f01bb Author: Chris Graham Date: 2015-05-09T10:06:36Z [SCM-795] Fixed. Content on stderr will no longer raise an exception. > scm output parsing is too aggressive on stderr > -- > > Key: SCM-795 > URL: https://issues.apache.org/jira/browse/SCM-795 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jazz >Affects Versions: 1.9.2 > Environment: All. >Reporter: Chris Graham >Assignee: Chris Graham > Fix For: 1.9.5 > > > In some versions of the jazz client (scm.exe), which is a wrapper for a > headless eclipse runtime, there are some additional lines output to stderr > (about a JobManager still running or similar) but the scm.exe return code is > zero. > The parsing code is being too aggressive as it detects stderr output and > assumes (incorrectly in this case) an error. The return code should take > priority over the stderr output (which really should be ignored). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SCM-795) scm output parsing is too aggressive on stderr
[ https://issues.apache.org/jira/browse/SCM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536348#comment-14536348 ] ASF GitHub Bot commented on SCM-795: Github user asfgit closed the pull request at: https://github.com/apache/maven-scm/pull/34 > scm output parsing is too aggressive on stderr > -- > > Key: SCM-795 > URL: https://issues.apache.org/jira/browse/SCM-795 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jazz >Affects Versions: 1.9.2 > Environment: All. >Reporter: Chris Graham >Assignee: Chris Graham > Fix For: 1.9.5 > > > In some versions of the jazz client (scm.exe), which is a wrapper for a > headless eclipse runtime, there are some additional lines output to stderr > (about a JobManager still running or similar) but the scm.exe return code is > zero. > The parsing code is being too aggressive as it detects stderr output and > assumes (incorrectly in this case) an error. The return code should take > priority over the stderr output (which really should be ignored). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SCM-795) scm output parsing is too aggressive on stderr
[ https://issues.apache.org/jira/browse/SCM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Graham resolved SCM-795. -- Resolution: Fixed > scm output parsing is too aggressive on stderr > -- > > Key: SCM-795 > URL: https://issues.apache.org/jira/browse/SCM-795 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jazz >Affects Versions: 1.9.2 > Environment: All. >Reporter: Chris Graham >Assignee: Chris Graham > Fix For: 1.9.5 > > > In some versions of the jazz client (scm.exe), which is a wrapper for a > headless eclipse runtime, there are some additional lines output to stderr > (about a JobManager still running or similar) but the scm.exe return code is > zero. > The parsing code is being too aggressive as it detects stderr output and > assumes (incorrectly in this case) an error. The return code should take > priority over the stderr output (which really should be ignored). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SCM-775) Add workItem and changeset associate support for scm deliver
[
https://issues.apache.org/jira/browse/SCM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Graham resolved SCM-775.
--
Resolution: Fixed
> Add workItem and changeset associate support for scm deliver
>
>
> Key: SCM-775
> URL: https://issues.apache.org/jira/browse/SCM-775
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-jazz
>Affects Versions: 1.9.1
>Reporter: AShit Shah
>Assignee: Chris Graham
> Fix For: 1.9.5
>
>
> 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.3.4#6332)
[jira] [Resolved] (MRELEASE-909) Add workItem/task support for scm deliver
[ https://issues.apache.org/jira/browse/MRELEASE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Graham resolved MRELEASE-909. --- Resolution: Fixed > Add workItem/task support for scm deliver > - > > Key: MRELEASE-909 > URL: https://issues.apache.org/jira/browse/MRELEASE-909 > Project: Maven Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.5.2 >Reporter: Chris Graham >Assignee: Chris Graham > Labels: patch > Attachments: Release-SCM-775.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Some SCMs (Jazz(RTC)/TFS/ClearCase etc) can support a mode where a workItem > or Task is required to be associated with changesets for a delivery operation > to work. > The SCM-775 has the necessary work to support this feature (with the Jazz > provider as a starting point). This issue is the complimentary issue; the > changes in the release plugin needed to support calling the scm apis with > workItem support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-909) Add workItem/task support for scm deliver
[ https://issues.apache.org/jira/browse/MRELEASE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536617#comment-14536617 ] Robert Scholte commented on MRELEASE-909: - Hi Chris, could you add the revision containing the main change? It should be as easy as: Fixed in [r1677765|http://svn.apache.org/r1677765] Above will create a link in Jira. The URL can be retrieved from the commits@m.a.o mailinglist. This gives a faster way to find the commit when going through the Jira issues. thanks, Robert Op Sat, 09 May 2015 14:03:59 +0200 schreef Chris Graham (JIRA) > Add workItem/task support for scm deliver > - > > Key: MRELEASE-909 > URL: https://issues.apache.org/jira/browse/MRELEASE-909 > Project: Maven Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.5.2 >Reporter: Chris Graham >Assignee: Chris Graham > Labels: patch > Attachments: Release-SCM-775.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Some SCMs (Jazz(RTC)/TFS/ClearCase etc) can support a mode where a workItem > or Task is required to be associated with changesets for a delivery operation > to work. > The SCM-775 has the necessary work to support this feature (with the Jazz > provider as a starting point). This issue is the complimentary issue; the > changes in the release plugin needed to support calling the scm apis with > workItem support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSKINS-116) use font icons bundled with bootstrap
[ https://issues.apache.org/jira/browse/MSKINS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536792#comment-14536792 ] jieryn commented on MSKINS-116: --- use glyphicons found in bootstrap, they are nice -- start using new ones where they fit, and replace the clunky old and busted ones used in almost all maven reports > use font icons bundled with bootstrap > - > > Key: MSKINS-116 > URL: https://issues.apache.org/jira/browse/MSKINS-116 > Project: Maven Skins > Issue Type: Wish > Components: Fluido Skin >Affects Versions: fluido-1.4 >Reporter: jieryn >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MASSEMBLY-767) Schema missing from the web site
Benson Margulies created MASSEMBLY-767: -- Summary: Schema missing from the web site Key: MASSEMBLY-767 URL: https://issues.apache.org/jira/browse/MASSEMBLY-767 Project: Maven Assembly Plugin Issue Type: Bug Reporter: Benson Margulies http://maven.apache.org/xsd/assembly-1.1.3.xsd isn't there. It should be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSKINS-116) use font icons bundled with bootstrap
[ https://issues.apache.org/jira/browse/MSKINS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536932#comment-14536932 ] Michael Osipov commented on MSKINS-116: --- Are they available in Bootstrap 3 only? > use font icons bundled with bootstrap > - > > Key: MSKINS-116 > URL: https://issues.apache.org/jira/browse/MSKINS-116 > Project: Maven Skins > Issue Type: Wish > Components: Fluido Skin >Affects Versions: fluido-1.4 >Reporter: jieryn >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-909) Add workItem/task support for scm deliver
[ https://issues.apache.org/jira/browse/MRELEASE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536983#comment-14536983 ] Chris Graham commented on MRELEASE-909: --- Oh, ok. Good idea. I just closed it from Jira. I'll add a comment to the issue. Thanks for the tip! -Chris Sent from my iPhone > Add workItem/task support for scm deliver > - > > Key: MRELEASE-909 > URL: https://issues.apache.org/jira/browse/MRELEASE-909 > Project: Maven Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.5.2 >Reporter: Chris Graham >Assignee: Chris Graham > Labels: patch > Attachments: Release-SCM-775.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Some SCMs (Jazz(RTC)/TFS/ClearCase etc) can support a mode where a workItem > or Task is required to be associated with changesets for a delivery operation > to work. > The SCM-775 has the necessary work to support this feature (with the Jazz > provider as a starting point). This issue is the complimentary issue; the > changes in the release plugin needed to support calling the scm apis with > workItem support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHADE-190) Shade does not relocate the contents of META-INF/services files
Benson Margulies created MSHADE-190: --- Summary: Shade does not relocate the contents of META-INF/services files Key: MSHADE-190 URL: https://issues.apache.org/jira/browse/MSHADE-190 Project: Maven Shade Plugin Issue Type: Bug Reporter: Benson Margulies If a META-INF/services/xxx file contains the name of a relocated class, the maven-shade-plugin does not rewrite the file to reflect the renamed class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-909) Add workItem/task support for scm deliver
[ https://issues.apache.org/jira/browse/MRELEASE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537000#comment-14537000 ] Chris Graham commented on MRELEASE-909: --- Fixed in r1677765. (I didn't know that we'd linked in email responses either...) > Add workItem/task support for scm deliver > - > > Key: MRELEASE-909 > URL: https://issues.apache.org/jira/browse/MRELEASE-909 > Project: Maven Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.5.2 >Reporter: Chris Graham >Assignee: Chris Graham > Labels: patch > Attachments: Release-SCM-775.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Some SCMs (Jazz(RTC)/TFS/ClearCase etc) can support a mode where a workItem > or Task is required to be associated with changesets for a delivery operation > to work. > The SCM-775 has the necessary work to support this feature (with the Jazz > provider as a starting point). This issue is the complimentary issue; the > changes in the release plugin needed to support calling the scm apis with > workItem support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MRELEASE-909) Add workItem/task support for scm deliver
[ https://issues.apache.org/jira/browse/MRELEASE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537000#comment-14537000 ] Chris Graham edited comment on MRELEASE-909 at 5/10/15 2:37 AM: Fixed in [r1677765|http://svn.apache.org/viewvc?view=revision&revision=1677765]. (I didn't know that we'd linked in email responses either...) was (Author: chrisgwarp): Fixed in r1677765. (I didn't know that we'd linked in email responses either...) > Add workItem/task support for scm deliver > - > > Key: MRELEASE-909 > URL: https://issues.apache.org/jira/browse/MRELEASE-909 > Project: Maven Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.5.2 >Reporter: Chris Graham >Assignee: Chris Graham > Labels: patch > Attachments: Release-SCM-775.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Some SCMs (Jazz(RTC)/TFS/ClearCase etc) can support a mode where a workItem > or Task is required to be associated with changesets for a delivery operation > to work. > The SCM-775 has the necessary work to support this feature (with the Jazz > provider as a starting point). This issue is the complimentary issue; the > changes in the release plugin needed to support calling the scm apis with > workItem support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
