[jira] [Commented] (MJAVADOC-475) Replace parameter additionalparam with additionalOptions
[
https://issues.apache.org/jira/browse/MJAVADOC-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517817#comment-16517817
]
Jörg Sesterhenn commented on MJAVADOC-475:
--
I'm afraid not. Is there a working example for using a doclet you could point
out?
> Replace parameter additionalparam with additionalOptions
>
>
> Key: MJAVADOC-475
> URL: https://issues.apache.org/jira/browse/MJAVADOC-475
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0
>
>
> Introduce an {{additionalOptions}} parameter which allows to pass multiple
> arbitrary parameters to the {{javadoc}} process without the shortcomings of
> MJAVADOC-368.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-475) Replace parameter additionalparam with additionalOptions
[
https://issues.apache.org/jira/browse/MJAVADOC-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517437#comment-16517437
]
Robert Scholte commented on MJAVADOC-475:
-
Nice find, I wasn't aware this parameter was used in several examples. Can you
provide a PR?
> Replace parameter additionalparam with additionalOptions
>
>
> Key: MJAVADOC-475
> URL: https://issues.apache.org/jira/browse/MJAVADOC-475
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0
>
>
> Introduce an {{additionalOptions}} parameter which allows to pass multiple
> arbitrary parameters to the {{javadoc}} process without the shortcomings of
> MJAVADOC-368.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6429) Integration Test site publishing requires Java 7 (or javadoc errors ignored)
[
https://issues.apache.org/jira/browse/MNG-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517436#comment-16517436
]
Robert Scholte commented on MNG-6429:
-
Would be nice if we could improve the {{.JenkinsFile}} to run site once too
> Integration Test site publishing requires Java 7 (or javadoc errors ignored)
>
>
> Key: MNG-6429
> URL: https://issues.apache.org/jira/browse/MNG-6429
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.4
>Reporter: Stephen Connolly
>Priority: Critical
> Fix For: 3.5.4
>
>
> {code:java}
> [INFO]
> 7 errors
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Maven Core ITs 2.1-SNAPSHOT SUCCESS [ 38.586
> s]
> [INFO] Maven IT Support ... SUCCESS [ 2.726 s]
> [INFO] Maven IT :: Plugins SUCCESS [ 2.693 s]
> [INFO] Maven IT Plugin :: Active Collection ... FAILURE [ 15.162
> s]
> [INFO] Maven IT Plugin :: Ant-Based ... SKIPPED
> [INFO] Maven IT Plugin :: Artifact SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Dependency A SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Dependency B SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Dependency C SKIPPED
> [INFO] Maven IT Plugin :: Class Loader SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Aggregator .. SKIPPED
> [INFO] Maven IT Plugin :: Configuration ... SKIPPED
> [INFO] Maven IT Plugin :: Context Passing . SKIPPED
> [INFO] Maven ITs :: Core Plugin Stubs . SKIPPED
> [INFO] Maven IT Clean Plugin Stub 0.1-stub-SNAPSHOT ... SKIPPED
> [INFO] Maven IT Compiler Plugin Stub 0.1-stub-SNAPSHOT SKIPPED
> [INFO] Maven IT Deploy Plugin Stub 0.1-stub-SNAPSHOT .. SKIPPED
> [INFO] Maven IT EAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT EJB Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Install Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT JAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Javadoc Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Plugin Plugin Stub 0.1-stub-SNAPSHOT .. SKIPPED
> [INFO] Maven IT RAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Resources Plugin Stub 0.1-stub-SNAPSHOT ... SKIPPED
> [INFO] Maven IT Site Plugin Stub 0.1-stub-SNAPSHOT SKIPPED
> [INFO] Maven IT Source Plugin Stub 0.1-stub-SNAPSHOT .. SKIPPED
> [INFO] Maven IT Surefire Plugin Stub 0.1-stub-SNAPSHOT SKIPPED
> [INFO] Maven IT WAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Plugin :: Dependency Collection ... SKIPPED
> [INFO] Maven IT Plugin :: Dependency Resolution ... SKIPPED
> [INFO] Maven IT Plugin :: Expression .. SKIPPED
> [INFO] Maven IT Plugin :: Error Mojos . SKIPPED
> [INFO] Maven IT Component . SKIPPED
> [INFO] Maven IT Plugin :: Extension Consumer .. SKIPPED
> [INFO] Maven IT Plugin :: Extension Provider .. SKIPPED
> [INFO] Maven IT Plugin :: Fork SKIPPED
> [INFO] Maven IT Plugin :: Invalid Descriptor .. SKIPPED
> [INFO] Maven IT Plugin :: Log File SKIPPED
> [INFO] Maven IT Helper Library SKIPPED
> [INFO] Maven IT Plugin :: Model Interpolation . SKIPPED
> [INFO] Maven IT Plugin :: No Default Component SKIPPED
> [INFO] Maven IT Plugin :: No Project .. SKIPPED
> [INFO] Maven IT Plugin :: Online .. SKIPPED
> [INFO] Maven IT Plugin :: Optional Mojos .. SKIPPED
> [INFO] Maven IT Plugin :: Packaging ... SKIPPED
> [INFO] Maven IT Plugin :: Parameter Implementation SKIPPED
> [INFO] Maven IT Plugin :: Plugin Dependency ... SKIPPED
> [INFO] Maven IT Plugin :: Project . SKIPPED
> [INFO] Maven IT Plugin :: Project Interpolation ... SKIPPED
> [INFO] Maven IT Plugin :: Setter .. SKIPPED
> [INFO] Maven IT Plugin :: Singleton Component . SKIPPED
> [INFO] Maven IT Plugin :: Site SKIPPED
> [INFO] Maven IT Plugin :: Toolchain ... SKIPPED
> [INFO] Maven IT Plugin :: Touch ... SKIPPED
> [INFO] Maven IT Plugin :: Uses Properties Plugin .. SKIPPED
> [INFO] Maven IT Plugin :: Uses Wagon Plugin ... SKIPPED
> [INFO] Maven IT Plugin :: This
[jira] [Closed] (MJAVADOC-480) Javadoc generation broken on Java9 if there are references to javax.xml.bind.annontation.XmlElement and building code for java8
[
https://issues.apache.org/jira/browse/MJAVADOC-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAVADOC-480.
---
Resolution: Not A Problem
Assignee: Robert Scholte
> Javadoc generation broken on Java9 if there are references to
> javax.xml.bind.annontation.XmlElement and building code for java8
> ---
>
> Key: MJAVADOC-480
> URL: https://issues.apache.org/jira/browse/MJAVADOC-480
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Enrico Olivelli
>Assignee: Robert Scholte
>Priority: Minor
>
> The code uses javax.xml.bind.annotation.XmlElement annotations
> Plugin configuration:
> {code}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.10.4
>
> true
>
>
>
>
> attach-javadocs
>
> jar
>
>
>
>
> {code}
> This is my error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (attach-javadocs) on
> project scripting-api: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 -
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlField.java:22:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlField.java:23:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlRootElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlFieldValue.java:19:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlRootElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlDatabaseSchema.java:21:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlDatabaseSchema.java:22:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlRootElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/mock/MockContactsDB.java:27:
> error: package javax.xml.bind is not visible
> [ERROR] import javax.xml.bind.JAXB;
> [ERROR] ^
> [ERROR] (package javax.xml.bind is declared in module java.xml.bind, which is
> not in the module graph)
> [ERROR]
> [ERROR] Command line was:
> /home/diennea.lan/enrico.olivelli/dev/jdk-9/bin/javadoc @options @packages
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> '/home/diennea.lan/enrico.olivelli/dev/magnews/scripting/target/apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPOM-186) Upgrade several plugins to most recent versions for JDK9/10 Support
[ https://issues.apache.org/jira/browse/MPOM-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MPOM-186: - Description: * maven-clean-plugin 3.1.0 * maven-compiler-plugin 3.7.0 * maven-dependency-plugin 3.1.1 * maven-invoker-plugin 3.1.0 * maven-javadoc-plugin 3.0.1 * maven-resources-plugin 3.1.0 * maven-scm-publish-plugin 3.0.0 * maven-war-plugin 3.2.2 * maven-shade-plugin 3.1.1 This would imply to lift the JDK minimum to JDK 7 (maven.compiler.source are currently 1.6).. was: * maven-clean-plugin 3.1.0 * maven-compiler-plugin 3.7.0 * maven-dependency-plugin 3.1.1 * maven-invoker-plugin 3.1.0 * maven-javadoc-plugin 3.0.1 * maven-resources-plugin 3.1.0 * maven-scm-publish-plugin 3.0.0 * maven-war-plugin 3.2.2 * maven-shade-plugin 3.1.1 > Upgrade several plugins to most recent versions for JDK9/10 Support > --- > > Key: MPOM-186 > URL: https://issues.apache.org/jira/browse/MPOM-186 > Project: Maven POMs > Issue Type: Improvement >Affects Versions: ASF-20 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: ASF-20 > > > * maven-clean-plugin 3.1.0 > * maven-compiler-plugin 3.7.0 > * maven-dependency-plugin 3.1.1 > * maven-invoker-plugin 3.1.0 > * maven-javadoc-plugin 3.0.1 > * maven-resources-plugin 3.1.0 > * maven-scm-publish-plugin 3.0.0 > * maven-war-plugin 3.2.2 > * maven-shade-plugin 3.1.1 > This would imply to lift the JDK minimum to JDK 7 (maven.compiler.source are > currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MENFORCER-306) [REGRESSION] RequirePluginVersions fails
[
https://issues.apache.org/jira/browse/MENFORCER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517370#comment-16517370
]
Matt Benson commented on MENFORCER-306:
---
I must have misunderstood the requirements of the plugin. So it does not take
into account plugin versions that are specified by the super POM or by
lifecycle definitions?
BTW, I could not find the pom lifecycle def but even switching packaging to jar
I did indeed encounter a failure with my sample pom using enforcer 1.4.1, so
I'm just trying to understand the rule. Surely a plugin version is permitted to
be specified by a parent pom, just not the super pom?
Thanks,
Matt
> [REGRESSION] RequirePluginVersions fails
>
>
> Key: MENFORCER-306
> URL: https://issues.apache.org/jira/browse/MENFORCER-306
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-M2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: pom.xml
>
>
> I have found that running the {{RequirePluginVersions}} rule on a project
> with version {{3.0.0-M1}} works fine whereas it fails with version
> {{3.0.0-M2}}.
> {code}
> [DEBUG] Executing rule:
> org.apache.maven.plugins.enforcer.RequirePluginVersions
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = clean
> [DEBUG] plugins = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] plugin = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] GAV = [org.apache.maven.plugins, maven-clean-plugin, 2.5, clean]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = install
> [DEBUG] plugins = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] plugin = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] GAV = [org.apache.maven.plugins, maven-install-plugin, 2.4,
> install]
> [DEBUG] lifecycleMapping = deploy
> [DEBUG] plugins = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-deploy-plugin, 2.7, deploy]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = site
> [DEBUG] plugins = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, site]
> [DEBUG] lifecycleMapping = site-deploy
> [DEBUG] plugins = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, deploy]
> [DEBUG] All Plugins in use: [Plugin [org.tinyjee.dim:doxia-include-macro],
> Plugin [org.apache.maven.plugins:maven-clean-plugin], Plugin
> [org.apache.maven.plugins:maven-install-plugin], Plugin
> [org.apache.maven.plugins:maven-site-plugin], Plugin
> [org.apache.maven.plugins:maven-deploy-plugin], Plugin
> [org.jacoco:jacoco-maven-plugin], Plugin
> [org.apache.maven.plugins:maven-enforcer-plugin]]
> [DEBUG] plugin org.tinyjee.dim:doxia-include-macro not found
> [DEBUG] plugin org.apache.maven.plugins:maven-clean-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-install-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-site-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-deploy-plugin not found
> [DEBUG] plugin org.jacoco:jacoco-maven-plugin not found
> [DEBUG] Adding failure due to exception
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Some plugins are
> missing valid versions:(LATEST RELEASE SNAPSHOT are not allowed )
> org.tinyjee.dim:doxia-include-macro. The version currently in use is 1.1
> org.apache.maven.plugins:maven-clean-plugin. The version currently in use is
> 3.0.0
> org.apache.maven.plugins:maven-install-plugin.The version currently
> in use is 2.5.2
> org.apache.maven.plugins:maven-site-plugin. The version currently in use is
> 3.6
> org.apache.maven.plugins:maven-deploy-plugin. The version currently
> in use is 2.8.2
> org.jacoco:jacoco-maven-plugin. The version currently in use is 0.8.0
> Always define plugin versions! Never use LATEST or RELEASE.
> at org.apache.maven.plugins.enforcer.RequirePluginVersions.execute
> (RequirePluginVersions.java:320)
> at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:194)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPOM-168) JDK 9 required updated to plugins
[ https://issues.apache.org/jira/browse/MPOM-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517363#comment-16517363 ] Karl Heinz Marbaise commented on MPOM-168: -- Currently maven-enforcer-plugin has not yet been done in final 3.0.0 release but for other plugins etc. I have created MPOM-186 > JDK 9 required updated to plugins > - > > Key: MPOM-168 > URL: https://issues.apache.org/jira/browse/MPOM-168 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-19 >Reporter: Karl Heinz Marbaise >Priority: Minor > Fix For: ASF-20 > > > The following plugins needed to be updated to work with JDK 9: > * The maven-enforcer-plugin should be updated to final 3.0.0 release to make > the pom working with JDK 9... > * maven-shade-plugin should be upgraded to 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPOM-186) Upgrade several plugins to most recent versions for JDK9/10 Support
Karl Heinz Marbaise created MPOM-186: Summary: Upgrade several plugins to most recent versions for JDK9/10 Support Key: MPOM-186 URL: https://issues.apache.org/jira/browse/MPOM-186 Project: Maven POMs Issue Type: Improvement Affects Versions: ASF-20 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: ASF-20 * maven-clean-plugin 3.1.0 * maven-compiler-plugin 3.7.0 * maven-dependency-plugin 3.1.1 * maven-invoker-plugin 3.1.0 * maven-javadoc-plugin 3.0.1 * maven-resources-plugin 3.1.0 * maven-scm-publish-plugin 3.0.0 * maven-war-plugin 3.2.2 * maven-shade-plugin 3.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-185) jdk10 needs maven-surefire-plugin version 2.21.0
[
https://issues.apache.org/jira/browse/MPOM-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MPOM-185.
Resolution: Duplicate
Assignee: Karl Heinz Marbaise
Is solved by MPOM-184
> jdk10 needs maven-surefire-plugin version 2.21.0
>
>
> Key: MPOM-185
> URL: https://issues.apache.org/jira/browse/MPOM-185
> Project: Maven POMs
> Issue Type: Dependency upgrade
> Components: maven-plugins
>Affects Versions: ASF-19
> Environment: w7, mvn 3.5.3, jdk-10.0.1
>Reporter: Tilman Hausherr
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: jdk10
>
> The apache parent pom has this line
> {code}
> 2.20.1
> {code}
> however in jdk10 maven-surefire-plugin goes NPE. 2.21.0 works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without modifying any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517328#comment-16517328 ] Hudson commented on MENFORCER-142: -- Build succeeded in Jenkins: Maven TLP » maven-enforcer » code-improvements #2 See https://builds.apache.org/job/maven-box/job/maven-enforcer/job/code-improvements/2/ > Specify enforcer rule in command line without modifying any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.0 > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAR-253) Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.
[
https://issues.apache.org/jira/browse/MJAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517310#comment-16517310
]
Karl Heinz Marbaise commented on MJAR-253:
--
So after rereading the description I'm getting the impression you are doing
things wrong. If you like to create a zip via maven-assembly you can create
different jars by having different modules which produce appropriate jar's
which can simply gathered together with an assembly descriptor...The
{{finalName}} field not the correct way to go...apart from that it will only
change the name which is created in the {{target}} directory which brings my to
the conclusion that you are using a file based assembly descriptor approach...
> Since 3.0.0 builds fail with You have to use a classifier to attach
> supplemental artifacts to the project instead of replacing them.
>
>
> Key: MJAR-253
> URL: https://issues.apache.org/jira/browse/MJAR-253
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0
>Reporter: J.Cranendonk
>Priority: Minor
>
> See also:
> [https://stackoverflow.com/questions/40964500/maven-jar-plugin-3-0-2-error-you-have-to-use-a-classifier-to-attach-supplementa]
> https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16420958=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16420958
> https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16516772=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16516772
> Builds where multiple jars were created with different names using the
> finalName field (for example to create jars to put together in an assembly)
> are failing since version 3.0.0 of the plugin.
> Apparently cause they now require a classifier field to be set:
> You have to use a classifier to attach supplemental artifacts to the project
> instead of replacing them.
> The problem with fixing this by setting a classifier is that it gets added
> after the finalName field, including a dash, which means the final jar has
> the wrong name.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without modifying any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517300#comment-16517300 ] ASF GitHub Bot commented on MENFORCER-142: -- khmarbaise commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-398468023 Your PR has been merged. Thanks for your contribution. You can close your PR... This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Specify enforcer rule in command line without modifying any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.0 > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] khmarbaise commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli
khmarbaise commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-398468023 Your PR has been merged. Thanks for your contribution. You can close your PR... This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Assigned] (MPIR-370) org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPIR-370:
---
Assignee: Michael Osipov
> org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
> --
>
> Key: MPIR-370
> URL: https://issues.apache.org/jira/browse/MPIR-370
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.9
> Environment: java -version
> java version "10.0.1" 2018-04-17
> Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
> mvn -v
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T20:49:05+01:00)
> Maven home: C:\Program Files\apache-maven-3.5.3
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jre-10.0.1
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Peter Lamby
>Assignee: Michael Osipov
>Priority: Minor
>
> When running the Dependiencies report target with java 10 i get the following
> exception:
> {noformat}
> [WARNING] Unable to process class module-info.class in JarAnalyzer File
> C:\Users\plamby\.m2\repository\org\apache\logging\log4j\log4j-api\2.10.0\log4j-api-2.10.0.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
> pool: 19
> at org.apache.bcel.classfile.Constant.readConstant(Constant.java:161)
> at org.apache.bcel.classfile.ConstantPool.(ConstantPool.java:69)
> at
> org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:235)
> at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:143)
> at
> org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:96)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:259)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1542)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:545)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:240)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:201)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 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:564)
>
[jira] [Closed] (MNG-6369) fastly.com cdn for https://repo.maven.apache.org/maven2/ hangs for keep-alive http
[ https://issues.apache.org/jira/browse/MNG-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6369. --- Resolution: Not A Problem Fix Version/s: (was: waiting-for-feedback) > fastly.com cdn for https://repo.maven.apache.org/maven2/ hangs for keep-alive > http > -- > > Key: MNG-6369 > URL: https://issues.apache.org/jira/browse/MNG-6369 > Project: Maven > Issue Type: Bug >Reporter: Frank Ch. Eigler >Priority: Major > > Users with java clients that happen to use https with the "Connection: > keep-alive" header to fetch maven content from the fastly.com cdn of your > repo are experiencing hung connections. > To reproduce, observe hang with: ab -v 2 -H "User-Agent: curl/7.29.0" -c1 > -n1 -k [https://repo.maven.apache.org/maven2/] > Noting that there is no hang if one uses http:// or drops the -k. > Already reported to fastly: > [https://fastly.zendesk.com/hc/en-us/requests/73810] but they don't seem to > take the issue seriously, coming from me. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without modifying any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517257#comment-16517257 ] Hudson commented on MENFORCER-142: -- Build succeeded in Jenkins: Maven TLP » maven-enforcer » master #27 See https://builds.apache.org/job/maven-box/job/maven-enforcer/job/master/27/ > Specify enforcer rule in command line without modifying any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.0 > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MJAR-253) Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.
[ https://issues.apache.org/jira/browse/MJAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516989#comment-16516989 ] Karl Heinz Marbaise edited comment on MJAR-253 at 6/19/18 3:55 PM: --- Can you please create an example project which shows the use case and could you please explain the whole context of such use case...? was (Author: khmarbaise): Can you please create an example project which shows the use case? > Since 3.0.0 builds fail with You have to use a classifier to attach > supplemental artifacts to the project instead of replacing them. > > > Key: MJAR-253 > URL: https://issues.apache.org/jira/browse/MJAR-253 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0 >Reporter: J.Cranendonk >Priority: Minor > > See also: > [https://stackoverflow.com/questions/40964500/maven-jar-plugin-3-0-2-error-you-have-to-use-a-classifier-to-attach-supplementa] > https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16420958=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16420958 > https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16516772=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16516772 > Builds where multiple jars were created with different names using the > finalName field (for example to create jars to put together in an assembly) > are failing since version 3.0.0 of the plugin. > Apparently cause they now require a classifier field to be set: > You have to use a classifier to attach supplemental artifacts to the project > instead of replacing them. > The problem with fixing this by setting a classifier is that it gets added > after the finalName field, including a dash, which means the final jar has > the wrong name. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MENFORCER-306) [REGRESSION] RequirePluginVersions fails
[
https://issues.apache.org/jira/browse/MENFORCER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517253#comment-16517253
]
Karl Heinz Marbaise commented on MENFORCER-306:
---
[~tgr] That's what I have in mind too at the moment.
[~mbenson] Your example contains no definition of plugins at all and I expect
it to fail. This is the case where it should show you have to define plugin
versions
> [REGRESSION] RequirePluginVersions fails
>
>
> Key: MENFORCER-306
> URL: https://issues.apache.org/jira/browse/MENFORCER-306
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-M2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: pom.xml
>
>
> I have found that running the {{RequirePluginVersions}} rule on a project
> with version {{3.0.0-M1}} works fine whereas it fails with version
> {{3.0.0-M2}}.
> {code}
> [DEBUG] Executing rule:
> org.apache.maven.plugins.enforcer.RequirePluginVersions
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = clean
> [DEBUG] plugins = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] plugin = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] GAV = [org.apache.maven.plugins, maven-clean-plugin, 2.5, clean]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = install
> [DEBUG] plugins = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] plugin = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] GAV = [org.apache.maven.plugins, maven-install-plugin, 2.4,
> install]
> [DEBUG] lifecycleMapping = deploy
> [DEBUG] plugins = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-deploy-plugin, 2.7, deploy]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = site
> [DEBUG] plugins = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, site]
> [DEBUG] lifecycleMapping = site-deploy
> [DEBUG] plugins = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, deploy]
> [DEBUG] All Plugins in use: [Plugin [org.tinyjee.dim:doxia-include-macro],
> Plugin [org.apache.maven.plugins:maven-clean-plugin], Plugin
> [org.apache.maven.plugins:maven-install-plugin], Plugin
> [org.apache.maven.plugins:maven-site-plugin], Plugin
> [org.apache.maven.plugins:maven-deploy-plugin], Plugin
> [org.jacoco:jacoco-maven-plugin], Plugin
> [org.apache.maven.plugins:maven-enforcer-plugin]]
> [DEBUG] plugin org.tinyjee.dim:doxia-include-macro not found
> [DEBUG] plugin org.apache.maven.plugins:maven-clean-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-install-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-site-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-deploy-plugin not found
> [DEBUG] plugin org.jacoco:jacoco-maven-plugin not found
> [DEBUG] Adding failure due to exception
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Some plugins are
> missing valid versions:(LATEST RELEASE SNAPSHOT are not allowed )
> org.tinyjee.dim:doxia-include-macro. The version currently in use is 1.1
> org.apache.maven.plugins:maven-clean-plugin. The version currently in use is
> 3.0.0
> org.apache.maven.plugins:maven-install-plugin.The version currently
> in use is 2.5.2
> org.apache.maven.plugins:maven-site-plugin. The version currently in use is
> 3.6
> org.apache.maven.plugins:maven-deploy-plugin. The version currently
> in use is 2.8.2
> org.jacoco:jacoco-maven-plugin. The version currently in use is 0.8.0
> Always define plugin versions! Never use LATEST or RELEASE.
> at org.apache.maven.plugins.enforcer.RequirePluginVersions.execute
> (RequirePluginVersions.java:320)
> at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:194)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without modifying any pom
[
https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517251#comment-16517251
]
ASF GitHub Bot commented on MENFORCER-142:
--
khmarbaise closed pull request #36: [MENFORCER-142] documentation - add example
for checking rules via cli
URL: https://github.com/apache/maven-enforcer/pull/36
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/maven-enforcer-plugin/src/site/apt/examples/check-specific-rule-via-cli.apt.vm
b/maven-enforcer-plugin/src/site/apt/examples/check-specific-rule-via-cli.apt.vm
new file mode 100644
index 000..4c7389c
--- /dev/null
+++
b/maven-enforcer-plugin/src/site/apt/examples/check-specific-rule-via-cli.apt.vm
@@ -0,0 +1,34 @@
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distributed on an
+ ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~~ KIND, either express or implied. See the License for the
+ ~~ specific language governing permissions and limitations
+ ~~ under the License.
+
+ -
+ Check specific rule via CLI
+ -
+ Sandra Parsick
+ --
+ 2018-06-19
+ --
+
+Check specific rule via CLI
+
+ The <<>> goal can be used via cli to check specific enforcer rule
that isn't defined in the POM.
+
++---+
+mvn enforcer:enforce -Drules=alwaysPass,alwaysFail
++---+
+
+ A full list of built-in rules can be found
{{{../../../enforcer/enforcer-rules/index.html}here}}.
\ No newline at end of file
diff --git a/maven-enforcer-plugin/src/site/site.xml
b/maven-enforcer-plugin/src/site/site.xml
index 372dd43..9caae07 100644
--- a/maven-enforcer-plugin/src/site/site.xml
+++ b/maven-enforcer-plugin/src/site/site.xml
@@ -36,6 +36,9 @@ under the License.
+
+
+
https://cwiki.apache.org/confluence/display/MAVENOLD/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges"/>
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Specify enforcer rule in command line without modifying any pom
> ---
>
> Key: MENFORCER-142
> URL: https://issues.apache.org/jira/browse/MENFORCER-142
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
>Reporter: Arnaud Bourrée
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>
> Hello,
> How could we specify enforcer:enforce rules from command line?
> I want to run command line like following without updating any pom.xml:
> mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom
> The goal of this enforcer:enforce rule is to check that Acme's
> developers write pom.xml which inherit from acme's parent pom.xml
> And because they may not inherit from acme's parent pom.xml, I cannot
> specify enforcer rule in.
> Regards,
> Arnaud.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] khmarbaise closed pull request #36: [MENFORCER-142] documentation - add example for checking rules via cli
khmarbaise closed pull request #36: [MENFORCER-142] documentation - add example
for checking rules via cli
URL: https://github.com/apache/maven-enforcer/pull/36
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/maven-enforcer-plugin/src/site/apt/examples/check-specific-rule-via-cli.apt.vm
b/maven-enforcer-plugin/src/site/apt/examples/check-specific-rule-via-cli.apt.vm
new file mode 100644
index 000..4c7389c
--- /dev/null
+++
b/maven-enforcer-plugin/src/site/apt/examples/check-specific-rule-via-cli.apt.vm
@@ -0,0 +1,34 @@
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distributed on an
+ ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~~ KIND, either express or implied. See the License for the
+ ~~ specific language governing permissions and limitations
+ ~~ under the License.
+
+ -
+ Check specific rule via CLI
+ -
+ Sandra Parsick
+ --
+ 2018-06-19
+ --
+
+Check specific rule via CLI
+
+ The <<>> goal can be used via cli to check specific enforcer rule
that isn't defined in the POM.
+
++---+
+mvn enforcer:enforce -Drules=alwaysPass,alwaysFail
++---+
+
+ A full list of built-in rules can be found
{{{../../../enforcer/enforcer-rules/index.html}here}}.
\ No newline at end of file
diff --git a/maven-enforcer-plugin/src/site/site.xml
b/maven-enforcer-plugin/src/site/site.xml
index 372dd43..9caae07 100644
--- a/maven-enforcer-plugin/src/site/site.xml
+++ b/maven-enforcer-plugin/src/site/site.xml
@@ -36,6 +36,9 @@ under the License.
+
+
+
https://cwiki.apache.org/confluence/display/MAVENOLD/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges"/>
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Commented] (MNG-6369) fastly.com cdn for https://repo.maven.apache.org/maven2/ hangs for keep-alive http
[ https://issues.apache.org/jira/browse/MNG-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517224#comment-16517224 ] Frank Ch. Eigler commented on MNG-6369: --- Sure. > fastly.com cdn for https://repo.maven.apache.org/maven2/ hangs for keep-alive > http > -- > > Key: MNG-6369 > URL: https://issues.apache.org/jira/browse/MNG-6369 > Project: Maven > Issue Type: Bug >Reporter: Frank Ch. Eigler >Priority: Major > Fix For: waiting-for-feedback > > > Users with java clients that happen to use https with the "Connection: > keep-alive" header to fetch maven content from the fastly.com cdn of your > repo are experiencing hung connections. > To reproduce, observe hang with: ab -v 2 -H "User-Agent: curl/7.29.0" -c1 > -n1 -k [https://repo.maven.apache.org/maven2/] > Noting that there is no hang if one uses http:// or drops the -k. > Already reported to fastly: > [https://fastly.zendesk.com/hc/en-us/requests/73810] but they don't seem to > take the issue seriously, coming from me. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MENFORCER-306) [REGRESSION] RequirePluginVersions fails
[
https://issues.apache.org/jira/browse/MENFORCER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517218#comment-16517218
]
Tobias Gruetzmacher commented on MENFORCER-306:
---
Well, that pom.xml doesn't contain any versions for those plugins, so this
fails even with enforcer 1.4.1. Did you reduce your minimal test case too much,
because I'm currently tracking down a similar issue... Expanding the example
pom.xml with versions for all those dependencies and THEN using it as a parent,
breaks with M2 but works with M1...
> [REGRESSION] RequirePluginVersions fails
>
>
> Key: MENFORCER-306
> URL: https://issues.apache.org/jira/browse/MENFORCER-306
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-M2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: pom.xml
>
>
> I have found that running the {{RequirePluginVersions}} rule on a project
> with version {{3.0.0-M1}} works fine whereas it fails with version
> {{3.0.0-M2}}.
> {code}
> [DEBUG] Executing rule:
> org.apache.maven.plugins.enforcer.RequirePluginVersions
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = clean
> [DEBUG] plugins = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] plugin = org.apache.maven.plugins:maven-clean-plugin:2.5:clean
> [DEBUG] GAV = [org.apache.maven.plugins, maven-clean-plugin, 2.5, clean]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = install
> [DEBUG] plugins = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] plugin = org.apache.maven.plugins:maven-install-plugin:2.4:install
> [DEBUG] GAV = [org.apache.maven.plugins, maven-install-plugin, 2.4,
> install]
> [DEBUG] lifecycleMapping = deploy
> [DEBUG] plugins = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-deploy-plugin, 2.7, deploy]
> [DEBUG] RequirePluginVersions.getAllPlugins:
> [DEBUG] lifecycleMapping = site
> [DEBUG] plugins = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:site
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, site]
> [DEBUG] lifecycleMapping = site-deploy
> [DEBUG] plugins = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] plugin = org.apache.maven.plugins:maven-site-plugin:3.3:deploy
> [DEBUG] GAV = [org.apache.maven.plugins, maven-site-plugin, 3.3, deploy]
> [DEBUG] All Plugins in use: [Plugin [org.tinyjee.dim:doxia-include-macro],
> Plugin [org.apache.maven.plugins:maven-clean-plugin], Plugin
> [org.apache.maven.plugins:maven-install-plugin], Plugin
> [org.apache.maven.plugins:maven-site-plugin], Plugin
> [org.apache.maven.plugins:maven-deploy-plugin], Plugin
> [org.jacoco:jacoco-maven-plugin], Plugin
> [org.apache.maven.plugins:maven-enforcer-plugin]]
> [DEBUG] plugin org.tinyjee.dim:doxia-include-macro not found
> [DEBUG] plugin org.apache.maven.plugins:maven-clean-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-install-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-site-plugin not found
> [DEBUG] plugin org.apache.maven.plugins:maven-deploy-plugin not found
> [DEBUG] plugin org.jacoco:jacoco-maven-plugin not found
> [DEBUG] Adding failure due to exception
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Some plugins are
> missing valid versions:(LATEST RELEASE SNAPSHOT are not allowed )
> org.tinyjee.dim:doxia-include-macro. The version currently in use is 1.1
> org.apache.maven.plugins:maven-clean-plugin. The version currently in use is
> 3.0.0
> org.apache.maven.plugins:maven-install-plugin.The version currently
> in use is 2.5.2
> org.apache.maven.plugins:maven-site-plugin. The version currently in use is
> 3.6
> org.apache.maven.plugins:maven-deploy-plugin. The version currently
> in use is 2.8.2
> org.jacoco:jacoco-maven-plugin. The version currently in use is 0.8.0
> Always define plugin versions! Never use LATEST or RELEASE.
> at org.apache.maven.plugins.enforcer.RequirePluginVersions.execute
> (RequirePluginVersions.java:320)
> at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:194)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-370) org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517201#comment-16517201
]
Michael Osipov commented on MPIR-370:
-
Not really, this is a transitive dependency via Maven Shared JAR. Codewise from
the plugin I'd do the same did. I likely will do.
> org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
> --
>
> Key: MPIR-370
> URL: https://issues.apache.org/jira/browse/MPIR-370
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.9
> Environment: java -version
> java version "10.0.1" 2018-04-17
> Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
> mvn -v
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T20:49:05+01:00)
> Maven home: C:\Program Files\apache-maven-3.5.3
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jre-10.0.1
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Peter Lamby
>Priority: Minor
>
> When running the Dependiencies report target with java 10 i get the following
> exception:
> {noformat}
> [WARNING] Unable to process class module-info.class in JarAnalyzer File
> C:\Users\plamby\.m2\repository\org\apache\logging\log4j\log4j-api\2.10.0\log4j-api-2.10.0.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
> pool: 19
> at org.apache.bcel.classfile.Constant.readConstant(Constant.java:161)
> at org.apache.bcel.classfile.ConstantPool.(ConstantPool.java:69)
> at
> org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:235)
> at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:143)
> at
> org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:96)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:259)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1542)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:545)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:240)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:201)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 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
>
[jira] [Commented] (MJAVADOC-480) Javadoc generation broken on Java9 if there are references to javax.xml.bind.annontation.XmlElement and building code for java8
[
https://issues.apache.org/jira/browse/MJAVADOC-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517179#comment-16517179
]
Enrico Olivelli commented on MJAVADOC-480:
--
[~rfscholte] we can close this issue
> Javadoc generation broken on Java9 if there are references to
> javax.xml.bind.annontation.XmlElement and building code for java8
> ---
>
> Key: MJAVADOC-480
> URL: https://issues.apache.org/jira/browse/MJAVADOC-480
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Enrico Olivelli
>Priority: Minor
>
> The code uses javax.xml.bind.annotation.XmlElement annotations
> Plugin configuration:
> {code}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.10.4
>
> true
>
>
>
>
> attach-javadocs
>
> jar
>
>
>
>
> {code}
> This is my error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (attach-javadocs) on
> project scripting-api: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 -
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlField.java:22:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlField.java:23:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlRootElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlFieldValue.java:19:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlRootElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlDatabaseSchema.java:21:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/xml/XmlDatabaseSchema.java:22:
> error: package javax.xml.bind.annotation is not visible
> [ERROR] import javax.xml.bind.annotation.XmlRootElement;
> [ERROR] ^
> [ERROR] (package javax.xml.bind.annotation is declared in module
> java.xml.bind, which is not in the module graph)
> [ERROR]
> /home/diennea.lan/enrico.olivelli/dev/magnews/scripting/src/main/java/scripting/mock/MockContactsDB.java:27:
> error: package javax.xml.bind is not visible
> [ERROR] import javax.xml.bind.JAXB;
> [ERROR] ^
> [ERROR] (package javax.xml.bind is declared in module java.xml.bind, which is
> not in the module graph)
> [ERROR]
> [ERROR] Command line was:
> /home/diennea.lan/enrico.olivelli/dev/jdk-9/bin/javadoc @options @packages
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> '/home/diennea.lan/enrico.olivelli/dev/magnews/scripting/target/apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6430) UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already loaded in another classloader
[ https://issues.apache.org/jira/browse/MNG-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517168#comment-16517168 ] Michael Osipov commented on MNG-6430: - Please retry with Maven 3.5.3 and most recen Java 8. > UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already > loaded in another classloader > > > Key: MNG-6430 > URL: https://issues.apache.org/jira/browse/MNG-6430 > Project: Maven > Issue Type: Bug > Components: Class Loading >Reporter: Burcu >Priority: Major > Labels: ClassLoader, Classloader, classloader, glass, > unsatisfiedLinkError > Attachments: glassdll.jpg, mvnTest.jpg, plugin.jpg, runAllTest.jpg > > > Although I made the linkte and tried other solutions, I could not resolve the > glass.dll not found error. I'm looking for a solution to this issue that is > long-lasting. I'm using Powermock and TestFx. I have encountered this problem > since I started working with both. I would like to try if you offer a > solution in this regard. Below you will find some images of the fault. > [https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without modifying any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517148#comment-16517148 ] ASF GitHub Bot commented on MENFORCER-142: -- sparsick opened a new pull request #36: [MENFORCER-142:] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36 Introduce an example site with example "check specific rule via cli" This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Specify enforcer rule in command line without modifying any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.0 > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] sparsick opened a new pull request #36: [MENFORCER-142:] documentation - add example for checking rules via cli
sparsick opened a new pull request #36: [MENFORCER-142:] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36 Introduce an example site with example "check specific rule via cli" This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MNG-6430) UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already loaded in another classloader
[ https://issues.apache.org/jira/browse/MNG-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517039#comment-16517039 ] Burcu commented on MNG-6430: maven version 3.3.9 and jdk1.8.0_121 > UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already > loaded in another classloader > > > Key: MNG-6430 > URL: https://issues.apache.org/jira/browse/MNG-6430 > Project: Maven > Issue Type: Bug > Components: Class Loading >Reporter: Burcu >Priority: Major > Labels: ClassLoader, Classloader, classloader, glass, > unsatisfiedLinkError > Attachments: glassdll.jpg, mvnTest.jpg, plugin.jpg, runAllTest.jpg > > > Although I made the linkte and tried other solutions, I could not resolve the > glass.dll not found error. I'm looking for a solution to this issue that is > long-lasting. I'm using Powermock and TestFx. I have encountered this problem > since I started working with both. I would like to try if you offer a > solution in this regard. Below you will find some images of the fault. > [https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6430) UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already loaded in another classloader
[ https://issues.apache.org/jira/browse/MNG-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517025#comment-16517025 ] Michael Osipov commented on MNG-6430: - Can you upload your Maven versin and JDK first?! > UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already > loaded in another classloader > > > Key: MNG-6430 > URL: https://issues.apache.org/jira/browse/MNG-6430 > Project: Maven > Issue Type: Bug > Components: Class Loading >Reporter: Burcu >Priority: Major > Labels: ClassLoader, Classloader, classloader, glass, > unsatisfiedLinkError > Attachments: glassdll.jpg, mvnTest.jpg, plugin.jpg, runAllTest.jpg > > > Although I made the linkte and tried other solutions, I could not resolve the > glass.dll not found error. I'm looking for a solution to this issue that is > long-lasting. I'm using Powermock and TestFx. I have encountered this problem > since I started working with both. I would like to try if you offer a > solution in this regard. Below you will find some images of the fault. > [https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-267) Running maven-pmd-plugin fails on missing HttpServletResponse
[ https://issues.apache.org/jira/browse/MPMD-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517020#comment-16517020 ] Michael Osipov commented on MPMD-267: - Please provide a sample project. > Running maven-pmd-plugin fails on missing HttpServletResponse > - > > Key: MPMD-267 > URL: https://issues.apache.org/jira/browse/MPMD-267 > Project: Maven PMD Plugin > Issue Type: Bug >Affects Versions: 3.10.0 > Environment: Java 8, Windows Server 2012 r2 >Reporter: Vincent Jansen >Priority: Major > > During running the verify phase on our project we get the following error in > one of our modules > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project > blueriq-component-dashboard: Execution pmd of goal > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: A required class > was missing while executing > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd: > javax/servlet/http/HttpServletResponse > [ERROR] - > [ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.10.0 > [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > Could you check why this is? > In maven-PMD-plugin 3.9.0 we did not have this error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6429) Integration Test site publishing requires Java 7 (or javadoc errors ignored)
[
https://issues.apache.org/jira/browse/MNG-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517018#comment-16517018
]
Michael Osipov commented on MNG-6429:
-
This issue persists across the entire codebase.
> Integration Test site publishing requires Java 7 (or javadoc errors ignored)
>
>
> Key: MNG-6429
> URL: https://issues.apache.org/jira/browse/MNG-6429
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.4
>Reporter: Stephen Connolly
>Priority: Critical
> Fix For: 3.5.4
>
>
> {code:java}
> [INFO]
> 7 errors
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Maven Core ITs 2.1-SNAPSHOT SUCCESS [ 38.586
> s]
> [INFO] Maven IT Support ... SUCCESS [ 2.726 s]
> [INFO] Maven IT :: Plugins SUCCESS [ 2.693 s]
> [INFO] Maven IT Plugin :: Active Collection ... FAILURE [ 15.162
> s]
> [INFO] Maven IT Plugin :: Ant-Based ... SKIPPED
> [INFO] Maven IT Plugin :: Artifact SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Dependency A SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Dependency B SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Dependency C SKIPPED
> [INFO] Maven IT Plugin :: Class Loader SKIPPED
> [INFO] Maven IT Plugin :: Class Loader :: Aggregator .. SKIPPED
> [INFO] Maven IT Plugin :: Configuration ... SKIPPED
> [INFO] Maven IT Plugin :: Context Passing . SKIPPED
> [INFO] Maven ITs :: Core Plugin Stubs . SKIPPED
> [INFO] Maven IT Clean Plugin Stub 0.1-stub-SNAPSHOT ... SKIPPED
> [INFO] Maven IT Compiler Plugin Stub 0.1-stub-SNAPSHOT SKIPPED
> [INFO] Maven IT Deploy Plugin Stub 0.1-stub-SNAPSHOT .. SKIPPED
> [INFO] Maven IT EAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT EJB Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Install Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT JAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Javadoc Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Plugin Plugin Stub 0.1-stub-SNAPSHOT .. SKIPPED
> [INFO] Maven IT RAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Resources Plugin Stub 0.1-stub-SNAPSHOT ... SKIPPED
> [INFO] Maven IT Site Plugin Stub 0.1-stub-SNAPSHOT SKIPPED
> [INFO] Maven IT Source Plugin Stub 0.1-stub-SNAPSHOT .. SKIPPED
> [INFO] Maven IT Surefire Plugin Stub 0.1-stub-SNAPSHOT SKIPPED
> [INFO] Maven IT WAR Plugin Stub 0.1-stub-SNAPSHOT . SKIPPED
> [INFO] Maven IT Plugin :: Dependency Collection ... SKIPPED
> [INFO] Maven IT Plugin :: Dependency Resolution ... SKIPPED
> [INFO] Maven IT Plugin :: Expression .. SKIPPED
> [INFO] Maven IT Plugin :: Error Mojos . SKIPPED
> [INFO] Maven IT Component . SKIPPED
> [INFO] Maven IT Plugin :: Extension Consumer .. SKIPPED
> [INFO] Maven IT Plugin :: Extension Provider .. SKIPPED
> [INFO] Maven IT Plugin :: Fork SKIPPED
> [INFO] Maven IT Plugin :: Invalid Descriptor .. SKIPPED
> [INFO] Maven IT Plugin :: Log File SKIPPED
> [INFO] Maven IT Helper Library SKIPPED
> [INFO] Maven IT Plugin :: Model Interpolation . SKIPPED
> [INFO] Maven IT Plugin :: No Default Component SKIPPED
> [INFO] Maven IT Plugin :: No Project .. SKIPPED
> [INFO] Maven IT Plugin :: Online .. SKIPPED
> [INFO] Maven IT Plugin :: Optional Mojos .. SKIPPED
> [INFO] Maven IT Plugin :: Packaging ... SKIPPED
> [INFO] Maven IT Plugin :: Parameter Implementation SKIPPED
> [INFO] Maven IT Plugin :: Plugin Dependency ... SKIPPED
> [INFO] Maven IT Plugin :: Project . SKIPPED
> [INFO] Maven IT Plugin :: Project Interpolation ... SKIPPED
> [INFO] Maven IT Plugin :: Setter .. SKIPPED
> [INFO] Maven IT Plugin :: Singleton Component . SKIPPED
> [INFO] Maven IT Plugin :: Site SKIPPED
> [INFO] Maven IT Plugin :: Toolchain ... SKIPPED
> [INFO] Maven IT Plugin :: Touch ... SKIPPED
> [INFO] Maven IT Plugin :: Uses Properties Plugin .. SKIPPED
> [INFO] Maven IT Plugin :: Uses Wagon Plugin ... SKIPPED
> [INFO] Maven IT Plugin :: This plugin should contain the mojos
[jira] [Commented] (MPIR-370) org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517013#comment-16517013
]
Peter Lamby commented on MPIR-370:
--
Thank you [~michael-o],
that Workaround is working for me:
{code:java}
maven-project-info-reports-plugin
2.9
org.apache.maven.shared
maven-shared-jar
1.2
com.google.code.findbugs
bcel-findbugs
org.apache.bcel
bcel
6.2
{code}
But it feels pretty akward. Can this be fixed in the plugin iteself?
> org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
> --
>
> Key: MPIR-370
> URL: https://issues.apache.org/jira/browse/MPIR-370
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.9
> Environment: java -version
> java version "10.0.1" 2018-04-17
> Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
> mvn -v
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T20:49:05+01:00)
> Maven home: C:\Program Files\apache-maven-3.5.3
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jre-10.0.1
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Peter Lamby
>Priority: Minor
>
> When running the Dependiencies report target with java 10 i get the following
> exception:
> {noformat}
> [WARNING] Unable to process class module-info.class in JarAnalyzer File
> C:\Users\plamby\.m2\repository\org\apache\logging\log4j\log4j-api\2.10.0\log4j-api-2.10.0.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
> pool: 19
> at org.apache.bcel.classfile.Constant.readConstant(Constant.java:161)
> at org.apache.bcel.classfile.ConstantPool.(ConstantPool.java:69)
> at
> org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:235)
> at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:143)
> at
> org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:96)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:259)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1542)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:545)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:240)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:201)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 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
[jira] [Updated] (MNG-6430) UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already loaded in another classloader
[ https://issues.apache.org/jira/browse/MNG-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burcu updated MNG-6430: --- Labels: ClassLoader Classloader classloader glass unsatisfiedLinkError (was: ) > UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already > loaded in another classloader > > > Key: MNG-6430 > URL: https://issues.apache.org/jira/browse/MNG-6430 > Project: Maven > Issue Type: Bug > Components: Class Loading >Reporter: Burcu >Priority: Major > Labels: ClassLoader, Classloader, classloader, glass, > unsatisfiedLinkError > Attachments: glassdll.jpg, mvnTest.jpg, plugin.jpg, runAllTest.jpg > > > Although I made the linkte and tried other solutions, I could not resolve the > glass.dll not found error. I'm looking for a solution to this issue that is > long-lasting. I'm using Powermock and TestFx. I have encountered this problem > since I started working with both. I would like to try if you offer a > solution in this regard. Below you will find some images of the fault. > [https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAR-253) Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.
[ https://issues.apache.org/jira/browse/MJAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516989#comment-16516989 ] Karl Heinz Marbaise commented on MJAR-253: -- Can you please create an example project which shows the use case? > Since 3.0.0 builds fail with You have to use a classifier to attach > supplemental artifacts to the project instead of replacing them. > > > Key: MJAR-253 > URL: https://issues.apache.org/jira/browse/MJAR-253 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0 >Reporter: J.Cranendonk >Priority: Minor > > See also: > [https://stackoverflow.com/questions/40964500/maven-jar-plugin-3-0-2-error-you-have-to-use-a-classifier-to-attach-supplementa] > https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16420958=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16420958 > https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16516772=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16516772 > Builds where multiple jars were created with different names using the > finalName field (for example to create jars to put together in an assembly) > are failing since version 3.0.0 of the plugin. > Apparently cause they now require a classifier field to be set: > You have to use a classifier to attach supplemental artifacts to the project > instead of replacing them. > The problem with fixing this by setting a classifier is that it gets added > after the finalName field, including a dash, which means the final jar has > the wrong name. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-475) Replace parameter additionalparam with additionalOptions
[
https://issues.apache.org/jira/browse/MJAVADOC-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516951#comment-16516951
]
Jörg Sesterhenn commented on MJAVADOC-475:
--
The documentation still uses the old additionalparams:
[https://maven.apache.org/plugins/maven-javadoc-plugin/examples/alternate-doclet.html]
This is not supposed to work anymore, or is it?
> Replace parameter additionalparam with additionalOptions
>
>
> Key: MJAVADOC-475
> URL: https://issues.apache.org/jira/browse/MJAVADOC-475
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0
>
>
> Introduce an {{additionalOptions}} parameter which allows to pass multiple
> arbitrary parameters to the {{javadoc}} process without the shortcomings of
> MJAVADOC-368.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6430) UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already loaded in another classloader
[ https://issues.apache.org/jira/browse/MNG-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burcu updated MNG-6430: --- Issue Type: Bug (was: Wish) > UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already > loaded in another classloader > > > Key: MNG-6430 > URL: https://issues.apache.org/jira/browse/MNG-6430 > Project: Maven > Issue Type: Bug > Components: Class Loading >Reporter: Burcu >Priority: Major > Attachments: glassdll.jpg, mvnTest.jpg, plugin.jpg, runAllTest.jpg > > > Although I made the linkte and tried other solutions, I could not resolve the > glass.dll not found error. I'm looking for a solution to this issue that is > long-lasting. I'm using Powermock and TestFx. I have encountered this problem > since I started working with both. I would like to try if you offer a > solution in this regard. Below you will find some images of the fault. > [https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-370) org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516930#comment-16516930
]
Michael Osipov commented on MPIR-370:
-
Exclude it from the plugin dep list and add the original ASM manually.
> org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
> --
>
> Key: MPIR-370
> URL: https://issues.apache.org/jira/browse/MPIR-370
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.9
> Environment: java -version
> java version "10.0.1" 2018-04-17
> Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
> mvn -v
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T20:49:05+01:00)
> Maven home: C:\Program Files\apache-maven-3.5.3
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jre-10.0.1
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Peter Lamby
>Priority: Minor
>
> When running the Dependiencies report target with java 10 i get the following
> exception:
> {noformat}
> [WARNING] Unable to process class module-info.class in JarAnalyzer File
> C:\Users\plamby\.m2\repository\org\apache\logging\log4j\log4j-api\2.10.0\log4j-api-2.10.0.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
> pool: 19
> at org.apache.bcel.classfile.Constant.readConstant(Constant.java:161)
> at org.apache.bcel.classfile.ConstantPool.(ConstantPool.java:69)
> at
> org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:235)
> at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:143)
> at
> org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:96)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:259)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1542)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:545)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:240)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:201)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 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
[jira] [Created] (MNG-6430) UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already loaded in another classloader
Burcu created MNG-6430: -- Summary: UnsatisfiedLinkError:Native Library jdk1.8.0_121\jre\bin\glass.dll already loaded in another classloader Key: MNG-6430 URL: https://issues.apache.org/jira/browse/MNG-6430 Project: Maven Issue Type: Wish Components: Class Loading Reporter: Burcu Attachments: glassdll.jpg, mvnTest.jpg, plugin.jpg, runAllTest.jpg Although I made the linkte and tried other solutions, I could not resolve the glass.dll not found error. I'm looking for a solution to this issue that is long-lasting. I'm using Powermock and TestFx. I have encountered this problem since I started working with both. I would like to try if you offer a solution in this regard. Below you will find some images of the fault. [https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MJAR-253) Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.
J.Cranendonk created MJAR-253: - Summary: Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. Key: MJAR-253 URL: https://issues.apache.org/jira/browse/MJAR-253 Project: Maven JAR Plugin Issue Type: Bug Affects Versions: 3.1.0, 3.0.2, 3.0.1, 3.0.0 Reporter: J.Cranendonk See also: [https://stackoverflow.com/questions/40964500/maven-jar-plugin-3-0-2-error-you-have-to-use-a-classifier-to-attach-supplementa] https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16420958=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16420958 https://issues.apache.org/jira/browse/MJAR-198?focusedCommentId=16516772=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16516772 Builds where multiple jars were created with different names using the finalName field (for example to create jars to put together in an assembly) are failing since version 3.0.0 of the plugin. Apparently cause they now require a classifier field to be set: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. The problem with fixing this by setting a classifier is that it gets added after the finalName field, including a dash, which means the final jar has the wrong name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPLUGIN-341) Make the plugin tool modular or at least module-ready
[ https://issues.apache.org/jira/browse/MPLUGIN-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516887#comment-16516887 ] Lukas Eder commented on MPLUGIN-341: Thanks for your explanations. I do understand these constraints. Certainly, going back to a monolithic single "module" isn't the way forward here. I guess this can only be done through a major release... > Make the plugin tool modular or at least module-ready > - > > Key: MPLUGIN-341 > URL: https://issues.apache.org/jira/browse/MPLUGIN-341 > Project: Maven Plugin Tools > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Lukas Eder >Priority: Minor > > When implementing custom maven modules, it is currently not possible to make > those plugins modular on JDK 9+. The reason for this is that there are a lot > of split packages among the various libraries, such as the > org.apache.maven.plugin package between: > * org.apache.maven:maven-core:3.5.3 > * org.apache.maven:maven-plugin-api:3.5.3 > This, and the fact that there are not Automatic-Module-Name entries in the > manifests (see > [http://branchandbound.net/blog/java/2017/12/automatic-module-name/),] means > that no one can currently reasonably create modular maven plugins. > It would be cool if these two things could be fixed in the next minor or > major release -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPMD-267) Running maven-pmd-plugin fails on missing HttpServletResponse
[ https://issues.apache.org/jira/browse/MPMD-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Jansen updated MPMD-267: Description: During running the verify phase on our project we get the following error in one of our modules [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project blueriq-component-dashboard: Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: A required class was missing while executing org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd: javax/servlet/http/HttpServletResponse [ERROR] - [ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.10.0 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy Could you check why this is? In maven-PMD-plugin 3.9.0 we did not have this error. was: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project blueriq-component-dashboard: Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: A required class was missing while executing org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd: javax/servlet/http/HttpServletResponse [ERROR] - [ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.10.0 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > Running maven-pmd-plugin fails on missing HttpServletResponse > - > > Key: MPMD-267 > URL: https://issues.apache.org/jira/browse/MPMD-267 > Project: Maven PMD Plugin > Issue Type: Bug >Affects Versions: 3.10.0 > Environment: Java 8, Windows Server 2012 r2 >Reporter: Vincent Jansen >Priority: Major > > During running the verify phase on our project we get the following error in > one of our modules > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project > blueriq-component-dashboard: Execution pmd of goal > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: A required class > was missing while executing > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd: > javax/servlet/http/HttpServletResponse > [ERROR] - > [ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.10.0 > [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > Could you check why this is? > In maven-PMD-plugin 3.9.0 we did not have this error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-267) Running maven-pmd-plugin fails on missing HttpServletResponse
[ https://issues.apache.org/jira/browse/MPMD-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516853#comment-16516853 ] Vincent Jansen commented on MPMD-267: - Workaround is to add servlet api as dependency on the plugin inside our own pom.xml > Running maven-pmd-plugin fails on missing HttpServletResponse > - > > Key: MPMD-267 > URL: https://issues.apache.org/jira/browse/MPMD-267 > Project: Maven PMD Plugin > Issue Type: Bug >Affects Versions: 3.10.0 > Environment: Java 8, Windows Server 2012 r2 >Reporter: Vincent Jansen >Priority: Major > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project > blueriq-component-dashboard: Execution pmd of goal > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: A required class > was missing while executing > org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd: > javax/servlet/http/HttpServletResponse > [ERROR] - > [ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.10.0 > [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPMD-267) Running maven-pmd-plugin fails on missing HttpServletResponse
Vincent Jansen created MPMD-267: --- Summary: Running maven-pmd-plugin fails on missing HttpServletResponse Key: MPMD-267 URL: https://issues.apache.org/jira/browse/MPMD-267 Project: Maven PMD Plugin Issue Type: Bug Affects Versions: 3.10.0 Environment: Java 8, Windows Server 2012 r2 Reporter: Vincent Jansen [ERROR] Failed to execute goal org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project blueriq-component-dashboard: Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: A required class was missing while executing org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd: javax/servlet/http/HttpServletResponse [ERROR] - [ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.10.0 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MJAR-198) jar:jar without classifier replaces default jar
[ https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516780#comment-16516780 ] Karl Heinz Marbaise edited comment on MJAR-198 at 6/19/18 8:20 AM: --- [~cranphin] Please do not use an closed issue. Please open an new one an make a reference to this...questions regarding the usage etc. must go to users mailing list... was (Author: khmarbaise): [~cranphin] Please do not use an closed issue. Please open an new one an make a reference to this... > jar:jar without classifier replaces default jar > --- > > Key: MJAR-198 > URL: https://issues.apache.org/jira/browse/MJAR-198 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.3.1, 2.3.2, 2.4, 2.5, 2.6 > Environment: Windows 8.1 Pro > JDK 1.8 45 > Maven 3.2.5 >Reporter: Elias Elmqvist Wulcan >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: newbie > Fix For: 3.0.0 > > Attachments: 0.tar, mvn.install.debug.txt > > > If I add an execution of jar:jar in a project of packaging jar and do not > configure a classifier for the additional jar, the additional jar will be > installed instead of the default jar. > Omitting a classifier in the configuration for the goal jar:jar is documented > to have the effect that the jar will not be attached and this is the behavior > that I want. Instead, the jar is attached and replaces the default jar. > AbstractJarMojo.java:254 checks nullness of classifier to decide whether to > attach or not. JarMojo.java:51 declares a default value the empty string for > classifier. Maybe the combination of these lines cause the bug. > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java?revision=1664111=markup > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/JarMojo.java?revision=1664111=markup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAR-198) jar:jar without classifier replaces default jar
[ https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516780#comment-16516780 ] Karl Heinz Marbaise commented on MJAR-198: -- [~cranphin] Please do not use an closed issue. Please open an new one an make a reference to this... > jar:jar without classifier replaces default jar > --- > > Key: MJAR-198 > URL: https://issues.apache.org/jira/browse/MJAR-198 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.3.1, 2.3.2, 2.4, 2.5, 2.6 > Environment: Windows 8.1 Pro > JDK 1.8 45 > Maven 3.2.5 >Reporter: Elias Elmqvist Wulcan >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: newbie > Fix For: 3.0.0 > > Attachments: 0.tar, mvn.install.debug.txt > > > If I add an execution of jar:jar in a project of packaging jar and do not > configure a classifier for the additional jar, the additional jar will be > installed instead of the default jar. > Omitting a classifier in the configuration for the goal jar:jar is documented > to have the effect that the jar will not be attached and this is the behavior > that I want. Instead, the jar is attached and replaces the default jar. > AbstractJarMojo.java:254 checks nullness of classifier to decide whether to > attach or not. JarMojo.java:51 declares a default value the empty string for > classifier. Maybe the combination of these lines cause the bug. > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java?revision=1664111=markup > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/JarMojo.java?revision=1664111=markup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-370) org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516777#comment-16516777
]
Peter Lamby commented on MPIR-370:
--
The only dependency I could find containing bcel was bcel-findbugs. The most
recent version on mvn central is 6.0
https://search.maven.org/#search|ga|1|bcel%2Dfindbugs
> org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
> --
>
> Key: MPIR-370
> URL: https://issues.apache.org/jira/browse/MPIR-370
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.9
> Environment: java -version
> java version "10.0.1" 2018-04-17
> Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
> mvn -v
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T20:49:05+01:00)
> Maven home: C:\Program Files\apache-maven-3.5.3
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jre-10.0.1
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Peter Lamby
>Priority: Minor
>
> When running the Dependiencies report target with java 10 i get the following
> exception:
> {noformat}
> [WARNING] Unable to process class module-info.class in JarAnalyzer File
> C:\Users\plamby\.m2\repository\org\apache\logging\log4j\log4j-api\2.10.0\log4j-api-2.10.0.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
> pool: 19
> at org.apache.bcel.classfile.Constant.readConstant(Constant.java:161)
> at org.apache.bcel.classfile.ConstantPool.(ConstantPool.java:69)
> at
> org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:235)
> at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:143)
> at
> org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:96)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:259)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1542)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:545)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:240)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:201)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 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
>
[jira] [Commented] (MJAR-198) jar:jar without classifier replaces default jar
[ https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516772#comment-16516772 ] J.Cranendonk commented on MJAR-198: --- Was an issue made for the comment Archie Cobbs mentioned? We have the same issue, broken build with multiple jar plugins configurations with different finalName's. I'm whitelisted, so can't reach the user or dev list, and google sends me here regarding this issue. What is the workaround? Adding classifier modifies the final name of the jar, instead of just using finalName, it becomes finalName-classifier.. > jar:jar without classifier replaces default jar > --- > > Key: MJAR-198 > URL: https://issues.apache.org/jira/browse/MJAR-198 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.3.1, 2.3.2, 2.4, 2.5, 2.6 > Environment: Windows 8.1 Pro > JDK 1.8 45 > Maven 3.2.5 >Reporter: Elias Elmqvist Wulcan >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: newbie > Fix For: 3.0.0 > > Attachments: 0.tar, mvn.install.debug.txt > > > If I add an execution of jar:jar in a project of packaging jar and do not > configure a classifier for the additional jar, the additional jar will be > installed instead of the default jar. > Omitting a classifier in the configuration for the goal jar:jar is documented > to have the effect that the jar will not be attached and this is the behavior > that I want. Instead, the jar is attached and replaces the default jar. > AbstractJarMojo.java:254 checks nullness of classifier to decide whether to > attach or not. JarMojo.java:51 declares a default value the empty string for > classifier. Maybe the combination of these lines cause the bug. > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java?revision=1664111=markup > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/JarMojo.java?revision=1664111=markup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
