[GitHub] [maven] josephw commented on a change in pull request #264: [MNG-6535] Improve test coverage of UrlNormalizer.
josephw commented on a change in pull request #264: [MNG-6535] Improve test
coverage of UrlNormalizer.
URL: https://github.com/apache/maven/pull/264#discussion_r300849941
##
File path:
maven-model-builder/src/test/java/org/apache/maven/model/path/DefaultUrlNormalizerTest.java
##
@@ -82,4 +82,8 @@ public void testPreservationOfDoubleSlashes()
normalize(
"[fetch=]http://server.org/[push=]ssh://server.org/; ) );
}
+public void testNormalizeInputWithNoParentDirectoriesToAscendTo()
+{
+assertEquals("a/../", normalize("a/../"));
+}
Review comment:
Thinking again; there's no reason to retain the existing behaviour if it's
wrong. The change to match `Path` is simple enough, and doesn't break the
existing tests: I've pushed it.
Ideally, the interface would be clearer about its contract, but this is the
least surprising behaviour.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [maven] michael-o commented on issue #134: [MNG-6294] Convert MavenPluginValidator into a plexus component
michael-o commented on issue #134: [MNG-6294] Convert MavenPluginValidator into a plexus component URL: https://github.com/apache/maven/pull/134#issuecomment-508957945 Willing to merge if someone can extend the tests. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven] asfgit closed pull request #263: [MNG-6698] Improve the ManagedVersionMap
asfgit closed pull request #263: [MNG-6698] Improve the ManagedVersionMap URL: https://github.com/apache/maven/pull/263 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Closed] (MNG-6698) Lazily compute the ManagedVersionMap
[ https://issues.apache.org/jira/browse/MNG-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6698. --- Resolution: Fixed Fixed with [7ba97003861fa23feb7a66923388cfc6a704750c|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=7ba97003861fa23feb7a66923388cfc6a704750c]. > Lazily compute the ManagedVersionMap > > > Key: MNG-6698 > URL: https://issues.apache.org/jira/browse/MNG-6698 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.6.1 >Reporter: Guillaume Nodet >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6698) Lazily compute the ManagedVersionMap
[ https://issues.apache.org/jira/browse/MNG-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6698: Fix Version/s: (was: 3.6.x-candidate) 3.6.2 > Lazily compute the ManagedVersionMap > > > Key: MNG-6698 > URL: https://issues.apache.org/jira/browse/MNG-6698 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.6.1 >Reporter: Guillaume Nodet >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNG-6700) Equal compile source roots are added multiple times
[
https://issues.apache.org/jira/browse/MNG-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6700.
---
Resolution: Fixed
Fixed with
[84bf1877f0b54144edcb85094fe10302e236303e|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=84bf1877f0b54144edcb85094fe10302e236303e].
> Equal compile source roots are added multiple times
> ---
>
> Key: MNG-6700
> URL: https://issues.apache.org/jira/browse/MNG-6700
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
> Environment: macOS 10.14.4
> Oracle JDK 1.8.0_212
>Reporter: zhb
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 3.6.1 introduced a bug that same compile source are added multiple times.
> It seems that since 3.6.1, [this
> method|https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]
> is invoked multiple times, thus adding project root directory absolute path
> and "." [in this
> method|https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]
> twice. Unfortunately, {{new File(basedir, ".").getAbsolutePath()}} doesn't
> equal {{basedir.getAbsolutePath()}} -- the same source roots are added
> multiple times to {{compileSourceRoots}}.
>
> Step to reproduce:
> * git clone g...@github.com:gradle/gradle.git
> * cd gradle/.teamcity
> * (With maven 3.6.0) mvn compile - success
> * (WIth maven 3.6.1) mvn compile - failure
> Kotlin compiler complains a lot "Redeclaration: X".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [maven] asfgit closed pull request #266: [MNG-6700] - Same compile source roots are added multiple times
asfgit closed pull request #266: [MNG-6700] - Same compile source roots are added multiple times URL: https://github.com/apache/maven/pull/266 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Closed] (MNG-6660) duplicate classes error with source in the root directory
[
https://issues.apache.org/jira/browse/MNG-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6660.
---
Resolution: Duplicate
If you think this is not a duplicate of MNG-6700 please reopen and provide a
complete, minimal sample project.
> duplicate classes error with source in the root directory
> -
>
> Key: MNG-6660
> URL: https://issues.apache.org/jira/browse/MNG-6660
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.1
>Reporter: Luke Usherwood
>Priority: Minor
> Attachments: debug.log
>
>
> Trying to follow the instructions from
> [here|https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]
> which entails adding this little pom:
> {{
> 4.0.0
> org.bytedeco.hdf5
> H5tutrCmprss
> 1.5
>
> H5tutrCmprss
>
>
>
> org.bytedeco
> hdf5-platform
> 1.10.5-1.5
>
>
>
> .
>
> }}
> and a Java source file to the root directory. (There's code in the same link,
> but actually anything I think anything with a `main` function will do.)
> It does not seem to work with:
> {{.}}
> Yielding the strange error
> Compilation failure
> [ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class:
> H5tutrCmprss
> (Seen also in: MCOMPILER-235)
> However if I move the source under a sub-directory `src` and update the pom
> accordingly, it works fine. I assume that this pom worked "out of the box"
> once, so I wonder if this is a regression?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6660) duplicate classes error with source in the root directory
[
https://issues.apache.org/jira/browse/MNG-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6660:
Fix Version/s: (was: waiting-for-feedback)
> duplicate classes error with source in the root directory
> -
>
> Key: MNG-6660
> URL: https://issues.apache.org/jira/browse/MNG-6660
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.1
>Reporter: Luke Usherwood
>Priority: Minor
> Attachments: debug.log
>
>
> Trying to follow the instructions from
> [here|https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]
> which entails adding this little pom:
> {{
> 4.0.0
> org.bytedeco.hdf5
> H5tutrCmprss
> 1.5
>
> H5tutrCmprss
>
>
>
> org.bytedeco
> hdf5-platform
> 1.10.5-1.5
>
>
>
> .
>
> }}
> and a Java source file to the root directory. (There's code in the same link,
> but actually anything I think anything with a `main` function will do.)
> It does not seem to work with:
> {{.}}
> Yielding the strange error
> Compilation failure
> [ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class:
> H5tutrCmprss
> (Seen also in: MCOMPILER-235)
> However if I move the source under a sub-directory `src` and update the pom
> accordingly, it works fine. I assume that this pom worked "out of the box"
> once, so I wonder if this is a regression?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSITE-843) Upgrade Jetty to 9.2.28 with Jetty Security artifact
[ https://issues.apache.org/jira/browse/MSITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated MSITE-843: --- Summary: Upgrade Jetty to 9.2.28 with Jetty Security artifact (was: Upgrade Jetty to 9.2.9 with Jetty Security artifact) > Upgrade Jetty to 9.2.28 with Jetty Security artifact > > > Key: MSITE-843 > URL: https://issues.apache.org/jira/browse/MSITE-843 > Project: Maven Site Plugin > Issue Type: Dependency upgrade > Components: site:run >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Reworks MSITE-829 so that latest Jetty 9 @ Java 1.7 would be used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-surefire] eolivelli commented on issue #240: Extensions API and SPI. Polymorphism for remote and local process communication.
eolivelli commented on issue #240: Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-508952306 Great. I will take a deep look as soon as I am back at home This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (MDEP-619) snapshotsOnly is not respected when fuzziness is artifactId or groupId
[
https://issues.apache.org/jira/browse/MDEP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-619:
---
Summary: snapshotsOnly is not respected when fuzziness is artifactId or
groupId (was: snapshotsOnly is not always respected)
> snapshotsOnly is not respected when fuzziness is artifactId or groupId
> --
>
> Key: MDEP-619
> URL: https://issues.apache.org/jira/browse/MDEP-619
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: purge-local-repository
>Affects Versions: 3.1.1
> Environment: $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T20:49:05+01:00)
> Maven home: /usr/share/maven-bin-3.5
> Java version: 1.8.0_172, vendor: Oracle Corporation
> Java home: /opt/oracle-jdk-bin-1.8.0.172/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.9.76-gentoo-r1", arch: "amd64", family: "unix"
>Reporter: Joerg Schaible
>Priority: Major
>
> The configuration parameter snapshotsOnly is not always repected. We use a
> profile that can be activated in the root of a multi-project with following
> settings:
> {code:xml}
>
>
>
> purge
>
>
> purge-group
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> purge-local-repository
> clean
>
>
> purge-local-repository
>
>
>
> ${project.groupId}
>
> groupId
>
> ${purge}
>
>
>
>
>
>
>
> {code}
> We'd like to handle all artifacts with the same groupId. The purge parameter
> should be used to purge only the snapshots or anything. However, the
> snapshotOnly parameter is not respected. The goal will wipe always all
> artifacts with the same groupId.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-619) snapshotsOnly is not always respected
[
https://issues.apache.org/jira/browse/MDEP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879746#comment-16879746
]
Hervé Boutemy commented on MDEP-619:
that will require an important change in the algorithm: when fuzziness is
artifactId or groupId, currently the full artifact or group directories are
deleted
but in your case, a path transversal should be done to only select SNAPSHOT
versions directories
> snapshotsOnly is not always respected
> -
>
> Key: MDEP-619
> URL: https://issues.apache.org/jira/browse/MDEP-619
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: purge-local-repository
>Affects Versions: 3.1.1
> Environment: $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T20:49:05+01:00)
> Maven home: /usr/share/maven-bin-3.5
> Java version: 1.8.0_172, vendor: Oracle Corporation
> Java home: /opt/oracle-jdk-bin-1.8.0.172/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.9.76-gentoo-r1", arch: "amd64", family: "unix"
>Reporter: Joerg Schaible
>Priority: Major
>
> The configuration parameter snapshotsOnly is not always repected. We use a
> profile that can be activated in the root of a multi-project with following
> settings:
> {code:xml}
>
>
>
> purge
>
>
> purge-group
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> purge-local-repository
> clean
>
>
> purge-local-repository
>
>
>
> ${project.groupId}
>
> groupId
>
> ${purge}
>
>
>
>
>
>
>
> {code}
> We'd like to handle all artifacts with the same groupId. The purge parameter
> should be used to purge only the snapshots or anything. However, the
> snapshotOnly parameter is not respected. The goal will wipe always all
> artifacts with the same groupId.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-2893) Update the DefaultPluginManager to not use a project depMan for controlling its transitive dependencies
[ https://issues.apache.org/jira/browse/MNG-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-2893: --- Summary: Update the DefaultPluginManager to not use a project depMan for controlling its transitive dependencies (was: Update the DefaultPluginManager to not use a project depMan for controlling it's transitive dependencies) > Update the DefaultPluginManager to not use a project depMan for controlling > its transitive dependencies > --- > > Key: MNG-2893 > URL: https://issues.apache.org/jira/browse/MNG-2893 > Project: Maven > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 2.0.5 >Reporter: Jason van Zyl >Priority: Major > Fix For: 3.2.x, 3.6.x-candidate > > > An adjustment to MNG-1577. The classpath for plugins should not be affected > by a projects depMan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-5438) cli parameter to use a custom path settings-security.xml
[ https://issues.apache.org/jira/browse/MNG-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-5438: --- Fix Version/s: (was: 3.6.x-candidate) 3.7.0-candidate > cli parameter to use a custom path settings-security.xml > > > Key: MNG-5438 > URL: https://issues.apache.org/jira/browse/MNG-5438 > Project: Maven > Issue Type: New Feature > Components: Command Line >Affects Versions: 3.0.4, 3.0.5 >Reporter: Sarah Haselbauer >Priority: Major > Fix For: 3.7.0-candidate, 3.x / Backlog > > Attachments: MNG-5438-maven-embedder.patch, > apache-maven-3.0.4-ssec-bin.tar.gz, apache-maven-3.0.4-ssec-bin.zip, > maven-3.0.4-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch, > maven-latest-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch > > > added -ssec as cli param, so that you have the same flexibility to place your > settings-security.xml as you have to point to a custom settings.xml file > mvn -s /path/to/my/custom/settings.xml -ssec > /path/to/my/custom/settings-security.xml > I attached to patches: one that can be run on the maven-3.0.4 tag and one > that can be run on trunk (latest code state of today). > I also attached a maven-3.0.4-bin.zip (linux) so you can quickly try out the > feature and test it yourself. > if you like the idea, I would welcome to have this feature merged into one of > the next releases. I need it to write a puppet-maven module that allows to > download artifacts from maven repositories with encrypted passwords in the > puppet recipe. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-5600) Dependency management import should support exclusions.
[
https://issues.apache.org/jira/browse/MNG-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-5600:
---
Fix Version/s: (was: 3.6.x-candidate)
3.7.0-candidate
> Dependency management import should support exclusions.
> ---
>
> Key: MNG-5600
> URL: https://issues.apache.org/jira/browse/MNG-5600
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Radai Rosenblatt
>Priority: Major
> Fix For: 3.7.0-candidate
>
>
> suppose i have a multi-module project that uses spring, and so have this in
> dependency-managements in a parent pom:
> {code:xml}
>
> org.springframework
> spring-framework-bom
> ${org.springframework.version}
> pom
> import
>
> {code}
> spring artifacts (or at least a lot of them) have a dependency on
> commons-logging. right now, if i want to exclude commons-logging i have to
> add an exclusion to every spring dependency in every module of my project,
> which is actually more XML overall than giving up on using the bom dependency
> altogether and listing all spring dependencies with excludes once in the
> parent dependency management.
> I'd like to be able to do this:
> {code:xml}
>
> org.springframework
> spring-framework-bom
> ${org.springframework.version}
> pom
> import
>
>
> commons-logging
> commons-logging
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-5587) When the build fails emit any errors without the user having to specify -e or -X
[ https://issues.apache.org/jira/browse/MNG-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-5587: --- Fix Version/s: (was: 3.6.x-candidate) 3.7.0-candidate > When the build fails emit any errors without the user having to specify -e or > -X > > > Key: MNG-5587 > URL: https://issues.apache.org/jira/browse/MNG-5587 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.2.1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl >Priority: Major > Fix For: 3.7.0-candidate, 3.x / Backlog > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-5693) Change logging of MojoExceptions to console
[
https://issues.apache.org/jira/browse/MNG-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-5693:
---
Fix Version/s: (was: 3.6.x-candidate)
3.7.0-candidate
> Change logging of MojoExceptions to console
> ---
>
> Key: MNG-5693
> URL: https://issues.apache.org/jira/browse/MNG-5693
> Project: Maven
> Issue Type: Improvement
> Components: FDPFC, Plugin API
>Reporter: Robert Scholte
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.7.0-candidate
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If a plugin fails for any reason, a general message is logged with a
> reference to a wiki page, which never contains the real reason why the plugin
> failed.
> For new users this is very confusing. Even when we teach them to read, and
> they finally see a link, it's quite frustrating for them that they still
> don't know what happened.
> {{MojoExecutionException}} and {{MojoFailureException}} should never refer to
> a wikipage anymore.
> Plugin writers should get more control over the message written to the
> console.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-5868) Adding serval times the same artifact via MavenProjectHelper (attachArtifact) does not produce a failure
[
https://issues.apache.org/jira/browse/MNG-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-5868:
---
Fix Version/s: (was: 3.6.x-candidate)
3.7.0-candidate
> Adding serval times the same artifact via MavenProjectHelper (attachArtifact)
> does not produce a failure
> -
>
> Key: MNG-5868
> URL: https://issues.apache.org/jira/browse/MNG-5868
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.2.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.7.0-candidate
>
>
> During the check of an issue MSHADE-195 i stumbled over several things...
> If you take a look here and the log output excerpt:
> {noformat}
> INFO] Minimized 2341 -> 1293
> [INFO] Minimized 3282 -> 2234
> [INFO] Replacing original artifact with shaded artifact.
> [INFO] Replacing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT.jar
> with
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-shaded.jar
> [INFO] Replacing original source artifact with shaded source artifact.
> [INFO] Replacing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-sources.jar
> with
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-shaded-sources.jar
> [INFO] Dependency-reduced POM written at:
> /Users/kama/ws-git/apache/mshade/mshade-195/dependency-reduced-pom.xml
> [INFO]
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> MSHADE-195-example ---
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT.jar
> to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT.jar
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/dependency-reduced-pom.xml to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT.pom
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-sources.jar
> to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT-sources.jar
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-sources.jar
> to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT-sources.jar
> [INFO]
> {noformat}
> Install plugin tries to install two identical artifacts which will work for
> maven-install-plugin but would fail a deploy to repository manager (for
> releases) etc.
> So after diving into the problem i found the following code in maven-core
> (MavenProject.java):
> {code:java}
> /**
> * Add or replace an artifact. This method is now deprecated. Use the
> @{MavenProjectHelper} to attach artifacts to a
> * project. In spite of the 'throws' declaration on this API, this method
> has never thrown an exception since Maven
> * 3.0.x. Historically, it logged and ignored a second addition of the
> same g/a/v/c/t. Now it replaces the file for
> * the artifact, so that plugins (e.g. shade) can change the pathname of
> the file for a particular set of
> * coordinates.
> *
> * @param artifact the artifact to add or replace.
> * @throws DuplicateArtifactAttachmentException
> */
> public void addAttachedArtifact( Artifact artifact )
> throws DuplicateArtifactAttachmentException
> {
> getAttachedArtifacts().add( artifact );
> }
> public List getAttachedArtifacts()
> {
> if ( attachedArtifacts == null )
> {
> attachedArtifacts = new ArrayList<>();
> }
> return attachedArtifacts;
> }
> {code}
> So taking a look into MavenProjectHelper.java and the implementation
> (DefaultMavenProjectHelper.java).
> {code:java}
> /**
> * Add an attached artifact or replace the file for an existing artifact.
> *
> * @see
> MavenProject#addAttachedArtifact(org.apache.maven.artifact.Artifact)
> * @param project project reference.
> * @param artifact artifact to add or replace.
> */
> public void attachArtifact( MavenProject project, Artifact artifact )
> {
> project.addAttachedArtifact( artifact );
> }
> {code}
> which means that there is not check if an artifacts is already attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6389) Move the toolchains model to a separate artifactId
[ https://issues.apache.org/jira/browse/MNG-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6389: --- Fix Version/s: (was: 3.6.x-candidate) 3.7.0-candidate > Move the toolchains model to a separate artifactId > -- > > Key: MNG-6389 > URL: https://issues.apache.org/jira/browse/MNG-6389 > Project: Maven > Issue Type: Improvement > Components: Toolchains >Affects Versions: 3.5.3 >Reporter: George Gastaldi >Priority: Major > Fix For: 3.7.0-candidate > > > Just as maven-model and maven-settings, it would be nice to have a > maven-toolchains artifactId containing only the model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-5227) The 'optional' flag of a dependency should be manageable.
[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-5227:
---
Fix Version/s: (was: 3.6.x-candidate)
3.7.0-candidate
> The 'optional' flag of a dependency should be manageable.
> -
>
> Key: MNG-5227
> URL: https://issues.apache.org/jira/browse/MNG-5227
> Project: Maven
> Issue Type: New Feature
> Components: Artifacts and Repositories
>Affects Versions: 3.0.3
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: 3.7.0-candidate
>
> Attachments: MNG-5227.patch, MNG-5227.patch
>
>
> {code}
>
>
>
> groupId
> artifactId
> version
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [maven] michael-o removed a comment on issue #260: Speed improvements
michael-o removed a comment on issue #260: Speed improvements URL: https://github.com/apache/maven/pull/260#issuecomment-508946402 Can you please move out the changes in the `DefaultModelValidator` to a separate ticket? Its a large diff. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven] michael-o commented on issue #260: Speed improvements
michael-o commented on issue #260: Speed improvements URL: https://github.com/apache/maven/pull/260#issuecomment-508946402 Can you please move out the changes in the `DefaultModelValidator` to a separate ticket? Its a large diff. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Assigned] (MNG-6698) Lazily compute the ManagedVersionMap
[ https://issues.apache.org/jira/browse/MNG-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-6698: --- Assignee: Michael Osipov > Lazily compute the ManagedVersionMap > > > Key: MNG-6698 > URL: https://issues.apache.org/jira/browse/MNG-6698 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.6.1 >Reporter: Guillaume Nodet >Assignee: Michael Osipov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6698) Lazily compute the ManagedVersionMap
[ https://issues.apache.org/jira/browse/MNG-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6698: Fix Version/s: 3.6.x-candidate > Lazily compute the ManagedVersionMap > > > Key: MNG-6698 > URL: https://issues.apache.org/jira/browse/MNG-6698 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.6.1 >Reporter: Guillaume Nodet >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.x-candidate > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven] michael-o commented on issue #263: [MNG-6698] Improve the ManagedVersionMap
michael-o commented on issue #263: [MNG-6698] Improve the ManagedVersionMap URL: https://github.com/apache/maven/pull/263#issuecomment-508944889 While I understand the diff, I don't understand "This map is not used by maven". Who uses this map? Plugins? Other components from our ecosystem? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven] hboutemy opened a new pull request #267: [MNG-6549] Remove unused transitive dependencies of Guava
hboutemy opened a new pull request #267: [MNG-6549] Remove unused transitive dependencies of Guava URL: https://github.com/apache/maven/pull/267 while at it, did a little bit of cleanup: - removed aopalliance (like done in maven-resolver-provider) - removed guice dependency management that should be part of MNG-6475 see https://issues.apache.org/jira/browse/MNG-6549 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (MNG-6660) duplicate classes error with source in the root directory
[
https://issues.apache.org/jira/browse/MNG-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6660:
Description:
Trying to follow the instructions from
[here|https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]
which entails adding this little pom:
{{
4.0.0
org.bytedeco.hdf5
H5tutrCmprss
1.5
H5tutrCmprss
org.bytedeco
hdf5-platform
1.10.5-1.5
.
}}
and a Java source file to the root directory. (There's code in the same link,
but actually anything I think anything with a `main` function will do.)
It does not seem to work with:
{{.}}
Yielding the strange error
Compilation failure
[ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class:
H5tutrCmprss
(Seen also in: MCOMPILER-235)
However if I move the source under a sub-directory `src` and update the pom
accordingly, it works fine. I assume that this pom worked "out of the box"
once, so I wonder if this is a regression?
was:
Trying to follow the instructions from
[here|[https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]]
which entails adding this little pom:
{{
4.0.0
org.bytedeco.hdf5
H5tutrCmprss
1.5
H5tutrCmprss
org.bytedeco
hdf5-platform
1.10.5-1.5
.
}}
and a Java source file to the root directory. (There's code in the same link,
but actually anything I think anything with a `main` function will do.)
It does not seem to work with:
{{.}}
Yielding the strange error
Compilation failure
[ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class:
H5tutrCmprss
(Seen also in: MCOMPILER-235)
However if I move the source under a sub-directory `src` and update the pom
accordingly, it works fine. I assume that this pom worked "out of the box"
once, so I wonder if this is a regression?
> duplicate classes error with source in the root directory
> -
>
> Key: MNG-6660
> URL: https://issues.apache.org/jira/browse/MNG-6660
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.1
>Reporter: Luke Usherwood
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: debug.log
>
>
> Trying to follow the instructions from
> [here|https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]
> which entails adding this little pom:
> {{
> 4.0.0
> org.bytedeco.hdf5
> H5tutrCmprss
> 1.5
>
> H5tutrCmprss
>
>
>
> org.bytedeco
> hdf5-platform
> 1.10.5-1.5
>
>
>
> .
>
> }}
> and a Java source file to the root directory. (There's code in the same link,
> but actually anything I think anything with a `main` function will do.)
> It does not seem to work with:
> {{.}}
> Yielding the strange error
> Compilation failure
> [ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class:
> H5tutrCmprss
> (Seen also in: MCOMPILER-235)
> However if I move the source under a sub-directory `src` and update the pom
> accordingly, it works fine. I assume that this pom worked "out of the box"
> once, so I wonder if this is a regression?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MNG-6688) When some error is found and fixed, maven does something for minutes before it stops again if there are other errors
[ https://issues.apache.org/jira/browse/MNG-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6688. --- Resolution: Not A Problem > When some error is found and fixed, maven does something for minutes before > it stops again if there are other errors > > > Key: MNG-6688 > URL: https://issues.apache.org/jira/browse/MNG-6688 > Project: Maven > Issue Type: Bug >Reporter: Yuri >Priority: Major > > I am trying to make Hadoop work on FreeBSD. I need to fix some issues. > > Every time I fix something in the C++ code and rerun maven, it first does > something for minutes before stopping for the next issue in the nearby code. > > Maven should be target-based, and skip targets that have been built. cmake > and gmake do this. > > The turnaround time problem is certainly very bad for development. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6549) Remove unused transitive dependencies of Guava
[
https://issues.apache.org/jira/browse/MNG-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6549:
---
Description:
With MNG-6475 we excluded explicit dependency to Guava but it's still required
by Guice and then packaged with all dependencies to the installation package.
Unfortunately, we pack few dependencies that are not required at runtime so we
can skip and decrease the size of the Maven package.
{noformat}
com.google.inject:guice:jar:no_aop:4.2.1:compile
- aopalliance:aopalliance:jar:1.0:compile
- com.google.guava:guava:jar:25.1-android:compile
- com.google.code.findbugs:jsr305:jar:3.0.2:compile
- org.checkerframework:checker-compat-qual:jar:2.0.0:compile
- com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
- com.google.j2objc:j2objc-annotations:jar:1.1:compile
- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
{noformat}
was:
With MNG-6475 we excluded explicit dependency to Guava but it's still required
by Guice and then packaged with all dependencies to the installation package.
Unfortunately, we pack few dependencies that are not required at runtime so we
can skip and decrease the size of the Maven package.
{code:java}
com.google.inject:guice:jar:no_aop:4.2.1:compile
- aopalliance:aopalliance:jar:1.0:compile
- com.google.guava:guava:jar:25.1-android:compile
- com.google.code.findbugs:jsr305:jar:3.0.2:compile
- org.checkerframework:checker-compat-qual:jar:2.0.0:compile
- com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
- com.google.j2objc:j2objc-annotations:jar:1.1:compile
- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
{code}
> Remove unused transitive dependencies of Guava
> --
>
> Key: MNG-6549
> URL: https://issues.apache.org/jira/browse/MNG-6549
> Project: Maven
> Issue Type: Dependency upgrade
> Components: Dependencies
>Affects Versions: 3.6.0
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.6.x-candidate, waiting-for-feedback
>
>
> With MNG-6475 we excluded explicit dependency to Guava but it's still
> required by Guice and then packaged with all dependencies to the installation
> package.
> Unfortunately, we pack few dependencies that are not required at runtime so
> we can skip and decrease the size of the Maven package.
> {noformat}
> com.google.inject:guice:jar:no_aop:4.2.1:compile
> - aopalliance:aopalliance:jar:1.0:compile
> - com.google.guava:guava:jar:25.1-android:compile
>- com.google.code.findbugs:jsr305:jar:3.0.2:compile
>- org.checkerframework:checker-compat-qual:jar:2.0.0:compile
>- com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
>- com.google.j2objc:j2objc-annotations:jar:1.1:compile
>- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6549) Remove unused transitive dependencies of Guava
[
https://issues.apache.org/jira/browse/MNG-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6549:
---
Affects Version/s: 3.6.0
> Remove unused transitive dependencies of Guava
> --
>
> Key: MNG-6549
> URL: https://issues.apache.org/jira/browse/MNG-6549
> Project: Maven
> Issue Type: Dependency upgrade
> Components: Dependencies
>Affects Versions: 3.6.0
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.6.x-candidate, waiting-for-feedback
>
>
> With MNG-6475 we excluded explicit dependency to Guava but it's still
> required by Guice and then packaged with all dependencies to the installation
> package.
> Unfortunately, we pack few dependencies that are not required at runtime so
> we can skip and decrease the size of the Maven package.
>
> {code:java}
> com.google.inject:guice:jar:no_aop:4.2.1:compile
> - aopalliance:aopalliance:jar:1.0:compile
> - com.google.guava:guava:jar:25.1-android:compile
>- com.google.code.findbugs:jsr305:jar:3.0.2:compile
>- org.checkerframework:checker-compat-qual:jar:2.0.0:compile
>- com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
>- com.google.j2objc:j2objc-annotations:jar:1.1:compile
>- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6688) When some error is found and fixed, maven does something for minutes before it stops again if there are other errors
[ https://issues.apache.org/jira/browse/MNG-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879726#comment-16879726 ] Yuri commented on MNG-6688: --- This issue is resolved, Michael. Thank you for your answer. Please close this issue. > When some error is found and fixed, maven does something for minutes before > it stops again if there are other errors > > > Key: MNG-6688 > URL: https://issues.apache.org/jira/browse/MNG-6688 > Project: Maven > Issue Type: Bug >Reporter: Yuri >Priority: Major > > I am trying to make Hadoop work on FreeBSD. I need to fix some issues. > > Every time I fix something in the C++ code and rerun maven, it first does > something for minutes before stopping for the next issue in the nearby code. > > Maven should be target-based, and skip targets that have been built. cmake > and gmake do this. > > The turnaround time problem is certainly very bad for development. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6700) Equal compile source roots are added multiple times
[
https://issues.apache.org/jira/browse/MNG-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6700:
Fix Version/s: (was: 3.6.x-candidate)
3.6.2
> Equal compile source roots are added multiple times
> ---
>
> Key: MNG-6700
> URL: https://issues.apache.org/jira/browse/MNG-6700
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
> Environment: macOS 10.14.4
> Oracle JDK 1.8.0_212
>Reporter: zhb
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 3.6.1 introduced a bug that same compile source are added multiple times.
> It seems that since 3.6.1, [this
> method|https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]
> is invoked multiple times, thus adding project root directory absolute path
> and "." [in this
> method|https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]
> twice. Unfortunately, {{new File(basedir, ".").getAbsolutePath()}} doesn't
> equal {{basedir.getAbsolutePath()}} -- the same source roots are added
> multiple times to {{compileSourceRoots}}.
>
> Step to reproduce:
> * git clone g...@github.com:gradle/gradle.git
> * cd gradle/.teamcity
> * (With maven 3.6.0) mvn compile - success
> * (WIth maven 3.6.1) mvn compile - failure
> Kotlin compiler complains a lot "Redeclaration: X".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6660) duplicate classes error with source in the root directory
[
https://issues.apache.org/jira/browse/MNG-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6660:
Fix Version/s: waiting-for-feedback
> duplicate classes error with source in the root directory
> -
>
> Key: MNG-6660
> URL: https://issues.apache.org/jira/browse/MNG-6660
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.1
>Reporter: Luke Usherwood
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: debug.log
>
>
> Trying to follow the instructions from
> [here|[https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]]
> which entails adding this little pom:
> {{
> 4.0.0
> org.bytedeco.hdf5
> H5tutrCmprss
> 1.5
>
> H5tutrCmprss
>
>
>
> org.bytedeco
> hdf5-platform
> 1.10.5-1.5
>
>
>
> .
>
> }}
> and a Java source file to the root directory. (There's code in the same link,
> but actually anything I think anything with a `main` function will do.)
> It does not seem to work with:
> {{.}}
> Yielding the strange error
> Compilation failure
> [ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class:
> H5tutrCmprss
> (Seen also in: MCOMPILER-235)
> However if I move the source under a sub-directory `src` and update the pom
> accordingly, it works fine. I assume that this pom worked "out of the box"
> once, so I wonder if this is a regression?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6660) duplicate classes error with source in the root directory
[
https://issues.apache.org/jira/browse/MNG-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879722#comment-16879722
]
Michael Osipov commented on MNG-6660:
-
This is likely a dup of MNG-6700 which has a valid PR.
> duplicate classes error with source in the root directory
> -
>
> Key: MNG-6660
> URL: https://issues.apache.org/jira/browse/MNG-6660
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.1
>Reporter: Luke Usherwood
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: debug.log
>
>
> Trying to follow the instructions from
> [here|[https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]]
> which entails adding this little pom:
> {{
> 4.0.0
> org.bytedeco.hdf5
> H5tutrCmprss
> 1.5
>
> H5tutrCmprss
>
>
>
> org.bytedeco
> hdf5-platform
> 1.10.5-1.5
>
>
>
> .
>
> }}
> and a Java source file to the root directory. (There's code in the same link,
> but actually anything I think anything with a `main` function will do.)
> It does not seem to work with:
> {{.}}
> Yielding the strange error
> Compilation failure
> [ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class:
> H5tutrCmprss
> (Seen also in: MCOMPILER-235)
> However if I move the source under a sub-directory `src` and update the pom
> accordingly, it works fine. I assume that this pom worked "out of the box"
> once, so I wonder if this is a regression?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MNG-6649) Duplicate class error in maven-compiler-plugin
[
https://issues.apache.org/jira/browse/MNG-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6649.
---
Resolution: Duplicate
The sample project passes with the PR for MNG-6700:
{noformat}
PS D:\Entwicklung\Projekte\repro>
D:\Entwicklung\Programme\apache-maven-3.6.2-SNAPSHOT\bin\mvn.cmd package
"-DtargetDirectory=C:\temp"
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] XYZ[pom]
[INFO] dsl[jar]
[INFO]
[INFO] ---< com.microsoft.mavenerrors:XYZ >
[INFO] Building XYZ 6.19.0-private[1/2]
[INFO] [ pom ]-
[INFO]
[INFO] ---< com.microsoft.mavenerrors:dsl >
[INFO] Building dsl 6.19.0-private[2/2]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ dsl ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\repro\Java\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ dsl ---
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e.
build is platform dependent!
[INFO] Compiling 1 source file to C:\temp\classes
[WARNING]
/D:/Entwicklung/Projekte/repro/Java/src/com/microsoft/mavenerrors/Tuple.java:
D:\Entwicklung\Projekte\repro\Java\src\com\microsoft\mavenerrors\Tuple.java
uses unchecked or unsafe operations.
[WARNING]
/D:/Entwicklung/Projekte/repro/Java/src/com/microsoft/mavenerrors/Tuple.java:
Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
dsl ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\repro\Java\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ dsl ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ dsl ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ dsl ---
[INFO] Building jar: C:\temp\dsl-6.19.0-private.jar
[INFO]
[INFO] Reactor Summary for XYZ 6.19.0-private:
[INFO]
[INFO] XYZ SUCCESS [ 0.141 s]
[INFO] dsl SUCCESS [ 1.957 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.518 s
[INFO] Finished at: 2019-07-06T18:37:47+02:00
[INFO]
PS D:\Entwicklung\Projekte\repro>
{noformat}
> Duplicate class error in maven-compiler-plugin
> --
>
> Key: MNG-6649
> URL: https://issues.apache.org/jira/browse/MNG-6649
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.6.1
> Environment: maven version 3.6.1
> OpenJDK8 installed using choco's zulu8 package.
>Reporter: Kunal
>Priority: Trivial
> Attachments: repro.zip
>
>
> When trying to run `mvn package` the `maven-compiler-plugin` fails with maven
> 3.6.1 with below errors. It works with maven's 3.6.0.
> {noformat}
> [ERROR] /AccessStep.java:[12,8] duplicate class:
> com.microsoft.programSynthesis.wrangling.json.jPathStep.AccessStep
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project dsl: Compilation failure
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
>
[jira] [Updated] (MNG-6700) Equal compile source roots are added multiple times
[
https://issues.apache.org/jira/browse/MNG-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6700:
Summary: Equal compile source roots are added multiple times (was: Compile
source roots are added multiple times)
> Equal compile source roots are added multiple times
> ---
>
> Key: MNG-6700
> URL: https://issues.apache.org/jira/browse/MNG-6700
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
> Environment: macOS 10.14.4
> Oracle JDK 1.8.0_212
>Reporter: zhb
>Assignee: Michael Osipov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 3.6.1 introduced a bug that same compile source are added multiple times.
> It seems that since 3.6.1, [this
> method|https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]
> is invoked multiple times, thus adding project root directory absolute path
> and "." [in this
> method|https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]
> twice. Unfortunately, {{new File(basedir, ".").getAbsolutePath()}} doesn't
> equal {{basedir.getAbsolutePath()}} -- the same source roots are added
> multiple times to {{compileSourceRoots}}.
>
> Step to reproduce:
> * git clone g...@github.com:gradle/gradle.git
> * cd gradle/.teamcity
> * (With maven 3.6.0) mvn compile - success
> * (WIth maven 3.6.1) mvn compile - failure
> Kotlin compiler complains a lot "Redeclaration: X".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6700) Equal compile source roots are added multiple times
[
https://issues.apache.org/jira/browse/MNG-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6700:
Fix Version/s: 3.6.x-candidate
> Equal compile source roots are added multiple times
> ---
>
> Key: MNG-6700
> URL: https://issues.apache.org/jira/browse/MNG-6700
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
> Environment: macOS 10.14.4
> Oracle JDK 1.8.0_212
>Reporter: zhb
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.x-candidate
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 3.6.1 introduced a bug that same compile source are added multiple times.
> It seems that since 3.6.1, [this
> method|https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]
> is invoked multiple times, thus adding project root directory absolute path
> and "." [in this
> method|https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]
> twice. Unfortunately, {{new File(basedir, ".").getAbsolutePath()}} doesn't
> equal {{basedir.getAbsolutePath()}} -- the same source roots are added
> multiple times to {{compileSourceRoots}}.
>
> Step to reproduce:
> * git clone g...@github.com:gradle/gradle.git
> * cd gradle/.teamcity
> * (With maven 3.6.0) mvn compile - success
> * (WIth maven 3.6.1) mvn compile - failure
> Kotlin compiler complains a lot "Redeclaration: X".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MNG-6700) Compile source roots are added multiple times
[
https://issues.apache.org/jira/browse/MNG-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MNG-6700:
---
Assignee: Michael Osipov
> Compile source roots are added multiple times
> -
>
> Key: MNG-6700
> URL: https://issues.apache.org/jira/browse/MNG-6700
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
> Environment: macOS 10.14.4
> Oracle JDK 1.8.0_212
>Reporter: zhb
>Assignee: Michael Osipov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 3.6.1 introduced a bug that same compile source are added multiple times.
> It seems that since 3.6.1, [this
> method|https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]
> is invoked multiple times, thus adding project root directory absolute path
> and "." [in this
> method|https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]
> twice. Unfortunately, {{new File(basedir, ".").getAbsolutePath()}} doesn't
> equal {{basedir.getAbsolutePath()}} -- the same source roots are added
> multiple times to {{compileSourceRoots}}.
>
> Step to reproduce:
> * git clone g...@github.com:gradle/gradle.git
> * cd gradle/.teamcity
> * (With maven 3.6.0) mvn compile - success
> * (WIth maven 3.6.1) mvn compile - failure
> Kotlin compiler complains a lot "Redeclaration: X".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6700) Compile source roots are added multiple times
[
https://issues.apache.org/jira/browse/MNG-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6700:
Description:
3.6.1 introduced a bug that same compile source are added multiple times.
It seems that since 3.6.1, [this
method|https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]
is invoked multiple times, thus adding project root directory absolute path
and "." [in this
method|https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]
twice. Unfortunately, {{new File(basedir, ".").getAbsolutePath()}} doesn't
equal {{basedir.getAbsolutePath()}} -- the same source roots are added multiple
times to {{compileSourceRoots}}.
Step to reproduce:
* git clone g...@github.com:gradle/gradle.git
* cd gradle/.teamcity
* (With maven 3.6.0) mvn compile - success
* (WIth maven 3.6.1) mvn compile - failure
Kotlin compiler complains a lot "Redeclaration: X".
was:
3.6.1 introduced a bug that same compile source are added multiple times.
It seems that since 3.6.1, [this
method|[https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]]
is invoked multiple times, thus adding project root directory absolute path
and "." [in this
method|[https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]]
twice. Unfortunately, `new File(basedir, ".").getAbsolutePath()` doesn't equal
`basedir.getAbsolutePath()` - the same source roots are added multiple times to
`compileSourceRoots`.
Step to reproduce:
* git clone g...@github.com:gradle/gradle.git
* cd gradle/.teamcity
* (With maven 3.6.0) mvn compile - success
* (WIth maven 3.6.1) mvn compile - failure
Kotlin compiler complains a lot "Redeclaration: X".
> Compile source roots are added multiple times
> -
>
> Key: MNG-6700
> URL: https://issues.apache.org/jira/browse/MNG-6700
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
> Environment: macOS 10.14.4
> Oracle JDK 1.8.0_212
>Reporter: zhb
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 3.6.1 introduced a bug that same compile source are added multiple times.
> It seems that since 3.6.1, [this
> method|https://github.com/apache/maven/blob/24c762d7c3d66607e620fddb0743c7eadd041107/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java#L855]
> is invoked multiple times, thus adding project root directory absolute path
> and "." [in this
> method|https://github.com/apache/maven/blob/0940c7c9730eac23fd8598f3fb51520ee774761b/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L295]
> twice. Unfortunately, {{new File(basedir, ".").getAbsolutePath()}} doesn't
> equal {{basedir.getAbsolutePath()}} -- the same source roots are added
> multiple times to {{compileSourceRoots}}.
>
> Step to reproduce:
> * git clone g...@github.com:gradle/gradle.git
> * cd gradle/.teamcity
> * (With maven 3.6.0) mvn compile - success
> * (WIth maven 3.6.1) mvn compile - failure
> Kotlin compiler complains a lot "Redeclaration: X".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6615) Failed to execute mvn site command for any project, including brand new
[ https://issues.apache.org/jira/browse/MNG-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879719#comment-16879719 ] Michael Osipov commented on MNG-6615: - Did you use the Maven Archetype Plugin? Can you provide the exact input? > Failed to execute mvn site command for any project, including brand new > --- > > Key: MNG-6615 > URL: https://issues.apache.org/jira/browse/MNG-6615 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Mykyta Bezverkhyi >Priority: Major > > Steps to reproduce: > # Create project of any archetype using Maven 3.6.0. > # Execute _mvn site_ command. > *Actual result:* [INFO] BUILD FAILURE > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project > test: > Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.3:site failed: > A required class was missing while executing > org.apache.maven.plugins:maven-site-plugin:3.3:site: > org/apache/maven/doxia/siterenderer/DocumentContent > *Expected result:* [INFO] BUILD SUCCESS > Notes: As far as I know it can be fixed by updating _maven-site-plugin_ > version to the latest one, currently _3.7.1_, but it's kinda annoying to do > this for all of the projects and trying to remember what you did to fix it > coding the new one. So I think it makes sense for you to update the default > plugin version to _3.7.1_ in your next release, or to fix it in the way you > want. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6615) Failed to execute mvn site command for any project, including brand new
[ https://issues.apache.org/jira/browse/MNG-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6615: Fix Version/s: waiting-for-feedback > Failed to execute mvn site command for any project, including brand new > --- > > Key: MNG-6615 > URL: https://issues.apache.org/jira/browse/MNG-6615 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Mykyta Bezverkhyi >Priority: Major > Fix For: waiting-for-feedback > > > Steps to reproduce: > # Create project of any archetype using Maven 3.6.0. > # Execute _mvn site_ command. > *Actual result:* [INFO] BUILD FAILURE > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project > test: > Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.3:site failed: > A required class was missing while executing > org.apache.maven.plugins:maven-site-plugin:3.3:site: > org/apache/maven/doxia/siterenderer/DocumentContent > *Expected result:* [INFO] BUILD SUCCESS > Notes: As far as I know it can be fixed by updating _maven-site-plugin_ > version to the latest one, currently _3.7.1_, but it's kinda annoying to do > this for all of the projects and trying to remember what you did to fix it > coding the new one. So I think it makes sense for you to update the default > plugin version to _3.7.1_ in your next release, or to fix it in the way you > want. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6688) When some error is found and fixed, maven does something for minutes before it stops again if there are other errors
[ https://issues.apache.org/jira/browse/MNG-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879718#comment-16879718 ] Michael Osipov commented on MNG-6688: - [~yurivict], is there anything left to resolve here or can we close this issue? > When some error is found and fixed, maven does something for minutes before > it stops again if there are other errors > > > Key: MNG-6688 > URL: https://issues.apache.org/jira/browse/MNG-6688 > Project: Maven > Issue Type: Bug >Reporter: Yuri >Priority: Major > > I am trying to make Hadoop work on FreeBSD. I need to fix some issues. > > Every time I fix something in the C++ code and rerun maven, it first does > something for minutes before stopping for the next issue in the nearby code. > > Maven should be target-based, and skip targets that have been built. cmake > and gmake do this. > > The turnaround time problem is certainly very bad for development. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNG-6701) Document maven.repo.local system property
[ https://issues.apache.org/jira/browse/MNG-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6701. --- Resolution: Fixed Fixed with [8da81ce73ca9cdeebbd89ecb1bb04556a19e46e8|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=8da81ce73ca9cdeebbd89ecb1bb04556a19e46e8].. > Document maven.repo.local system property > - > > Key: MNG-6701 > URL: https://issues.apache.org/jira/browse/MNG-6701 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: 3.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Per a team member, maven.repo.local "is supported by the MavenCli class which > uses the value to set the local repository. But beyond multiple references in > StackOverflow and the Maven JIRA, I don't see it referenced in any official > documentation for Maven 3.x, just Maven 1.x." > 1.x docs are here: > https://maven.apache.org/archives/maven-1.x/reference/properties.html#Maven_Configuration_Properties > It may be that we need a similar page for Maven 3.x. There could well be > other properties that should be documented too. I don't see it here, for > example: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Properties+Guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven] asfgit closed pull request #265: (doc) MNGSITE-353: Document maven.repo.local property
asfgit closed pull request #265: (doc) MNGSITE-353: Document maven.repo.local property URL: https://github.com/apache/maven/pull/265 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-surefire] Tibor17 edited a comment on issue #240: Extensions API and SPI. Polymorphism for remote and local process communication.
Tibor17 edited a comment on issue #240: Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-508937319 @eolivelli Here is the long awaited abstraction for remote communication between processes. Pls see the class (extension-api) `ForkedChannelServer` and internal class `NetworkingProcessExecutor`. This integrates two things (maven process side - new tcp/ip server in our case): 1. execution of Jar file via CLI 2. the communication between processes It is a polymorphism which means that the standard pipes would work as well but the TCP connector is our default favorite. The implementation can be changed by user in POM `... implementation="..."`. You have to extract the Line 607 from `ForkStarter` adapt it in the fasion we need in the communication level and use it in `NetworkingProcessExecutor` and `PipeProcessExecutor`. The lines 607 - 608 represent the modification of the original code in `ForkStarter` which will be substituted by the polymorhism. There are two modules. The `surefire-extensions-api` for the above extension and `surefire-extensions-spi` used as a typical SPI in a forked JMV which includes the command decoder. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-surefire] Tibor17 commented on issue #240: Extensions API and SPI. Polymorphism for remote and local process communication.
Tibor17 commented on issue #240: Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-508937319 @eolivelli Here is the long awaited abstraction for remote communication between processes. Pls see the class (extension-api) `ForkedChannelServer` and internal class `NetworkingProcessExecutor`. This integrates two things (maven process side - new tcp/ip server in our case): 1. execution of Jar file via CLI 2. the communication between processes It is a polymorphism which means that the standard pipes would work as well but the TCP connector is our default favorite. The implementation can be changed by user in POM `... implementation="..."`. You has to extract the Line 607 from `ForkStarter` adapt it in the fasion we need in the communication level and use it in `NetworkingProcessExecutor` and `PipeProcessExecutor`. The lines 607 - 608 represent the modification of the original code in `ForkStarter` which will be substituted by the polymorhism. There are two modules. The `surefire-extensions-api` for the above extension and `surefire-extensions-spi` used as a typical SPI in a forked JMV which includes the command decoder. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (MNG-6549) Remove unused transitive dependencies of Guava
[
https://issues.apache.org/jira/browse/MNG-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6549:
---
Summary: Remove unused transitive dependencies of Guava (was: Remove
unused inherited dependencies of Guava)
> Remove unused transitive dependencies of Guava
> --
>
> Key: MNG-6549
> URL: https://issues.apache.org/jira/browse/MNG-6549
> Project: Maven
> Issue Type: Dependency upgrade
> Components: Dependencies
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.6.x-candidate, waiting-for-feedback
>
>
> With MNG-6475 we excluded explicit dependency to Guava but it's still
> required by Guice and then packaged with all dependencies to the installation
> package.
> Unfortunately, we pack few dependencies that are not required at runtime so
> we can skip and decrease the size of the Maven package.
>
> {code:java}
> com.google.inject:guice:jar:no_aop:4.2.1:compile
> - aopalliance:aopalliance:jar:1.0:compile
> - com.google.guava:guava:jar:25.1-android:compile
>- com.google.code.findbugs:jsr305:jar:3.0.2:compile
>- org.checkerframework:checker-compat-qual:jar:2.0.0:compile
>- com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
>- com.google.j2objc:j2objc-annotations:jar:1.1:compile
>- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6399) Lift JDK minimum to JDK 8
[ https://issues.apache.org/jira/browse/MNG-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6399: --- Fix Version/s: (was: 3.6.x-candidate) 3.7.0-candidate > Lift JDK minimum to JDK 8 > - > > Key: MNG-6399 > URL: https://issues.apache.org/jira/browse/MNG-6399 > Project: Maven > Issue Type: Task >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.7.0-candidate > > > I would like to lift the minimum of Maven Core to JDK 8 (I think it's time).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-surefire] Tibor17 opened a new pull request #240: Extensions API and SPI. Polymorphism for remote and local process communication.
Tibor17 opened a new pull request #240: Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Moved] (MNG-6701) Document maven.repo.local system property
[ https://issues.apache.org/jira/browse/MNG-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov moved MNGSITE-353 to MNG-6701: - Key: MNG-6701 (was: MNGSITE-353) Project: Maven (was: Maven Project Web Site) > Document maven.repo.local system property > - > > Key: MNG-6701 > URL: https://issues.apache.org/jira/browse/MNG-6701 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Time Spent: 10m > Remaining Estimate: 0h > > Per a team member, maven.repo.local "is supported by the MavenCli class which > uses the value to set the local repository. But beyond multiple references in > StackOverflow and the Maven JIRA, I don't see it referenced in any official > documentation for Maven 3.x, just Maven 1.x." > 1.x docs are here: > https://maven.apache.org/archives/maven-1.x/reference/properties.html#Maven_Configuration_Properties > It may be that we need a similar page for Maven 3.x. There could well be > other properties that should be documented too. I don't see it here, for > example: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Properties+Guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6701) Document maven.repo.local system property
[ https://issues.apache.org/jira/browse/MNG-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6701: Fix Version/s: 3.6.2 > Document maven.repo.local system property > - > > Key: MNG-6701 > URL: https://issues.apache.org/jira/browse/MNG-6701 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: 3.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > > Per a team member, maven.repo.local "is supported by the MavenCli class which > uses the value to set the local repository. But beyond multiple references in > StackOverflow and the Maven JIRA, I don't see it referenced in any official > documentation for Maven 3.x, just Maven 1.x." > 1.x docs are here: > https://maven.apache.org/archives/maven-1.x/reference/properties.html#Maven_Configuration_Properties > It may be that we need a similar page for Maven 3.x. There could well be > other properties that should be documented too. I don't see it here, for > example: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Properties+Guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MNGSITE-353) Document maven.repo.local system property
[ https://issues.apache.org/jira/browse/MNGSITE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNGSITE-353: -- Assignee: Michael Osipov > Document maven.repo.local system property > - > > Key: MNGSITE-353 > URL: https://issues.apache.org/jira/browse/MNGSITE-353 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Time Spent: 10m > Remaining Estimate: 0h > > Per a team member, maven.repo.local "is supported by the MavenCli class which > uses the value to set the local repository. But beyond multiple references in > StackOverflow and the Maven JIRA, I don't see it referenced in any official > documentation for Maven 3.x, just Maven 1.x." > 1.x docs are here: > https://maven.apache.org/archives/maven-1.x/reference/properties.html#Maven_Configuration_Properties > It may be that we need a similar page for Maven 3.x. There could well be > other properties that should be documented too. I don't see it here, for > example: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Properties+Guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven] michael-o commented on a change in pull request #264: [MNG-6535] Improve test coverage of UrlNormalizer.
michael-o commented on a change in pull request #264: [MNG-6535] Improve test
coverage of UrlNormalizer.
URL: https://github.com/apache/maven/pull/264#discussion_r300834002
##
File path:
maven-model-builder/src/test/java/org/apache/maven/model/path/DefaultUrlNormalizerTest.java
##
@@ -82,4 +82,8 @@ public void testPreservationOfDoubleSlashes()
normalize(
"[fetch=]http://server.org/[push=]ssh://server.org/; ) );
}
+public void testNormalizeInputWithNoParentDirectoriesToAscendTo()
+{
+assertEquals("a/../", normalize("a/../"));
+}
Review comment:
If we normalize URLs, the test for relative paths must fail. URLs are
absolute.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
Re: [jira] [Commented] (MNG-6691) Maven protocol specification
Just fyi, am aware of 3+2 oss solutions out there (the +2 are the trimmed ones) On Sat, Jul 6, 2019, 00:26 dzikoysk (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/MNG-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879546#comment-16879546 > ] > > dzikoysk commented on MNG-6691: > --- > > Yeah, it's what we need to do now and it's why I'm loking for something > better. At this moment, we have only 3 open source repository managers > where 2 of them are just trimmed-down versions of pro (commercial) software > that is huge and heavy - honestly, I don't think that `yet another` phrase > just fits here. Also, in our case it's not just Maven support, we're also > targeting our language and related stuff, nvm, but it is not an option. It > looks like there is no other resources than sources and we have to stay > with our present methods. Thanks for your answers, just consider simple > specification for future users :) > > > Maven protocol specification > > > > > > Key: MNG-6691 > > URL: https://issues.apache.org/jira/browse/MNG-6691 > > Project: Maven > > Issue Type: Wish > > Components: Documentation: General > >Reporter: dzikoysk > >Priority: Trivial > > Labels: documentation > > > > There is a lot of guides and docs about "How to start" on [ > maven.apache.org|https://maven.apache.org/] with maven as developer who > wants to use maven in a project, but I'm not able to find something for > people working with repository managers. Is there any technical > specification of maven http/protocol specification/rest api and what's > required from a custom repository manager to serve requests properly or the > only way is to search in maven/other repositories like nexus, artifcatory > sources? > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) >
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal even in non-verbose mode
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Description:
currently, there is no info message apart from download status while
re-resolving (or in verbose mode, there is too much output):
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Deleting 75 projects' transitive dependencies from
/home/herve/.m2/repository at artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
with bold color for configurable arguments (count, "transitive" vs "direct",
"version" or other fuzzyness values)
was:
currently, there is no info message apart from download status while
re-resolving (or in verbose mode, there is too much output):
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
with bold color for configurable arguments (count, "transitive" vs "direct",
"version" or other fuzzyness values)
> add info message to purge-local-repository goal even in non-verbose mode
>
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Priority: Major
> Labels: up-for-grabs
> Fix For: next-release
>
>
> currently, there is no info message apart from download status while
> re-resolving (or in verbose mode, there is too much output):
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
>
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal even in non-verbose mode
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Summary: add info message to purge-local-repository goal even in
non-verbose mode (was: add info message to purge-local-repository goal)
> add info message to purge-local-repository goal even in non-verbose mode
>
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Priority: Major
> Labels: up-for-grabs
> Fix For: next-release
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
> artifact version level
> [INFO] Re-resolving dependencies
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]{noformat}
> with bold color for configurable arguments (count, "transitive" vs "direct",
> "version" or other fuzzyness values)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal even in non-verbose mode
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Description:
currently, there is no info message apart from download status while
re-resolving (or in verbose mode, there is too much output):
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
with bold color for configurable arguments (count, "transitive" vs "direct",
"version" or other fuzzyness values)
was:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
with bold color for configurable arguments (count, "transitive" vs "direct",
"version" or other fuzzyness values)
> add info message to purge-local-repository goal even in non-verbose mode
>
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Priority: Major
> Labels: up-for-grabs
> Fix For: next-release
>
>
> currently, there is no info message apart from download status while
> re-resolving (or in verbose mode, there is too much output):
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Description:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
with bold color for configurable arguments (count, "transitive" vs "direct",
"version" or other fuzzyness values)
was:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Priority: Major
> Labels: up-for-grabs
> Fix For: next-release
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Deleting 75 transitive dependencies from
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Labels: up-for-grabs (was: )
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Priority: Major
> Labels: up-for-grabs
> Fix For: next-release
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
> artifact version level
> [INFO] Re-resolving dependencies
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Fix Version/s: (was: 3.1.2)
next-release
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Priority: Major
> Fix For: next-release
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
> artifact version level
> [INFO] Re-resolving dependencies
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy reassigned MDEP-653:
--
Assignee: (was: Hervé Boutemy)
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Priority: Major
> Fix For: 3.1.2
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
> artifact version level
> [INFO] Re-resolving dependencies
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Description:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
was:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Purging 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.1.2
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Deleting 75 transitive dependencies from /home/herve/.m2/repository at
> artifact version level
> [INFO] Re-resolving dependencies
> Downloading from central:
>
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Description:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Purging 75 transitive dependencies from /home/herve/.m2/repository at
artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
was:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Purging 75 transitive dependencies from local repository
/home/herve/.m2/repository at artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.1.2
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Purging 75 transitive dependencies from /home/herve/.m2/repository at
> artifact version level
> [INFO] Re-resolving dependencies
> Downloading
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Description:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Purging 75 transitive dependencies from local repository
/home/herve/.m2/repository at artifact version level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
was:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Purging 75 dependencies at artifact version-level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.1.2
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Purging 75 transitive dependencies from local repository
> /home/herve/.m2/repository at artifact version level
> [INFO] Re-resolving dependencies
> Downloading from central:
>
[jira] [Updated] (MNG-6268) When a reactor build fails Maven should include -f (if used) in command line suggestion
[
https://issues.apache.org/jira/browse/MNG-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MNG-6268:
--
Fix Version/s: (was: 3.6.x-candidate)
> When a reactor build fails Maven should include -f (if used) in command line
> suggestion
> ---
>
> Key: MNG-6268
> URL: https://issues.apache.org/jira/browse/MNG-6268
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.5.0
>Reporter: Andreas Sewe
>Priority: Trivial
> Fix For: wontfix-candidate
>
>
> When a reactor build fails, Maven prints out a helpful suggestion on how to
> resume.
> {noformat}
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :example
> {noformat}
> Unfortunately, when running {{mvn}} with {{-f}}, this suggestion is wrong;
> Maven will either pick the wrong {{pom.xml}} or simply won’t find any; in
> either case, the {{pom.xml}} specified with {{-f}} is *crucial* information
> that was left out of the suggestion.
> FYI, this is related to MNG-6028, but covers a different bit of info that
> IMHO should be part of the suggestion. Hence this separate issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MDEP-653) add info message to purge-local-repository goal
[
https://issues.apache.org/jira/browse/MDEP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MDEP-653:
---
Description:
currently, there is no info message apart from download status while
re-resolving:
{noformat}
$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}
[INFO] Purging 75 dependencies at artifact version-level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
was:
currently, there is no info message apart from download status while
re-resolving:
{noformat}$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}[INFO] Purging 150 dependencies at artifact version-level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
> add info message to purge-local-repository goal
> ---
>
> Key: MDEP-653
> URL: https://issues.apache.org/jira/browse/MDEP-653
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
>Affects Versions: 3.1.1
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.1.2
>
>
> currently, there is no info message apart from download status while
> re-resolving:
> {noformat}
> $ mvn dependency:purge-local-repository
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven.plugins:maven-dependency-plugin
> >--
> [INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
> [INFO] [ maven-plugin
> ]
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli)
> @ maven-dependency-plugin ---
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> (1.9 kB at 29 kB/s)
> [...]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
> {noformat}
> would be useful to write something like:
> {noformat}
> [INFO] Purging 75 dependencies at artifact version-level
> [INFO] Re-resolving dependencies
> Downloading from central:
> http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
> Downloaded from central:
[jira] [Created] (MDEP-653) add info message to purge-local-repository goal
Hervé Boutemy created MDEP-653:
--
Summary: add info message to purge-local-repository goal
Key: MDEP-653
URL: https://issues.apache.org/jira/browse/MDEP-653
Project: Maven Dependency Plugin
Issue Type: Improvement
Components: purge-local-repository
Affects Versions: 3.1.1
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
Fix For: 3.1.2
currently, there is no info message apart from download status while
re-resolving:
{noformat}$ mvn dependency:purge-local-repository
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven.plugins:maven-dependency-plugin >--
[INFO] Building Apache Maven Dependency Plugin 3.1.2-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-dependency-plugin:3.1.1:purge-local-repository (default-cli) @
maven-dependency-plugin ---
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
would be useful to write something like:
{noformat}[INFO] Purging 150 dependencies at artifact version-level
[INFO] Re-resolving dependencies
Downloading from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
Downloaded from central:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/maven-artifact/3.0/maven-artifact-3.0.pom
(1.9 kB at 29 kB/s)
[...]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6691) Maven protocol specification
[ https://issues.apache.org/jira/browse/MNG-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879610#comment-16879610 ] Hervé Boutemy commented on MNG-6691: don't hesitate to contribute back your findings > Maven protocol specification > > > Key: MNG-6691 > URL: https://issues.apache.org/jira/browse/MNG-6691 > Project: Maven > Issue Type: Wish > Components: Documentation: General >Reporter: dzikoysk >Priority: Trivial > Labels: documentation > > There is a lot of guides and docs about "How to start" on > [maven.apache.org|https://maven.apache.org/] with maven as developer who > wants to use maven in a project, but I'm not able to find something for > people working with repository managers. Is there any technical specification > of maven http/protocol specification/rest api and what's required from a > custom repository manager to serve requests properly or the only way is to > search in maven/other repositories like nexus, artifcatory sources? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
