[jira] [Created] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
Kamalpreet created MDEP-812:
---
Summary: Error opening zip file or JAR manifest missing :
${groupId:artifactId:jar}
Key: MDEP-812
URL: https://issues.apache.org/jira/browse/MDEP-812
Project: Maven Dependency Plugin
Issue Type: Bug
Components: resolve
Reporter: Kamalpreet
My profile :-
{code:java}
test
maven-dependency-plugin
3.3.0
getClasspathFilenames
properties
org.codehaus.mojo
exec-maven-plugin
3.1.0
java
test
java
-javaagent:${groupId:artifactId:jar}
-classpath
sampleTest
{code}
When running command
{code:java}
mvn exec:exec -P test{code}
, I'm getting error
{code:java}
Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
Error occurred during initialization of VM
agent library failed to init: instrument
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit
value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal
(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute
(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
(ExecMojo.java:1000){code}
Is there anyway to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated MDEP-812:
Description:
My profile :-
{code:java}
test
maven-dependency-plugin
3.3.0
getClasspathFilenames
properties
org.codehaus.mojo
exec-maven-plugin
3.1.0
java
test
java
-javaagent:${groupId:artifactId:jar}
-classpath
sampleTest
{code}
When running command
{code:java}
mvn exec:exec -P test{code}
, I'm getting error
{code:java}
Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
Error occurred during initialization of VM
agent library failed to init: instrument
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit
value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal
(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute
(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
(ExecMojo.java:1000){code}
Why maven-dependency-plugin is not able to resolve jar path? Is there anyway to
fix this issue? Any help is much appreciated.
was:
My profile :-
{code:java}
test
maven-dependency-plugin
3.3.0
getClasspathFilenames
properties
org.codehaus.mojo
exec-maven-plugin
3.1.0
java
test
java
-javaagent:${groupId:artifactId:jar}
-classpath
sampleTest
{code}
When running command
{code:java}
mvn exec:exec -P test{code}
, I'm getting error
{code:java}
Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
Error occurred during initialization of VM
agent library failed to init: instrument
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit
value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal
(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute
(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
(ExecMojo.java:1000){code}
Is there anyway to fix this issue? Any help is much appreciated.
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
>
[GitHub] [maven-reporting-api] michael-o commented on pull request #2: [MSHARED-1024] Replace deprecated code
michael-o commented on PR #2: URL: https://github.com/apache/maven-reporting-api/pull/2#issuecomment-1198969504 > FYI this breaks binary compatibility with https://github.com/kohsuke/maven-jellydoc-plugin and https://github.com/jenkinsci/maven-stapler-plugin: > > [jenkins-infra/helpdesk#3049 (comment)](https://github.com/jenkins-infra/helpdesk/issues/3049#issuecomment-1186294149) > > But I suppose we are long past the point where such binary compatibility could reasonably be expected. I will try to update the consumers. That's true, but is a major and we have to remove at some point. Those methods were deprecated for a long time. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MENFORCER-423) Maven enforcer rule which checks that all dependencies have an explicit scope set
[
https://issues.apache.org/jira/browse/MENFORCER-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572793#comment-17572793
]
Slawomir Jaranowski commented on MENFORCER-423:
---
we have many build-in rules for dependency management, so I think we can add
one more
> Maven enforcer rule which checks that all dependencies have an explicit scope
> set
> -
>
> Key: MENFORCER-423
> URL: https://issues.apache.org/jira/browse/MENFORCER-423
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: Konrad Windszus
>Priority: Major
>
> Useful in case when the scope is no longer part of the dependencyManagement
> or in general to force making developers a distinct decision for every local
> dependency (prevents the default scope compile from being used for test
> dependencies).
> I propose the name {{requireDependencyScope}} for the new rule.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MENFORCER-423) Maven enforcer rule which checks that all dependencies have an explicit scope set
[
https://issues.apache.org/jira/browse/MENFORCER-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned MENFORCER-423:
-
Assignee: Slawomir Jaranowski
> Maven enforcer rule which checks that all dependencies have an explicit scope
> set
> -
>
> Key: MENFORCER-423
> URL: https://issues.apache.org/jira/browse/MENFORCER-423
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: Konrad Windszus
>Assignee: Slawomir Jaranowski
>Priority: Major
>
> Useful in case when the scope is no longer part of the dependencyManagement
> or in general to force making developers a distinct decision for every local
> dependency (prevents the default scope compile from being used for test
> dependencies).
> I propose the name {{requireDependencyScope}} for the new rule.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MENFORCER-424) Maven enforcer rule which checks that all dependencies in dependencyManagement don't have an explicit scope set
[
https://issues.apache.org/jira/browse/MENFORCER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572795#comment-17572795
]
Slawomir Jaranowski commented on MENFORCER-424:
---
we have many build-in rules for dependency management, so I think we can add
one more
> Maven enforcer rule which checks that all dependencies in
> dependencyManagement don't have an explicit scope set
> ---
>
> Key: MENFORCER-424
> URL: https://issues.apache.org/jira/browse/MENFORCER-424
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: Konrad Windszus
>Priority: Major
>
> Setting the scope in the dependencyManagement is an anti-pattern and may lead
> to surprising results during classpath creation. Compare also with the
> discussion in
> https://github.com/apache/maven-apache-parent/pull/63#discussion_r788361219.
> I propose to add a new rule with name {{banDependencyManagementScope}}.
> Probably scope {{import}} should be accepted though, because it is a special
> case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-410) Create implementation attribute for @Parameter as it exists for javadoc @parameter
[ https://issues.apache.org/jira/browse/MPLUGIN-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572799#comment-17572799 ] Herve Boutemy commented on MPLUGIN-410: --- thanks for the explanation [~romain.manni-bucau], it was useful it's true that this feature seems near not used: [~gnodet] found it in Maven core ITs, but I don't know if it happens in real world. Another fact: the real feature is in Maven core, with the plugin descriptor https://maven.apache.org/ref/3.8.6/maven-plugin-api/plugin.html Not adding the parameter in plugin-tools Java5 annotations just makes it not visible (it is visible only as Javadoc annotation) I have no idea if keeping the feature defacto hidden in Java annotation is finally a choice to keep or not > Create implementation attribute for @Parameter as it exists for javadoc > @parameter > -- > > Key: MPLUGIN-410 > URL: https://issues.apache.org/jira/browse/MPLUGIN-410 > Project: Maven Plugin Tools > Issue Type: Improvement > Components: maven-plugin-tools-annotations >Reporter: Herve Boutemy >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.7.0 > > > it exists in javadoc annotations: > https://maven.apache.org/plugin-tools/maven-plugin-tools-java/ (line 33) > that goes into plugin.xml descriptor > https://maven.apache.org/ref/3.8.6/maven-plugin-api/plugin.html (line 44) > but was forgotten in Java 5 annotations: > https://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/ (line > 44) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-410) Create implementation attribute for @Parameter as it exists for javadoc @parameter
[ https://issues.apache.org/jira/browse/MPLUGIN-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572801#comment-17572801 ] Herve Boutemy commented on MPLUGIN-410: --- notice: feature added, discussion closed... > Create implementation attribute for @Parameter as it exists for javadoc > @parameter > -- > > Key: MPLUGIN-410 > URL: https://issues.apache.org/jira/browse/MPLUGIN-410 > Project: Maven Plugin Tools > Issue Type: Improvement > Components: maven-plugin-tools-annotations >Reporter: Herve Boutemy >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.7.0 > > > it exists in javadoc annotations: > https://maven.apache.org/plugin-tools/maven-plugin-tools-java/ (line 33) > that goes into plugin.xml descriptor > https://maven.apache.org/ref/3.8.6/maven-plugin-api/plugin.html (line 44) > but was forgotten in Java 5 annotations: > https://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/ (line > 44) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINVOKER-306) Bugfix for case if invoker.test parameter contains only exclude-patterns
[ https://issues.apache.org/jira/browse/MINVOKER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir V. Bychkov updated MINVOKER-306: - Summary: Bugfix for case if invoker.test parameter contains only exclude-patterns (was: Bugfix for case if invoker.test parameter contains only exclude patterns) > Bugfix for case if invoker.test parameter contains only exclude-patterns > > > Key: MINVOKER-306 > URL: https://issues.apache.org/jira/browse/MINVOKER-306 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 3.2.2, 3.3.0 >Reporter: Vladimir V. Bychkov >Assignee: Slawomir Jaranowski >Priority: Major > > Behavior described in MINVOKER-140 dont't work in case if parameter > invoker.test contains only exclude patterns (without include patterns). As a > result list of appropriated tests is empty and tests are skipping. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated MDEP-812:
Priority: Critical (was: Blocker)
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Critical
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7523) support MAVEN_ARGS for Apache Maven 3.8.x as well
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572865#comment-17572865 ] Michael Osipov commented on MNG-7523: - [~henning], would it be sufficient to have it in 3.9.0 for you? If all goes well 3.9.0 should go out in August... > support MAVEN_ARGS for Apache Maven 3.8.x as well > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Improvement > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Priority: Minor > Fix For: 3.8.x-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-7443) Consistent logging between optional projects and optional profiles
[ https://issues.apache.org/jira/browse/MNG-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-7443: --- Assignee: Michael Osipov > Consistent logging between optional projects and optional profiles > -- > > Key: MNG-7443 > URL: https://issues.apache.org/jira/browse/MNG-7443 > Project: Maven > Issue Type: Improvement > Components: Core, Logging >Affects Versions: 4.0.0-alpha-1 >Reporter: Giovanni van der Schelde >Assignee: Michael Osipov >Priority: Minor > Attachments: example.png > > > Maven 4 introduces optional profiles and optional projects. However, the > feedback provided to the user on whether a project or profile has been > skipped is inconsistent between the two (see image attached). > For profiles, it will be logged twice: before and after the build. > For projects, it will be logged once: before the build. > The idea would be to log the information for skipped optional projects after > the build as well. > !example.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7443) Consistent logging between optional projects and optional profiles
[ https://issues.apache.org/jira/browse/MNG-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7443: Fix Version/s: 4.0.0-alpha-1 4.0.0 > Consistent logging between optional projects and optional profiles > -- > > Key: MNG-7443 > URL: https://issues.apache.org/jira/browse/MNG-7443 > Project: Maven > Issue Type: Improvement > Components: Core, Logging >Affects Versions: 4.0.0-alpha-1 >Reporter: Giovanni van der Schelde >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0-alpha-1, 4.0.0 > > Attachments: example.png > > > Maven 4 introduces optional profiles and optional projects. However, the > feedback provided to the user on whether a project or profile has been > skipped is inconsistent between the two (see image attached). > For profiles, it will be logged twice: before and after the build. > For projects, it will be logged once: before the build. > The idea would be to log the information for skipped optional projects after > the build as well. > !example.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7443) Implement consistent logging between optional projects and optional profiles
[ https://issues.apache.org/jira/browse/MNG-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7443: Summary: Implement consistent logging between optional projects and optional profiles (was: Consistent logging between optional projects and optional profiles) > Implement consistent logging between optional projects and optional profiles > > > Key: MNG-7443 > URL: https://issues.apache.org/jira/browse/MNG-7443 > Project: Maven > Issue Type: Improvement > Components: Core, Logging >Affects Versions: 4.0.0-alpha-1 >Reporter: Giovanni van der Schelde >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0-alpha-1, 4.0.0 > > Attachments: example.png > > > Maven 4 introduces optional profiles and optional projects. However, the > feedback provided to the user on whether a project or profile has been > skipped is inconsistent between the two (see image attached). > For profiles, it will be logged twice: before and after the build. > For projects, it will be logged once: before the build. > The idea would be to log the information for skipped optional projects after > the build as well. > !example.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-integration-testing] michael-o commented on pull request #168: [MNG-7443] IT for consistent logging of optional selectors
michael-o commented on PR #168: URL: https://github.com/apache/maven-integration-testing/pull/168#issuecomment-1199058698 Running this now, the IT needs some non-functional improvements I will perform -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] asfgit closed pull request #168: [MNG-7443] IT for consistent logging of optional selectors
asfgit closed pull request #168: [MNG-7443] IT for consistent logging of optional selectors URL: https://github.com/apache/maven-integration-testing/pull/168 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] asfgit closed pull request #701: [MNG-7443] Make logging consistent between optional profiles and projects
asfgit closed pull request #701: [MNG-7443] Make logging consistent between optional profiles and projects URL: https://github.com/apache/maven/pull/701 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7443) Implement consistent logging between optional projects and optional profiles
[ https://issues.apache.org/jira/browse/MNG-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572885#comment-17572885 ] ASF GitHub Bot commented on MNG-7443: - asfgit closed pull request #701: [MNG-7443] Make logging consistent between optional profiles and projects URL: https://github.com/apache/maven/pull/701 > Implement consistent logging between optional projects and optional profiles > > > Key: MNG-7443 > URL: https://issues.apache.org/jira/browse/MNG-7443 > Project: Maven > Issue Type: Improvement > Components: Core, Logging >Affects Versions: 4.0.0-alpha-1 >Reporter: Giovanni van der Schelde >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0-alpha-1, 4.0.0 > > Attachments: example.png > > > Maven 4 introduces optional profiles and optional projects. However, the > feedback provided to the user on whether a project or profile has been > skipped is inconsistent between the two (see image attached). > For profiles, it will be logged twice: before and after the build. > For projects, it will be logged once: before the build. > The idea would be to log the information for skipped optional projects after > the build as well. > !example.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7443) Implement consistent logging between optional projects and optional profiles
[ https://issues.apache.org/jira/browse/MNG-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-7443. --- Resolution: Fixed Fixed with [a53a1aa232bc383baf055d884a7c66319d10d404|https://gitbox.apache.org/repos/asf?p=maven.git&a=commit&h=a53a1aa232bc383baf055d884a7c66319d10d404] and ITs with [393f6242d93eb1ef951268c94a1699d2f3567563|https://gitbox.apache.org/repos/asf?p=maven-integration-testing.git&a=commit&h=393f6242d93eb1ef951268c94a1699d2f3567563]. > Implement consistent logging between optional projects and optional profiles > > > Key: MNG-7443 > URL: https://issues.apache.org/jira/browse/MNG-7443 > Project: Maven > Issue Type: Improvement > Components: Core, Logging >Affects Versions: 4.0.0-alpha-1 >Reporter: Giovanni van der Schelde >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0-alpha-1, 4.0.0 > > Attachments: example.png > > > Maven 4 introduces optional profiles and optional projects. However, the > feedback provided to the user on whether a project or profile has been > skipped is inconsistent between the two (see image attached). > For profiles, it will be logged twice: before and after the build. > For projects, it will be logged once: before the build. > The idea would be to log the information for skipped optional projects after > the build as well. > !example.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7443) Implement consistent logging between optional projects and optional profiles
[ https://issues.apache.org/jira/browse/MNG-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572904#comment-17572904 ] Hudson commented on MNG-7443: - Build unstable in Jenkins: Maven » Maven TLP » maven » master #77 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/77/ > Implement consistent logging between optional projects and optional profiles > > > Key: MNG-7443 > URL: https://issues.apache.org/jira/browse/MNG-7443 > Project: Maven > Issue Type: Improvement > Components: Core, Logging >Affects Versions: 4.0.0-alpha-1 >Reporter: Giovanni van der Schelde >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0-alpha-1, 4.0.0 > > Attachments: example.png > > > Maven 4 introduces optional profiles and optional projects. However, the > feedback provided to the user on whether a project or profile has been > skipped is inconsistent between the two (see image attached). > For profiles, it will be logged twice: before and after the build. > For projects, it will be logged once: before the build. > The idea would be to log the information for skipped optional projects after > the build as well. > !example.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572962#comment-17572962
]
Michael Osipov commented on MDEP-812:
-
Provide full verbose output of the execution..
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Critical
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-812:
Fix Version/s: waiting-for-feedback
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEPLOY-298: --- Fix Version/s: waiting-for-feedback > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > Fix For: waiting-for-feedback > > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572965#comment-17572965 ] Michael Osipov commented on MDEPLOY-298: See these properties for Maven Wagon HTTP: https://maven.apache.org/wagon/wagon-providers/wagon-http/ > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572975#comment-17572975 ] Amruta Kawade commented on MDEPLOY-298: --- This needs to be implemented in mvn deploy plugin right? > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > Fix For: waiting-for-feedback > > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated MDEP-812:
Priority: Blocker (was: Critical)
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated MDEP-812:
Attachment: log.txt
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-pmd-plugin] JLLeitschuh opened a new pull request, #80: [SECURITY] Fix Partial Path Traversal Vulnerability
JLLeitschuh opened a new pull request, #80:
URL: https://github.com/apache/maven-pmd-plugin/pull/80
# Security Vulnerability Fix
This pull request fixes a partial-path traversal vulnerability due to an
insufficient path traversal guard.
## Preamble
### Impact
This issue allows a malicious actor to potentially break out of the expected
directory. The impact is limited to sibling directories. For example,
`userControlled.getCanonicalPath().startsWith("/usr/out")` will allow an
attacker to access a directory with a name like `/usr/outnot`.
### Why?
To demonstrate this vulnerability, consider
`"/usr/outnot".startsWith("/usr/out")`.
The check is bypassed although `/outnot` is not under the `/out` directory.
It's important to understand that the terminating slash may be removed when
using various `String` representations of the `File` object.
For example, on Linux, `println(new File("/var"))` will print `/var`, but
`println(new File("/var", "/")` will print `/var/`;
however, `println(new File("/var", "/").getCanonicalPath())` will print
`/var`.
### The Fix
Comparing paths with the `java.nio.files.Path#startsWith` will adequately
protect againts this vulnerability.
For example: `file.getCanonicalFile().toPath().startsWith(BASE_DIRECTORY)`
or
`file.getCanonicalFile().toPath().startsWith(BASE_DIRECTORY_FILE.getCanonicalFile().toPath())`
### Other Examples
-
[CVE-2022-31159](https://github.com/aws/aws-sdk-java/security/advisories/GHSA-c28r-hw5m-5gv3)
- aws/aws-sdk-java
-
[CVE-2022-23457](https://securitylab.github.com/advisories/GHSL-2022-008_The_OWASP_Enterprise_Security_API/)
- ESAPI/esapi-java-legacy
# :arrow_right: Vulnerability Disclosure :arrow_left:
:wave: Vulnerability disclosure is a super important part of the
vulnerability handling process and should not be skipped! This may be
completely new to you, and that's okay, I'm here to assist!
First question, do we need to perform vulnerability disclosure? It depends!
1. Is the vulnerable code only in tests or example code? No disclosure
required!
2. Is the vulnerable code in code shipped to your end users? Vulnerability
disclosure is probably required!
## Vulnerability Disclosure How-To
You have a few options options to perform vulnerability disclosure. However,
I'd like to suggest the following 2 options:
1. Request a CVE number from GitHub by creating a repository-level [GitHub
Security
Advisory](https://docs.github.com/en/code-security/repository-security-advisories/creating-a-repository-security-advisory).
This has the advantage that, if you provide sufficient information, GitHub
will automatically generate Dependabot alerts for your downstream consumers,
resolving this vulnerability more quickly.
2. Reach out to the team at Snyk to assist with CVE issuance. They can be
reached at the [Snyk's Disclosure Email](mailto:rep...@snyk.io). Note: Please
include `JLLeitschuh Disclosure` in the subject of your email so it is not
missed.
## Detecting this and Future Vulnerabilities
You can automatically detect future vulnerabilities like this by enabling
the free (for open-source) [GitHub
Action](https://github.com/github/codeql-action).
I'm not an employee of GitHub, I'm simply an open-source security researcher.
## Source
This contribution was automatically generated with an
[OpenRewrite](https://github.com/openrewrite/rewrite) [refactoring
recipe](https://docs.openrewrite.org/), which was lovingly hand crafted to
bring this security fix to your repository.
The source code that generated this PR can be found here:
[PartialPathTraversalVulnerability](https://github.com/openrewrite/rewrite-java-security/blob/main/src/main/java/org/openrewrite/java/security/PartialPathTraversalVulnerability.java)
## Why didn't you disclose privately (ie. coordinated disclosure)?
This is technically what is called a "Full Disclosure" in vulnerability
disclosure, and I agree it's less than ideal. If GitHub offered a way to create
private pull requests to submit pull requests, I'd leverage it, but that
infrastructure sadly doesn't exist.
The problem is that as an open source software security researcher, I
(exactly like open source maintainers), I only have so much time in a day. I'm
able to find vulnerabilities impacting hundreds, or sometimes thousands of open
source projects with tools like GitHub Code Search and CodeQL. The problem is
that my knowledge of vulnerabilities doesn't scale very well.
Individualized vulnerability disclosure takes time and care. It's a long and
tedious process, and I have a significant amount of experience with it (I have
over 50 CVEs to my name). Even tracking down the reporting channel (email,
Jira, ect..) can take time and isn't automatable. Unfortunately, when facing
prblems of th
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572981#comment-17572981
]
Kamalpreet commented on MDEP-812:
-
Here, is the log file.
[^log.txt]
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572987#comment-17572987 ] Michael Osipov commented on MDEPLOY-298: No, you need to supply the user properties to the maven run. You will likely be better off with RFTM: https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#retryFailedDeploymentCount > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > Fix For: waiting-for-feedback > > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEPLOY-298: --- Fix Version/s: wontfix-candidate > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > Fix For: waiting-for-feedback, wontfix-candidate > > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572988#comment-17572988
]
Michael Osipov commented on MDEP-812:
-
Provide {{mvn dependency:tree}} on that failing project.
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572990#comment-17572990 ] Amruta Kawade commented on MDEPLOY-298: --- oh ok. so suppose i am trying to publish project which has 10 files. in first run 4 files succeeded. for 5th file upload connection dropped. so with this retry parameter mvn client will try to publish whole project or just 5th file which was failed ? > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > Fix For: waiting-for-feedback, wontfix-candidate > > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-compiler-plugin] ledoyen commented on pull request #143: MCOMPILER 499 display recompilation causes
ledoyen commented on PR #143: URL: https://github.com/apache/maven-compiler-plugin/pull/143#issuecomment-1199339609 Thanks @olamy, being currently AFK, I did not see your request in time. Hopefully this will allow users to understand and optimize their build reactor. Good job 👍 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572997#comment-17572997 ] Michael Osipov commented on MDEPLOY-298: Give it a try. > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > Fix For: waiting-for-feedback, wontfix-candidate > > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7524) Add type coercion table for plugin parameters
Konrad Windszus created MNG-7524: Summary: Add type coercion table for plugin parameters Key: MNG-7524 URL: https://issues.apache.org/jira/browse/MNG-7524 Project: Maven Issue Type: Improvement Components: Documentation: Guides Reporter: Konrad Windszus All plugin parameters in the pom.xml or on the command line are given as strings. There should be a type coercion table in https://maven.apache.org/guides/mini/guide-configuring-plugins.html#configuring-parameters elaborating how those Strings are converted into the target type (i.e. which method is called under the hood). Compare with the discussion started in https://lists.apache.org/thread/3q3bt89cms0pl7ylgkjhj708vgfqf927 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7524) Add type coercion table for plugin parameters
[ https://issues.apache.org/jira/browse/MNG-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573013#comment-17573013 ] Michael Osipov commented on MNG-7524: - Beat me I have seen this somewhere... > Add type coercion table for plugin parameters > - > > Key: MNG-7524 > URL: https://issues.apache.org/jira/browse/MNG-7524 > Project: Maven > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Konrad Windszus >Priority: Major > > All plugin parameters in the pom.xml or on the command line are given as > strings. There should be a type coercion table in > https://maven.apache.org/guides/mini/guide-configuring-plugins.html#configuring-parameters > elaborating how those Strings are converted into the target type (i.e. which > method is called under the hood). > Compare with the discussion started in > https://lists.apache.org/thread/3q3bt89cms0pl7ylgkjhj708vgfqf927 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7524) Add type coercion table for plugin parameters
[ https://issues.apache.org/jira/browse/MNG-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573016#comment-17573016 ] Konrad Windszus commented on MNG-7524: -- [~michael-o] Do you mean the documentation at https://maven.apache.org/guides/plugin/guide-java-plugin-development.html#parameters? Even that one is not really complete.. > Add type coercion table for plugin parameters > - > > Key: MNG-7524 > URL: https://issues.apache.org/jira/browse/MNG-7524 > Project: Maven > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Konrad Windszus >Priority: Major > > All plugin parameters in the pom.xml or on the command line are given as > strings. There should be a type coercion table in > https://maven.apache.org/guides/mini/guide-configuring-plugins.html#configuring-parameters > elaborating how those Strings are converted into the target type (i.e. which > method is called under the hood). > Compare with the discussion started in > https://lists.apache.org/thread/3q3bt89cms0pl7ylgkjhj708vgfqf927 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573024#comment-17573024 ] Amruta Kawade commented on MDEPLOY-298: --- I tried this. without this parameter also it retries. and it retries for individual file. We are working on creating maven repository. so wanted to understand will there be scenario of retrying whole project ? as maven uploads single file at a time and there is no indication of how many files will be uploaded once you receive request for any particular release version. how maven repository will understand that all files requests are received ? how many pending file requests are there. also how central maven repository handles this scenario ? > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > Fix For: waiting-for-feedback, wontfix-candidate > > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-reporting-api] basil commented on pull request #2: [MSHARED-1024] Replace deprecated code
basil commented on PR #2: URL: https://github.com/apache/maven-reporting-api/pull/2#issuecomment-1199516999 Was this breaking change documented in any release notes? -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-analyzer] slawekjaranowski merged pull request #67: Bump maven-shared-components from 36 to 37
slawekjaranowski merged PR #67: URL: https://github.com/apache/maven-dependency-analyzer/pull/67 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MSHARED-1085) Upgrade Parent to 37
[ https://issues.apache.org/jira/browse/MSHARED-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MSHARED-1085: - Summary: Upgrade Parent to 37 (was: Upgrade Parent to 36) > Upgrade Parent to 37 > > > Key: MSHARED-1085 > URL: https://issues.apache.org/jira/browse/MSHARED-1085 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-dependency-analyzer >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-dependency-analyzer-3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573038#comment-17573038
]
Slawomir Jaranowski commented on MDEP-812:
--
Does your project work with older version of m-dependency-p?
property:
{code}
${groupId:artifactId:jar}
{code}
is very strange for me ...
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated MDEP-812:
Attachment: log-1.txt
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573039#comment-17573039
]
Kamalpreet commented on MDEP-812:
-
[^log.txt] Check this.
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573039#comment-17573039
]
Kamalpreet edited comment on MDEP-812 at 7/29/22 3:39 PM:
--
[^log.txt] Check this. [~michael-o]
was (Author: JIRAUSER288713):
[^log.txt] Check this.
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573040#comment-17573040
]
Kamalpreet commented on MDEP-812:
-
[~sjaranowski] This is the documentation page referred to this page -
[https://maven.apache.org/plugins/maven-dependency-plugin/properties-mojo.html]
[https://stackoverflow.com/questions/14777909/specify-javaagent-argument-with-maven-exec-plugin|https://stackoverflow.com/questions/14777909/specify-javaagent-argument-with-maven-exec-plugin]
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573040#comment-17573040
]
Kamalpreet edited comment on MDEP-812 at 7/29/22 3:44 PM:
--
[~sjaranowski] This is the documentation page referred to these page -
[https://maven.apache.org/plugins/maven-dependency-plugin/properties-mojo.html]
[https://stackoverflow.com/questions/14777909/specify-javaagent-argument-with-maven-exec-plugin]
was (Author: JIRAUSER288713):
[~sjaranowski] This is the documentation page referred to this page -
[https://maven.apache.org/plugins/maven-dependency-plugin/properties-mojo.html]
[https://stackoverflow.com/questions/14777909/specify-javaagent-argument-with-maven-exec-plugin|https://stackoverflow.com/questions/14777909/specify-javaagent-argument-with-maven-exec-plugin]
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEP-812.
---
Fix Version/s: (was: waiting-for-feedback)
Resolution: Invalid
I am really tired of things like this
maven-dependency-plugin:2.8:tree
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7525) Automatic handling of non multi thread safe mojos
Christoph Läubrich created MNG-7525: --- Summary: Automatic handling of non multi thread safe mojos Key: MNG-7525 URL: https://issues.apache.org/jira/browse/MNG-7525 Project: Maven Issue Type: Improvement Reporter: Christoph Läubrich Currently, when I run a mojo that is not marked as thread safe, one gets a warning from maven. The usual "workaround" is to ask the mojo author to add a global lock and mark the mojo as thread safe, but this is rather useless, because the Mojo obviously not became "thread-safer", requires additional code and release ... It would be better if maven handle this internally e.g. simply synchronize on the mojo-class-object when executing a mojo that is not marked as thread-safe. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-reporting-api] michael-o commented on pull request #2: [MSHARED-1024] Replace deprecated code
michael-o commented on PR #2: URL: https://github.com/apache/maven-reporting-api/pull/2#issuecomment-1199631771 I need to revert my previous statement because I had another release in memory. Yes, this change was partially wrong and I haven't anticipated people still using 10 years old deprecated interfaces. It should have happened only in a new major version. Although I am still surprised that code even being deprecated and the IDE tells you the successor is still not changed. BTW, same happened with Asciidoctor Maven Plugin. Sorry for the inconvenience. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-reporting-api] michael-o commented on pull request #2: [MSHARED-1024] Replace deprecated code
michael-o commented on PR #2: URL: https://github.com/apache/maven-reporting-api/pull/2#issuecomment-1199645154 Would you prefer a patch release with a revert? This code will go away in 4.0.0 anyway. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-reporting-api] basil commented on pull request #2: [MSHARED-1024] Replace deprecated code
basil commented on PR #2: URL: https://github.com/apache/maven-reporting-api/pull/2#issuecomment-1199649708 Thanks Michael, that would definitely be appreciated as otherwise I need to go obtaining write access to two ancient Maven plugins to modernize them and perform new releases, which I would rather not rush to do. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-reporting-api] michael-o commented on pull request #2: [MSHARED-1024] Replace deprecated code
michael-o commented on PR #2: URL: https://github.com/apache/maven-reporting-api/pull/2#issuecomment-1199657760 > Thanks Michael, that would definitely be appreciated as otherwise I need to go obtaining write access to two ancient Maven plugins to modernize them and perform new releases, which I would rather not rush to do. That would only be an interims solution because with Maven Site Plugin 4 they will fail anyway. Please file an issue with MSHARED and link this conversation to it. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573055#comment-17573055
]
Kamalpreet commented on MDEP-812:
-
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue?
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573055#comment-17573055
]
Kamalpreet edited comment on MDEP-812 at 7/29/22 4:44 PM:
--
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
was (Author: JIRAUSER288713):
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue?
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573055#comment-17573055
]
Kamalpreet edited comment on MDEP-812 at 7/29/22 4:45 PM:
--
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
[^dependency-tree.txt]
^Still I'm getting the same issue.^
was (Author: JIRAUSER288713):
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: dependency-tree.txt, log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated MDEP-812:
Attachment: dependency-tree.txt
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: dependency-tree.txt, log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573055#comment-17573055
]
Kamalpreet edited comment on MDEP-812 at 7/29/22 4:46 PM:
--
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
[^dependency-tree.txt]
was (Author: JIRAUSER288713):
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
[^dependency-tree.txt]
^Still I'm getting the same issue.^
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: dependency-tree.txt, log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573055#comment-17573055
]
Kamalpreet edited comment on MDEP-812 at 7/29/22 4:47 PM:
--
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
[^dependency-tree.txt]
^Still I'm getting the same error.^
was (Author: JIRAUSER288713):
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
[^dependency-tree.txt]
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: dependency-tree.txt, log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573055#comment-17573055
]
Kamalpreet edited comment on MDEP-812 at 7/29/22 4:47 PM:
--
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
[^dependency-tree.txt]
was (Author: JIRAUSER288713):
[~michael-o] Could you please let me know what's wrong? I know
{code:java}
maven-dependency-plugin:2.8:tree {code}
This is been resolved but what's the issue? Updated mvn dependency tree -
[^dependency-tree.txt]
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: dependency-tree.txt, log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MENFORCER-398) show rules processed
[
https://issues.apache.org/jira/browse/MENFORCER-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573087#comment-17573087
]
Slawomir Jaranowski commented on MENFORCER-398:
---
[~raupach]
Another idea - message like:
{code}
Rule executed (x.xx s)
{code}
always after rule finish, with name and time taken for execution.
> show rules processed
>
>
> Key: MENFORCER-398
> URL: https://issues.apache.org/jira/browse/MENFORCER-398
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: Delany
>Priority: Minor
> Labels: up-for-grabs
>
> Would be nice to have the option of showing what rules are processed, rather
> than relying on each rule to output its own success/failure message.
> {noformat}
> [INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (fail) @
> traderoot-maven-super ---
> [INFO] Adding ignore: module-info
>
> [INFO] Adding ignore: META-INF/versions/*/module-info
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-invoker-plugin] slawekjaranowski commented on pull request #134: Bump maven-plugins from 36 to 37
slawekjaranowski commented on PR #134: URL: https://github.com/apache/maven-invoker-plugin/pull/134#issuecomment-1199798563 @dependabot rebase -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gzm55 opened a new issue, #668: release .tar.gz format precompiled binary archives
gzm55 opened a new issue, #668: URL: https://github.com/apache/maven-mvnd/issues/668 Now until the 0.8.0 version, only .zip format packages is released. It is better to also release .tar.gz format like [maven](https://maven.apache.org/download.cgi) -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7523) support MAVEN_ARGS for Apache Maven 3.8.x as well
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573101#comment-17573101 ] Henning Schmiedehausen commented on MNG-7523: - Yes, 3.9.x would be sufficient for me (if it does come out in August). Happy to provide a PR here as well. > support MAVEN_ARGS for Apache Maven 3.8.x as well > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Improvement > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Priority: Minor > Fix For: 3.8.x-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] hgschmie opened a new pull request, #782: [MNG-7523] Backport MAVEN_ARGS support to 3.9.x
hgschmie opened a new pull request, #782: URL: https://github.com/apache/maven/pull/782 https://maven.apache.org/configure.html shows the MAVEN_ARGS environment variable which is extremely useful for customizing build scripts and processes. Unfortunately, it is only support for (unreleased) Maven 4. This patch backports support to Maven 3.9.x in the hope that this support would arrive much sooner than with Maven 4.x.x Following this checklist to help us incorporate your contribution quickly and easily: - [X] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X] Each commit in the pull request should have a meaningful subject line and body. - [X] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-7523) support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Schmiedehausen updated MNG-7523: Summary: support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x (was: support MAVEN_ARGS for Apache Maven 3.8.x as well ) > support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x > > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Improvement > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Priority: Minor > Fix For: 3.8.x-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7523) support MAVEN_ARGS for Apache Maven 3.8.x as well
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573102#comment-17573102 ] ASF GitHub Bot commented on MNG-7523: - hgschmie opened a new pull request, #782: URL: https://github.com/apache/maven/pull/782 https://maven.apache.org/configure.html shows the MAVEN_ARGS environment variable which is extremely useful for customizing build scripts and processes. Unfortunately, it is only support for (unreleased) Maven 4. This patch backports support to Maven 3.9.x in the hope that this support would arrive much sooner than with Maven 4.x.x Following this checklist to help us incorporate your contribution quickly and easily: - [X] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X] Each commit in the pull request should have a meaningful subject line and body. - [X] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ > support MAVEN_ARGS for Apache Maven 3.8.x as well > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Improvement > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Priority: Minor > Fix For: 3.8.x-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-7523) support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-7523: --- Assignee: Michael Osipov > support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x > > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Improvement > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.8.x-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7523) support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7523: Fix Version/s: 3.9.0-candidate (was: 3.8.x-candidate) > support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x > > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Improvement > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7523) Back port MAVEN_ARGS to Apache Maven 3.9.0
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7523: Summary: Back port MAVEN_ARGS to Apache Maven 3.9.0 (was: support MAVEN_ARGS for Apache Maven 3.8.x and 3.9.x ) > Back port MAVEN_ARGS to Apache Maven 3.9.0 > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Improvement > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-plugin] slawekjaranowski closed pull request #217: Bump org.eclipse.sisu.plexus from 0.0.0.M5 to 0.9.0.M1
slawekjaranowski closed pull request #217: Bump org.eclipse.sisu.plexus from 0.0.0.M5 to 0.9.0.M1 URL: https://github.com/apache/maven-dependency-plugin/pull/217 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #217: Bump org.eclipse.sisu.plexus from 0.0.0.M5 to 0.9.0.M1
dependabot[bot] commented on PR #217: URL: https://github.com/apache/maven-dependency-plugin/pull/217#issuecomment-1199835790 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] slawekjaranowski closed pull request #216: Bump org.eclipse.sisu.inject from 0.0.0.M5 to 0.9.0.M1
slawekjaranowski closed pull request #216: Bump org.eclipse.sisu.inject from 0.0.0.M5 to 0.9.0.M1 URL: https://github.com/apache/maven-dependency-plugin/pull/216 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #216: Bump org.eclipse.sisu.inject from 0.0.0.M5 to 0.9.0.M1
dependabot[bot] commented on PR #216: URL: https://github.com/apache/maven-dependency-plugin/pull/216#issuecomment-1199835980 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-7523) Back port MAVEN_ARGS to Apache Maven 3.9.0
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7523: Affects Version/s: (was: 3.8.x-candidate) > Back port MAVEN_ARGS to Apache Maven 3.9.0 > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Task > Components: Command Line, Core >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7523) Back port MAVEN_ARGS to Apache Maven 3.9.0
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7523: Issue Type: Task (was: Improvement) > Back port MAVEN_ARGS to Apache Maven 3.9.0 > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Task > Components: Command Line, Core >Affects Versions: 3.8.x-candidate >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7524) Add type coercion table for plugin parameters
[ https://issues.apache.org/jira/browse/MNG-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573109#comment-17573109 ] Michael Osipov commented on MNG-7524: - Yes, that is the one. No documention from us is complete :-D > Add type coercion table for plugin parameters > - > > Key: MNG-7524 > URL: https://issues.apache.org/jira/browse/MNG-7524 > Project: Maven > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Konrad Windszus >Priority: Major > > All plugin parameters in the pom.xml or on the command line are given as > strings. There should be a type coercion table in > https://maven.apache.org/guides/mini/guide-configuring-plugins.html#configuring-parameters > elaborating how those Strings are converted into the target type (i.e. which > method is called under the hood). > Compare with the discussion started in > https://lists.apache.org/thread/3q3bt89cms0pl7ylgkjhj708vgfqf927 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] hgschmie merged pull request #781: [MNG-7523] Backport MAVEN_ARGS support to 3.8.x
hgschmie merged PR #781: URL: https://github.com/apache/maven/pull/781 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7523) Back port MAVEN_ARGS to Apache Maven 3.9.0
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573112#comment-17573112 ] ASF GitHub Bot commented on MNG-7523: - hgschmie merged PR #781: URL: https://github.com/apache/maven/pull/781 > Back port MAVEN_ARGS to Apache Maven 3.9.0 > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Task > Components: Command Line, Core >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0-candidate > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7193) Introduce MAVEN_ARGS environment variable
[
https://issues.apache.org/jira/browse/MNG-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573113#comment-17573113
]
Michael Osipov commented on MNG-7193:
-
Fixed with
[29c53d67483445094270740477fa8909b6fd9f85|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=29c53d67483445094270740477fa8909b6fd9f85]
for {{maven-3.9.x}} branch.
> Introduce MAVEN_ARGS environment variable
> -
>
> Key: MNG-7193
> URL: https://issues.apache.org/jira/browse/MNG-7193
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.8.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-alpha-1, 4.0.0
>
>
> Over the last couple of years people demanded to always pass arguments down
> to Maven without supplying it specifically or repeat for every project over
> and over again in {{maven.config}}. Arguments like {{-B}} or {{-V}}.
> A new environment variable {{MAVEN_ARGS}} can be passed *before* the actual
> CLI arguments.
> Ideal precedence:
> {{MAVEN_ARGS}} is overwritten by {{maven.config}} is overwritten by CLI
> arguments. General to specific. Unfortunately, since {{MAVEN_ARGS}} will be
> passed just like CLI arguments there is no way to detect that these arguments
> came either via CLI or {{MAVEN_ARGS}}
> One option would be to add separator token which would be dropped internally
> thus makes it possible to differentiate between both, e.g,,
> {{MAVEN_ARGS_START [ARGS...] MAVEN_ARGS_STOP}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] michael-o closed pull request #782: [MNG-7523] Backport MAVEN_ARGS support to 3.9.x
michael-o closed pull request #782: [MNG-7523] Backport MAVEN_ARGS support to 3.9.x URL: https://github.com/apache/maven/pull/782 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] michael-o commented on pull request #782: [MNG-7523] Backport MAVEN_ARGS support to 3.9.x
michael-o commented on PR #782: URL: https://github.com/apache/maven/pull/782#issuecomment-1199847441 Merged manually. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-7193) Introduce MAVEN_ARGS environment variable
[
https://issues.apache.org/jira/browse/MNG-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7193:
Fix Version/s: 3.9.0
> Introduce MAVEN_ARGS environment variable
> -
>
> Key: MNG-7193
> URL: https://issues.apache.org/jira/browse/MNG-7193
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.8.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Over the last couple of years people demanded to always pass arguments down
> to Maven without supplying it specifically or repeat for every project over
> and over again in {{maven.config}}. Arguments like {{-B}} or {{-V}}.
> A new environment variable {{MAVEN_ARGS}} can be passed *before* the actual
> CLI arguments.
> Ideal precedence:
> {{MAVEN_ARGS}} is overwritten by {{maven.config}} is overwritten by CLI
> arguments. General to specific. Unfortunately, since {{MAVEN_ARGS}} will be
> passed just like CLI arguments there is no way to detect that these arguments
> came either via CLI or {{MAVEN_ARGS}}
> One option would be to add separator token which would be dropped internally
> thus makes it possible to differentiate between both, e.g,,
> {{MAVEN_ARGS_START [ARGS...] MAVEN_ARGS_STOP}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-7523) Back port MAVEN_ARGS to Apache Maven 3.9.0
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-7523. --- Fix Version/s: 3.9.0 (was: 3.9.0-candidate) Resolution: Done > Back port MAVEN_ARGS to Apache Maven 3.9.0 > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Task > Components: Command Line, Core >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0 > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7523) Back port MAVEN_ARGS to Apache Maven 3.9.0
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573116#comment-17573116 ] ASF GitHub Bot commented on MNG-7523: - michael-o commented on PR #782: URL: https://github.com/apache/maven/pull/782#issuecomment-1199847441 Merged manually. > Back port MAVEN_ARGS to Apache Maven 3.9.0 > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Task > Components: Command Line, Core >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0 > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7523) Back port MAVEN_ARGS to Apache Maven 3.9.0
[ https://issues.apache.org/jira/browse/MNG-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573117#comment-17573117 ] ASF GitHub Bot commented on MNG-7523: - michael-o closed pull request #782: [MNG-7523] Backport MAVEN_ARGS support to 3.9.x URL: https://github.com/apache/maven/pull/782 > Back port MAVEN_ARGS to Apache Maven 3.9.0 > -- > > Key: MNG-7523 > URL: https://issues.apache.org/jira/browse/MNG-7523 > Project: Maven > Issue Type: Task > Components: Command Line, Core >Reporter: Henning Schmiedehausen >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.9.0 > > > https://maven.apache.org/configure.html shows the MAVEN_ARGS environment > variable which is extremely useful for customizing build scripts and > processes. Unfortunately, it is only support for (unreleased) Maven 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEPLOY-298) mvn deploy retry on transient network failure
[ https://issues.apache.org/jira/browse/MDEPLOY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MDEPLOY-298. -- Fix Version/s: (was: wontfix-candidate) (was: waiting-for-feedback) Resolution: Not A Problem Please address *questions* to the users mailing list. > mvn deploy retry on transient network failure > - > > Key: MDEPLOY-298 > URL: https://issues.apache.org/jira/browse/MDEPLOY-298 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: Amruta Kawade >Priority: Major > > mvn deploy project uploads multiple files to remote repository. if after few > files upload there is network drop and user retries upload user might get 409 > file already exists. > gradle handles this with built in retry mechanism > [https://github.com/gradle/gradle/issues/8992#issue-431651478] > do we have something similar in maven ? > also how repository owners can identify whether file upload is completed for > any version of maven package ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MDEP-812:
-
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: dependency-tree.txt, log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7524) Add type coercion table for plugin parameters
[ https://issues.apache.org/jira/browse/MNG-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573123#comment-17573123 ] Sylwester Lachiewicz commented on MNG-7524: --- Similar date&time types. If we add it, one more reason for users to switch to Maven 3.9 > Add type coercion table for plugin parameters > - > > Key: MNG-7524 > URL: https://issues.apache.org/jira/browse/MNG-7524 > Project: Maven > Issue Type: Improvement > Components: Documentation: Guides >Reporter: Konrad Windszus >Priority: Major > > All plugin parameters in the pom.xml or on the command line are given as > strings. There should be a type coercion table in > https://maven.apache.org/guides/mini/guide-configuring-plugins.html#configuring-parameters > elaborating how those Strings are converted into the target type (i.e. which > method is called under the hood). > Compare with the discussion started in > https://lists.apache.org/thread/3q3bt89cms0pl7ylgkjhj708vgfqf927 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] michael-o commented on a diff in pull request #768: [MNG-7509] - Huge memory cost when parent pom widely used in a big project for dependencyManagement for maven-3.9.x
michael-o commented on code in PR #768:
URL: https://github.com/apache/maven/pull/768#discussion_r933543587
##
maven-resolver-provider/src/test/java/org/apache/maven/repository/internal/ArtifactDescriptorReaderDelegateTest.java:
##
@@ -0,0 +1,79 @@
+package org.apache.maven.repository.internal;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.maven.model.Dependency;
+import org.apache.maven.model.DependencyManagement;
+import org.apache.maven.model.Model;
+import org.eclipse.aether.artifact.DefaultArtifact;
+import org.eclipse.aether.resolution.ArtifactDescriptorRequest;
+import org.eclipse.aether.resolution.ArtifactDescriptorResult;
+
+public class ArtifactDescriptorReaderDelegateTest extends
AbstractRepositoryTestCase{
+public void testMNG7509()
Review Comment:
Please format this file according to our rules
--
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.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MNG-7509) Huge memory cost when parent pom widely used in a big project for dependencyManagement
[
https://issues.apache.org/jira/browse/MNG-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573125#comment-17573125
]
ASF GitHub Bot commented on MNG-7509:
-
michael-o commented on code in PR #768:
URL: https://github.com/apache/maven/pull/768#discussion_r933543587
##
maven-resolver-provider/src/test/java/org/apache/maven/repository/internal/ArtifactDescriptorReaderDelegateTest.java:
##
@@ -0,0 +1,79 @@
+package org.apache.maven.repository.internal;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.maven.model.Dependency;
+import org.apache.maven.model.DependencyManagement;
+import org.apache.maven.model.Model;
+import org.eclipse.aether.artifact.DefaultArtifact;
+import org.eclipse.aether.resolution.ArtifactDescriptorRequest;
+import org.eclipse.aether.resolution.ArtifactDescriptorResult;
+
+public class ArtifactDescriptorReaderDelegateTest extends
AbstractRepositoryTestCase{
+public void testMNG7509()
Review Comment:
Please format this file according to our rules
> Huge memory cost when parent pom widely used in a big project for
> dependencyManagement
> --
>
> Key: MNG-7509
> URL: https://issues.apache.org/jira/browse/MNG-7509
> Project: Maven
> Issue Type: Improvement
> Components: Performance
>Reporter: Xiong Luyao
>Priority: Critical
> Fix For: 3.9.0-candidate, 4.0.x-candidate
>
> Attachments: image-2022-07-09-09-37-53-823.png,
> image-2022-07-09-09-38-26-354.png, image-2022-07-09-10-27-12-668.png,
> image-2022-07-09-10-27-56-437.png, image-2022-07-09-10-28-05-706.png,
> image-2022-07-09-10-28-22-864.png, image-2022-07-09-10-28-35-341.png,
> image-2022-07-09-10-28-40-612.png, image-2022-07-09-10-29-04-045.png,
> image-2022-07-09-10-29-15-822.png, image-2022-07-09-10-29-21-991.png,
> image-2022-07-09-10-29-46-216.png, image-2022-07-09-10-29-51-456.png
>
>
> When maven try to resolve dependency relationship, it will create many
> instances of dependency / artifact, even the dependency/artifact content is
> totally same, but just in different pom models. It cost huge memory if there
> is a parent pom with dependencyManagement which managed a lot of
> dependencies, and this parent pom are implemented by many project libraries.
> (libraries_count * managedDependency_count) dependency instances will be
> created. For example, if there are 3000 libraries, and all the library
> introduce same parent pom which managed 3000 dependencies version. There will
> be 3000*3000 =9,000,000 dependency instances will be created. But most of
> them are same, in fact, we only need one instance for each dependency in
> parent pom (3000 dependency instances).
>
> I'm from eBay, and here is a real case in enterprise level project. We have
> about 3000 business domain libraries, there are dependency relationship
> between them. We need to build all libraries in one release to keep all the
> libraries in same release are based on same code. So we used a parent pom as
> a central management to manage all the version for a release, and introduced
> by those libraries. As below picture, when the release start, it will
> calculate and start with the library which doesn't depend on others, then
> start the library which dependency libraries are already built. Keep this
> process until all libraries are built.
> With current maven resolve logic, it costs huge memory in above ways to built
> libraries. And even the libraries have been released, if the project which
> contains a lot of above libraries, it also cost huge memory when building
> project.
> So current now, we have to specify version in each library pom files instead
> of using parent pom. We think we can make some enhancement for this case.
>
> !image-2022-07-09-09-37-53-823.png|width=493,height=226!
>
> Here is a thread dump when building a real project which depends on about
> 1000 above libraries. The top 5 objects are all related to
> org.
[jira] [Commented] (MDEP-812) Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
[
https://issues.apache.org/jira/browse/MDEP-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573126#comment-17573126
]
Michael Osipov commented on MDEP-812:
-
Try a dependency which is *not* in {{system}} scope and report.
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> --
>
> Key: MDEP-812
> URL: https://issues.apache.org/jira/browse/MDEP-812
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Reporter: Kamalpreet
>Priority: Blocker
> Attachments: dependency-tree.txt, log-1.txt, log.txt
>
>
> My profile :-
> {code:java}
>
>
> test
>
>
>
>
> maven-dependency-plugin
> 3.3.0
>
>
> getClasspathFilenames
>
> properties
>
>
>
>
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.1.0
>
>
>
> java
>
>
>
>
> test
> java
>
>
> -javaagent:${groupId:artifactId:jar}
>
> -classpath
>
> sampleTest
>
>
>
>
>
>
>
> {code}
> When running command
> {code:java}
> mvn exec:exec -P test{code}
> , I'm getting error
> {code:java}
> Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> [ERROR] Command execution failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)
> at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)
> at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> (ExecMojo.java:1000){code}
> Why maven-dependency-plugin is not able to resolve jar path? Is there anyway
> to fix this issue? Any help is much appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-invoker-plugin] slawekjaranowski merged pull request #135: [MINVOKER-306] - Fixed bug if only exclude-patterns specified
slawekjaranowski merged PR #135: URL: https://github.com/apache/maven-invoker-plugin/pull/135 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MINVOKER-306) Bugfix for case if invoker.test parameter contains only exclude-patterns
[ https://issues.apache.org/jira/browse/MINVOKER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MINVOKER-306. Fix Version/s: next-release Resolution: Fixed > Bugfix for case if invoker.test parameter contains only exclude-patterns > > > Key: MINVOKER-306 > URL: https://issues.apache.org/jira/browse/MINVOKER-306 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 3.2.2, 3.3.0 >Reporter: Vladimir V. Bychkov >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > > Behavior described in MINVOKER-140 dont't work in case if parameter > invoker.test contains only exclude patterns (without include patterns). As a > result list of appropriated tests is empty and tests are skipping. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-813) Require Maven 3.2.5
Slawomir Jaranowski created MDEP-813: Summary: Require Maven 3.2.5 Key: MDEP-813 URL: https://issues.apache.org/jira/browse/MDEP-813 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7193) Introduce MAVEN_ARGS environment variable
[
https://issues.apache.org/jira/browse/MNG-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573129#comment-17573129
]
Hudson commented on MNG-7193:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #59
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/59/
> Introduce MAVEN_ARGS environment variable
> -
>
> Key: MNG-7193
> URL: https://issues.apache.org/jira/browse/MNG-7193
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.8.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Over the last couple of years people demanded to always pass arguments down
> to Maven without supplying it specifically or repeat for every project over
> and over again in {{maven.config}}. Arguments like {{-B}} or {{-V}}.
> A new environment variable {{MAVEN_ARGS}} can be passed *before* the actual
> CLI arguments.
> Ideal precedence:
> {{MAVEN_ARGS}} is overwritten by {{maven.config}} is overwritten by CLI
> arguments. General to specific. Unfortunately, since {{MAVEN_ARGS}} will be
> passed just like CLI arguments there is no way to detect that these arguments
> came either via CLI or {{MAVEN_ARGS}}
> One option would be to add separator token which would be dropped internally
> thus makes it possible to differentiate between both, e.g,,
> {{MAVEN_ARGS_START [ARGS...] MAVEN_ARGS_STOP}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7443) Implement consistent logging between optional projects and optional profiles
[ https://issues.apache.org/jira/browse/MNG-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573130#comment-17573130 ] Hudson commented on MNG-7443: - Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #59 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/59/ > Implement consistent logging between optional projects and optional profiles > > > Key: MNG-7443 > URL: https://issues.apache.org/jira/browse/MNG-7443 > Project: Maven > Issue Type: Improvement > Components: Core, Logging >Affects Versions: 4.0.0-alpha-1 >Reporter: Giovanni van der Schelde >Assignee: Michael Osipov >Priority: Minor > Fix For: 4.0.0-alpha-1, 4.0.0 > > Attachments: example.png > > > Maven 4 introduces optional profiles and optional projects. However, the > feedback provided to the user on whether a project or profile has been > skipped is inconsistent between the two (see image attached). > For profiles, it will be logged twice: before and after the build. > For projects, it will be logged once: before the build. > The idea would be to log the information for skipped optional projects after > the build as well. > !example.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7160) Extension And Classloaders: difference of result given extension types
[
https://issues.apache.org/jira/browse/MNG-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573132#comment-17573132
]
Hudson commented on MNG-7160:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #34
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/34/
> Extension And Classloaders: difference of result given extension types
> --
>
> Key: MNG-7160
> URL: https://issues.apache.org/jira/browse/MNG-7160
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.2, 3.8.1
>Reporter: Nick Cross
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> I have a project that we use for all of our internal Red Hat builds (although
> primarily through its CLI mode hence not noticing this until
> [https://github.com/release-engineering/pom-manipulation-ext/issues/832] was
> submitted in the community). This project creates an extension (lib/ext
> style) but trying to use it as a ".mvn/extensions.xml" it _seems_ to get a
> classloader problem as _I think _the Maven Model/Plugin objects are created
> within a different classloader which means when the Plugin configuration is
> retrieved and cast to a Xpp3Dom object it fails. Is there some configuration
> we are missing or is there a problem in how the classloading in Maven for
> core extensions is working when using Xpp3Dom ?
> An reproducer branch is
> [https://github.com/rnc/pom-manipulation-ext/tree/ISSUE832]
> (Simply build and install the project, then use it on any simple Maven
> project with an extensions.xml with the command e.g. "mvn -X
> -DversionSuffix=redhat-1" )
> An example log is below:
> {noformat}
> Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
> Maven home: /home/rnc/Software/apache-maven-3.8.1
> Java version: 11.0.11, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-11-openjdk-11.0.11.0.9-2.fc33.x86_64
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.11.14-200.fc33.x86_64", arch: "amd64", family:
> "unix"
> [DEBUG] Reading global settings from
> /home/rnc/Software/apache-maven-3.8.1/conf/settings.xml
> [DEBUG] Reading user settings from /home/rnc/.m2/settings.xml
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> /home/rnc/.m2/repository
> [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for
> repository.jboss.org (http://repository.jboss.org/maven2).
> [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for
> snapshots.jboss.org (http://snapshots.jboss.org/maven2).
> [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for
> oss.sonatype.org/jboss-snapshots
> (http://oss.sonatype.org/content/repositories/jboss-snapshots).
> [DEBUG] Dependency collection stats {ConflictMarker.analyzeTime=644417,
> ConflictMarker.markTime=145101, ConflictMarker.nodeCount=11,
> ConflictIdSorter.graphTime=429885, ConflictIdSorter.topsortTime=359266,
> ConflictIdSorter.conflictIdCount=10, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=2854763, ConflictResolver.conflictItemCount=11,
> DefaultDependencyCollector.collectTime=122702048,
> DefaultDependencyCollector.transformTime=6173804}
> [DEBUG] org.commonjava.maven.ext:pom-manipulation-ext:jar:4.4-SNAPSHOT
> [DEBUG]javax.inject:javax.inject:jar:1:compile
> [DEBUG]org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.3.4:compile
> [DEBUG] javax.enterprise:cdi-api:jar:1.0:compile
> [DEBUG] javax.annotation:jsr250-api:jar:1.0:compile
> [DEBUG] org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.3.4:compile
> [DEBUG]
> org.codehaus.plexus:plexus-component-annotations:jar:1.5.5:compile
> [DEBUG] org.codehaus.plexus:plexus-classworlds:jar:2.5.2:compile
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:3.1.0:compile (version
> managed from default)
> [DEBUG]org.slf4j:slf4j-api:jar:1.7.30:compile
> [DEBUG] Populating class realm
> coreExtension>org.commonjava.maven.ext:pom-manipulation-ext:4.4-SNAPSHOT
> [DEBUG] Included
> /home/rnc/.m2/repository/org/commonjava/maven/ext/pom-manipulation-ext/4.4-SNAPSHOT/pom-manipulation-ext-4.4-SNAPSHOT.jar
> [DEBUG] Included
> /home/rnc/.m2/repository/javax/enterprise/cdi-api/1.0/cdi-api-1.0.jar
> [DEBUG] Included
> /home/rnc/.m2/repository/org/eclipse/sisu/org.eclipse.sisu.inject/0.3.4/org.eclipse.sisu.inject-0.3.4.jar
> [DEBUG] Included
> /home/rnc/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> [DEBUG] Included
> /home/rnc/.m2/repository/org/codehaus/plexus/plexus-utils/3.1.0/plexus-utils-3.1.0.jar
> [DEBUG] Populating class realm maven.ext
> [INFO] Running Maven Ma
[jira] [Commented] (MNG-6965) Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
[
https://issues.apache.org/jira/browse/MNG-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573133#comment-17573133
]
Hudson commented on MNG-6965:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #34
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/34/
> Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their
> classpath
>
>
> Key: MNG-6965
> URL: https://issues.apache.org/jira/browse/MNG-6965
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.6.0, 3.6.3
> Environment: Win7, Win10, at least one variant of Linux (not sure
> which)
>Reporter: Mark Nolan
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Labels: archetype
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
> Attachments: pom.xml
>
>
> A simple minimal archetype pom following the manual pages downloads
> plexus-utils 1.1, even though it is not (apparently) declared anywhere. This
> version is banned at my organization (edited to add: due to vulnerabilities),
> meaning such a pom always fails.
>
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> test
> test
> 0.0.1-SNAPSHOT
> maven-archetype
> test
>
>
>
> org.apache.maven.archetype
> archetype-packaging
> 3.1.2
>
>
>
>
>
> org.apache.maven.plugins
> maven-archetype-plugin
> 3.1.2
>
>
>
>
>
> {code}
> Running any goal, such as mvn -X clean, produces the following before the
> goal is executed:
> {code}
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=952800,
> ConflictMarker.markTime=586900, ConflictMarker.nodeCount=1,
> ConflictIdSorter.graphTime=549200, ConflictIdSorter.topsortTime=586700,
> ConflictIdSorter.conflictIdCount=1, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=3313100, ConflictResolver.conflictItemCount=1,
> DefaultDependencyCollector.collectTime=66890900,
> DefaultDependencyCollector.transformTime=8523500}
> [DEBUG] org.apache.maven.archetype:archetype-packaging:jar:3.1.2:
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> {code}
>
> As far as I can see, there is no declared dependency on plexus-utils:1.1.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
