[jira] [Updated] (MCOMPILER-306) Incorrect `compilerArgs` example usage

[Stephan Schroevers (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MCOMPILER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephan Schroevers updated MCOMPILER-306:
-
Description: 
The {{compilerArgs}} property documentation 
[contains|https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArgs]
 this example usage:
{code:xml}

  -Xmaxerrs=1000
  -Xlint
  -J-Duser.language=en_us

{code}

But setting {{-Xmaxerrs=1000}} causes:
{noformat}
...
Caused by: java.lang.IllegalArgumentException: invalid flag: -Xmaxerrs=1000
at com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:206)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:156)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:107)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:64)
at 
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125)
... 16 more
{noformat}

This does work:
{code:xml}

  -Xmaxerrs
  1000

{code}

  was:
The {{compilerArgs}} property documentation 
[contains|https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArgs]
 this example usage:
{code:xml}

  -Xmaxerrs=1000
  -Xlint
  -J-Duser.language=en_us

{code}

But setting {{-Xmaxerrs=1000}} causes:
{noformat}
...
Caused by: java.lang.IllegalArgumentException: invalid flag: -Xmaxerrs=1000
at com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:206)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:156)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:107)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:64)
at 
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125)
... 16 more
{noformat}

This does work:
{code:xml}

  -Xmaxerrs
  1

{code}


> Incorrect `compilerArgs` example usage
> --
>
> Key: MCOMPILER-306
> URL: https://issues.apache.org/jira/browse/MCOMPILER-306
> Project: Maven Compiler Plugin
>  Issue Type: Bug
>Affects Versions: 3.6.2
>Reporter: Stephan Schroevers
>
> The {{compilerArgs}} property documentation 
> [contains|https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArgs]
>  this example usage:
> {code:xml}
> 
>   -Xmaxerrs=1000
>   -Xlint
>   -J-Duser.language=en_us
> 
> {code}
> But setting {{-Xmaxerrs=1000}} causes:
> {noformat}
>   ...
> Caused by: java.lang.IllegalArgumentException: invalid flag: -Xmaxerrs=1000
>   at com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:206)
>   at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:156)
>   at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:107)
>   at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:64)
>   at 
> org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125)
>   ... 16 more
> {noformat}
> This does work:
> {code:xml}
> 
>   -Xmaxerrs
>   1000
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MCOMPILER-306) Incorrect `compilerArgs` example usage

[Stephan Schroevers (JIRA)]

Stephan Schroevers created MCOMPILER-306:


 Summary: Incorrect `compilerArgs` example usage
 Key: MCOMPILER-306
 URL: https://issues.apache.org/jira/browse/MCOMPILER-306
 Project: Maven Compiler Plugin
  Issue Type: Bug
Affects Versions: 3.6.2
Reporter: Stephan Schroevers


The {{compilerArgs}} property documentation 
[contains|https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArgs]
 this example usage:
{code:xml}

  -Xmaxerrs=1000
  -Xlint
  -J-Duser.language=en_us

{code}

But setting {{-Xmaxerrs=1000}} causes:
{noformat}
...
Caused by: java.lang.IllegalArgumentException: invalid flag: -Xmaxerrs=1000
at com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:206)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:156)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:107)
at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:64)
at 
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125)
... 16 more
{noformat}

This does work:
{code:xml}

  -Xmaxerrs
  1

{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134142#comment-16134142
 ] 

ASF GitHub Bot commented on SUREFIRE-1383:
--

Github user owenfarrell commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
@Tibor17 - thoughts?


> dependenciesToScan Does Not Leverage Classpath Elements 
> 
>
> Key: SUREFIRE-1383
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: Owen Farrell
> Fix For: Backlog
>
> Attachments: scanned-dependencies-sample.zip
>
>
> The  configuration attribute relies solely on installed 
> artifacts. This is an issue when the targeted dependencies were built as part 
> of the current session. The net result is that stale artifacts are used (i.e. 
> if the dependency has changed since it was last installed) or the tests are 
> not executed at all (if the dependency has not been previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>And the first module built includes test classes as part of the project 
> artifact
>And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>And tests should be executed with each module



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MSHADE-258) RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHADE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134119#comment-16134119
 ] 

Hudson commented on MSHADE-258:
---

SUCCESS: Integrated in Jenkins build maven-plugins #9072 (See 
[https://builds.apache.org/job/maven-plugins/9072/])
[MSHADE-258] RemappingClassAdapter is deprecated and throws an exception with 
ASM 6.0 beta
Provide IT (rfscholte: [http://svn.apache.org/viewvc/?view=rev=1805503])
* (add) maven-shade-plugin/src/it/MSHADE-258_module_relocation
* (add) maven-shade-plugin/src/it/MSHADE-258_module_relocation/pom.xml
* (add) maven-shade-plugin/src/it/MSHADE-258_module_relocation/verify.groovy


> RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta
> -
>
> Key: MSHADE-258
> URL: https://issues.apache.org/jira/browse/MSHADE-258
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Ismael Juma
>Assignee: Robert Scholte
> Fix For: 3.1.0
>
>
> While trying to use the maven shade plugin with ASM 6.0 beta (for Java 9 
> support) in the easymock project, I ran into the following exception:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
> easymock: Error creating shaded jar: Error in ASM processing class 
> module-info.class: RemappingClassAdapter is deprecated, use ClassRemapper 
> instead -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on 
> project easymock: Error creating shaded jar: Error in ASM processing class 
> module-info.class
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>   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:309)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   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: Error in ASM processing class module-info.class
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 20 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error in ASM 
> processing class module-info.class
>   at 
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:453)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar(DefaultShader.java:220)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeJars(DefaultShader.java:181)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:104)
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:442)
>   ... 22 more
> Caused by: java.lang.RuntimeException: RemappingClassAdapter is deprecated, 
> use ClassRemapper instead
>   at org.objectweb.asm.commons.RemappingClassAdapter.visitModule(Unknown 
> 

[jira] [Commented] (MSHADE-242) Plugin does not work with Java 9

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHADE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134120#comment-16134120
 ] 

Hudson commented on MSHADE-242:
---

SUCCESS: Integrated in Jenkins build maven-plugins #9072 (See 
[https://builds.apache.org/job/maven-plugins/9072/])
[MSHADE-242] Plugin does not work with Java 9
Upgraded ASM + JDependency
Adjust code due to dependency upgrades (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1805501])
* (edit) maven-shade-plugin/pom.xml
* (edit) 
maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java
* (edit) 
maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/filter/MinijarFilter.java


