[jira] [Comment Edited] (MDEP-532) Undeclared test resources fail build despite 'ignoreNonCompile'
[
https://issues.apache.org/jira/browse/MDEP-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778280#comment-17778280
]
Alexander Kriegisch edited comment on MDEP-532 at 10/22/23 4:57 AM:
OK, even though I had totally forgotten what this issue was about, simply
reading my own description enabled me to easily create a reproducer within 10
minutes. I am sure, you could have done that, too, [~elharo]. Notably, the
problem still reproduces in 3.6.0, not just in the old 2.10 from 7 years ago.
https://github.com/kriegaex/MDEP-532
was (Author: kriegaex):
OK, even though I had totally forgotten what this issue was about, simply
reading my own description enabled me to easily create a reproducer within 10
minutes. I am sure, you could have done that, too, [~elharo]. Notably, the
problem still reproduces in 3.6.0.
https://github.com/kriegaex/MDEP-532
> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---
>
> Key: MDEP-532
> URL: https://issues.apache.org/jira/browse/MDEP-532
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.10
> Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>Reporter: Alexander Kriegisch
>Priority: Minor
> Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.10
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
> *
>
>
>
>
> {code}
> Even though I want to ignore used undeclared test dependencies via
> {{true}}, my build fails like this in
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MDEP-532) Undeclared test resources fail build despite 'ignoreNonCompile'
[
https://issues.apache.org/jira/browse/MDEP-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778280#comment-17778280
]
Alexander Kriegisch edited comment on MDEP-532 at 10/22/23 4:56 AM:
OK, even though I had totally forgotten what this issue was about, simply
reading my own description enabled me to easily create a reproducer within 10
minutes. I am sure, you could have done that, too, [~elharo]. Notably, the
problem still reproduces in 3.6.0.
https://github.com/kriegaex/MDEP-532
was (Author: kriegaex):
OK, even though I had totally forgotten what this issue was about, simply
reading my own description enabled me to easily create a reproducer within 10
minutes. I am sure, you could have done that, too, [~elharo].
https://github.com/kriegaex/MDEP-532
> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---
>
> Key: MDEP-532
> URL: https://issues.apache.org/jira/browse/MDEP-532
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.10
> Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>Reporter: Alexander Kriegisch
>Priority: Minor
> Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.10
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
> *
>
>
>
>
> {code}
> Even though I want to ignore used undeclared test dependencies via
> {{true}}, my build fails like this in
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-532) Undeclared test resources fail build despite 'ignoreNonCompile'
[
https://issues.apache.org/jira/browse/MDEP-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778280#comment-17778280
]
Alexander Kriegisch commented on MDEP-532:
--
OK, even though I had totally forgotten what this issue was about, simply
reading my own description enabled me to easily create a reproducer within 10
minutes. I am sure, you could have done that, too, [~elharo].
https://github.com/kriegaex/MDEP-532
> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---
>
> Key: MDEP-532
> URL: https://issues.apache.org/jira/browse/MDEP-532
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.10
> Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>Reporter: Alexander Kriegisch
>Priority: Minor
> Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.10
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
> *
>
>
>
>
> {code}
> Even though I want to ignore used undeclared test dependencies via
> {{true}}, my build fails like this in
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-532) Undeclared test resources fail build despite 'ignoreNonCompile'
[
https://issues.apache.org/jira/browse/MDEP-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778277#comment-17778277
]
Alexander Kriegisch commented on MDEP-532:
--
[~elharo], of course I had a reproducer more than 7 years ago when I created
this issue. I can conclude from the Arquillian Spock stuff in the log and from
the creation date, which customer I was working for at the time, but of course
I did not take any code home from there. Therefore, I cannot use the original
project and condense it into a minimal reproducer now. This is what happens
when issues are left to rot for a long time, c'est la vie.
The only thing I could try is to recreate the situation from scratch according
to my own description. But this is something you could do, too. I think, it is
somewhat unfair to ignore an issue for 7 years and then burden the creator with
providing information you could have asked for much earlier. 🤨
> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---
>
> Key: MDEP-532
> URL: https://issues.apache.org/jira/browse/MDEP-532
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.10
> Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>Reporter: Alexander Kriegisch
>Priority: Minor
> Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.10
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
> *
>
>
>
>
> {code}
> Even though I want to ignore used undeclared test dependencies via
> {{true}}, my build fails like this in
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-765) Some goals result in download of Struts 1.3.8 POMs
[
https://issues.apache.org/jira/browse/MDEP-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778253#comment-17778253
]
Andrew Swan commented on MDEP-765:
--
{quote}Do you have a repro project?
{quote}
All the repro details are in the description, you just need to copy and paste
that POM into a new project.
> Some goals result in download of Struts 1.3.8 POMs
> --
>
> Key: MDEP-765
> URL: https://issues.apache.org/jira/browse/MDEP-765
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies, unpack-dependencies
>Affects Versions: 3.2.0
>Reporter: Andrew Swan
>Priority: Minor
> Labels: security, struts
>
> h1. Problem
> Executing certain goals of the {{dependency}} plugin (for example
> {{copy-dependencies}} and {{unpack-dependencies}}) causes various Struts
> 1.3.8 POMs to be downloaded to the user's local Maven repository. This
> version of Struts has known security vulnerabilities.
> h1. Reproduction
> Here's a minimal POM that demonstrates the problem:
> {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
> org.example
> dependency-plugin-demo
> 1.0-SNAPSHOT
>
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.2.0
>
>
>
>
> {code}
> Running {{mvn dependency:copy-dependencies}} results in the following output:
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< org.example:dependency-plugin-demo
> >-
> [INFO] Building dependency-plugin-demo 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.2.0:copy-dependencies (default-cli) @
> dependency-plugin-demo ---
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-core/1.3.8/struts-core-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-core/1.3.8/struts-core-1.3.8.pom
> (4.3 kB at 2.8 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-parent/1.3.8/struts-parent-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-parent/1.3.8/struts-parent-1.3.8.pom
> (9.8 kB at 21 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-master/4/struts-master-4.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-master/4/struts-master-4.pom
> (11 kB at 25 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-taglib/1.3.8/struts-taglib-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-taglib/1.3.8/struts-taglib-1.3.8.pom
> (3.1 kB at 6.4 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-tiles/1.3.8/struts-tiles-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-tiles/1.3.8/struts-tiles-1.3.8.pom
> (2.9 kB at 5.2 kB/s)
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 4.297 s
> [INFO] Finished at: 2021-09-09T14:18:10+10:00
> [INFO]
> {code}
> h1. Workaround
> One workaround is to downgrade to version 2.8 of the plugin, however this may
> also require the user to modify their plugin configuration, because the
> semantics of configuration options like {{includeScope}} have changed even
> between minor versions 3.1.2 and 3.2.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] Is mvnd "safe" for parallel builds where "mvn" alone is not? [maven-mvnd]
jimklimov commented on issue #896: URL: https://github.com/apache/maven-mvnd/issues/896#issuecomment-1773940773 Thanks for the options, my first shot missed the "file-gav" part ;) Putting them into SCM as part of the components' source seems a bit like overkill... they should be buildable anywhere (and maybe with different environmental settings), right? For posterity and my own back-tracking, I'll exploring the `MAVEN_OPTS` envvar instead for now, so each Jenkins worker might set what is relevant there... -- 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
Re: [I] Is mvnd "safe" for parallel builds where "mvn" alone is not? [maven-mvnd]
cstamas commented on issue #896: URL: https://github.com/apache/maven-mvnd/issues/896#issuecomment-1773936232 create (and check in into SCM) a file in project like this: ``` .mvn/maven.config ``` with contents ``` -Daether.syncContext.named.factory=file-lock -Daether.syncContext.named.nameMapper=file-gav ``` -- 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] [Created] (MENFORCER-493) Provide a more meaningful hint after deprecation of goal display-info
Philipp Ottlinger created MENFORCER-493:
---
Summary: Provide a more meaningful hint after deprecation of goal
display-info
Key: MENFORCER-493
URL: https://issues.apache.org/jira/browse/MENFORCER-493
Project: Maven Enforcer Plugin
Issue Type: Wish
Affects Versions: 3.4.1
Reporter: Philipp Ottlinger
After upgrading to 3.4.1 I see many warnings in my builds
{{[WARNING] Goal 'display-info' is deprecated: please use mvn --version}}
as I use
{{enforcer:display-info}}
as part of my defaultGoal definition.
I do know mvn --version but I'm not sure how to integrate it into my build as I
did with display-info as part of my defaultGoal. Adding a new build step to all
my projects seems a rather cumbersome way of deprecating this functionality.
Is there a better way to get these build informations into my build logs? If
so, I'd love to see this instead of a build warning.
Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] Is mvnd "safe" for parallel builds where "mvn" alone is not? [maven-mvnd]
jimklimov commented on issue #896: URL: https://github.com/apache/maven-mvnd/issues/896#issuecomment-1773928553 Oh that funny moment when the huge internet looks like a small village: https://www.mail-archive.com/users@maven.apache.org/msg144072.html > Configuration should be as easy as setting “aether.syncContext.named.factory” to “file-lock” So looking for some best way among several possibilities, to pass `aether.syncContext.named.factory=file-lock` from CI to maven and not confuse possible other (pre 3.9.x) tool versions along the way :) -- 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] (MPLUGIN-485) Upgrade Parent to 40
[ https://issues.apache.org/jira/browse/MPLUGIN-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MPLUGIN-485. --- Fix Version/s: next-release Resolution: Fixed > Upgrade Parent to 40 > > > Key: MPLUGIN-485 > URL: https://issues.apache.org/jira/browse/MPLUGIN-485 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-485] Upgrade Parent to 40 [maven-plugin-tools]
slawekjaranowski merged PR #230: URL: https://github.com/apache/maven-plugin-tools/pull/230 -- 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] (MPLUGIN-485) Upgrade Parent to 40
[ https://issues.apache.org/jira/browse/MPLUGIN-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778223#comment-17778223 ] ASF GitHub Bot commented on MPLUGIN-485: slawekjaranowski merged PR #230: URL: https://github.com/apache/maven-plugin-tools/pull/230 > Upgrade Parent to 40 > > > Key: MPLUGIN-485 > URL: https://issues.apache.org/jira/browse/MPLUGIN-485 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MDEP-889) javax.inject is undeclared but used
[ https://issues.apache.org/jira/browse/MDEP-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MDEP-889. Resolution: Fixed > javax.inject is undeclared but used > --- > > Key: MDEP-889 > URL: https://issues.apache.org/jira/browse/MDEP-889 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-889) javax.inject is undeclared but used
[ https://issues.apache.org/jira/browse/MDEP-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MDEP-889: --- Summary: javax.inject is undeclared but used (was: javax.inject is undelcared but used) > javax.inject is undeclared but used > --- > > Key: MDEP-889 > URL: https://issues.apache.org/jira/browse/MDEP-889 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-703) something points to codehaus
[ https://issues.apache.org/jira/browse/MDEP-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-703: Fix Version/s: (was: waiting-for-feedback) > something points to codehaus > > > Key: MDEP-703 > URL: https://issues.apache.org/jira/browse/MDEP-703 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > seen in integration test logs: > [DEBUG] Using mirror mrm-maven-plugin (http://localhost:46045) for > codehaus.snapshots (http://snapshots.repository.codehaus.org). > [DEBUG] Using mirror mrm-maven-plugin (http://localhost:46045) for snapshots > (http://snapshots.maven.codehaus.org/maven2). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-888) Commons-lang 2.13.0
[ https://issues.apache.org/jira/browse/MDEP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778187#comment-17778187 ] ASF GitHub Bot commented on MDEP-888: - elharo merged PR #341: URL: https://github.com/apache/maven-dependency-plugin/pull/341 > Commons-lang 2.13.0 > --- > > Key: MDEP-888 > URL: https://issues.apache.org/jira/browse/MDEP-888 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MDEP-888] Update used but undeclared commons-lang3 to 3.13.0 [maven-dependency-plugin]
elharo merged PR #341: URL: https://github.com/apache/maven-dependency-plugin/pull/341 -- 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-889) javax.inject is undelcared but used
[ https://issues.apache.org/jira/browse/MDEP-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778186#comment-17778186 ] ASF GitHub Bot commented on MDEP-889: - elharo merged PR #343: URL: https://github.com/apache/maven-dependency-plugin/pull/343 > javax.inject is undelcared but used > --- > > Key: MDEP-889 > URL: https://issues.apache.org/jira/browse/MDEP-889 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MDEP-889] declare javax.inject explicitly [maven-dependency-plugin]
elharo merged PR #343: URL: https://github.com/apache/maven-dependency-plugin/pull/343 -- 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
Re: [PR] Assorted grammar nits on the home page [maven-dependency-plugin]
elharo merged PR #345: URL: https://github.com/apache/maven-dependency-plugin/pull/345 -- 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-887) Commons-IO to 2.14.0
[ https://issues.apache.org/jira/browse/MDEP-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778185#comment-17778185 ] ASF GitHub Bot commented on MDEP-887: - elharo merged PR #340: URL: https://github.com/apache/maven-dependency-plugin/pull/340 > Commons-IO to 2.14.0 > > > Key: MDEP-887 > URL: https://issues.apache.org/jira/browse/MDEP-887 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MDEP-887] commons-io to 2.14.0 [maven-dependency-plugin]
elharo merged PR #340: URL: https://github.com/apache/maven-dependency-plugin/pull/340 -- 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
Re: [I] Is mvnd "safe" for parallel builds where "mvn" alone is not? [maven-mvnd]
cstamas commented on issue #896: URL: https://github.com/apache/maven-mvnd/issues/896#issuecomment-1773851213 Maven 3.9 introduced "locks" for local repository, trying to solve exactly that: shared access to local repository from multiple processes... So best would be to try it out (hopefully using some sound FS like ext4 or alike, no windows in picture). -- 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
Re: [I] Is mvnd "safe" for parallel builds where "mvn" alone is not? [maven-mvnd]
jimklimov commented on issue #896: URL: https://github.com/apache/maven-mvnd/issues/896#issuecomment-1773848683 Thanks for suggestions, checked that the workers used maven 3.8.6... So change to 3.9.x could just fix the situation while keeping all those build calls independent as they are now? -- 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
Re: [I] Is mvnd "safe" for parallel builds where "mvn" alone is not? [maven-mvnd]
cstamas commented on issue #896: URL: https://github.com/apache/maven-mvnd/issues/896#issuecomment-1773845614 First, please forget the "built in" parallel builder, use instead this https://github.com/takari/takari-smart-builder (same is used by mvnd). Second, did you try maven 3.9.x (preferably latest) version? You could use file locking for start (if local repository is on local FS) -- 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] (WAGON-632) Java 8 minimum
[ https://issues.apache.org/jira/browse/WAGON-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778155#comment-17778155 ] ASF GitHub Bot commented on WAGON-632: -- slachiewicz commented on PR #89: URL: https://github.com/apache/maven-wagon/pull/89#issuecomment-1773844321 implicitly fixed by parent pom update https://issues.apache.org/jira/browse/WAGON-634 > Java 8 minimum > -- > > Key: WAGON-632 > URL: https://issues.apache.org/jira/browse/WAGON-632 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 4.0.0-M1 > > > Mostly so we can get a recent version of commons IO to replace bugs in Plexus > utils -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [WAGON-632] Java 8 [maven-wagon]
slachiewicz commented on PR #89: URL: https://github.com/apache/maven-wagon/pull/89#issuecomment-1773844321 implicitly fixed by parent pom update https://issues.apache.org/jira/browse/WAGON-634 -- 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
Re: [PR] Bump mina-core from 2.0.5 to 2.0.22 in /wagon-providers/wagon-ssh-common-test [maven-wagon]
slachiewicz commented on PR #81: URL: https://github.com/apache/maven-wagon/pull/81#issuecomment-1773844559 @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
Re: [PR] Bump commons-net from 3.6 to 3.9.0 in /wagon-providers/wagon-ftp [maven-wagon]
slachiewicz commented on PR #87: URL: https://github.com/apache/maven-wagon/pull/87#issuecomment-1773844508 @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
[jira] [Commented] (WAGON-632) Java 8 minimum
[ https://issues.apache.org/jira/browse/WAGON-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778156#comment-17778156 ] ASF GitHub Bot commented on WAGON-632: -- slachiewicz closed pull request #89: [WAGON-632] Java 8 URL: https://github.com/apache/maven-wagon/pull/89 > Java 8 minimum > -- > > Key: WAGON-632 > URL: https://issues.apache.org/jira/browse/WAGON-632 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 4.0.0-M1 > > > Mostly so we can get a recent version of commons IO to replace bugs in Plexus > utils -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (WAGON-632) Java 8 minimum
[ https://issues.apache.org/jira/browse/WAGON-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed WAGON-632. -- Resolution: Fixed implicitly fixed by parent pom update https://issues.apache.org/jira/browse/WAGON-634 > Java 8 minimum > -- > > Key: WAGON-632 > URL: https://issues.apache.org/jira/browse/WAGON-632 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 4.0.0-M1 > > > Mostly so we can get a recent version of commons IO to replace bugs in Plexus > utils -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [WAGON-632] Java 8 [maven-wagon]
slachiewicz closed pull request #89: [WAGON-632] Java 8 URL: https://github.com/apache/maven-wagon/pull/89 -- 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] [Assigned] (WAGON-632) Java 8 minimum
[ https://issues.apache.org/jira/browse/WAGON-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned WAGON-632: -- Assignee: Sylwester Lachiewicz > Java 8 minimum > -- > > Key: WAGON-632 > URL: https://issues.apache.org/jira/browse/WAGON-632 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 4.0.0-M1 > > > Mostly so we can get a recent version of commons IO to replace bugs in Plexus > utils -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (WAGON-634) Upgrade parent POM to version 40
[ https://issues.apache.org/jira/browse/WAGON-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778153#comment-17778153 ] ASF GitHub Bot commented on WAGON-634: -- slachiewicz merged PR #93: URL: https://github.com/apache/maven-wagon/pull/93 > Upgrade parent POM to version 40 > > > Key: WAGON-634 > URL: https://issues.apache.org/jira/browse/WAGON-634 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 4.0.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (WAGON-634) Upgrade parent POM to version 40
[ https://issues.apache.org/jira/browse/WAGON-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed WAGON-634. -- Resolution: Fixed > Upgrade parent POM to version 40 > > > Key: WAGON-634 > URL: https://issues.apache.org/jira/browse/WAGON-634 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 4.0.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [WAGON-634] Bump parent pom to 40 [maven-wagon]
slachiewicz merged PR #93: URL: https://github.com/apache/maven-wagon/pull/93 -- 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] (MSKINS-239) Remove support for defunct Flattr site
[ https://issues.apache.org/jira/browse/MSKINS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778152#comment-17778152 ] Sylwester Lachiewicz commented on MSKINS-239: - Done in [7cb683f5505badcb7ecac9569c8445ae435377d8|https://github.com/apache/maven-fluido-skin/commit/7cb683f5505badcb7ecac9569c8445ae435377d8] > Remove support for defunct Flattr site > -- > > Key: MSKINS-239 > URL: https://issues.apache.org/jira/browse/MSKINS-239 > Project: Maven Skins > Issue Type: Bug >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: fluido-2.0.0-M9 > > > Flattr no longer offers service and all links to api/button returns 404. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSKINS-239) Remove support for defunct Flattr site
[ https://issues.apache.org/jira/browse/MSKINS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778151#comment-17778151 ] ASF GitHub Bot commented on MSKINS-239: --- slachiewicz merged PR #57: URL: https://github.com/apache/maven-fluido-skin/pull/57 > Remove support for defunct Flattr site > -- > > Key: MSKINS-239 > URL: https://issues.apache.org/jira/browse/MSKINS-239 > Project: Maven Skins > Issue Type: Bug >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: fluido-2.0.0-M9 > > > Flattr no longer offers service and all links to api/button returns 404. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSKINS-239) Remove support for defunct Flattr site
[ https://issues.apache.org/jira/browse/MSKINS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSKINS-239. --- Resolution: Fixed > Remove support for defunct Flattr site > -- > > Key: MSKINS-239 > URL: https://issues.apache.org/jira/browse/MSKINS-239 > Project: Maven Skins > Issue Type: Bug >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: fluido-2.0.0-M9 > > > Flattr no longer offers service and all links to api/button returns 404. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MSKINS-239] Drop support for defunct Flattr.com [maven-fluido-skin]
slachiewicz merged PR #57: URL: https://github.com/apache/maven-fluido-skin/pull/57 -- 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
Re: [PR] Bump asmVersion from 9.5 to 9.6 [maven-plugin-tools]
slachiewicz closed pull request #228: Bump asmVersion from 9.5 to 9.6 URL: https://github.com/apache/maven-plugin-tools/pull/228 -- 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] (MPLUGIN-488) Bump asmVersion from 9.5 to 9.6
[ https://issues.apache.org/jira/browse/MPLUGIN-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778144#comment-17778144 ] ASF GitHub Bot commented on MPLUGIN-488: slachiewicz opened a new pull request, #233: URL: https://github.com/apache/maven-plugin-tools/pull/233 (no comment) > Bump asmVersion from 9.5 to 9.6 > --- > > Key: MPLUGIN-488 > URL: https://issues.apache.org/jira/browse/MPLUGIN-488 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump asmVersion from 9.5 to 9.6 [maven-plugin-tools]
dependabot[bot] commented on PR #228: URL: https://github.com/apache/maven-plugin-tools/pull/228#issuecomment-1773839896 OK, I won't notify you again about this release, but will get in touch when a new version is available. 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
Re: [PR] Bump asmVersion from 9.5 to 9.6 [maven-plugin-tools]
slachiewicz commented on PR #228: URL: https://github.com/apache/maven-plugin-tools/pull/228#issuecomment-1773839861 superseded by #233 -- 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] [Created] (MPLUGIN-488) Bump asmVersion from 9.5 to 9.6
Sylwester Lachiewicz created MPLUGIN-488: Summary: Bump asmVersion from 9.5 to 9.6 Key: MPLUGIN-488 URL: https://issues.apache.org/jira/browse/MPLUGIN-488 Project: Maven Plugin Tools Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Assignee: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-487) Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0
[ https://issues.apache.org/jira/browse/MPLUGIN-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778140#comment-17778140 ] ASF GitHub Bot commented on MPLUGIN-487: slachiewicz merged PR #231: URL: https://github.com/apache/maven-plugin-tools/pull/231 > Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0 > > > Key: MPLUGIN-487 > URL: https://issues.apache.org/jira/browse/MPLUGIN-487 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > > [https://github.com/codehaus-plexus/plexus-languages/releases/tag/plexus-languages-1.2.0] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPLUGIN-487) Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0
[ https://issues.apache.org/jira/browse/MPLUGIN-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPLUGIN-487. Resolution: Fixed > Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0 > > > Key: MPLUGIN-487 > URL: https://issues.apache.org/jira/browse/MPLUGIN-487 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > > [https://github.com/codehaus-plexus/plexus-languages/releases/tag/plexus-languages-1.2.0] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-487] Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0 [maven-plugin-tools]
slachiewicz merged PR #231: URL: https://github.com/apache/maven-plugin-tools/pull/231 -- 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] (MPLUGIN-487) Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0
[ https://issues.apache.org/jira/browse/MPLUGIN-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPLUGIN-487: - Description: [https://github.com/codehaus-plexus/plexus-languages/releases/tag/plexus-languages-1.2.0] > Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0 > > > Key: MPLUGIN-487 > URL: https://issues.apache.org/jira/browse/MPLUGIN-487 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > > [https://github.com/codehaus-plexus/plexus-languages/releases/tag/plexus-languages-1.2.0] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPLUGIN-487) Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0
Sylwester Lachiewicz created MPLUGIN-487: Summary: Bump org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0 Key: MPLUGIN-487 URL: https://issues.apache.org/jira/browse/MPLUGIN-487 Project: Maven Plugin Tools Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Assignee: Sylwester Lachiewicz Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPLUGIN-484) Downgrade plexus-xml to 3.0.0
[ https://issues.apache.org/jira/browse/MPLUGIN-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPLUGIN-484. Resolution: Fixed > Downgrade plexus-xml to 3.0.0 > - > > Key: MPLUGIN-484 > URL: https://issues.apache.org/jira/browse/MPLUGIN-484 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > > To keep compatibility with Maven 3.x we must use: > plexus-utils 4.x and plexus-xml 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPLUGIN-484) Downgrade plexus-xml to 3.0.0
[ https://issues.apache.org/jira/browse/MPLUGIN-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPLUGIN-484: - Fix Version/s: next-release > Downgrade plexus-xml to 3.0.0 > - > > Key: MPLUGIN-484 > URL: https://issues.apache.org/jira/browse/MPLUGIN-484 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.1 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > > To keep compatibility with Maven 3.x we must use: > plexus-utils 4.x and plexus-xml 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-484) Downgrade plexus-xml to 3.0.0
[ https://issues.apache.org/jira/browse/MPLUGIN-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778139#comment-17778139 ] ASF GitHub Bot commented on MPLUGIN-484: slachiewicz merged PR #229: URL: https://github.com/apache/maven-plugin-tools/pull/229 > Downgrade plexus-xml to 3.0.0 > - > > Key: MPLUGIN-484 > URL: https://issues.apache.org/jira/browse/MPLUGIN-484 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > > To keep compatibility with Maven 3.x we must use: > plexus-utils 4.x and plexus-xml 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPLUGIN-484) Downgrade plexus-xml to 3.0.0
[ https://issues.apache.org/jira/browse/MPLUGIN-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPLUGIN-484: Assignee: Sylwester Lachiewicz > Downgrade plexus-xml to 3.0.0 > - > > Key: MPLUGIN-484 > URL: https://issues.apache.org/jira/browse/MPLUGIN-484 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > > To keep compatibility with Maven 3.x we must use: > plexus-utils 4.x and plexus-xml 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-484] Downgrade plexus-xml to 3.0.0 - restore Maven 3.x compatibility [maven-plugin-tools]
slachiewicz merged PR #229: URL: https://github.com/apache/maven-plugin-tools/pull/229 -- 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-7877) Attach the build POM and simplify the build/consumer implementation
[
https://issues.apache.org/jira/browse/MNG-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7877:
---
Description:
The build/consumer implementation was initially written in SAX, later rewritten
using Xpp3, then Stax, but this implementation is quite complex with a big
drawback in that it affects multiple places in the code where the models are
loaded.
Rewriting the transformation on top of the object model remove those problems,
at the cost of loosing the comments in the consumer POM. The build POM is thus
attached with the original unmodified POM, with {{build}} classifier to
differentiate.
was:
The build/consumer implementation was initially written in SAX, later rewritten
using Xpp3, then Stax, but this implementation is quite complex with a big
drawback in that it affects multiple places in the code where the models are
loaded.
Rewriting the transformation on top of the object model remove those problems,
at the cost of loosing the comments in the POM. A build POM is thus attached
with the original unmodified POM.
> Attach the build POM and simplify the build/consumer implementation
> ---
>
> Key: MNG-7877
> URL: https://issues.apache.org/jira/browse/MNG-7877
> Project: Maven
> Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-alpha-8, 4.0.0
>
>
> The build/consumer implementation was initially written in SAX, later
> rewritten using Xpp3, then Stax, but this implementation is quite complex
> with a big drawback in that it affects multiple places in the code where the
> models are loaded.
> Rewriting the transformation on top of the object model remove those
> problems, at the cost of loosing the comments in the consumer POM. The build
> POM is thus attached with the original unmodified POM, with {{build}}
> classifier to differentiate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7911) Require JDK 11 and support JDK 21 at build time
[ https://issues.apache.org/jira/browse/MNG-7911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7911: --- Description: keep JDK 8 requirement for runtime > Require JDK 11 and support JDK 21 at build time > --- > > Key: MNG-7911 > URL: https://issues.apache.org/jira/browse/MNG-7911 > Project: Maven > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-alpha-8, 4.0.0 > > > keep JDK 8 requirement for runtime -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-621) New goal to "fix-warnings"
[ https://issues.apache.org/jira/browse/MDEP-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778104#comment-17778104 ] Elliotte Rusty Harold commented on MDEP-621: This is a good idea but hard to implement. I don't think it would be OK to do a clean install first though. > New goal to "fix-warnings" > -- > > Key: MDEP-621 > URL: https://issues.apache.org/jira/browse/MDEP-621 > Project: Maven Dependency Plugin > Issue Type: New Feature > Components: analyze >Affects Versions: 3.1.1 >Reporter: Alex Collins >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The analyze goal works well in some scenarios, but time and time again I come > across a large project (100s modules and 1000s dependenencies) where I want > fix the warnings that the "analyze" goal produces. > Fixing these dependency issues will make builds faster, and with large > projects, Maybe 2-5x faster. As they reduce IO and CPU usage, allow the > reactor more flexibily in build order, so parallel builds can make better > usage of the CPU cores. > This is hard to automate, and I've tried a few scripts people have written, > but they're generally not up to the job, typically they are basic: > * Only work on one pom, not multi-module projects. > * Do multi-module, but don't follow reactor order. > * Try to remove the wrong dependencies. > * Don't check the removal worked OK, e.g. > ** Removing annotation processors. > ** Removing "magic" jars, those that appear unused, but actually are some > how (e.g. some Spring class-path scanning magic). > My thought is to introduce a new goal that peforms the following steps for > each pom in reactor order: > # Verify the module isn't broken to start with (clean install). > # Check-point (save a backup of the pom.xml). > # Perform dependency analysis. > # Add in all used undeclared dependencies. > # Verify - check that didn't break anything (clean install) and give up if > it did. > # Check-point. > # Remove all unused declared dependencies (i.e. see if any of them are > needed at all, this assumes that there is a good probabily that is the case > and is quicker than testing each in order). > # Check-point > # Verify. > # For each unused declared dependency. > # Check-point. > # Remove. > # Validate. > I'm making a key assumption here that if a module's tests pass, then it's > just fine. That's a big assumption, but I see no feasible way to make this > work otherwise. > Many projects have "terminal" modules, i.e. modules that have no downstream > dependencies. It would be risky to remove "magic" dependencies, so it maybe > the case we want to bookend this process by > # Determine "terminal" modules. > # For each terminal module, create a list of their dependencies. > # Do the fix as discussed above. > # For each terminal module, create a list of their dependencies. > # Re-instate any that were removed. > Whadaythink? > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MDEP-703) something points to codehaus
[ https://issues.apache.org/jira/browse/MDEP-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MDEP-703. Resolution: Fixed seems to have been resolved by one dependency upgrade or another. I just looked and couldn't find it now. > something points to codehaus > > > Key: MDEP-703 > URL: https://issues.apache.org/jira/browse/MDEP-703 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > Fix For: waiting-for-feedback > > > seen in integration test logs: > [DEBUG] Using mirror mrm-maven-plugin (http://localhost:46045) for > codehaus.snapshots (http://snapshots.repository.codehaus.org). > [DEBUG] Using mirror mrm-maven-plugin (http://localhost:46045) for snapshots > (http://snapshots.maven.codehaus.org/maven2). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-703) something points to codehaus
[ https://issues.apache.org/jira/browse/MDEP-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MDEP-703. -- > something points to codehaus > > > Key: MDEP-703 > URL: https://issues.apache.org/jira/browse/MDEP-703 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > Fix For: waiting-for-feedback > > > seen in integration test logs: > [DEBUG] Using mirror mrm-maven-plugin (http://localhost:46045) for > codehaus.snapshots (http://snapshots.repository.codehaus.org). > [DEBUG] Using mirror mrm-maven-plugin (http://localhost:46045) for snapshots > (http://snapshots.maven.codehaus.org/maven2). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Assorted grammar nits on the home page [maven-dependency-plugin]
elharo opened a new pull request, #345: URL: https://github.com/apache/maven-dependency-plugin/pull/345 (no comment) -- 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
[I] Is mvnd "safe" for parallel builds where "mvn" alone is not? [maven-mvnd]
jimklimov opened a new issue, #896: URL: https://github.com/apache/maven-mvnd/issues/896 Related context: > Generally, for using mvnd on the CI: > * If you expect faster builds thanks to building Maven modules in parallel, then you may consider using stock Maven's `-T` option. But be warned that it may lead to issues caused by the fact that stock Maven (as of 3.8.2) does not prevent concurrent writes to the same file in the local Maven repo. BTW mvnd 0.6.0 suffers from this problem as well. <...> _Originally posted by @ppalaga in https://github.com/apache/maven-mvnd/issues/498#issuecomment-943760507_ My question is rather this: we have CI jobs running `mvn` tests under the same user account on the same agent - whether for fully independent jobs, or for different parallel stages of the same job (spawning a burst of tests for different components etc.) This approach did hiccup with unexpected errors which we assume to be the cross-maven corruption of the same local repository, when downloads happened to run simultaneously and fetched the same files. We theorized of a few possible solutions, no idea if any are viable though (hence the question): * convert to use `mvnd`, hoping it would take care of parallelly-requested downloads to same local repo in a sane manner (even if sequentializing them internally, etc.) and transparently for `mvn` "client" calls; * use locking (e.g. Jenkins lockable resources) to ensure sequential runs, and separate the maven operations to first call an `mvn validate` before each longer build/test (assuming this would fetch all needed files) as the sequential operation, then do actual `mvn test/compile/package/etc.` as the parallel operations which rely on files fetched safely before. * With this I'm not sure if a later downloading session from another maven WOULD NOT endeavour to clean up the local repository from files it does not need for the current build this other maven is handling now. * Use separate maven local repos for each independent operation. This raises a few concerns however: * Seems to be wasteful on disk space, and on losing the benefits of having pre-fetched files on the workers -- especially if(?) we can not layer several local repos, e.g. use a separate location for "our" components, but a shared one for third-party dependencies. * Internet lore https://mkyong.com/maven/where-is-maven-local-repository/ or https://stackoverflow.com/questions/28767088/maven-local-repository-setting-being-overridden hints how... Any insights would be most welcome :) -- 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] [Updated] (MDEP-722) Verbose tree does not appropriately handle multi module projects
[ https://issues.apache.org/jira/browse/MDEP-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MDEP-722: --- Issue Type: Bug (was: Improvement) > Verbose tree does not appropriately handle multi module projects > > > Key: MDEP-722 > URL: https://issues.apache.org/jira/browse/MDEP-722 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Ian Lavallee >Priority: Minor > Fix For: waiting-for-feedback > > > When the verbose tree is processing a module that has another module as a > dependency it will print/create the parent module in proper verbose form but > the dependency module will be printed in non verbose form. > This is not a massive issue as the dependent module will still be printed in > verbose mode separately so a developer still has the info available but not > in the most convenient form. > Relevant classes are TreeMojo, VerboseDependencyGraphBuilder and once this is > fixed the warning message in the verbose serializers should be removed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-771) Broken link from Introduction - Examples to "Resolving Conflicts Using the Dependency Tree"
[ https://issues.apache.org/jira/browse/MDEP-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778093#comment-17778093 ] ASF GitHub Bot commented on MDEP-771: - elharo opened a new pull request, #344: URL: https://github.com/apache/maven-dependency-plugin/pull/344 (no comment) > Broken link from Introduction - Examples to "Resolving Conflicts Using the > Dependency Tree" > --- > > Key: MDEP-771 > URL: https://issues.apache.org/jira/browse/MDEP-771 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Philippe Cloutier >Assignee: Elliotte Rusty Harold >Priority: Minor > Labels: up-for-grabs > > [The Introduction page's Examples > section|http://maven.apache.org/plugins/maven-dependency-plugin/index.html] > contains a link titled "Resolving Conflicts Using the Dependency Tree" to the > following URL: > http://maven.apache.org/plugins/maven-dependency-plugin/index.html > That URL unfortunately yields a Page Not Found error. The content can be seen > on > https://maven.apache.org/plugins-archives/maven-dependency-plugin-2.4/examples/resolving-conflicts-using-the-dependency-tree.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [MDEP-771] Remove broken 404 link [maven-dependency-plugin]
elharo opened a new pull request, #344: URL: https://github.com/apache/maven-dependency-plugin/pull/344 (no comment) -- 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] [Assigned] (MDEP-771) Broken link from Introduction - Examples to "Resolving Conflicts Using the Dependency Tree"
[ https://issues.apache.org/jira/browse/MDEP-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold reassigned MDEP-771: -- Assignee: Elliotte Rusty Harold > Broken link from Introduction - Examples to "Resolving Conflicts Using the > Dependency Tree" > --- > > Key: MDEP-771 > URL: https://issues.apache.org/jira/browse/MDEP-771 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Philippe Cloutier >Assignee: Elliotte Rusty Harold >Priority: Minor > Labels: up-for-grabs > > [The Introduction page's Examples > section|http://maven.apache.org/plugins/maven-dependency-plugin/index.html] > contains a link titled "Resolving Conflicts Using the Dependency Tree" to the > following URL: > http://maven.apache.org/plugins/maven-dependency-plugin/index.html > That URL unfortunately yields a Page Not Found error. The content can be seen > on > https://maven.apache.org/plugins-archives/maven-dependency-plugin-2.4/examples/resolving-conflicts-using-the-dependency-tree.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-765) Some goals result in download of Struts 1.3.8 POMs
[
https://issues.apache.org/jira/browse/MDEP-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778092#comment-17778092
]
Elliotte Rusty Harold commented on MDEP-765:
Do you have a repro project?
I don't think anything in Maven depends on struts. This seems unlikely to be an
issue with the plugin itself. More likely there's some issue in your project.
Can you explain why you think this is an issue in the dependency plugin?
> Some goals result in download of Struts 1.3.8 POMs
> --
>
> Key: MDEP-765
> URL: https://issues.apache.org/jira/browse/MDEP-765
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies, unpack-dependencies
>Affects Versions: 3.2.0
>Reporter: Andrew Swan
>Priority: Minor
> Labels: security, struts
>
> h1. Problem
> Executing certain goals of the {{dependency}} plugin (for example
> {{copy-dependencies}} and {{unpack-dependencies}}) causes various Struts
> 1.3.8 POMs to be downloaded to the user's local Maven repository. This
> version of Struts has known security vulnerabilities.
> h1. Reproduction
> Here's a minimal POM that demonstrates the problem:
> {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
> org.example
> dependency-plugin-demo
> 1.0-SNAPSHOT
>
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.2.0
>
>
>
>
> {code}
> Running {{mvn dependency:copy-dependencies}} results in the following output:
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< org.example:dependency-plugin-demo
> >-
> [INFO] Building dependency-plugin-demo 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.2.0:copy-dependencies (default-cli) @
> dependency-plugin-demo ---
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-core/1.3.8/struts-core-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-core/1.3.8/struts-core-1.3.8.pom
> (4.3 kB at 2.8 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-parent/1.3.8/struts-parent-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-parent/1.3.8/struts-parent-1.3.8.pom
> (9.8 kB at 21 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-master/4/struts-master-4.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-master/4/struts-master-4.pom
> (11 kB at 25 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-taglib/1.3.8/struts-taglib-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-taglib/1.3.8/struts-taglib-1.3.8.pom
> (3.1 kB at 6.4 kB/s)
> Downloading from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-tiles/1.3.8/struts-tiles-1.3.8.pom
> Downloaded from maven-atlassian-com:
> https://packages.atlassian.com/maven/repository/internal/org/apache/struts/struts-tiles/1.3.8/struts-tiles-1.3.8.pom
> (2.9 kB at 5.2 kB/s)
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 4.297 s
> [INFO] Finished at: 2021-09-09T14:18:10+10:00
> [INFO]
> {code}
> h1. Workaround
> One workaround is to downgrade to version 2.8 of the plugin, however this may
> also require the user to modify their plugin configuration, because the
> semantics of configuration options like {{includeScope}} have changed even
> between minor versions 3.1.2 and 3.2.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-770) Integration test can not be run in parallel
[
https://issues.apache.org/jira/browse/MDEP-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MDEP-770:
---
Issue Type: Test (was: Bug)
> Integration test can not be run in parallel
> ---
>
> Key: MDEP-770
> URL: https://issues.apache.org/jira/browse/MDEP-770
> Project: Maven Dependency Plugin
> Issue Type: Test
>Reporter: Slawomir Jaranowski
>Priority: Minor
>
> Those test:
> {code:java}
> src/it/projects/get-artifact
> src/it/projects/get-artifact-maven-plugin
> src/it/projects/get-artifact-no-transitive
> src/it/projects/get-gav
> src/it/projects/analyze-testDependencyWithNonTestScope{code}
> operate on the same tests artifacts.
> During test prepare artifacts are deleted from local repository and after
> test execute - assertion checks if artifact was downloaded ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-532) Undeclared test resources fail build despite 'ignoreNonCompile'
[
https://issues.apache.org/jira/browse/MDEP-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778091#comment-17778091
]
Elliotte Rusty Harold commented on MDEP-532:
Do you have a repro project?
> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---
>
> Key: MDEP-532
> URL: https://issues.apache.org/jira/browse/MDEP-532
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.10
> Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>Reporter: Alexander Kriegisch
>Priority: Minor
> Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.10
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
> *
>
>
>
>
> {code}
> Even though I want to ignore used undeclared test dependencies via
> {{true}}, my build fails like this in
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze)
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-695) Improve mvn dependency:tree - add option to generate mermaidjs flowchart diagram format
[
https://issues.apache.org/jira/browse/MDEP-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778090#comment-17778090
]
Elliotte Rusty Harold commented on MDEP-695:
Maybe if someone contributes a well-written patch with tests and docs that does
not impose a large maintenance burden going forward. Or if this seems to be a
common open format. I've never heard of it before, but I've never heard of a
lot fo good things.
> Improve mvn dependency:tree - add option to generate mermaidjs flowchart
> diagram format
> ---
>
> Key: MDEP-695
> URL: https://issues.apache.org/jira/browse/MDEP-695
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: tree
>Affects Versions: waiting-for-feedback
> Environment: all
>Reporter: Emanuel Ciuca
>Priority: Minor
> Labels: S2, features, up-for-grabs
> Attachments: demo.svg
>
>
> While trying to generate some diagrams for maven module dependencies I found
> mermaidjs flowchart diagrams to be most suitable for large graphs. (see
> [https://mermaid-js.github.io/mermaid/#/flowchart|https://mermaid-js.github.io/mermaid/#/flowchart)])
> Here is an example of a graph I generated for one of the projects I work on:
>
> {code:java}
> graph LR
> module-1 --> |compile| module-2
> module-3 --> |compile| module-4
> module-3 --> |test| module-5
> module-3 --> |compile,test| module-2
> module-3 --> |test| module-1{code}
>
> I would be helpful to be able to generate this diagram for a multi-module
> maven project
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-695) Improve mvn dependency:tree - add option to generate mermaidjs flowchart diagram format
[
https://issues.apache.org/jira/browse/MDEP-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MDEP-695:
---
Labels: S2 features up-for-grabs (was: S2 features)
> Improve mvn dependency:tree - add option to generate mermaidjs flowchart
> diagram format
> ---
>
> Key: MDEP-695
> URL: https://issues.apache.org/jira/browse/MDEP-695
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: tree
>Affects Versions: waiting-for-feedback
> Environment: all
>Reporter: Emanuel Ciuca
>Priority: Minor
> Labels: S2, features, up-for-grabs
> Attachments: demo.svg
>
>
> While trying to generate some diagrams for maven module dependencies I found
> mermaidjs flowchart diagrams to be most suitable for large graphs. (see
> [https://mermaid-js.github.io/mermaid/#/flowchart|https://mermaid-js.github.io/mermaid/#/flowchart)])
> Here is an example of a graph I generated for one of the projects I work on:
>
> {code:java}
> graph LR
> module-1 --> |compile| module-2
> module-3 --> |compile| module-4
> module-3 --> |test| module-5
> module-3 --> |compile,test| module-2
> module-3 --> |test| module-1{code}
>
> I would be helpful to be able to generate this diagram for a multi-module
> maven project
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-669) Optimize the documentation of of build-classpath-mojo
[ https://issues.apache.org/jira/browse/MDEP-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MDEP-669: --- Priority: Major (was: Trivial) > Optimize the documentation of of build-classpath-mojo > -- > > Key: MDEP-669 > URL: https://issues.apache.org/jira/browse/MDEP-669 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Reporter: Xinrong Meng >Priority: Major > Labels: up-for-grabs > > The documentation in > [https://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html#outputProperty] > is relatively confusing. > > `A property to set to the content of the classpath string.` would give users > illusions that they can use this parameter to modify the content of the > classpath string, rather than set the content of the classpath string to some > property. > > As far as I'm concerned, I wanted to embed classifier information in the > displayed classpath string, and I misunderstood this parameter until I > checked the source code of how it is defined. > > All in all, it would be great we could explicitly point it out that this > parameter sets the content of the classpath string to some property. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MDEP-878) Unexpected failure in mappers: no empty replacement or extension possible
[
https://issues.apache.org/jira/browse/MDEP-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MDEP-878.
Resolution: Invalid
I don't think this bug belongs to this project. perhaps to something in plexus?
If I'm wrong about that, please provide more details and it can be reopened or
moved to the right place.
> Unexpected failure in mappers: no empty replacement or extension possible
> --
>
> Key: MDEP-878
> URL: https://issues.apache.org/jira/browse/MDEP-878
> Project: Maven Dependency Plugin
> Issue Type: New Feature
>Reporter: Ernst Reissner
>Priority: Major
>
> I have the following configuration:
> {code:xml}
>
> eu.simuline.m2latex
> latex-maven-plugin
> ${versionLatexPlugin}
> jar
> true
> src/main/resources
> .latexmkrc.raw
>
>
> c.raw$
> c
>
>
>
> {code}
> As you can see, I tricked.
> i wanted just to replace `.raw` by the empty string.
> This was not possible and I think, an empty replacement is fully valid.
> Also I would have used the `FileExtensionMapper`, but also this does not
> accept an empty extension.
> Analogously I think, this should be allowed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MDEP-890) Make sense of sisu plexus
Elliotte Rusty Harold created MDEP-890: -- Summary: Make sense of sisu plexus Key: MDEP-890 URL: https://issues.apache.org/jira/browse/MDEP-890 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Elliotte Rusty Harold -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.maven:maven-core from 3.0 to 3.8.1 in /src/it/projects/analyze-ignore-used-undeclared-dependency [maven-dependency-plugin]
dependabot[bot] commented on PR #333: URL: https://github.com/apache/maven-dependency-plugin/pull/333#issuecomment-1773782215 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
Re: [PR] Bump org.apache.maven:maven-core from 3.0 to 3.8.1 in /src/it/projects/analyze-ignore-used-undeclared-dependency [maven-dependency-plugin]
elharo closed pull request #333: Bump org.apache.maven:maven-core from 3.0 to 3.8.1 in /src/it/projects/analyze-ignore-used-undeclared-dependency URL: https://github.com/apache/maven-dependency-plugin/pull/333 -- 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
Re: [PR] Bump org.apache.xmlgraphics:batik-bridge from 1.7 to 1.17 in /src/it/projects/tree-verbose [maven-dependency-plugin]
dependabot[bot] commented on PR #336: URL: https://github.com/apache/maven-dependency-plugin/pull/336#issuecomment-1773782035 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
Re: [PR] Bump org.apache.xmlgraphics:batik-bridge from 1.7 to 1.17 in /src/it/projects/tree-verbose [maven-dependency-plugin]
elharo closed pull request #336: Bump org.apache.xmlgraphics:batik-bridge from 1.7 to 1.17 in /src/it/projects/tree-verbose URL: https://github.com/apache/maven-dependency-plugin/pull/336 -- 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
Re: [PR] Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 in /src/it/projects/list-repositories [maven-dependency-plugin]
dependabot[bot] commented on PR #334: URL: https://github.com/apache/maven-dependency-plugin/pull/334#issuecomment-1773781930 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
Re: [PR] Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 in /src/it/projects/list-repositories [maven-dependency-plugin]
elharo closed pull request #334: Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 in /src/it/projects/list-repositories URL: https://github.com/apache/maven-dependency-plugin/pull/334 -- 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-889) javax.inject is undelcared but used
[ https://issues.apache.org/jira/browse/MDEP-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778086#comment-17778086 ] ASF GitHub Bot commented on MDEP-889: - elharo opened a new pull request, #343: URL: https://github.com/apache/maven-dependency-plugin/pull/343 (no comment) > javax.inject is undelcared but used > --- > > Key: MDEP-889 > URL: https://issues.apache.org/jira/browse/MDEP-889 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-889) javax.inject is undelcared but used
Elliotte Rusty Harold created MDEP-889: -- Summary: javax.inject is undelcared but used Key: MDEP-889 URL: https://issues.apache.org/jira/browse/MDEP-889 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Elliotte Rusty Harold Assignee: Elliotte Rusty Harold -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-869) commons-collections to 4.4
[ https://issues.apache.org/jira/browse/MDEP-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778084#comment-17778084 ] ASF GitHub Bot commented on MDEP-869: - elharo opened a new pull request, #342: URL: https://github.com/apache/maven-dependency-plugin/pull/342 (no comment) > commons-collections to 4.4 > -- > > Key: MDEP-869 > URL: https://issues.apache.org/jira/browse/MDEP-869 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > Fix For: 3.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [MDEP-869] remove unused collections dependency [maven-dependency-plugin]
elharo opened a new pull request, #342: URL: https://github.com/apache/maven-dependency-plugin/pull/342 (no comment) -- 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-888) Commons-lang 2.13.0
[ https://issues.apache.org/jira/browse/MDEP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778078#comment-17778078 ] ASF GitHub Bot commented on MDEP-888: - elharo opened a new pull request, #341: URL: https://github.com/apache/maven-dependency-plugin/pull/341 (no comment) > Commons-lang 2.13.0 > --- > > Key: MDEP-888 > URL: https://issues.apache.org/jira/browse/MDEP-888 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-888) Commons-lang 2.13.0
[ https://issues.apache.org/jira/browse/MDEP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MDEP-888: --- Summary: Commons-lang 2.13.0 (was: Commons'lang 2.13.0) > Commons-lang 2.13.0 > --- > > Key: MDEP-888 > URL: https://issues.apache.org/jira/browse/MDEP-888 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-888) Commons'lang 2.13.0
Elliotte Rusty Harold created MDEP-888: -- Summary: Commons'lang 2.13.0 Key: MDEP-888 URL: https://issues.apache.org/jira/browse/MDEP-888 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Elliotte Rusty Harold Assignee: Elliotte Rusty Harold -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MARTIFACT-52) add moduleinfo.skipModules property to skipModules parameter
[ https://issues.apache.org/jira/browse/MARTIFACT-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MARTIFACT-52. -- Resolution: Fixed > add moduleinfo.skipModules property to skipModules parameter > > > Key: MARTIFACT-52 > URL: https://issues.apache.org/jira/browse/MARTIFACT-52 > Project: Maven Artifact Plugin > Issue Type: Improvement > Components: artifact:buildinfo, artifact:compare >Affects Versions: 3.5.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Labels: pull-request-available > Fix For: 3.5.1 > > > forgot it when implementing MARTIFACT-50 > without property support, this parameter is not usable from CLI or with a > simple property -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MARTIFACT-52) add moduleinfo.skipModules property to skipModules parameter
[ https://issues.apache.org/jira/browse/MARTIFACT-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778071#comment-17778071 ] ASF GitHub Bot commented on MARTIFACT-52: - hboutemy merged PR #26: URL: https://github.com/apache/maven-artifact-plugin/pull/26 > add moduleinfo.skipModules property to skipModules parameter > > > Key: MARTIFACT-52 > URL: https://issues.apache.org/jira/browse/MARTIFACT-52 > Project: Maven Artifact Plugin > Issue Type: Improvement > Components: artifact:buildinfo, artifact:compare >Affects Versions: 3.5.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Labels: pull-request-available > Fix For: 3.5.1 > > > forgot it when implementing MARTIFACT-50 > without property support, this parameter is not usable from CLI or with a > simple property -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MARTIFACT-52] add moduleinfo.skipModules property [maven-artifact-plugin]
hboutemy merged PR #26: URL: https://github.com/apache/maven-artifact-plugin/pull/26 -- 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] [Created] (MDEP-887) Commons-IO to 2.14.0
Elliotte Rusty Harold created MDEP-887: -- Summary: Commons-IO to 2.14.0 Key: MDEP-887 URL: https://issues.apache.org/jira/browse/MDEP-887 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Elliotte Rusty Harold Assignee: Elliotte Rusty Harold -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] commons-io to 2.14.0 [maven-dependency-plugin]
elharo opened a new pull request, #340: URL: https://github.com/apache/maven-dependency-plugin/pull/340 (no comment) -- 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
Re: [PR] Bump resolverVersion from 1.0.0.v20140518 to 1.0.2.v20150114 [maven-dependency-plugin]
elharo merged PR #329: URL: https://github.com/apache/maven-dependency-plugin/pull/329 -- 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] (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:
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: properties
>Reporter: Kamalpreet
>Priority: Critical
> 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)
Re: [PR] Bump jettyVersion from 9.4.51.v20230217 to 9.4.53.v20231009 [maven-dependency-plugin]
elharo merged PR #338: URL: https://github.com/apache/maven-dependency-plugin/pull/338 -- 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
Re: [PR] Bump org.jsoup:jsoup from 1.16.1 to 1.16.2 [maven-dependency-plugin]
elharo merged PR #339: URL: https://github.com/apache/maven-dependency-plugin/pull/339 -- 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] (MCOMPILER-550) Make 'outputDirectory' writeable
[
https://issues.apache.org/jira/browse/MCOMPILER-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778055#comment-17778055
]
ASF GitHub Bot commented on MCOMPILER-550:
--
bmarwell opened a new pull request, #202:
URL: https://github.com/apache/maven-compiler-plugin/pull/202
- add more documentation when and how to use it (and when to not use it)
- fixes MCOMPILER-550
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/MCOMPILER-550) 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 `[MCOMPILER-550] - Fixes bug in
ApproximateQuantiles`,
where you replace `MCOMPILER-XXX` 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 integration tests successfully (`mvn -Prun-its clean
verify`).
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)
- [X] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> Make 'outputDirectory' writeable
>
>
> Key: MCOMPILER-550
> URL: https://issues.apache.org/jira/browse/MCOMPILER-550
> Project: Maven Compiler Plugin
> Issue Type: Improvement
>Reporter: Benjamin Marwell
>Assignee: Benjamin Marwell
>Priority: Major
>
> h2. Description of Improvement
> Currently, the property 'outputDirectory' is not writeable, i.e. not meant to
> be modified.
> However, making it writeable has at least two major advantages.
> h2. Use case one -- variable is already used
> Some Tutorials (e.g. https://www.baeldung.com/maven-multi-release-jars)
> already make use of rewriting the variable.
> h2. Use case two: MR-Jars with different bytecode level.
> Another use case is Multi-Release-Jars. Currently, they can officially only
> be controlled by setting the {{release}} property. That will not only require
> a suitable JDK or Toolchain-JDK, it will also require the bytecode for that
> version to be the bytecode of that version.
> E.g. using {{release}} and {{multiReleaseOutput}}, the bytecode in
> {{META-INF/version/java9}} MUST be exactly Java 9 bytecode.
> However, the JDK does not know of such restrictions.
> Using {{outputDirectory}}, you can now create Java 8 bytecode to run in e.g.
> Java 24. Here is an example use case:
> https://github.com/groovy/GMavenPlus/pull/287
> Granted, this could also be done differently, but this way it seems a little
> more elegant.
> The actual advantage is, that some developers can now plan ahead. For
> example, the SecurityManager is not just deprecated, it is deprecated for
> removal. The moment we know which Java version it is, we can create a MR-Jar
> for e.g. Java 30, even though Java 30 SDKs are not available then (currently
> we have Java 21 GA).
> h2. Proposed solution
> Make variable writeable as suggested in Slack.
> PR available locally.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MCOMPILER-550] make outputDirectory writeable [maven-compiler-plugin]
bmarwell opened a new pull request, #202: URL: https://github.com/apache/maven-compiler-plugin/pull/202 - add more documentation when and how to use it (and when to not use it) - fixes MCOMPILER-550 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/MCOMPILER-550) 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 `[MCOMPILER-550] - Fixes bug in ApproximateQuantiles`, where you replace `MCOMPILER-XXX` 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 integration tests successfully (`mvn -Prun-its clean verify`). 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) - [X] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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] [Created] (MCOMPILER-550) Make 'outputDirectory' writeable
Benjamin Marwell created MCOMPILER-550:
--
Summary: Make 'outputDirectory' writeable
Key: MCOMPILER-550
URL: https://issues.apache.org/jira/browse/MCOMPILER-550
Project: Maven Compiler Plugin
Issue Type: Improvement
Reporter: Benjamin Marwell
Assignee: Benjamin Marwell
h2. Description of Improvement
Currently, the property 'outputDirectory' is not writeable, i.e. not meant to
be modified.
However, making it writeable has at least two major advantages.
h2. Use case one -- variable is already used
Some Tutorials (e.g. https://www.baeldung.com/maven-multi-release-jars) already
make use of rewriting the variable.
h2. Use case two: MR-Jars with different bytecode level.
Another use case is Multi-Release-Jars. Currently, they can officially only be
controlled by setting the {{release}} property. That will not only require a
suitable JDK or Toolchain-JDK, it will also require the bytecode for that
version to be the bytecode of that version.
E.g. using {{release}} and {{multiReleaseOutput}}, the bytecode in
{{META-INF/version/java9}} MUST be exactly Java 9 bytecode.
However, the JDK does not know of such restrictions.
Using {{outputDirectory}}, you can now create Java 8 bytecode to run in e.g.
Java 24. Here is an example use case:
https://github.com/groovy/GMavenPlus/pull/287
Granted, this could also be done differently, but this way it seems a little
more elegant.
The actual advantage is, that some developers can now plan ahead. For example,
the SecurityManager is not just deprecated, it is deprecated for removal. The
moment we know which Java version it is, we can create a MR-Jar for e.g. Java
30, even though Java 30 SDKs are not available then (currently we have Java 21
GA).
h2. Proposed solution
Make variable writeable as suggested in Slack.
PR available locally.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MCHECKSTYLE-411) There should be info on skipped checkstyle check in maven build log
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778054#comment-17778054 ] Michael Osipov commented on MCHECKSTYLE-411: [~hboutemy], WDYT? > There should be info on skipped checkstyle check in maven build log > --- > > Key: MCHECKSTYLE-411 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-411 > Project: Maven Checkstyle Plugin > Issue Type: Improvement > Components: checkstyle:check >Affects Versions: 3.1.1 > Environment: Windows >Reporter: Marcin Slusarczyk >Priority: Minor > > EXPECTED BEHAVIOR: There should be info on skipped checkstyle check in maven > build log > ACTUAL BEHAVIOR: There is no info in maven log that the Checkstyle check was > skipped -- This message was sent by Atlassian Jira (v8.20.10#820010)
