[jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[ https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758255#comment-15758255 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #49 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/49/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 06580630a3b09143770fd8eeda6c86f70a016f4d) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java > Maven plugins and core extensions are not dependencies, they should be > resolved the same way as projects. > - > > Key: MNG-6135 > URL: https://issues.apache.org/jira/browse/MNG-6135 > Project: Maven > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > can you explain the logic, please? > I don't understand why "they should be resolved the same way as project", > what it really means and what impact it has: I just see that everything is > currently failing: it's a mess!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[ https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758251#comment-15758251 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1459 (See [https://builds.apache.org/job/maven-3.x/1459/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 06580630a3b09143770fd8eeda6c86f70a016f4d) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java > Maven plugins and core extensions are not dependencies, they should be > resolved the same way as projects. > - > > Key: MNG-6135 > URL: https://issues.apache.org/jira/browse/MNG-6135 > Project: Maven > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > can you explain the logic, please? > I don't understand why "they should be resolved the same way as project", > what it really means and what impact it has: I just see that everything is > currently failing: it's a mess!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[ https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758163#comment-15758163 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #48 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/48/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev bbffde98fdf3c46d7698c300ca074ed980fa921e) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java > Maven plugins and core extensions are not dependencies, they should be > resolved the same way as projects. > - > > Key: MNG-6135 > URL: https://issues.apache.org/jira/browse/MNG-6135 > Project: Maven > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > can you explain the logic, please? > I don't understand why "they should be resolved the same way as project", > what it really means and what impact it has: I just see that everything is > currently failing: it's a mess!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[ https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758160#comment-15758160 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1457 (See [https://builds.apache.org/job/maven-3.x/1457/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev bbffde98fdf3c46d7698c300ca074ed980fa921e) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java > Maven plugins and core extensions are not dependencies, they should be > resolved the same way as projects. > - > > Key: MNG-6135 > URL: https://issues.apache.org/jira/browse/MNG-6135 > Project: Maven > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > can you explain the logic, please? > I don't understand why "they should be resolved the same way as project", > what it really means and what impact it has: I just see that everything is > currently failing: it's a mess!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[ https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758103#comment-15758103 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x #1456 (See [https://builds.apache.org/job/maven-3.x/1456/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 80f2fd6375ad5311031929c1bbaf87aa42a3c53a) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 286c7ffba1696053274c5da6cad4336f678fceee) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java > Maven plugins and core extensions are not dependencies, they should be > resolved the same way as projects. > - > > Key: MNG-6135 > URL: https://issues.apache.org/jira/browse/MNG-6135 > Project: Maven > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > can you explain the logic, please? > I don't understand why "they should be resolved the same way as project", > what it really means and what impact it has: I just see that everything is > currently failing: it's a mess!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5457) Show repository id when downloading or uploading from/to a remote repository
[
https://issues.apache.org/jira/browse/MNG-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758102#comment-15758102
]
Hudson commented on MNG-5457:
-
SUCCESS: Integrated in Jenkins build maven-3.x #1456 (See
[https://builds.apache.org/job/maven-3.x/1456/])
Revert "[MNG-5457] Show repository id when downloading or uploading (schulte:
rev 2385484a813edc157ba151c9daa0625eaf8902f9)
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/AbstractMavenTransferListener.java
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/Slf4jMavenTransferListener.java
[MNG-5457] Show repository id when downloading or uploading from/to a (schulte:
rev ff5d215b54cb9a77e3742dc5dd05865dec08795b)
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/Slf4jMavenTransferListener.java
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/AbstractMavenTransferListener.java
> Show repository id when downloading or uploading from/to a remote repository
>
>
> Key: MNG-5457
> URL: https://issues.apache.org/jira/browse/MNG-5457
> Project: Maven
> Issue Type: Improvement
> Components: General
>Affects Versions: 3.0.5
>Reporter: Hervé Boutemy
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
> Attachments: 2016-05-18_204749.png
>
>
> currently, the log only show the url being downloaded:
> {noformat}Downloading:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
> nothing is told about the repository id.
> But as shown in MNG-5181, repository id is an important information since it
> is stored in local repository to limit artifact scope: it would be useful
> IMHO to display the id in the output, like
> {noformat}Downloading from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5457) Show repository id when downloading or uploading from/to a remote repository
[
https://issues.apache.org/jira/browse/MNG-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758097#comment-15758097
]
Hudson commented on MNG-5457:
-
SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #47 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/47/])
Revert "[MNG-5457] Show repository id when downloading or uploading (schulte:
rev 2385484a813edc157ba151c9daa0625eaf8902f9)
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/AbstractMavenTransferListener.java
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/Slf4jMavenTransferListener.java
[MNG-5457] Show repository id when downloading or uploading from/to a (schulte:
rev ff5d215b54cb9a77e3742dc5dd05865dec08795b)
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/Slf4jMavenTransferListener.java
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/AbstractMavenTransferListener.java
> Show repository id when downloading or uploading from/to a remote repository
>
>
> Key: MNG-5457
> URL: https://issues.apache.org/jira/browse/MNG-5457
> Project: Maven
> Issue Type: Improvement
> Components: General
>Affects Versions: 3.0.5
>Reporter: Hervé Boutemy
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
> Attachments: 2016-05-18_204749.png
>
>
> currently, the log only show the url being downloaded:
> {noformat}Downloading:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
> nothing is told about the repository id.
> But as shown in MNG-5181, repository id is an important information since it
> is stored in local repository to limit artifact scope: it would be useful
> IMHO to display the id in the output, like
> {noformat}Downloading from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[ https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758099#comment-15758099 ] Hudson commented on MNG-6135: - SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #47 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/47/]) [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 80f2fd6375ad5311031929c1bbaf87aa42a3c53a) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java [MNG-6135] Maven plugins and core extensions are not dependencies, they (schulte: rev 286c7ffba1696053274c5da6cad4336f678fceee) * (edit) maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java > Maven plugins and core extensions are not dependencies, they should be > resolved the same way as projects. > - > > Key: MNG-6135 > URL: https://issues.apache.org/jira/browse/MNG-6135 > Project: Maven > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > can you explain the logic, please? > I don't understand why "they should be resolved the same way as project", > what it really means and what impact it has: I just see that everything is > currently failing: it's a mess!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-5986) XML validators flag errors on poms that declare plugin configurations using the 'combine.self' attribute because the maven-4.0.0 XSD does not declare this attribute.
[
https://issues.apache.org/jira/browse/MNG-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757944#comment-15757944
]
Michael Osipov edited comment on MNG-5986 at 12/18/16 1:10 AM:
---
The fix won't work because the schema is generated by Plexus Modello. See
https://codehaus-plexus.github.io/modello/modello.html and {{maven.mdo}} in the
Maven Git repo.
was (Author: michael-o):
The fix won't work because the schema is generated by Plexus Modello.
> XML validators flag errors on poms that declare plugin configurations using
> the 'combine.self' attribute because the maven-4.0.0 XSD does not declare
> this attribute.
> -
>
> Key: MNG-5986
> URL: https://issues.apache.org/jira/browse/MNG-5986
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.3.3
> Environment: All
>Reporter: Ben Tels
>Priority: Minor
>
> Maven recognizes an attribute 'combine.self' on the 'configuration' element
> within plugin declarations within a POM ('configuration' elements within and
> outside 'execution' elements). However, an XML validator flags use of this
> attribute as an error. Which is correct, because published XSD
> http://maven.apache.org/xsd/maven-4.0.0.xsd does not declare 'combine.self'
> as an attribute of 'configuration'.
> Current declaration of the configuration element:
>
>
> 4.0.0
> The configuration of the
> reporting plugin.
>
>
>
> processContents="skip"/>
>
>
>
> Simple fix:
>
>
> 0.0.0+
>
>
>
> processContents="skip"/>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5986) XML validators flag errors on poms that declare plugin configurations using the 'combine.self' attribute because the maven-4.0.0 XSD does not declare this attribute.
[
https://issues.apache.org/jira/browse/MNG-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757944#comment-15757944
]
Michael Osipov commented on MNG-5986:
-
The fix won't work because the schema is generated by Plexus Modello.
> XML validators flag errors on poms that declare plugin configurations using
> the 'combine.self' attribute because the maven-4.0.0 XSD does not declare
> this attribute.
> -
>
> Key: MNG-5986
> URL: https://issues.apache.org/jira/browse/MNG-5986
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.3.3
> Environment: All
>Reporter: Ben Tels
>Priority: Minor
>
> Maven recognizes an attribute 'combine.self' on the 'configuration' element
> within plugin declarations within a POM ('configuration' elements within and
> outside 'execution' elements). However, an XML validator flags use of this
> attribute as an error. Which is correct, because published XSD
> http://maven.apache.org/xsd/maven-4.0.0.xsd does not declare 'combine.self'
> as an attribute of 'configuration'.
> Current declaration of the configuration element:
>
>
> 4.0.0
> The configuration of the
> reporting plugin.
>
>
>
> processContents="skip"/>
>
>
>
> Simple fix:
>
>
> 0.0.0+
>
>
>
> processContents="skip"/>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPOM-156) Upgrade archetyp-packaging extension to 3.4.
[ https://issues.apache.org/jira/browse/MPOM-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757929#comment-15757929 ] Hudson commented on MPOM-156: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-156] Upgrade archetyp-packaging extension to 3.4. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774834]) * (edit) maven-archetype-bundles/pom.xml > Upgrade archetyp-packaging extension to 3.4. > > > Key: MPOM-156 > URL: https://issues.apache.org/jira/browse/MPOM-156 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-151) Upgrade modello-maven-plugin to 1.8.3.
[ https://issues.apache.org/jira/browse/MPOM-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757937#comment-15757937 ] Hudson commented on MPOM-151: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-151] Upgrade modello-maven-plugin to 1.8.3. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774829]) * (edit) pom.xml > Upgrade modello-maven-plugin to 1.8.3. > -- > > Key: MPOM-151 > URL: https://issues.apache.org/jira/browse/MPOM-151 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-153) Upgrade maven-pmd-plugin to 3.7.
[ https://issues.apache.org/jira/browse/MPOM-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757935#comment-15757935 ] Hudson commented on MPOM-153: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-153] Upgrade maven-pmd-plugin to 3.7.. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774831]) * (edit) pom.xml > Upgrade maven-pmd-plugin to 3.7. > > > Key: MPOM-153 > URL: https://issues.apache.org/jira/browse/MPOM-153 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-157) Upgrade maven-shared-resources to 2.
[ https://issues.apache.org/jira/browse/MPOM-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757930#comment-15757930 ] Hudson commented on MPOM-157: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-157] Upgrade maven-shared-resources to 2. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774836]) * (edit) maven-plugins/pom.xml > Upgrade maven-shared-resources to 2. > > > Key: MPOM-157 > URL: https://issues.apache.org/jira/browse/MPOM-157 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHARED-603) Upgrade maven-shared-resources to 2.
[ https://issues.apache.org/jira/browse/MSHARED-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757932#comment-15757932 ] Hudson commented on MSHARED-603: FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MSHARED-603] Upgrade maven-shared-resources to 2. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774837]) * (edit) maven-shared-components/pom.xml > Upgrade maven-shared-resources to 2. > > > Key: MSHARED-603 > URL: https://issues.apache.org/jira/browse/MSHARED-603 > Project: Maven Shared Components > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-154) Upgrade findbugs-maven-plugin to 3.0.4.
[ https://issues.apache.org/jira/browse/MPOM-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757931#comment-15757931 ] Hudson commented on MPOM-154: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-154] Upgrade findbugs-maven-plugin to 3.0.4. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774832]) * (edit) pom.xml > Upgrade findbugs-maven-plugin to 3.0.4. > --- > > Key: MPOM-154 > URL: https://issues.apache.org/jira/browse/MPOM-154 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-152) Upgrade maven-checkstyle-plugin to 2.17.
[ https://issues.apache.org/jira/browse/MPOM-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757934#comment-15757934 ] Hudson commented on MPOM-152: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-152] Upgrade maven-checkstyle-plugin to 2.17. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774830]) * (edit) pom.xml > Upgrade maven-checkstyle-plugin to 2.17. > > > Key: MPOM-152 > URL: https://issues.apache.org/jira/browse/MPOM-152 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-150) Upgrade plexus to 1.7.1.
[ https://issues.apache.org/jira/browse/MPOM-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757936#comment-15757936 ] Hudson commented on MPOM-150: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-150] Upgrade plexus to 1.7.1. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774828]) * (edit) pom.xml [MPOM-150] Upgrade plexus to 1.7.1. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774827]) * (edit) pom.xml > Upgrade plexus to 1.7.1. > > > Key: MPOM-150 > URL: https://issues.apache.org/jira/browse/MPOM-150 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-155) Upgrade maven-changes-plugin to 2.12.1.
[ https://issues.apache.org/jira/browse/MPOM-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757933#comment-15757933 ] Hudson commented on MPOM-155: - FAILURE: Integrated in Jenkins build maven-parent #2061 (See [https://builds.apache.org/job/maven-parent/2061/]) [MPOM-155] Upgrade maven-changes-plugin to 2.12.1. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774833]) * (edit) pom.xml > Upgrade maven-changes-plugin to 2.12.1. > --- > > Key: MPOM-155 > URL: https://issues.apache.org/jira/browse/MPOM-155 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-147) Upgrade maven-war-plugin to 3.0.0.
[ https://issues.apache.org/jira/browse/MPOM-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757889#comment-15757889 ] Hudson commented on MPOM-147: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-147] Upgrade maven-war-plugin to 3.0.0. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774823]) * (edit) pom.xml > Upgrade maven-war-plugin to 3.0.0. > -- > > Key: MPOM-147 > URL: https://issues.apache.org/jira/browse/MPOM-147 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-145) Upgrade maven-plugin-plugin to 3.5.
[ https://issues.apache.org/jira/browse/MPOM-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757891#comment-15757891 ] Hudson commented on MPOM-145: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-145] Upgrade maven-plugin-plugin to 3.5. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774821]) * (edit) pom.xml > Upgrade maven-plugin-plugin to 3.5. > --- > > Key: MPOM-145 > URL: https://issues.apache.org/jira/browse/MPOM-145 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-141) Upgrade maven-assembly-plugin to 3.0.0.
[ https://issues.apache.org/jira/browse/MPOM-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757895#comment-15757895 ] Hudson commented on MPOM-141: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-141] Upgrade maven-assembly-plugin to 3.0.0. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774816]) * (edit) pom.xml > Upgrade maven-assembly-plugin to 3.0.0. > --- > > Key: MPOM-141 > URL: https://issues.apache.org/jira/browse/MPOM-141 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-142) Upgrade maven-compiler-plugin to 3.6.0.
[ https://issues.apache.org/jira/browse/MPOM-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757896#comment-15757896 ] Hudson commented on MPOM-142: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-142] Upgrade maven-compiler-plugin to 3.6.0. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774817]) * (edit) pom.xml > Upgrade maven-compiler-plugin to 3.6.0. > --- > > Key: MPOM-142 > URL: https://issues.apache.org/jira/browse/MPOM-142 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-146) Upgrade maven-resources-plugin to 3.0.2.
[ https://issues.apache.org/jira/browse/MPOM-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757892#comment-15757892 ] Hudson commented on MPOM-146: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-146] Upgrade maven-resources-plugin to 3.0.2. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774822]) * (edit) pom.xml > Upgrade maven-resources-plugin to 3.0.2. > > > Key: MPOM-146 > URL: https://issues.apache.org/jira/browse/MPOM-146 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-143) Upgrade maven-dependency-plugin to 3.0.0.
[ https://issues.apache.org/jira/browse/MPOM-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757893#comment-15757893 ] Hudson commented on MPOM-143: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-143] Upgrade maven-dependency-plugin to 3.0.0. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774818]) * (edit) pom.xml > Upgrade maven-dependency-plugin to 3.0.0. > - > > Key: MPOM-143 > URL: https://issues.apache.org/jira/browse/MPOM-143 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-148) Upgrade clirr-maven-plugin to 2.8.
[ https://issues.apache.org/jira/browse/MPOM-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757890#comment-15757890 ] Hudson commented on MPOM-148: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-148] Upgrade clirr-maven-plugin to 2.8. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774824]) * (edit) pom.xml > Upgrade clirr-maven-plugin to 2.8. > -- > > Key: MPOM-148 > URL: https://issues.apache.org/jira/browse/MPOM-148 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-144) Upgrade maven-javadoc-plugin to 2.10.4.
[ https://issues.apache.org/jira/browse/MPOM-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757894#comment-15757894 ] Hudson commented on MPOM-144: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #159 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/159/]) [MPOM-144] Upgrade maven-javadoc-plugin to 2.10.4. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774819]) * (edit) pom.xml > Upgrade maven-javadoc-plugin to 2.10.4. > --- > > Key: MPOM-144 > URL: https://issues.apache.org/jira/browse/MPOM-144 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-6095) mvn script warns on Solaris
[
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6095.
---
Resolution: Fixed
No reaction, fixed according to Christian.
> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Assignee: Christian Schulte
>Priority: Minor
> Labels: solaris
> Fix For: 3.4.0
>
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation SunOS 5.11 11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local:
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local:
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6095) mvn script warns on Solaris
[
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6095:
Fix Version/s: 3.4.0
> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Assignee: Christian Schulte
>Priority: Minor
> Labels: solaris
> Fix For: 3.4.0
>
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation SunOS 5.11 11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local:
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local:
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6095) mvn script warns on Solaris
[
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6095:
Assignee: Christian Schulte
> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Assignee: Christian Schulte
>Priority: Minor
> Labels: solaris
> Fix For: 3.4.0
>
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation SunOS 5.11 11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local:
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local:
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6128) JAVA_HOME resolution not working on IBM i under PASE
[
https://issues.apache.org/jira/browse/MNG-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6128:
Labels: AS/400 IBM-i close-pending iseries (was: AS/400 IBM-i iseries)
> JAVA_HOME resolution not working on IBM i under PASE
>
>
> Key: MNG-6128
> URL: https://issues.apache.org/jira/browse/MNG-6128
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.9
>Reporter: Tim
>Priority: Minor
> Labels: AS/400, IBM-i, close-pending, iseries
>
> Running the "mvn" command on an IBM i (aka AS/400, iseries or system i)
> machine in the PASE (UNIX Bourne-like shell) environment without having first
> set JAVA_HOME results in the following error:
> {code}
> 001-0050 Syntaxfehler bei Zeile 144: Token "!" nicht erwartet.
> {code}
> (Syntax failure on line 144: Token ! unexpected)
> I was able to prevent the error by changing this line in the mvn shell script:
> {code} if [ -n "$javaExecutable" ] && ! [ "`expr \"$javaExecutable\" : '\([^
> ]*\)'`" = "no" ]; then{code}
> to
> {code} if [ -n "$javaExecutable" ] && ["`expr \"$javaExecutable\" : '\([^
> ]*\)'`" != "no" ]; then{code}
> The automatic JAVA_HOME resolution fails on IBM i anyway due to the specific
> location of the JVM on this platform, I could probably suggest a way to fix
> it if anyone's interested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (WAGON-421) "Not authorized" when deploying artifact following HTTP redirect
[
https://issues.apache.org/jira/browse/WAGON-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated WAGON-421:
-
Fix Version/s: 2.6
> "Not authorized" when deploying artifact following HTTP redirect
>
>
> Key: WAGON-421
> URL: https://issues.apache.org/jira/browse/WAGON-421
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.4, 2.5, 2.6, 2.7
> Environment: Maven 3.0.4+
>Reporter: Bruno Medeiros
>Assignee: Robert Scholte
>Priority: Critical
> Fix For: 2.6
>
>
> I always deployed artifacts to my repository without problems, until last
> week when I was forced to migrate my repository to a different URL. I still
> have control of the old domain, so I set a redirect in Apache on the old
> domain, like this:
> bq. Redirect permanent /maven2 http://newsubdomain.company.com/maven2
> Deploys works perfect with the old URL for maven 2.2.1 and 3.0.3, but all
> maven 3.0.4+ are broken (even 3.1.1 and 3.2.3). Here follows my test:
> #> ~/apache-maven-3.2.3/bin/mvn -X deploy
> error (full stacktrace):
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project jcompany_flex_util: Failed to retrieve remote metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml: Could
> not transfer metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml from/to
> company-repo (http://dev.company.com.br:80/maven2/libs-snapshots-local): Not
> authorized , ReasonPhrase:Unauthorized. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project jcompany_flex_util: Failed to retrieve remote
> metadata br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml:
> Could not transfer metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml from/to
> company-repo (http://dev.company.com.br:80/maven2/libs-snapshots-local): Not
> authorized , ReasonPhrase:Unauthorized.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to retrieve
> remote metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml: Could
> not transfer metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml from/to
> company-repo (http://dev.company.com.br:80/maven2/libs-snapshots-local): Not
> authorized , ReasonPhrase:Unauthorized.
> at
> org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:284)
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:169)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: org.apache.maven.artifa
[jira] [Closed] (WAGON-421) "Not authorized" when deploying artifact following HTTP redirect
[
https://issues.apache.org/jira/browse/WAGON-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-421.
> "Not authorized" when deploying artifact following HTTP redirect
>
>
> Key: WAGON-421
> URL: https://issues.apache.org/jira/browse/WAGON-421
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.4, 2.5, 2.6, 2.7
> Environment: Maven 3.0.4+
>Reporter: Bruno Medeiros
>Assignee: Robert Scholte
>Priority: Critical
> Fix For: 2.6
>
>
> I always deployed artifacts to my repository without problems, until last
> week when I was forced to migrate my repository to a different URL. I still
> have control of the old domain, so I set a redirect in Apache on the old
> domain, like this:
> bq. Redirect permanent /maven2 http://newsubdomain.company.com/maven2
> Deploys works perfect with the old URL for maven 2.2.1 and 3.0.3, but all
> maven 3.0.4+ are broken (even 3.1.1 and 3.2.3). Here follows my test:
> #> ~/apache-maven-3.2.3/bin/mvn -X deploy
> error (full stacktrace):
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project jcompany_flex_util: Failed to retrieve remote metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml: Could
> not transfer metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml from/to
> company-repo (http://dev.company.com.br:80/maven2/libs-snapshots-local): Not
> authorized , ReasonPhrase:Unauthorized. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project jcompany_flex_util: Failed to retrieve remote
> metadata br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml:
> Could not transfer metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml from/to
> company-repo (http://dev.company.com.br:80/maven2/libs-snapshots-local): Not
> authorized , ReasonPhrase:Unauthorized.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to retrieve
> remote metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml: Could
> not transfer metadata
> br.com.company:jcompany_flex_util:0.4.0-SNAPSHOT/maven-metadata.xml from/to
> company-repo (http://dev.company.com.br:80/maven2/libs-snapshots-local): Not
> authorized , ReasonPhrase:Unauthorized.
> at
> org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:284)
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:169)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeplo
[jira] [Closed] (MNG-5460) Transitive dependency with variable scope
[
https://issues.apache.org/jira/browse/MNG-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5460.
---
Resolution: Cannot Reproduce
Cannot reproduce with recent Maven version:
{noformat}
$ /d/Entwicklung/Programme/apache-maven-3.3.9/bin/mvn -V dependency:tree
-Pmyprofile
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.3.9
Java version: 1.8.0_112, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_112\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] myProject
[INFO] modA
[INFO] modB
[INFO] modC
[INFO]
[INFO]
[INFO] Building myProject 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ myProject ---
[INFO] com.mycompany.app:myProject:pom:1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] Building modA 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ modA ---
[INFO] com.mycompany.app:modA:jar:1.0-SNAPSHOT
[INFO] \- junit:junit:jar:4.11:test
[INFO]\- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO]
[INFO]
[INFO] Building modB 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ modB ---
[INFO] com.mycompany.app:modB:jar:1.0-SNAPSHOT
[INFO] +- com.mycompany.app:modA:jar:1.0-SNAPSHOT:provided
[INFO] \- junit:junit:jar:4.11:test
[INFO]\- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO]
[INFO]
[INFO] Building modC 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ modC ---
[INFO] com.mycompany.app:modC:jar:1.0-SNAPSHOT
[INFO] +- com.mycompany.app:modB:jar:1.0-SNAPSHOT:compile
[INFO] \- junit:junit:jar:4.11:test
[INFO]\- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] myProject .. SUCCESS [ 0.538 s]
[INFO] modA ... SUCCESS [ 0.024 s]
[INFO] modB ... SUCCESS [ 0.012 s]
[INFO] modC ... SUCCESS [ 0.005 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.767 s
[INFO] Finished at: 2016-12-18T01:30:14+01:00
[INFO] Final Memory: 12M/241M
[INFO]
{noformat}
> Transitive dependency with variable scope
> --
>
> Key: MNG-5460
> URL: https://issues.apache.org/jira/browse/MNG-5460
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.0
> Environment: Windows xp
>Reporter: Continuus Auchan
> Attachments: myproject.zip
>
>
> We have a bad transitivity resolution when using variable scopes in our
> project hierarchy on maven 3.
> The same test on maven 2 gives us a correct behavior.
> I've got a pom parent project with 3 modules.
> In the parent pom I define :
> -a property "myscope" with value "compile"
> -a profile "myprofile" with a property "myscope" with value "provided"
> The moduleA depends on nothing
> The moduleB depends on moduleA with scope equals to myscope
> The moduleC depends on moduleB with scope equals provided
> When I enter the command "mvn dependency:tree -P myprofile" I've got
> {quote}
> --- maven-dependency-plugin:2.1:tree (default-cli) @ modB ---
> com.mycompany.app:modB:jar:1.0-SNAPSHOT
> \- com.mycompany.app:modA:jar:1.0-SNAPSHOT:provided
> {quote}
> which is OK, but I also have
> {quote}
> --- maven-dependency-plugin:2.1:tree (default-cli) @ modC ---
> com.mycompany.app:modC:jar:1.0-SNAPSHOT
> \- com.mycompany.app:modB:jar:1.0-SNAPSHOT:compile
> \- com.mycompany.app:modA:jar:1.0-SNAPSHOT:compile
> {quote}
> where i do not excpect modA to appear.
> You 'll find in attachment the sample project.
> Not
[jira] [Created] (MSHARED-603) Upgrade maven-shared-resources to 2.
Christian Schulte created MSHARED-603: - Summary: Upgrade maven-shared-resources to 2. Key: MSHARED-603 URL: https://issues.apache.org/jira/browse/MSHARED-603 Project: Maven Shared Components Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-157) Upgrade maven-shared-resources to 2.
[ https://issues.apache.org/jira/browse/MPOM-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-157. -- Resolution: Fixed Fix Version/s: MAVEN-31 > Upgrade maven-shared-resources to 2. > > > Key: MPOM-157 > URL: https://issues.apache.org/jira/browse/MPOM-157 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-157) Upgrade maven-shared-resources to 2.
Christian Schulte created MPOM-157: -- Summary: Upgrade maven-shared-resources to 2. Key: MPOM-157 URL: https://issues.apache.org/jira/browse/MPOM-157 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-5708) Maven dependency resolution inconsistent with multiple excludes
[
https://issues.apache.org/jira/browse/MNG-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5708.
---
Resolution: Fixed
This issue has been resolved implicitly by the numerous dependency resolution
improvements performed by [~schulte77].
Maven 3.3.9:
{noformat}
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.3.9
Java version: 1.8.0_112, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_112\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building proj3 1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ proj3 ---
[INFO] Deleting D:\Entwicklung\Projekte\dependency-bug-3.tar\proj3\target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ proj3 ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\dependency-bug-3.tar\proj3\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ proj3 ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
proj3 ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\dependency-bug-3.tar\proj3\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ proj3
---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ proj3 ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ proj3 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar:
D:\Entwicklung\Projekte\dependency-bug-3.tar\proj3\target\proj3-1-SNAPSHOT.jar
[INFO]
[INFO] --- maven-duplicate-finder-plugin:1.0.9:check (default) @ proj3 ---
[INFO] Checking compile classpath
[WARNING] Found duplicate and different classes in
[log4j:log4j:1.2.7,org.slf4j:log4j-over-slf4j:1.7.7] :
[WARNING] org.apache.log4j.Appender
[WARNING] org.apache.log4j.AppenderSkeleton
[WARNING] org.apache.log4j.BasicConfigurator
[WARNING] org.apache.log4j.Category
[WARNING] org.apache.log4j.ConsoleAppender
[WARNING] org.apache.log4j.FileAppender
[WARNING] org.apache.log4j.Layout
[WARNING] org.apache.log4j.Level
[WARNING] org.apache.log4j.LogManager
[WARNING] org.apache.log4j.Logger
[WARNING] org.apache.log4j.MDC
[WARNING] org.apache.log4j.NDC
[WARNING] org.apache.log4j.PatternLayout
[WARNING] org.apache.log4j.Priority
[WARNING] org.apache.log4j.PropertyConfigurator
[WARNING] org.apache.log4j.RollingFileAppender
[WARNING] org.apache.log4j.SimpleLayout
[WARNING] org.apache.log4j.WriterAppender
[WARNING] org.apache.log4j.helpers.LogLog
[WARNING] org.apache.log4j.helpers.NullEnumeration
[WARNING] org.apache.log4j.spi.Configurator
[WARNING] org.apache.log4j.spi.ErrorHandler
[WARNING] org.apache.log4j.spi.Filter
[WARNING] org.apache.log4j.spi.HierarchyEventListener
[WARNING] org.apache.log4j.spi.LoggerFactory
[WARNING] org.apache.log4j.spi.LoggerRepository
[WARNING] org.apache.log4j.spi.LoggingEvent
[WARNING] org.apache.log4j.spi.OptionHandler
[WARNING] org.apache.log4j.xml.DOMConfigurator
[INFO] Checking runtime classpath
[WARNING] Found duplicate and different classes in
[log4j:log4j:1.2.7,org.slf4j:log4j-over-slf4j:1.7.7] :
[WARNING] org.apache.log4j.Appender
[WARNING] org.apache.log4j.AppenderSkeleton
[WARNING] org.apache.log4j.BasicConfigurator
[WARNING] org.apache.log4j.Category
[WARNING] org.apache.log4j.ConsoleAppender
[WARNING] org.apache.log4j.FileAppender
[WARNING] org.apache.log4j.Layout
[WARNING] org.apache.log4j.Level
[WARNING] org.apache.log4j.LogManager
[WARNING] org.apache.log4j.Logger
[WARNING] org.apache.log4j.MDC
[WARNING] org.apache.log4j.NDC
[WARNING] org.apache.log4j.PatternLayout
[WARNING] org.apache.log4j.Priority
[WARNING] org.apache.log4j.PropertyConfigurator
[WARNING] org.apache.log4j.RollingFileAppender
[WARNING] org.apache.log4j.SimpleLayout
[WARNING] org.apache.log4j.WriterAppender
[WARNING] org.apache.log4j.helpers.LogLog
[WARNING] org.apache.log4j.helpers.NullEnumeration
[WARNING] org.apache.log4j.spi.Configurator
[WARNING] org.apache.log4j.spi.ErrorHandler
[WARNING] org.apache.log4j.spi.Filter
[WARNING] org.apache.log4j.spi.HierarchyEventListener
[WARNING] org.apache.log4j.spi.LoggerF
[jira] [Created] (MARCHETYPES-48) Upgrade archetyp-packaging extension to 3.4.
Christian Schulte created MARCHETYPES-48: Summary: Upgrade archetyp-packaging extension to 3.4. Key: MARCHETYPES-48 URL: https://issues.apache.org/jira/browse/MARCHETYPES-48 Project: Maven Archetype Bundles Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-5708) Maven dependency resolution inconsistent with multiple excludes
[ https://issues.apache.org/jira/browse/MNG-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5708: Fix Version/s: 3.4.0 > Maven dependency resolution inconsistent with multiple excludes > --- > > Key: MNG-5708 > URL: https://issues.apache.org/jira/browse/MNG-5708 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.2.3 > Environment: Apache Maven 3.2.3 > (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T13:58:10-07:00) > Maven home: /home/henning/.apache-maven > Java version: 1.7.0_67, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-1.7.0-sun-1.7.0.67/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.16.6-200.fc20.x86_64", arch: "amd64", family: > "unix" >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov > Fix For: 3.4.0 > > Attachments: dependency-bug-2.tar.gz, dependency-bug-3.tar.gz, > dependency-bug.tar.gz > > > This is how to reproduce the problem: > download and unpack the attached tarball. It contains three projects: > proj1 depends on log4j and commons-lang3 > proj2 is a multi module project which uses proj1. But it uses slf4j, so for > proj1 it has an exclusion in the dependency management section which excludes > log4j > module1 depends on proj1 and log4j-over-slf4j > module2 depends on proj1 > proj3 is a project that depends on module1. > enter each project one-by-one and do "mvn clean install". This works fine. So > dependency exclusion etc. works. > Now, remove the comments from the exclude block in proj2/module2/pom.xml > run "mvn clean install" in proj2. Everything still builds fine in proj2. > Same goes for "mvn clean install -pl :module2" (only build module2) and "mvn > clean install -rf :module2" (resume from module2) > now go to proj3. The build fails because there are duplicates on the > classpath. Looking at the dependency tree: > [INFO] group:proj3:jar:1-SNAPSHOT > [INFO] \- group:module1:jar:1-SNAPSHOT:compile > [INFO]+- group:proj1:jar:1-SNAPSHOT:compile > [INFO]| \- log4j:log4j:jar:1.2.7:compile > [INFO]\- org.slf4j:log4j-over-slf4j:jar:1.7.7:compile > [INFO] \- org.slf4j:slf4j-api:jar:1.7.7:compile > log4j (which was excluded in the dependencyManagement section) has reappeared! > This only happens if there are excludes in the depMgt section of a parent pom > *and* excludes in the dependency itself in a child project *and* the > dependency is referred from outside the multi module project. For an in-tree > project (such as module2), everything is fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-156) Upgrade archetyp-packaging extension to 3.4.
[ https://issues.apache.org/jira/browse/MPOM-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-156. -- Resolution: Won't Fix > Upgrade archetyp-packaging extension to 3.4. > > > Key: MPOM-156 > URL: https://issues.apache.org/jira/browse/MPOM-156 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MNG-5708) Maven dependency resolution inconsistent with multiple excludes
[ https://issues.apache.org/jira/browse/MNG-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-5708: --- Assignee: Michael Osipov > Maven dependency resolution inconsistent with multiple excludes > --- > > Key: MNG-5708 > URL: https://issues.apache.org/jira/browse/MNG-5708 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.2.3 > Environment: Apache Maven 3.2.3 > (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T13:58:10-07:00) > Maven home: /home/henning/.apache-maven > Java version: 1.7.0_67, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-1.7.0-sun-1.7.0.67/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.16.6-200.fc20.x86_64", arch: "amd64", family: > "unix" >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov > Attachments: dependency-bug-2.tar.gz, dependency-bug-3.tar.gz, > dependency-bug.tar.gz > > > This is how to reproduce the problem: > download and unpack the attached tarball. It contains three projects: > proj1 depends on log4j and commons-lang3 > proj2 is a multi module project which uses proj1. But it uses slf4j, so for > proj1 it has an exclusion in the dependency management section which excludes > log4j > module1 depends on proj1 and log4j-over-slf4j > module2 depends on proj1 > proj3 is a project that depends on module1. > enter each project one-by-one and do "mvn clean install". This works fine. So > dependency exclusion etc. works. > Now, remove the comments from the exclude block in proj2/module2/pom.xml > run "mvn clean install" in proj2. Everything still builds fine in proj2. > Same goes for "mvn clean install -pl :module2" (only build module2) and "mvn > clean install -rf :module2" (resume from module2) > now go to proj3. The build fails because there are duplicates on the > classpath. Looking at the dependency tree: > [INFO] group:proj3:jar:1-SNAPSHOT > [INFO] \- group:module1:jar:1-SNAPSHOT:compile > [INFO]+- group:proj1:jar:1-SNAPSHOT:compile > [INFO]| \- log4j:log4j:jar:1.2.7:compile > [INFO]\- org.slf4j:log4j-over-slf4j:jar:1.7.7:compile > [INFO] \- org.slf4j:slf4j-api:jar:1.7.7:compile > log4j (which was excluded in the dependencyManagement section) has reappeared! > This only happens if there are excludes in the depMgt section of a parent pom > *and* excludes in the dependency itself in a child project *and* the > dependency is referred from outside the multi module project. For an in-tree > project (such as module2), everything is fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Created] (MPOM-152) Upgrade maven-checkstyle-plugin to 2.17.
There might be a corner-case here. I remember an issue about this upgrade, a dependency onmaven-shared-resourcesneeded to be added: https://issues.apache.org/jira/browse/MCHECKSTYLE-327?focusedCommentId=15383006&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15383006 Le 18/12/2016 à 01:09, Christian Schulte (JIRA) a écrit : Christian Schulte created MPOM-152: -- Summary: Upgrade maven-checkstyle-plugin to 2.17. Key: MPOM-152 URL: https://issues.apache.org/jira/browse/MPOM-152 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332) --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus
[jira] [Created] (MPOM-156) Upgrade archetyp-packaging extension to 3.4.
Christian Schulte created MPOM-156: -- Summary: Upgrade archetyp-packaging extension to 3.4. Key: MPOM-156 URL: https://issues.apache.org/jira/browse/MPOM-156 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-155) Upgrade maven-changes-plugin to 2.12.1.
[ https://issues.apache.org/jira/browse/MPOM-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-155. -- Resolution: Fixed Fix Version/s: MAVEN-31 > Upgrade maven-changes-plugin to 2.12.1. > --- > > Key: MPOM-155 > URL: https://issues.apache.org/jira/browse/MPOM-155 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-155) Upgrade maven-changes-plugin to 2.12.1.
Christian Schulte created MPOM-155: -- Summary: Upgrade maven-changes-plugin to 2.12.1. Key: MPOM-155 URL: https://issues.apache.org/jira/browse/MPOM-155 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-154) Upgrade findbugs-maven-plugin to 3.0.4.
[ https://issues.apache.org/jira/browse/MPOM-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-154. -- Resolution: Fixed Assignee: Christian Schulte Fix Version/s: MAVEN-31 > Upgrade findbugs-maven-plugin to 3.0.4. > --- > > Key: MPOM-154 > URL: https://issues.apache.org/jira/browse/MPOM-154 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-154) Upgrade findbugs-maven-plugin to 3.0.4.
Christian Schulte created MPOM-154: -- Summary: Upgrade findbugs-maven-plugin to 3.0.4. Key: MPOM-154 URL: https://issues.apache.org/jira/browse/MPOM-154 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-153) Upgrade maven-pmd-plugin to 3.7.
[ https://issues.apache.org/jira/browse/MPOM-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-153. -- Resolution: Fixed Fix Version/s: MAVEN-31 > Upgrade maven-pmd-plugin to 3.7. > > > Key: MPOM-153 > URL: https://issues.apache.org/jira/browse/MPOM-153 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-153) Upgrade maven-pmd-plugin to 3.7.
Christian Schulte created MPOM-153: -- Summary: Upgrade maven-pmd-plugin to 3.7. Key: MPOM-153 URL: https://issues.apache.org/jira/browse/MPOM-153 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-152) Upgrade maven-checkstyle-plugin to 2.17.
Christian Schulte created MPOM-152: -- Summary: Upgrade maven-checkstyle-plugin to 2.17. Key: MPOM-152 URL: https://issues.apache.org/jira/browse/MPOM-152 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-152) Upgrade maven-checkstyle-plugin to 2.17.
[ https://issues.apache.org/jira/browse/MPOM-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-152. -- Resolution: Fixed Fix Version/s: MAVEN-31 > Upgrade maven-checkstyle-plugin to 2.17. > > > Key: MPOM-152 > URL: https://issues.apache.org/jira/browse/MPOM-152 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-149) Upgrade plugin tools to 3.5.
[ https://issues.apache.org/jira/browse/MPOM-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757846#comment-15757846 ] Hudson commented on MPOM-149: - FAILURE: Integrated in Jenkins build maven-parent #2060 (See [https://builds.apache.org/job/maven-parent/2060/]) [MPOM-149] Upgrade plugin tools to 3.5. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1774826]) * (edit) pom.xml > Upgrade plugin tools to 3.5. > > > Key: MPOM-149 > URL: https://issues.apache.org/jira/browse/MPOM-149 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-151) Upgrade modello-maven-plugin to 1.8.3.
[ https://issues.apache.org/jira/browse/MPOM-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-151. -- Resolution: Fixed Fix Version/s: MAVEN-31 > Upgrade modello-maven-plugin to 1.8.3. > -- > > Key: MPOM-151 > URL: https://issues.apache.org/jira/browse/MPOM-151 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-151) Upgrade modello-maven-plugin to 1.8.3.
Christian Schulte created MPOM-151: -- Summary: Upgrade modello-maven-plugin to 1.8.3. Key: MPOM-151 URL: https://issues.apache.org/jira/browse/MPOM-151 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-150) Upgrade plexus to 1.7.1.
[ https://issues.apache.org/jira/browse/MPOM-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-150. -- Resolution: Fixed Fix Version/s: MAVEN-31 > Upgrade plexus to 1.7.1. > > > Key: MPOM-150 > URL: https://issues.apache.org/jira/browse/MPOM-150 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-150) Upgrade plexus to 1.7.1.
Christian Schulte created MPOM-150: -- Summary: Upgrade plexus to 1.7.1. Key: MPOM-150 URL: https://issues.apache.org/jira/browse/MPOM-150 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5982) The POM for ... is invalid, transitive dependencies ... while property was overriden
[
https://issues.apache.org/jira/browse/MNG-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757835#comment-15757835
]
Michael Osipov commented on MNG-5982:
-
I can confirm this on FreeBSD 10.3. This is not a Linux-specific issue. There
are two problems here:
1. {{DefaultModelValidator}}:
{noformat}
[ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for
com.sun:tools:jar must specify an absolute path but is
D:/java/jdk1.8.0_65/lib/tools.jar @
test.properties.installme:dependency:1.0-SNAPSHOT
{noformat}
Valadation happens on a static model.
2. The warning itself arises from
{{MavenMetatdataSource#retrieveRelocatedProject()}} simply because the
artifact's scope is not {{system}}. This error makes no sense to me.
If I add {{/usr/local/openjdk8/lib/tools.jar}} to the POM, it works on FreeBSD.
[~khmarbaise], this might not be related to system scope.
> The POM for ... is invalid, transitive dependencies ... while property was
> overriden
>
>
> Key: MNG-5982
> URL: https://issues.apache.org/jira/browse/MNG-5982
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Inheritance and Interpolation, POM
>Affects Versions: 3.0, 3.3.9
> Environment: Linux and Mac
>Reporter: Fabrice Pipart
>
> I experienced issues with a maven build that does not behave the same way if
> done on Windows (like they were done in the past) or Linux (like I want to do
> them now).
> I want to build a project that has a dependency on another project that pom
> that itself imports a pom that contains a Windows path.
> {code:xml}
>my project | other project
> |
> mybuild ---|--> pom > pom with systemPath
> dependencyimport
> |
> {code}
> But in a nutshell, here is my pom:
> {code:xml}
> test.properties
> buildme
> 1.0-SNAPSHOT
> ...
>
>
> test.properties.installme
> module
> 1.0-SNAPSHOT
> pom
>
>
> {code}
> And I depend on a pom that looks like this (not under my control)
> {code:xml}
> test.properties.installme
> module
> 1.0-SNAPSHOT
> ...
>
>
>
> test.properties.installme
> dependency
> 1.0-SNAPSHOT
> import
> pom
>
>
>
>
>
> log4j
> log4j
> 1.2.17
>
>
> {code}
> and the problem lies in this last pom (not under my control again):
> {code:xml}
> 4.0.0
> test.properties.installme
> dependency
> 1.0-SNAPSHOT
> ...
>
> D:/java/jdk1.8.0_65/lib/tools.jar
>
>
>
>
> com.sun
> tools
> 1.8
> system
> ${com.sun.tools.path}
>
>
>
> {code}
> I have no control on the other project in question. I totally agree that a
> refactoring to use environment variable in place of the hard coded paths
> would solve my problem. But instead the Windows path is defined in a
> property. *One would think that overriding the value of the property
> depending on my platform would be enough.* But it is not.
> Unfortunately in this precise case case maven seems to behave to behave
> poorly.
> Before applying any property override in any form (in settings.xml,
> -Dproperty=, redefinition in root pom), maven starts building the effective
> pom. And during that step, if it finds the pattern I mentioned above (a
> dependency on another pom that itself imports a pom that contains a Windows
> path), then it says:
> {code:xml}
> The POM for ::jar: is invalid, transitive
> dependencies (if any) will not be available
> {code}
> As a consequence, my project needs to explicitly define all the dependencies
> of the second project. And I cannot rely on transitive dependencies which
> gives me a lot of trouble.
> In order to illustrate the issue, I created a minimal example showing the
> problem. It can be found here:
> [https://github.com/fabricepipart/test-properties]
> Can you confirm this is a bug from maven?
> I tested with several versions of maven. 3.0 up to a 3.3.9 I think.
> The issue remains the same. It is all a matter of redefining the value of the
> property based on the environment. If I *launch maven with
> -Dcom.sun.tools.path=/correct/linux/path*, globally my build is fine. Because
> when the classes are compiled, it is the *overriden Linux path that is
> taken*, not the Windows one.
> But during the *initial evaluation of the pom*(before any maven phase is
> started), the error I mentioned above is thrown because the *value of the
> property is still the Windows one* (and the path is considered invalid).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MPOM-149) Upgrade plugin tools to 3.5.
[ https://issues.apache.org/jira/browse/MPOM-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-149. -- Resolution: Fixed Fix Version/s: MAVEN-31 > Upgrade plugin tools to 3.5. > > > Key: MPOM-149 > URL: https://issues.apache.org/jira/browse/MPOM-149 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-149) Upgrade plugin tools to 3.5.
Christian Schulte created MPOM-149: -- Summary: Upgrade plugin tools to 3.5. Key: MPOM-149 URL: https://issues.apache.org/jira/browse/MPOM-149 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-148) Upgrade clirr-maven-plugin to 2.8.
[ https://issues.apache.org/jira/browse/MPOM-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-148. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade clirr-maven-plugin to 2.8. > -- > > Key: MPOM-148 > URL: https://issues.apache.org/jira/browse/MPOM-148 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-148) Upgrade clirr-maven-plugin to 2.8.
Christian Schulte created MPOM-148: -- Summary: Upgrade clirr-maven-plugin to 2.8. Key: MPOM-148 URL: https://issues.apache.org/jira/browse/MPOM-148 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-147) Upgrade maven-war-plugin to 3.0.0.
[ https://issues.apache.org/jira/browse/MPOM-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-147. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade maven-war-plugin to 3.0.0. > -- > > Key: MPOM-147 > URL: https://issues.apache.org/jira/browse/MPOM-147 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-147) Upgrade maven-war-plugin to 3.0.0.
Christian Schulte created MPOM-147: -- Summary: Upgrade maven-war-plugin to 3.0.0. Key: MPOM-147 URL: https://issues.apache.org/jira/browse/MPOM-147 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-146) Upgrade maven-resources-plugin to 3.0.2.
[ https://issues.apache.org/jira/browse/MPOM-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-146. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade maven-resources-plugin to 3.0.2. > > > Key: MPOM-146 > URL: https://issues.apache.org/jira/browse/MPOM-146 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-146) Upgrade maven-resources-plugin to 3.0.2.
Christian Schulte created MPOM-146: -- Summary: Upgrade maven-resources-plugin to 3.0.2. Key: MPOM-146 URL: https://issues.apache.org/jira/browse/MPOM-146 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-145) Upgrade maven-plugin-plugin to 3.5.
[ https://issues.apache.org/jira/browse/MPOM-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-145. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade maven-plugin-plugin to 3.5. > --- > > Key: MPOM-145 > URL: https://issues.apache.org/jira/browse/MPOM-145 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-145) Upgrade maven-plugin-plugin to 3.5.
Christian Schulte created MPOM-145: -- Summary: Upgrade maven-plugin-plugin to 3.5. Key: MPOM-145 URL: https://issues.apache.org/jira/browse/MPOM-145 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-144) Upgrade maven-javadoc-plugin to 2.10.4.
[ https://issues.apache.org/jira/browse/MPOM-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-144. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade maven-javadoc-plugin to 2.10.4. > --- > > Key: MPOM-144 > URL: https://issues.apache.org/jira/browse/MPOM-144 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-144) Upgrade maven-javadoc-plugin to 2.10.4.
Christian Schulte created MPOM-144: -- Summary: Upgrade maven-javadoc-plugin to 2.10.4. Key: MPOM-144 URL: https://issues.apache.org/jira/browse/MPOM-144 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-143) Upgrade maven-dependency-plugin to 3.0.0.
Christian Schulte created MPOM-143: -- Summary: Upgrade maven-dependency-plugin to 3.0.0. Key: MPOM-143 URL: https://issues.apache.org/jira/browse/MPOM-143 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-143) Upgrade maven-dependency-plugin to 3.0.0.
[ https://issues.apache.org/jira/browse/MPOM-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-143. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade maven-dependency-plugin to 3.0.0. > - > > Key: MPOM-143 > URL: https://issues.apache.org/jira/browse/MPOM-143 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MWAR-360) Overlay: ignore WAR which is transitively dependent over JAR
[
https://issues.apache.org/jira/browse/MWAR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757820#comment-15757820
]
Michal Domagala commented on MWAR-360:
--
The current issue has not only performance impact, but it is also logical defect
Assume I have 3 WARs, war1, war2, war3. Each WAR applies
{{true}}.
war1 has a file {{x.html}}.
war2 depends on war1 and excludes file {{x.html}}
war3 depends on war2 and war2-classes
Expected: war3 does not contain {{x.html}}, actual: war3 contains {{x.html}}
> Overlay: ignore WAR which is transitively dependent over JAR
>
>
> Key: MWAR-360
> URL: https://issues.apache.org/jira/browse/MWAR-360
> Project: Maven WAR Plugin
> Issue Type: Improvement
>Reporter: Michal Domagala
>Priority: Minor
>
> Example:
> I have WAR project 'Base' with class A.
> I have WAR project 'Level1' which is depends on 'Base'. 'Level1' has class B
> extends A.
> Then 'Base' must have true
> Finally, I have WAR project 'Level2' with class C extends B. For the same
> reason 'Level1' must have true
> Expected: when Level2 WAR is build, only Level1 WAR is overlayed, because
> Level1 contains Base
> Actual: Level1 and Base are overlayed together. That wastes time.
> {noformat}
> [INFO] Copying webapp resources [mwar/Level2/src/main/webapp]
> [INFO] Processing overlay [ id mwar:Level1]
> [INFO] Processing overlay [ id Base:Base]
> [INFO] Webapp assembled in [26 msecs]
> {noformat}
> Reason: Level1 classes JAR has dependency to Base WAR, but that dependency is
> "fake"
> {noformat}
> [INFO] mwar:Level2:war:0.0.1-SNAPSHOT
> [INFO] +- mwar:Level1:war:0.0.1-SNAPSHOT:compile
> [INFO] \- mwar:Level1:jar:classes:0.0.1-SNAPSHOT:compile
> [INFO]+- Base:Base:war:0.0.1-SNAPSHOT:compile
> [INFO]\- Base:Base:jar:classes:0.0.1-SNAPSHOT:compile
> {noformat}
> Proposed solution: There should be option 'notOverlayTransitiveWar' which
> allow exclude WARs like 'Base' from overlaying, because the transitive WAR
> may be reached only over JAR and I think there is no reason any JAR really
> depends on WAR.
> Workaround is manually define ovelays in plugin configuration, but Maven
> spirit is Convention over Configuration
> h2. example
> # git clone https://github.com/michaldo/mwar360.git
> # cd mwar360
> # mvn package
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MPOM-142) Upgrade maven-compiler-plugin to 3.6.0.
[ https://issues.apache.org/jira/browse/MPOM-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-142. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade maven-compiler-plugin to 3.6.0. > --- > > Key: MPOM-142 > URL: https://issues.apache.org/jira/browse/MPOM-142 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-141) Upgrade maven-assembly-plugin to 3.0.0.
[ https://issues.apache.org/jira/browse/MPOM-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MPOM-141. -- Resolution: Fixed Fix Version/s: ASF-19 > Upgrade maven-assembly-plugin to 3.0.0. > --- > > Key: MPOM-141 > URL: https://issues.apache.org/jira/browse/MPOM-141 > Project: Maven POMs > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: ASF-19 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-142) Upgrade maven-compiler-plugin to 3.6.0.
Christian Schulte created MPOM-142: -- Summary: Upgrade maven-compiler-plugin to 3.6.0. Key: MPOM-142 URL: https://issues.apache.org/jira/browse/MPOM-142 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-141) Upgrade maven-assembly-plugin to 3.0.0.
Christian Schulte created MPOM-141: -- Summary: Upgrade maven-assembly-plugin to 3.0.0. Key: MPOM-141 URL: https://issues.apache.org/jira/browse/MPOM-141 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPOM-140) Upgrade maven-assembly-plugin to 3.0.0.
Christian Schulte created MPOM-140: -- Summary: Upgrade maven-assembly-plugin to 3.0.0. Key: MPOM-140 URL: https://issues.apache.org/jira/browse/MPOM-140 Project: Maven POMs Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-5807) Both classes and shaded jar exposed as dependency from artifact in multimodule build
[
https://issues.apache.org/jira/browse/MNG-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5807.
---
Resolution: Cannot Reproduce
Cannot reproduce with
{noformat}
Apache Maven 3.4.0-SNAPSHOT (8a1b6359f31178ce804018cfb524e72f1178028a;
2016-12-17T20:46:55+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.4.0-SNAPSHOT
Java version: 1.8.0_112, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_112\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{noformat}
by running {{mvn clean install}} on master:
{noformat}
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ trees ---
[INFO] Installing
D:\Entwicklung\Projekte\immutables\trees\target\trees-2.3.11-SNAPSHOT.jar to
C:\Users\mosipov\.m2\repository\org\immutables\trees\2.3.11-SNAPSHOT\trees-2.3.11-SNAPSHOT.jar
[INFO] Installing D:\Entwicklung\Projekte\immutables\trees\pom.xml to
C:\Users\mosipov\.m2\repository\org\immutables\trees\2.3.11-SNAPSHOT\trees-2.3.11-SNAPSHOT.pom
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] org.immutables.immutables .. SUCCESS [ 0.694 s]
[INFO] org.immutables.dependency.utility .. SUCCESS [ 0.046 s]
[INFO] org.immutables.testing . SUCCESS [ 1.937 s]
[INFO] org.immutables.generator ... SUCCESS [ 1.900 s]
[INFO] org.immutables.generator-processor . SUCCESS [ 3.334 s]
[INFO] org.immutables.metainf . SUCCESS [ 3.000 s]
[INFO] org.immutables.generator-fixture ... SUCCESS [ 1.516 s]
[INFO] org.immutables.mirror .. SUCCESS [ 0.985 s]
[INFO] org.immutables.value-processor . SUCCESS [ 7.876 s]
[INFO] org.immutables.value ... SUCCESS [ 2.007 s]
[INFO] org.immutables.ordinal . SUCCESS [ 1.313 s]
[INFO] org.immutables.builder . SUCCESS [ 1.594 s]
[INFO] org.immutables.android-stub SUCCESS [ 0.062 s]
[INFO] org.immutables.gson SUCCESS [ 4.406 s]
[INFO] org.immutables.mongo ... SUCCESS [ 2.285 s]
[INFO] org.immutables.func SUCCESS [ 0.530 s]
[INFO] org.immutables.serial .. SUCCESS [ 1.296 s]
[INFO] org.immutables.encode .. SUCCESS [ 0.288 s]
[INFO] org.immutables.value-fixture ... SUCCESS [ 17.613 s]
[INFO] org.immutables.trees ... SUCCESS [ 2.536 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 55.461 s
[INFO] Finished at: 2016-12-18T00:42:24+01:00
[INFO] Final Memory: 107M/1480M
[INFO]
{noformat}
> Both classes and shaded jar exposed as dependency from artifact in
> multimodule build
>
>
> Key: MNG-5807
> URL: https://issues.apache.org/jira/browse/MNG-5807
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.1
> Environment: Apache Maven 3.3.1
> (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T13:10:27-07:00)
> Maven home: /usr/local/Cellar/maven/3.3.1/libexec
> Java version: 1.8.0_25, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"
>Reporter: Eugene Lucash
>
> After upgrade from 3.2.x to 3.3.1 my project experienced build failure.
> During multi-module build, where couple of module has dependency on another
> module. The dependency itself is an annotation processor module which builds
> shaded all-in-one jar (with relocated dependencies) which becomes main
> artifact of that module. It worked well in 3.2.x, but in 3.3.1, the dependent
> modules' classpath receives both shaded and original/classes dependencies.
> The dependent module fails to build due to duplicate processor runs (files
> already generated etc). Interesting is that if I resume build from the failed
> module (using `-rf`) then it would succeed as only shaded jar will be
> available then.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-5415) Duplicate dependency with property causes the build to fail
[
https://issues.apache.org/jira/browse/MNG-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5415:
Labels: close-pending (was: )
> Duplicate dependency with property causes the build to fail
> ---
>
> Key: MNG-5415
> URL: https://issues.apache.org/jira/browse/MNG-5415
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0.3, 3.0.4
> Environment: $ mvn -version
> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /usr/share/maven
> Java version: 1.7.0_09, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_09.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.8.2", arch: "x86_64", family: "mac"
>Reporter: Tarje Killingberg
> Labels: close-pending
> Attachments: my-app.zip
>
>
> The following excerpt from a _pom.xml_ file causes just about any maven
> command (e.g. {{mvn package}}) to fail with the error
> _'dependencies.dependency.version' for junit:junit:jar is missing_:
> {code}
>
> jar
> jar
>
>
>
>
> junit
> junit
> 4.10
> ${my.type}
>
>
> junit
> junit
> 4.10
> ${my.other.type}
>
>
>
>
>
> junit
> junit
> ${my.type}
>
>
> junit
> junit
> ${my.other.type}
> true
>
>
> {code}
> If the string _jar_ is used instead of the properties, the build succeeds
> with warnings.
> A SSCCE is attached. Running the command {{mvn validate}} inside the
> _my-app_-folder should show the symptom.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MNG-6072) Cannot build archetypes on Windows
[
https://issues.apache.org/jira/browse/MNG-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6072.
---
Resolution: Incomplete
The original issue has been closed already. I cannot reproduce this neither
with the tag and master (63a14183fb7789888622587b84f8cd5e1c00faf0). All I get
with
{noformat}
Apache Maven 3.4.0-SNAPSHOT (8a1b6359f31178ce804018cfb524e72f1178028a;
2016-12-17T20:46:55+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.4.0-SNAPSHOT
Java version: 1.8.0_112, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_112\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{noformat}
is
{noformat}
[INFO] --- wildfly-feature-pack-build-maven-plugin:1.1.6.Final:build
(feature-pack-build) @ wildfly-camel-feature-pack ---
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Wildfly Camel .. SUCCESS [ 2.031 s]
[INFO] Wildfly Camel :: Config SUCCESS [ 3.042 s]
[INFO] WildFly Camel :: CXF Undertow .. SUCCESS [ 4.421 s]
[INFO] Wildfly Camel :: Subsystem . SUCCESS [ 0.027 s]
[INFO] Wildfly Camel :: Subsystem :: Core . SUCCESS [ 2.187 s]
[INFO] Wildfly Camel :: Subsystem :: CDI .. SUCCESS [ 2.740 s]
[INFO] Wildfly Camel :: Subsystem :: Security . SUCCESS [ 0.926 s]
[INFO] Wildfly Camel :: Subsystem :: Undertow . SUCCESS [ 1.344 s]
[INFO] Wildfly Camel :: Feature Pack .. FAILURE [ 19.737 s]
[INFO] Wildfly Camel :: Archetypes SKIPPED
[INFO] Wildfly Camel :: Archetypes :: CDI . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 38.231 s
[INFO] Finished at: 2016-12-18T00:21:26+01:00
[INFO] Final Memory: 222M/1548M
[INFO]
[ERROR] Failed to execute goal
org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.1.6.Final:build
(feature-pack-build) on project wildfly-camel-feature-pack: Execution
feature-pack-build of goal
org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.1.6.Final:build
failed: java.lang.RuntimeException: Some errors were encountered creating the
feature pack
[ERROR] Missing module ModuleIdentifier{name='junit', slot='5.5'}. Module was
required by [ModuleIdentifier{name='org.apache.lucene', slot='5.5'}]
[ERROR] Missing module ModuleIdentifier{name='ch.qos.logback', slot='main'}.
Module was required by [ModuleIdentifier{name='io.netty', slot='4.1'},
ModuleIdentifier{name='org.quartz', slot='main'},
ModuleIdentifier{name='org.springframework.security', slot='main'}]
[ERROR] Missing module ModuleIdentifier{name='org.osgi.compendium',
slot='main'}. Module was required by
[ModuleIdentifier{name='org.fusesource.mqtt', slot='main'},
ModuleIdentifier{name='org.fusesource.hawtdispatch', slot='main'}]
[ERROR] Missing module ModuleIdentifier{name='org.apache.aries.blueprint',
slot='main'}. Module was required by
[ModuleIdentifier{name='org.apache.cxf.ext', slot='main'}]
[ERROR] Missing module ModuleIdentifier{name='io.netty.parts', slot='main'}.
Module was required by [ModuleIdentifier{name='io.netty', slot='4.1'},
ModuleIdentifier{name='org.apache.camel.component.mongodb', slot='main'}]
[ERROR] Missing module ModuleIdentifier{name='jline', slot='main'}. Module was
required by [ModuleIdentifier{name='org.apache.camel.script.groovy',
slot='main'}]
[ERROR] Missing module ModuleIdentifier{name='org.joda.convert', slot='main'}.
Module was required by
[ModuleIdentifier{name='org.apache.camel.component.swagger', slot='main'}]
[ERROR] Missing module ModuleIdentifier{name='junit', slot='main'}. Module was
required by [ModuleIdentifier{name='org.apache.camel.component.jacksonxml',
slot='main'}, ModuleIdentifier{name='org.apache.kafka.clients', slot='main'},
ModuleIdentifier{name='org.fusesource.hawtdispatch', slot='main'},
ModuleIdentifier{name='org.apache.ws.commons.axiom.axiom-api', slot='main'},
ModuleIdentifier{name='org.apache.camel.component.jdbc', slot='main'},
ModuleIdentifier{name='org.apache.camel.component.atom', slot='main'},
ModuleIdentifier{name='org.apache.camel.component.salesforce', slot='main'},
ModuleIdentifier{name='org.apache.camel.component.xmlsecurity', slot='main'},
ModuleIdentifier{name='org.apache.kafka', slot='main'},
ModuleIdentifier{name='org.apache.camel.component.flatpack', slot='main'},
ModuleIdentifier{name='org.apache.camel.component.soap', slot='main'},
ModuleIdentifier{name='org.apache.camel.component.barcode', slot='main'},
Mod
[jira] [Closed] (MNG-5941) AbstractMethodError in Maven dependency tree library
[ https://issues.apache.org/jira/browse/MNG-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-5941. --- Resolution: Not A Problem The issue seems to be fixed with Sonar itself. Not a problem anymore here unless you see otherwise. > AbstractMethodError in Maven dependency tree library > > > Key: MNG-5941 > URL: https://issues.apache.org/jira/browse/MNG-5941 > Project: Maven > Issue Type: Bug > Components: Dependencies, Plugin API >Affects Versions: 3.2.2, 3.3.9 > Environment: Windows 7 64 bits > Oracle JDK 1.7.0_79 > sonar-maven-plugin 2.7.1 >Reporter: Juan Farré > Labels: maven > > This issue came up using sonar-maven-plugin. > When dealing with managed transitive system-scoped dependencies, sonar > analysis crashed. > According to sonar plugin maintainers, this is an issue in Maven dependency > tree library, and not in sonar-maven-plugin itself. > In order to allow this plugin to work correctly in this situation, without > modifications that would break backward compatibility, a fix for this issue > is needed in a 2.1 branch of Maven dependency tree library. > The external issue given includes a link to a detailed reproducer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-5529) Misuse of iterator.remove in DefaultModelBuilder
[ https://issues.apache.org/jira/browse/MNG-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-5529. --- Resolution: Incomplete Requested patch has not been provided. > Misuse of iterator.remove in DefaultModelBuilder > > > Key: MNG-5529 > URL: https://issues.apache.org/jira/browse/MNG-5529 > Project: Maven > Issue Type: Bug >Affects Versions: 3.1.1 >Reporter: Christopher Hunt > Labels: patch-pending > > Line 905 of DefaultModelBuilder removes elements from the list of > dependencies for dependency management. The JDK states that the iterator's > remove operation is optional and when it is not present then an > UnsupportedOperationException will be thrown. > My recommendation is that the list of dependencies returned is composed into > an array list for working purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-5864) "optional" attribute validation
[
https://issues.apache.org/jira/browse/MNG-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5864.
---
Resolution: Invalid
{{optional}} is defined as string in the XSD as well as in the generated model.
> "optional" attribute validation
> ---
>
> Key: MNG-5864
> URL: https://issues.apache.org/jira/browse/MNG-5864
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.3
> Environment: JBoss Developer Studio 8.1.0.GA
>Reporter: Vsevolod Golovanov
>
> I have some dependencies, whose {{optional}} attributes are defined by
> property expressions. E.g.:
> {code}
>
>
> ${someProperty}
>
> {code}
> This works fine, but leads to validation errors in JBoss Developer Studio:
> {noformat}
> cvc-datatype-valid.1.2.1: '${someProperty}' is not a valid value for
> 'boolean'.
> cvc-type.3.1.3: The value '${someProperty}' of element 'optional' is not
> valid.
> {noformat}
> I far as I understand the problem is in [the
> XSD|http://maven.apache.org/xsd/maven-4.0.0.xsd]:
> {code}
>
> {code}
> It's defined as boolean, yet [Maven
> Model|http://maven.apache.org/ref/3.3.3//maven-model/maven.html] says:
> {quote}Note: While the type of this field is String for technical reasons,
> the semantic type is actually Boolean.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6105) properties.internal.SystemProperties.addSystemProperties() is not really thread-safe
[
https://issues.apache.org/jira/browse/MNG-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757725#comment-15757725
]
Guillaume Boué commented on MNG-6105:
-
All right, the issue is fixed to me yes.
> properties.internal.SystemProperties.addSystemProperties() is not really
> thread-safe
>
>
> Key: MNG-6105
> URL: https://issues.apache.org/jira/browse/MNG-6105
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /usr/maven/default
> Java version: 1.8.0_102, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_102/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-431.29.2.el6.x86_64", arch: "amd64",
> family: "unix"
>Reporter: Falko Modler
>Assignee: Guillaume Boué
> Fix For: 3.4.0
>
>
> We got a rather large Maven project with a couble of modules that execute
> {{maven-assembly-plugin}}. Our build runs in parallel mode via {{-Tx}}.
> From time to time we are seeing following exception causing the respective
> build to fail:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip) on
> project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip)
> on project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at
> org.apache.maven.properties.internal.SystemProperties.addSystemProperties(SystemProperties.java:38)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.getSystemProperties(MavenMetadataSource.java:756)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:574)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:190)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:532)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:584)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.collect(DefaultLegacyArtifactCollector.java:144)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:493)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveWithExceptions(DefaultArtifactResolver.java:348)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:342)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:321)
> at
> org.ap
[jira] [Closed] (MNG-6105) properties.internal.SystemProperties.addSystemProperties() is not really thread-safe
[
https://issues.apache.org/jira/browse/MNG-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Boué closed MNG-6105.
---
Resolution: Fixed
Fix Version/s: 3.4.0
> properties.internal.SystemProperties.addSystemProperties() is not really
> thread-safe
>
>
> Key: MNG-6105
> URL: https://issues.apache.org/jira/browse/MNG-6105
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /usr/maven/default
> Java version: 1.8.0_102, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_102/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-431.29.2.el6.x86_64", arch: "amd64",
> family: "unix"
>Reporter: Falko Modler
>Assignee: Guillaume Boué
> Fix For: 3.4.0
>
>
> We got a rather large Maven project with a couble of modules that execute
> {{maven-assembly-plugin}}. Our build runs in parallel mode via {{-Tx}}.
> From time to time we are seeing following exception causing the respective
> build to fail:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip) on
> project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip)
> on project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at
> org.apache.maven.properties.internal.SystemProperties.addSystemProperties(SystemProperties.java:38)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.getSystemProperties(MavenMetadataSource.java:756)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:574)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:190)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:532)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:584)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.collect(DefaultLegacyArtifactCollector.java:144)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:493)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveWithExceptions(DefaultArtifactResolver.java:348)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:342)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:321)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolve
[jira] [Closed] (MDEP-508) URL contains illegal character ("[") for google guava artifact from central repo (goal: dependency:go-offline)
[
https://issues.apache.org/jira/browse/MDEP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Boué closed MDEP-508.
---
Resolution: Fixed
Assignee: Guillaume Boué
Fix Version/s: 3.0.0
> URL contains illegal character ("[") for google guava artifact from central
> repo (goal: dependency:go-offline)
> --
>
> Key: MDEP-508
> URL: https://issues.apache.org/jira/browse/MDEP-508
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.8
> Environment: CentOS 6.7; Tycho 0.23.0
>Reporter: Mark Leone
>Assignee: Guillaume Boué
> Fix For: 3.0.0
>
> Attachments: sample-build.zip
>
>
> While running the Maven goal dependency:go-offline, the build fails while
> trying to download google guava artifacts from the central repository. The
> error message indicates an illegal character in the URL, specifically a "["
> character, which comes from the version specifier.
> First I run
> {noformat}mvn -Dmaven.repo.local=/some/path/ -DgeneratePom=true clean
> install{noformat}
> to create the artifacts, and that build succeeds. Then when I run
> {noformat}mvn -Dmaven.repo.local=/some/path/ -o clean install{noformat}
> it fails because it's running in offline mode and there is no local cache
> available for http://download.eclipse.org/tools/cdt/releases/8.6
> So then I run
> {noformat}mvn -Dmaven.repo.local=/some/path/ dependency:go-offline{noformat}
> to make it download all the artifacts it needs for the build, but it fails
> with this message:
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.8:resolve-plugins
> (resolve-plugins) on project : Nested: Could not transfer artifact
> com.google.guava:guava:jar:[10.0.1,14.0.1] from/to central
> (https://repo.maven.apache.org/maven2): Illegal character in path at index
> 60:
> https://repo.maven.apache.org/maven2/com/google/guava/guava/[10.0.1,14.0.1]/guava-[10.0.1,14.0.1].jar{noformat}
> The product being built is an Eclipse RCP product, using the
> org.eclipse.tycho:target-platform-configuration plug-in to load the
> dependencies from an RCP target file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MDEP-508) URL contains illegal character ("[") for google guava artifact from central repo (goal: dependency:go-offline)
[
https://issues.apache.org/jira/browse/MDEP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757723#comment-15757723
]
Guillaume Boué commented on MDEP-508:
-
This issue was resolved implicitly with the release of version 3.0.0, when
upgrading the plugin to Maven 3. The sample project does not show the issue
anymore: the version range in Guava is correctly resolved and the downloads are
successful.
> URL contains illegal character ("[") for google guava artifact from central
> repo (goal: dependency:go-offline)
> --
>
> Key: MDEP-508
> URL: https://issues.apache.org/jira/browse/MDEP-508
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.8
> Environment: CentOS 6.7; Tycho 0.23.0
>Reporter: Mark Leone
> Attachments: sample-build.zip
>
>
> While running the Maven goal dependency:go-offline, the build fails while
> trying to download google guava artifacts from the central repository. The
> error message indicates an illegal character in the URL, specifically a "["
> character, which comes from the version specifier.
> First I run
> {noformat}mvn -Dmaven.repo.local=/some/path/ -DgeneratePom=true clean
> install{noformat}
> to create the artifacts, and that build succeeds. Then when I run
> {noformat}mvn -Dmaven.repo.local=/some/path/ -o clean install{noformat}
> it fails because it's running in offline mode and there is no local cache
> available for http://download.eclipse.org/tools/cdt/releases/8.6
> So then I run
> {noformat}mvn -Dmaven.repo.local=/some/path/ dependency:go-offline{noformat}
> to make it download all the artifacts it needs for the build, but it fails
> with this message:
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.8:resolve-plugins
> (resolve-plugins) on project : Nested: Could not transfer artifact
> com.google.guava:guava:jar:[10.0.1,14.0.1] from/to central
> (https://repo.maven.apache.org/maven2): Illegal character in path at index
> 60:
> https://repo.maven.apache.org/maven2/com/google/guava/guava/[10.0.1,14.0.1]/guava-[10.0.1,14.0.1].jar{noformat}
> The product being built is an Eclipse RCP product, using the
> org.eclipse.tycho:target-platform-configuration plug-in to load the
> dependencies from an RCP target file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6105) properties.internal.SystemProperties.addSystemProperties() is not really thread-safe
[
https://issues.apache.org/jira/browse/MNG-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757716#comment-15757716
]
Michael Osipov commented on MNG-6105:
-
Guillaume, if you consider it fixed and the OP hasn't reacted for two months,
consider it fixed and target for 3.4.0.
> properties.internal.SystemProperties.addSystemProperties() is not really
> thread-safe
>
>
> Key: MNG-6105
> URL: https://issues.apache.org/jira/browse/MNG-6105
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /usr/maven/default
> Java version: 1.8.0_102, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_102/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-431.29.2.el6.x86_64", arch: "amd64",
> family: "unix"
>Reporter: Falko Modler
>Assignee: Guillaume Boué
>
> We got a rather large Maven project with a couble of modules that execute
> {{maven-assembly-plugin}}. Our build runs in parallel mode via {{-Tx}}.
> From time to time we are seeing following exception causing the respective
> build to fail:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip) on
> project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single (assembly-zip)
> on project some-module: Execution assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> assembly-zip of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at
> org.apache.maven.properties.internal.SystemProperties.addSystemProperties(SystemProperties.java:38)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.getSystemProperties(MavenMetadataSource.java:756)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:574)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:190)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:532)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.recurse(DefaultLegacyArtifactCollector.java:584)
> at
> org.apache.maven.repository.legacy.resolver.DefaultLegacyArtifactCollector.collect(DefaultLegacyArtifactCollector.java:144)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:493)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveWithExceptions(DefaultArtifactResolver.java:348)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:342)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(Default
[jira] [Closed] (MDEP-482) Can't use both outputProperty and outputFile in build-classpath mojo
[ https://issues.apache.org/jira/browse/MDEP-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MDEP-482. --- Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.1 > Can't use both outputProperty and outputFile in build-classpath mojo > > > Key: MDEP-482 > URL: https://issues.apache.org/jira/browse/MDEP-482 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Affects Versions: 2.10 >Reporter: Dagan Sandler >Assignee: Guillaume Boué >Priority: Minor > Fix For: 3.0.1 > > Attachments: MDEP-482-maven-dependency-plugin.patch > > > When defining the configuration for the dependency:build-classpath mojo, a > user can use either and to define the desired > output of the classpath string. These both work as expected. > However, if the user wishes to use both output methods in conjunction, the > gets discarded and only is used. > A current workaround that achieves the desired missing behavior involves > defining two different executions for the mojo only differing by the output > method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MDEP-482) Can't use both outputProperty and outputFile in build-classpath mojo
[ https://issues.apache.org/jira/browse/MDEP-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757603#comment-15757603 ] Hudson commented on MDEP-482: - SUCCESS: Integrated in Jenkins build maven-plugins #7797 (See [https://builds.apache.org/job/maven-plugins/7797/]) [MDEP-482] Can't use both outputProperty and outputFile in build-classpath mojo Submitted by: Dagan Sandler Make sure outputFile and outputProperty can both be used at the same time. Applied patch after adding an IT. (gboue: [http://svn.apache.org/viewvc/?view=rev&rev=1774803]) * (add) maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property * (add) maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/invoker.properties * (add) maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/pom.xml * (add) maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/test.properties * (add) maven-dependency-plugin/src/it/projects/build-classpath-output-file-and-property/verify.bsh * (edit) maven-dependency-plugin/src/main/java/org/apache/maven/plugins/dependency/fromDependencies/BuildClasspathMojo.java > Can't use both outputProperty and outputFile in build-classpath mojo > > > Key: MDEP-482 > URL: https://issues.apache.org/jira/browse/MDEP-482 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Affects Versions: 2.10 >Reporter: Dagan Sandler >Priority: Minor > Attachments: MDEP-482-maven-dependency-plugin.patch > > > When defining the configuration for the dependency:build-classpath mojo, a > user can use either and to define the desired > output of the classpath string. These both work as expected. > However, if the user wishes to use both output methods in conjunction, the > gets discarded and only is used. > A current workaround that achieves the desired missing behavior involves > defining two different executions for the mojo only differing by the output > method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MDEP-482) Can't use both outputProperty and outputFile in build-classpath mojo
[ https://issues.apache.org/jira/browse/MDEP-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757584#comment-15757584 ] Guillaume Boué commented on MDEP-482: - Fixed in [r1774803|http://svn.apache.org/viewvc?rev=1774803&view=rev]. > Can't use both outputProperty and outputFile in build-classpath mojo > > > Key: MDEP-482 > URL: https://issues.apache.org/jira/browse/MDEP-482 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Affects Versions: 2.10 >Reporter: Dagan Sandler >Priority: Minor > Attachments: MDEP-482-maven-dependency-plugin.patch > > > When defining the configuration for the dependency:build-classpath mojo, a > user can use either and to define the desired > output of the classpath string. These both work as expected. > However, if the user wishes to use both output methods in conjunction, the > gets discarded and only is used. > A current workaround that achieves the desired missing behavior involves > defining two different executions for the mojo only differing by the output > method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6038) use Gossip slf4j provider as default logging, since it supports level colorization
[ https://issues.apache.org/jira/browse/MNG-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757580#comment-15757580 ] Michael Osipov commented on MNG-6038: - Hervé, isn't this a won't fix right now? > use Gossip slf4j provider as default logging, since it supports level > colorization > -- > > Key: MNG-6038 > URL: https://issues.apache.org/jira/browse/MNG-6038 > Project: Maven > Issue Type: New Feature > Components: Logging >Affects Versions: 3.3.9 >Reporter: Hervé Boutemy > > support was added in MNG-6037 > using it by default will add color for level rendering without need to > manually add the provider as lib -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5457) Show repository id when downloading or uploading from/to a remote repository
[
https://issues.apache.org/jira/browse/MNG-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757571#comment-15757571
]
Hudson commented on MNG-5457:
-
SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #46 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/46/])
[MNG-5457] Show repository id when downloading or uploading from/to a
(michaelo: rev 8a1b6359f31178ce804018cfb524e72f1178028a)
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/AbstractMavenTransferListener.java
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/Slf4jMavenTransferListener.java
> Show repository id when downloading or uploading from/to a remote repository
>
>
> Key: MNG-5457
> URL: https://issues.apache.org/jira/browse/MNG-5457
> Project: Maven
> Issue Type: Improvement
> Components: General
>Affects Versions: 3.0.5
>Reporter: Hervé Boutemy
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
> Attachments: 2016-05-18_204749.png
>
>
> currently, the log only show the url being downloaded:
> {noformat}Downloading:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
> nothing is told about the repository id.
> But as shown in MNG-5181, repository id is an important information since it
> is stored in local repository to limit artifact scope: it would be useful
> IMHO to display the id in the output, like
> {noformat}Downloading from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5457) Show repository id when downloading or uploading from/to a remote repository
[
https://issues.apache.org/jira/browse/MNG-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757567#comment-15757567
]
Hudson commented on MNG-5457:
-
FAILURE: Integrated in Jenkins build maven-3.x #1454 (See
[https://builds.apache.org/job/maven-3.x/1454/])
[MNG-5457] Show repository id when downloading or uploading from/to a
(michaelo: rev 8a1b6359f31178ce804018cfb524e72f1178028a)
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/AbstractMavenTransferListener.java
* (edit)
maven-embedder/src/main/java/org/apache/maven/cli/transfer/Slf4jMavenTransferListener.java
> Show repository id when downloading or uploading from/to a remote repository
>
>
> Key: MNG-5457
> URL: https://issues.apache.org/jira/browse/MNG-5457
> Project: Maven
> Issue Type: Improvement
> Components: General
>Affects Versions: 3.0.5
>Reporter: Hervé Boutemy
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
> Attachments: 2016-05-18_204749.png
>
>
> currently, the log only show the url being downloaded:
> {noformat}Downloading:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
> nothing is told about the repository id.
> But as shown in MNG-5181, repository id is an important information since it
> is stored in local repository to limit artifact scope: it would be useful
> IMHO to display the id in the output, like
> {noformat}Downloading from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MNG-3879) Dependency map and documentation
[ https://issues.apache.org/jira/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-3879. --- > Dependency map and documentation > > > Key: MNG-3879 > URL: https://issues.apache.org/jira/browse/MNG-3879 > Project: Maven > Issue Type: New Feature > Components: Dependencies >Affects Versions: 2.0.9 >Reporter: Benson Margulies > > This JIRA proposes a feature. I'm willing to try to contribute it given a > modicum of encouragement and guidance. > Over at CXF, we get many questions from users who are completely confounded > by the complex dependency graph that results from our many dependencies and > their many dependencies. I think that they would be less confused by far if > maven gave them a tiny bit of help. > My idea for this requires an addition to the core POM, which is why I'm > starting with a JIRA here. I propose to add an 'explanation' element to the > dependency element. This would contain a human-readable string explaining why > the dependency is here, which could be carried out through the dependency > plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-5457) Show repository id when downloading or uploading from/to a remote repository
[
https://issues.apache.org/jira/browse/MNG-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5457.
---
Resolution: Fixed
Fixed with
[8a1b6359f31178ce804018cfb524e72f1178028a|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8a1b6359f31178ce804018cfb524e72f1178028a].
> Show repository id when downloading or uploading from/to a remote repository
>
>
> Key: MNG-5457
> URL: https://issues.apache.org/jira/browse/MNG-5457
> Project: Maven
> Issue Type: Improvement
> Components: General
>Affects Versions: 3.0.5
>Reporter: Hervé Boutemy
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
> Attachments: 2016-05-18_204749.png
>
>
> currently, the log only show the url being downloaded:
> {noformat}Downloading:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
> nothing is told about the repository id.
> But as shown in MNG-5181, repository id is an important information since it
> is stored in local repository to limit artifact scope: it would be useful
> IMHO to display the id in the output, like
> {noformat}Downloading from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-5896) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MNG-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5896: Assignee: (was: Michael Osipov) > Download dependency POMs in parallel > > > Key: MNG-5896 > URL: https://issues.apache.org/jira/browse/MNG-5896 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.3.3 >Reporter: Harald Wellmann > Fix For: 3.4.0 > > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.3 first downloads the dependency POMs > _sequentially_ and then proceeds downloading the dependency JARs with up to 5 > threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MDEP-422) Support version ranges in get
[
https://issues.apache.org/jira/browse/MDEP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Boué closed MDEP-422.
---
Resolution: Fixed
Assignee: Guillaume Boué
Fix Version/s: 3.0.0
> Support version ranges in get
> -
>
> Key: MDEP-422
> URL: https://issues.apache.org/jira/browse/MDEP-422
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: get
>Affects Versions: 2.8
>Reporter: stanislav bashkirtsev
>Assignee: Guillaume Boué
> Fix For: 3.0.0
>
>
> {code}mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get
> -DgroupId=some.group.id -DartifactId=some-artifact -Dversion="[8.2.0,8.2.9)"
> -Dpackaging=zip{code}*Expected Result*: the latest artifact between 8.2.0 and
> 8.2.8 should be downloaded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MDEP-422) Support version ranges in get
[
https://issues.apache.org/jira/browse/MDEP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757222#comment-15757222
]
Guillaume Boué commented on MDEP-422:
-
Version ranges are now supported starting with version 3.0.0 of the plugin.
This has been solved by using the shared component {{maven-artifact-transfer}},
done with this version.
{noformat}
$ mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get
-Dartifact=asm:asm-analysis:[3.2,3.4]
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Maven Stub Project (No POM) 1
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:3.0.0:get (default-cli) @ standalone-pom ---
[INFO] Resolving asm:asm-analysis:jar:[3.2,3.4] with transitive dependencies
Downloading:
https://repo.maven.apache.org/maven2/asm/asm-analysis/3.3.1/asm-analysis-3.3.1.pom
Downloaded:
https://repo.maven.apache.org/maven2/asm/asm-analysis/3.3.1/asm-analysis-3.3.1.pom
(419 B at 0.8 KB/sec)
Downloading:
https://repo.maven.apache.org/maven2/asm/asm-tree/3.3.1/asm-tree-3.3.1.pom
Downloaded:
https://repo.maven.apache.org/maven2/asm/asm-tree/3.3.1/asm-tree-3.3.1.pom (406
B at 8.3 KB/sec)
Downloading:
https://repo.maven.apache.org/maven2/asm/asm-tree/3.3.1/asm-tree-3.3.1.jar
Downloading:
https://repo.maven.apache.org/maven2/asm/asm-analysis/3.3.1/asm-analysis-3.3.1.jar
Downloaded:
https://repo.maven.apache.org/maven2/asm/asm-analysis/3.3.1/asm-analysis-3.3.1.jar
(18 KB at 182.9 KB/sec)
Downloaded:
https://repo.maven.apache.org/maven2/asm/asm-tree/3.3.1/asm-tree-3.3.1.jar (22
KB at 84.7 KB/sec)
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.900 s
[INFO] Finished at: 2016-12-17T16:44:41+01:00
[INFO] Final Memory: 16M/196M
[INFO]
{noformat}
> Support version ranges in get
> -
>
> Key: MDEP-422
> URL: https://issues.apache.org/jira/browse/MDEP-422
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: get
>Affects Versions: 2.8
>Reporter: stanislav bashkirtsev
>
> {code}mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get
> -DgroupId=some.group.id -DartifactId=some-artifact -Dversion="[8.2.0,8.2.9)"
> -Dpackaging=zip{code}*Expected Result*: the latest artifact between 8.2.0 and
> 8.2.8 should be downloaded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
