[jira] [Resolved] (SUREFIRE-1168) failsafe won't exclude scope 'provided'
[
https://issues.apache.org/jira/browse/SUREFIRE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved SUREFIRE-1168.
Resolution: Invalid
> failsafe won't exclude scope 'provided'
> ---
>
> Key: SUREFIRE-1168
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1168
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.18.1
>Reporter: Benson Margulies
>
> https://github.com/bimargulies/failsafe-cp-tc is a test case.
> I have a jar with provided scope which needs to _not_ be in the classpath
> when running the tests. So, I wrote:
> {code}
>
>
> provided
>
> {code}
> No such luck, the jar remains in the classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (MRELEASE-889) Version policies don't work with Maven 2.2.1
[ https://issues.apache.org/jira/browse/MRELEASE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MRELEASE-889. --- Resolution: Won't Fix > Version policies don't work with Maven 2.2.1 > > > Key: MRELEASE-889 > URL: https://issues.apache.org/jira/browse/MRELEASE-889 > Project: Maven Release Plugin > Issue Type: Bug >Reporter: Benson Margulies >Assignee: Robert Scholte > > rfscholte fixed a problem in svn commit 1626251 that broke the build for > 2.2.1: > Fix doclettag attribute for hint, which causes the build to fail with M2.2.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MNG-3879) Dependency map and documentation
[ https://issues.apache.org/jira/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MNG-3879. --- Resolution: Won't Fix Fix Version/s: (was: Issues to be reviewed for 4.x) > Dependency map and documentation > > > Key: MNG-3879 > URL: https://issues.apache.org/jira/browse/MNG-3879 > Project: Maven > Issue Type: New Feature > Components: Dependencies >Affects Versions: 2.0.9 >Reporter: Benson Margulies > > This JIRA proposes a feature. I'm willing to try to contribute it given a > modicum of encouragement and guidance. > Over at CXF, we get many questions from users who are completely confounded > by the complex dependency graph that results from our many dependencies and > their many dependencies. I think that they would be less confused by far if > maven gave them a tiny bit of help. > My idea for this requires an addition to the core POM, which is why I'm > starting with a JIRA here. I propose to add an 'explanation' element to the > dependency element. This would contain a human-readable string explaining why > the dependency is here, which could be carried out through the dependency > plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MDEP-434) Give better explanation of dependency intent.
[ https://issues.apache.org/jira/browse/MDEP-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MDEP-434. --- Resolution: Won't Fix > Give better explanation of dependency intent. > - > > Key: MDEP-434 > URL: https://issues.apache.org/jira/browse/MDEP-434 > Project: Maven Dependency Plugin > Issue Type: Wish >Reporter: Benson Margulies > > If MNG-3879 ever gets done, this plugin could decorate its output with > human-readable content about dependency intent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MENFORCER-203) dependencyConvergence seems to get tangled in reactor
[
https://issues.apache.org/jira/browse/MENFORCER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved MENFORCER-203.
Resolution: Invalid
> dependencyConvergence seems to get tangled in reactor
> -
>
> Key: MENFORCER-203
> URL: https://issues.apache.org/jira/browse/MENFORCER-203
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 1.3.1
>Reporter: Benson Margulies
> Fix For: more-investigation, waiting-for-feedback
>
>
> The enforcer is claiming that one of the modules of my project is using the
> prior release version of another of the modules of my project.
> The problem version, 1.9.112, occurs _nowhere_ in any current POM.
> Both modules refer to adm-model with {{$\{project.version\}}} references.
> {noformat}
> [WARNING]
> Dependency convergence error for com.basistech:adm-model:2.0.0-rc1-SNAPSHOT
> paths to dependency are:
> +-com.basistech:adm-tools:2.0.0-rc1-SNAPSHOT
> +-com.basistech:adm-model:2.0.0-rc1-SNAPSHOT
> and
> +-com.basistech:adm-tools:2.0.0-rc1-SNAPSHOT
> +-com.basistech:adm-json:2.0.0-rc1-SNAPSHOT
> +-com.basistech:adm-model:1.9.112
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence
> failed with message:
> Failed while enforcing releasability the error(s) are [
> Dependency convergence error for com.basistech:adm-model:2.0.0-rc1-SNAPSHOT
> paths to dependency are:
> +-com.basistech:adm-tools:2.0.0-rc1-SNAPSHOT
> +-com.basistech:adm-model:2.0.0-rc1-SNAPSHOT
> and
> +-com.basistech:adm-tools:2.0.0-rc1-SNAPSHOT
> +-com.basistech:adm-json:2.0.0-rc1-SNAPSHOT
> +-com.basistech:adm-model:1.9.112
> {noformat}
> but mvn dependency:tree says in the failing module:
> {noformat}
> [INFO] --- maven-dependency-plugin:2.5.1:tree (default-cli) @ adm-tools ---
> [INFO] com.basistech:adm-tools:jar:2.0.0-rc1-SNAPSHOT
> [INFO] +- com.basistech:adm-model:jar:2.0.0-rc1-SNAPSHOT:compile
> [INFO] +- com.basistech:adm-json:jar:2.0.0-rc1-SNAPSHOT:compile
> [INFO] +- com.basistech:rlp-java-blackboard:jar:12.1:compile
> [INFO] | +- com.basistech:rlp:jar:7.10.0:compile
> [INFO] | | \- com.basistech:utilities:jar:7.10.0:compile
> [INFO] | +-
> com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:2.4.1:compile
> (version managed from 2.3.0)
> [INFO] | \- org.javassist:javassist:jar:3.18.0-GA:compile
> [INFO] +- com.basistech:common:jar:33:compile
> [INFO] +- com.google.guava:guava:jar:16.0.1:compile
> [INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.4.1:compile
> [INFO] +- com.fasterxml.jackson.core:jackson-databind:jar:2.4.1:compile
> [INFO] | \- com.fasterxml.jackson.core:jackson-annotations:jar:2.4.1:compile
> (version managed from 2.4.0)
> [INFO] +- junit:junit:jar:4.11:test
> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test
> [INFO] \- args4j:args4j:jar:2.0.26:compile
> {noformat}
> and in the 'json' module:
> {noformat}
> --- maven-dependency-plugin:2.5.1:tree (default-cli) @ adm-json ---
> [INFO] com.basistech:adm-json:jar:2.0.0-rc1-SNAPSHOT
> [INFO] +- com.basistech:adm-model:jar:2.0.0-rc1-SNAPSHOT:compile
> [INFO] +- com.basistech:common:jar:33:compile
> [INFO] +- com.google.guava:guava:jar:16.0.1:compile
> [INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.4.1:compile
> [INFO] +- com.fasterxml.jackson.core:jackson-databind:jar:2.4.1:compile
> [INFO] | \- com.fasterxml.jackson.core:jackson-annotations:jar:2.4.1:compile
> (version managed from 2.4.0)
> [INFO] \- junit:junit:jar:4.11:test
> [INFO]\- org.hamcrest:hamcrest-core:jar:1.3:test
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (MSHADE-253) NullPointerException if minimizeJar == true && packaging == pom
[
https://issues.apache.org/jira/browse/MSHADE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved MSHADE-253.
-
Resolution: Fixed
Assignee: Benson Margulies
Fix Version/s: 3.0.1
> NullPointerException if minimizeJar == true && packaging == pom
> ---
>
> Key: MSHADE-253
> URL: https://issues.apache.org/jira/browse/MSHADE-253
> Project: Maven Shade Plugin
> Issue Type: Bug
>Reporter: Aviem Zur
>Assignee: Benson Margulies
> Fix For: 3.0.1
>
>
> NullPointerException is thrown if minimizeJar == true && packaging == pom
> Discovered when trying to configure shading a parent pom (With packaging ==
> pom) so all submodules will shade using this configuration.
> Stack trace:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (*) on project
> *: Error creating shaded jar: null: NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (*) on
> project *: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:498)
> 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.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:540)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.io.FileInputStream.(FileInputStream.java:130)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:94)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:814)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:446)
> ... 22 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MSHADE-253) NullPointerException if minimizeJar == true && packaging == pom
[
https://issues.apache.org/jira/browse/MSHADE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943394#comment-15943394
]
Benson Margulies commented on MSHADE-253:
-
Merged.
> NullPointerException if minimizeJar == true && packaging == pom
> ---
>
> Key: MSHADE-253
> URL: https://issues.apache.org/jira/browse/MSHADE-253
> Project: Maven Shade Plugin
> Issue Type: Bug
>Reporter: Aviem Zur
>Assignee: Benson Margulies
> Fix For: 3.0.1
>
>
> NullPointerException is thrown if minimizeJar == true && packaging == pom
> Discovered when trying to configure shading a parent pom (With packaging ==
> pom) so all submodules will shade using this configuration.
> Stack trace:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (*) on project
> *: Error creating shaded jar: null: NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (*) on
> project *: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:498)
> 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.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:540)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.io.FileInputStream.(FileInputStream.java:130)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:94)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:814)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:446)
> ... 22 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MDEP-643) includeGroupIds ending with ".pom" lead to error
[ https://issues.apache.org/jira/browse/MDEP-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099315#comment-17099315 ] Benson Margulies commented on MDEP-643: --- To help someone get started with this; you'll need an integration test that reproduces it. > includeGroupIds ending with ".pom" lead to error > > > Key: MDEP-643 > URL: https://issues.apache.org/jira/browse/MDEP-643 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: unpack-dependencies >Affects Versions: 3.1.1 > Environment: MacOS, Intelij Idea with built-in-terminal >Reporter: Arnd Horstmann >Priority: Major > > a set of dependencies to third-party-jars, which I have to unpack, ends with > ".pom" in groupId. > When I try to include this groupId with , I get this Error > with "mvn clean install": > No such archiver: 'pom'. > If I rename the groupId in my local .m2-repository (and the effected pom), > everything just works fine. > By the way: I didn't try ".pom." as a qualifier in the middle... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
[ https://issues.apache.org/jira/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MDEP-480: - Assignee: Benson Margulies > There should be an option to prevent files overwrite for unpack-dependencies > and unpack > --- > > Key: MDEP-480 > URL: https://issues.apache.org/jira/browse/MDEP-480 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: unpack, unpack-dependencies >Reporter: duongdeptrai >Assignee: Benson Margulies >Priority: Major > Labels: close-pending > Attachments: patch-maven-dependency-2.9-overwriteFiles.patch > > > There should be an option to prevent file overwrite when extracting files. > This option is very helpful when unpack or unpack-dependencies happens after > process-resouce phase. > Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. > But they all work on the artifact scope (that means decide if a whole > artifact should overwrite), not files scope (if a file should overwrite an > existing file). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
[ https://issues.apache.org/jira/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MDEP-480: -- Labels: (was: close-pending) > There should be an option to prevent files overwrite for unpack-dependencies > and unpack > --- > > Key: MDEP-480 > URL: https://issues.apache.org/jira/browse/MDEP-480 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: unpack, unpack-dependencies >Reporter: duongdeptrai >Assignee: Benson Margulies >Priority: Major > Attachments: patch-maven-dependency-2.9-overwriteFiles.patch > > > There should be an option to prevent file overwrite when extracting files. > This option is very helpful when unpack or unpack-dependencies happens after > process-resouce phase. > Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. > But they all work on the artifact scope (that means decide if a whole > artifact should overwrite), not files scope (if a file should overwrite an > existing file). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
[ https://issues.apache.org/jira/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104887#comment-17104887 ] Benson Margulies commented on MDEP-480: --- Jonathan Volfson and I are working on this. I wanted to state the original 'mission' of this patch more carefully and see if the community is comfortable: Consider a artifact (g:a) that has multiple files, either via classifiers or by type. Consider a directory on disk that contains _some_ of the files for this artifact. The effect of this flag is to allow the plugin to deliver the missing files without overwriting any existing files. > There should be an option to prevent files overwrite for unpack-dependencies > and unpack > --- > > Key: MDEP-480 > URL: https://issues.apache.org/jira/browse/MDEP-480 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: unpack, unpack-dependencies >Reporter: duongdeptrai >Assignee: Benson Margulies >Priority: Major > Attachments: patch-maven-dependency-2.9-overwriteFiles.patch > > > There should be an option to prevent file overwrite when extracting files. > This option is very helpful when unpack or unpack-dependencies happens after > process-resouce phase. > Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. > But they all work on the artifact scope (that means decide if a whole > artifact should overwrite), not files scope (if a file should overwrite an > existing file). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEP-645) List classes in a given artifact
[
https://issues.apache.org/jira/browse/MDEP-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107643#comment-17107643
]
Benson Margulies commented on MDEP-645:
---
Is this the job of a new mojo, or rather an option to :list?
> List classes in a given artifact
>
>
> Key: MDEP-645
> URL: https://issues.apache.org/jira/browse/MDEP-645
> Project: Maven Dependency Plugin
> Issue Type: New Feature
>Reporter: John Lin
>Priority: Minor
> Labels: intern
>
> When I want to list all the classes in a given artifact, I have to use
> {{jar}} command to show files in the corresponding .jar file.
> For example, I want to list all the classes in the artifact
> {code}
> org.apache.commons:commons-lang3:3.6
> {code}
> I have to run
> {code}
> jar tf
> ~/.m2/repository/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6.jar
> {code}
> This method has some disadvantages:
> # The jar file may not be downloaded, so it may not be in
> {{~/.m2/repository}}.
> # It's kind of tedious to type such a long filename.
> # The output is shown in raw filenames, e.g.,
> {{org/apache/commons/lang3/SystemUtils.class}}, but I generally want a
> package + class name {{org.apache.commons.lang3.SystemUtils}}.
> So I would expect a goal called {{show}} with an argument {{artifact}}, so I
> can type
> {code}
> mvn dependency:show -Dartifact=org.apache.commons:commons-lang3:3.6
> {code}
> to show
> {code}
> org.apache.commons.lang3.CharUtils
> org.apache.commons.lang3.RandomStringUtils
> ...
> {code}
> What do you guys think? Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MRELEASE-915) Forked execution of perform leaks source roots
Benson Margulies created MRELEASE-915: - Summary: Forked execution of perform leaks source roots Key: MRELEASE-915 URL: https://issues.apache.org/jira/browse/MRELEASE-915 Project: Maven Release Plugin Issue Type: Bug Components: perform Affects Versions: 2.5.1 Reporter: Benson Margulies https://github.com/bimargulies/release-root-leakage is a test case for the following: If you add a source root in generate-sources in a pom, that source root will show up in the 'validate' phase in the forked execution for release:perform. This causes checkstyle to see things that it should not, if nothing else bad. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-915) Forked execution of perform leaks source roots
[ https://issues.apache.org/jira/browse/MRELEASE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624013#comment-14624013 ] Benson Margulies commented on MRELEASE-915: --- forked-path does not change the results. > Forked execution of perform leaks source roots > -- > > Key: MRELEASE-915 > URL: https://issues.apache.org/jira/browse/MRELEASE-915 > Project: Maven Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.5.1 >Reporter: Benson Margulies > > https://github.com/bimargulies/release-root-leakage is a test case for the > following: > If you add a source root in generate-sources in a pom, that source root will > show up in the 'validate' phase in the forked execution for release:perform. > This causes checkstyle to see things that it should not, if nothing else bad. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHADE-190) Shade does not relocate the contents of META-INF/services files
[ https://issues.apache.org/jira/browse/MSHADE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MSHADE-190: Fix Version/s: (was: waiting-for-feedback) Description: 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. A test case can be found at https://github.com/bimargulies/shade-meta-tc. Just run mvn package, and examine the resulting META-INF/services file. was: 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. > 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. > A test case can be found at > https://github.com/bimargulies/shade-meta-tc. > Just run mvn package, and examine the resulting META-INF/services file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MSHADE-190) Shade does not relocate the contents of META-INF/services files
[ https://issues.apache.org/jira/browse/MSHADE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MSHADE-190: --- Assignee: Benson Margulies > 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 >Assignee: 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. > A test case can be found at > https://github.com/bimargulies/shade-meta-tc. > Just run mvn package, and examine the resulting META-INF/services file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MSHADE-190) Shade does not relocate the contents of META-INF/services files
[ https://issues.apache.org/jira/browse/MSHADE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MSHADE-190. - Resolution: Fixed svn rev 1690562. > 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 >Assignee: 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. > A test case can be found at > https://github.com/bimargulies/shade-meta-tc. > Just run mvn package, and examine the resulting META-INF/services file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MSHADE-190) Shade does not relocate the contents of META-INF/services files
[ https://issues.apache.org/jira/browse/MSHADE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624125#comment-14624125 ] Benson Margulies edited comment on MSHADE-190 at 7/13/15 2:09 AM: -- svn rev 1690562. I added code to the ServicesResourceTransformer to handle this. was (Author: bmargulies): svn rev 1690562. > 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 >Assignee: Benson Margulies > Fix For: 2.4.2 > > > 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. > A test case can be found at > https://github.com/bimargulies/shade-meta-tc. > Just run mvn package, and examine the resulting META-INF/services file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHADE-190) Shade does not relocate the contents of META-INF/services files
[ https://issues.apache.org/jira/browse/MSHADE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MSHADE-190: Fix Version/s: 2.4.2 > 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 >Assignee: Benson Margulies > Fix For: 2.4.2 > > > 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. > A test case can be found at > https://github.com/bimargulies/shade-meta-tc. > Just run mvn package, and examine the resulting META-INF/services file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MASSEMBLY-777) The assembly plugin refuses to copy a file named lexicon.filtered
Benson Margulies created MASSEMBLY-777: -- Summary: The assembly plugin refuses to copy a file named lexicon.filtered Key: MASSEMBLY-777 URL: https://issues.apache.org/jira/browse/MASSEMBLY-777 Project: Maven Assembly Plugin Issue Type: Bug Affects Versions: 2.5.5 Reporter: Benson Margulies Assignee: Benson Margulies I will attach a pointer to a github project which demonstrated that the plugin skips a file named lexicon.filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MASSEMBLY-777) The assembly plugin refuses to copy a file named lexicon.filtered
[ https://issues.apache.org/jira/browse/MASSEMBLY-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MASSEMBLY-777: --- Description: https://github.com/bimargulies/massembly-777 is a github project which demonstrated that the plugin skips a file named lexicon.filtered. was: I will attach a pointer to a github project which demonstrated that the plugin skips a file named lexicon.filtered. > The assembly plugin refuses to copy a file named lexicon.filtered > - > > Key: MASSEMBLY-777 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-777 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Benson Margulies >Assignee: Benson Margulies > > https://github.com/bimargulies/massembly-777 is a github project which > demonstrated that the plugin skips a file named lexicon.filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MASSEMBLY-777) The assembly plugin refuses to copy a file named lexicon.filtered
[ https://issues.apache.org/jira/browse/MASSEMBLY-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MASSEMBLY-777. Resolution: Fixed Fix Version/s: 3.0.0 svn 1690973. AddFileSetsTask.java contained an undocumented, unconfigurable, exclusion for files named *.filtered and *.formatted. Since this is going into a major (3.0.0) release, I'm removing it without further ceremony. > The assembly plugin refuses to copy a file named lexicon.filtered > - > > Key: MASSEMBLY-777 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-777 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0.0 > > > https://github.com/bimargulies/massembly-777 is a github project which > demonstrated that the plugin skips a file named lexicon.filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MASSEMBLY-777) The assembly plugin refuses to copy a file named lexicon.filtered
[ https://issues.apache.org/jira/browse/MASSEMBLY-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reopened MASSEMBLY-777: > The assembly plugin refuses to copy a file named lexicon.filtered > - > > Key: MASSEMBLY-777 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-777 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0.0 > > > https://github.com/bimargulies/massembly-777 is a github project which > demonstrated that the plugin skips a file named lexicon.filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MASSEMBLY-777) The assembly plugin refuses to copy a file named lexicon.filtered
[ https://issues.apache.org/jira/browse/MASSEMBLY-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626934#comment-14626934 ] Benson Margulies commented on MASSEMBLY-777: Reverted for now, perhaps returning with a controlling parameter, perhaps returning with a repair to filtering. > The assembly plugin refuses to copy a file named lexicon.filtered > - > > Key: MASSEMBLY-777 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-777 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0.0 > > > https://github.com/bimargulies/massembly-777 is a github project which > demonstrated that the plugin skips a file named lexicon.filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1168) failsafe won't exclude scope 'provided'
Benson Margulies created SUREFIRE-1168:
--
Summary: failsafe won't exclude scope 'provided'
Key: SUREFIRE-1168
URL: https://issues.apache.org/jira/browse/SUREFIRE-1168
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin
Affects Versions: 2.18.1
Reporter: Benson Margulies
https://github.com/bimargulies/failsafe-cp-tc is a test case.
I have a jar with provided scope which needs to _not_ be in the classpath when
running the tests. So, I wrote:
{code}
provided
{code}
No such luck, the jar remains in the classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1168) failsafe won't exclude scope 'provided'
[
https://issues.apache.org/jira/browse/SUREFIRE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630627#comment-14630627
]
Benson Margulies commented on SUREFIRE-1168:
I did read the doc, quoted below. It mentions provided. Further, it references
a class, and that class contains
org.apache.maven.artifact.Artifact#SCOPE_PROVIDED. So I continue to see this as
a bug.
{noformat}
A dependency scope to exclude from the test classpath. The scope should be one
of the scopes defined by org.apache.maven.artifact.Artifact. This includes the
following:
compile - system, provided, compile
runtime - compile, runtime
compile+runtime - system, provided, compile, runtime
runtime+system - system, compile, runtime
test - system, provided, compile, runtime, test
{noformat}
> failsafe won't exclude scope 'provided'
> ---
>
> Key: SUREFIRE-1168
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1168
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.18.1
>Reporter: Benson Margulies
>
> https://github.com/bimargulies/failsafe-cp-tc is a test case.
> I have a jar with provided scope which needs to _not_ be in the classpath
> when running the tests. So, I wrote:
> {code}
>
>
> provided
>
> {code}
> No such luck, the jar remains in the classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1168) failsafe won't exclude scope 'provided'
[
https://issues.apache.org/jira/browse/SUREFIRE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631177#comment-14631177
]
Benson Margulies commented on SUREFIRE-1168:
If you guys aren't ready to stop supporting 2.2.1, then I would suggest that
the doc could be clarified, which I may well PR.
> failsafe won't exclude scope 'provided'
> ---
>
> Key: SUREFIRE-1168
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1168
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.18.1
>Reporter: Benson Margulies
>
> https://github.com/bimargulies/failsafe-cp-tc is a test case.
> I have a jar with provided scope which needs to _not_ be in the classpath
> when running the tests. So, I wrote:
> {code}
>
>
> provided
>
> {code}
> No such luck, the jar remains in the classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1168) failsafe won't exclude scope 'provided'
[
https://issues.apache.org/jira/browse/SUREFIRE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631322#comment-14631322
]
Benson Margulies commented on SUREFIRE-1168:
This is especially true because there are other plugins, like the dependency
plugin, that accept simple scope lists for exclusion/inclusion, so a bear of
little brain like myself just assumed that this was more of the same.
> failsafe won't exclude scope 'provided'
> ---
>
> Key: SUREFIRE-1168
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1168
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.18.1
>Reporter: Benson Margulies
>
> https://github.com/bimargulies/failsafe-cp-tc is a test case.
> I have a jar with provided scope which needs to _not_ be in the classpath
> when running the tests. So, I wrote:
> {code}
>
>
> provided
>
> {code}
> No such luck, the jar remains in the classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MASSEMBLY-777) The assembly plugin refuses to copy a file named lexicon.filtered or lexicon.formatted
[ https://issues.apache.org/jira/browse/MASSEMBLY-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632104#comment-14632104 ] Benson Margulies commented on MASSEMBLY-777: [~hboutemy] Thanks! > The assembly plugin refuses to copy a file named lexicon.filtered or > lexicon.formatted > -- > > Key: MASSEMBLY-777 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-777 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Benson Margulies >Assignee: Hervé Boutemy > Fix For: 3.0.0 > > > https://github.com/bimargulies/massembly-777 is a github project which > demonstrated that the plugin skips a file named lexicon.filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MASSEMBLY-779) It would be useful to be able to make the assembly plugin fail on errors
Benson Margulies created MASSEMBLY-779: -- Summary: It would be useful to be able to make the assembly plugin fail on errors Key: MASSEMBLY-779 URL: https://issues.apache.org/jira/browse/MASSEMBLY-779 Project: Maven Assembly Plugin Issue Type: New Feature Reporter: Benson Margulies We've encountered some situations in which we would like our builds to fail if the assembly plugin cannot find some item called for in the descriptor. This suggests the invention of a failOnMissingItem boolean parameter. Default, of course, to current behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-915) Forked execution of perform leaks source roots
[ https://issues.apache.org/jira/browse/MRELEASE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632913#comment-14632913 ] Benson Margulies commented on MRELEASE-915: --- Martin, the scenario you describe bears no resemblance to the situation at hand. I wrote a maven plugin which generates code from an XML file and a template. The code in question is not intended to comply with our checkstyle rules. I have worked around it by configuring checkstyle to look only in src/main/java. I'd like to see someone track this down in the release plugin or the core; I'm not sure where to start or I'd do some tracking on my own. > Forked execution of perform leaks source roots > -- > > Key: MRELEASE-915 > URL: https://issues.apache.org/jira/browse/MRELEASE-915 > Project: Maven Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.5.1 >Reporter: Benson Margulies > > https://github.com/bimargulies/release-root-leakage is a test case for the > following: > If you add a source root in generate-sources in a pom, that source root will > show up in the 'validate' phase in the forked execution for release:perform. > This causes checkstyle to see things that it should not, if nothing else bad. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MASSEMBLY-780) Snappy supported
Benson Margulies created MASSEMBLY-780: -- Summary: Snappy supported Key: MASSEMBLY-780 URL: https://issues.apache.org/jira/browse/MASSEMBLY-780 Project: Maven Assembly Plugin Issue Type: New Feature Reporter: Benson Margulies Plexus archiver supports snappy. So maven-assembly can, too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MASSEMBLY-780) Snappy supported
[ https://issues.apache.org/jira/browse/MASSEMBLY-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MASSEMBLY-780: -- Assignee: Benson Margulies > Snappy supported > > > Key: MASSEMBLY-780 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-780 > Project: Maven Assembly Plugin > Issue Type: New Feature >Reporter: Benson Margulies >Assignee: Benson Margulies > > Plexus archiver supports snappy. So maven-assembly can, too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MASSEMBLY-780) Snappy supported
[ https://issues.apache.org/jira/browse/MASSEMBLY-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MASSEMBLY-780. Resolution: Fixed Fix Version/s: 3.0.0 1692379: added .tar.snappy. > Snappy supported > > > Key: MASSEMBLY-780 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-780 > Project: Maven Assembly Plugin > Issue Type: New Feature >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0.0 > > > Plexus archiver supports snappy. So maven-assembly can, too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)
[
https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697908#comment-14697908
]
Benson Margulies commented on MPIR-234:
---
I am going to put in a fruitless reminder that it would be a lot cleaner to add
more elements under than to keep making the URL longer and longer.
Everyone says, 'oh, we can't do that, we might bust some crappily-written tool
that reads POMs.' I think we should just rev the POM schema to allow for
arbitrary 'foreign namespace' elements, and use namespace for this kind of
extension, and the tools that are still using 15-year-old XML parsing
technology can go ahead and croak.
> SCM-link in site of multimodule projects should not append module name by
> default (at least for git)
>
>
> Key: MPIR-234
> URL: https://issues.apache.org/jira/browse/MPIR-234
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: scm
>Affects Versions: 2.4
>Reporter: Mirko Friedenhagen
>
> I have setup a simple multi module project (see
> https://github.com/mfriedenhagen/multi-module-sample/tree/multi-site-complex)
> which uses git on github as {{scm}}. While rendering the site, MPIR will by
> default add the name of the module to the SCM-URLs in source-repository.html.
> So instead of https://github.com/mfriedenhagen/multi-module-sample/ I see
> https://github.com/mfriedenhagen/multi-module-sample/core/,
> g...@github.com:mfriedenhagen/multi-module-sample.git/core and
> git://github.com/mfriedenhagen/multi-module-sample.git/core in the report for
> the core module. All these URLs are invalid. For SVN this could be assumed to
> be the right behaviour, for git and probably other SCMs this is not true. As
> a workaround I have to reconfigure the scm section (see
> https://github.com/mfriedenhagen/multi-module-sample/blob/multi-site-complex/core/pom.xml)
> in the modules like this:
> {code:xml}
>
> ${project.parent.scm.connection}
>
> ${project.parent.scm.developerConnection}
> ${project.parent.scm.url}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (MRELEASE-893) Put the tag in a property in :prepare
[ https://issues.apache.org/jira/browse/MRELEASE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MRELEASE-893. --- Resolution: Invalid > Put the tag in a property in :prepare > - > > Key: MRELEASE-893 > URL: https://issues.apache.org/jira/browse/MRELEASE-893 > Project: Maven Release Plugin > Issue Type: New Feature >Reporter: Benson Margulies > > Imagine another plugin that runs as part of the lifecycle after > release:prepare and which needs to know the scm tag name. It could use > maven-scm to try to guess what's most recent, but wouldn't it be easier if it > :prepare just set a property to the tag name that a subsequent plugin > execution could read? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SUREFIRE-945) Top of web page is pretty opaque
[ https://issues.apache.org/jira/browse/SUREFIRE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved SUREFIRE-945. --- Resolution: Invalid > Top of web page is pretty opaque > > > Key: SUREFIRE-945 > URL: https://issues.apache.org/jira/browse/SUREFIRE-945 > Project: Maven Surefire > Issue Type: Bug > Components: documentation >Reporter: Benson Margulies > > http://maven.apache.org/surefire/index.html is an about page with no > meaningful content and no navigation to other information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SUREFIRE-955) Surefire top-level website has obscure navigation (at least in Chrome)
[ https://issues.apache.org/jira/browse/SUREFIRE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved SUREFIRE-955. --- Resolution: Invalid > Surefire top-level website has obscure navigation (at least in Chrome) > -- > > Key: SUREFIRE-955 > URL: https://issues.apache.org/jira/browse/SUREFIRE-955 > Project: Maven Surefire > Issue Type: Bug > Components: documentation >Affects Versions: 2.13 >Reporter: Benson Margulies > > Browse to > http://maven.apache.org/surefire > And you will find yourself at an 'about' page with the only navigation being > top-level dropdown menus. Maybe this JIRA needs to be redirected to a skin, > but it took me several minutes to see how I could get from this page to > anywhere else, and I bet others will have the same problem. It also does not > comply with Apache trademark guidelines; there are no trademark notices for > Maven or Surefire. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1175) classpathDependencyExclude config in pom ineffective
Benson Margulies created SUREFIRE-1175:
--
Summary: classpathDependencyExclude config in pom ineffective
Key: SUREFIRE-1175
URL: https://issues.apache.org/jira/browse/SUREFIRE-1175
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.18.1
Reporter: Benson Margulies
I configure:
{code}
org.apache.karaf:org.apache.karaf.client
org.jboss.logging:jboss-logging
org.ops4j.pax.logging:pax-logging-service
org.ops4j.pax.logging:pax-logging-api
{code}
I see in the -X log, first:
{noformat}
org.apache.karaf:org.apache.karaf.client
org.jboss.logging:jboss-logging
org.ops4j.pax.logging:pax-logging-service
org.ops4j.pax.logging:pax-logging-api${maven.test.dependency.excludes}
{noformat}
and then:
{noformat}
[DEBUG] (s) classpathDependencyExcludes =
[org.apache.karaf:org.apache.karaf.client, org.jboss.logging:jboss-logging,
org.ops4j.pax.logging:pax-logging-service,
org.ops4j.pax.logging:pax-logging-api]
{noformat}
but then I get:
{noformat}
LF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/Users/benson/.m2/repository/org/apache/karaf/org.apache.karaf.client/4.0.1/org.apache.karaf.client-4.0.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/Users/benson/.m2/repository/org/ops4j/pax/logging/pax-logging-api/1.8.3/pax-logging-api-1.8.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/Users/benson/.m2/repository/org/slf4j/slf4j-log4j12/1.7.5/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SUREFIRE-1175) classpathDependencyExclude config in pom ineffective
[
https://issues.apache.org/jira/browse/SUREFIRE-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved SUREFIRE-1175.
Resolution: Invalid
> classpathDependencyExclude config in pom ineffective
>
>
> Key: SUREFIRE-1175
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1175
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.18.1
>Reporter: Benson Margulies
>
> I configure:
> {code}
>
>
> org.apache.karaf:org.apache.karaf.client
>
> org.jboss.logging:jboss-logging
>
> org.ops4j.pax.logging:pax-logging-service
>
> org.ops4j.pax.logging:pax-logging-api
>
> {code}
> I see in the -X log, first:
> {noformat}
>
>
> org.apache.karaf:org.apache.karaf.client
>
> org.jboss.logging:jboss-logging
>
> org.ops4j.pax.logging:pax-logging-service
>
> org.ops4j.pax.logging:pax-logging-api${maven.test.dependency.excludes}
> {noformat}
> and then:
> {noformat}
> [DEBUG] (s) classpathDependencyExcludes =
> [org.apache.karaf:org.apache.karaf.client, org.jboss.logging:jboss-logging,
> org.ops4j.pax.logging:pax-logging-service,
> org.ops4j.pax.logging:pax-logging-api]
> {noformat}
> but then I get:
> {noformat}
> LF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/Users/benson/.m2/repository/org/apache/karaf/org.apache.karaf.client/4.0.1/org.apache.karaf.client-4.0.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/Users/benson/.m2/repository/org/ops4j/pax/logging/pax-logging-api/1.8.3/pax-logging-api-1.8.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/Users/benson/.m2/repository/org/slf4j/slf4j-log4j12/1.7.5/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSCMPUB-20) Can build too-long command lines on MacOSX and fail
Benson Margulies created MSCMPUB-20: --- Summary: Can build too-long command lines on MacOSX and fail Key: MSCMPUB-20 URL: https://issues.apache.org/jira/browse/MSCMPUB-20 Project: Maven SCM Publish Plugin Issue Type: Bug Affects Versions: 1.1 Reporter: Benson Margulies In a large project: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm (default-cli) on project rbl: Failed to add new files to SCM: Exception while executing SCM command. Error while executing command. Error while executing process. Cannot run program "/bin/sh" (in directory "/Users/benson/x/rbl-je-2/target/scmpublish-checkout"): error=7, Argument list too long -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more
[
https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527440#comment-14527440
]
Benson Margulies edited comment on MCOMPILER-235 at 9/27/15 6:33 PM:
-
Using {{useIncrementalCompilation}} set explicitly to false as noted in
MCOMPILER-236 seems to be a workaround for this also.
MCOMPILER-157 makes a lot of sense, but causes headaches when used in a forked
build, e.g with Clover. (and {{useIncrementalCompilation}} does NOT help,
there)
was (Author: gjoseph):
Using {{useIncrementalCompilation}} as noted in MCOMPILER-236 seems to be a
workaround for this also.
MCOMPILER-157 makes a lot of sense, but causes headaches when used in a forked
build, e.g with Clover. (and {{useIncrementalCompilation}} does NOT help,
there)
> duplicate classes due to MCOMPILER-157 when compiler is called twice or more
>
>
> Key: MCOMPILER-235
> URL: https://issues.apache.org/jira/browse/MCOMPILER-235
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.2
> Environment: Maven 3.2.3
>Reporter: Arnaud HERITIER
> Attachments: MCOMPILER-235.zip
>
>
> I tried to upgrade our projects to use the compiler 3.2 and instead of 3.1
> Classical builds are ok but site builds are KO because for various reasons
> (reports) the lifecycle is forked and thus the compiler is called twice (or
> more) and fails because it finds duplicated classes
> Example :
> {code}
> [INFO]
>
> [INFO] Building eXo Commons - Common Services 4.1.x-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @
> commons-component-common ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @
> commons-component-common ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.3:create (default) @
> commons-component-common ---
> [INFO]
> [INFO] --- jacoco-maven-plugin:0.7.2.201409121644:prepare-agent
> (prepare-ut-agent) @ commons-component-common ---
> [INFO] argLine set to
> -javaagent:/srv/ciagent/workspace/commons-master-site/.repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.7.2.201409121644-runtime.jar=destfile=/srv/ciagent/workspace/commons-master-site/sources/commons-component-common/target/jacoco.exec,append=true
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @
> commons-component-common ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO] Copying 5 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @
> commons-component-common ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 97 source files to
> /srv/ciagent/workspace/commons-master-site/sources/commons-component-common/target/classes
> [WARNING] Supported source version 'RELEASE_5' from annotation processor
> 'org.chromattic.apt.ChromatticProcessor' less than -source '1.7'
> [INFO] About to process the type
> org.exoplatform.settings.chromattic.SettingsRoot
> [INFO] About to process the type
> org.exoplatform.settings.chromattic.SubContextEntity
> [INFO] About to process the type
> org.exoplatform.settings.chromattic.SimpleContextEntity
> [INFO] About to process the type
> org.exoplatform.settings.chromattic.ScopeEntity
> [INFO] About to process the type
> org.exoplatform.settings.chromattic.ContextEntity
> [INFO] Processing node type package org.exoplatform.settings.chromattic
> [INFO]
> /srv/ciagent/workspace/commons-master-site/sources/commons-component-common/src/main/java/org/exoplatform/services/user/UserStateService.java:
> Some input files use unchecked or unsafe operations.
> [INFO]
> /srv/ciagent/workspace/commons-master-site/sources/commons-component-common/src/main/java/org/exoplatform/services/user/UserStateService.java:
> Recompile with -Xlint:unchecked for details.
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @
> commons-component-common ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 19 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @
> commons-component-common ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 32 source files to
> /srv/ciagent/workspace/commons-master-site/sources/commons-component-common/target/test-classes
> [WARNING]
> /srv/ciagent/workspace/commons-master-site/sources/commons-component-common/src/test/java/org/exoplatform/commons/event/TestEventManager.java:[29,23]
> junit.fra
[jira] [Updated] (MASSEMBLY-780) Snappy supported
[ https://issues.apache.org/jira/browse/MASSEMBLY-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MASSEMBLY-780: --- Fix Version/s: 2.6 > Snappy supported > > > Key: MASSEMBLY-780 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-780 > Project: Maven Assembly Plugin > Issue Type: New Feature >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0.0, 2.6 > > > Plexus archiver supports snappy. So maven-assembly can, too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MDEP-509) dependency:tree should reveal 'optional'
Benson Margulies created MDEP-509: - Summary: dependency:tree should reveal 'optional' Key: MDEP-509 URL: https://issues.apache.org/jira/browse/MDEP-509 Project: Maven Dependency Plugin Issue Type: New Feature Reporter: Benson Margulies It would be helpful if dependency:tree would reveal the 'optional' status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MDEP-509) dependency:tree should reveal 'optional'
[ https://issues.apache.org/jira/browse/MDEP-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MDEP-509: - Assignee: Benson Margulies > dependency:tree should reveal 'optional' > > > Key: MDEP-509 > URL: https://issues.apache.org/jira/browse/MDEP-509 > Project: Maven Dependency Plugin > Issue Type: New Feature >Reporter: Benson Margulies >Assignee: Benson Margulies > > It would be helpful if dependency:tree would reveal the 'optional' status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MDEP-509) dependency:tree should reveal 'optional'
[ https://issues.apache.org/jira/browse/MDEP-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MDEP-509. --- Resolution: Fixed Fix Version/s: 3.0 r1707376 | bimargulies | 2015-10-07 15:58:29 -0400 (Wed, 07 Oct 2015) | 2 lines MDEP-509: add optional to the display of the tree when available. The change is in maven-dependency-tree. > dependency:tree should reveal 'optional' > > > Key: MDEP-509 > URL: https://issues.apache.org/jira/browse/MDEP-509 > Project: Maven Dependency Plugin > Issue Type: New Feature >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0 > > > It would be helpful if dependency:tree would reveal the 'optional' status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MDEP-509) dependency:tree and :list should reveal 'optional'
[ https://issues.apache.org/jira/browse/MDEP-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MDEP-509: -- Summary: dependency:tree and :list should reveal 'optional' (was: dependency:tree should reveal 'optional') > dependency:tree and :list should reveal 'optional' > -- > > Key: MDEP-509 > URL: https://issues.apache.org/jira/browse/MDEP-509 > Project: Maven Dependency Plugin > Issue Type: New Feature >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0 > > > It would be helpful if dependency:tree would reveal the 'optional' status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MDEP-509) dependency:tree and :list should reveal 'optional'
[ https://issues.apache.org/jira/browse/MDEP-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MDEP-509. - > dependency:tree and :list should reveal 'optional' > -- > > Key: MDEP-509 > URL: https://issues.apache.org/jira/browse/MDEP-509 > Project: Maven Dependency Plugin > Issue Type: New Feature >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 3.0 > > > It would be helpful if dependency:tree would reveal the 'optional' status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MASSEMBLY-784) Remove deprecated goals for 3.0
Benson Margulies created MASSEMBLY-784: -- Summary: Remove deprecated goals for 3.0 Key: MASSEMBLY-784 URL: https://issues.apache.org/jira/browse/MASSEMBLY-784 Project: Maven Assembly Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Benson Margulies The deprecated goals have been cluttering up the doc for years. Kill! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MASSEMBLY-784) Remove deprecated goals for 3.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MASSEMBLY-784: -- Assignee: Benson Margulies > Remove deprecated goals for 3.0 > --- > > Key: MASSEMBLY-784 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-784 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Benson Margulies >Assignee: Benson Margulies > > The deprecated goals have been cluttering up the doc for years. > Kill! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MASSEMBLY-784) Remove deprecated goals for 3.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MASSEMBLY-784. -- Resolution: Duplicate Someone else did this, but my search for a JIRA failed. > Remove deprecated goals for 3.0 > --- > > Key: MASSEMBLY-784 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-784 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Benson Margulies >Assignee: Benson Margulies > > The deprecated goals have been cluttering up the doc for years. > Kill! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MRELEASE-925) Old version of plexus utils forced here causes failures
Benson Margulies created MRELEASE-925: - Summary: Old version of plexus utils forced here causes failures Key: MRELEASE-925 URL: https://issues.apache.org/jira/browse/MRELEASE-925 Project: Maven Release Plugin Issue Type: Bug Reporter: Benson Margulies -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MRELEASE-925) Old version of plexus utils forced here causes failures
[
https://issues.apache.org/jira/browse/MRELEASE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MRELEASE-925:
--
Description:
The maven-release pom calls for plexus utils 3.0.10. This is considerably older
than the version included with Maven 3.2.5; in any case, it seems to be the
cause of the following explosion in mvn release:prepare, where, somehow, that
old plexus utils beats out the newer one in the dependency graph, and a
required class goes missing. To repro this, pretend to repeat the release
process for maven-plugins version 28.
{noformat}
mvn release:prepare with 3.2.5
➜ maven-plugins mvn release:prepare
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Apache Maven Plugins 28-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-release-plugin:2.5.2:prepare (default-cli) @ maven-plugins ---
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **/pom.xml.backup,
**/release.properties, **/pom.xml.branch, **/pom.xml.next,
**/pom.xml.releaseBackup, **/pom.xml.tag
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.163 s
[INFO] Finished at: 2015-10-10T20:18:26-04:00
[INFO] Final Memory: 18M/310M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare
(default-cli) on project maven-plugins: Execution default-cli of goal
org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare failed: A
required class was missing while executing
org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare:
org/codehaus/plexus/util/xml/pull/EntityReplacementMap
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-release-plugin:2.5.2
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/benson/.m2/repository/org/apache/maven/plugins/maven-release-plugin/2.5.2/maven-release-plugin-2.5.2.jar
[ERROR] urls[1] =
file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-manager/2.5.2/maven-release-manager-2.5.2.jar
[ERROR] urls[2] =
file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-api/2.5.2/maven-release-api-2.5.2.jar
[ERROR] urls[3] =
file:/Users/benson/.m2/repository/org/eclipse/aether/aether-util/1.0.0.v20140518/aether-util-1.0.0.v20140518.jar
[ERROR] urls[4] =
file:/Users/benson/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[5] =
file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-6/plexus-interactivity-api-1.0-alpha-6.jar
[ERROR] urls[6] =
file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] =
file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[8] =
file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[9] =
file:/Users/benson/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[ERROR] urls[10] =
file:/Users/benson/.m2/repository/org/apache/maven/shared/maven-invoker/2.2/maven-invoker-2.2.jar
[ERROR] urls[11] =
file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[12] =
file:/Users/benson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[13] =
file:/Users/benson/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
[ERROR] urls[14] =
file:/Users/benson/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar
[ERROR] urls[15] =
file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-providers-standard/1.9.4/maven-scm-providers-standard-1.9.4.pom
[ERROR] urls[16] =
file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-accurev/1.9.4/maven-scm-provider-accurev-1.9.4.jar
[ERROR] urls[17] =
file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-bazaar/1.9.4/maven-scm-provider-bazaar-1.9.4.jar
[ERROR] urls[18] =
file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-clearcase/1.9.4/maven-scm-provider-clearcase-1.9.4.jar
[ERROR] urls[19] =
file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvsexe/1.9.4/maven-scm-provider-cvsexe-1.9.4.jar
[ERROR] urls[20] =
file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.9.4/maven-scm-provider-cvs-commons-1.9.4.jar
[ERROR] urls[21] =
file:/Users/benson/
[jira] [Commented] (MRELEASE-925) Old version of plexus utils forced here causes failures
[
https://issues.apache.org/jira/browse/MRELEASE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952390#comment-14952390
]
Benson Margulies commented on MRELEASE-925:
---
It has been suggested that 3.0.15 is the right solution here.
> Old version of plexus utils forced here causes failures
> ---
>
> Key: MRELEASE-925
> URL: https://issues.apache.org/jira/browse/MRELEASE-925
> Project: Maven Release Plugin
> Issue Type: Bug
>Reporter: Benson Margulies
>
> The maven-release pom calls for plexus utils 3.0.10. This is considerably
> older than the version included with Maven 3.2.5; in any case, it seems to be
> the cause of the following explosion in mvn release:prepare, where, somehow,
> that old plexus utils beats out the newer one in the dependency graph, and a
> required class goes missing. To repro this, pretend to repeat the release
> process for maven-plugins version 28.
> {noformat}
> mvn release:prepare with 3.2.5
> ➜ maven-plugins mvn release:prepare
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Apache Maven Plugins 28-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.5.2:prepare (default-cli) @ maven-plugins
> ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **/pom.xml.backup,
> **/release.properties, **/pom.xml.branch, **/pom.xml.next,
> **/pom.xml.releaseBackup, **/pom.xml.tag
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.163 s
> [INFO] Finished at: 2015-10-10T20:18:26-04:00
> [INFO] Final Memory: 18M/310M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare
> (default-cli) on project maven-plugins: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare failed: A
> required class was missing while executing
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare:
> org/codehaus/plexus/util/xml/pull/EntityReplacementMap
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-release-plugin:2.5.2
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/benson/.m2/repository/org/apache/maven/plugins/maven-release-plugin/2.5.2/maven-release-plugin-2.5.2.jar
> [ERROR] urls[1] =
> file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-manager/2.5.2/maven-release-manager-2.5.2.jar
> [ERROR] urls[2] =
> file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-api/2.5.2/maven-release-api-2.5.2.jar
> [ERROR] urls[3] =
> file:/Users/benson/.m2/repository/org/eclipse/aether/aether-util/1.0.0.v20140518/aether-util-1.0.0.v20140518.jar
> [ERROR] urls[4] =
> file:/Users/benson/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[5] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-6/plexus-interactivity-api-1.0-alpha-6.jar
> [ERROR] urls[6] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[7] =
> file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[8] =
> file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[9] =
> file:/Users/benson/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[10] =
> file:/Users/benson/.m2/repository/org/apache/maven/shared/maven-invoker/2.2/maven-invoker-2.2.jar
> [ERROR] urls[11] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> [ERROR] urls[12] =
> file:/Users/benson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> [ERROR] urls[13] =
> file:/Users/benson/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
> [ERROR] urls[14] =
> file:/Users/benson/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar
> [ERROR] urls[15] =
> file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-providers-standard/1.9.4/maven-scm-providers-standard-1.9.4.pom
> [ERROR] urls[16] =
> file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-accurev/1.9.4/maven-scm-provider-accurev-1.9.4.jar
> [ERROR] urls[17]
[jira] [Resolved] (MRELEASE-907) Upgrade Plexus-utils to 3.0.15 to match with maven-scm
[ https://issues.apache.org/jira/browse/MRELEASE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MRELEASE-907. --- Resolution: Duplicate > Upgrade Plexus-utils to 3.0.15 to match with maven-scm > -- > > Key: MRELEASE-907 > URL: https://issues.apache.org/jira/browse/MRELEASE-907 > Project: Maven Release Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.5.1 >Reporter: Dan Tran > Fix For: 3.0 > > > For my case when release with p4maven, maven-release-plugin fails since it > plexus-utils is 3.0.10 with some classloader issue ( sorry, dont have the > stack trace) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHARED-420) Remove Maven2 specific code
[
https://issues.apache.org/jira/browse/MSHARED-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MSHARED-420:
-
Fix Version/s: (was: maven-dependency-tree-3.0)
Component/s: (was: maven-dependency-tree)
> Remove Maven2 specific code
> ---
>
> Key: MSHARED-420
> URL: https://issues.apache.org/jira/browse/MSHARED-420
> Project: Maven Shared Components
> Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>
> All the Apache Maven plugins have had their final Maven-2.2.1 compatible
> versions released.
> This makes it possible to drop old code in depending projects like this one.
> In this case: remove the {{org.apache.maven.shared.dependency.tree}} package.
> Plugins should switch to {{org.apache.maven.shared.dependency.graph}} which
> is more accurate since it uses Aether from the Maven runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSHARED-420) Remove Maven2 specific code
[
https://issues.apache.org/jira/browse/MSHARED-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MSHARED-420:
-
Component/s: maven-dependency-tree
> Remove Maven2 specific code
> ---
>
> Key: MSHARED-420
> URL: https://issues.apache.org/jira/browse/MSHARED-420
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>
> All the Apache Maven plugins have had their final Maven-2.2.1 compatible
> versions released.
> This makes it possible to drop old code in depending projects like this one.
> In this case: remove the {{org.apache.maven.shared.dependency.tree}} package.
> Plugins should switch to {{org.apache.maven.shared.dependency.graph}} which
> is more accurate since it uses Aether from the Maven runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSHARED-420) Remove Maven2 specific code
[
https://issues.apache.org/jira/browse/MSHARED-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952471#comment-14952471
]
Benson Margulies commented on MSHARED-420:
--
r1685420 | rfscholte | 2015-06-14 12:17:07 -0400 (Sun, 14 Jun 2015) | 1 line
MSHARED-420: Remove Maven2 specific code
> Remove Maven2 specific code
> ---
>
> Key: MSHARED-420
> URL: https://issues.apache.org/jira/browse/MSHARED-420
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: maven-dependency-tree-3.0
>
>
> All the Apache Maven plugins have had their final Maven-2.2.1 compatible
> versions released.
> This makes it possible to drop old code in depending projects like this one.
> In this case: remove the {{org.apache.maven.shared.dependency.tree}} package.
> Plugins should switch to {{org.apache.maven.shared.dependency.graph}} which
> is more accurate since it uses Aether from the Maven runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (MSHARED-420) Remove Maven2 specific code
[
https://issues.apache.org/jira/browse/MSHARED-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved MSHARED-420.
--
Resolution: Fixed
Fix Version/s: maven-dependency-tree-3.0
> Remove Maven2 specific code
> ---
>
> Key: MSHARED-420
> URL: https://issues.apache.org/jira/browse/MSHARED-420
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: maven-dependency-tree-3.0
>
>
> All the Apache Maven plugins have had their final Maven-2.2.1 compatible
> versions released.
> This makes it possible to drop old code in depending projects like this one.
> In this case: remove the {{org.apache.maven.shared.dependency.tree}} package.
> Plugins should switch to {{org.apache.maven.shared.dependency.graph}} which
> is more accurate since it uses Aether from the Maven runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MSHARED-420) Remove Maven2 specific code
[
https://issues.apache.org/jira/browse/MSHARED-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MSHARED-420.
> Remove Maven2 specific code
> ---
>
> Key: MSHARED-420
> URL: https://issues.apache.org/jira/browse/MSHARED-420
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-tree
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: maven-dependency-tree-3.0
>
>
> All the Apache Maven plugins have had their final Maven-2.2.1 compatible
> versions released.
> This makes it possible to drop old code in depending projects like this one.
> In this case: remove the {{org.apache.maven.shared.dependency.tree}} package.
> Plugins should switch to {{org.apache.maven.shared.dependency.graph}} which
> is more accurate since it uses Aether from the Maven runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (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
]
Benson Margulies reopened SCM-775:
--
I reverted r1677765 of maven-release to make it releasable. You can re-apply it
when SCM is released.
> 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] (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
]
Benson Margulies 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-925) Old version of plexus utils forced here causes failures
[
https://issues.apache.org/jira/browse/MRELEASE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved MRELEASE-925.
---
Resolution: Fixed
Assignee: Benson Margulies
I've changed the version of plexus-utils in the dependencyManagement section.
> Old version of plexus utils forced here causes failures
> ---
>
> Key: MRELEASE-925
> URL: https://issues.apache.org/jira/browse/MRELEASE-925
> Project: Maven Release Plugin
> Issue Type: Bug
>Reporter: Benson Margulies
>Assignee: Benson Margulies
>
> The maven-release pom calls for plexus utils 3.0.10. This is considerably
> older than the version included with Maven 3.2.5; in any case, it seems to be
> the cause of the following explosion in mvn release:prepare, where, somehow,
> that old plexus utils beats out the newer one in the dependency graph, and a
> required class goes missing. To repro this, pretend to repeat the release
> process for maven-plugins version 28.
> {noformat}
> mvn release:prepare with 3.2.5
> ➜ maven-plugins mvn release:prepare
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Apache Maven Plugins 28-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.5.2:prepare (default-cli) @ maven-plugins
> ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **/pom.xml.backup,
> **/release.properties, **/pom.xml.branch, **/pom.xml.next,
> **/pom.xml.releaseBackup, **/pom.xml.tag
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.163 s
> [INFO] Finished at: 2015-10-10T20:18:26-04:00
> [INFO] Final Memory: 18M/310M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare
> (default-cli) on project maven-plugins: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare failed: A
> required class was missing while executing
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare:
> org/codehaus/plexus/util/xml/pull/EntityReplacementMap
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-release-plugin:2.5.2
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/benson/.m2/repository/org/apache/maven/plugins/maven-release-plugin/2.5.2/maven-release-plugin-2.5.2.jar
> [ERROR] urls[1] =
> file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-manager/2.5.2/maven-release-manager-2.5.2.jar
> [ERROR] urls[2] =
> file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-api/2.5.2/maven-release-api-2.5.2.jar
> [ERROR] urls[3] =
> file:/Users/benson/.m2/repository/org/eclipse/aether/aether-util/1.0.0.v20140518/aether-util-1.0.0.v20140518.jar
> [ERROR] urls[4] =
> file:/Users/benson/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[5] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-6/plexus-interactivity-api-1.0-alpha-6.jar
> [ERROR] urls[6] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[7] =
> file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[8] =
> file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[9] =
> file:/Users/benson/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[10] =
> file:/Users/benson/.m2/repository/org/apache/maven/shared/maven-invoker/2.2/maven-invoker-2.2.jar
> [ERROR] urls[11] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> [ERROR] urls[12] =
> file:/Users/benson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> [ERROR] urls[13] =
> file:/Users/benson/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
> [ERROR] urls[14] =
> file:/Users/benson/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar
> [ERROR] urls[15] =
> file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-providers-standard/1.9.4/maven-scm-providers-standard-1.9.4.pom
> [ERROR] urls[16] =
> file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-accurev/1.9.4/m
[jira] [Updated] (MRELEASE-925) Old version of plexus utils forced here causes failures
[
https://issues.apache.org/jira/browse/MRELEASE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MRELEASE-925:
--
Fix Version/s: 2.5.3
> Old version of plexus utils forced here causes failures
> ---
>
> Key: MRELEASE-925
> URL: https://issues.apache.org/jira/browse/MRELEASE-925
> Project: Maven Release Plugin
> Issue Type: Bug
>Reporter: Benson Margulies
>Assignee: Benson Margulies
> Fix For: 2.5.3
>
>
> The maven-release pom calls for plexus utils 3.0.10. This is considerably
> older than the version included with Maven 3.2.5; in any case, it seems to be
> the cause of the following explosion in mvn release:prepare, where, somehow,
> that old plexus utils beats out the newer one in the dependency graph, and a
> required class goes missing. To repro this, pretend to repeat the release
> process for maven-plugins version 28.
> {noformat}
> mvn release:prepare with 3.2.5
> ➜ maven-plugins mvn release:prepare
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Apache Maven Plugins 28-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.5.2:prepare (default-cli) @ maven-plugins
> ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **/pom.xml.backup,
> **/release.properties, **/pom.xml.branch, **/pom.xml.next,
> **/pom.xml.releaseBackup, **/pom.xml.tag
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.163 s
> [INFO] Finished at: 2015-10-10T20:18:26-04:00
> [INFO] Final Memory: 18M/310M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare
> (default-cli) on project maven-plugins: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare failed: A
> required class was missing while executing
> org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare:
> org/codehaus/plexus/util/xml/pull/EntityReplacementMap
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-release-plugin:2.5.2
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/benson/.m2/repository/org/apache/maven/plugins/maven-release-plugin/2.5.2/maven-release-plugin-2.5.2.jar
> [ERROR] urls[1] =
> file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-manager/2.5.2/maven-release-manager-2.5.2.jar
> [ERROR] urls[2] =
> file:/Users/benson/.m2/repository/org/apache/maven/release/maven-release-api/2.5.2/maven-release-api-2.5.2.jar
> [ERROR] urls[3] =
> file:/Users/benson/.m2/repository/org/eclipse/aether/aether-util/1.0.0.v20140518/aether-util-1.0.0.v20140518.jar
> [ERROR] urls[4] =
> file:/Users/benson/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[5] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-6/plexus-interactivity-api-1.0-alpha-6.jar
> [ERROR] urls[6] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[7] =
> file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[8] =
> file:/Users/benson/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[9] =
> file:/Users/benson/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[10] =
> file:/Users/benson/.m2/repository/org/apache/maven/shared/maven-invoker/2.2/maven-invoker-2.2.jar
> [ERROR] urls[11] =
> file:/Users/benson/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> [ERROR] urls[12] =
> file:/Users/benson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> [ERROR] urls[13] =
> file:/Users/benson/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
> [ERROR] urls[14] =
> file:/Users/benson/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar
> [ERROR] urls[15] =
> file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-providers-standard/1.9.4/maven-scm-providers-standard-1.9.4.pom
> [ERROR] urls[16] =
> file:/Users/benson/.m2/repository/org/apache/maven/scm/maven-scm-provider-accurev/1.9.4/maven-scm-provider-accurev-1.9.4.jar
> [ERROR] urls[17] =
> file:/Users/benson/.m
[jira] [Commented] (SUREFIRE-1034) dependencesToScan versus classifiers: what's the scoop?
[ https://issues.apache.org/jira/browse/SUREFIRE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043882#comment-15043882 ] Benson Margulies commented on SUREFIRE-1034: I don't have anything around either, and 1004 was created specifically to hold the fix. So I don't see why you reopened this. > dependencesToScan versus classifiers: what's the scoop? > --- > > Key: SUREFIRE-1034 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1034 > Project: Maven Surefire > Issue Type: Bug >Reporter: Benson Margulies > Fix For: 3.0 > > > # The doc could really use an example of dependenciesToScan > # The doc should tell me the syntax for using classifiers > # if classifiers don't work, please make them work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] Created: (SUREFIRE-731) Cannot build 2.8.1 from tag
Cannot build 2.8.1 from tag --- Key: SUREFIRE-731 URL: http://jira.codehaus.org/browse/SUREFIRE-731 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.8.1 Reporter: Benson Margulies I checked out the 2.8.1 tag of the surefire plugin from svn, and tried to run 'mvn install' with maven 3.0.3. I was rewarded with: Downloading: http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-shadefire/2.8.1/surefire-shadefire-2.8.1.pom [WARNING] The POM for org.apache.maven.surefire:surefire-shadefire:jar:2.8.1 is missing, no dependency information available Downloading: http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-shadefire/2.8.1/surefire-shadefire-2.8.1.jar -- 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-731) Cannot build 2.8.1 from tag
[ http://jira.codehaus.org/browse/SUREFIRE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264487#action_264487 ] Benson Margulies commented on SUREFIRE-731: --- It looks to me as if the bottom line here is that the plugin has to be built from the directory one up. I'll submit a patch to improve the doc. > Cannot build 2.8.1 from tag > --- > > Key: SUREFIRE-731 > URL: http://jira.codehaus.org/browse/SUREFIRE-731 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.8.1 >Reporter: Benson Margulies > > I checked out the 2.8.1 tag of the surefire plugin from svn, and tried to run > 'mvn install' with maven 3.0.3. > I was rewarded with: > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-shadefire/2.8.1/surefire-shadefire-2.8.1.pom > [WARNING] The POM for org.apache.maven.surefire:surefire-shadefire:jar:2.8.1 > is missing, no dependency information available > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-shadefire/2.8.1/surefire-shadefire-2.8.1.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-731) Cannot build 2.8.1 from tag
[ http://jira.codehaus.org/browse/SUREFIRE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated SUREFIRE-731: -- Attachment: SUREFIRE-731.patch Here's some doc to reduce the possibility of confusion. > Cannot build 2.8.1 from tag > --- > > Key: SUREFIRE-731 > URL: http://jira.codehaus.org/browse/SUREFIRE-731 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.8.1 >Reporter: Benson Margulies > Attachments: SUREFIRE-731.patch > > > I checked out the 2.8.1 tag of the surefire plugin from svn, and tried to run > 'mvn install' with maven 3.0.3. > I was rewarded with: > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-shadefire/2.8.1/surefire-shadefire-2.8.1.pom > [WARNING] The POM for org.apache.maven.surefire:surefire-shadefire:jar:2.8.1 > is missing, no dependency information available > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-shadefire/2.8.1/surefire-shadefire-2.8.1.jar -- 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-5076) Improve SEO of documentation of lifecycle.xml
Improve SEO of documentation of lifecycle.xml - Key: MNG-5076 URL: http://jira.codehaus.org/browse/MNG-5076 Project: Maven 2 & 3 Issue Type: Improvement Components: Plugins and Lifecycle Affects Versions: 2.2.1 Reporter: Benson Margulies I will attach a patch. If someone tells me the corresponding mdo file for 3.x, I'll get that too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5076) Improve SEO of documentation of lifecycle.xml
[ http://jira.codehaus.org/browse/MNG-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MNG-5076: -- Attachment: MNG-5076.patch Improvement to description to make google more likely to find it. > Improve SEO of documentation of lifecycle.xml > - > > Key: MNG-5076 > URL: http://jira.codehaus.org/browse/MNG-5076 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.2.1 >Reporter: Benson Margulies > Attachments: MNG-5076.patch > > > I will attach a patch. If someone tells me the corresponding mdo file for > 3.x, I'll get that too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5076) Improve SEO of documentation of lifecycle.xml
[ http://jira.codehaus.org/browse/MNG-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264548#action_264548 ] Benson Margulies commented on MNG-5076: --- Hmm. Do you think Google does the right thing if you search for 'lifecycle.xml' if the occurrence on the page is /a/b/c/lifecycle.xml? Is there any way in the mdo file to add to the meta keywords? > Improve SEO of documentation of lifecycle.xml > - > > Key: MNG-5076 > URL: http://jira.codehaus.org/browse/MNG-5076 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.2.1 >Reporter: Benson Margulies >Assignee: Herve Boutemy > Fix For: 2.2.2, 3.0.4 > > Attachments: MNG-5076.patch > > > I will attach a patch. If someone tells me the corresponding mdo file for > 3.x, I'll get that too. -- 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: (MDEPLOY-132) Discrepancy between pom syntax for artifacts and deploy:deploy-file parameters
Discrepancy between pom syntax for artifacts and deploy:deploy-file parameters -- Key: MDEPLOY-132 URL: http://jira.codehaus.org/browse/MDEPLOY-132 Project: Maven 2.x Deploy Plugin Issue Type: Bug Components: deploy:deploy-file Affects Versions: 2.6 Reporter: Benson Margulies It is confusing, at least to me, that the pom says, 'foo' but the deploy-file parameter is -Dpackaging=. I'll post up a patch to add -Dtype= if I get the slightest encouragement here. -- 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: (MCHANGES-247) StatusIds don't end up in the URL
StatusIds don't end up in the URL
-
Key: MCHANGES-247
URL: http://jira.codehaus.org/browse/MCHANGES-247
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.5
Reporter: Benson Margulies
Running announcement-generate. Note from the -X output blob here that I have
selected more statusIds than 'Closed'. But then see the URL from a little
further down the trace, where statusIds=6.
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-changes-plugin:2.5:announcement-generate' -->
[DEBUG] (s) artifactId = basis-parent
[DEBUG] (f) basedir = /Users/benson/x/maven-support/basis-parent/trunk
[DEBUG] (s) developmentTeam = Common Parent for Basis Maven Projects team
[DEBUG] (s) finalName = basis-parent-26-SNAPSHOT
[DEBUG] (f) generateJiraAnnouncement = false
[DEBUG] (s) groupId = com.basistech
[DEBUG] (f) issueManagementSystems = [JIRA]
[DEBUG] (f) jiraMerge = false
[DEBUG] (f) jiraPassword = xx
[DEBUG] (f) jiraUser = maven-reporting
[DEBUG] (f) jiraXML =
/Users/benson/x/maven-support/basis-parent/trunk/target/jira-announcement.xml
[DEBUG] (f) mavenSession = org.apache.maven.execution.MavenSession@4e3e97cd
[DEBUG] (f) maxEntries = 25
[DEBUG] (s) outputDirectory =
/Users/benson/x/maven-support/basis-parent/trunk/target/announcement
[DEBUG] (s) packaging = pom
[DEBUG] (f) project = MavenProject: com.basistech:basis-parent:26-SNAPSHOT @
/Users/benson/x/maven-support/basis-parent/trunk/pom.xml
[DEBUG] (f) resolutionIds = Fixed
[DEBUG] (f) runOnlyAtExecutionRoot = false
[DEBUG] (f) settings = org.apache.maven.settings.Settings@7fb6a1c4
[DEBUG] (f) statusIds = Resolved,Closed
[DEBUG] (f) template = announcement.vm
[DEBUG] (f) templateDirectory = org/apache/maven/plugin/announcement
[DEBUG] (f) tracQuery = order=id
[DEBUG] (s) url = http://hudson.basistech.net:8280/projects/basis-parent
[DEBUG] (s) version = 26-SNAPSHOT
[DEBUG] (s) xmlPath =
/Users/benson/x/maven-support/basis-parent/trunk/src/changes/changes.xml
...
[DEBUG] Found the pid 10300 at
http://jira.basistech.net:8080/browse/MAVEN/component/10784
[ERROR] maven-changes-plugin: None of the configured sortColumnNames 'null' are
correct.
[DEBUG] download jira issues from url
http://jira.basistech.net:8080/secure/IssueNavigator.jspa?view=rss&pid=10300&statusIds=6&resolutionIds=1&tempMax=25&reset=true&decorator=none
[INFO] Downloading from JIRA at:
http://jira.basistech.net:8080/secure/IssueNavigator.jspa?view=rss&pid=10300&statusIds=6&resolutionIds=1&tempMax=25&reset=true&decorator=none
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-248) Support custom jira status ids, please
Support custom jira status ids, please -- Key: MCHANGES-248 URL: http://jira.codehaus.org/browse/MCHANGES-248 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: jira Affects Versions: 2.5 Reporter: Benson Margulies It is possible to add status IDs to JIRA. e.g., Verified. There is currently no way to make these work with the changes plugin. -- 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: (MCHANGES-249) The jira downloaded used for announcements only supports 'closed'
The jira downloaded used for announcements only supports 'closed' - Key: MCHANGES-249 URL: http://jira.codehaus.org/browse/MCHANGES-249 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: announcement Affects Versions: 2.5 Reporter: Benson Margulies org.apache.maven.plugin.announcement.JiraDownloader only puts 'Closed' in the statusMap, so it's not possible to specify, say, Resolved,Closed. Why are there two of these, anyhow? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-249) The jira downloaded used for announcements only supports 'closed'
[ http://jira.codehaus.org/browse/MCHANGES-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MCHANGES-249: -- Attachment: MCHANGES-249.patch Remove the extra JiraDownloader that has no effect except to prevent announcements of unclosed issues. > The jira downloaded used for announcements only supports 'closed' > - > > Key: MCHANGES-249 > URL: http://jira.codehaus.org/browse/MCHANGES-249 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: announcement >Affects Versions: 2.5 >Reporter: Benson Margulies > Attachments: MCHANGES-249.patch > > > org.apache.maven.plugin.announcement.JiraDownloader only puts 'Closed' in the > statusMap, so it's not possible to specify, say, Resolved,Closed. > Why are there two of these, anyhow? -- 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: (MCHANGES-250) ccAddresses and bccAddresses should not be 'required'
ccAddresses and bccAddresses should not be 'required' - Key: MCHANGES-250 URL: http://jira.codehaus.org/browse/MCHANGES-250 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.5 Reporter: Benson Margulies It seems unkind and unnecessary to require the cc and bcc. If one doesn't need them, why require them? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-248) Support custom jira status ids, please
[ http://jira.codehaus.org/browse/MCHANGES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MCHANGES-248: -- Attachment: MCHANGES-248.patch This patch allows numeric statusId values. > Support custom jira status ids, please > -- > > Key: MCHANGES-248 > URL: http://jira.codehaus.org/browse/MCHANGES-248 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: jira >Affects Versions: 2.5 >Reporter: Benson Margulies > Attachments: MCHANGES-248.patch > > > It is possible to add status IDs to JIRA. e.g., Verified. There is currently > no way to make these work with the changes plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-250) ccAddresses and bccAddresses should not be 'required'
[ http://jira.codehaus.org/browse/MCHANGES-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MCHANGES-250: -- Attachment: MCHANGES-250.patch > ccAddresses and bccAddresses should not be 'required' > - > > Key: MCHANGES-250 > URL: http://jira.codehaus.org/browse/MCHANGES-250 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.5 >Reporter: Benson Margulies > Attachments: MCHANGES-250.patch > > > It seems unkind and unnecessary to require the cc and bcc. If one doesn't > need them, why require them? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-251) Tolerate novel issue types
Tolerate novel issue types --- Key: MCHANGES-251 URL: http://jira.codehaus.org/browse/MCHANGES-251 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.5 Reporter: Benson Margulies Attachments: types.patch If the plugin encounters an issue with a type it's never met, the issue gets dropped on the ground. Calling such issues 'fix' results in something useful in the announcement, even if it's not ideal. -- 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: (MCHANGES-250) ccAddresses and bccAddresses should not be 'required'
[ http://jira.codehaus.org/browse/MCHANGES-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268525#action_268525 ] Benson Margulies commented on MCHANGES-250: --- The code would crash without them. This looked neater than a bunch of checks for null. Unless by default maven injects empty lists :-) > ccAddresses and bccAddresses should not be 'required' > - > > Key: MCHANGES-250 > URL: http://jira.codehaus.org/browse/MCHANGES-250 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.5 >Reporter: Benson Margulies > Attachments: MCHANGES-250.patch > > > It seems unkind and unnecessary to require the cc and bcc. If one doesn't > need them, why require them? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-249) The jira downloaded used for announcements only supports 'closed'
[ http://jira.codehaus.org/browse/MCHANGES-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268527#action_268527 ] Benson Margulies commented on MCHANGES-249: --- Dennis, I should have edited out the question of 'why two?' There are two because someone wanted to prevent anyone from making announcements on any issues other than closed. My patch is to abolish that restriction. > The jira downloaded used for announcements only supports 'closed' > - > > Key: MCHANGES-249 > URL: http://jira.codehaus.org/browse/MCHANGES-249 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: announcement >Affects Versions: 2.5 >Reporter: Benson Margulies > Attachments: MCHANGES-249.patch > > > org.apache.maven.plugin.announcement.JiraDownloader only puts 'Closed' in the > statusMap, so it's not possible to specify, say, Resolved,Closed. > Why are there two of these, anyhow? -- 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: (MCHANGES-249) The jira downloaded used for announcements only supports 'closed'
[ http://jira.codehaus.org/browse/MCHANGES-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268529#action_268529 ] Benson Margulies commented on MCHANGES-249: --- Yes. If the default is Closed, then my change is backward-compatible except .. the old behavior was to silently discard unrecognized statusses. Anyone who wrote, say, 'Closed,Resolved' will now find themselves looking more issues in their announcement. > The jira downloaded used for announcements only supports 'closed' > - > > Key: MCHANGES-249 > URL: http://jira.codehaus.org/browse/MCHANGES-249 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: announcement >Affects Versions: 2.5 >Reporter: Benson Margulies > Attachments: MCHANGES-249.patch > > > org.apache.maven.plugin.announcement.JiraDownloader only puts 'Closed' in the > statusMap, so it's not possible to specify, say, Resolved,Closed. > Why are there two of these, anyhow? -- 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: (MSHADE-99) Very wierd error message, "unknown local variable"
Very wierd error message, "unknown local variable"
--
Key: MSHADE-99
URL: http://jira.codehaus.org/browse/MSHADE-99
Project: Maven 2.x Shade Plugin
Issue Type: Bug
Affects Versions: 1.4
Reporter: Benson Margulies
{noformat}
[INFO] [shade:shade {execution: shade}]
[INFO] Including com.basistech.rse:rse-generic:jar:1.8.100.2-SNAPSHOT in the
shaded jar.
[INFO] Including com.basistech.rse:rlp-common:jar:1.8.100.2-SNAPSHOT in the
shaded jar.
[INFO] Excluding com.basistech:common:jar:13 from the shaded jar.
[INFO] Including com.ibm.icu:icu4j:jar:4.6.1 in the shaded jar.
[INFO] Including com.basistech.rse:rlp-breaks:jar:1.8.100.2-SNAPSHOT in the
shaded jar.
[INFO] Including com.basistech.rse:rlp-segmentation:jar:1.8.100.2-SNAPSHOT in
the shaded jar.
[INFO] Including com.basistech:ap-segmentation-features:jar:25 in the shaded
jar.
[INFO] Including commons-io:commons-io:jar:1.4 in the shaded jar.
[INFO] Including it.unimi.dsi:fastutil:jar:6.3 in the shaded jar.
[INFO] Including com.basistech.rse:rlp-hebrew-breaks:jar:1.8.100.2-SNAPSHOT in
the shaded jar.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error creating shaded jar: Unknown local variable 5
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 minute 12 seconds
[INFO] Finished at: Thu May 26 08:37:22 EDT 2011
[INFO] Final Memory: 53M/107M
[INFO]
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-99) Very wierd error message, "unknown local variable"
[
http://jira.codehaus.org/browse/MSHADE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268612#action_268612
]
Benson Margulies commented on MSHADE-99:
{noformat}
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error creating shaded
jar: Unknown local variable 5
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
shaded jar: Unknown local variable 5
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:503)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: java.lang.IllegalStateException: Unknown local variable 5
at org.objectweb.asm.commons.LocalVariablesSorter.remap(Unknown Source)
at org.objectweb.asm.commons.LocalVariablesSorter.visitFrame(Unknown
Source)
at org.objectweb.asm.commons.RemappingMethodAdapter.visitFrame(Unknown
Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at
org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:267)
at
org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:148)
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:444)
... 19 more
{noformat}
> Very wierd error message, "unknown local variable"
> --
>
> Key: MSHADE-99
> URL: http://jira.codehaus.org/browse/MSHADE-99
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.4
>Reporter: Benson Margulies
>
> {noformat}
> [INFO] [shade:shade {execution: shade}]
> [INFO] Including com.basistech.rse:rse-generic:jar:1.8.100.2-SNAPSHOT in the
> shaded jar.
> [INFO] Including com.basistech.rse:rlp-common:jar:1.8.100.2-SNAPSHOT in the
> shaded jar.
> [INFO] Excluding com.basistech:common:jar:13 from the shaded jar.
> [INFO] Including com.ibm.icu:icu4j:jar:4.6.1 in the shaded jar.
> [INFO] Including com.basistech.rse:rlp-breaks:jar:1.8.100.2-SNAPSHOT in the
> shaded jar.
> [INFO] Including com.basistech.rse:rlp-segmentation:jar:1.8.100.2-SNAPSHOT in
> the shaded jar.
> [INFO] Including com.basistech:ap-segmentation-features:jar:25 in the shaded
> jar.
> [INFO] Including commons-io:commons-io:jar:1.4 in the shaded jar.
> [INFO] Including it.unimi.dsi:fastutil:jar:6.3 in the shaded jar.
> [INFO] Including com.basistech.rse:rlp-hebrew-breaks:jar:1.8.100.2-SNAPSHOT
> in the shaded jar.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error creating shaded jar: Unknown local variable 5
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total ti
[jira] Created: (MPIR-225) Change 'developer access', optionally, to show trunk, not tag URL
Change 'developer access', optionally, to show trunk, not tag URL - Key: MPIR-225 URL: http://jira.codehaus.org/browse/MPIR-225 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: scm Affects Versions: 2.4 Reporter: Benson Margulies When I go to look at the scm report for the SVN url, I am getting ready to prepare to fix something. In that case, I essentially never want the tagged version of the release. I want the 'corresponding development branch'. This is not a concept currently modelled in maven at all. At very least, I'd like to add a config property to this plugin that specifies that URL, and then add it as an additional clause in the output. Obviously, it's would be slicker in some respects to add another something to the pom, but that's a much bigger deal (though there might be other uses for it). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSHADE-99) Very wierd error message, "unknown local variable"
[
http://jira.codehaus.org/browse/MSHADE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MSHADE-99:
---
Attachment: MSHADE-99.patch
Updating to current asm fixed this. I also added some error handling to make
problems like this easier to cope with.
> Very wierd error message, "unknown local variable"
> --
>
> Key: MSHADE-99
> URL: http://jira.codehaus.org/browse/MSHADE-99
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.4
>Reporter: Benson Margulies
> Attachments: MSHADE-99.patch
>
>
> {noformat}
> [INFO] [shade:shade {execution: shade}]
> [INFO] Including com.basistech.rse:rse-generic:jar:1.8.100.2-SNAPSHOT in the
> shaded jar.
> [INFO] Including com.basistech.rse:rlp-common:jar:1.8.100.2-SNAPSHOT in the
> shaded jar.
> [INFO] Excluding com.basistech:common:jar:13 from the shaded jar.
> [INFO] Including com.ibm.icu:icu4j:jar:4.6.1 in the shaded jar.
> [INFO] Including com.basistech.rse:rlp-breaks:jar:1.8.100.2-SNAPSHOT in the
> shaded jar.
> [INFO] Including com.basistech.rse:rlp-segmentation:jar:1.8.100.2-SNAPSHOT in
> the shaded jar.
> [INFO] Including com.basistech:ap-segmentation-features:jar:25 in the shaded
> jar.
> [INFO] Including commons-io:commons-io:jar:1.4 in the shaded jar.
> [INFO] Including it.unimi.dsi:fastutil:jar:6.3 in the shaded jar.
> [INFO] Including com.basistech.rse:rlp-hebrew-breaks:jar:1.8.100.2-SNAPSHOT
> in the shaded jar.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error creating shaded jar: Unknown local variable 5
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 1 minute 12 seconds
> [INFO] Finished at: Thu May 26 08:37:22 EDT 2011
> [INFO] Final Memory: 53M/107M
> [INFO]
>
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-225) Change 'developer access', optionally, to show trunk, not tag URL
[ http://jira.codehaus.org/browse/MPIR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268644#action_268644 ] Benson Margulies commented on MPIR-225: --- That replaces the dev url with the one you specify. On the other hand, since no-one should ever be modifying the tag, perhaps that's the right answer. > Change 'developer access', optionally, to show trunk, not tag URL > - > > Key: MPIR-225 > URL: http://jira.codehaus.org/browse/MPIR-225 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.4 >Reporter: Benson Margulies > > When I go to look at the scm report for the SVN url, I am getting ready to > prepare to fix something. In that case, I essentially never want the tagged > version of the release. I want the 'corresponding development branch'. This > is not a concept currently modelled in maven at all. > At very least, I'd like to add a config property to this plugin that > specifies that URL, and then add it as an additional clause in the output. > Obviously, it's would be slicker in some respects to add another something to > the pom, but that's a much bigger deal (though there might be other uses for > it). -- 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-5108) Useful information on property inheritance control is not in the pom doc
Useful information on property inheritance control is not in the pom doc Key: MNG-5108 URL: http://jira.codehaus.org/browse/MNG-5108 Project: Maven 2 & 3 Issue Type: Improvement Components: Documentation: General Affects Versions: 3.0.3 Reporter: Benson Margulies This handy page at sonatype contains data that, I submit, should be part of the core maven pom reference documentation. http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-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
[jira] Closed: (MDEPLOY-132) Discrepancy between pom syntax for artifacts and deploy:deploy-file parameters
[ http://jira.codehaus.org/browse/MDEPLOY-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MDEPLOY-132. Resolution: Fixed Fix Version/s: 2.7 1131407. Improved documentation. > Discrepancy between pom syntax for artifacts and deploy:deploy-file parameters > -- > > Key: MDEPLOY-132 > URL: http://jira.codehaus.org/browse/MDEPLOY-132 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug > Components: deploy:deploy-file >Affects Versions: 2.6 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.7 > > > It is confusing, at least to me, that the pom says, 'foo' but > the deploy-file parameter is -Dpackaging=. I'll post up a patch to add > -Dtype= if I get the slightest encouragement here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-254) Example doesn't work - spaces not allowed in statusIds and resolutionIds after a comma
[
http://jira.codehaus.org/browse/MCHANGES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MCHANGES-254:
--
Fix Version/s: 2.6
> Example doesn't work - spaces not allowed in statusIds and resolutionIds
> after a comma
> --
>
> Key: MCHANGES-254
> URL: http://jira.codehaus.org/browse/MCHANGES-254
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html#Using_Maven_syntax
> gives the following examples:
> {quote}
>
> Closed
> Resolved, Closed
> Bug, New Feature, Improvement, Wish
>
> {quote}
> However, spaces are not always allowed, they can cause the field to be
> ignored.
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> In particular, the example from the web page does not work.
> Note that the typeIds field does appear to allow leading space after a comma.
> The resolutionIds field does not.
> Since spaces are sometimes allowed, may I suggest the code is fixed rather
> than the documentation?
--
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: (MCHANGES-255) fixVersionIds supports human readable display versions in JIRA 4
[ http://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269541#action_269541 ] Benson Margulies commented on MCHANGES-255: --- Once could, but there's no JIRA API to obtain them, and it would be a big job to add jira-4-specific querying. Obtaining them is a matter of waving your mouse over an obscure location in jira. > fixVersionIds supports human readable display versions in JIRA 4 > > > Key: MCHANGES-255 > URL: http://jira.codehaus.org/browse/MCHANGES-255 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: SebbASF > > http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds > says > bq. Sets the fix version id(s) that you want to limit your report to include. > These are JIRA's internal version ids, NOT the human readable display ones. > This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human > readable versions. > It would be helpful to document how to obtain the internal version ids, if > these are still supported or needed. -- 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: (MCHANGES-254) Example doesn't work - spaces not allowed in statusIds and resolutionIds after a comma
[
http://jira.codehaus.org/browse/MCHANGES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-254.
-
Resolution: Fixed
1131414
> Example doesn't work - spaces not allowed in statusIds and resolutionIds
> after a comma
> --
>
> Key: MCHANGES-254
> URL: http://jira.codehaus.org/browse/MCHANGES-254
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html#Using_Maven_syntax
> gives the following examples:
> {quote}
>
> Closed
> Resolved, Closed
> Bug, New Feature, Improvement, Wish
>
> {quote}
> However, spaces are not always allowed, they can cause the field to be
> ignored.
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> In particular, the example from the web page does not work.
> Note that the typeIds field does appear to allow leading space after a comma.
> The resolutionIds field does not.
> Since spaces are sometimes allowed, may I suggest the code is fixed rather
> than the documentation?
--
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: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-253.
-
Resolution: Fixed
1131414
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MCHANGES-253:
--
Fix Version/s: 2.6
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-253.
-
Resolution: Fixed
Once more with feeling.
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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: (MCHANGES-245) Custom mapping of IMS issue types to action types for announcements
[ http://jira.codehaus.org/browse/MCHANGES-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHANGES-245. - Resolution: Fixed Fix Version/s: 2.6 Patch applied rev 1131456. Thanks. > Custom mapping of IMS issue types to action types for announcements > --- > > Key: MCHANGES-245 > URL: http://jira.codehaus.org/browse/MCHANGES-245 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: announcement >Affects Versions: 2.4 >Reporter: Alan Parkinson > Fix For: 2.6 > > Attachments: MCHANGES-245-maven-changes-plugin.patch > > > The current version only maps "Bug", "New Feature" and "Improvement" issues > types to "fix", "add" and "update" actions. If the issue type from the IMS > isn't recognized the default action type is blank and this leads to the issue > not being included within the announcement when using the default template. > This set of supported issue types can be limiting with a modern JIRA > installation as is it has a greater range of issue types and can be extended > with additional types. The most flexible solution for JIRA and other IMSes > would be to allow the the mapping of issue types to action types. -- 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: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-253.
-
Resolution: Fixed
Really, I did fix it.
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269552#action_269552
]
Benson Margulies commented on MCHANGES-253:
---
Sebb, I fixed it in 1131454 after your last reopen.
** Using Maven syntax
In the following example we are only including issues that have as
their resolution. The status must be either or . Only
issues with one of the types , , or are
included in the report.
+-+
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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: (MCHANGES-248) Support custom jira status ids, please
[ http://jira.codehaus.org/browse/MCHANGES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHANGES-248. - Resolution: Fixed Fix Version/s: 2.6 rev 1131459. > Support custom jira status ids, please > -- > > Key: MCHANGES-248 > URL: http://jira.codehaus.org/browse/MCHANGES-248 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: jira >Affects Versions: 2.5 >Reporter: Benson Margulies > Fix For: 2.6 > > Attachments: MCHANGES-248.patch > > > It is possible to add status IDs to JIRA. e.g., Verified. There is currently > no way to make these work with the changes plugin. -- 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
