[jira] Created: (MSHADE-94) NullPointerException on empty relocation pattern (default package)
NullPointerException on empty relocation pattern (default package)
--
Key: MSHADE-94
URL: http://jira.codehaus.org/browse/MSHADE-94
Project: Maven 2.x Shade Plugin
Issue Type: Bug
Affects Versions: 1.4
Reporter: J@ck
I need a few classes from a 3rd party jar that are declared in the default
package. Since usage of the default package should be avoided, I try to
relocate the classes to a named package:
{code:title=pom.xml}
...
org.example.foo.bar
{code}
The Shade Plugin crashes with a NPE:
{code:title=Stacktrace}
Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
shaded jar: null
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:503)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.NullPointerException
at
org.apache.maven.plugins.shade.relocation.SimpleRelocator.(SimpleRelocator.java:52)
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.getRelocators(ShadeMojo.java:616)
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:440)
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-285) regression: duplicate files added to the assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255752#action_255752 ] Andreas Pieber commented on MASSEMBLY-285: -- Please reopen this issue. I've the same problems as Daniel thanks > regression: duplicate files added to the assembly > - > > Key: MASSEMBLY-285 > URL: http://jira.codehaus.org/browse/MASSEMBLY-285 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 >Reporter: Brett Porter >Assignee: John Casey >Priority: Blocker > Fix For: 2.2-beta-3 > > > I found that it was possible to add a file twice to the assembly through > different filesets (a zip file) so that when it extracted it prompted for > overwrite. > It should error out or collapse the entries (as 2.1 did). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-220) IOException: Failed to open file During Site generation
[
http://jira.codehaus.org/browse/MPIR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255742#action_255742
]
Ian Brandt commented on MPIR-220:
-
Same here:
java version "1.5.0_26"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_26-b03-376-10M3261)
Java HotSpot(TM) Client VM (build 1.5.0_26-156, mixed mode, sharing)
Apache Maven 3.0.2 (r1056850; 2011-01-08 16:58:10-0800)
Java version: 1.5.0_26, vendor: Apple Inc.
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.6", arch: "i386", family: "unix"
> IOException: Failed to open file During Site generation
> ---
>
> Key: MPIR-220
> URL: http://jira.codehaus.org/browse/MPIR-220
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.3.1
> Environment: Linux (Ubuntu)
> java -version
> java version "1.6.0_22"
> Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-27-generic", arch: "amd64", family: "unix"
>Reporter: Karl Heinz Marbaise
>
> I have build which is working completely fine which means mvn clean package
> works perfect.
> If i try to do a mvn site i got the following Exception message:
> {code}[INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.3.1
> [ERROR] IOException: Failed to open file
> /home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
> opening zip file
> java.util.zip.ZipException: Failed to open file
> /home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
> opening zip file
> at org.apache.maven.shared.jar.JarAnalyzer.(JarAnalyzer.java:109)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:273)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1374)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:544)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:271)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:206)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:165)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:159)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:122)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> 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:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
> 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.ref
[jira] Updated: (MNG-5009) StackOverflowError in DefaultProjectBuilder.build
[
http://jira.codehaus.org/browse/MNG-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Fedorenko updated MNG-5009:
Attachment: pom.xml
trivial project to reproduce the problem (nothing beats stupidity of copy&paste
errors)
> StackOverflowError in DefaultProjectBuilder.build
> -
>
> Key: MNG-5009
> URL: http://jira.codehaus.org/browse/MNG-5009
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0.2
>Reporter: Igor Fedorenko
> Attachments: pom.xml
>
>
> I was refactoring m2e unit tests and got the following StackOverflowError
> when rebuilding test artifact repository (see below). To reproduce, run "mvn
> clean" from testLifecycleMappingMetadata of the attached project. I'll
> provide more info when I figure out what causes this.
> {noformat}
> [INFO] Scanning for projects...
> ---
> constituent[0]: file:/opt/maven/lib/maven-embedder-3.0.2.jar
> constituent[1]: file:/opt/maven/lib/maven-settings-3.0.2.jar
> constituent[2]: file:/opt/maven/lib/plexus-utils-2.0.4.jar
> constituent[3]: file:/opt/maven/lib/maven-core-3.0.2.jar
> constituent[4]: file:/opt/maven/lib/maven-model-3.0.2.jar
> constituent[5]: file:/opt/maven/lib/maven-settings-builder-3.0.2.jar
> constituent[6]: file:/opt/maven/lib/plexus-interpolation-1.14.jar
> constituent[7]: file:/opt/maven/lib/plexus-component-annotations-1.5.5.jar
> constituent[8]: file:/opt/maven/lib/plexus-sec-dispatcher-1.3.jar
> constituent[9]: file:/opt/maven/lib/plexus-cipher-1.4.jar
> constituent[10]: file:/opt/maven/lib/maven-repository-metadata-3.0.2.jar
> constituent[11]: file:/opt/maven/lib/maven-artifact-3.0.2.jar
> constituent[12]: file:/opt/maven/lib/maven-plugin-api-3.0.2.jar
> constituent[13]: file:/opt/maven/lib/sisu-inject-plexus-1.4.3.1.jar
> constituent[14]: file:/opt/maven/lib/sisu-inject-bean-1.4.3.1.jar
> constituent[15]: file:/opt/maven/lib/sisu-guice-2.9.1-noaop.jar
> constituent[16]: file:/opt/maven/lib/maven-model-builder-3.0.2.jar
> constituent[17]: file:/opt/maven/lib/maven-aether-provider-3.0.2.jar
> constituent[18]: file:/opt/maven/lib/aether-api-1.9.jar
> constituent[19]: file:/opt/maven/lib/aether-spi-1.9.jar
> constituent[20]: file:/opt/maven/lib/aether-util-1.9.jar
> constituent[21]: file:/opt/maven/lib/aether-impl-1.9.jar
> constituent[22]: file:/opt/maven/lib/maven-compat-3.0.2.jar
> constituent[23]: file:/opt/maven/lib/wagon-provider-api-1.0-beta-7.jar
> constituent[24]: file:/opt/maven/lib/commons-cli-1.2.jar
> constituent[25]: file:/opt/maven/lib/wagon-http-lightweight-1.0-beta-7.jar
> constituent[26]: file:/opt/maven/lib/wagon-http-shared-1.0-beta-7.jar
> constituent[27]: file:/opt/maven/lib/xercesMinimal-1.9.6.2.jar
> constituent[28]: file:/opt/maven/lib/nekohtml-1.9.6.2.jar
> constituent[29]: file:/opt/maven/lib/wagon-file-1.0-beta-7.jar
> constituent[30]: file:/opt/maven/lib/aether-connector-wagon-1.9.jar
> ---
> Exception in thread "main" java.lang.StackOverflowError
> at java.util.Vector.size(Vector.java:268)
> at java.util.Stack.pop(Stack.java:65)
> at
> org.codehaus.plexus.interpolation.PrefixAwareRecursionInterceptor.expressionResolutionFinished(PrefixAwareRecursionInterceptor.java:85)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:246)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:124)
> at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.interpolateInternal(AbstractStringBasedModelInterpolator.java:241)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:158)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:305)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:122)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateObject(StringSearchModelInterpolator.java:75)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateModel(StringSearchModelInterpolator.java:58)
> at
> org.apache.maven.model.building.DefaultModelBuilder.interpolateModel(DefaultModelBuilder.java:643)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:339)
> at
> org.apache.maven.model.building.Defa
[jira] Updated: (MNG-5009) StackOverflowError in DefaultProjectBuilder.build
[
http://jira.codehaus.org/browse/MNG-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Fedorenko updated MNG-5009:
Attachment: (was: stackoverflowerror.zip)
> StackOverflowError in DefaultProjectBuilder.build
> -
>
> Key: MNG-5009
> URL: http://jira.codehaus.org/browse/MNG-5009
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0.2
>Reporter: Igor Fedorenko
> Attachments: pom.xml
>
>
> I was refactoring m2e unit tests and got the following StackOverflowError
> when rebuilding test artifact repository (see below). To reproduce, run "mvn
> clean" from testLifecycleMappingMetadata of the attached project. I'll
> provide more info when I figure out what causes this.
> {noformat}
> [INFO] Scanning for projects...
> ---
> constituent[0]: file:/opt/maven/lib/maven-embedder-3.0.2.jar
> constituent[1]: file:/opt/maven/lib/maven-settings-3.0.2.jar
> constituent[2]: file:/opt/maven/lib/plexus-utils-2.0.4.jar
> constituent[3]: file:/opt/maven/lib/maven-core-3.0.2.jar
> constituent[4]: file:/opt/maven/lib/maven-model-3.0.2.jar
> constituent[5]: file:/opt/maven/lib/maven-settings-builder-3.0.2.jar
> constituent[6]: file:/opt/maven/lib/plexus-interpolation-1.14.jar
> constituent[7]: file:/opt/maven/lib/plexus-component-annotations-1.5.5.jar
> constituent[8]: file:/opt/maven/lib/plexus-sec-dispatcher-1.3.jar
> constituent[9]: file:/opt/maven/lib/plexus-cipher-1.4.jar
> constituent[10]: file:/opt/maven/lib/maven-repository-metadata-3.0.2.jar
> constituent[11]: file:/opt/maven/lib/maven-artifact-3.0.2.jar
> constituent[12]: file:/opt/maven/lib/maven-plugin-api-3.0.2.jar
> constituent[13]: file:/opt/maven/lib/sisu-inject-plexus-1.4.3.1.jar
> constituent[14]: file:/opt/maven/lib/sisu-inject-bean-1.4.3.1.jar
> constituent[15]: file:/opt/maven/lib/sisu-guice-2.9.1-noaop.jar
> constituent[16]: file:/opt/maven/lib/maven-model-builder-3.0.2.jar
> constituent[17]: file:/opt/maven/lib/maven-aether-provider-3.0.2.jar
> constituent[18]: file:/opt/maven/lib/aether-api-1.9.jar
> constituent[19]: file:/opt/maven/lib/aether-spi-1.9.jar
> constituent[20]: file:/opt/maven/lib/aether-util-1.9.jar
> constituent[21]: file:/opt/maven/lib/aether-impl-1.9.jar
> constituent[22]: file:/opt/maven/lib/maven-compat-3.0.2.jar
> constituent[23]: file:/opt/maven/lib/wagon-provider-api-1.0-beta-7.jar
> constituent[24]: file:/opt/maven/lib/commons-cli-1.2.jar
> constituent[25]: file:/opt/maven/lib/wagon-http-lightweight-1.0-beta-7.jar
> constituent[26]: file:/opt/maven/lib/wagon-http-shared-1.0-beta-7.jar
> constituent[27]: file:/opt/maven/lib/xercesMinimal-1.9.6.2.jar
> constituent[28]: file:/opt/maven/lib/nekohtml-1.9.6.2.jar
> constituent[29]: file:/opt/maven/lib/wagon-file-1.0-beta-7.jar
> constituent[30]: file:/opt/maven/lib/aether-connector-wagon-1.9.jar
> ---
> Exception in thread "main" java.lang.StackOverflowError
> at java.util.Vector.size(Vector.java:268)
> at java.util.Stack.pop(Stack.java:65)
> at
> org.codehaus.plexus.interpolation.PrefixAwareRecursionInterceptor.expressionResolutionFinished(PrefixAwareRecursionInterceptor.java:85)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:246)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:124)
> at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.interpolateInternal(AbstractStringBasedModelInterpolator.java:241)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:158)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:305)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:122)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateObject(StringSearchModelInterpolator.java:75)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateModel(StringSearchModelInterpolator.java:58)
> at
> org.apache.maven.model.building.DefaultModelBuilder.interpolateModel(DefaultModelBuilder.java:643)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:339)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
> at
[jira] Issue Comment Edited: (MNG-5009) StackOverflowError in DefaultProjectBuilder.build
[
http://jira.codehaus.org/browse/MNG-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255741#action_255741
]
Igor Fedorenko edited comment on MNG-5009 at 2/11/11 7:23 PM:
--
attached trivial project to reproduce the problem (nothing beats stupidity of
copy&paste errors)
was (Author: igorfie):
trivial project to reproduce the problem (nothing beats stupidity of
copy&paste errors)
> StackOverflowError in DefaultProjectBuilder.build
> -
>
> Key: MNG-5009
> URL: http://jira.codehaus.org/browse/MNG-5009
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0.2
>Reporter: Igor Fedorenko
> Attachments: pom.xml
>
>
> I was refactoring m2e unit tests and got the following StackOverflowError
> when rebuilding test artifact repository (see below). To reproduce, run "mvn
> clean" from testLifecycleMappingMetadata of the attached project. I'll
> provide more info when I figure out what causes this.
> {noformat}
> [INFO] Scanning for projects...
> ---
> constituent[0]: file:/opt/maven/lib/maven-embedder-3.0.2.jar
> constituent[1]: file:/opt/maven/lib/maven-settings-3.0.2.jar
> constituent[2]: file:/opt/maven/lib/plexus-utils-2.0.4.jar
> constituent[3]: file:/opt/maven/lib/maven-core-3.0.2.jar
> constituent[4]: file:/opt/maven/lib/maven-model-3.0.2.jar
> constituent[5]: file:/opt/maven/lib/maven-settings-builder-3.0.2.jar
> constituent[6]: file:/opt/maven/lib/plexus-interpolation-1.14.jar
> constituent[7]: file:/opt/maven/lib/plexus-component-annotations-1.5.5.jar
> constituent[8]: file:/opt/maven/lib/plexus-sec-dispatcher-1.3.jar
> constituent[9]: file:/opt/maven/lib/plexus-cipher-1.4.jar
> constituent[10]: file:/opt/maven/lib/maven-repository-metadata-3.0.2.jar
> constituent[11]: file:/opt/maven/lib/maven-artifact-3.0.2.jar
> constituent[12]: file:/opt/maven/lib/maven-plugin-api-3.0.2.jar
> constituent[13]: file:/opt/maven/lib/sisu-inject-plexus-1.4.3.1.jar
> constituent[14]: file:/opt/maven/lib/sisu-inject-bean-1.4.3.1.jar
> constituent[15]: file:/opt/maven/lib/sisu-guice-2.9.1-noaop.jar
> constituent[16]: file:/opt/maven/lib/maven-model-builder-3.0.2.jar
> constituent[17]: file:/opt/maven/lib/maven-aether-provider-3.0.2.jar
> constituent[18]: file:/opt/maven/lib/aether-api-1.9.jar
> constituent[19]: file:/opt/maven/lib/aether-spi-1.9.jar
> constituent[20]: file:/opt/maven/lib/aether-util-1.9.jar
> constituent[21]: file:/opt/maven/lib/aether-impl-1.9.jar
> constituent[22]: file:/opt/maven/lib/maven-compat-3.0.2.jar
> constituent[23]: file:/opt/maven/lib/wagon-provider-api-1.0-beta-7.jar
> constituent[24]: file:/opt/maven/lib/commons-cli-1.2.jar
> constituent[25]: file:/opt/maven/lib/wagon-http-lightweight-1.0-beta-7.jar
> constituent[26]: file:/opt/maven/lib/wagon-http-shared-1.0-beta-7.jar
> constituent[27]: file:/opt/maven/lib/xercesMinimal-1.9.6.2.jar
> constituent[28]: file:/opt/maven/lib/nekohtml-1.9.6.2.jar
> constituent[29]: file:/opt/maven/lib/wagon-file-1.0-beta-7.jar
> constituent[30]: file:/opt/maven/lib/aether-connector-wagon-1.9.jar
> ---
> Exception in thread "main" java.lang.StackOverflowError
> at java.util.Vector.size(Vector.java:268)
> at java.util.Stack.pop(Stack.java:65)
> at
> org.codehaus.plexus.interpolation.PrefixAwareRecursionInterceptor.expressionResolutionFinished(PrefixAwareRecursionInterceptor.java:85)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:246)
> at
> org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:124)
> at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.interpolateInternal(AbstractStringBasedModelInterpolator.java:241)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:158)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:305)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:122)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateObject(StringSearchModelInterpolator.java:75)
> at
> org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateModel(StringSearchModelInterpolator.java:58)
> at
> org.apache.maven.model.building.DefaultMo
[jira] Created: (MNG-5009) StackOverflowError in DefaultProjectBuilder.build
StackOverflowError in DefaultProjectBuilder.build
-
Key: MNG-5009
URL: http://jira.codehaus.org/browse/MNG-5009
Project: Maven 2 & 3
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 3.0.2
Reporter: Igor Fedorenko
Attachments: stackoverflowerror.zip
I was refactoring m2e unit tests and got the following StackOverflowError when
rebuilding test artifact repository (see below). To reproduce, run "mvn clean"
from testLifecycleMappingMetadata of the attached project. I'll provide more
info when I figure out what causes this.
{noformat}
[INFO] Scanning for projects...
---
constituent[0]: file:/opt/maven/lib/maven-embedder-3.0.2.jar
constituent[1]: file:/opt/maven/lib/maven-settings-3.0.2.jar
constituent[2]: file:/opt/maven/lib/plexus-utils-2.0.4.jar
constituent[3]: file:/opt/maven/lib/maven-core-3.0.2.jar
constituent[4]: file:/opt/maven/lib/maven-model-3.0.2.jar
constituent[5]: file:/opt/maven/lib/maven-settings-builder-3.0.2.jar
constituent[6]: file:/opt/maven/lib/plexus-interpolation-1.14.jar
constituent[7]: file:/opt/maven/lib/plexus-component-annotations-1.5.5.jar
constituent[8]: file:/opt/maven/lib/plexus-sec-dispatcher-1.3.jar
constituent[9]: file:/opt/maven/lib/plexus-cipher-1.4.jar
constituent[10]: file:/opt/maven/lib/maven-repository-metadata-3.0.2.jar
constituent[11]: file:/opt/maven/lib/maven-artifact-3.0.2.jar
constituent[12]: file:/opt/maven/lib/maven-plugin-api-3.0.2.jar
constituent[13]: file:/opt/maven/lib/sisu-inject-plexus-1.4.3.1.jar
constituent[14]: file:/opt/maven/lib/sisu-inject-bean-1.4.3.1.jar
constituent[15]: file:/opt/maven/lib/sisu-guice-2.9.1-noaop.jar
constituent[16]: file:/opt/maven/lib/maven-model-builder-3.0.2.jar
constituent[17]: file:/opt/maven/lib/maven-aether-provider-3.0.2.jar
constituent[18]: file:/opt/maven/lib/aether-api-1.9.jar
constituent[19]: file:/opt/maven/lib/aether-spi-1.9.jar
constituent[20]: file:/opt/maven/lib/aether-util-1.9.jar
constituent[21]: file:/opt/maven/lib/aether-impl-1.9.jar
constituent[22]: file:/opt/maven/lib/maven-compat-3.0.2.jar
constituent[23]: file:/opt/maven/lib/wagon-provider-api-1.0-beta-7.jar
constituent[24]: file:/opt/maven/lib/commons-cli-1.2.jar
constituent[25]: file:/opt/maven/lib/wagon-http-lightweight-1.0-beta-7.jar
constituent[26]: file:/opt/maven/lib/wagon-http-shared-1.0-beta-7.jar
constituent[27]: file:/opt/maven/lib/xercesMinimal-1.9.6.2.jar
constituent[28]: file:/opt/maven/lib/nekohtml-1.9.6.2.jar
constituent[29]: file:/opt/maven/lib/wagon-file-1.0-beta-7.jar
constituent[30]: file:/opt/maven/lib/aether-connector-wagon-1.9.jar
---
Exception in thread "main" java.lang.StackOverflowError
at java.util.Vector.size(Vector.java:268)
at java.util.Stack.pop(Stack.java:65)
at
org.codehaus.plexus.interpolation.PrefixAwareRecursionInterceptor.expressionResolutionFinished(PrefixAwareRecursionInterceptor.java:85)
at
org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:246)
at
org.codehaus.plexus.interpolation.StringSearchInterpolator.interpolate(StringSearchInterpolator.java:124)
at
org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.interpolateInternal(AbstractStringBasedModelInterpolator.java:241)
at
org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:158)
at
org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.traverseObjectWithParents(StringSearchModelInterpolator.java:305)
at
org.apache.maven.model.interpolation.StringSearchModelInterpolator$InterpolateObjectAction.run(StringSearchModelInterpolator.java:122)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateObject(StringSearchModelInterpolator.java:75)
at
org.apache.maven.model.interpolation.StringSearchModelInterpolator.interpolateModel(StringSearchModelInterpolator.java:58)
at
org.apache.maven.model.building.DefaultModelBuilder.interpolateModel(DefaultModelBuilder.java:643)
at
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:339)
at
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:354)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:417)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:417)
at
org.apache.maven.project.DefaultProjectBuilder.buil
[jira] Created: (WAGON-321) NPE in SftpWagon.returnToParentDirectory:105
NPE in SftpWagon.returnToParentDirectory:105 Key: WAGON-321 URL: http://jira.codehaus.org/browse/WAGON-321 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 1.0-beta-7 Environment: Apache Maven 3.0 (r1004208; 2010-10-04 04:50:56-0700) Java version: 1.6.0_22 Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/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: Jeff Rodriguez Attachments: log.txt, pom.txt I'm receiving an NPE when trying to deploy with release:perform. It looks like the code is trying to cd to the parent directory, but the channel is null for some reason. I can successfully login and download this file by hand. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255736#action_255736
]
Mark Struberg commented on SCM-606:
---
committed, review would be appreciated ;)
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-577) running only some method of a unit class (with -Dtest=MyClass#myMethod)
[ http://jira.codehaus.org/browse/SUREFIRE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255731#action_255731 ] Olivier Lamy commented on SUREFIRE-577: --- I'm +1 for -Dtest=Foo#mytest (with support of * -Dtest=Foo#my*test ). > running only some method of a unit class (with -Dtest=MyClass#myMethod) > --- > > Key: SUREFIRE-577 > URL: http://jira.codehaus.org/browse/SUREFIRE-577 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > I definitely don't know if it's possible with junit. > But it's an idea, I have now :-). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPIR-221) Fix for MPIR-171 generates unnecessary and confusing warnings for non-integral time-zones
Fix for MPIR-171 generates unnecessary and confusing warnings for non-integral time-zones - Key: MPIR-221 URL: http://jira.codehaus.org/browse/MPIR-221 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Affects Versions: 2.3.1 Reporter: SebbASF The change for MPIR-171 added a check to see if the timezone is numeric. If not, it reports a warning. However, the check fails to allow for non-integral timezones - e.g. 5.5 - and the warning message is incorrect, as it does not show the correct information. For example, the following setting: +5.5 results in the warning: [WARNING] The time zone '-2147483648' for the developer 'Name' is not a recognised time zone, use a number in the range -12 to +14 instead of. The message should read something like: [WARNING] The time zone '+5.5' for the developer 'Name' is not a recognised time zone, use a number in the range -12 to +14 or a valid long TimeZone id. except that it should not be generated for that particular timezone, as +5.5 is as valid as +5 (which does not generate a warning). To summarise: 1) the warning message is not helpful, as it does not show the correct timezone. 2) the warning should not be generated for fractional timezones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTTASKS-212) Maven Ant task seems to ignore artifacts with versions that start with a letter
Maven Ant task seems to ignore artifacts with versions that start with a letter --- Key: MANTTASKS-212 URL: http://jira.codehaus.org/browse/MANTTASKS-212 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.1, 2.1.0 Environment: OSX Reporter: Dave Whittaker I added a dependency on http://mvnrepository.com/artifact/org.xhtmlrenderer/core-renderer/R8pre2 to my POM today and found that while the dependencies of core-renderer were getting copied to my lib folder, the core-renderer artifact itself was not. After playing around with it for a while and verifying that It still happens with the latest version of the Maven Ant tasks (I was originally using v2.1.0) Maven itself listed core-renderer as a compile scoped dependency when running mvn dependency:tree It wasn't the flatten step in my build script that was somehow excluding it I tried uploading the dependency to a local repository with version 0.8pre2 instead or R8pre2. When I changed my dependency to the local version the jar showed up as expected. My ant task looks like: And inside the POM the dependency was specified as: org.xhtmlrenderer core-renderer R8pre2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255714#action_255714
]
Mark Struberg commented on SCM-606:
---
btw, not sure if this was intentionally, but what should scm:blame report? the
author or the committer? Remember that this might be different in git!
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255698#action_255698
]
Mark Struberg commented on SCM-606:
---
Fabien, could you please attach a
$> git blame --porcelain > git-blame2.out
?
Please use a repo/file which is ideally under ALv2. But at least not under some
problematic license and content, need it for inclusion in our test suite ;)
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255694#action_255694
]
Mark Struberg commented on SCM-606:
---
I think we should redo the parser and switch to the porcelain option finally
$> git blame -p
But that will take some time. So I will probably implement a quick fix for the
current parser upfront and later re-implement it with -p.
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255692#action_255692
]
Mark Struberg commented on SCM-606:
---
maybe it's even depending on the Locale, ...
A few of my findings so far indicate that I'll need to rewrite the whole
GitLogConsumer to use regexp (will commit test cases + fix later):
git-blame outputs spaces over here:
^e670863 (Mark Struberg 2007-11-22 22:16:03 +0100 17) * KIND, either express
or implied. See the License for the
^e670863 (Mark Struberg 2007-11-22 22:16:03 +0100 18) * specific language
governing permissions and limitations
--
git-blame with user.name="Mark (work)" (bracelets in the user.name)
66e621ed (Mark (work) 2011-02-11 19:01:15 +0100 1) testcontent
--
git-blame on a fresh file (not committed yet...)
(Not Committed Yet 2011-02-11 18:21:25 +0100 1) [core]
(Not Committed Yet 2011-02-11 18:21:25 +0100 2)
repositoryformatversion = 0
--
will of course also test a git-blame on an empty file and things.
If you have ideas of additional things to check, then please post ;)
LieGrue,
strub
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255691#action_255691
]
Fabien Bousquet commented on SCM-606:
-
My configurations tested :
* git-1.7.3 on Windows Vista
* git-1.7.4 on Windows Vista
* git-1.7.0.4 on a Linux
For these configurations, blame output is split on tabulator character.
I test on GitHub projects.
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255683#action_255683
]
Mark Struberg commented on SCM-606:
---
I c.
Did more research and it looks like we currently only split the output of
git-blame on tabulator characters('\t'). But here on my installation (Fedora14,
kernel-2.6.38, git-1.7.4) I get spaces as separator.
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-516) reportPlugins should/could inherit more information from pluginManagement
[ http://jira.codehaus.org/browse/MSITE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255681#action_255681 ] Jeremy Gustie commented on MSITE-516: - Dependencies from pluginManagement should be inherited as well; for example, when including Checkstyle configuration in a dependent JAR you should only need to specify that dependency once in pluginManagement. > reportPlugins should/could inherit more information from pluginManagement > - > > Key: MSITE-516 > URL: http://jira.codehaus.org/browse/MSITE-516 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Improvement > Components: inheritance >Affects Versions: 3.0-beta-2 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 15:50:56+0400) > Java version: 1.6.0_22 >Reporter: Oleg Estekhin > > At the moment the plugins configured in the reportPlugins section inherit > only the version specified in the pluginManagement section as described in > https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html#Maven3.xandsiteplugin-VersionResolution > . > Additional configuration (for example, configuration for > maven-javadoc-plugin) is effectively should be entered twice - once in either > build/pluginManagement/plugins or build/plugins to be used by the usual build > process, and once in the > build/plugins/maven-site-plugin/configuration/reportPlugins to be used by the > site generation. > Please, consider possibility for reportPlugins to inherit the same amount of > configuration from the pluginManagement as is being inherited by usual build > plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-131) Issue tracking typo; should mention how to report metadata issues
[ http://jira.codehaus.org/browse/MNGSITE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNGSITE-131. - Resolution: Fixed Assignee: Benjamin Bentmann Done in [r1069888|http://svn.apache.org/viewvc?view=revision&revision=1069888]. > Issue tracking typo; should mention how to report metadata issues > - > > Key: MNGSITE-131 > URL: http://jira.codehaus.org/browse/MNGSITE-131 > Project: Maven Project Web Site > Issue Type: Improvement > Environment: http://maven.apache.org/issue-tracking.html >Reporter: SebbASF >Assignee: Benjamin Bentmann > > The sentence: > "Issues, bugs, and feature requests should be submitted to the following > issue tracking systems depending projects." > does not make sense, it should be something like: > "Issues, bugs, and feature requests should be submitted to the following > issue tracking systems depending on which projects is involved." > Also, it is not particularly easy to find out how to report problems with > meta data in Maven Central, so it would help to add a link from this page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-132) MNG summary page should link to metadata issue tracker
[ http://jira.codehaus.org/browse/MNGSITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNGSITE-132. - Resolution: Fixed Assignee: Benjamin Bentmann Done. > MNG summary page should link to metadata issue tracker > -- > > Key: MNGSITE-132 > URL: http://jira.codehaus.org/browse/MNGSITE-132 > Project: Maven Project Web Site > Issue Type: Improvement > Environment: http://jira.codehaus.org/browse/MNG - Summary page >Reporter: SebbASF >Assignee: Benjamin Bentmann > > The Summary page helpfully links to various other JIRAs - e.g. for the > website - but does not include a link for reporting problems with Maven > metadata. > Please could such a link be added? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNGSITE-132) MNG summary page should link to metadata issue tracker
MNG summary page should link to metadata issue tracker -- Key: MNGSITE-132 URL: http://jira.codehaus.org/browse/MNGSITE-132 Project: Maven Project Web Site Issue Type: Improvement Environment: http://jira.codehaus.org/browse/MNG - Summary page Reporter: SebbASF The Summary page helpfully links to various other JIRAs - e.g. for the website - but does not include a link for reporting problems with Maven metadata. Please could such a link be added? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNGSITE-131) Issue tracking typo; should mention how to report metadata issues
Issue tracking typo; should mention how to report metadata issues - Key: MNGSITE-131 URL: http://jira.codehaus.org/browse/MNGSITE-131 Project: Maven Project Web Site Issue Type: Improvement Environment: http://maven.apache.org/issue-tracking.html Reporter: SebbASF The sentence: "Issues, bugs, and feature requests should be submitted to the following issue tracking systems depending projects." does not make sense, it should be something like: "Issues, bugs, and feature requests should be submitted to the following issue tracking systems depending on which projects is involved." Also, it is not particularly easy to find out how to report problems with meta data in Maven Central, so it would help to add a link from this page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSHARED-186) package goal on multi-module project does not find project module of type POM
package goal on multi-module project does not find project module of type POM - Key: MSHARED-186 URL: http://jira.codehaus.org/browse/MSHARED-186 Project: Maven Shared Components Issue Type: Bug Components: maven-artifact-resolver Affects Versions: maven-artifact-resolver-1.0 Environment: Windows XP, Maven 2.2.1 Reporter: Andrew Spencer Attachments: example-base.zip To reproduce this bug: unzip the attachment, it contains: * example-base (reactor project) * example-base\example-pom (module of type "pom") * example-base\example-submodule (other module, depends on example-pom) Launch "mvn package" in example-base, with a clean local repository Result: 1 required artifact is missing. for artifact: com.example:example-submodule:jar:1.0.0-SNAPSHOT 1) com.example:example-pomlib:pom:1.0.0-SNAPSHOT Path to dependency: 1) com.example:example-submodule:jar:1.0.0-SNAPSHOT 2) com.example:example-pomlib:pom:1.0.0-SNAPSHOT Expected behaviour: project should build successfully Note: build is successful if "mvn install" or later goal is launched. The artifact resolver has not looked within the project itself for the dependency of type pom, as it does for a dependency of type jar, war etc. Instead it looks in the repository, and does not find it since the "install" goal has not yet been launched. I have set priority to Major because 1) having an intra-reactor dependency on a POM project is a common way to manage skinny WARs, so this problem will crop up often 2) the error message doesn't give a clue to the cause of the problem, so it has the potential to cause a lot of wasted time 3) the error also happens when maven-release-plugin is used to perform a release, since this plugin by default executes the "package" goal -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SCM-606 started by Mark Struberg.
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPMD-130) excludeRoot doesn't work in site build on multi-module projects
excludeRoot doesn't work in site build on multi-module projects
---
Key: MPMD-130
URL: http://jira.codehaus.org/browse/MPMD-130
Project: Maven 2.x PMD Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Marcel Stör
The parent POM of my multi-module setup says
1.6
target/generated-sources
If I run {{mvn pmd:cpd}} or {{mvn site}} directly on the module that actually
has generated code the report is as expected. The files in
{{target/generated-sources}} are ignored. Also, if I run {{mvn pmd:cpd}} at
root level outside all the modules the report is fine.
However, if I run {{mvn site}} at root level outside all the modules the
excludeRoot is ignored.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5008) resolution of concurrent SNAPSHOT artifacts from multiple repositories should use timestamp instead of buildNumber
resolution of concurrent SNAPSHOT artifacts from multiple repositories should use timestamp instead of buildNumber --- Key: MNG-5008 URL: http://jira.codehaus.org/browse/MNG-5008 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.1, 2.2.1 Reporter: Julien CARSIQUE When getting a SNAPSHOT artifact from multiple repositories, Maven must choose the more recent one. Using buildNumber is useless and meaningless as the two repositories have separate incrementation of their buildNumber. For example, retrieving the two following metadata: org.nuxeo.runtime nuxeo-runtime-parent 5.4.1-SNAPSHOT 20110202.045408 48 20110202045420 org.nuxeo.runtime nuxeo-runtime-parent 5.4.1-SNAPSHOT 20110206.141840 18 20110206141840 As you can see, the snapshot artifact with timestamp 20110206.141840 is more recent than the one with timestamp 20110202.045408. But when parsing the POM, comparing metadata, the oldest artifact will be downloaded. I saw that issue raised on Jenkins which uses Maven API. Last year, I've encountered the same issue with Nexus (also using Maven API) for which a workaround was easily done as Nexus aggregates information from multiple repositories. Such workaround may not be possible in Jenkins, or when directly building with Maven. That need to be fixed in the Maven API. I guess it comes from http://svn.apache.org/viewvc/maven/maven-3/tags/maven-3.0.2/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java?view=markup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-448) You don't have a SNAPSHOT project in the reactor projects list.
[ http://jira.codehaus.org/browse/MRELEASE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255642#action_255642 ] Damian Nowak commented on MRELEASE-448: --- Release plugin should be flexible, not it isn't. You can suggest good practises but not demand it. Therefore, something like -Drelease.force=true should be available. > You don't have a SNAPSHOT project in the reactor projects list. > --- > > Key: MRELEASE-448 > URL: http://jira.codehaus.org/browse/MRELEASE-448 > Project: Maven 2.x Release Plugin > Issue Type: New Feature > Components: prepare >Affects Versions: 2.0-beta-9 >Reporter: fabrice >Assignee: Olivier Lamy > > I need to have A SNAPSHOT VERSION to use this plugin. > Do I need really to change the version guideline of my company or is it > possible to adapt this plugin to work with non snapshot version ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255640#action_255640
]
Fabien Bousquet commented on SCM-606:
-
This feature (blame for gitexe) is already implemented (See
{code}org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand{code})
. I use it already and it is operational.
Is what I'm wrong?
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with that ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-649) release:prepare - ignores SNAPSHOT version in pluginManagement section
release:prepare - ignores SNAPSHOT version in pluginManagement section -- Key: MRELEASE-649 URL: http://jira.codehaus.org/browse/MRELEASE-649 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Marcus Linke When release prepare a project with a pom.xml that defines a SNAPSHOT version in its section, the plugin should detect that and ask the user for the release version as is does it for dependencies versions already. This is especially needed if the project to be released is of package type 'pom' and acts as a parent pom for other projects. Otherwise this raises an error later when try to release one of these child projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