> Plugin does not work with Java 9
> 
>
> Key: MSHADE-242
> URL: https://issues.apache.org/jira/browse/MSHADE-242
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4.3
> Environment: ╰─✘ java -version
> openjdk version "9-internal"
> OpenJDK Runtime Environment (build 9-internal+0-2016-11-17-101644.norman.jdk9)
> OpenJDK 64-Bit Server VM (build 9-internal+0-2016-11-17-101644.norman.jdk9, 
> mixed mode)
>Reporter: Norman Maurer
>Assignee: Robert Scholte
> Fix For: 3.1.0
>
>
> When trying to use the shade plugin with java9  I get:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on project 
> netty-common: Error creating shaded jar: null: IllegalArgumentException -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on 
> project netty-common: 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 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:537)
>   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.IllegalArgumentException
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
>   at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
>   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
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPMD-239) Add documentation about upgrading PMD version at runtime

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPMD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134122#comment-16134122
 ] 

Hudson commented on MPMD-239:
-

SUCCESS: Integrated in Jenkins build maven-plugins #9072 (See 
[https://builds.apache.org/job/maven-plugins/9072/])
[MPMD-239] Add documentation about upgrading PMD version at runtime (adangel: 
[http://svn.apache.org/viewvc/?view=rev=1805494])
* (add) maven-pmd-plugin/src/site/apt/examples/upgrading-PMD-at-runtime.apt.vm
* (edit) maven-pmd-plugin/src/site/apt/index.apt.vm
* (edit) maven-pmd-plugin/src/site/site.xml


> Add documentation about upgrading PMD version at runtime
> 
>
> Key: MPMD-239
> URL: https://issues.apache.org/jira/browse/MPMD-239
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.9
>
>
> The documentation should be similar to 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
> Example configuration, to use m-pmd-p 3.8 + PMD "choose your version":
> {noformat}
> 
>   
> ...choose your version...
>   
> ...
>   
> 
>   
> 
>   org.apache.maven.plugins
>   maven-pmd-plugin
>   3.8
>   
> 
>   net.sourceforge.pmd
>   pmd-core
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-java
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-javascript
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-jsp
>   ${pmdVersion}
> 
>   
> 
>   
> 
>   
> ...
> 
> {noformat}
> See also https://github.com/pmd/pmd/issues/402



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MEJB-115) Wrong default EJB version stated on Usage page

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MEJB-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134121#comment-16134121
 ] 

Hudson commented on MEJB-115:
-

SUCCESS: Integrated in Jenkins build maven-plugins #9072 (See 
[https://builds.apache.org/job/maven-plugins/9072/])
[MEJB-115] Wrong default EJB version stated on Usage page (andham: 
[http://svn.apache.org/viewvc/?view=rev=1805498])
* (edit) maven-ejb-plugin/src/site/apt/usage.apt.vm


> Wrong default EJB version stated on Usage page
> --
>
> Key: MEJB-115
> URL: https://issues.apache.org/jira/browse/MEJB-115
> Project: Maven EJB Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Anders Hammar
>Priority: Minor
> Fix For: 3.0.1
>
>
> On the Usage page, it is stated that the default EJB version is "2.1". This 
> was changed in v3.0.0 of the plugin to "3.1". This doc page needs to be 
> updated. We should rewrite the text so that we do not have this hard-coded to 
> prevent this to happen again in the future.
> Also, the sentence "In EJB3, the ejb-jar.xml deployment descriptor is not 
> mandatory anymore." could also be removed in this paragraph as it is somewhat 
> confusing in this text where we talk about how to configure/use the plugin.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MSHADE-257) Bad zero length source jars published by 3rd parties cause source jar creation to fail.

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHADE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134118#comment-16134118
 ] 

Hudson commented on MSHADE-257:
---

SUCCESS: Integrated in Jenkins build maven-plugins #9072 (See 
[https://builds.apache.org/job/maven-plugins/9072/])
[MSHADE-257] Bad zero length source jars published by 3rd parties cause source 
jar creation to fail. (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1805504])
* (edit) 
maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java


> Bad zero length source jars published by 3rd parties cause source jar 
> creation to fail.
> ---
>
> Key: MSHADE-257
> URL: https://issues.apache.org/jira/browse/MSHADE-257
> Project: Maven Shade Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Jess
>Assignee: Robert Scholte
> Fix For: 3.1.0
>
> Attachments: maven-shade-plugin-257-patch.diff
>
>
> If a transient dependency that is being  shaded (in my case 
> xmlpull:xmlpull:1.1.3.1) published a zero length source jar, then the source 
> generation will throw a zip exception and abort the build.  The plugin should 
> guard against this and issue a warning instead of failing.
> A patch with the guard will be attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MPOM-1) apache-release does unwanted things in the prepare goal

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MPOM-1.
--
Resolution: Implemented

My assumption is that this is implemented based on the comments with related 
svn revision number.

> apache-release does unwanted things in the prepare goal
> ---
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-7
>Reporter: Olivier Lamy (*$^¨%`£)
>Assignee: Brian Fox
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' 
> profile in the release plugin. By using -P, this profile is turned on in 
> prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump 
> in a lake, but I think this is a bad idea. At prepare time, we're just 
> looking to get the versions setup and the tag made. Having to deal with gpg 
> signing, and source archiving seems out of place.
> At very least, I'd request that this the  element be left out of 
> the release plugin spec. If some project wants to use that particular 
> collection of functions, fine. For the rest of us, who just want to get 
> distribution management and other universals, you we wouldn't have to worry 
> about it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MPOM-159) Upgrade plexus-component-metadata to 1.7.1 to fix JDK 9 issues

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPOM-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise reassigned MPOM-159:


Assignee: Karl Heinz Marbaise

> Upgrade plexus-component-metadata to 1.7.1 to fix JDK 9 issues
> --
>
> Key: MPOM-159
> URL: https://issues.apache.org/jira/browse/MPOM-159
> Project: Maven POMs
>  Issue Type: Improvement
>  Components: maven
>Affects Versions: MAVEN-30
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: MAVEN-31
>
>
> Currently the plexus-component-metadata is on 1.6 which seemed to cause some 
> issues with JDK 9...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MSHADE-252) shadeSourcesContent is broken when combined with partial relocation

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MSHADE-252:
--
Description: 
per description in 
https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#shadeSourcesContent,
 when set it to true, 
"it will attempt to shade the contents of the java source files when creating 
the sources jar." However, it seems will blindly shade all the source files 
include those are excluded from relocation rules.

This could be illustrated with a simple example:

Assume there are two classes defined in two packages as below:
{code:title=A.java}
package com.fake.fooA;
import com.fake.fooB;
public Class A {}
{code}

{code:title=B.java}
package com.fake.fooB;
import com.fake.fooA;
public class B {}
{code}

and the maven config looks like:
{code:xml}
 
org.apache.maven.plugins
maven-shade-plugin
2.4.3

  
  
package

  shade


  false
  true
  true
  

  com.fake
  .com.fake.shaded
  
com.fake.fooA.*
  


{code}

Then the shade plugin will modify the B's source file to be:
{code}
package com.fake.shaded.fooB;
import com.fake.shaded.fooA;
public class B {}
{code}

Notice that package A's path was also updated, which is wrong as it's not got 
relocated.

  was:
per description in 
https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#shadeSourcesContent,
 when set it to true, 
"it will attempt to shade the contents of the java source files when creating 
the sources jar." However, it seems will blindly shade all the source files 
include those are excluded from relocation rules.

This could be illustrated with a simple example:

Assume there are two classes defined in two packages as below:
A.java:
package com.fake.fooA;
import com.fake.fooB;
public Class A {}

B.java:
package com.fake.fooB;
import com.fake.fooA;
public class B {}

and the maven config looks like:
 
org.apache.maven.plugins
maven-shade-plugin
2.4.3

  
  
package

  shade


  false
  true
  true
  

  com.fake
  .com.fake.shaded
  
com.fake.fooA.*
  



Then the shade plugin will modify the B's source file to be:
package com.fake.shaded.fooB;
import com.fake.shaded.fooA;
public class B {}

Notice that package A's path was also updated, which is wrong as it's not got 
relocated.


> shadeSourcesContent is broken when combined with partial relocation
> ---
>
> Key: MSHADE-252
> URL: https://issues.apache.org/jira/browse/MSHADE-252
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4.3, 3.0.0
>Reporter: Zhenyu Yang
>  Labels: easyfix
>
> per description in 
> https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#shadeSourcesContent,
>  when set it to true, 
> "it will attempt to shade the contents of the java source files when creating 
> the sources jar." However, it seems will blindly shade all the source files 
> include those are excluded from relocation rules.
> This could be illustrated with a simple example:
> Assume there are two classes defined in two packages as below:
> {code:title=A.java}
> package com.fake.fooA;
> import com.fake.fooB;
> public Class A {}
> {code}
> {code:title=B.java}
> package com.fake.fooB;
> import com.fake.fooA;
> public class B {}
> {code}
> and the maven config looks like:
> {code:xml}
>  
> org.apache.maven.plugins
> maven-shade-plugin
> 2.4.3
> 
>   
>   
> package
> 
>   shade
> 
> 
>   false
>   true
>   true
>   
> 
>   com.fake
>   .com.fake.shaded
>   
> com.fake.fooA.*
>   
> 
> 
> {code}
> Then the shade plugin will modify the B's source file to be:
> {code}
> package com.fake.shaded.fooB;
> import com.fake.shaded.fooA;
> public class B {}
> {code}
> Notice that package A's path was also updated, which is wrong as it's not got 
> relocated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MSHADE-254) NullPointerException thrown by Maven Shade Plugin 3.0.0

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MSHADE-254.
-
Resolution: Duplicate
  Assignee: Robert Scholte

> NullPointerException thrown by Maven Shade Plugin 3.0.0
> ---
>
> Key: MSHADE-254
> URL: https://issues.apache.org/jira/browse/MSHADE-254
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: Maven 3.5.0
>Reporter: Rafael Winterhalter
>Assignee: Robert Scholte
> Attachments: maven-shade-plugin-254-patch.diff
>
>
> When building my project https://github.com/raphw/byte-buddy, a null pointer 
> exception is thrown with 3.0.0 that did not occur before:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
> byte-buddy: Execution default of goal 
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade failed.: 
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on 
> project byte-buddy: Execution default of goal 
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>   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:309)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>   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.PluginExecutionException: Execution 
> default of goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 20 more
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.resolveArtifactSources(ShadeMojo.java:730)
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.processArtifactSelectors(ShadeMojo.java:627)
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:425)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   ... 21 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MSHADE-257) Bad zero length source jars published by 3rd parties cause source jar creation to fail.

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MSHADE-257.
-
   Resolution: Fixed
 Assignee: Robert Scholte
Fix Version/s: 3.0.1

Fixed in [1805504|http://svn.apache.org/viewvc?rev=1805504=rev]
Thanks for the patch!

> Bad zero length source jars published by 3rd parties cause source jar 
> creation to fail.
> ---
>
> Key: MSHADE-257
> URL: https://issues.apache.org/jira/browse/MSHADE-257
> Project: Maven Shade Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Jess
>Assignee: Robert Scholte
> Fix For: 3.0.1
>
> Attachments: maven-shade-plugin-257-patch.diff
>
>
> If a transient dependency that is being  shaded (in my case 
> xmlpull:xmlpull:1.1.3.1) published a zero length source jar, then the source 
> generation will throw a zip exception and abort the build.  The plugin should 
> guard against this and issue a warning instead of failing.
> A patch with the guard will be attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MSHADE-254) NullPointerException thrown by Maven Shade Plugin 3.0.0

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MSHADE-254:
--
Description: 
When building my project https://github.com/raphw/byte-buddy, a null pointer 
exception is thrown with 3.0.0 that did not occur before:
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
byte-buddy: Execution default of goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade failed.: 
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
byte-buddy: Execution default of goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade failed.
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
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:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
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.PluginExecutionException: Execution default 
of goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade failed.
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.NullPointerException
at 
org.apache.maven.plugins.shade.mojo.ShadeMojo.resolveArtifactSources(ShadeMojo.java:730)
at 
org.apache.maven.plugins.shade.mojo.ShadeMojo.processArtifactSelectors(ShadeMojo.java:627)
at 
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:425)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
{noformat}

  was:
When building my project https://github.com/raphw/byte-buddy, a null pointer 
exception is thrown with 3.0.0 that did not occur before:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
byte-buddy: Execution default of goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade failed.: 
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
byte-buddy: Execution default of goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade failed.
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
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 

[jira] [Closed] (MSHADE-255) IllegalArgumentException on relocating class

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MSHADE-255.
-
   Resolution: Duplicate
 Assignee: Robert Scholte
Fix Version/s: 3.0.1

Should be fixed with MSHADE-258

> IllegalArgumentException on relocating class
> 
>
> Key: MSHADE-255
> URL: https://issues.apache.org/jira/browse/MSHADE-255
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: $ mvn -version
> Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-72-generic", arch: "amd64", family: "unix"
> [INFO] Plugin Resolved: maven-shade-plugin-3.0.0.jar
> [INFO] Plugin Dependency Resolved: maven-plugin-api-3.0.jar
> [INFO] Plugin Dependency Resolved: maven-model-3.0.jar
> [INFO] Plugin Dependency Resolved: maven-core-3.0.jar
> [INFO] Plugin Dependency Resolved: maven-artifact-3.0.jar
> [INFO] Plugin Dependency Resolved: plexus-utils-3.0.24.jar
> [INFO] Plugin Dependency Resolved: maven-artifact-transfer-0.9.0.jar
> [INFO] Plugin Dependency Resolved: asm-5.1.jar
> [INFO] Plugin Dependency Resolved: asm-commons-5.1.jar
> [INFO] Plugin Dependency Resolved: jdom-1.1.3.jar
> [INFO] Plugin Dependency Resolved: maven-dependency-tree-2.2.jar
> [INFO] Plugin Dependency Resolved: commons-io-2.5.jar
> [INFO] Plugin Dependency Resolved: jdependency-1.1.jar
> [INFO] Plugin Dependency Resolved: guava-19.0.jar
>Reporter: eliuser2
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 3.0.1
>
>
> {code:xml}
> 
> 
> package
> 
> shade
> 
> 
> 
> 
> 
> 
> org.jdom
> 
> my.company.shaded.org.jdom
> 
> 
> 
> 
> 
> 
> {code}
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
> spark-uberjar: Error creating shaded jar: null: IllegalArgumentException -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on 
> project spark-uberjar: 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 
> 

[jira] [Updated] (MSHADE-255) IllegalArgumentException on relocating class

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MSHADE-255:
--
Description: 
{code:xml}


package

shade






org.jdom

my.company.shaded.org.jdom






{code}

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
spark-uberjar: Error creating shaded jar: null: IllegalArgumentException -> 
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
spark-uberjar: 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:546)
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.IllegalArgumentException
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at 
org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:418)
at 
org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar(DefaultShader.java:220)
at 
org.apache.maven.plugins.shade.DefaultShader.shadeJars(DefaultShader.java:181)
at 
org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:104)
at 
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:442)
... 22 more
{noformat}

  was:


package

shade





 

[jira] [Closed] (MSHADE-258) RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MSHADE-258.
-
   Resolution: Fixed
Fix Version/s: 3.0.1

Verified with [r1805503|http://svn.apache.org/viewvc?rev=1805503=rev]
Code change committed as part of MSHADE-242

> RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta
> -
>
> Key: MSHADE-258
> URL: https://issues.apache.org/jira/browse/MSHADE-258
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Ismael Juma
>Assignee: Robert Scholte
> Fix For: 3.0.1
>
>
> While trying to use the maven shade plugin with ASM 6.0 beta (for Java 9 
> support) in the easymock project, I ran into the following exception:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
> easymock: Error creating shaded jar: Error in ASM processing class 
> module-info.class: RemappingClassAdapter is deprecated, use ClassRemapper 
> instead -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on 
> project easymock: Error creating shaded jar: Error in ASM processing class 
> module-info.class
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>   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:309)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   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: Error in ASM processing class module-info.class
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 20 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error in ASM 
> processing class module-info.class
>   at 
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:453)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar(DefaultShader.java:220)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeJars(DefaultShader.java:181)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:104)
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:442)
>   ... 22 more
> Caused by: java.lang.RuntimeException: RemappingClassAdapter is deprecated, 
> use ClassRemapper instead
>   at org.objectweb.asm.commons.RemappingClassAdapter.visitModule(Unknown 
> Source)
>   at org.objectweb.asm.ClassReader.a(Unknown Source)
>   at org.objectweb.asm.ClassReader.accept(Unknown Source)
>   at org.objectweb.asm.ClassReader.accept(Unknown Source)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:449)
> {code}
> Link to the exception:
> 

[jira] [Closed] (MSHADE-242) Plugin does not work with Java 9

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MSHADE-242.
-
   Resolution: Fixed
Fix Version/s: 3.0.1

Fixed in [r1805501|http://svn.apache.org/viewvc?rev=1805501=rev]

> Plugin does not work with Java 9
> 
>
> Key: MSHADE-242
> URL: https://issues.apache.org/jira/browse/MSHADE-242
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4.3
> Environment: ╰─✘ java -version
> openjdk version "9-internal"
> OpenJDK Runtime Environment (build 9-internal+0-2016-11-17-101644.norman.jdk9)
> OpenJDK 64-Bit Server VM (build 9-internal+0-2016-11-17-101644.norman.jdk9, 
> mixed mode)
>Reporter: Norman Maurer
>Assignee: Robert Scholte
> Fix For: 3.0.1
>
>
> When trying to use the shade plugin with java9  I get:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on project 
> netty-common: Error creating shaded jar: null: IllegalArgumentException -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on 
> project netty-common: 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 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:537)
>   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.IllegalArgumentException
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
>   at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
>   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
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MSHADE-242) Plugin does not work with Java 9

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte reassigned MSHADE-242:
-

Assignee: Robert Scholte

> Plugin does not work with Java 9
> 
>
> Key: MSHADE-242
> URL: https://issues.apache.org/jira/browse/MSHADE-242
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4.3
> Environment: ╰─✘ java -version
> openjdk version "9-internal"
> OpenJDK Runtime Environment (build 9-internal+0-2016-11-17-101644.norman.jdk9)
> OpenJDK 64-Bit Server VM (build 9-internal+0-2016-11-17-101644.norman.jdk9, 
> mixed mode)
>Reporter: Norman Maurer
>Assignee: Robert Scholte
>
> When trying to use the shade plugin with java9  I get:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on project 
> netty-common: Error creating shaded jar: null: IllegalArgumentException -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on 
> project netty-common: 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 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:537)
>   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.IllegalArgumentException
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.objectweb.asm.ClassReader.(Unknown Source)
>   at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
>   at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
>   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
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MSHADE-258) RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte reassigned MSHADE-258:
-

Assignee: Robert Scholte

> RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta
> -
>
> Key: MSHADE-258
> URL: https://issues.apache.org/jira/browse/MSHADE-258
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Ismael Juma
>Assignee: Robert Scholte
>
> While trying to use the maven shade plugin with ASM 6.0 beta (for Java 9 
> support) in the easymock project, I ran into the following exception:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project 
> easymock: Error creating shaded jar: Error in ASM processing class 
> module-info.class: RemappingClassAdapter is deprecated, use ClassRemapper 
> instead -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on 
> project easymock: Error creating shaded jar: Error in ASM processing class 
> module-info.class
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>   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:309)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   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: Error in ASM processing class module-info.class
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 20 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error in ASM 
> processing class module-info.class
>   at 
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:453)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar(DefaultShader.java:220)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeJars(DefaultShader.java:181)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:104)
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:442)
>   ... 22 more
> Caused by: java.lang.RuntimeException: RemappingClassAdapter is deprecated, 
> use ClassRemapper instead
>   at org.objectweb.asm.commons.RemappingClassAdapter.visitModule(Unknown 
> Source)
>   at org.objectweb.asm.ClassReader.a(Unknown Source)
>   at org.objectweb.asm.ClassReader.accept(Unknown Source)
>   at org.objectweb.asm.ClassReader.accept(Unknown Source)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:449)
> {code}
> Link to the exception:
> https://gitlab.ow2.org/asm/asm/blob/master/src/org/objectweb/asm/commons/RemappingClassAdapter.java#L75
> Link to the change that deprecated the class:
> 

[jira] [Comment Edited] (SUREFIRE-1365) Allow environment variables to be read from a file, instead of set as a Map

[Darius Cooper (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134054#comment-16134054
 ] 

Darius Cooper edited comment on SUREFIRE-1365 at 8/19/17 10:55 AM:
---

I'm not sure how we could reuse the existing variable. 
Just as 2.20 has systemPropertyVariables and systemPropertiesFile, 
wouldn't this need a new variable, 
say, environmentVariables and environmentFile (or environmentVariablesFile)
Can a config parameter be of either one type or another? If so, are there 
existing examples?

I would have that that we add another config parameter, and only 
AbstractSurefireMojo is aware of its existence: any variables read from the 
file are combined with the one's set via the in-line Map


was (Author: dariusx):
I'm not sure how we could reuse the existing variable. 
Just as 2.20 has systemPropertyVariables and systemPropertiesFile, 
wouldn't this need a new variable, 
say, environmentVariables and environmentFile (or environmentVariablesFile)
Can a config parameter be of either one type or another? If so, are there 
existing examples?

> Allow environment variables to be read from a file, instead of set as a Map
> ---
>
> Key: SUREFIRE-1365
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1365
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Darius Cooper
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 3.0, 3.0-RC1
>
>
> With 12-factors apps and deployment on platforms like OpenShift, there a new 
> push on using Environment Variables for configuration. When running 
> Integration tests with Failsafe, it would be nice to set the same variables 
> as will be set to the target environment. 
> Often, there's a file that contains the variables in a key-value pair format, 
> just like a properties file. It would be nice to be able to read that same 
> file in while setting environment variables for Failsafe and also when 
> deploying.
> (There may be some type of simple file-formatting differences, but that's 
> typically easy to handle in an automated way.)
> failsafe:integration-test supports an "environmentVariables" parameter. It 
> would nice if it could support an "environmentVariablesFile" parameter that 
> allowed a simple properties-style file to be read in an set as environment 
> variables.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MEJB-115) Wrong default EJB version stated on Usage page

[Anders Hammar (JIRA)]

[ 
https://issues.apache.org/jira/browse/MEJB-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134064#comment-16134064
 ] 

Anders Hammar commented on MEJB-115:


Fixed in [r1805498|http://svn.apache.org/r1805498]

> Wrong default EJB version stated on Usage page
> --
>
> Key: MEJB-115
> URL: https://issues.apache.org/jira/browse/MEJB-115
> Project: Maven EJB Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Anders Hammar
>Priority: Minor
> Fix For: 3.0.1
>
>
> On the Usage page, it is stated that the default EJB version is "2.1". This 
> was changed in v3.0.0 of the plugin to "3.1". This doc page needs to be 
> updated. We should rewrite the text so that we do not have this hard-coded to 
> prevent this to happen again in the future.
> Also, the sentence "In EJB3, the ejb-jar.xml deployment descriptor is not 
> mandatory anymore." could also be removed in this paragraph as it is somewhat 
> confusing in this text where we talk about how to configure/use the plugin.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MEJB-115) Wrong default EJB version stated on Usage page

[Anders Hammar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEJB-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anders Hammar resolved MEJB-115.

Resolution: Fixed

> Wrong default EJB version stated on Usage page
> --
>
> Key: MEJB-115
> URL: https://issues.apache.org/jira/browse/MEJB-115
> Project: Maven EJB Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Anders Hammar
>Priority: Minor
> Fix For: 3.0.1
>
>
> On the Usage page, it is stated that the default EJB version is "2.1". This 
> was changed in v3.0.0 of the plugin to "3.1". This doc page needs to be 
> updated. We should rewrite the text so that we do not have this hard-coded to 
> prevent this to happen again in the future.
> Also, the sentence "In EJB3, the ejb-jar.xml deployment descriptor is not 
> mandatory anymore." could also be removed in this paragraph as it is somewhat 
> confusing in this text where we talk about how to configure/use the plugin.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MJMOD-1) Upgrade dependencies in component

[Karl Heinz Marbaise (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MJMOD-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MJMOD-1.
---
Resolution: Fixed

Done in [r1805497|https://svn.apache.org/r1805497]

> Upgrade dependencies in component
> -
>
> Key: MJMOD-1
> URL: https://issues.apache.org/jira/browse/MJMOD-1
> Project: Maven JMod Plugin
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 1.0.0-alpha
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MJMOD-1) Upgrade dependencies in component

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJMOD-1:
---

 Summary: Upgrade dependencies in component
 Key: MJMOD-1
 URL: https://issues.apache.org/jira/browse/MJMOD-1
 Project: Maven JMod Plugin
  Issue Type: Improvement
Affects Versions: 1.0.0-alpha
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Priority: Trivial
 Fix For: 1.0.0-alpha






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MEJB-115) Wrong default EJB version stated on Usage page

[Anders Hammar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MEJB-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anders Hammar reassigned MEJB-115:
--

Assignee: Anders Hammar

> Wrong default EJB version stated on Usage page
> --
>
> Key: MEJB-115
> URL: https://issues.apache.org/jira/browse/MEJB-115
> Project: Maven EJB Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Anders Hammar
>Priority: Minor
> Fix For: 3.0.1
>
>
> On the Usage page, it is stated that the default EJB version is "2.1". This 
> was changed in v3.0.0 of the plugin to "3.1". This doc page needs to be 
> updated. We should rewrite the text so that we do not have this hard-coded to 
> prevent this to happen again in the future.
> Also, the sentence "In EJB3, the ejb-jar.xml deployment descriptor is not 
> mandatory anymore." could also be removed in this paragraph as it is somewhat 
> confusing in this text where we talk about how to configure/use the plugin.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MEJB-115) Wrong default EJB version stated on Usage page

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MEJB-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134057#comment-16134057
 ] 

Karl Heinz Marbaise commented on MEJB-115:
--

Do you have a good suggestions how the text could look like?

> Wrong default EJB version stated on Usage page
> --
>
> Key: MEJB-115
> URL: https://issues.apache.org/jira/browse/MEJB-115
> Project: Maven EJB Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: n/a
>Reporter: Anders Hammar
>Priority: Minor
> Fix For: 3.0.1
>
>
> On the Usage page, it is stated that the default EJB version is "2.1". This 
> was changed in v3.0.0 of the plugin to "3.1". This doc page needs to be 
> updated. We should rewrite the text so that we do not have this hard-coded to 
> prevent this to happen again in the future.
> Also, the sentence "In EJB3, the ejb-jar.xml deployment descriptor is not 
> mandatory anymore." could also be removed in this paragraph as it is somewhat 
> confusing in this text where we talk about how to configure/use the plugin.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1365) Allow environment variables to be read from a file, instead of set as a Map

[Darius Cooper (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134054#comment-16134054
 ] 

Darius Cooper commented on SUREFIRE-1365:
-

I'm not sure how we could reuse the existing variable. 
Just as 2.20 has systemPropertyVariables and systemPropertiesFile, 
wouldn't this need a new variable, 
say, environmentVariables and environmentFile (or environmentVariablesFile)
Can a config parameter be of either one type or another? If so, are there 
existing examples?

> Allow environment variables to be read from a file, instead of set as a Map
> ---
>
> Key: SUREFIRE-1365
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1365
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Darius Cooper
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 3.0, 3.0-RC1
>
>
> With 12-factors apps and deployment on platforms like OpenShift, there a new 
> push on using Environment Variables for configuration. When running 
> Integration tests with Failsafe, it would be nice to set the same variables 
> as will be set to the target environment. 
> Often, there's a file that contains the variables in a key-value pair format, 
> just like a properties file. It would be nice to be able to read that same 
> file in while setting environment variables for Failsafe and also when 
> deploying.
> (There may be some type of simple file-formatting differences, but that's 
> typically easy to handle in an automated way.)
> failsafe:integration-test supports an "environmentVariables" parameter. It 
> would nice if it could support an "environmentVariablesFile" parameter that 
> allowed a simple properties-style file to be read in an set as environment 
> variables.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134048#comment-16134048
 ] 

ASF GitHub Bot commented on SUREFIRE-1384:
--

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/162
  
@Tibor17 when I run `mvn compile` I get:

```
Restricted to JDK 1.5 yet 
org.apache.maven.surefire:surefire-api:jar:2.19.2-SNAPSHOT:compile contains 
org/apache/maven/plugin/surefire/runorder/PrioritizedTest.class targeted to JDK 
1.6
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion 
failed with message:
Found Banned Dependency: 
org.apache.maven.surefire:surefire-api:jar:2.19.2-SNAPSHOT
```

Jenkins Build is also red. I don't know how to fix this. Can you help?


> Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
> 
>
> Key: SUREFIRE-1384
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1384
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: JUnit 5.x support
>Reporter: Benedikt Ritter
> Fix For: 3.0-RC1
>
>
> In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we 
> need to add the corresponding ProviderInfo implementation to 
> AbstractSurefireMojo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134047#comment-16134047
 ] 

ASF GitHub Bot commented on SUREFIRE-1384:
--

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/153
  
See #162 


> Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
> 
>
> Key: SUREFIRE-1384
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1384
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: JUnit 5.x support
>Reporter: Benedikt Ritter
> Fix For: 3.0-RC1
>
>
> In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we 
> need to add the corresponding ProviderInfo implementation to 
> AbstractSurefireMojo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134042#comment-16134042
 ] 

ASF GitHub Bot commented on SUREFIRE-1384:
--

GitHub user britter opened a pull request:

https://github.com/apache/maven-surefire/pull/162

SUREFIRE-1384: ProviderInfo for JUnit Plattform (WIP)

Followup for #153 

This is Work in Progress! First take on a JUnitPlattform ProviderInfo, to 
enable automatic provider lookup.

Need help to get things working :)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/britter/maven-surefire SUREFIRE-1384

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-surefire/pull/162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #162


commit 1a7dd9b84f8462fa841e015826b44c553ff64b5e
Author: Benedikt Ritter 
Date:   2017-06-08T12:46:04Z

SUREFIRE-1384: Start implemeting JUnit Plattform ProviderInfo for automatic
provider lookup




> Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
> 
>
> Key: SUREFIRE-1384
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1384
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: JUnit 5.x support
>Reporter: Benedikt Ritter
> Fix For: 3.0-RC1
>
>
> In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we 
> need to add the corresponding ProviderInfo implementation to 
> AbstractSurefireMojo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134041#comment-16134041
 ] 

ASF GitHub Bot commented on SUREFIRE-1384:
--

Github user britter closed the pull request at:

https://github.com/apache/maven-surefire/pull/153


> Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
> 
>
> Key: SUREFIRE-1384
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1384
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: JUnit 5.x support
>Reporter: Benedikt Ritter
> Fix For: 3.0-RC1
>
>
> In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we 
> need to add the corresponding ProviderInfo implementation to 
> AbstractSurefireMojo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134040#comment-16134040
 ] 

ASF GitHub Bot commented on SUREFIRE-1384:
--

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/153
  
Opening a new PR against junit5 branch!


> Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
> 
>
> Key: SUREFIRE-1384
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1384
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: JUnit 5.x support
>Reporter: Benedikt Ritter
> Fix For: 3.0-RC1
>
>
> In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we 
> need to add the corresponding ProviderInfo implementation to 
> AbstractSurefireMojo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MPMD-239) Add documentation about upgrading PMD version at runtime

[Andreas Dangel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPMD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Dangel updated MPMD-239:

Description: 
The documentation should be similar to 
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html

Example configuration, to use m-pmd-p 3.8 + PMD "choose your version":

{noformat}

  
...choose your version...
  
...
  

  

  org.apache.maven.plugins
  maven-pmd-plugin
  3.8
  

  net.sourceforge.pmd
  pmd-core
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-java
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-javascript
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-jsp
  ${pmdVersion}

  

  

  
...

{noformat}

See also https://github.com/pmd/pmd/issues/402



  was:
The documentation should be similar to 
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html

Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:

{noformat}

  
...choose your version...
  
...
  

  

  org.apache.maven.plugins
  maven-pmd-plugin
  3.8
  

  net.sourceforge.pmd
  pmd-core
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-java
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-javascript
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-jsp
  ${pmdVersion}

  

  

  
...

{noformat}

See also https://github.com/pmd/pmd/issues/402




> Add documentation about upgrading PMD version at runtime
> 
>
> Key: MPMD-239
> URL: https://issues.apache.org/jira/browse/MPMD-239
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.9
>
>
> The documentation should be similar to 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
> Example configuration, to use m-pmd-p 3.8 + PMD "choose your version":
> {noformat}
> 
>   
> ...choose your version...
>   
> ...
>   
> 
>   
> 
>   org.apache.maven.plugins
>   maven-pmd-plugin
>   3.8
>   
> 
>   net.sourceforge.pmd
>   pmd-core
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-java
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-javascript
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-jsp
>   ${pmdVersion}
> 
>   
> 
>   
> 
>   
> ...
> 
> {noformat}
> See also https://github.com/pmd/pmd/issues/402



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPMD-239) Add documentation about upgrading PMD version at runtime

[Andreas Dangel (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPMD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134037#comment-16134037
 ] 

Andreas Dangel commented on MPMD-239:
-

Fixed in [r1805494|https://svn.apache.org/r1805494].

> Add documentation about upgrading PMD version at runtime
> 
>
> Key: MPMD-239
> URL: https://issues.apache.org/jira/browse/MPMD-239
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.9
>
>
> The documentation should be similar to 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
> Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:
> {noformat}
> 
>   
> ...choose your version...
>   
> ...
>   
> 
>   
> 
>   org.apache.maven.plugins
>   maven-pmd-plugin
>   3.8
>   
> 
>   net.sourceforge.pmd
>   pmd-core
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-java
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-javascript
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-jsp
>   ${pmdVersion}
> 
>   
> 
>   
> 
>   
> ...
> 
> {noformat}
> See also https://github.com/pmd/pmd/issues/402



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MPMD-239) Add documentation about upgrading PMD version at runtime

[Andreas Dangel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPMD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Dangel resolved MPMD-239.
-
Resolution: Fixed

> Add documentation about upgrading PMD version at runtime
> 
>
> Key: MPMD-239
> URL: https://issues.apache.org/jira/browse/MPMD-239
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.9
>
>
> The documentation should be similar to 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
> Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:
> {noformat}
> 
>   
> ...choose your version...
>   
> ...
>   
> 
>   
> 
>   org.apache.maven.plugins
>   maven-pmd-plugin
>   3.8
>   
> 
>   net.sourceforge.pmd
>   pmd-core
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-java
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-javascript
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-jsp
>   ${pmdVersion}
> 
>   
> 
>   
> 
>   
> ...
> 
> {noformat}
> See also https://github.com/pmd/pmd/issues/402



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPMD-241) Please provide the version relationship between plugin and pmd

[Andreas Dangel (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPMD-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134033#comment-16134033
 ] 

Andreas Dangel commented on MPMD-241:
-

[~tankilo] There is no direct relationship between the m-pmd-p version and its 
referenced PMD version.
The used version of PMD is however mentioned on the 
[index.html|https://maven.apache.org/plugins/maven-pmd-plugin/index.html] page. 
For the current version 3.8 of m-pmd-p, PMD 5.6.1 is used.
There is also the possibility, to upgrade the PMD version at runtime, see 
MPMD-239

For the older version, you can look up the archived documentations under 
http://maven.apache.org/plugins-archives/, e.g. [m-pmd-p 
3.7|http://maven.apache.org/plugins-archives/maven-pmd-plugin-3.7/] used PMD 
5.5.1.

What exactly is your use case?

Regards,
Andreas

> Please provide the version relationship between plugin and pmd
> --
>
> Key: MPMD-241
> URL: https://issues.apache.org/jira/browse/MPMD-241
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>Reporter: tankilo
>Priority: Minor
>
> I search through https://maven.apache.org/plugins/maven-pmd-plugin/index.html
> and failed to find any release history that explains the version relationship 
> between maven pmd plugin and pmd itself.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MPMD-239) Add documentation about upgrading PMD version at runtime

[Andreas Dangel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPMD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Dangel updated MPMD-239:

Description: 
The documentation should be similar to 
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html

Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:

{noformat}

  
...choose your version...
  
...
  

  

  org.apache.maven.plugins
  maven-pmd-plugin
  3.8
  

  net.sourceforge.pmd
  pmd-core
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-java
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-javascript
  ${pmdVersion}


  net.sourceforge.pmd
  pmd-jsp
  ${pmdVersion}

  

  

  
...

{noformat}

See also https://github.com/pmd/pmd/issues/402



  was:
The documentation should be similar to 
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html

Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:

{noformat}

  
...choose your version...
  
...
  

  

  org.apache.maven.plugins
  maven-pmd-plugin
  ${project.version}
  

  net.sourceforge.pmd
  pmd-core
  \${pmdVersion}


  net.sourceforge.pmd
  pmd-java
  \${pmdVersion}


  net.sourceforge.pmd
  pmd-javascript
  \${pmdVersion}


  net.sourceforge.pmd
  pmd-jsp
  \${pmdVersion}

  

  

  
...

{noformat}

See also https://github.com/pmd/pmd/issues/402




> Add documentation about upgrading PMD version at runtime
> 
>
> Key: MPMD-239
> URL: https://issues.apache.org/jira/browse/MPMD-239
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.9
>
>
> The documentation should be similar to 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
> Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:
> {noformat}
> 
>   
> ...choose your version...
>   
> ...
>   
> 
>   
> 
>   org.apache.maven.plugins
>   maven-pmd-plugin
>   3.8
>   
> 
>   net.sourceforge.pmd
>   pmd-core
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-java
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-javascript
>   ${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-jsp
>   ${pmdVersion}
> 
>   
> 
>   
> 
>   
> ...
> 
> {noformat}
> See also https://github.com/pmd/pmd/issues/402



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MPMD-239) Add documentation about upgrading PMD version at runtime

[Andreas Dangel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPMD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Dangel updated MPMD-239:

Description: 
The documentation should be similar to 
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html

Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:

{noformat}

  
...choose your version...
  
...
  

  

  org.apache.maven.plugins
  maven-pmd-plugin
  ${project.version}
  

  net.sourceforge.pmd
  pmd-core
  \${pmdVersion}


  net.sourceforge.pmd
  pmd-java
  \${pmdVersion}


  net.sourceforge.pmd
  pmd-javascript
  \${pmdVersion}


  net.sourceforge.pmd
  pmd-jsp
  \${pmdVersion}

  

  

  
...

{noformat}

See also https://github.com/pmd/pmd/issues/402



  was:
The documentation should be similar to 
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html

Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:

{noformat}
  
org.apache.maven.plugins
maven-pmd-plugin
3.8


net.sourceforge.pmd
pmd-core
5.7.0


net.sourceforge.pmd
pmd-java
5.7.0

  
  
{noformat}

See also https://github.com/pmd/pmd/issues/402




> Add documentation about upgrading PMD version at runtime
> 
>
> Key: MPMD-239
> URL: https://issues.apache.org/jira/browse/MPMD-239
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.9
>
>
> The documentation should be similar to 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
> Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:
> {noformat}
> 
>   
> ...choose your version...
>   
> ...
>   
> 
>   
> 
>   org.apache.maven.plugins
>   maven-pmd-plugin
>   ${project.version}
>   
> 
>   net.sourceforge.pmd
>   pmd-core
>   \${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-java
>   \${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-javascript
>   \${pmdVersion}
> 
> 
>   net.sourceforge.pmd
>   pmd-jsp
>   \${pmdVersion}
> 
>   
> 
>   
> 
>   
> ...
> 
> {noformat}
> See also https://github.com/pmd/pmd/issues/402



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MPMD-240) Migrate plugin to Maven 3.0

[Andreas Dangel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPMD-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Dangel updated MPMD-240:

Description: 
Cloning from MCHECKSTYLE-335 to address the same slf4j issues based on the old 
maven-core-2.2.1 dependencies.

See 
https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
 for more info

  was:Cloning from MCHECKSTYLE-335 to address the same slf4j issues based on 
the old maven-core-2.2.1 dependencies.


> Migrate plugin to Maven 3.0
> ---
>
> Key: MPMD-240
> URL: https://issues.apache.org/jira/browse/MPMD-240
> Project: Maven PMD Plugin
>  Issue Type: Bug
>  Components: PMD
>Affects Versions: 3.8
>Reporter: Matt Nelson
>
> Cloning from MCHECKSTYLE-335 to address the same slf4j issues based on the 
> old maven-core-2.2.1 dependencies.
> See 
> https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
>  for more info



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MPMD-239) Add documentation about upgrading PMD version at runtime

[Andreas Dangel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPMD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Dangel reassigned MPMD-239:
---

Assignee: Andreas Dangel

> Add documentation about upgrading PMD version at runtime
> 
>
> Key: MPMD-239
> URL: https://issues.apache.org/jira/browse/MPMD-239
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.9
>
>
> The documentation should be similar to 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
> Example configuration, to use m-pmd-p 3.8 + PMD 5.7.0:
> {noformat}
>   
> org.apache.maven.plugins
> maven-pmd-plugin
> 3.8
> 
> 
> net.sourceforge.pmd
> pmd-core
> 5.7.0
> 
> 
> net.sourceforge.pmd
> pmd-java
> 5.7.0
> 
>   
>   
> {noformat}
> See also https://github.com/pmd/pmd/issues/402



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MJARSIGNER-53) Add support of the certchain parameter to the "sign" mojo

[*$^¨%`£]

 [ 
https://issues.apache.org/jira/browse/MJARSIGNER-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy (*$^¨%`£) closed MJARSIGNER-53.

Resolution: Fixed

All done.
Thanks [~oleg_nenashev]

> Add support of the certchain parameter to the "sign" mojo
> -
>
> Key: MJARSIGNER-53
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-53
> Project: Maven Jar Signer Plugin
>  Issue Type: New Feature
>Reporter: Oleg Nenashev
>Assignee: Olivier Lamy (*$^¨%`£)
>  Labels: java7, options, signing
> Fix For: 3.0.0
>
>
> "certchain" parameter has been added to jarsigner in Java SE 7. In my case it 
> is required to do signing of JAR's with a hardware key (see 
> [JENKINS-37567|https://issues.jenkins-ci.org/browse/JENKINS-37567]).
> I propose to add a new option to JAR Signer Lib and to Maven JarSigner 
> Plugin. This option should be opt-in in order to keep the plugin compatible 
> with the Java 6 flow



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MJARSIGNER-53) Add support of the certchain parameter to the "sign" mojo

[*$^¨%`£]

 [ 
https://issues.apache.org/jira/browse/MJARSIGNER-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy (*$^¨%`£) reassigned MJARSIGNER-53:


Assignee: Olivier Lamy (*$^¨%`£)

> Add support of the certchain parameter to the "sign" mojo
> -
>
> Key: MJARSIGNER-53
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-53
> Project: Maven Jar Signer Plugin
>  Issue Type: New Feature
>Reporter: Oleg Nenashev
>Assignee: Olivier Lamy (*$^¨%`£)
>  Labels: java7, options, signing
> Fix For: 3.0.0
>
>
> "certchain" parameter has been added to jarsigner in Java SE 7. In my case it 
> is required to do signing of JAR's with a hardware key (see 
> [JENKINS-37567|https://issues.jenkins-ci.org/browse/JENKINS-37567]).
> I propose to add a new option to JAR Signer Lib and to Maven JarSigner 
> Plugin. This option should be opt-in in order to keep the plugin compatible 
> with the Java 6 flow



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MJARSIGNER-53) Add support of the certchain parameter to the "sign" mojo

[*$^¨%`£]

 [ 
https://issues.apache.org/jira/browse/MJARSIGNER-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy (*$^¨%`£) updated MJARSIGNER-53:
-
Fix Version/s: 3.0.0

> Add support of the certchain parameter to the "sign" mojo
> -
>
> Key: MJARSIGNER-53
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-53
> Project: Maven Jar Signer Plugin
>  Issue Type: New Feature
>Reporter: Oleg Nenashev
>  Labels: java7, options, signing
> Fix For: 3.0.0
>
>
> "certchain" parameter has been added to jarsigner in Java SE 7. In my case it 
> is required to do signing of JAR's with a hardware key (see 
> [JENKINS-37567|https://issues.jenkins-ci.org/browse/JENKINS-37567]).
> I propose to add a new option to JAR Signer Lib and to Maven JarSigner 
> Plugin. This option should be opt-in in order to keep the plugin compatible 
> with the Java 6 flow



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)