[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=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] [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=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] [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] [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] [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=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] [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=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] [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] [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] (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] (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] (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] (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] [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=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] [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] =
>
[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] =
>
[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=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=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] [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] (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] [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] =
[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] (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] [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] [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] [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] [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=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.framework.Assert in
[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] [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] [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] (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-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] [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-tabpanelfocusedCommentId=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 scm/ 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}
scm
connection${project.parent.scm.connection}/connection
developerConnection${project.parent.scm.developerConnection}/developerConnection
url${project.parent.scm.url}/url
/scm
{code}
--
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] (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-tabpanelfocusedCommentId=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] [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-tabpanelfocusedCommentId=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}
configuration
classpathDependencyScopeExcludeprovided/classpathDependencyScopeExclude
/configuration
{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-tabpanelfocusedCommentId=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}
configuration
classpathDependencyScopeExcludeprovided/classpathDependencyScopeExclude
/configuration
{code}
No such luck, the jar remains in the classpath.
--
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] (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-tabpanelfocusedCommentId=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] [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-tabpanelfocusedCommentId=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}
configuration
classpathDependencyScopeExcludeprovided/classpathDependencyScopeExclude
/configuration
{code}
No such luck, the jar remains in the classpath.
--
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}
configuration
classpathDependencyScopeExcludeprovided/classpathDependencyScopeExclude
/configuration
{code}
No such luck, the jar remains in the classpath.
--
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] [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] [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] [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-tabpanelfocusedCommentId=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] [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] [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-tabpanelfocusedCommentId=14624013#comment-14624013 ] Benson Margulies commented on MRELEASE-915: --- mavenExecutorIdforked-path/mavenExecutorId 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-tabpanelfocusedCommentId=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] (MSHADE-190) Shade does not relocate the contents of META-INF/services files
Benson Margulies created MSHADE-190: --- Summary: Shade does not relocate the contents of META-INF/services files Key: MSHADE-190 URL: https://issues.apache.org/jira/browse/MSHADE-190 Project: Maven Shade Plugin Issue Type: Bug Reporter: Benson Margulies If a META-INF/services/xxx file contains the name of a relocated class, the maven-shade-plugin does not rewrite the file to reflect the renamed class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MASSEMBLY-767) Schema missing from the web site
Benson Margulies created MASSEMBLY-767: -- Summary: Schema missing from the web site Key: MASSEMBLY-767 URL: https://issues.apache.org/jira/browse/MASSEMBLY-767 Project: Maven Assembly Plugin Issue Type: Bug Reporter: Benson Margulies http://maven.apache.org/xsd/assembly-1.1.3.xsd isn't there. It should be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (ARCHETYPE-471) Make a final Maven 2.2.1 release
[ https://jira.codehaus.org/browse/ARCHETYPE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed ARCHETYPE-471. -- Resolution: Fixed Make a final Maven 2.2.1 release Key: ARCHETYPE-471 URL: https://jira.codehaus.org/browse/ARCHETYPE-471 Project: Maven Archetype Issue Type: Task Reporter: Benson Margulies Assignee: Benson Margulies Fix For: 2.3 Release current state with prereqs amped up to 2.2.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-471) Make a final Maven 2.2.1 release
[ https://jira.codehaus.org/browse/ARCHETYPE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=362405#comment-362405 ] Benson Margulies commented on ARCHETYPE-471: commit 1656583: ARCHETYPE-471: update maven baseline to 2.2.1. all tests pass with versions bumped to 2.2.1. Make a final Maven 2.2.1 release Key: ARCHETYPE-471 URL: https://jira.codehaus.org/browse/ARCHETYPE-471 Project: Maven Archetype Issue Type: Task Reporter: Benson Margulies Assignee: Benson Margulies Fix For: 2.3 Release current state with prereqs amped up to 2.2.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-464) Upgrade Plugin Required Maven Version to 2.2.1
[ https://jira.codehaus.org/browse/ARCHETYPE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed ARCHETYPE-464. -- Resolution: Duplicate Fix Version/s: 2.3 Upgrade Plugin Required Maven Version to 2.2.1 -- Key: ARCHETYPE-464 URL: https://jira.codehaus.org/browse/ARCHETYPE-464 Project: Maven Archetype Issue Type: Wish Components: Plugin Affects Versions: 2.2 Reporter: Herve Boutemy Assignee: Benson Margulies Fix For: 2.3 2.2.1 is the unified minimum Maven version we're targetting see https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-prerequisites.html for report -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-435) Bad link to old docs in usage page
[ https://jira.codehaus.org/browse/ARCHETYPE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed ARCHETYPE-435. -- Resolution: Fixed Assignee: Benson Margulies Bad link to old docs in usage page -- Key: ARCHETYPE-435 URL: https://jira.codehaus.org/browse/ARCHETYPE-435 Project: Maven Archetype Issue Type: Bug Components: Documentation Affects Versions: 2.2 Environment: online docs Reporter: Anders Hammar Assignee: Benson Margulies Priority: Critical Fix For: 2.3 At the bottom of the usage page there is a link to the old docs, which renders a Page Not Found. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-182) Adding 'role-hint' for the default Selector/Configurer/Queryer implementations
[ https://jira.codehaus.org/browse/ARCHETYPE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed ARCHETYPE-182. -- Resolution: Fixed Fix Version/s: 2.3 Assignee: Benson Margulies Commit 1656610. Adding 'role-hint' for the default Selector/Configurer/Queryer implementations -- Key: ARCHETYPE-182 URL: https://jira.codehaus.org/browse/ARCHETYPE-182 Project: Maven Archetype Issue Type: Improvement Components: Creator, Generator Affects Versions: 2.0-alpha-3 Reporter: Gert Vanthienen Assignee: Benson Margulies Fix For: 2.3 Attachments: archetype-default-role-hint.patch With the current version of the Maven archetype plugin, it is not possible to add a custom Selector/Configurer/Queryer implementation. If I understand plexus correctly, adding a role-hint 'default' to the default implementations would allow you to add an implementation with another role-hint in your own pom.xml files as an extension to the maven-archetype-plugin plugin. This patch configures the role-hint attribute so it's generated in the components.xml file -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-475) Each template file should have its own Velocity context
[
https://jira.codehaus.org/browse/ARCHETYPE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=362407#comment-362407
]
Benson Margulies commented on ARCHETYPE-475:
How about a patch?
Each template file should have its own Velocity context
---
Key: ARCHETYPE-475
URL: https://jira.codehaus.org/browse/ARCHETYPE-475
Project: Maven Archetype
Issue Type: Improvement
Components: Generator
Affects Versions: 2.2
Reporter: Christian Schlichtherle
Priority: Minor
Right now, when generating a project from an archetype, all template files
are merged with the same Velocity context. This has the side effect that
changes to the Velocity context in one template file are reflected in all
subsequent template files. Consider the following example:
{code}
#set ($foo = bar)
{code}
This is a change to the Velocity context. Once it has been done, it's visible
in all template files which get subsequently merged with the global Velocity
context. This is bad because it's unexpected and uncontrollable because users
have no control over the order of processing.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (ARCHETYPE-464) Upgrade Plugin Required Maven Version to 2.2.1
[ https://jira.codehaus.org/browse/ARCHETYPE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=362409#comment-362409 ] Benson Margulies commented on ARCHETYPE-464: I made the code changes marked with 471. Upgrade Plugin Required Maven Version to 2.2.1 -- Key: ARCHETYPE-464 URL: https://jira.codehaus.org/browse/ARCHETYPE-464 Project: Maven Archetype Issue Type: Wish Components: Plugin Affects Versions: 2.2 Reporter: Herve Boutemy Assignee: Benson Margulies Fix For: 2.3 2.2.1 is the unified minimum Maven version we're targetting see https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-prerequisites.html for report -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-464) Upgrade Plugin Required Maven Version to 2.2.1
[ https://jira.codehaus.org/browse/ARCHETYPE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned ARCHETYPE-464: -- Assignee: Benson Margulies Upgrade Plugin Required Maven Version to 2.2.1 -- Key: ARCHETYPE-464 URL: https://jira.codehaus.org/browse/ARCHETYPE-464 Project: Maven Archetype Issue Type: Wish Components: Plugin Affects Versions: 2.2 Reporter: Herve Boutemy Assignee: Benson Margulies Fix For: 2.3 2.2.1 is the unified minimum Maven version we're targetting see https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-prerequisites.html for report -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-469) Maven Failed to read artifact descriptor for org.codehaus.mojo:jaxb2-maven-plugin:jar:1.6 in pom.xml?
[ https://jira.codehaus.org/browse/ARCHETYPE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed ARCHETYPE-469. -- Resolution: Not A Bug Assignee: Benson Margulies Please use the mailing list for support requests. Maven Failed to read artifact descriptor for org.codehaus.mojo:jaxb2-maven-plugin:jar:1.6 in pom.xml? - Key: ARCHETYPE-469 URL: https://jira.codehaus.org/browse/ARCHETYPE-469 Project: Maven Archetype Issue Type: Task Components: Archetypes, Plugin Reporter: Siva Prasad Assignee: Benson Margulies Attachments: consolelogEclipse.txt, errormaven.png, pom.xml I have done a check out from svn as in Eclipse(luna) as Checkout Maven Project as SCM.After doing that i am getting g error in pom.xml.How to resolve the error.?Below is the error...Please verifiy the attached file.How to resole this error and what it means.? Thank you... -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-471) Make a final Maven 2.2.1 release
[ https://jira.codehaus.org/browse/ARCHETYPE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated ARCHETYPE-471: --- Description: Release current state with prereqs amped up to 2.2.1. Fix Version/s: 2.3 Make a final Maven 2.2.1 release Key: ARCHETYPE-471 URL: https://jira.codehaus.org/browse/ARCHETYPE-471 Project: Maven Archetype Issue Type: Task Reporter: Benson Margulies Fix For: 2.3 Release current state with prereqs amped up to 2.2.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHADE-181) Allow including dependencies of scope:provided
[
https://jira.codehaus.org/browse/MSHADE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MSHADE-181:
Summary: Allow including dependencies of scope:provided (was: CLONE -
Allow including dependencies of scope:provided)
Allow including dependencies of scope:provided
---
Key: MSHADE-181
URL: https://jira.codehaus.org/browse/MSHADE-181
Project: Maven Shade Plugin
Issue Type: Wish
Affects Versions: 2.3
Reporter: Matthias Stevens
Assignee: Benson Margulies
I have a project for which I'd like to create a shaded jar.
It has a bunch of dependencies in scope:provided, because they really are, in
the normal use-case of this artifact; it's meant to be deployed as a plugin
in another app, so, for example, {{myapp-api}} really is provided.
The project's assembly depends on these deps to be scope:provided (so they're
not included in the assembly)
If a webapp project is made and depends on this project, the scope:provided
also helps avoiding duplicated dependencies in some cases.
.. but yes, this project now also needs a standalone/executable jar; some of
the provided dependencies are needed at runtime for this. As far as I can
tell, the shade plugin currently does not propose any solution for this.
Is there any way this could be considered for the plugin ? Or am I looking at
it the wrong way ? I suppose I could split my project and have 2 modules, one
simply being the standalone/shaded version of the other, but it seems
overkill, since they're really the same source.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1034) dependencesToScan versus classifiers: what's the scoop?
[ https://jira.codehaus.org/browse/SUREFIRE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned SUREFIRE-1034: -- Assignee: (was: Benson Margulies) dependencesToScan versus classifiers: what's the scoop? --- Key: SUREFIRE-1034 URL: https://jira.codehaus.org/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.1.6#6162)
[jira] (MWAR-284) overlay parameter documentation is missing
[ https://jira.codehaus.org/browse/MWAR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MWAR-284: - Assignee: (was: Benson Margulies) overlay parameter documentation is missing -- Key: MWAR-284 URL: https://jira.codehaus.org/browse/MWAR-284 Project: Maven WAR Plugin Issue Type: Improvement Components: overlay Affects Versions: 2.2 Reporter: Benson Margulies The doc for the overlays element is incomplete. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-471) Make a final Maven 2.2.1 release
[ https://jira.codehaus.org/browse/ARCHETYPE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned ARCHETYPE-471: -- Assignee: Benson Margulies Make a final Maven 2.2.1 release Key: ARCHETYPE-471 URL: https://jira.codehaus.org/browse/ARCHETYPE-471 Project: Maven Archetype Issue Type: Task Reporter: Benson Margulies Assignee: Benson Margulies Fix For: 2.3 Release current state with prereqs amped up to 2.2.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHADE-181) Allow including dependencies of scope:provided
[
https://jira.codehaus.org/browse/MSHADE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reassigned MSHADE-181:
---
Assignee: (was: Benson Margulies)
Allow including dependencies of scope:provided
---
Key: MSHADE-181
URL: https://jira.codehaus.org/browse/MSHADE-181
Project: Maven Shade Plugin
Issue Type: Wish
Affects Versions: 2.3
Reporter: Matthias Stevens
I have a project for which I'd like to create a shaded jar.
It has a bunch of dependencies in scope:provided, because they really are, in
the normal use-case of this artifact; it's meant to be deployed as a plugin
in another app, so, for example, {{myapp-api}} really is provided.
The project's assembly depends on these deps to be scope:provided (so they're
not included in the assembly)
If a webapp project is made and depends on this project, the scope:provided
also helps avoiding duplicated dependencies in some cases.
.. but yes, this project now also needs a standalone/executable jar; some of
the provided dependencies are needed at runtime for this. As far as I can
tell, the shade plugin currently does not propose any solution for this.
Is there any way this could be considered for the plugin ? Or am I looking at
it the wrong way ? I suppose I could split my project and have 2 modules, one
simply being the standalone/shaded version of the other, but it seems
overkill, since they're really the same source.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5416) Forked execution message should specify the forked goal
[
https://jira.codehaus.org/browse/MNG-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reassigned MNG-5416:
-
Assignee: (was: Benson Margulies)
Forked execution message should specify the forked goal
---
Key: MNG-5416
URL: https://jira.codehaus.org/browse/MNG-5416
Project: Maven
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 3.0.4
Reporter: Benson Margulies
Priority: Minor
{noformat}
[INFO]
[INFO] Forking License Test :: global-db - something to depend on 1
[INFO]
{noformat}
One of the struggles in debugging a build can be forked executions.
If the forked execution implicitly depends on some goal of some plugin that
is bound to a phase after the forked goal, the build fails. This would be
easier to debug if this message included the goal.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MANTRUN-186) taskdef/ seems ignoring classpath
[
https://jira.codehaus.org/browse/MANTRUN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MANTRUN-186:
-
Assignee: (was: Benson Margulies)
Summary: taskdef/ seems ignoring classpath (was: CLONE - taskdef/
seems ignoring classpath)
taskdef/ seems ignoring classpath
---
Key: MANTRUN-186
URL: https://jira.codehaus.org/browse/MANTRUN-186
Project: Maven Antrun Plugin
Issue Type: Bug
Affects Versions: 1.5, 1.6, 1.7
Environment: Fedora
Reporter: Mansour Al Akeel
Fix For: 1.7
I'm trying to run xdoclet in ant build file called from antrun plugin. The
build file is very simple:
{code:xml}
project name=testcase default=run
property name=maven.repository value=set repository location
here!/
property name=destdir value=target/generated-sources/
path id=xdoclet.classpath
fileset dir=${maven.repository}
include
name=commons-collections/commons-collections/3.1/commons-collections-3.1.jar/
include
name=commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar/
include
name=jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar/
include name=xjavadoc/xjavadoc/1.1/xjavadoc-1.1.jar/
include
name=xdoclet/xdoclet/1.2.3/xdoclet-1.2.3.jar/
include
name=xdoclet/xdoclet-ejb-module/1.2.3/xdoclet-ejb-module-1.2.3.jar/
/fileset
/path
target name=run
!-- print classplath --
property refid=xdoclet.classpath name=cp/
echo message=xdoclet.classpath: ${cp}/
!-- define ejbdoclet task --
taskdef classname=xdoclet.modules.ejb.EjbDocletTask
classpathref=xdoclet.classpath name=ejbdoclet/
!-- run ejbdoclet --
ejbdoclet destdir=${destdir}
fileset includes=**/*Bean.java
dir=${basedir}/src/main/java/
remoteinterface/
/ejbdoclet
/target
/project
{code}
When executed directly from command (ant
-Dmaven.repository=/home/javor/.m2/repository) it works fine. But fails when
embedded in antrun:
{code:xml}
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.2-SNAPSHOT/version
executions
execution
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
ant inheritRefs=true inheritall=true
antfile=build.xml
property name=maven.repository
value=${settings.localRepository}/
/ant
/tasks
/configuration
/execution
/executions
/plugin
{code}
Maven output:
{noformat}
...
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
run:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
/home/javor/workspace/testcase/build.xml:26: Can't create a remoteinterface
element under ejbdoclet. Make sure the jar file containing the corresponding
subtask class is on the classpath specified in the taskdef that defined {2}.
...
{noformat}
Could you show me any workaround or put a bit of light on that problem?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-885) When the base pom is a subdirectory, tagging fails in GIT
[ https://jira.codehaus.org/browse/MRELEASE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MRELEASE-885: - Assignee: (was: Benson Margulies) When the base pom is a subdirectory, tagging fails in GIT - Key: MRELEASE-885 URL: https://jira.codehaus.org/browse/MRELEASE-885 Project: Maven Release Plugin Issue Type: Bug Components: Git, scm Affects Versions: 2.3.2, 2.5 Environment: linux (fedora 20) Reporter: Bradley Baetz Fix For: 2.5.1 (NOTE, this is not the same as MRELEASE-875. I think) Given a GIT checkout with a project structure of: project/ dir1/pom.xml dir2/pom.xml Given an scm config of: developerConnectionscm:git:ssh://g...@github.com:bbaetz/maven-release-bug.git/developerConnection the maven-release plugin correctly commits the pom file, but fails to tag. The problem is that its stripping off one level of the URL, and doing: [INFO] Executing: /bin/sh -c cd /home/bbaetz/src/subdir-project git push ssh://g...@github.com:bbaetz refs/tags/project-1.0.0 which is wrong for git To reproduce, fork https://github.com/bbaetz/maven-release-bug/, change the scm settings to your own, and run: mvn -X -B -f build/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT -DreleaseVersion=1.0.0 -Dresume=false release:prepare release:perform I've tried various combinations of maven-release-plugin and maven-scm-plugin versions, with no luck -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-471) Make a final Maven 2.2.1 release
Benson Margulies created ARCHETYPE-471: -- Summary: Make a final Maven 2.2.1 release Key: ARCHETYPE-471 URL: https://jira.codehaus.org/browse/ARCHETYPE-471 Project: Maven Archetype Issue Type: Task Reporter: Benson Margulies -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-120) Javac compiler plugin doesn't support -Werror
[
https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCOMPILER-120.
--
Resolution: Fixed
Here's the story.
If you are compiling down with -source / -target, and not supplying
-Xbootclasspath, you get a warning at the outset. That stops the process with
-Werror _unless_ you then also use -Xlint:-options to turn this off. I can't
explain the apparent influence of deprecation/warning control.
Javac compiler plugin doesn't support -Werror
-
Key: MCOMPILER-120
URL: https://jira.codehaus.org/browse/MCOMPILER-120
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Christopher Webster
Assignee: Kristian Rosenvold
Fix For: 2.4
Attachments: JavacCompiler.java, JavacCompiler.patch,
trial-maven.zip, werror.zip
If I write a pom file like the following:
{code:xml}...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.1/version
configuration
compilerIdjavac/compilerId
source1.6/source
target1.6/target
compilerArguments
Werror /
Xlint:all /
/compilerArguments
showDeprecationtrue/showDeprecation
/configuration
/plugin{code}
and if there are only warnings, then the build will not fail as intended by
the compiler Argument. The reason is that in compileInProcess the exit code
from javac is only considered if there are no messages. In the case of
treating warnings as errors, there will be messages but no errors so the
intention of the build failure is lost.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCOMPILER-120) Javac compiler plugin doesn't support -Werror
[
https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361982#comment-361982
]
Benson Margulies edited comment on MCOMPILER-120 at 1/28/15 4:08 PM:
-
The problem here is
{code}
showDeprecationtrue/showDeprecation
{code}
If this is present, the warnings disappear with -Werror.
was (Author: bmargulies):
The problem here is
{code}
showWarningtrue/showWarnings
{code}
If this is present, the warnings disappear with -Werror.
Javac compiler plugin doesn't support -Werror
-
Key: MCOMPILER-120
URL: https://jira.codehaus.org/browse/MCOMPILER-120
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Christopher Webster
Assignee: Kristian Rosenvold
Fix For: 2.4
Attachments: JavacCompiler.java, JavacCompiler.patch,
trial-maven.zip, werror.zip
If I write a pom file like the following:
{code:xml}...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.1/version
configuration
compilerIdjavac/compilerId
source1.6/source
target1.6/target
compilerArguments
Werror /
Xlint:all /
/compilerArguments
showDeprecationtrue/showDeprecation
/configuration
/plugin{code}
and if there are only warnings, then the build will not fail as intended by
the compiler Argument. The reason is that in compileInProcess the exit code
from javac is only considered if there are no messages. In the case of
treating warnings as errors, there will be messages but no errors so the
intention of the build failure is lost.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCOMPILER-120) Javac compiler plugin doesn't support -Werror
[
https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361982#comment-361982
]
Benson Margulies commented on MCOMPILER-120:
The problem here is
{code}
showWarningtrue/showWarnings
{code}
If this is present, the warnings disappear with -Werror.
Javac compiler plugin doesn't support -Werror
-
Key: MCOMPILER-120
URL: https://jira.codehaus.org/browse/MCOMPILER-120
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Christopher Webster
Assignee: Kristian Rosenvold
Fix For: 2.4
Attachments: JavacCompiler.java, JavacCompiler.patch,
trial-maven.zip, werror.zip
If I write a pom file like the following:
{code:xml}...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.1/version
configuration
compilerIdjavac/compilerId
source1.6/source
target1.6/target
compilerArguments
Werror /
Xlint:all /
/compilerArguments
showDeprecationtrue/showDeprecation
/configuration
/plugin{code}
and if there are only warnings, then the build will not fail as intended by
the compiler Argument. The reason is that in compileInProcess the exit code
from javac is only considered if there are no messages. In the case of
treating warnings as errors, there will be messages but no errors so the
intention of the build failure is lost.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCOMPILER-120) Javac compiler plugin doesn't support -Werror
[
https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361831#comment-361831
]
Benson Margulies edited comment on MCOMPILER-120 at 1/26/15 12:52 PM:
--
I'm reopening this because the 'fix' has a pretty major problem: no message is
printed explaining why the compilation fails. Adding -e and -X do not lead to
the actual message arriving.
{noformat}
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 179 source files to /Users/benson/x/gcoref/core/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.000 s
[INFO] Finished at: 2015-01-26T13:50:23-05:00
[INFO] Final Memory: 30M/705M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on
project res-core: Compilation failure - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
{noformat}
Here's the effective pom of note:
{code}
execution
iddefault-compile/id
phasecompile/phase
goals
goalcompile/goal
/goals
configuration
compilerArgs
arg-Werror/arg
arg-Xlint:all/arg
/compilerArgs
showDeprecationtrue/showDeprecation
showWarningstrue/showWarnings
forktrue/fork
verbosetrue/verbose
encodingutf-8/encoding
source1.7/source
target1.7/target
maxmem256M/maxmem
debugtrue/debug
optimizetrue/optimize
/configuration
/execution
{code}
was (Author: bmargulies):
I'm reopening this because the 'fix' has a pretty major problem: no message os
printed explaining why the compilation fails. Adding -e and -X do not lead to
the actual message arriving.
{noformat}
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 179 source files to /Users/benson/x/gcoref/core/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.000 s
[INFO] Finished at: 2015-01-26T13:50:23-05:00
[INFO] Final Memory: 30M/705M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on
project res-core: Compilation failure - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
{noformat}
Here's the effective pom of note:
{code}
execution
iddefault-compile/id
phasecompile/phase
goals
goalcompile/goal
/goals
configuration
compilerArgs
arg-Werror/arg
arg-Xlint:all/arg
/compilerArgs
showDeprecationtrue/showDeprecation
showWarningstrue/showWarnings
forktrue/fork
verbosetrue/verbose
encodingutf-8/encoding
source1.7/source
target1.7/target
maxmem256M/maxmem
debugtrue/debug
optimizetrue/optimize
/configuration
/execution
{code}
Javac compiler plugin doesn't support -Werror
-
Key: MCOMPILER-120
URL: https://jira.codehaus.org/browse/MCOMPILER-120
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Christopher Webster
Assignee: Kristian Rosenvold
Fix For: 2.4
Attachments: JavacCompiler.java, JavacCompiler.patch,
trial-maven.zip, werror.zip
If I write a pom file like the following:
{code:xml}...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.1/version
configuration
compilerIdjavac/compilerId
source1.6/source
target1.6/target
compilerArguments
Werror /
[jira] (MCOMPILER-120) Javac compiler plugin doesn't support -Werror
[
https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reopened MCOMPILER-120:
I'm reopening this because the 'fix' has a pretty major problem: no message os
printed explaining why the compilation fails. Adding -e and -X do not lead to
the actual message arriving.
{noformat}
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 179 source files to /Users/benson/x/gcoref/core/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.000 s
[INFO] Finished at: 2015-01-26T13:50:23-05:00
[INFO] Final Memory: 30M/705M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on
project res-core: Compilation failure - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
{noformat}
Here's the effective pom of note:
{code}
execution
iddefault-compile/id
phasecompile/phase
goals
goalcompile/goal
/goals
configuration
compilerArgs
arg-Werror/arg
arg-Xlint:all/arg
/compilerArgs
showDeprecationtrue/showDeprecation
showWarningstrue/showWarnings
forktrue/fork
verbosetrue/verbose
encodingutf-8/encoding
source1.7/source
target1.7/target
maxmem256M/maxmem
debugtrue/debug
optimizetrue/optimize
/configuration
/execution
{code}
Javac compiler plugin doesn't support -Werror
-
Key: MCOMPILER-120
URL: https://jira.codehaus.org/browse/MCOMPILER-120
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Christopher Webster
Assignee: Kristian Rosenvold
Fix For: 2.4
Attachments: JavacCompiler.java, JavacCompiler.patch,
trial-maven.zip, werror.zip
If I write a pom file like the following:
{code:xml}...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.1/version
configuration
compilerIdjavac/compilerId
source1.6/source
target1.6/target
compilerArguments
Werror /
Xlint:all /
/compilerArguments
showDeprecationtrue/showDeprecation
/configuration
/plugin{code}
and if there are only warnings, then the build will not fail as intended by
the compiler Argument. The reason is that in compileInProcess the exit code
from javac is only considered if there are no messages. In the case of
treating warnings as errors, there will be messages but no errors so the
intention of the build failure is lost.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-855) Allow failsafe to use actual jar file instead of target/classes
[ https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=358239#comment-358239 ] Benson Margulies commented on SUREFIRE-855: --- I have recently been using pax-exam with failsafe to test OSGi bundles. You need to pass project.build.directory and project.version into the test as system properties, so that you can load the bundle by pathname. If you need other bundles from earlier in the reactor, you have to use the maven-dependency-plugin get them; if you use pax-aether, you end up with old versions. Allow failsafe to use actual jar file instead of target/classes --- Key: SUREFIRE-855 URL: https://jira.codehaus.org/browse/SUREFIRE-855 Project: Maven Surefire Issue Type: Improvement Components: Maven Failsafe Plugin Affects Versions: 2.12 Reporter: Benson Margulies Priority: Critical I've got some code that calls Class.getPackage() to see the manifest. I want to test it. A seemingly logical scheme here would be to have failsafe put the actual packaged jar into the classpath instead of the unpacked directory -- or some way to get the manifest copied across. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-893) Put the tag in a property in :prepare
Benson Margulies created MRELEASE-893: - Summary: Put the tag in a property in :prepare Key: MRELEASE-893 URL: https://jira.codehaus.org/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.1.6#6162)
[jira] (MSITE-731) footer elements in site.xml are ignored
Benson Margulies created MSITE-731: -- Summary: footer elements in site.xml are ignored Key: MSITE-731 URL: https://jira.codehaus.org/browse/MSITE-731 Project: Maven Site Plugin Issue Type: Bug Affects Versions: 3.4 Reporter: Benson Margulies See https://github.com/basis-technology-corp/tcl-regex-java. If you clone this and run mvn site:site, you will see a copyright notice that I don't want, instead of the footer that is supplied in the site.xml. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-885) When the base pom is a subdirectory, tagging fails in GIT
[ https://jira.codehaus.org/browse/MRELEASE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=353399#comment-353399 ] Benson Margulies commented on MRELEASE-885: --- Unless you attach a repro, including your specific git version, I will reclose this. 'fatal: Could not read from remote repository.' has nothing to do with tags, and nothing to do with pom relative paths. it has to do with an incorrect remote. I recommend putting an example on github that someone else can clone and use to demonstrate. When the base pom is a subdirectory, tagging fails in GIT - Key: MRELEASE-885 URL: https://jira.codehaus.org/browse/MRELEASE-885 Project: Maven Release Plugin Issue Type: Bug Components: Git, scm Affects Versions: 2.3.2, 2.5 Environment: linux (fedora 20) Reporter: Bradley Baetz Assignee: Benson Margulies Fix For: 2.5.1 (NOTE, this is not the same as MRELEASE-875. I think) Given a GIT checkout with a project structure of: project/ dir1/pom.xml dir2/pom.xml Given an scm config of: developerConnectionscm:git:ssh://g...@github.com:bbaetz/maven-release-bug.git/developerConnection the maven-release plugin correctly commits the pom file, but fails to tag. The problem is that its stripping off one level of the URL, and doing: [INFO] Executing: /bin/sh -c cd /home/bbaetz/src/subdir-project git push ssh://g...@github.com:bbaetz refs/tags/project-1.0.0 which is wrong for git To reproduce, fork https://github.com/bbaetz/maven-release-bug/, change the scm settings to your own, and run: mvn -X -B -f build/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT -DreleaseVersion=1.0.0 -Dresume=false release:prepare release:perform I've tried various combinations of maven-release-plugin and maven-scm-plugin versions, with no luck -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-885) When the base pom is a subdirectory, tagging fails in GIT
[ https://jira.codehaus.org/browse/MRELEASE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=353403#comment-353403 ] Benson Margulies commented on MRELEASE-885: --- What version of git? Obviously, I didn't see anything like the behavior you report in my testing or I wouldn't have gone to all the trouble of releasing this mess. When the base pom is a subdirectory, tagging fails in GIT - Key: MRELEASE-885 URL: https://jira.codehaus.org/browse/MRELEASE-885 Project: Maven Release Plugin Issue Type: Bug Components: Git, scm Affects Versions: 2.3.2, 2.5 Environment: linux (fedora 20) Reporter: Bradley Baetz Assignee: Benson Margulies Fix For: 2.5.1 (NOTE, this is not the same as MRELEASE-875. I think) Given a GIT checkout with a project structure of: project/ dir1/pom.xml dir2/pom.xml Given an scm config of: developerConnectionscm:git:ssh://g...@github.com:bbaetz/maven-release-bug.git/developerConnection the maven-release plugin correctly commits the pom file, but fails to tag. The problem is that its stripping off one level of the URL, and doing: [INFO] Executing: /bin/sh -c cd /home/bbaetz/src/subdir-project git push ssh://g...@github.com:bbaetz refs/tags/project-1.0.0 which is wrong for git To reproduce, fork https://github.com/bbaetz/maven-release-bug/, change the scm settings to your own, and run: mvn -X -B -f build/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT -DreleaseVersion=1.0.0 -Dresume=false release:prepare release:perform I've tried various combinations of maven-release-plugin and maven-scm-plugin versions, with no luck -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-885) When the base pom is a subdirectory, tagging fails in GIT
[ https://jira.codehaus.org/browse/MRELEASE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=353404#comment-353404 ] Benson Margulies commented on MRELEASE-885: --- What's with the 'ssh:' url? have you tried something like plain old: scm:git:g...@github.com:bbaetz/maven-release-bug.git ? I suspect that all those slashes are provocative. When the base pom is a subdirectory, tagging fails in GIT - Key: MRELEASE-885 URL: https://jira.codehaus.org/browse/MRELEASE-885 Project: Maven Release Plugin Issue Type: Bug Components: Git, scm Affects Versions: 2.3.2, 2.5 Environment: linux (fedora 20) Reporter: Bradley Baetz Assignee: Benson Margulies Fix For: 2.5.1 (NOTE, this is not the same as MRELEASE-875. I think) Given a GIT checkout with a project structure of: project/ dir1/pom.xml dir2/pom.xml Given an scm config of: developerConnectionscm:git:ssh://g...@github.com:bbaetz/maven-release-bug.git/developerConnection the maven-release plugin correctly commits the pom file, but fails to tag. The problem is that its stripping off one level of the URL, and doing: [INFO] Executing: /bin/sh -c cd /home/bbaetz/src/subdir-project git push ssh://g...@github.com:bbaetz refs/tags/project-1.0.0 which is wrong for git To reproduce, fork https://github.com/bbaetz/maven-release-bug/, change the scm settings to your own, and run: mvn -X -B -f build/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT -DreleaseVersion=1.0.0 -Dresume=false release:prepare release:perform I've tried various combinations of maven-release-plugin and maven-scm-plugin versions, with no luck -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] [Resolved] (MPOM-58) Pom calls for yet another version of maven-release-plugin to deal with more git problems
[ https://issues.apache.org/jira/browse/MPOM-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MPOM-58. -- Resolution: Fixed Done in r1626879. Pom calls for yet another version of maven-release-plugin to deal with more git problems Key: MPOM-58 URL: https://issues.apache.org/jira/browse/MPOM-58 Project: Maven POMs Issue Type: Bug Affects Versions: ASF-14 Reporter: Benson Margulies Assignee: Benson Margulies Fix For: ASF-15 MRELEASE-875 is another problem with git that prevents work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (MRELEASE-889) Version policies don't work with Maven 2.2.1
[ https://jira.codehaus.org/browse/MRELEASE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MRELEASE-889. - Resolution: Fixed Fix Version/s: 2.5.2 Version policies don't work with Maven 2.2.1 Key: MRELEASE-889 URL: https://jira.codehaus.org/browse/MRELEASE-889 Project: Maven Release Plugin Issue Type: Bug Affects Versions: 2.5 Reporter: Benson Margulies Fix For: 2.5.1 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.1.6#6162)
[jira] (MRELEASE-889) Version policies don't work with Maven 2.2.1
Benson Margulies created MRELEASE-889: - Summary: Version policies don't work with Maven 2.2.1 Key: MRELEASE-889 URL: https://jira.codehaus.org/browse/MRELEASE-889 Project: Maven Release Plugin Issue Type: Bug Affects Versions: 2.5 Reporter: Benson Margulies 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.1.6#6162)
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[ https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MRELEASE-875. - Resolution: Fixed Fix Version/s: 2.5.1 I can no longer reproduce this, even with -f, with SCM 1.9.2 integrated. release:prepare does not commit pom.xml if not in the git root -- Key: MRELEASE-875 URL: https://jira.codehaus.org/browse/MRELEASE-875 Project: Maven Release Plugin Issue Type: Bug Components: prepare, scm Affects Versions: 2.5 Environment: git 1.9.0 Reporter: john ten Den Assignee: Benson Margulies Fix For: 2.5.1 When the project pom.xml is not in the Git project root (f.e. in the src directory) the pom.xml not committed and pushed (before tagging) Commit of the pom.xml during release:prepare works fine if it is in the / (root) of the git repository Using the pom.xml in a subdirectory worked well with version 2.4.2 using git 1.7. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
