[jira] [Updated] (MNG-6526) Upgrade to Wagon 3.3.1 (from 3.2.0)
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6526: --- Description: Wagon 3.3.0 contains an important improvement for the transfer speed of large artifacts (see WAGON-537). h2. Release Notes - Maven Wagon - Version 3.3.0 h3. Bug * [WAGON-538] - Basic authentication fails if the password contains non-ASCII characters h3. Improvement * [WAGON-537] - Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy * [WAGON-539] - Explicitly register only supported auth schemes * [WAGON-540] - Switch to modern-day encoding (UTF-8) of auth credentials h2. Release Notes - Maven Wagon - Version 3.3.1 h3. Bug * [WAGON-538] - Basic authentication fails if the password contains non-ASCII characters * [WAGON-543] - wagon-ssh download hangs h3. Improvement * [WAGON-537] - Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy * [WAGON-539] - Explicitly register only supported auth schemes * [WAGON-540] - Switch to modern-day encoding (UTF-8) of auth credentials h3. Task * [WAGON-544] - Work around JSch issue #122 was:Wagon 3.3.0 contains an important improvement for the transfer speed of large artifacts (see WAGON-537). > Upgrade to Wagon 3.3.1 (from 3.2.0) > --- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). > > h2. Release Notes - Maven Wagon - Version 3.3.0 > h3. Bug > * [WAGON-538] - Basic authentication fails if the password contains > non-ASCII characters > h3. Improvement > * [WAGON-537] - Maven transfer speed of large artifacts is slow due to > unsuitable buffer strategy > * [WAGON-539] - Explicitly register only supported auth schemes > * [WAGON-540] - Switch to modern-day encoding (UTF-8) of auth credentials > h2. Release Notes - Maven Wagon - Version 3.3.1 > h3. Bug > * [WAGON-538] - Basic authentication fails if the password contains > non-ASCII characters > * [WAGON-543] - wagon-ssh download hangs > h3. Improvement > * [WAGON-537] - Maven transfer speed of large artifacts is slow due to > unsuitable buffer strategy > * [WAGON-539] - Explicitly register only supported auth schemes > * [WAGON-540] - Switch to modern-day encoding (UTF-8) of auth credentials > h3. Task > * [WAGON-544] - Work around JSch issue #122 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6526) Upgrade to Wagon 3.3.1 (from 3.2.0)
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6526: --- Summary: Upgrade to Wagon 3.3.1 (from 3.2.0) (was: Upgrade to Wagon 3.3.1 (from 2.2.0)) > Upgrade to Wagon 3.3.1 (from 3.2.0) > --- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6591) Upgrade to Wagon 3.3.2
[ https://issues.apache.org/jira/browse/MNG-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6591: --- Description: Version 3.3.1 contains a regression which needed to be fixed. h2. Release Notes - Maven Wagon - Version 3.3.2 h3. Bug * [WAGON-545] - Connection reset while downloading artifacts in cloud environment (Azure) * [WAGON-546] - HttpWagon TTL not set * [WAGON-554] - Tests with checkin rely on global Git config h3. Task * [WAGON-552] - Replace Commons Codec with Plexus Utils * [WAGON-555] - Use java.nio.file.Path for URI construction of file:// URIs in tests * [WAGON-556] - Skip parsing of user info for file:// URLs h3. Dependency upgrade * [WAGON-547] - Upgrade HttpCore to 4.4.11 * [WAGON-548] - Upgrade HttpClient to 4.5.7 * [WAGON-549] - Upgrade Commons Net to 3.6 * [WAGON-550] - Upgrade JSoup to 1.11.3 * [WAGON-551] - Uprade JSch to 0.1.55 * [WAGON-553] - Upgrade Plexus Classworlds to 2.6.0 was:Version 3.3.1 contains a regression which needed to be fixed. > Upgrade to Wagon 3.3.2 > -- > > Key: MNG-6591 > URL: https://issues.apache.org/jira/browse/MNG-6591 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Version 3.3.1 contains a regression which needed to be fixed. > h2. Release Notes - Maven Wagon - Version 3.3.2 > h3. Bug > * [WAGON-545] - Connection reset while downloading artifacts in cloud > environment (Azure) > * [WAGON-546] - HttpWagon TTL not set > * [WAGON-554] - Tests with checkin rely on global Git config > h3. Task > * [WAGON-552] - Replace Commons Codec with Plexus Utils > * [WAGON-555] - Use java.nio.file.Path for URI construction of file:// > URIs in tests > * [WAGON-556] - Skip parsing of user info for file:// URLs > h3. Dependency upgrade > * [WAGON-547] - Upgrade HttpCore to 4.4.11 > * [WAGON-548] - Upgrade HttpClient to 4.5.7 > * [WAGON-549] - Upgrade Commons Net to 3.6 > * [WAGON-550] - Upgrade JSoup to 1.11.3 > * [WAGON-551] - Uprade JSch to 0.1.55 > * [WAGON-553] - Upgrade Plexus Classworlds to 2.6.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6526) Upgrade to Wagon 3.3.1 (from 2.2.0)
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6526: --- Summary: Upgrade to Wagon 3.3.1 (from 2.2.0) (was: Upgrade to Wagon 3.3.1) > Upgrade to Wagon 3.3.1 (from 2.2.0) > --- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6255) Maven script cannot parse jvm.config with CRLF
[
https://issues.apache.org/jira/browse/MNG-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810418#comment-16810418
]
Hudson commented on MNG-6255:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #13
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/13/
> Maven script cannot parse jvm.config with CRLF
> --
>
> Key: MNG-6255
> URL: https://issues.apache.org/jira/browse/MNG-6255
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 7 with MINGW64 environment via Git for Windows
> 0.1.1 including GNU coreutils and bash 4.4.12
>Reporter: Andrew Kennedy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.5.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A project with a {{.mvn/jvm.config}} file that has *CRLF* line endings will
> not parse it correctly. The script uses the {{tr}} command to change *LF* to
> space, but this leaves *CR* behind. For example, with the {{jvm.config}} file
> containing the text {{-Xmx1024m -Xms512m}} followed by *CRLF*, the following
> error message is printed:
> {code}
> $ mvn install
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Invalid initial heap size: -Xms512m
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6613) Mirror matching ignores closest/nearest definition
[
https://issues.apache.org/jira/browse/MNG-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810416#comment-16810416
]
Hudson commented on MNG-6613:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #13
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/13/
> Mirror matching ignores closest/nearest definition
> --
>
> Key: MNG-6613
> URL: https://issues.apache.org/jira/browse/MNG-6613
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.5.4, 3.6.1
> Environment: Java 8u202, Java11u2
>Reporter: Michael Osipov
>Priority: Critical
> Attachments: log.txt
>
>
> Ran our IT suite in a locked down environment at work, w/o direct internet
> access. IT {{mng3461MirrorMatching(itNonGreedyWildcard)}} blocks forever
> because the mirror exclude does not work: {{*,!maven-core-it}}.
> It still tries to download via mirror instead of ignoring it. See attached
> log file. Even switching {{!maven-core-it,*}} makes no difference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6506) Mojos are unable to load package annotations on Java >= 9
[
https://issues.apache.org/jira/browse/MNG-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810417#comment-16810417
]
Hudson commented on MNG-6506:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #13
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/13/
> Mojos are unable to load package annotations on Java >= 9
> -
>
> Key: MNG-6506
> URL: https://issues.apache.org/jira/browse/MNG-6506
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.6.0
>Reporter: Andreas Veithen
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Labels: up-for-grabs
> Fix For: 3.6.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On Java 9 and above, calls to {{java.lang.Package.getAnnotation(Class)}} from
> within a Mojo always return {{null}} (unless the {{package-info}} class has
> been loaded by some other means before).
> The reason appears to be an incompatibility between Java 9 and Plexus
> Classworlds:
> * Java 9 ultimately calls {{findClass}} (instead of {{loadClass}}) to get the
> {{package-info}} class.
> * The {{findClass}} implementation in {{ClassRealm}} always throws
> {{ClassNotFoundException}}:
> https://github.com/codehaus-plexus/plexus-classworlds/blob/master/src/main/java/org/codehaus/plexus/classworlds/realm/ClassRealm.java#L275.
> This in particular affects plugins that interact with the JAXB API because it
> relies on package annotations.
> A workaround is to preload the required {{package-info}} classes using
> {{loadClass}}; see e.g. http://svn.apache.org/viewvc?rev=1845026&view=rev.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6255) Maven script cannot parse jvm.config with CRLF
[
https://issues.apache.org/jira/browse/MNG-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810399#comment-16810399
]
Hudson commented on MNG-6255:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Maven script cannot parse jvm.config with CRLF
> --
>
> Key: MNG-6255
> URL: https://issues.apache.org/jira/browse/MNG-6255
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 7 with MINGW64 environment via Git for Windows
> 0.1.1 including GNU coreutils and bash 4.4.12
>Reporter: Andrew Kennedy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.5.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A project with a {{.mvn/jvm.config}} file that has *CRLF* line endings will
> not parse it correctly. The script uses the {{tr}} command to change *LF* to
> space, but this leaves *CR* behind. For example, with the {{jvm.config}} file
> containing the text {{-Xmx1024m -Xms512m}} followed by *CRLF*, the following
> error message is printed:
> {code}
> $ mvn install
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Invalid initial heap size: -Xms512m
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6593) track input location for super-pom
[ https://issues.apache.org/jira/browse/MNG-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810385#comment-16810385 ] Hudson commented on MNG-6593: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > track input location for super-pom > -- > > Key: MNG-6593 > URL: https://issues.apache.org/jira/browse/MNG-6593 > Project: Maven > Issue Type: Improvement > Components: Inheritance and Interpolation >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 3.6.1 > > > while working on MPH-160, found that input location from > [super-pom|https://maven.apache.org/ref/current/maven-model-builder/super-pom.html] > content is not tracked -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6573) Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI
[ https://issues.apache.org/jira/browse/MNG-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810380#comment-16810380 ] Hudson commented on MNG-6573: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI > -- > > Key: MNG-6573 > URL: https://issues.apache.org/jira/browse/MNG-6573 > Project: Maven > Issue Type: Task > Components: Integration Tests >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.6.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Maven Core Integration Test passed ok for Linux and Windows for Java 7, 8, > 11, 12-ea, 13-ea. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6613) Mirror matching ignores closest/nearest definition
[
https://issues.apache.org/jira/browse/MNG-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810398#comment-16810398
]
Hudson commented on MNG-6613:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Mirror matching ignores closest/nearest definition
> --
>
> Key: MNG-6613
> URL: https://issues.apache.org/jira/browse/MNG-6613
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.5.4, 3.6.1
> Environment: Java 8u202, Java11u2
>Reporter: Michael Osipov
>Priority: Critical
> Attachments: log.txt
>
>
> Ran our IT suite in a locked down environment at work, w/o direct internet
> access. IT {{mng3461MirrorMatching(itNonGreedyWildcard)}} blocks forever
> because the mirror exclude does not work: {{*,!maven-core-it}}.
> It still tries to download via mirror instead of ignoring it. See attached
> log file. Even switching {{!maven-core-it,*}} makes no difference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6558) ToolchainsBuildingResult event is not sent on EventSpy
[
https://issues.apache.org/jira/browse/MNG-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810381#comment-16810381
]
Hudson commented on MNG-6558:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> ToolchainsBuildingResult event is not sent on EventSpy
> --
>
> Key: MNG-6558
> URL: https://issues.apache.org/jira/browse/MNG-6558
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.0
>Reporter: Guy Brand
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> On the {{EventSpy}} we get the {{ToolchainsBuildingRequest}} event twice and
> the {{ToolchainsBuildingResult}} is not sent. The problem is
> [here|https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1268]
> where the {{ToolchainsBuildingRequest}} event is sent twice to the
> {{eventSpyDispatcher}} instead of the {{ToolchainsBuildingResult}} event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6495) ModelResolver cannot be null
[
https://issues.apache.org/jira/browse/MNG-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810384#comment-16810384
]
Hudson commented on MNG-6495:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> ModelResolver cannot be null
>
>
> Key: MNG-6495
> URL: https://issues.apache.org/jira/browse/MNG-6495
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.5.4
>Reporter: Elliotte Rusty Harold
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.1
>
>
> Got this exception stacktrace while writing some of my own code today:
> {noformat}
> Exception in thread "main" java.lang.NullPointerException:
> request.modelResolver cannot be null (parent POM
> com.google.guava:guava-parent:26.0-jre and POM
> com.google.guava:guava:[unknown-version])
> at org.apache.commons.lang3.Validate.notNull(Validate.java:225)
> at
> org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1046)
> at
> org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:830)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:332)
> at
> com.google.cloud.tools.opensource.dependencies.MetadataExplorer.main(MetadataExplorer.java:50)
> {noformat}
> No big deal except that the JavaDoc at
> [ModelBuildingRequest|http://maven.apache.org/ref/3.5.4/maven-model-builder/apidocs/org/apache/maven/model/building/ModelBuildingRequest.html]
> says "The model resolver to use, may be null."
> Not sure whether to update the docs or the code here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6571) Maven memory consumption issue
[ https://issues.apache.org/jira/browse/MNG-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810382#comment-16810382 ] Hudson commented on MNG-6571: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Maven memory consumption issue > -- > > Key: MNG-6571 > URL: https://issues.apache.org/jira/browse/MNG-6571 > Project: Maven > Issue Type: Wish >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 3.6.1 > > Attachments: Maven-Reactor-Dump-Patched.png, Maven-Reactor-Dump.png > > > as reported on Users list: > https://lists.apache.org/thread.html/7d75142448b3c234742bdfd3c743e2f62065fe8e0a313905cbbb2523@%3Cusers.maven.apache.org%3E > then with details on Dev list: > https://lists.apache.org/thread.html/34b64295238594e554f1f2f119848bce3b60d4e1e22e09f26aa64166@%3Cdev.maven.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5995) Maven itself cannot run without maven-compat
[
https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810379#comment-16810379
]
Hudson commented on MNG-5995:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Maven itself cannot run without maven-compat
>
>
> Key: MNG-5995
> URL: https://issues.apache.org/jira/browse/MNG-5995
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build, core
>Affects Versions: 3.3.9
>Reporter: Robert Scholte
>Assignee: Sylwester Lachiewicz
>Priority: Critical
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For all the 3.0 versions of the maven-plugins we require to not depend on
> maven-compat anymore. However, the Maven distribution still requires
> maven-compat. A simple proof: remove {{lib/maven-compat-3.x.y}} and execute
> {{mvn validate}}.
> You'll get the following exception:
> {noformat}[WARNING] Error injecting:
> org.apache.maven.project.DefaultProjectBuildingHelper
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> 1) No implementation for org.apache.maven.repository.RepositorySystem was
> bound.
> while locating
> org.apache.maven.project.DefaultProjectBuildingHelper{noformat}
> Reason: there's only one implementation: o.a.m.r.l.LegacyRepositorySystem,
> which is part of maven-compat.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6069) Migrate to non deprecated parts of Commons CLI
[
https://issues.apache.org/jira/browse/MNG-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810377#comment-16810377
]
Hudson commented on MNG-6069:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Migrate to non deprecated parts of Commons CLI
> --
>
> Key: MNG-6069
> URL: https://issues.apache.org/jira/browse/MNG-6069
> Project: Maven
> Issue Type: Improvement
> Components: Embedding
>Affects Versions: 3.3.9, 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.x / Backlog
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment all parts of {{OptionBuilder...}} are marked deprecated in
> {{CLIManager}}. They should be migrated to:
> {code:java}
> Option.builder( HELP ).longOpt( "help" ).desc( "Display help information"
> ).build()
> {code}
> Ensure that the following command succeeds: {{mvn -X -D x=1 -D y=2 test}} (
> watch out for the space after {{-D}} )
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6543) Upgrade plexus classworld to support java 9+ ClassLoader.findClass(String moduleName, String name) in Mojos
[ https://issues.apache.org/jira/browse/MNG-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810394#comment-16810394 ] Hudson commented on MNG-6543: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Upgrade plexus classworld to support java 9+ ClassLoader.findClass(String > moduleName, String name) in Mojos > --- > > Key: MNG-6543 > URL: https://issues.apache.org/jira/browse/MNG-6543 > Project: Maven > Issue Type: Bug > Components: Class Loading >Affects Versions: 3.6.0 >Reporter: Romain Manni-Bucau >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.6.1 > > Attachments: MNG-6543-xjc.zip > > > Goal is to include > https://github.com/codehaus-plexus/plexus-classworlds/pull/4 in Maven and > enable Mojos using this Java 9 new JPMS API to work under java 9+ > see [Java 9 ClassLoader.findClass(String moduleName,String > name)|https://docs.oracle.com/javase/9/docs/api/java/lang/ClassLoader.html#findClass-java.lang.String-java.lang.String-] > see MNG-6506 for more details -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6533) ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in exception report
[
https://issues.apache.org/jira/browse/MNG-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810378#comment-16810378
]
Hudson commented on MNG-6533:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in
> exception report
>
>
> Key: MNG-6533
> URL: https://issues.apache.org/jira/browse/MNG-6533
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.5.4, 3.6.0
>Reporter: Mickael Istria
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To save a lot of CPU and RAM in Eclipse m2e, we're trying to use
> {{ProjectBuilder.build(List projects ...)}} instead of sequencing
> multiple {{Projectbuilder.build(File singleProject...)}}. This has a big
> positive impact on m2e.
> However, we noticed that when the operation is failing in some case because
> pom is incomplete (which is a pretty usual state in the IDE), the
> multi-projects method does not return the MavenProject in the
> {{ProjectBuildingException.getResults()}}, while the single-project method
> does.
> Adding MavenProject for the multi-project {{ProjectBuilder.build(...)}} would
> allow m2e to use this method and save ~75% RAM and CPU in many operations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6605) Allow to suppress download messages in interactive mode
[
https://issues.apache.org/jira/browse/MNG-6605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810396#comment-16810396
]
Hudson commented on MNG-6605:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Allow to suppress download messages in interactive mode
> ---
>
> Key: MNG-6605
> URL: https://issues.apache.org/jira/browse/MNG-6605
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.6.0
>Reporter: Gunnar Wagenknecht
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.1
>
> Attachments: 2019-03-06_14-06-09.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When running Maven in batch mode (with option {{-B}}) it's possible to
> suppress download messages using
> "{{-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}"
> Example:
> {{mvn clean install -B
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}
> When leaving out the {{-B}} option this no longer works.
> *Example:*
> {noformat}
> export MAVEN_OPTS='-Xmx1g
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
> -Dorg.slf4j.simpleLogger.showDateTime=true
> -Dorg.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss'
> mvn clean install
> {noformat}
> Prints out time stamps as configured but does not suppress download progress
> messages.
> *Expected:*
> Suppressing "Downloaded" messages from the console output should be possible
> without requiring the "{{--batch-mode}}" command line argument.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6572) use int or long instead of BigIntegers for little numbers in ComparableVersion
[
https://issues.apache.org/jira/browse/MNG-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810391#comment-16810391
]
Hudson commented on MNG-6572:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> use int or long instead of BigIntegers for little numbers in ComparableVersion
> --
>
> Key: MNG-6572
> URL: https://issues.apache.org/jira/browse/MNG-6572
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories, Performance
>Affects Versions: 3.6.0
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Labels: up-for-grabs
> Fix For: 3.6.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> while working on MNG-6571, we found that this could enhance performance when
> many versions are compared: perhaps not in Maven builds, since this is
> probably negligible, but in other scenario where version comparison is used,
> this could be useful
> see
> https://github.com/apache/maven/blob/master/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/ComparableVersion.java
> for every Integer, a BigInteger is currently used
> but for integer that have less than 10 digits, an int would be sufficient and
> would be a lot more efficient
> and for integers that are less than 19 digits, a long would be the way to go
> the biggest numbers we get usually is the timestamp of a SNAPSHOT, like
> {{20171015.230843}} (MMDD.HHmmss), then an int will be sufficient in the
> vast majority of case
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6618) Maven doesn't export org.slf4j.event.Level
[
https://issues.apache.org/jira/browse/MNG-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810397#comment-16810397
]
Hudson commented on MNG-6618:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Maven doesn't export org.slf4j.event.Level
> --
>
> Key: MNG-6618
> URL: https://issues.apache.org/jira/browse/MNG-6618
> Project: Maven
> Issue Type: Task
>Affects Versions: 3.6.0
>Reporter: Viacheslav Yakunin
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
>
> Hi, this is the same issue as
> [MNG-6360|https://issues.apache.org/jira/browse/MNG-6360]. Unfortunately I
> was not able to reopen it so I am creating new one.
> I was able to reproduce it when I tried to create maven plugin for running
> kafka broker during integration tests. Kafka refers to org.slf4j.event.Level
> and this causes following exception during plugin execution.
> {code:java}
> [ERROR] [KafkaServer id=1] Fatal error during KafkaServer shutdown.
> java.lang.NoClassDefFoundError: org/slf4j/event/Level
> at
> kafka.utils.CoreUtils$.swallow$default$3(CoreUtils.scala:84)
> at kafka.server.KafkaServer.shutdown(KafkaServer.scala:567)
> at
> net.sla.buildtools.kafka.maven.plugin.SingletonLauncher.stop(SingletonLauncher.java:73)
> at
> net.sla.buildtools.kafka.maven.plugin.StopKafkaBrokerMojo.execute(StopKafkaBrokerMojo.java:18)
> 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 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
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:65)
> Caused by: java.lang.ClassNotFoundException: org.slf4j.event.Level
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm
[jira] [Commented] (MNG-6559) Mailing list URL is incorrect in CONTRIBUTING.md
[ https://issues.apache.org/jira/browse/MNG-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810376#comment-16810376 ] Hudson commented on MNG-6559: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Mailing list URL is incorrect in CONTRIBUTING.md > > > Key: MNG-6559 > URL: https://issues.apache.org/jira/browse/MNG-6559 > Project: Maven > Issue Type: Bug > Components: Documentation: General >Reporter: John Lin >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > The mailing list URL in CONTRIBUTING.md is currently > [https://maven.apache.org/mail-lists.html], but it should have been > [https://maven.apache.org/mailing-lists.html]. > Besides, I also found that problem in > [https://github.com/apache/maven/tree/master/apache-maven|https://github.com/apache/maven/tree/master/apache-maven]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6597) add input location tracking for plugins configuration
[ https://issues.apache.org/jira/browse/MNG-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810389#comment-16810389 ] Hudson commented on MNG-6597: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > add input location tracking for plugins configuration > - > > Key: MNG-6597 > URL: https://issues.apache.org/jira/browse/MNG-6597 > Project: Maven > Issue Type: Improvement > Components: Inheritance and Interpolation >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 3.6.1 > > > while working on input location display in verbose help:effedctive-pom (see > MPH-160), I found that input location was not tracked for plugins > configuration, ie XPP3 DOM > neet to add this tracking, which requires: > # a newer plexus-utils 3.2.0 version for > [https://github.com/codehaus-plexus/plexus-utils/issues/61] > # a newer Modello 1.10.0 version for > [https://github.com/codehaus-plexus/modello/issues/29] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6548) Lifecycle plugin version upgrades
[ https://issues.apache.org/jira/browse/MNG-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810386#comment-16810386 ] Hudson commented on MNG-6548: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Lifecycle plugin version upgrades > - > > Key: MNG-6548 > URL: https://issues.apache.org/jira/browse/MNG-6548 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.7.0-candidate > > > Regular plugin upgrades to absorb changes if plugin version is not specified > in the client POM. > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/lifecycles.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6601) add input location tracking for site's reportPlugins injected by reports conversion
[ https://issues.apache.org/jira/browse/MNG-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810390#comment-16810390 ] Hudson commented on MNG-6601: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > add input location tracking for site's reportPlugins injected by reports > conversion > --- > > Key: MNG-6601 > URL: https://issues.apache.org/jira/browse/MNG-6601 > Project: Maven > Issue Type: Improvement > Components: Inheritance and Interpolation >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 3.6.1 > > > working on MPH-160 > there is no explanation for site's reportPlugins injected by [reports > conversion to decoupled site > plugin|https://maven.apache.org/ref/3.6.0/maven-model-builder/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6599) unknown version in model id when version is defined from parent
[
https://issues.apache.org/jira/browse/MNG-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810387#comment-16810387
]
Hudson commented on MNG-6599:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> unknown version in model id when version is defined from parent
> ---
>
> Key: MNG-6599
> URL: https://issues.apache.org/jira/browse/MNG-6599
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.6.0
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.6.1
>
>
> working on MPH-160 limitation
> bq. parent POM version is not recognized, leading to suboptimal output ""
> if we look at this pom:
> {code:xml}
>
> org.apache.maven
> maven-parent
> 33
>
> org.apache.maven.plugins
> maven-plugins
> pom
> ...{code}
> the fact that version is not defined as project.version but should be
> extrapolated from project.parent.version seems to cause the issue in model id
> calculation for input source tracking
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6506) Mojos are unable to load package annotations on Java >= 9
[
https://issues.apache.org/jira/browse/MNG-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810393#comment-16810393
]
Hudson commented on MNG-6506:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Mojos are unable to load package annotations on Java >= 9
> -
>
> Key: MNG-6506
> URL: https://issues.apache.org/jira/browse/MNG-6506
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.6.0
>Reporter: Andreas Veithen
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Labels: up-for-grabs
> Fix For: 3.6.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On Java 9 and above, calls to {{java.lang.Package.getAnnotation(Class)}} from
> within a Mojo always return {{null}} (unless the {{package-info}} class has
> been loaded by some other means before).
> The reason appears to be an incompatibility between Java 9 and Plexus
> Classworlds:
> * Java 9 ultimately calls {{findClass}} (instead of {{loadClass}}) to get the
> {{package-info}} class.
> * The {{findClass}} implementation in {{ClassRealm}} always throws
> {{ClassNotFoundException}}:
> https://github.com/codehaus-plexus/plexus-classworlds/blob/master/src/main/java/org/codehaus/plexus/classworlds/realm/ClassRealm.java#L275.
> This in particular affects plugins that interact with the JAXB API because it
> relies on package annotations.
> A workaround is to preload the required {{package-info}} classes using
> {{loadClass}}; see e.g. http://svn.apache.org/viewvc?rev=1845026&view=rev.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6611) Update animal-sniffer-maven-plugin to 1.17
[ https://issues.apache.org/jira/browse/MNG-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810395#comment-16810395 ] Hudson commented on MNG-6611: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Update animal-sniffer-maven-plugin to 1.17 > -- > > Key: MNG-6611 > URL: https://issues.apache.org/jira/browse/MNG-6611 > Project: Maven > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.6.1 > > Attachments: MNG-6611-stacktrace.txt > > Time Spent: 20m > Remaining Estimate: 0h > > Update animal-sniffer-maven-plugin from 1.15 to version 1.17 to get support > for use [multi-release jar|http://openjdk.java.net/jeps/238] that was > introduced in 1.16 > https://github.com/mojohaus/animal-sniffer/milestone/2?closed=1 > will permit to use MR jars as dependency to Maven's Core - like slf4j > 1.8.0-beta4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6591) Upgrade to Wagon 3.3.2
[ https://issues.apache.org/jira/browse/MNG-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810383#comment-16810383 ] Hudson commented on MNG-6591: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Upgrade to Wagon 3.3.2 > -- > > Key: MNG-6591 > URL: https://issues.apache.org/jira/browse/MNG-6591 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Version 3.3.1 contains a regression which needed to be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6600) add input location tracking for default lifecycle bindings executions
[ https://issues.apache.org/jira/browse/MNG-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810388#comment-16810388 ] Hudson commented on MNG-6600: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > add input location tracking for default lifecycle bindings executions > - > > Key: MNG-6600 > URL: https://issues.apache.org/jira/browse/MNG-6600 > Project: Maven > Issue Type: Improvement > Components: Inheritance and Interpolation >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 3.6.1 > > > working on MPH-160 > default lifecycle bindings injections adds executions with "default-" > id, but does not add any input location tracking > adding > "org.apache.maven:maven-core::default-lifecycle-bindings" > modelId will ease understanding where this comes from -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6538) Upgrade Maven Artifact Resolver to 1.3.3 to restore API
[ https://issues.apache.org/jira/browse/MNG-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810392#comment-16810392 ] Hudson commented on MNG-6538: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Upgrade Maven Artifact Resolver to 1.3.3 to restore API > --- > > Key: MNG-6538 > URL: https://issues.apache.org/jira/browse/MNG-6538 > Project: Maven > Issue Type: Task > Components: Embedding >Affects Versions: 3.6.0 >Reporter: Hervé Boutemy >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.6.1 > > > IntelliJ IDEA Maven integration was broken by API removal done in MRESOLVER-36 > the missing API was added back (with empty implementation) in MRESOLVER-64 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6530) Regression in ProjectBuilder when file change between invocations (introduced by MNG-6311)
[ https://issues.apache.org/jira/browse/MNG-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810374#comment-16810374 ] Hudson commented on MNG-6530: - Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/ > Regression in ProjectBuilder when file change between invocations (introduced > by MNG-6311) > -- > > Key: MNG-6530 > URL: https://issues.apache.org/jira/browse/MNG-6530 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.6.0 >Reporter: Mickael Istria >Assignee: Michael Osipov >Priority: Critical > Fix For: 3.6.1 > > Time Spent: 10m > Remaining Estimate: 0h > > The patch for MNG-6311 introduces a regression in ProjectBuilder due to > missing cache invalidation when content change. > It was identified as a potential issue by [~fbricon] on Oct 10, yet no > further investigation happened and Maven 3.6.0 was released with this > regression. > This regression prevents Eclipse m2e (and probably most APIs using the > ProjectBuilder for a longer session which allows pom.xml files to be > modified) from adopting 3.6.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6256) Maven script can break if "-f" path contains special characters
[
https://issues.apache.org/jira/browse/MNG-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810375#comment-16810375
]
Hudson commented on MNG-6256:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #12
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/12/
> Maven script can break if "-f" path contains special characters
>
>
> Key: MNG-6256
> URL: https://issues.apache.org/jira/browse/MNG-6256
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 10 with PowerShell
>Reporter: Christoph Etzel
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.6.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Executing maven on Windows using the {{\-f}} or {{--file}} parameter to
> specify an alternate POM file can break the script if the path contains
> special characters.
> It was originally discovered on a Windows Jenkins instance with working
> directory located under C:\Program Files (x86)\Jenkins..
> Example:
> {code:java}mvn -f "folderWithClosing)Bracket/pomFolder"{code}
> Command line output: {{"Bracket/pomFolder" kann syntaktisch an dieser Stelle
> nicht verarbeitet werden.}}
> Just for fun: Starting calc from maven script using {{\-f}}
> {code:java}mvn -f " ' & start calc"{code}
> Command line output: {{POM file '}} and a new calculator process
> The bug was introduced with commit
> https://github.com/apache/maven/commit/f8ab2a650f32d5d87126d341d9bbfccbf99fd0ca
> for issue MNG-5889.
> Workaround: Use maven 3.3.9 or below
> Possible fix: Escape {{%FILE_ARG%}} and {{%POM_DIR%}} with {{"}} in {{echo}}
> commands in {{maven.cmd}} (line 120 and 129).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6255) Maven script cannot parse jvm.config with CRLF
[
https://issues.apache.org/jira/browse/MNG-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810362#comment-16810362
]
Hudson commented on MNG-6255:
-
Build succeeded in Jenkins: Maven TLP » maven » slf4j-1.8-modules #7
See https://builds.apache.org/job/maven-box/job/maven/job/slf4j-1.8-modules/7/
> Maven script cannot parse jvm.config with CRLF
> --
>
> Key: MNG-6255
> URL: https://issues.apache.org/jira/browse/MNG-6255
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 7 with MINGW64 environment via Git for Windows
> 0.1.1 including GNU coreutils and bash 4.4.12
>Reporter: Andrew Kennedy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.5.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A project with a {{.mvn/jvm.config}} file that has *CRLF* line endings will
> not parse it correctly. The script uses the {{tr}} command to change *LF* to
> space, but this leaves *CR* behind. For example, with the {{jvm.config}} file
> containing the text {{-Xmx1024m -Xms512m}} followed by *CRLF*, the following
> error message is printed:
> {code}
> $ mvn install
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Invalid initial heap size: -Xms512m
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DOXIA-590) either provided element class or default class gets ignored.
Fred Eckertson created DOXIA-590: Summary: either provided element class or default class gets ignored. Key: DOXIA-590 URL: https://issues.apache.org/jira/browse/DOXIA-590 Project: Maven Doxia Issue Type: Bug Components: Core Affects Versions: 1.8 Reporter: Fred Eckertson The following construct is somewhat common in doxia-core att.addAttribute( Attribute.CLASS, "a" ); The documentation says that basic attributes (including CLASS) are supported. However in cases like this either that "a" or the CLASS that was provided in the attributes parameter will be ignored. The correct way to do this is to append the provided CLASS to "a " if a CLASS attribute was provided. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-dependency-plugin] apolopeix commented on issue #8: [MDEP-613] - Fixes bug Analyze failed: Unsupported class file major version 55 (Java 11)
apolopeix commented on issue #8: [MDEP-613] - Fixes bug Analyze failed: Unsupported class file major version 55 (Java 11) URL: https://github.com/apache/maven-dependency-plugin/pull/8#issuecomment-480063939 When do you guys plan to have a new release that includes those changes? I see the changes in master, but the latest tag 3.1.1 does not include those changes. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [Created] (DOXIA-589) Impossible to assign attributes with tableRow
Fred Eckertson created DOXIA-589: Summary: Impossible to assign attributes with tableRow Key: DOXIA-589 URL: https://issues.apache.org/jira/browse/DOXIA-589 Project: Maven Doxia Issue Type: Bug Components: Core Affects Versions: 1.8 Reporter: Fred Eckertson writeStartTag(HtmlMarkup.TR, att) does not get called when tableRow(SinkEventAttributes) is invoked. It only gets called if tableRow() is used and that is because tableRow() calls tableRows(null, false). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-316) Explicit minijar includes
[ https://issues.apache.org/jira/browse/MSHADE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810254#comment-16810254 ] Markus Karg commented on MSHADE-316: [~rfscholte] Shall I provide a PR for that? For which solution, "explicit minijar exceptions" or "useDefaultIncludes=true"? Both solve the same problem, but have different side aspects (positive and negative). > Explicit minijar includes > - > > Key: MSHADE-316 > URL: https://issues.apache.org/jira/browse/MSHADE-316 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Markus Karg >Priority: Major > > Minijar currently respects includes, but these have a drawback: Once you > defined an include, the _default includes_ are gone! But what you actually > want to have when combining minijar with includes is just an "exception" to > minijar's filtering, not a complete replacement of the default includes! > So what we need to make this work intuitively is either "explicit minijar > exceptions", or a "useDefaultIncludes=true" option that turns the notion from > "replace default includes by the single given include" to "add the single > given include ontop of the default includes". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHADE-316) Explicit minijar includes
Markus Karg created MSHADE-316: -- Summary: Explicit minijar includes Key: MSHADE-316 URL: https://issues.apache.org/jira/browse/MSHADE-316 Project: Maven Shade Plugin Issue Type: Improvement Reporter: Markus Karg Minijar currently respects includes, but these have a drawback: Once you defined an include, the _default includes_ are gone! But what you actually want to have when combining minijar with includes is just an "exception" to minijar's filtering, not a complete replacement of the default includes! So what we need to make this work intuitively is either "explicit minijar exceptions", or a "useDefaultIncludes=true" option that turns the notion from "replace default includes by the single given include" to "add the single given include ontop of the default includes". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (MSHADE-308) Support SPI pluggability for ResourceTranformers and Filters
[ https://issues.apache.org/jira/browse/MSHADE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Karg updated MSHADE-308: --- Comment: was deleted (was: Maybe it would be a good idea to actually *not* provide a new goal, but instead have a different *Shader* strategy. This sounds most intuitive: What you actually want to reach is *not* that another goal is reached -- you still want to *shade* stuff. But you want to use a different *strategy* when shading: A JPMS strategy. So my advice would be: Keep the goal, but change the shader.) > Support SPI pluggability for ResourceTranformers and Filters > > > Key: MSHADE-308 > URL: https://issues.apache.org/jira/browse/MSHADE-308 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: Romain Manni-Bucau >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-308) Support SPI pluggability for ResourceTranformers and Filters
[ https://issues.apache.org/jira/browse/MSHADE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810240#comment-16810240 ] Markus Karg commented on MSHADE-308: [~romain.manni-bucau] Yes, wrong ticket, thanks for the pointer. > Support SPI pluggability for ResourceTranformers and Filters > > > Key: MSHADE-308 > URL: https://issues.apache.org/jira/browse/MSHADE-308 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: Romain Manni-Bucau >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MSHADE-315) Broken link on Maven Shade Plugin
[ https://issues.apache.org/jira/browse/MSHADE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MSHADE-315: -- Assignee: Karl Heinz Marbaise > Broken link on Maven Shade Plugin > - > > Key: MSHADE-315 > URL: https://issues.apache.org/jira/browse/MSHADE-315 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Vinicius Scheidegger >Assignee: Karl Heinz Marbaise >Priority: Trivial > Labels: broken-link > Fix For: 3.2.2 > > > The links to the mailing list and mailing list archive are broken > Where: [https://maven.apache.org/plugins/maven-shade-plugin/] > Page it is currently pointing to: > [https://maven.apache.org/plugins/maven-shade-plugin/mail-lists.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-262) Add jpms goal
[ https://issues.apache.org/jira/browse/MSHADE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810237#comment-16810237 ] Markus Karg commented on MSHADE-262: Maybe it would be a good idea to actually *not* provide a new goal, but instead have a different *Shader* strategy. This sounds most intuitive: What you actually want to reach is *not* that another goal is reached – you still want to *shade* stuff. But you want to use a different *strategy* when shading: A JPMS strategy. So my advice would be: Keep the goal, but change the shader. > Add jpms goal > - > > Key: MSHADE-262 > URL: https://issues.apache.org/jira/browse/MSHADE-262 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > > With Java 9 we get module descriptors for strong encapsulation and reliable > configuration. > When shading we should not merge or ignore these descriptors. > In case of an application we should think of the way spring boot works, i.e. > bundle the jars in a jar and provide a new classloader. This is the only way > to preserve the strong encapsulation right now. > After a talk with [~pwebb] and [~dblevins] we came to the conclusion that it > should NOT be combined with the current shade goal. First idea was to make a > new plugin, but after some rethinking I'd prefer to just make a separate goal > for it in this shade-plugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MSHADE-315) Broken link on Maven Shade Plugin
[ https://issues.apache.org/jira/browse/MSHADE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810232#comment-16810232 ] Karl Heinz Marbaise edited comment on MSHADE-315 at 4/4/19 7:59 PM: Moved this issue to the correct location. was (Author: khmarbaise): Move this issue to the correct location. > Broken link on Maven Shade Plugin > - > > Key: MSHADE-315 > URL: https://issues.apache.org/jira/browse/MSHADE-315 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Vinicius Scheidegger >Priority: Trivial > Labels: broken-link > Fix For: 3.2.2 > > > The links to the mailing list and mailing list archive are broken > Where: [https://maven.apache.org/plugins/maven-shade-plugin/] > Page it is currently pointing to: > [https://maven.apache.org/plugins/maven-shade-plugin/mail-lists.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHADE-315) Broken link on Maven Shade Plugin
[ https://issues.apache.org/jira/browse/MSHADE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-315: --- Priority: Trivial (was: Minor) > Broken link on Maven Shade Plugin > - > > Key: MSHADE-315 > URL: https://issues.apache.org/jira/browse/MSHADE-315 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Vinicius Scheidegger >Priority: Trivial > Labels: broken-link > Fix For: 3.2.2 > > > The links to the mailing list and mailing list archive are broken > Where: [https://maven.apache.org/plugins/maven-shade-plugin/] > Page it is currently pointing to: > [https://maven.apache.org/plugins/maven-shade-plugin/mail-lists.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHADE-315) Broken link on Maven Shade Plugin
[ https://issues.apache.org/jira/browse/MSHADE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-315: --- Fix Version/s: 3.2.2 > Broken link on Maven Shade Plugin > - > > Key: MSHADE-315 > URL: https://issues.apache.org/jira/browse/MSHADE-315 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Vinicius Scheidegger >Priority: Minor > Labels: broken-link > Fix For: 3.2.2 > > > The links to the mailing list and mailing list archive are broken > Where: [https://maven.apache.org/plugins/maven-shade-plugin/] > Page it is currently pointing to: > [https://maven.apache.org/plugins/maven-shade-plugin/mail-lists.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-315) Broken link on Maven Shade Plugin
[ https://issues.apache.org/jira/browse/MSHADE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810232#comment-16810232 ] Karl Heinz Marbaise commented on MSHADE-315: Move this issue to the correct location. > Broken link on Maven Shade Plugin > - > > Key: MSHADE-315 > URL: https://issues.apache.org/jira/browse/MSHADE-315 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Vinicius Scheidegger >Priority: Minor > Labels: broken-link > > The links to the mailing list and mailing list archive are broken > Where: [https://maven.apache.org/plugins/maven-shade-plugin/] > Page it is currently pointing to: > [https://maven.apache.org/plugins/maven-shade-plugin/mail-lists.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Moved] (MSHADE-315) Broken link on Maven Shade Plugin
[ https://issues.apache.org/jira/browse/MSHADE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise moved MNGSITE-359 to MSHADE-315: Key: MSHADE-315 (was: MNGSITE-359) Project: Maven Shade Plugin (was: Maven Project Web Site) > Broken link on Maven Shade Plugin > - > > Key: MSHADE-315 > URL: https://issues.apache.org/jira/browse/MSHADE-315 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Vinicius Scheidegger >Priority: Minor > Labels: broken-link > > The links to the mailing list and mailing list archive are broken > Where: [https://maven.apache.org/plugins/maven-shade-plugin/] > Page it is currently pointing to: > [https://maven.apache.org/plugins/maven-shade-plugin/mail-lists.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-308) Support SPI pluggability for ResourceTranformers and Filters
[ https://issues.apache.org/jira/browse/MSHADE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810228#comment-16810228 ] Romain Manni-Bucau commented on MSHADE-308: --- [~mkarg] bad ticket? > Support SPI pluggability for ResourceTranformers and Filters > > > Key: MSHADE-308 > URL: https://issues.apache.org/jira/browse/MSHADE-308 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: Romain Manni-Bucau >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-365) EOL page surprisingly links to current M3 plugins
[
https://issues.apache.org/jira/browse/MNGSITE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810225#comment-16810225
]
Karl Heinz Marbaise commented on MNGSITE-365:
-
Hi, so are talking about this page: https://maven.apache.org/maven-2.x-eol.html
?
> EOL page surprisingly links to current M3 plugins
> -
>
> Key: MNGSITE-365
> URL: https://issues.apache.org/jira/browse/MNGSITE-365
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Paul Benedict
>Assignee: Paul Benedict
>Priority: Trivial
>
> The EOL page has links on "Plugin" and "Version" columns. The former links to
> the current plugin sites; the second links to the last M2 versions,
> respectively.
> An unsuspecting user (like me!) was clicking through the "Plugin" column, and
> didn't realize it was the current documentation. This is a small usability
> issue, but one I believe should be fixed. I am supporting ancient M2 stuff so
> I come to the page often. The links are too good of a trap.
> Recommendation:
> # Set the "Plugin" links to their EOL versions.
> # Amend the "Plugin" values to include the V of the GAV (to make explicit
> the connection between the two columns). Example: {{clean:2.6.1}}
> # Remove the "Version" links.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPMD-278) pmd-plugin 3.11.0 fails in multi module release builds
[
https://issues.apache.org/jira/browse/MPMD-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810168#comment-16810168
]
Andreas Dangel commented on MPMD-278:
-
I think, that problem is the one mentioned at MPMD-277.
Do you use the aggregate=true parameter?
This will make pmd execute on the reactor root before all the modules are
compiled, which is problematic. The bug MPMD-277 will be fixed, to not try to
load the modules artifacts from the repository in that case. But if the modules
are not compiled before, PMD's results might not be accurate (e.g. it could
find more false positives).
> pmd-plugin 3.11.0 fails in multi module release builds
> --
>
> Key: MPMD-278
> URL: https://issues.apache.org/jira/browse/MPMD-278
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.11.0
>Reporter: Andreas Müller
>Priority: Major
>
> When using maven-pmd-plugin 3.11.0 the pmd plugin fails in release builds of
> multi module maven projects:
> {noformat}[INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd (pmd) on project xxx:
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd
> failed:
> org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException:
> Could not find artifact xxx:jar: in maven repository> -> [Help 1]
> {noformat}
> or
> {noformat}[INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd (pmd) on project xxx:
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd
> failed:
> rg.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException:
> Failure to find xxx:jar: in repository> was cached in the local repository,
> resolution will not be reattempted until the update interval of
> has elapsed or updates are forced -> [Help 1]{noformat}
> Normal build are working fine.
> I guess the problem is that the plugin is looking for the released version in
> the remote repository before it's actually transferred after the successful
> release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPMD-273) Dependency jar with rules fails only with SNAPSHOT version
[
https://issues.apache.org/jira/browse/MPMD-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810161#comment-16810161
]
Andreas Dangel commented on MPMD-273:
-
Hi [~leemeador],
does it work now, if you specify the pluginRepositories?
> Dependency jar with rules fails only with SNAPSHOT version
> --
>
> Key: MPMD-273
> URL: https://issues.apache.org/jira/browse/MPMD-273
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.10.0
> Environment: Jenkins scripted build job calls Maven running on RHEL 7
> Linux build agents controlled by Jenkins 2.73. Java 8.
>Reporter: Lee Meador
>Priority: Major
>
> One build job creates a coding-standards jar containing PMD rulesets and I
> have run that build with and without SNAPSHOT for version 0.0.2. If I go to
> my Nexus GUI and search, I see the 0.0.2 version and about 8 SNAPSHOT
> versions with different dates and times. 0.0.2 is in the releases repo and
> 0.0.2-SNAPSHOT(s) are in the snapshots repo.
> I have settings.xml set to point to our the public Nexus 3 repository which
> proxies to Maven Central and several other repos both open source and
> internal to our company. The releases repo is included in public. The
> snapshot repo is not included in public, this proxy repo.
> This is the mirrorOf tag in settings.xml.
> {{ !nexus-snapshots,*}}
> For another build job, I have a tag in the pom pointing to our
> snapshot repo with snapshot enabled and releases NOT enabled. This tag is
> there to give it an id that works with the mirroring:
> {{ nexus-snapshots}}
> Other snapshot versions of things needed when compiling the code are found by
> maven.
> I configure the maven pmd plugin thusly:
> {quote}{{}}
> {{ org.apache.maven.plugins}}
> {{ maven-pmd-plugin}}
> {{ }}
> {{ }}
> {{ }}
> {{ check}}
> {{ }}
> {{ }}
> {{ }}
> {{ }}
> {{ utf-8}}
> {{ 100}}
> {{ 1.8}}
> {{ 3}}
> {{ true}}
> {{ }}
> {{ pmd-config2.xml}}
> {{ }}
> {{ }}
> {{ }}
> {{ }}
> {{ com.aa.crewtech.tools}}
> {{ coding-standards}}
> {{ ${coding-standards.version}}}
> {{ }}
> {{ }}
> {{ }}{quote}
> If I run my build and the property coding-standards.version has the value
> 0.0.2 everything works.
> If coding-standards.version has the value 0.0.2-SNAPSHOT it fails with this
> error:
> _ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project
> SqlTool: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: Plugin
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0 or one of its dependencies
> could not be resolved: Could not find artifact
> com.my.company:coding-standards:jar:0.0.2-SNAPSHOT in nexus
> ([https://nexusread.mycompany.com/repository/public/|https://nexusread.aa.com/repository/OT-public/])
> -> [Help 1]_
> All these builds actually run in my Jenkins with all the code under source
> control and its all repeatable. SNAPSHOT version for the ruleset jar fails.
> Non-SNAPSHOT version works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPMD-276) DOC of excludeFromFailureFile for cpd-check is wrong
[ https://issues.apache.org/jira/browse/MPMD-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-276: Component/s: CPD > DOC of excludeFromFailureFile for cpd-check is wrong > > > Key: MPMD-276 > URL: https://issues.apache.org/jira/browse/MPMD-276 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Reporter: Albert Motos González >Priority: Major > > Hi, > > How you can see on your page: > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/violation-exclusions.html] > for exclude failureFiles in cpd-check the example is > exclude-cpd.properties. After a lot of hours of test, looking the source of > original pmd plugin code: > [https://github.com/sturton/maven-pmd-plugin/blob/master/src/test/resources/unit/excludes/cpd_exclude.txt] > you can see that file must be of type txt. > > The change of wiki is cosmetic but I loose a lot of time trying it, and it's > frustrating. And it help a lot of developers > > Thanks in advance, > > > exclude-cpd.properties -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-pmd-plugin] adangel commented on issue #7: [MPMD-279] Improve documentation of maxAllowedViolations
adangel commented on issue #7: [MPMD-279] Improve documentation of maxAllowedViolations URL: https://github.com/apache/maven-pmd-plugin/pull/7#issuecomment-47644 @jbennett2091 I've updated the descriptions. Preview is available here: http://chunk.io/adangel/f7e190fce5e342b6971a7cdb1639a7f5/maven-pmd-plugin/index.html This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-shade-plugin] mkarg commented on issue #17: [MSHADE-313] - Keep Services
mkarg commented on issue #17: [MSHADE-313] - Keep Services URL: https://github.com/apache/maven-shade-plugin/pull/17#issuecomment-479997909 > A little bit of patient, I only have 1 set of hands. Really? How old school. You should apply for a second set. ;-) This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (MSHADE-308) Support SPI pluggability for ResourceTranformers and Filters
[ https://issues.apache.org/jira/browse/MSHADE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810141#comment-16810141 ] Markus Karg commented on MSHADE-308: Maybe it would be a good idea to actually *not* provide a new goal, but instead have a different *Shader* strategy. This sounds most intuitive: What you actually want to reach is *not* that another goal is reached -- you still want to *shade* stuff. But you want to use a different *strategy* when shading: A JPMS strategy. So my advice would be: Keep the goal, but change the shader. > Support SPI pluggability for ResourceTranformers and Filters > > > Key: MSHADE-308 > URL: https://issues.apache.org/jira/browse/MSHADE-308 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: Romain Manni-Bucau >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-shade-plugin] rfscholte commented on issue #17: [MSHADE-313] - Keep Services
rfscholte commented on issue #17: [MSHADE-313] - Keep Services URL: https://github.com/apache/maven-shade-plugin/pull/17#issuecomment-479991973 A little bit of patient, I only have 1 set of hands. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-pmd-plugin] adangel commented on issue #7: [MPMD-279] Improve documentation of maxAllowedViolations
adangel commented on issue #7: [MPMD-279] Improve documentation of maxAllowedViolations URL: https://github.com/apache/maven-pmd-plugin/pull/7#issuecomment-479990460 @jbennett2091 Thanks for your comment. I was struggling with the term "issues", since PMD only reports violations (rule violations to be specific). That's why I felt introducing a new generic term does not help but add to the confusion...but I get your point. In short: * Violations: PMD reports violations. * Each violation has a priority (1 - high, 2 - medium-high, 3 - medium, 4 - medium-low, 5 - low). * Failures: These are violations, with a high enough priority, that we fail the build. * Warnings: These are violations, that won't fail the build. By default, the plugin fails the build for any violation (all violations are failures). "failurePriority" configures, which violations are failures and which violations are warnings. "maxAllowedViolations" controls, how many failures are needed to fail the build. It turns out, that the property "maxAllowedViolations" should have been named actually "maxAllowedFailures", since it only checks the failure count. I'll try to rephrase the documention with that terminologoy... This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-shade-plugin] mkarg commented on issue #17: [MSHADE-313] - Keep Services
mkarg commented on issue #17: [MSHADE-313] - Keep Services URL: https://github.com/apache/maven-shade-plugin/pull/17#issuecomment-479987061 How to go on? This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [Updated] (MPMD-277) Plugin tries to download local submodules from repo
[ https://issues.apache.org/jira/browse/MPMD-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-277: Summary: Plugin tries to download local submodules from repo (was: plugin tries to download local submodules from repo) > Plugin tries to download local submodules from repo > --- > > Key: MPMD-277 > URL: https://issues.apache.org/jira/browse/MPMD-277 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 3.11.0 >Reporter: Sylvain >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.12.0 > > > My bug seems kinda related to #MPMD-273, but 3.10.0 works for me, not 3.11.0. > > I'm trying to build a multi-module maven project with OpenJDK11 and Maven > 3.5.4. > The project works fine with maven-pmd-plugin 3.10.0, but with 3.11.0, I get > this error: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd (pmd) on project parent: > Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd > failed: org.apache.maven.reporting.MavenReportException: > org.eclipse.aether.resolution.DependencyResolutionException: Could not find > artifact com.incepto.cloud:api-common:jar:0.0.1-SNAPSHOT in spring-repo > (https://repo.spring.io/release) -> [Help 1] > > pmd-plugin doesn't have a dependency on api-common, it's the first submodule > maven tries to build. The problem doesn't occur if I skip pmd first and let > maven install the submodules in the local repo, then re-run the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-279) Improve documentation of maxAllowedViolations
[ https://issues.apache.org/jira/browse/MPMD-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810048#comment-16810048 ] Jeffrey Bennett commented on MPMD-279: -- I threw a comment onto the pull request > Improve documentation of maxAllowedViolations > - > > Key: MPMD-279 > URL: https://issues.apache.org/jira/browse/MPMD-279 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 3.11.0 >Reporter: Jeffrey Bennett >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.12.0 > > Attachments: build-snippet.txt > > Time Spent: 10m > Remaining Estimate: 0h > > Specified failurePriority=5 and failOnViolation=true. For code with > violations, expected 'mvn clean verify' to result in BUILD FAILED, but got > BUILD SUCCESS instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809988#comment-16809988
]
Robert Scholte commented on MNG-6609:
-
* {{true}} means it is inherited by all
* {{false}} means it is inherited by none (only
effective on current pom)
* {{jar}} would mean it is only inherited by projects
with packaging:jar. This will be a responsibility of Maven and requires an
explicit version. Once implemented and you're trying to run thi with an older
version of Maven, it'll complain for an invalid value for inherited.
regarding the docs, the idea is documented somewhere, I would expected this
(huge) page, but I might be wrong.
> Profile activation by packaging
>
>
> Key: MNG-6609
> URL: https://issues.apache.org/jira/browse/MNG-6609
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 3.6.0
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to the lack of mixins, it is common that modules which use different
> packagings share the same parent pom. As those often use different
> dependencies/plugins, it would be nice to have profiles which are activated
> based on the packaging of a module. That is currently not possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MNG-6625) Maven 3.6.0 - throws exception of configuration while trying to build
[
https://issues.apache.org/jira/browse/MNG-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-6625.
---
Resolution: Invalid
Assignee: Robert Scholte
This is not a Maven issue, but an issue with
org.codehaus.mojo:findbugs-maven-plugin:3.0.0
For some reason it contains an invalid mojo descriptor (
{{/META-INF/maven/plugin.xml}} ).
You need to figure out if it is only a problem in your local repository, or if
the jar in Maven central has the same issue. For the latter you need to contact
the mojohaus team.
> Maven 3.6.0 - throws exception of configuration while trying to build
> -
>
> Key: MNG-6625
> URL: https://issues.apache.org/jira/browse/MNG-6625
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build, Deployment
>Affects Versions: 3.6.0
>Reporter: Vipin VijayKumar
>Assignee: Robert Scholte
>Priority: Blocker
>
> reactor: Unable to parse configuration of mojo
> org.codehaus.mojo:findbugs-maven-plugin:3.0.0:findbugs for parameter
> pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with
> value '$æplugin.artifactså' of type
> java.util.Collections.UnmodifiableRandomAccessList to property of type
> java.util.ArrayList
>
> The project builds successfully with lower version of mavens
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-314) Should warn (and fix) breaking signed JARs
[ https://issues.apache.org/jira/browse/MSHADE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809925#comment-16809925 ] Markus Karg commented on MSHADE-314: [~rfscholte] Shall I provide a PR for this? > Should warn (and fix) breaking signed JARs > -- > > Key: MSHADE-314 > URL: https://issues.apache.org/jira/browse/MSHADE-314 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.2.1 >Reporter: Markus Karg >Priority: Major > > Pulling content from signed JARs into uber-jar results in non-executable > outcome, as the signing information included is invalid within the new JAR. > The solution must be to strip the signing information, and prompt a clear > warning about breaking the signing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHADE-314) Should warn (and fix) breaking signed JARs
Markus Karg created MSHADE-314: -- Summary: Should warn (and fix) breaking signed JARs Key: MSHADE-314 URL: https://issues.apache.org/jira/browse/MSHADE-314 Project: Maven Shade Plugin Issue Type: Improvement Affects Versions: 3.2.1 Reporter: Markus Karg Pulling content from signed JARs into uber-jar results in non-executable outcome, as the signing information included is invalid within the new JAR. The solution must be to strip the signing information, and prompt a clear warning about breaking the signing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #11: [MCHECKSTYLE-54] Add integration test
eolivelli commented on issue #11: [MCHECKSTYLE-54] Add integration test URL: https://github.com/apache/maven-checkstyle-plugin/pull/11#issuecomment-479859210 I will commit as soon as this job is green https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-54-integration-tests/ This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #10: [MCHECKSTYLE-163] Add integration test
eolivelli commented on issue #10: [MCHECKSTYLE-163] Add integration test URL: https://github.com/apache/maven-checkstyle-plugin/pull/10#issuecomment-479858898 @zregvart I will commit as soon as this job is green https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-163-integration-tests/ This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies
eolivelli commented on issue #5: [MCHECKSTYLE-353] - Don't resolve any dependencies URL: https://github.com/apache/maven-checkstyle-plugin/pull/5#issuecomment-479856730 @zregvart I am going to cut a release soon. Please make your tests. I will be happy to fix your problem with the upcoming release This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (SCM-889) Jazz tag command creates snapshot in wrong workspace
[ https://issues.apache.org/jira/browse/SCM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809700#comment-16809700 ] Chris Graham commented on SCM-889: -- What this issue boils down to is this: Should the tag implementation use what is defined in the pom, or what is currently on-disk, checkedout? I've written it based on what is in the pom (which is how I thought that the other providers did it). This issue provides a fix for the latter. How have the other providers handled this? [~olamy], [~rfscholte] [~hboutemy] Thoughts on how this issue should be resolved? > Jazz tag command creates snapshot in wrong workspace > > > Key: SCM-889 > URL: https://issues.apache.org/jira/browse/SCM-889 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jazz >Affects Versions: 1.9.5, 1.10.0 >Reporter: Sérgio Ozaki >Assignee: Chris Graham >Priority: Major > Fix For: 1.11.1 > > > Jazz provider tag command uses the jazz workspace set int the pom.xml scm > tag. When in other jazz workspace, the snapshot is not created based on the > current work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6625) Maven 3.6.0 - throws exception of configuration while trying to build
Vipin VijayKumar created MNG-6625: - Summary: Maven 3.6.0 - throws exception of configuration while trying to build Key: MNG-6625 URL: https://issues.apache.org/jira/browse/MNG-6625 Project: Maven Issue Type: Bug Components: Bootstrap & Build, Deployment Affects Versions: 3.6.0 Reporter: Vipin VijayKumar reactor: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:3.0.0:findbugs for parameter pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with value '$æplugin.artifactså' of type java.util.Collections.UnmodifiableRandomAccessList to property of type java.util.ArrayList The project builds successfully with lower version of mavens -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6609) Profile activation by packaging
[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809573#comment-16809573
]
Konrad Windszus commented on MNG-6609:
--
[~rfscholte] Thanks for your input, but I haven't really understood how you can
use {{inherited}} to only inherit to modules of a specific packaging but not to
the other. Setting {{jar}} on the common parent pom is
clear, but how do I make sure that those plugin settings are really used by
"jar" packaging only?
Also in
https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0 I
haven't found this mentioned...
> Profile activation by packaging
>
>
> Key: MNG-6609
> URL: https://issues.apache.org/jira/browse/MNG-6609
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 3.6.0
>Reporter: Konrad Windszus
>Priority: Major
>
> Due to the lack of mixins, it is common that modules which use different
> packagings share the same parent pom. As those often use different
> dependencies/plugins, it would be nice to have profiles which are activated
> based on the packaging of a module. That is currently not possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
