[jira] [Commented] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath
[ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521317#comment-16521317 ] Dan Tran commented on SUREFIRE-1527: I stepped thru the code, and it seems TestNG provider is picked first ( when no provider specified at surefire plugin) and since TestNG can run junit4, it runs junit4 test and skip junit5 I think we can enhance TestNG TestNgProviderInfo.isApplicable to return false when either testng.jar not found or testng suite(s) is not configured at surefire configuration > Surefire does not discover junit5 test case when testng is in the classpath > --- > > Key: SUREFIRE-1527 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1527 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support, TestNG support >Affects Versions: 2.22.0 >Reporter: Dan Tran >Priority: Major > > My maven module uses junit5 but also has testng in its test classpath and my > surefire does not specify any testng.xml files > Looks like surefire only look for testng test cases -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6261) Relative parent POM resolution failing in 3.5.0 with complex multimodule builds
[
https://issues.apache.org/jira/browse/MNG-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521298#comment-16521298
]
Michael Osipov commented on MNG-6261:
-
The entire file handling needs to be changed for `Path`.
> Relative parent POM resolution failing in 3.5.0 with complex multimodule
> builds
> ---
>
> Key: MNG-6261
> URL: https://issues.apache.org/jira/browse/MNG-6261
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Dawid Weiss
>Priority: Minor
> Attachments: capture-6.png, repro.zip
>
>
> In my effort to upgrade an existing (fairly complex) Maven build to Java
> 1.9.0 I updated Maven to 3.5.0 (from 3.3.9). Unfortunately I get errors when
> the project's modules are resolved:
> {noformat}
> > mvn validate
> [FATAL] Non-resolvable parent POM for
> com.carrotsearch.lingo4g:lingo4g-public-bom:[unknown-version]: Could not find
> artifact com.carrotsearch.lingo4g:lingo4g-public:pom:1.6.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 5, column 11
> ...
> (and many follow).
> {noformat}
> This build has a correct pom parent-structure (a tree), but is fairly complex
> -- the submodule hierarchy is not aligned with parent-child pom hierarchy
> (it's best to look at the repro code to understand how it's structured).
> However, it's been working correctly with all prior Maven versions and I
> wonder if it's a regression bug or maybe underspecified Maven requirement
> (that should be enforced with a warning and not lead to this odd runtime
> message).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6013) Injecting goals into default lifecycle, this is actually possible, but requires hacks
[
https://issues.apache.org/jira/browse/MNG-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521294#comment-16521294
]
Michael Osipov commented on MNG-6013:
-
Please provide a sample project.
> Injecting goals into default lifecycle, this is actually possible, but
> requires hacks
> -
>
> Key: MNG-6013
> URL: https://issues.apache.org/jira/browse/MNG-6013
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9
>Reporter: Mariusz Smykuła
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I have developed plugin, which allows to inject three goals into default
> lifecycle and extend it. I'm not sure if this is undocumented feature or bug,
> but this works and I think this is very useful.
> Plugin: https://github.com/Codearte/accurest-maven-plugin
> Sample project with jar package, without goal defined with extension:true
> https://github.com/mariuszs/gs-rest-service-accurest/blob/master/pom.xml
> My custom components.xml works, but requires hack to work.
> {code}
>
> org.apache.maven.lifecycle.Lifecycle
> org.apache.maven.lifecycle.Lifecycle
> accurest
>
> accurest
>
> accurest-not-used-phase
>
>
>
>
> io.codearte.accurest:accurest-maven-plugin:${project.version}:convert
>
>
>
> io.codearte.accurest:accurest-maven-plugin:${project.version}:generateTests
>
>
>
> io.codearte.accurest:accurest-maven-plugin:${project.version}:generateStubs
>
>
>
>
> {code}
> I need to define fake phase to make this working:
> accurest-not-used-phase
> WIthout this ugly hacks, error occurs in sample project.
> Error:
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.DefaultLifecycles.getPhaseToLifecycleMap(DefaultLifecycles.java:94)
> at
> org.apache.maven.lifecycle.DefaultLifecycles.get(DefaultLifecycles.java:71)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings(DefaultLifecycleExecutionPlanCalculator.java:242)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:217)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:127)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:145)
> at
> org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan(BuilderCommon.java:96)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:109)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
[jira] [Commented] (MNG-6015) Settings.xml server configuration not inyected to wagon extension
[
https://issues.apache.org/jira/browse/MNG-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521293#comment-16521293
]
Michael Osipov commented on MNG-6015:
-
Is this one still valid? Can you provide a complete sample project?
> Settings.xml server configuration not inyected to wagon extension
> -
>
> Key: MNG-6015
> URL: https://issues.apache.org/jira/browse/MNG-6015
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.3
>Reporter: Rubén Suárez Alvarez
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I'm trying to pass configuration settings from _settings.xml_ to wagon
> extensions for _wagon-maven-plugin_.
> _Configuration_ properties from _server_ tag seems not to be passed anymore
> (I think those where passed on maven 2.x).
> I tried with _wagon-ssh_ and _wagon-ssh-external_ extensions.
> With _wagon-ssh_:
> {code:xml|title=settings.xml|borderStyle=solid}
>
> ssh-server
> sshuser
> sshpassword
>
>
> implementation="org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostProvider">
> no
>
>
>
> {code}
> {code:xml|title=pom.xml|borderStyle=solid}
>
>
>
> org.apache.maven.wagon
> wagon-ssh
> 2.10
>
>
> ...
>
>
> org.codehaus.mojo
> wagon-maven-plugin
> 1.0
>
>
> upload-javadoc
> install
>
> upload
>
>
> ${basedir}/target
>
> ${project.artifactId}*
>
> pom.xml
> scp://192.168.3.174
> /opt/doc
> ssh-server
>
>
>
>
>
>
> {code}
> *knownHostsProvider* is not passed to _wagon-ssh_. It's always *null*.
> With _wagon-ssh-external_:
> {code:xml|title=settings.xml|borderStyle=solid}
>
> ssh-server
> sshuser
> sshpassword
>
> -o 'StrictHostKeyChecking=no' -o
> 'UserKnownHostsFile=/dev/null'
>
>
> {code}
> {code:xml|title=pom.xml|borderStyle=solid}
>
>
>
> org.apache.maven.wagon
> wagon-ssh-external
> 2.10
>
>
> ...
>
>
> org.codehaus.mojo
> wagon-maven-plugin
> 1.0
>
>
> upload-javadoc
> install
>
> upload
>
>
> ${basedir}/target
>
> ${project.artifactId}*
>
> pom.xml
> scpexe://192.168.3.174
> /opt/doc
> ssh-server
>
>
>
>
>
>
> {code}
> *sshArgs* is not passed to _wagon-ssh-external_. It's always *null*.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6013) Injecting goals into default lifecycle, this is actually possible, but requires hacks
[
https://issues.apache.org/jira/browse/MNG-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6013:
Fix Version/s: waiting-for-feedback
> Injecting goals into default lifecycle, this is actually possible, but
> requires hacks
> -
>
> Key: MNG-6013
> URL: https://issues.apache.org/jira/browse/MNG-6013
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9
>Reporter: Mariusz Smykuła
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I have developed plugin, which allows to inject three goals into default
> lifecycle and extend it. I'm not sure if this is undocumented feature or bug,
> but this works and I think this is very useful.
> Plugin: https://github.com/Codearte/accurest-maven-plugin
> Sample project with jar package, without goal defined with extension:true
> https://github.com/mariuszs/gs-rest-service-accurest/blob/master/pom.xml
> My custom components.xml works, but requires hack to work.
> {code}
>
> org.apache.maven.lifecycle.Lifecycle
> org.apache.maven.lifecycle.Lifecycle
> accurest
>
> accurest
>
> accurest-not-used-phase
>
>
>
>
> io.codearte.accurest:accurest-maven-plugin:${project.version}:convert
>
>
>
> io.codearte.accurest:accurest-maven-plugin:${project.version}:generateTests
>
>
>
> io.codearte.accurest:accurest-maven-plugin:${project.version}:generateStubs
>
>
>
>
> {code}
> I need to define fake phase to make this working:
> accurest-not-used-phase
> WIthout this ugly hacks, error occurs in sample project.
> Error:
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.DefaultLifecycles.getPhaseToLifecycleMap(DefaultLifecycles.java:94)
> at
> org.apache.maven.lifecycle.DefaultLifecycles.get(DefaultLifecycles.java:71)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings(DefaultLifecycleExecutionPlanCalculator.java:242)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:217)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:127)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:145)
> at
> org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan(BuilderCommon.java:96)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:109)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Updated] (MNG-6015) Settings.xml server configuration not inyected to wagon extension
[
https://issues.apache.org/jira/browse/MNG-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6015:
Fix Version/s: waiting-for-feedback
> Settings.xml server configuration not inyected to wagon extension
> -
>
> Key: MNG-6015
> URL: https://issues.apache.org/jira/browse/MNG-6015
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.3
>Reporter: Rubén Suárez Alvarez
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I'm trying to pass configuration settings from _settings.xml_ to wagon
> extensions for _wagon-maven-plugin_.
> _Configuration_ properties from _server_ tag seems not to be passed anymore
> (I think those where passed on maven 2.x).
> I tried with _wagon-ssh_ and _wagon-ssh-external_ extensions.
> With _wagon-ssh_:
> {code:xml|title=settings.xml|borderStyle=solid}
>
> ssh-server
> sshuser
> sshpassword
>
>
> implementation="org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostProvider">
> no
>
>
>
> {code}
> {code:xml|title=pom.xml|borderStyle=solid}
>
>
>
> org.apache.maven.wagon
> wagon-ssh
> 2.10
>
>
> ...
>
>
> org.codehaus.mojo
> wagon-maven-plugin
> 1.0
>
>
> upload-javadoc
> install
>
> upload
>
>
> ${basedir}/target
>
> ${project.artifactId}*
>
> pom.xml
> scp://192.168.3.174
> /opt/doc
> ssh-server
>
>
>
>
>
>
> {code}
> *knownHostsProvider* is not passed to _wagon-ssh_. It's always *null*.
> With _wagon-ssh-external_:
> {code:xml|title=settings.xml|borderStyle=solid}
>
> ssh-server
> sshuser
> sshpassword
>
> -o 'StrictHostKeyChecking=no' -o
> 'UserKnownHostsFile=/dev/null'
>
>
> {code}
> {code:xml|title=pom.xml|borderStyle=solid}
>
>
>
> org.apache.maven.wagon
> wagon-ssh-external
> 2.10
>
>
> ...
>
>
> org.codehaus.mojo
> wagon-maven-plugin
> 1.0
>
>
> upload-javadoc
> install
>
> upload
>
>
> ${basedir}/target
>
> ${project.artifactId}*
>
> pom.xml
> scpexe://192.168.3.174
> /opt/doc
> ssh-server
>
>
>
>
>
>
> {code}
> *sshArgs* is not passed to _wagon-ssh-external_. It's always *null*.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-5861) Documentation lacks support of Enum-types in mojo parameters
[ https://issues.apache.org/jira/browse/MNG-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521287#comment-16521287 ] Michael Osipov commented on MNG-5861: - Enums are supported, see the Enum section here: http://maven.apache.org/guides/plugin/guide-java-plugin-development.html > Documentation lacks support of Enum-types in mojo parameters > > > Key: MNG-5861 > URL: https://issues.apache.org/jira/browse/MNG-5861 > Project: Maven > Issue Type: Bug > Components: Documentation: Guides >Reporter: S L >Priority: Trivial > Fix For: waiting-for-feedback > > Attachments: enum-maven-plugin.zip > > > Since it appears that Maven support Enum-type parameters in mojos (MNG-4292) > I couldn't find anything related to that topic in the documentation > (https://maven.apache.org/guides/mini/guide-configuring-plugins.html). > Maybe it's due to the lack of docu however setting the default-value inside > the paramter will also cause a null-pointer exception -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-5861) Documentation lacks support of Enum-types in mojo parameters
[ https://issues.apache.org/jira/browse/MNG-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5861: Fix Version/s: waiting-for-feedback > Documentation lacks support of Enum-types in mojo parameters > > > Key: MNG-5861 > URL: https://issues.apache.org/jira/browse/MNG-5861 > Project: Maven > Issue Type: Bug > Components: Documentation: Guides >Reporter: S L >Priority: Trivial > Fix For: waiting-for-feedback > > Attachments: enum-maven-plugin.zip > > > Since it appears that Maven support Enum-type parameters in mojos (MNG-4292) > I couldn't find anything related to that topic in the documentation > (https://maven.apache.org/guides/mini/guide-configuring-plugins.html). > Maybe it's due to the lack of docu however setting the default-value inside > the paramter will also cause a null-pointer exception -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-336) API changes report for Maven Core (including snapshot)
[ https://issues.apache.org/jira/browse/MNGSITE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521286#comment-16521286 ] Michael Osipov commented on MNGSITE-336: I like this, I'd like to integrate this into the Maven site through a link. What would you recommend and where? > API changes report for Maven Core (including snapshot) > -- > > Key: MNGSITE-336 > URL: https://issues.apache.org/jira/browse/MNGSITE-336 > Project: Maven Project Web Site > Issue Type: New Feature >Reporter: Andrey Ponomarenko >Priority: Major > Attachments: maven-core-1.png, maven-core-2.png > > > Hi, > I'd like to share report on API changes and backward compatibility for the > Maven Core library: > https://abi-laboratory.pro/java/tracker/timeline/maven-core/ > BC — binary compatibility > SC — source compatibility > The analysis result for the latest snapshot of the library (from > https://repository.apache.org/content/repositories/snapshots/org/apache/maven/maven-core/) > is included to the report. > The report is generated according to the article > https://wiki.eclipse.org/Evolving_Java-based_APIs_2 by the > https://github.com/lvc/japi-tracker tool. > RSS: https://abi-laboratory.pro/java/tracker/rss/maven-core/feed.rss > Hope it will be helpful for users and maintainers of the library. > Please feel free to request any other Maven modules to be included to the > tracker if you are interested. > Thank you. > !maven-core-1.png|API changes review! > !maven-core-2.png|API symbols timeline! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Moved] (MNGSITE-336) API changes report for Maven Core (including snapshot)
[ https://issues.apache.org/jira/browse/MNGSITE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov moved MNG-6301 to MNGSITE-336: - Issue Type: New Feature (was: Test) Key: MNGSITE-336 (was: MNG-6301) Project: Maven Project Web Site (was: Maven) > API changes report for Maven Core (including snapshot) > -- > > Key: MNGSITE-336 > URL: https://issues.apache.org/jira/browse/MNGSITE-336 > Project: Maven Project Web Site > Issue Type: New Feature >Reporter: Andrey Ponomarenko >Priority: Major > Attachments: maven-core-1.png, maven-core-2.png > > > Hi, > I'd like to share report on API changes and backward compatibility for the > Maven Core library: > https://abi-laboratory.pro/java/tracker/timeline/maven-core/ > BC — binary compatibility > SC — source compatibility > The analysis result for the latest snapshot of the library (from > https://repository.apache.org/content/repositories/snapshots/org/apache/maven/maven-core/) > is included to the report. > The report is generated according to the article > https://wiki.eclipse.org/Evolving_Java-based_APIs_2 by the > https://github.com/lvc/japi-tracker tool. > RSS: https://abi-laboratory.pro/java/tracker/rss/maven-core/feed.rss > Hope it will be helpful for users and maintainers of the library. > Please feel free to request any other Maven modules to be included to the > tracker if you are interested. > Thank you. > !maven-core-1.png|API changes review! > !maven-core-2.png|API symbols timeline! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5641) AbstractMavenLifecycleParticipant#afterSessionStart is never invoked
[
https://issues.apache.org/jira/browse/MNG-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521284#comment-16521284
]
Michael Osipov commented on MNG-5641:
-
Is this one still valid?
> AbstractMavenLifecycleParticipant#afterSessionStart is never invoked
>
>
> Key: MNG-5641
> URL: https://issues.apache.org/jira/browse/MNG-5641
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Reporter: Cservenak, Tamas
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Seems this affects all released maven versions.
> The problem, is that
> {{org.apache.maven.DefaultMaven#getLifecycleParticipants}} is invoked with
> empty list, as there are no projects read up yet.
> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/DefaultMaven.java#L233
> Moreover, there is a comment on class, suggesting to remove this method. So,
> maybe just remove it?
> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/AbstractMavenLifecycleParticipant.java#L56
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-5641) AbstractMavenLifecycleParticipant#afterSessionStart is never invoked
[
https://issues.apache.org/jira/browse/MNG-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5641:
Fix Version/s: waiting-for-feedback
> AbstractMavenLifecycleParticipant#afterSessionStart is never invoked
>
>
> Key: MNG-5641
> URL: https://issues.apache.org/jira/browse/MNG-5641
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Reporter: Cservenak, Tamas
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Seems this affects all released maven versions.
> The problem, is that
> {{org.apache.maven.DefaultMaven#getLifecycleParticipants}} is invoked with
> empty list, as there are no projects read up yet.
> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/DefaultMaven.java#L233
> Moreover, there is a comment on class, suggesting to remove this method. So,
> maybe just remove it?
> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/AbstractMavenLifecycleParticipant.java#L56
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6130) Loss of profile information in workaround for MNG-4900
[
https://issues.apache.org/jira/browse/MNG-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521277#comment-16521277
]
Michael Osipov commented on MNG-6130:
-
[~boris_brodski], do you think you can provide an IT for that? Would be awesome.
> Loss of profile information in workaround for MNG-4900
> --
>
> Key: MNG-6130
> URL: https://issues.apache.org/jira/browse/MNG-6130
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9, 3.5.0
> Environment: Windows
>Reporter: Boris Brodski
>Priority: Major
> Labels: easyfix, patch
> Fix For: waiting-for-feedback
>
> Attachments: MNG-6130.patch
>
>
> Please, forgive me not providing example project reproducing the bug.
> It's very tricky and hopefully not necessary, since the 1-line fix is
> provided.
> Using profiles together with maven-javadoc-plugin results in the following
> problem:
> - Configuration from active profiles is not considered during dependency
> resolution started problematically from the maven-javadoc-plugin.
> This leads to unpredictable behavior, that is somewhat hard to reproduce.
> Here is the technical inside and the 1-line fix:
> In the DefaultMavenProjectBuilder.toRequest():
> {noformat}
> if ( profileManager != null ) {
>...
> } else {
> ...
> /*
>* MNG-4900: Hack to workaround deficiency of legacy API which makes it
> impossible for plugins to access the
>* global profile manager which is required to build a POM like a CLI
> invocation does. Failure to consider
>* the activated profiles can cause repo declarations to be lost which in
> turn will result in artifact
>* resolution failures, in particular when using the enhanced local repo
> which guards access to local files
>* based on the configured remote repos.
>*/
> request.setActiveProfileIds( req.getActiveProfiles() );
> request.setInactiveProfileIds( req.getInactiveProfiles() );
> }
> {noformat}
> Here we copy active and inactive profile ids, but we don't copy the list of
> all profile ids. Missing line:
> {noformat}
> request.setProfiles( req.getProfiles() );
> {noformat}
> As the result the method DefaultProfileManager.getActiveProfiles() always
> returns an empty list:
> {noformat}
> List activeProfiles = new ArrayList<>( profiles.size() );
> for ( Profile profile : profiles ) {
> ...
> }
> return activeProfiles;
> {noformat}
> "profiles" here is empty, since it wasn't copied together with
> "getActiveProfiles()" and "getInactiveProfiles()"
> Adding the missing line fixes the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6130) Loss of profile information in workaround for MNG-4900
[
https://issues.apache.org/jira/browse/MNG-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6130:
Fix Version/s: waiting-for-feedback
> Loss of profile information in workaround for MNG-4900
> --
>
> Key: MNG-6130
> URL: https://issues.apache.org/jira/browse/MNG-6130
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9, 3.5.0
> Environment: Windows
>Reporter: Boris Brodski
>Priority: Major
> Labels: easyfix, patch
> Fix For: waiting-for-feedback
>
> Attachments: MNG-6130.patch
>
>
> Please, forgive me not providing example project reproducing the bug.
> It's very tricky and hopefully not necessary, since the 1-line fix is
> provided.
> Using profiles together with maven-javadoc-plugin results in the following
> problem:
> - Configuration from active profiles is not considered during dependency
> resolution started problematically from the maven-javadoc-plugin.
> This leads to unpredictable behavior, that is somewhat hard to reproduce.
> Here is the technical inside and the 1-line fix:
> In the DefaultMavenProjectBuilder.toRequest():
> {noformat}
> if ( profileManager != null ) {
>...
> } else {
> ...
> /*
>* MNG-4900: Hack to workaround deficiency of legacy API which makes it
> impossible for plugins to access the
>* global profile manager which is required to build a POM like a CLI
> invocation does. Failure to consider
>* the activated profiles can cause repo declarations to be lost which in
> turn will result in artifact
>* resolution failures, in particular when using the enhanced local repo
> which guards access to local files
>* based on the configured remote repos.
>*/
> request.setActiveProfileIds( req.getActiveProfiles() );
> request.setInactiveProfileIds( req.getInactiveProfiles() );
> }
> {noformat}
> Here we copy active and inactive profile ids, but we don't copy the list of
> all profile ids. Missing line:
> {noformat}
> request.setProfiles( req.getProfiles() );
> {noformat}
> As the result the method DefaultProfileManager.getActiveProfiles() always
> returns an empty list:
> {noformat}
> List activeProfiles = new ArrayList<>( profiles.size() );
> for ( Profile profile : profiles ) {
> ...
> }
> return activeProfiles;
> {noformat}
> "profiles" here is empty, since it wasn't copied together with
> "getActiveProfiles()" and "getInactiveProfiles()"
> Adding the missing line fixes the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-368) Upgrade to Java 7
[ https://issues.apache.org/jira/browse/MPIR-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521247#comment-16521247 ] Hudson commented on MPIR-368: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #22 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/22/ > Upgrade to Java 7 > - > > Key: MPIR-368 > URL: https://issues.apache.org/jira/browse/MPIR-368 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-372) Remove fields duplicating parent class members
[ https://issues.apache.org/jira/browse/MPIR-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521246#comment-16521246 ] Hudson commented on MPIR-372: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #22 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/22/ > Remove fields duplicating parent class members > -- > > Key: MPIR-372 > URL: https://issues.apache.org/jira/browse/MPIR-372 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Sylwester Lachiewicz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > > There are several fields which duplicate the same fields available in the > parent class -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MPIR-368) Upgrade to Java 7
[ https://issues.apache.org/jira/browse/MPIR-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458658#comment-16458658 ] Michael Osipov edited comment on MPIR-368 at 6/23/18 8:15 PM: -- Fixed with [c10048d12e28932294cf7cb7f8ce065b4d624182|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=c10048d12e28932294cf7cb7f8ce065b4d624182] and [26e65d36437040bed6a7e9a655c3857bec0a8842|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=26e65d36437040bed6a7e9a655c3857bec0a8842]. was (Author: michael-o): Fixed with [c10048d12e28932294cf7cb7f8ce065b4d624182|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=c10048d12e28932294cf7cb7f8ce065b4d624182]. > Upgrade to Java 7 > - > > Key: MPIR-368 > URL: https://issues.apache.org/jira/browse/MPIR-368 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] asfgit closed pull request #5: Java 7 code update and IDE hints fixed
asfgit closed pull request #5: Java 7 code update and IDE hints fixed
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/5
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/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
b/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
index 1243341..edccfa8 100644
---
a/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
+++
b/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
@@ -90,12 +90,6 @@
@Component
protected SiteTool siteTool;
-/**
- * Doxia Site Renderer component.
- */
-@Component
-protected Renderer siteRenderer;
-
/**
* Artifact Resolver component.
*/
@@ -120,21 +114,7 @@
// --
// Mojo parameters
// --
-
-/**
- * The output directory for the report. Note that this parameter is only
evaluated if the goal is run directly from
- * the command line. If the goal is run indirectly as part of a site
generation, the output directory configured in
- * the Maven Site Plugin is used instead.
- */
-@Parameter( property = "project.reporting.outputDirectory", required =
true )
-protected File outputDirectory;
-
-/**
- * The Maven Project.
- */
-@Parameter( defaultValue = "${project}", readonly = true, required = true )
-protected MavenProject project;
-
+
@Parameter( defaultValue = "${session}", readonly = true, required = true )
private MavenSession session;
@@ -222,7 +202,7 @@ public void execute()
DecorationModel model = new DecorationModel();
model.setBody( new Body() );
-Map attributes = new HashMap();
+Map attributes = new HashMap<>();
attributes.put( "outputEncoding", "UTF-8" );
attributes.put( "project", project );
@@ -233,7 +213,8 @@ public void execute()
SiteRenderingContext siteContext =
siteRenderer.createContextForSkin( defaultSkin, attributes,
model, getName( locale ), locale );
-RenderingContext context = new RenderingContext( outputDirectory,
filename, null );
+RenderingContext context = new RenderingContext(
+outputDirectory, null, filename, null, null, false, null );
SiteRendererSink sink = new SiteRendererSink( context );
@@ -250,22 +231,7 @@ public void execute()
writer.close();
writer = null;
}
-catch ( RendererException e )
-{
-throw new MojoExecutionException( "An error has occurred in " +
getName( Locale.ENGLISH )
-+ " report generation.", e );
-}
-catch ( IOException e )
-{
-throw new MojoExecutionException( "An error has occurred in " +
getName( Locale.ENGLISH )
-+ " report generation.", e );
-}
-catch ( SiteToolException e )
-{
-throw new MojoExecutionException( "An error has occurred in " +
getName( Locale.ENGLISH )
-+ " report generation.", e );
-}
-catch ( MavenReportException e )
+catch ( RendererException | IOException | SiteToolException |
MavenReportException e )
{
throw new MojoExecutionException( "An error has occurred in " +
getName( Locale.ENGLISH )
+ " report generation.", e );
@@ -345,12 +311,12 @@ protected Plugin getPlugin( String pluginId )
return null;
}
-Plugin plugin = (Plugin)
getProject().getBuild().getPluginsAsMap().get( pluginId );
+Plugin plugin = getProject().getBuild().getPluginsAsMap().get(
pluginId );
if ( ( plugin == null ) && (
getProject().getBuild().getPluginManagement() != null )
&& (
getProject().getBuild().getPluginManagement().getPluginsAsMap() != null ) )
{
-plugin = (Plugin)
getProject().getBuild().getPluginManagement().getPluginsAsMap().get( pluginId );
+plugin =
getProject().getBuild().getPluginManagement().getPluginsAsMap().get( pluginId );
}
return plugin;
@@ -407,15 +373,12 @@ protected I18N getI18N( Locale locale )
File customBundleFile = new File( customBundle );
if ( customBundleFile.isFile() &&
customBundleFile.getName().endsWith( ".properties" ) )
{
-if ( !i18n.getClass().isAssignableFrom(
[jira] [Closed] (MPIR-372) Remove fields duplicating parent class members
[ https://issues.apache.org/jira/browse/MPIR-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-372. --- Resolution: Fixed Fixed with [ecdd72249300f64331b89bcd11ad3cdd253cf223|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=ecdd72249300f64331b89bcd11ad3cdd253cf223]. > Remove fields duplicating parent class members > -- > > Key: MPIR-372 > URL: https://issues.apache.org/jira/browse/MPIR-372 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Sylwester Lachiewicz >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > > There are several fields which duplicate the same fields available in the > parent class -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPIR-372) Remove fields duplicating parent class members
Michael Osipov created MPIR-372: --- Summary: Remove fields duplicating parent class members Key: MPIR-372 URL: https://issues.apache.org/jira/browse/MPIR-372 Project: Maven Project Info Reports Plugin Issue Type: Task Affects Versions: 2.9 Reporter: Sylwester Lachiewicz Assignee: Michael Osipov Fix For: 3.0.0 There are several fields which duplicate the same fields available in the parent class -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1476) useSystemClassLoader=false doesn't work as expected after 2.8.1
[ https://issues.apache.org/jira/browse/SUREFIRE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521235#comment-16521235 ] Enrico Olivelli edited comment on SUREFIRE-1476 at 6/23/18 7:17 PM: I am looking into this. In current master useSystemClassLoader seems pretty unused. I will check why it disappeared in 2.9, I hope we won't need to introduce some kind of "useIsolatedClassloader" flag. As far as I can see [~ikelly] would like to have IsolatedClassLoader even when using forks > 0. With forks = 0 IsolatedClassLoader is important in order to keep application code "isolated" from Maven classpath, but with forcks > 0 we are in a "forked" JVMwe are adding only the "forked booter" classes to the application, so I still it is not clear to me what we have to protect. I need to go back to the code in BookKeeper when we found this issue was (Author: eolivelli): I am looking into this. In current master useSystemClassLoader seems pretty unused. I will check why it disappeared in 2.9, I hope we won't need to introduce some find of "useIsolatedClassloader" flag. As far as I can see [~ikelly] would like to have IsolatedClassLoader even when using forks > 0. With forks = 0 IsolatedClassLoader is important in order to keep application code "isolated" from Maven classpath, but with forcks > 0 we are in a "forked" JVMwe are adding only the "forked booter" classes to the application, so I still it is not clear to me what we have to protect. I need to go back to the code in BookKeeper when we found this issue > useSystemClassLoader=false doesn't work as expected after 2.8.1 > --- > > Key: SUREFIRE-1476 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1476 > Project: Maven Surefire > Issue Type: Bug >Reporter: Ivan Kelly >Priority: Major > > I have a test case where I want to load a bunch of jars in a custom > classloader, and check that they are isolated from the classes in the > classloader within which the test is running. This is for BC testing > elsewhere in my code. > > See > [https://github.com/ivankelly/bookkeeper/blob/faa9f6db6f6861b9579be441227621bb06f0fac8/tests/integration-tests-utils/pom.xml] > > Run test in that module to see it work correctly. Change the surefire plugin > to a newer version to see it fail. The problem seems to be that all > dependencies are being added to the classpath of the forked processes, so no > matter what happens, they are in the system class loader. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1476) useSystemClassLoader=false doesn't work as expected after 2.8.1
[ https://issues.apache.org/jira/browse/SUREFIRE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521235#comment-16521235 ] Enrico Olivelli commented on SUREFIRE-1476: --- I am looking into this. In current master useSystemClassLoader seems pretty unused. I will check why it disappeared in 2.9, I hope we won't need to introduce some find of "useIsolatedClassloader" flag. As far as I can see [~ikelly] would like to have IsolatedClassLoader even when using forks > 0. With forks = 0 IsolatedClassLoader is important in order to keep application code "isolated" from Maven classpath, but with forcks > 0 we are in a "forked" JVMwe are adding only the "forked booter" classes to the application, so I still it is not clear to me what we have to protect. I need to go back to the code in BookKeeper when we found this issue > useSystemClassLoader=false doesn't work as expected after 2.8.1 > --- > > Key: SUREFIRE-1476 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1476 > Project: Maven Surefire > Issue Type: Bug >Reporter: Ivan Kelly >Priority: Major > > I have a test case where I want to load a bunch of jars in a custom > classloader, and check that they are isolated from the classes in the > classloader within which the test is running. This is for BC testing > elsewhere in my code. > > See > [https://github.com/ivankelly/bookkeeper/blob/faa9f6db6f6861b9579be441227621bb06f0fac8/tests/integration-tests-utils/pom.xml] > > Run test in that module to see it work correctly. Change the surefire plugin > to a newer version to see it fail. The problem seems to be that all > dependencies are being added to the classpath of the forked processes, so no > matter what happens, they are in the system class loader. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPMD-266) Aggregate report in multi-module projects doesn't use correct auxclasspath
[ https://issues.apache.org/jira/browse/MPMD-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-266. --- Resolution: Fixed > Aggregate report in multi-module projects doesn't use correct auxclasspath > -- > > Key: MPMD-266 > URL: https://issues.apache.org/jira/browse/MPMD-266 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 3.9.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.11.0 > > > When generating a site with the pmd report enabled and using > "aggregate=true", then more PMD violations are found than it should be. > > The reason is probably a wrong configured auxclasspath for PMD: In aggregate > mode, PMD is executed once for all modules. The classpath needs to include > all dependencies of all modules, in oder for the typeresolution feature to > work. Currently, only the compile classpath of the parent module is used. > > Relevant code parts: > * Determining the auxclasspath: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L665-L678] > * Determining the source folders: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/AbstractPmdReport.java#L362-L391] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-266) Aggregate report in multi-module projects doesn't use correct auxclasspath
[ https://issues.apache.org/jira/browse/MPMD-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521225#comment-16521225 ] Hudson commented on MPMD-266: - Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » master #39 See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/39/ > Aggregate report in multi-module projects doesn't use correct auxclasspath > -- > > Key: MPMD-266 > URL: https://issues.apache.org/jira/browse/MPMD-266 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 3.9.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.11.0 > > > When generating a site with the pmd report enabled and using > "aggregate=true", then more PMD violations are found than it should be. > > The reason is probably a wrong configured auxclasspath for PMD: In aggregate > mode, PMD is executed once for all modules. The classpath needs to include > all dependencies of all modules, in oder for the typeresolution feature to > work. Currently, only the compile classpath of the parent module is used. > > Relevant code parts: > * Determining the auxclasspath: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L665-L678] > * Determining the source folders: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/AbstractPmdReport.java#L362-L391] > -- 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=16521224#comment-16521224
]
Robert Scholte commented on MNG-6429:
-
Now seeing this is on the integration tests only. Do we really want to publish
this? What's the real benefit of it? Why not drop it?
> 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.6.0-candidate
>
>
> {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
[jira] [Closed] (MPMD-268) Missing warnings about deprecated rules
[
https://issues.apache.org/jira/browse/MPMD-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-268.
---
Resolution: Fixed
> Missing warnings about deprecated rules
> ---
>
> Key: MPMD-268
> URL: https://issues.apache.org/jira/browse/MPMD-268
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.11.0
>
>
> If you use a custom ruleset, which contains deprecated rules, then a warnings
> is expected.
> E.g. referencing this rule
> {noformat}
> {noformat}
> Should give the warning:
> {noformat}
> [WARNING] Use Rule name category/java/design.xml/CollapsibleIfStatements
> instead of the deprecated Rule name
> rulesets/java/basic.xml/CollapsibleIfStatements. PMD 7.0.0 will remove
> support for this deprecated Rule name usage.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPMD-266) Aggregate report in multi-module projects doesn't use correct auxclasspath
[ https://issues.apache.org/jira/browse/MPMD-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-266: Fix Version/s: 3.11.0 > Aggregate report in multi-module projects doesn't use correct auxclasspath > -- > > Key: MPMD-266 > URL: https://issues.apache.org/jira/browse/MPMD-266 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 3.9.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.11.0 > > > When generating a site with the pmd report enabled and using > "aggregate=true", then more PMD violations are found than it should be. > > The reason is probably a wrong configured auxclasspath for PMD: In aggregate > mode, PMD is executed once for all modules. The classpath needs to include > all dependencies of all modules, in oder for the typeresolution feature to > work. Currently, only the compile classpath of the parent module is used. > > Relevant code parts: > * Determining the auxclasspath: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L665-L678] > * Determining the source folders: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/AbstractPmdReport.java#L362-L391] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MPMD-266) Aggregate report in multi-module projects doesn't use correct auxclasspath
[ https://issues.apache.org/jira/browse/MPMD-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel reassigned MPMD-266: --- Assignee: Andreas Dangel > Aggregate report in multi-module projects doesn't use correct auxclasspath > -- > > Key: MPMD-266 > URL: https://issues.apache.org/jira/browse/MPMD-266 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 3.9.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.11.0 > > > When generating a site with the pmd report enabled and using > "aggregate=true", then more PMD violations are found than it should be. > > The reason is probably a wrong configured auxclasspath for PMD: In aggregate > mode, PMD is executed once for all modules. The classpath needs to include > all dependencies of all modules, in oder for the typeresolution feature to > work. Currently, only the compile classpath of the parent module is used. > > Relevant code parts: > * Determining the auxclasspath: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L665-L678] > * Determining the source folders: > [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/AbstractPmdReport.java#L362-L391] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-268) Missing warnings about deprecated rules
[
https://issues.apache.org/jira/browse/MPMD-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521206#comment-16521206
]
Hudson commented on MPMD-268:
-
Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » master #38
See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/38/
> Missing warnings about deprecated rules
> ---
>
> Key: MPMD-268
> URL: https://issues.apache.org/jira/browse/MPMD-268
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.11.0
>
>
> If you use a custom ruleset, which contains deprecated rules, then a warnings
> is expected.
> E.g. referencing this rule
> {noformat}
> {noformat}
> Should give the warning:
> {noformat}
> [WARNING] Use Rule name category/java/design.xml/CollapsibleIfStatements
> instead of the deprecated Rule name
> rulesets/java/basic.xml/CollapsibleIfStatements. PMD 7.0.0 will remove
> support for this deprecated Rule name usage.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MREPOSITORY-44) Upgrade shared verifier
[ https://issues.apache.org/jira/browse/MREPOSITORY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MREPOSITORY-44. -- Resolution: Done Done in [cc622431e08763c77a71929b9e898bf39156e63d|https://gitbox.apache.org/repos/asf?p=maven-repository-plugin.git;a=commitdiff;h=cc622431e08763c77a71929b9e898bf39156e63d] > Upgrade shared verifier > > > Key: MREPOSITORY-44 > URL: https://issues.apache.org/jira/browse/MREPOSITORY-44 > Project: Maven Repository Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MREPOSITORY-44) Upgrade shared verifier
[ https://issues.apache.org/jira/browse/MREPOSITORY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521186#comment-16521186 ] Hudson commented on MREPOSITORY-44: --- Build succeeded in Jenkins: Maven TLP » maven-repository-plugin » master #7 See https://builds.apache.org/job/maven-box/job/maven-repository-plugin/job/master/7/ > Upgrade shared verifier > > > Key: MREPOSITORY-44 > URL: https://issues.apache.org/jira/browse/MREPOSITORY-44 > Project: Maven Repository Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Deleted] (MVERIFIER-29) Upgrade verifier to 1.6
[ https://issues.apache.org/jira/browse/MVERIFIER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise deleted MVERIFIER-29: - > Upgrade verifier to 1.6 > --- > > Key: MVERIFIER-29 > URL: https://issues.apache.org/jira/browse/MVERIFIER-29 > Project: Maven Verifier Plugin > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MREPOSITORY-44) Upgrade shared verifier
Karl Heinz Marbaise created MREPOSITORY-44: -- Summary: Upgrade shared verifier Key: MREPOSITORY-44 URL: https://issues.apache.org/jira/browse/MREPOSITORY-44 Project: Maven Repository Plugin Issue Type: Dependency upgrade Affects Versions: 3.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MVERIFIER-29) Upgrade verifier to 1.6
Karl Heinz Marbaise created MVERIFIER-29: Summary: Upgrade verifier to 1.6 Key: MVERIFIER-29 URL: https://issues.apache.org/jira/browse/MVERIFIER-29 Project: Maven Verifier Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MREPOSITORY-43) Upgrade plexus-archiver to 3.6.0
[ https://issues.apache.org/jira/browse/MREPOSITORY-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MREPOSITORY-43. -- Resolution: Done Done in [39c383313045b427a38875e2fc7d4c7a6edc3754|https://gitbox.apache.org/repos/asf?p=maven-repository-plugin.git;a=commitdiff;h=39c383313045b427a38875e2fc7d4c7a6edc3754] > Upgrade plexus-archiver to 3.6.0 > > > Key: MREPOSITORY-43 > URL: https://issues.apache.org/jira/browse/MREPOSITORY-43 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MREPOSITORY-43) Upgrade plexus-archiver to 3.6.0
[ https://issues.apache.org/jira/browse/MREPOSITORY-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1652#comment-1652 ] Hudson commented on MREPOSITORY-43: --- Build succeeded in Jenkins: Maven TLP » maven-repository-plugin » master #6 See https://builds.apache.org/job/maven-box/job/maven-repository-plugin/job/master/6/ > Upgrade plexus-archiver to 3.6.0 > > > Key: MREPOSITORY-43 > URL: https://issues.apache.org/jira/browse/MREPOSITORY-43 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MREPOSITORY-43) Upgrade plexus-archiver to 3.6.0
[ https://issues.apache.org/jira/browse/MREPOSITORY-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521109#comment-16521109 ] Hudson commented on MREPOSITORY-43: --- Build succeeded in Jenkins: Maven TLP » maven-repository-plugin » MREPOSITORY-43 #2 See https://builds.apache.org/job/maven-box/job/maven-repository-plugin/job/MREPOSITORY-43/2/ > Upgrade plexus-archiver to 3.6.0 > > > Key: MREPOSITORY-43 > URL: https://issues.apache.org/jira/browse/MREPOSITORY-43 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MREPOSITORY-43) Upgrade plexus-archiver to 3.6.0
Karl Heinz Marbaise created MREPOSITORY-43: -- Summary: Upgrade plexus-archiver to 3.6.0 Key: MREPOSITORY-43 URL: https://issues.apache.org/jira/browse/MREPOSITORY-43 Project: Maven Repository Plugin Issue Type: Improvement Affects Versions: 3.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] michael-o commented on issue #5: Java 7 code update and IDE hints fixed
michael-o commented on issue #5: Java 7 code update and IDE hints fixed URL: https://github.com/apache/maven-project-info-reports-plugin/pull/5#issuecomment-399676949 I really like your changes! Please create a JIRA issue for. I will look for it thoroughly this night. I want it to be in 3.0.0. 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] (MPIR-370) Upgrade transitive BCEL to 6.2 to avoid org.apache.bcel.classfile.ClassFormatException
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521087#comment-16521087
]
Hudson commented on MPIR-370:
-
Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin »
master #21
See
https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/21/
> Upgrade transitive BCEL to 6.2 to avoid
> org.apache.bcel.classfile.ClassFormatException
> --
>
> 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
> Fix For: 3.0.0
>
>
> 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
>
[jira] [Commented] (MRESOLVER-17) Re-parent maven-resolver-provider to maven-resolver (github pull request #3)
[ https://issues.apache.org/jira/browse/MRESOLVER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521085#comment-16521085 ] Robert Scholte commented on MRESOLVER-17: - Right now maven-artifact-resolver has no dependency on maven(-core), which is IMO a very good separation of concern. What is the issue you're trying to solve with this change? > Re-parent maven-resolver-provider to maven-resolver (github pull request #3) > > > Key: MRESOLVER-17 > URL: https://issues.apache.org/jira/browse/MRESOLVER-17 > Project: Maven Resolver > Issue Type: Improvement > Components: resolver >Reporter: Simon Spero >Priority: Minor > Labels: github-import > > [This project doesn't seem to be set up to auto-create issues for pull > requests in JIRA] > See https://github.com/apache/maven-resolver/pull/3 > History is preserved, hence the seemingly large number of commits. > The actual new commits are at the end, and are changes to the poms, plus a > couple of minimal doc comments to avoid checkstyle fail. > The changes to the poms mostly involve version bumps to try and get as many > plexus versions as possible to line up (provider was failing to find classes.) > Wagon was bumped to latest release. > The version of the maven dependencies is configurable ; the pull request > uses 3.3.9. > - > PR comment: > The changes make maven-resolver-provider a sub-project of maven-resolver, > instead of the main maven repository. > These changes allow maven-resolver-provider to be built against maven-3.3.9. > This might make it easier to create a release version of the entire > maven-resolver-suite, with version numbers in the maven-resolver sequence, > rather than the maven line. > Fortunately, the missing OSGI metadata in the jar manifests makes the drop in > version numbers less problematic. It would be nice to have these jars be > bundles again, since aether is used for provisioning OSGI bundles by > containers like Apache Karaf. > Plexus versions are not quite all lined up, but the provider provides (which > is more than it did before the version bumping). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPIR-370) Upgrade transitive BCEL to 6.2 to avoid org.apache.bcel.classfile.ClassFormatException
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-370.
---
Resolution: Fixed
Fixed with
[b8e717557e66adec3bc22813794d8295bfb453fc|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=b8e717557e66adec3bc22813794d8295bfb453fc].
> Upgrade transitive BCEL to 6.2 to avoid
> org.apache.bcel.classfile.ClassFormatException
> --
>
> 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
> Fix For: 3.0.0
>
>
> 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
>
[jira] [Commented] (MPIR-370) Upgrade transitive BCEL to 6.2 to avoid org.apache.bcel.classfile.ClassFormatException
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521081#comment-16521081
]
ASF GitHub Bot commented on MPIR-370:
-
asfgit closed pull request #6: [MPIR-370] Upgrade bcel to avoid
ClassFormatException
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/6
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/pom.xml b/pom.xml
index 9ec8065..8d95a5b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -185,6 +185,17 @@ under the License.
org.apache.maven.shared
maven-shared-jar
1.2
+
+
+ com.google.code.findbugs
+ bcel-findbugs
+
+
+
+
+ org.apache.bcel
+ bcel
+ 6.2
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
> Upgrade transitive BCEL to 6.2 to avoid
> org.apache.bcel.classfile.ClassFormatException
> --
>
> 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
> Fix For: 3.0.0
>
>
> 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
>
[GitHub] asfgit closed pull request #6: [MPIR-370] Upgrade bcel to avoid ClassFormatException
asfgit closed pull request #6: [MPIR-370] Upgrade bcel to avoid ClassFormatException URL: https://github.com/apache/maven-project-info-reports-plugin/pull/6 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/pom.xml b/pom.xml index 9ec8065..8d95a5b 100644 --- a/pom.xml +++ b/pom.xml @@ -185,6 +185,17 @@ under the License. org.apache.maven.shared maven-shared-jar 1.2 + + + com.google.code.findbugs + bcel-findbugs + + + + + org.apache.bcel + bcel + 6.2 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] [Closed] (MRESOLVER-36) SLFJ - remove LoggerFactory from dependency injection
[
https://issues.apache.org/jira/browse/MRESOLVER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRESOLVER-36.
---
Resolution: Fixed
Assignee: Olivier Lamy (*$^¨%`£)
Fix Version/s: Maven Artifact Resolver 1.1.2
Fixed in
[e1976767cf714da24336339f7a6286c6ab50986a|https://gitbox.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=e1976767cf714da24336339f7a6286c6ab50986a]
> SLFJ - remove LoggerFactory from dependency injection
> -
>
> Key: MRESOLVER-36
> URL: https://issues.apache.org/jira/browse/MRESOLVER-36
> Project: Maven Resolver
> Issue Type: Improvement
> Components: resolver
>Affects Versions: Maven Artifact Resolver 1.1.1
>Reporter: Sylwester Lachiewicz
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Fix For: Maven Artifact Resolver 1.1.2
>
>
> Because Maven moved to SL4J as the primary login structure we can remove
> {{NullLoggerFactory}} class and replace {{loggerFactory}} variables with
> {{LoggerFactory.getLogger}}
> To maintain compatibility constructors will be Deprecated
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521076#comment-16521076 ] Michael Osipov commented on MPOM-186: - [~khmarbaise], I must have read another POM, but this is the version in question. We really need 3.0.0 here to solve the BCEL issue. > 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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.2 > This would imply to lift the minimum JRE torun Maven to JRE 7. This is > related to plugins which are require minimum JDK 7 instead of JDK 6. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6400) can not work with a system dependency on a unix / mac / windows project
[
https://issues.apache.org/jira/browse/MNG-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521072#comment-16521072
]
Terrien Jean-Yves commented on MNG-6400:
No this is the problem :
with profile in .m2/settings.xml I've properties defined for each JCO jar with
the value of systemPath depending on OS.
In some project that use JCO, I've a dépencencie with
${sapidoc3}
${sapijco3}
In this configuration it work with maven 3.3.9 but not with maven 3.5.3
=> error absolute path is ${sapjco3}
> can not work with a system dependency on a unix / mac / windows project
> ---
>
> Key: MNG-6400
> URL: https://issues.apache.org/jira/browse/MNG-6400
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.3
> Environment: Windows 07
>Reporter: Terrien Jean-Yves
>Priority: Blocker
> Fix For: waiting-for-feedback
>
>
> the sapjco3.jar and sapIdoc3.jar jars can not be renamed.
> to work with you have to use an addiction system
> however, a unix / windows project can not have an identical absolute path on
> both systems.
> in previous versions of maven you can set properties in .m2 / settings.xml
> and and use system
> $ \{sapidoc3}
> a warnning will be displayed.
> on version 3.5.3 it is an error.
> But that's not all because even putting the system dependency with an
> absolute path the jar is not found with the correct name
>
> de.sap
> sapjco3
> 3.0.0
> system
> D:/project-ati/libs/libsap/sapjco3.jar
>
> JCO3 code
> protected boolean registerNativeMethods(Class clazz){
> if(!initializedDLL){
> try{
> JCoRuntime.nativeLibraryPath = loadLibrary("sapjco3");
> initializedDLL = true;
> }catch(UnsatisfiedLinkError arg2){
> JCoRuntime.nativeLibraryPath = "not loaded, caused by " + arg2.toString();
> arg2.printStackTrace();
> throw arg2;
> }
> }
> return true;
> }
> java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1865)
> at java.lang.Runtime.loadLibrary0(Runtime.java:870)
> at java.lang.System.loadLibrary(System.java:1122)
> at
> com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:444)
>
> The first sap-schema-plugin is a project with sap dependencies defined by an
> absolute path or property. it compiles well.
> the second project use this plugin.
> if the plugin project is compiled whith properties
> => error absolute pah is ${sapjco3}
> if the plugin project is compiled with absolute path
> => java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
>
> the same project without change with maven 3.3.9 works perfectly
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPOM-188) maven-invoker-plugin should copy value of https.protocols system property during invocation
[
https://issues.apache.org/jira/browse/MPOM-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPOM-188:
---
Description:
Central now requires at least TLSv1.2, which has to be activated for Java 7
from commandline with {{-Dhttps.protocols=TLSv1.2}}.
In such case, maven-invoker-plugin should use the same property value of
{{https.protocols}}, so better to always copy this value from Maven runtime
environment to invoker environment.
was:
Central now requires at least TLSv1.2, which can be activated for Java 7 from
commandline with {{-Dhttps.protocols=TLSv1.2}}.
In such case, maven-invoker-plugin should use the same property value of
{{https.protocols}}, so better to always copy this value from Maven runtime
environment to invoker environment.
> maven-invoker-plugin should copy value of https.protocols system property
> during invocation
> ---
>
> Key: MPOM-188
> URL: https://issues.apache.org/jira/browse/MPOM-188
> Project: Maven POMs
> Issue Type: Dependency upgrade
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: MAVEN-32
>
>
> Central now requires at least TLSv1.2, which has to be activated for Java 7
> from commandline with {{-Dhttps.protocols=TLSv1.2}}.
> In such case, maven-invoker-plugin should use the same property value of
> {{https.protocols}}, so better to always copy this value from Maven runtime
> environment to invoker environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (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 reassigned MPOM-186: Assignee: Karl Heinz Marbaise > 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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.2 > This would imply to lift the minimum JRE torun Maven to JRE 7. This is > related to plugins which are require minimum JDK 7 instead of JDK 6. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6028) When a reactor build fails maven should include current goals in resume suggestion
[
https://issues.apache.org/jira/browse/MNG-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521048#comment-16521048
]
ASF GitHub Bot commented on MNG-6028:
-
hboutemy commented on issue #165: [MNG-6028] Include current goals in resume
suggestion
URL: https://github.com/apache/maven/pull/165#issuecomment-399664736
than you Axel for feedback: it's good to have discussion.
IMHO, the reality of how I work is: I scroll up to get my previous command
then add the "-rf xxx"
don't you do the same?
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
> When a reactor build fails maven should include current goals in resume
> suggestion
> --
>
> Key: MNG-6028
> URL: https://issues.apache.org/jira/browse/MNG-6028
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.3.9
>Reporter: Axel Fontaine
>Priority: Major
> Fix For: 3.6.x-candidate
>
>
> Start multiproject build at root with mvn clean install
> if module-a fails you currently get
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn -rf :module-a{noformat}
> to be able to easily copy-paste this it would be much nicer if the goals were
> already filled in:
> {noformat}[ERROR] After correcting the problems, you can resume the build
> with the command
> [ERROR] mvn clean install -rf :module-a{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] hboutemy commented on issue #165: [MNG-6028] Include current goals in resume suggestion
hboutemy commented on issue #165: [MNG-6028] Include current goals in resume suggestion URL: https://github.com/apache/maven/pull/165#issuecomment-399664736 than you Axel for feedback: it's good to have discussion. IMHO, the reality of how I work is: I scroll up to get my previous command then add the "-rf xxx" don't you do the same? 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] (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:comment-tabpanel=16521047#comment-16521047 ] Karl Heinz Marbaise commented on MPOM-186: -- [~michael-o] Maybe I misunderstood your commit but https://github.com/apache/maven-apache-parent/blob/apache-19/pom.xml#L202 ? > 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 >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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.2 > This would imply to lift the minimum JRE torun Maven to JRE 7. This is > related to plugins which are require minimum JDK 7 instead of JDK 6. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (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:comment-tabpanel=16521047#comment-16521047 ] Karl Heinz Marbaise edited comment on MPOM-186 at 6/23/18 10:46 AM: [~michael-o] Maybe I misunderstood your comment but https://github.com/apache/maven-apache-parent/blob/apache-19/pom.xml#L202 ? was (Author: khmarbaise): [~michael-o] Maybe I misunderstood your commit but https://github.com/apache/maven-apache-parent/blob/apache-19/pom.xml#L202 ? > 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 >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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.2 > This would imply to lift the minimum JRE torun Maven to JRE 7. This is > related to plugins which are require minimum JDK 7 instead of JDK 6. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- 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 * maven-surefire/failsafe 2.22.0 * maven-plugin-plugin 3.5.2 This would imply to lift the minimum JRE torun Maven to JRE 7. This is related to plugins which are require minimum JDK 7 instead of JDK 6. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. Furthermore [security related things |http://maven.apache.org/security-plexus-archiver.html] 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 * maven-surefire/failsafe 2.22.0 * maven-plugin-plugin 3.5.2 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. Furthermore [security related things |http://maven.apache.org/security-plexus-archiver.html] > 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 >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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.2 > This would imply to lift the minimum JRE torun Maven to JRE 7. This is > related to plugins which are require minimum JDK 7 instead of JDK 6. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521043#comment-16521043 ] Hudson commented on MPOM-186: - Build succeeded in Jenkins: Maven TLP » maven-apache-parent » MPOM-186 #4 See https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/MPOM-186/4/ > 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 >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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.2 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- 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 * maven-surefire/failsafe 2.22.0 * maven-plugin-plugin 3.5.2 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. Furthermore [security related things |http://maven.apache.org/security-plexus-archiver.html] 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 * maven-surefire/failsafe 2.22.0 * maven-plugin-plugin 3.5.3 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. Furthermore [security related things |http://maven.apache.org/security-plexus-archiver.html] > 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 >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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.2 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- 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 * maven-surefire/failsafe 2.22.0 * maven-plugin-plugin 3.5.3 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. Furthermore [security related things |http://maven.apache.org/security-plexus-archiver.html] 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 * maven-surefire/failsafe 2.22.0 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. Furthermore [security related things |http://maven.apache.org/security-plexus-archiver.html] > 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 >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 > * maven-surefire/failsafe 2.22.0 > * maven-plugin-plugin 3.5.3 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- 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 * maven-surefire/failsafe 2.22.0 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. Furthermore [security related things |http://maven.apache.org/security-plexus-archiver.html] 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 * maven-surefire/failsafe 2.22.0 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. > 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 >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 > * maven-surefire/failsafe 2.22.0 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. Furthermore > [security related things > |http://maven.apache.org/security-plexus-archiver.html] -- 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 * maven-surefire/failsafe 2.22.0 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. Several projects are already upgrading different plugins to get the running with JDK9/JDK10 (for example surefire) and others as well. 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 * maven-surefire/failsafe 2.22.0 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. > 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 >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 > * maven-surefire/failsafe 2.22.0 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. > Several projects are already upgrading different plugins to get the running > with JDK9/JDK10 (for example surefire) and others as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPOM-191) Add maven-ear-plugin version
Karl Heinz Marbaise created MPOM-191: Summary: Add maven-ear-plugin version Key: MPOM-191 URL: https://issues.apache.org/jira/browse/MPOM-191 Project: Maven POMs Issue Type: Improvement Components: asf Affects Versions: ASF-20 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: ASF-20 Add the version for maven-ear-plugin which is not yet added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521040#comment-16521040 ] Hudson commented on MPOM-186: - Build succeeded in Jenkins: Maven TLP » maven-apache-parent » MPOM-186 #3 See https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/MPOM-186/3/ > 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 >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 > * maven-surefire/failsafe 2.22.0 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521038#comment-16521038 ] Michael Osipov commented on MPOM-186: - [~hboutemy], it is at least MPIR-370 is will merge today and start the vote. But as far as I can see, Apache Parent does not contain MPIR. Seems to be safe to continue. > 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 >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 > * maven-surefire/failsafe 2.22.0 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521034#comment-16521034 ] Hudson commented on MPOM-186: - Build succeeded in Jenkins: Maven TLP » maven-apache-parent » MPOM-186 #2 See https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/MPOM-186/2/ > 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 >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 > * maven-surefire/failsafe 2.22.0 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPIR-370) Upgrade transitive BCEL to 6.2 to avoid org.apache.bcel.classfile.ClassFormatException
[
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-370:
Summary: Upgrade transitive BCEL to 6.2 to avoid
org.apache.bcel.classfile.ClassFormatException (was:
org.apache.bcel.classfile.ClassFormatException when scanning log4j-api)
> Upgrade transitive BCEL to 6.2 to avoid
> org.apache.bcel.classfile.ClassFormatException
> --
>
> 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
> Fix For: 3.0.0
>
>
> 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
>
[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 * maven-surefire/failsafe 2.22.0 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice 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 This would imply to lift the minimum JRE torun Maven to JRE 7 (notice maven.compiler.source are currently 1.6).. > 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 >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 > * maven-surefire/failsafe 2.22.0 > This would imply to lift the minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521032#comment-16521032 ] Karl Heinz Marbaise commented on MPOM-186: -- I can simply add it > 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 >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 minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521033#comment-16521033 ] Hervé Boutemy commented on MPOM-186: [~michael-o] 1. any version info, or Jira issue? 2. does that mean that we should do a MPIR release before Apache parent POM? > 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 >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 minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16521031#comment-16521031 ] Hervé Boutemy commented on MPOM-186: notice: Surefire upgrade from 2.21 to 2.22 is not proposed does anybody know why? > 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 >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 minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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 ] Hervé Boutemy reassigned MPOM-186: -- Assignee: (was: Hervé Boutemy) > 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 >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 minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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 ] Hervé Boutemy reassigned MPOM-186: -- Assignee: Hervé Boutemy (was: Karl Heinz Marbaise) > 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: Hervé Boutemy >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 minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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 updated MPIR-370:
Fix Version/s: 3.0.0
> 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
> Fix For: 3.0.0
>
>
> 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] [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 ] Hervé Boutemy 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 minimum JRE torun Maven to JRE 7 (notice 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 This would imply to lift the JDK minimum to JDK 7 (maven.compiler.source are currently 1.6).. > 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 minimum JRE torun Maven to JRE 7 (notice > maven.compiler.source are currently 1.6).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MDOAP-52) Upgrade plexus-utils 3.1.0
Karl Heinz Marbaise created MDOAP-52: Summary: Upgrade plexus-utils 3.1.0 Key: MDOAP-52 URL: https://issues.apache.org/jira/browse/MDOAP-52 Project: Maven DOAP Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MDOAP-51) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MDOAP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDOAP-51: - Description: JDK 10 needed update. > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MDOAP-51 > URL: https://issues.apache.org/jira/browse/MDOAP-51 > Project: Maven DOAP Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > JDK 10 needed update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MDOAP-51) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MDOAP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDOAP-51. Resolution: Done Done in [459274a266d4966f2637ebeea58192c600ada88d|https://gitbox.apache.org/repos/asf?p=maven-doap-plugin.git;a=commitdiff;h=459274a266d4966f2637ebeea58192c600ada88d] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MDOAP-51 > URL: https://issues.apache.org/jira/browse/MDOAP-51 > Project: Maven DOAP Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MDOAP-51) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MDOAP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDOAP-51: - Issue Type: Bug (was: Dependency upgrade) > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MDOAP-51 > URL: https://issues.apache.org/jira/browse/MDOAP-51 > Project: Maven DOAP Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPOM-190) Change to https instead of http
[ https://issues.apache.org/jira/browse/MPOM-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521015#comment-16521015 ] Hudson commented on MPOM-190: - Build succeeded in Jenkins: Maven TLP » maven-parent » master #79 See https://builds.apache.org/job/maven-box/job/maven-parent/job/master/79/ > Change to https instead of http > --- > > Key: MPOM-190 > URL: https://issues.apache.org/jira/browse/MPOM-190 > Project: Maven POMs > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-32 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: MAVEN-32 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-190) Change to https instead of http
[ https://issues.apache.org/jira/browse/MPOM-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPOM-190. Resolution: Done Done in [5c3996060495abc814629bc11f16cd068b2dd0a8|https://gitbox.apache.org/repos/asf?p=maven-parent.git;a=commitdiff;h=5c3996060495abc814629bc11f16cd068b2dd0a8] > Change to https instead of http > --- > > Key: MPOM-190 > URL: https://issues.apache.org/jira/browse/MPOM-190 > Project: Maven POMs > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-32 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: MAVEN-32 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPOM-190) Change to https instead of http
Karl Heinz Marbaise created MPOM-190: Summary: Change to https instead of http Key: MPOM-190 URL: https://issues.apache.org/jira/browse/MPOM-190 Project: Maven POMs Issue Type: Improvement Components: maven Affects Versions: MAVEN-32 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: MAVEN-32 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MRRESOURCES-104) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MRRESOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRRESOURCES-104. --- Resolution: Duplicate > Upgrade parent to 31 > > > Key: MRRESOURCES-104 > URL: https://issues.apache.org/jira/browse/MRRESOURCES-104 > Project: Maven Remote Resources Plugin > Issue Type: Dependency upgrade >Affects Versions: 1.6 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPOM-188) maven-invoker-plugin should copy value of https.protocols system property during invocation
[
https://issues.apache.org/jira/browse/MPOM-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPOM-188:
---
Summary: maven-invoker-plugin should copy value of https.protocols system
property during invocation (was: maven-invoker-plugin should copy value of
https.protocols during invocation)
> maven-invoker-plugin should copy value of https.protocols system property
> during invocation
> ---
>
> Key: MPOM-188
> URL: https://issues.apache.org/jira/browse/MPOM-188
> Project: Maven POMs
> Issue Type: Dependency upgrade
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: MAVEN-32
>
>
> Central now requires at least TLSv1.2, which can be activated for Java 7 from
> commandline with {{-Dhttps.protocols=TLSv1.2}}.
> In such case, maven-invoker-plugin should use the same property value of
> {{https.protocols}}, so better to always copy this value from Maven runtime
> environment to invoker environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPOM-188) maven-invoker-plugin should copy value of https.protocols during invocation
[
https://issues.apache.org/jira/browse/MPOM-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPOM-188:
---
Description:
Central now requires at least TLSv1.2, which can be activated for Java 7 from
commandline with {{-Dhttps.protocols=TLSv1.2}}.
In such case, maven-invoker-plugin should use the same property value of
{{https.protocols}}, so better to always copy this value from Maven runtime
environment to invoker environment.
was:Central now requires at least TLSv1.2, which can be passed from
commandline. In such case, maven-invoker-plugin should use the same value of
{{https.protocols}}, so better to always copy this value.
> maven-invoker-plugin should copy value of https.protocols during invocation
> ---
>
> Key: MPOM-188
> URL: https://issues.apache.org/jira/browse/MPOM-188
> Project: Maven POMs
> Issue Type: Dependency upgrade
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: MAVEN-32
>
>
> Central now requires at least TLSv1.2, which can be activated for Java 7 from
> commandline with {{-Dhttps.protocols=TLSv1.2}}.
> In such case, maven-invoker-plugin should use the same property value of
> {{https.protocols}}, so better to always copy this value from Maven runtime
> environment to invoker environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
