Re: [PR] Use the latest version of Maven in build [maven-jenkins-lib]
slawekjaranowski commented on code in PR #9:
URL: https://github.com/apache/maven-jenkins-lib/pull/9#discussion_r1423483733
##
vars/asfMavenTlpPlgnBuild.groovy:
##
@@ -40,12 +40,12 @@ def call(Map params = [:]) {
// minimum, LTS, current and next ea
def jdks = params.containsKey('jdks') ? params.jdks :
params.containsKey('jdk') ? params.jdk : ['8','11','17']
def jdkMin = jdks[0];
-def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.8.x']
+def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.x.x']
Review Comment:
done
--
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] Use the latest version of Maven in build [maven-jenkins-lib]
slawekjaranowski commented on code in PR #9:
URL: https://github.com/apache/maven-jenkins-lib/pull/9#discussion_r1423476222
##
vars/asfMavenTlpPlgnBuild.groovy:
##
@@ -40,12 +40,12 @@ def call(Map params = [:]) {
// minimum, LTS, current and next ea
def jdks = params.containsKey('jdks') ? params.jdks :
params.containsKey('jdk') ? params.jdk : ['8','11','17']
def jdkMin = jdks[0];
-def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.8.x']
+def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.x.x']
Review Comment:
can be
##
vars/asfMavenTlpPlgnBuild.groovy:
##
@@ -40,12 +40,12 @@ def call(Map params = [:]) {
// minimum, LTS, current and next ea
def jdks = params.containsKey('jdks') ? params.jdks :
params.containsKey('jdk') ? params.jdk : ['8','11','17']
def jdkMin = jdks[0];
-def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.8.x']
+def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.x.x']
Review Comment:
can be
--
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] (MJAVADOC-783) Invalid path when using TagletArtifact and TagletPath
[
https://issues.apache.org/jira/browse/MJAVADOC-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795592#comment-17795592
]
Alexander Kriegisch commented on MJAVADOC-783:
--
[~elharo], no I won't call you a luddite.
[~elharo] and [~michael-o], I do not wish to start a general debate about the
pros and cons of HTML mail here, so please forgive me for my digression above.
Anyway, I cannot help but notice that, while the two of you agree, I gave
reasons for my statement, but the two of you simply stated something as if it
was a fact, which it is not. It is just an opinion, and both of you expressed
your respective opinions as what in German we call "killer phrases".
_"Even when the experts all agree, they may well be mistaken." -- Bertrand
Russell_
> Invalid path when using TagletArtifact and TagletPath
> -
>
> Key: MJAVADOC-783
> URL: https://issues.apache.org/jira/browse/MJAVADOC-783
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.6.3
>Reporter: Rob Gordon
>Priority: Major
>
> I’m trying to use the Javadoc plugin with both a tagletartifact and a
> tagletpath but I get an InvliadPathException from the Javadoc goal.
> I can see from the generated options file that there is no separator between
> the end of the artifact path and the taglet path.
> I think the problem is that getTagletPath method of AbstractJavadocMojo
> should check for an existing path before adding the tagletpath. Something
> like:
> {code:java}
> if (tagletpath != null && !tagletpath.isEmpty()) {
> if (path.length() > 0)
> { path.append(File.pathSeparator); }
> path.append(JavadocUtil.unifyPathSeparator(tagletpath));
> }
> {code}
> I looked at creating a pull request but I can’t work out how to create a
> suitable test. I found a taglet-test-plugin-config.xml, but not where it’s
> used.
> Could someone familiar with this codebase possibly take a look at this
> problem please?
> My configuration can be seen here:
> [https://github.com/robjg/oj-parent/blob/d3e2328ca285516f1a4f6ee2bce94b44ba89b748/pom.xml#L304]
> I attempted to report this problem via 'us...@maven.apache.org' however my
> mail did not make it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-775) Option 'tagletpath' not working, completely ignored
[
https://issues.apache.org/jira/browse/MJAVADOC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795591#comment-17795591
]
Alexander Kriegisch edited comment on MJAVADOC-775 at 12/12/23 5:06 AM:
[~elharo], are you sure it is is godd idea to close this one? My
{{ClassNotFoundException}} is not the same as the {{InvliadPathException}} in
the other issue. The descriptions also sound different. Just because there
happen to be two issues about tagle paths, it does not automatically mean that
they are identical.
I also do not understand what you are missing here. There is a link to a
real-world reproducer with exact instructions which commit to check out. A link
to previous conversation on a mailing list about this, where you can also find
an error description, also exists. Usually, developers ask for reproducers and
links to further details. Sometimes, when providing same, I feel like they have
not been read.
was (Author: kriegaex):
[~elharo], are you sure it is is godd idea to close this one? My
{{ClassNotFoundException}} is not the same as the {{InvliadPathException}} in
the other issue. The descriptions also sound different. Just because there
happen to be two issues about tagle paths, it does not automatically mean that
they are identical.
I also do not understand what you are missing here. There is a link to a
real-world reproducer with exact instructions which commit to check out. A link
to previous conversation on a mailing list about this, where you can also find
an error description, also exists.
> Option 'tagletpath' not working, completely ignored
> ---
>
> Key: MJAVADOC-775
> URL: https://issues.apache.org/jira/browse/MJAVADOC-775
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.6.0
>Reporter: Alexander Kriegisch
>Priority: Major
>
> The [{{tagletpath}}
> option|https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#tagletpath]
> seems to be completely ignored, despite being documented. It looks as if
> this never worked before. It is also utterly untested. There is an old bug
> MJAVADOC-231, but whatever that was meant to fix, it seems to be unrelated to
> this one. If I have a local JAR unavailable on Maven Central sitting in a
> libraries folder, I cannot use it in any other way than to contrive to put a
> copy into my local Maven repository and use {{tagletArtifact}} instead of
> {{tagletpath}}.
> I noticed this, when trying to help someone asking a question on the [Maven
> users mailing
> list|https://lists.apache.org/thread/zv25z3hx9gbmbt6wwhby6cy0t5lr542l]. In
> his [sample repository|https://github.com/jkesselm/xalan-java-mvn], an effort
> to convert the Xalan Ant Build to Maven, the commit to check out is is
> [6daf2890|https://github.com/jkesselm/xalan-java-mvn/tree/6daf2890bc03b13cd741b963d33897d61dcf4e5f].
> Just run {{mvn -DskipTests=true site}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-775) Option 'tagletpath' not working, completely ignored
[
https://issues.apache.org/jira/browse/MJAVADOC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795591#comment-17795591
]
Alexander Kriegisch commented on MJAVADOC-775:
--
[~elharo], are you sure it is is godd idea to close this one? My
{{ClassNotFoundException}} is not the same as the {{InvliadPathException}} in
the other issue. The descriptions also sound different. Just because there
happen to be two issues about tagle paths, it does not automatically mean that
they are identical.
I also do not understand what you are missing here. There is a link to a
real-world reproducer with exact instructions which commit to check out. A link
to previous conversation on a mailing list about this, where you can also find
an error description, also exists.
> Option 'tagletpath' not working, completely ignored
> ---
>
> Key: MJAVADOC-775
> URL: https://issues.apache.org/jira/browse/MJAVADOC-775
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.6.0
>Reporter: Alexander Kriegisch
>Priority: Major
>
> The [{{tagletpath}}
> option|https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#tagletpath]
> seems to be completely ignored, despite being documented. It looks as if
> this never worked before. It is also utterly untested. There is an old bug
> MJAVADOC-231, but whatever that was meant to fix, it seems to be unrelated to
> this one. If I have a local JAR unavailable on Maven Central sitting in a
> libraries folder, I cannot use it in any other way than to contrive to put a
> copy into my local Maven repository and use {{tagletArtifact}} instead of
> {{tagletpath}}.
> I noticed this, when trying to help someone asking a question on the [Maven
> users mailing
> list|https://lists.apache.org/thread/zv25z3hx9gbmbt6wwhby6cy0t5lr542l]. In
> his [sample repository|https://github.com/jkesselm/xalan-java-mvn], an effort
> to convert the Xalan Ant Build to Maven, the commit to check out is is
> [6daf2890|https://github.com/jkesselm/xalan-java-mvn/tree/6daf2890bc03b13cd741b963d33897d61dcf4e5f].
> Just run {{mvn -DskipTests=true site}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Prepare 4.0.0-alpha-9 [maven-site]
gnodet merged PR #474: URL: https://github.com/apache/maven-site/pull/474 -- 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] Use the latest version of Maven in build [maven-jenkins-lib]
olamy commented on code in PR #9:
URL: https://github.com/apache/maven-jenkins-lib/pull/9#discussion_r1423247005
##
vars/asfMavenTlpPlgnBuild.groovy:
##
@@ -40,12 +40,12 @@ def call(Map params = [:]) {
// minimum, LTS, current and next ea
def jdks = params.containsKey('jdks') ? params.jdks :
params.containsKey('jdk') ? params.jdk : ['8','11','17']
def jdkMin = jdks[0];
-def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.8.x']
+def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.x.x']
Review Comment:
the naming is really weird.. shouldn’t we have something such `3.9.x`?
##
vars/asfMavenTlpPlgnBuild.groovy:
##
@@ -40,12 +40,12 @@ def call(Map params = [:]) {
// minimum, LTS, current and next ea
def jdks = params.containsKey('jdks') ? params.jdks :
params.containsKey('jdk') ? params.jdk : ['8','11','17']
def jdkMin = jdks[0];
-def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.8.x']
+def mavens = params.containsKey('maven') ? params.maven : ['3.6.x',
'3.x.x']
Review Comment:
the naming is really weird.. shouldn’t we have something such `3.9.x`?
--
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
[PR] Bump net.sourceforge.plantuml:plantuml from 1.2023.12 to 1.2023.13 [maven-site]
dependabot[bot] opened a new pull request, #476: URL: https://github.com/apache/maven-site/pull/476 Bumps [net.sourceforge.plantuml:plantuml](https://github.com/plantuml/plantuml) from 1.2023.12 to 1.2023.13. Commits https://github.com/plantuml/plantuml/commit/5128891a0fe3473bf660a24f2077c5f6eab6d9e7;>5128891 chore: version 1.2023.13 https://github.com/plantuml/plantuml/commit/a87f84406465e29784342173ee1eb2733d135b81;>a87f844 fix: missing label in activity diagrams https://github.com/plantuml/plantuml/commit/a061b11305e8754a958fd8f59ed336de0c99f7b5;>a061b11 chore: formatting issue https://github.com/plantuml/plantuml/commit/428381ca44ed7f86cc9b46cf01328c224b3362c3;>428381c Merge branch 'tmp2' https://github.com/plantuml/plantuml/commit/c20b3d9642eb56600c6c22b09021b545b05f6174;>c20b3d9 feat: work on chronology https://github.com/plantuml/plantuml/commit/c20153a8416be07f56bb1f295a3f131dc6ace4e5;>c20153a Merge pull request https://redirect.github.com/plantuml/plantuml/issues/1624;>#1624 from The-Lum/PatchBranch https://github.com/plantuml/plantuml/commit/5c7245623a1c8cd700b7aaa30bbc44399a2307d3;>5c72456 test refactor: simplify test using TimTestUtils https://github.com/plantuml/plantuml/commit/3f836a44ccc507713b4cfcc87149e5853e02185a;>3f836a4 fix: allow (int corresponding of) unicode value for Chr builtin fct https://github.com/plantuml/plantuml/commit/1cb61d56099d3fddd5f0ea33812160fb939b576d;>1cb61d5 fix: allow different type inside array for GetJsonKey builtin fct https://github.com/plantuml/plantuml/commit/3a4c614fc1af53c3242d92de152171e76eb6b5d0;>3a4c614 Merge pull request https://redirect.github.com/plantuml/plantuml/issues/1617;>#1617 from plantuml/dependabot/github_actions/actions/setu... Additional commits viewable in https://github.com/plantuml/plantuml/compare/v1.2023.12...v1.2023.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] (MCOMPILER-564) Update plexus-compiler to 2.14.0
[ https://issues.apache.org/jira/browse/MCOMPILER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski reassigned MCOMPILER-564: - Assignee: Slawomir Jaranowski > Update plexus-compiler to 2.14.0 > > > Key: MCOMPILER-564 > URL: https://issues.apache.org/jira/browse/MCOMPILER-564 > Project: Maven Compiler Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.11.0 >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.12.0 > > > Once the plexus-compiler release is done to 2.14.0, it should be updated in > maven-compier-plugin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump plexusCompilerVersion from 2.13.0 to 2.14.0 [maven-compiler-plugin]
dependabot[bot] opened a new pull request, #215: URL: https://github.com/apache/maven-compiler-plugin/pull/215 Bumps `plexusCompilerVersion` from 2.13.0 to 2.14.0. Updates `org.codehaus.plexus:plexus-compiler-api` from 2.13.0 to 2.14.0 Release notes Sourced from https://github.com/codehaus-plexus/plexus-compiler/releases;>org.codehaus.plexus:plexus-compiler-api's releases. 2.14.0 ❗ Requirements for plexus compilers plexus-compiler-aspectj - JDK 17+, Maven 3.9.6 plexus-compiler-eclipse - JDK 17+, Maven 3.9.6 plexus-compiler-javac - JDK 8+ plexus-compiler-javac-errorprone - JDK 11+ Removed Drop J2ObjC compiler (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/325;>#325) https://github.com/slawekjaranowski;>@slawekjaranowski New features and improvements Update AspectJ Compiler to 1.9.21 to support Java 21 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/330;>#330) https://github.com/slachiewicz;>@slachiewicz Require JDK 17 for build (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/327;>#327) https://github.com/slawekjaranowski;>@slawekjaranowski Improve locking on JavacCompiler (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/315;>#315) https://github.com/gnodet;>@gnodet Include 'parameter' and 'preview' describe log (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/319;>#319) https://github.com/jorsol;>@jorsol Switch to SISU annotations and plugin, fixes https://redirect.github.com/codehaus-plexus/plexus-compiler/issues/217;>#217 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/313;>#313) https://github.com/gnodet;>@gnodet Support jdk 21 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/311;>#311) https://github.com/gnodet;>@gnodet Require Maven 3.5.4+ (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/283;>#283) https://github.com/slachiewicz;>@slachiewicz Require Java 11 for plexus-compiler-eclipse an javac-errorprone and aspectj compilers (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/279;>#279) https://github.com/slachiewicz;>@slachiewicz Add support to run its with Java 20 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/277;>#277) https://github.com/slachiewicz;>@slachiewicz Bug Fixes Fix javac memory leak (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/309;>#309) https://github.com/gnodet;>@gnodet Validate zip file names before extracting (Zip Slip) (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/291;>#291) https://github.com/slachiewicz;>@slachiewicz Dependency updates Update AspectJ Compiler to 1.9.21 to support Java 21 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/330;>#330) https://github.com/slachiewicz;>@slachiewicz Bump org.codehaus.plexus:plexus from 15 to 16 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/328;>#328) https://github.com/dependabot;>@dependabot Bump org.eclipse.jdt:ecj from 3.33.0 to 3.36.0 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/326;>#326) https://github.com/dependabot;>@dependabot Bump org.codehaus.plexus:plexus-testing from 1.1.0 to 1.2.0 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/317;>#317) https://github.com/dependabot;>@dependabot Bump org.junit:junit-bom from 5.10.0 to 5.10.1 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/320;>#320) https://github.com/dependabot;>@dependabot Bump org.apache.maven.plugins:maven-surefire-plugin from 3.2.1 to 3.2.2 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/321;>#321) https://github.com/dependabot;>@dependabot Upgrade parent and reformat using spotless (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/314;>#314) https://github.com/gnodet;>@gnodet Bump org.apache.maven.plugins:maven-surefire-plugin from 3.1.2 to 3.2.1 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/310;>#310) https://github.com/dependabot;>@dependabot Bump com.google.errorprone:error_prone_core from 2.22.0 to 2.23.0 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/308;>#308) https://github.com/dependabot;>@dependabot Bump com.google.errorprone:error_prone_core from 2.21.1 to 2.22.0 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/306;>#306) https://github.com/dependabot;>@dependabot Bump org.apache.maven.plugins:maven-enforcer-plugin from 3.4.0 to 3.4.1 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/304;>#304) https://github.com/dependabot;>@dependabot Bump maven-surefire-plugin from 3.1.0 to 3.1.2 (https://redirect.github.com/codehaus-plexus/plexus-compiler/pull/290;>#290) https://github.com/dependabot;>@dependabot Bump
[PR] Bump org.apache.commons:commons-text from 1.10.0 to 1.11.0 [maven-dependency-plugin]
dependabot[bot] opened a new pull request, #357: URL: https://github.com/apache/maven-dependency-plugin/pull/357 Bumps org.apache.commons:commons-text from 1.10.0 to 1.11.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[PR] Bump org.apache.maven.wagon:wagon-http-lightweight from 3.5.1 to 3.5.3 [maven-surefire]
dependabot[bot] opened a new pull request, #699: URL: https://github.com/apache/maven-surefire/pull/699 Bumps org.apache.maven.wagon:wagon-http-lightweight from 3.5.1 to 3.5.3. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[PR] Bump org.apache.maven.shared:maven-shared-utils from 3.3.4 to 3.4.2 [maven-surefire]
dependabot[bot] opened a new pull request, #698: URL: https://github.com/apache/maven-surefire/pull/698 Bumps [org.apache.maven.shared:maven-shared-utils](https://github.com/apache/maven-shared-utils) from 3.3.4 to 3.4.2. Release notes Sourced from https://github.com/apache/maven-shared-utils/releases;>org.apache.maven.shared:maven-shared-utils's releases. 3.4.2 Bug Fixes https://issues.apache.org/jira/browse/MSHARED-1072;>[MSHARED-1072] - Poll data from input stream (https://redirect.github.com/apache/maven-shared-utils/pull/140;>#140) https://github.com/slawekjaranowski;>@slawekjaranowski Maintenance https://issues.apache.org/jira/browse/MSHARED-1252;>[MSHARED-1252] - Bump plexus-io to 3.4.1 for maven-assembly-plugin (https://redirect.github.com/apache/maven-shared-utils/pull/141;>#141) https://github.com/slawekjaranowski;>@slawekjaranowski 3.4.1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922version=12353186;>Release Notes New features and improvements https://issues.apache.org/jira/browse/MNG-7729;>[MNG-7729] - deprecate questionable IsEmpty/IsNotEmpty methods (https://redirect.github.com/apache/maven-shared-utils/pull/136;>#136) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1014;>[MSHARED-1014] - Make Commandline.addSystemEnvironment public and deprecated (https://redirect.github.com/apache/maven-shared-utils/pull/138;>#138) https://github.com/slawekjaranowski;>@slawekjaranowski Deprecate newXmlWriter (https://redirect.github.com/apache/maven-shared-utils/pull/131;>#131) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1172;>[MSHARED-1172] - Deprecate redundant isEmptyString method (https://redirect.github.com/apache/maven-shared-utils/pull/123;>#123) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1169;>[MSHARED-1169] - deprecate join methods now available in Java 8 String class (https://redirect.github.com/apache/maven-shared-utils/pull/127;>#127) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1122;>[MSHARED-1122] - FileUtils: avoid getCanonicalPath() (https://redirect.github.com/apache/maven-shared-utils/pull/114;>#114) https://github.com/jukzi;>@jukzi https://issues.apache.org/jira/browse/MSHARED-1079;>[MSHARED-1079] - add build() method and document toString() method (https://redirect.github.com/apache/maven-shared-utils/pull/96;>#96) https://github.com/kwin;>@kwin https://issues.apache.org/jira/browse/MSHARED-1014;>[MSHARED-1014] - Optionally inherit system environment variables by Commandline (https://redirect.github.com/apache/maven-shared-utils/pull/94;>#94) https://github.com/slawekjaranowski;>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-983;>[MSHARED-983] - Drop plexus container default (https://redirect.github.com/apache/maven-shared-utils/pull/87;>#87) https://github.com/cstamas;>@cstamas Bug Fixes https://issues.apache.org/jira/browse/MSHARED-953;>[MSHARED-953] - don't trim (https://redirect.github.com/apache/maven-shared-utils/pull/124;>#124) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1072;>[MSHARED-1072] - fix blocking in StreamFeeder (https://redirect.github.com/apache/maven-shared-utils/pull/113;>#113) https://github.com/slawekjaranowski;>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1109;>[MSHARED-1109] - Ignore MessageUtilsTest methods on unsupported platforms (https://redirect.github.com/apache/maven-shared-utils/pull/106;>#106) https://github.com/kwin;>@kwin https://issues.apache.org/jira/browse/MSHARED-1107;>[MSHARED-1107] - Make copyFile succeed with source file having (https://redirect.github.com/apache/maven-shared-utils/pull/105;>#105) https://github.com/kwin;>@kwin https://issues.apache.org/jira/browse/MSHARED-985;>[MSHARED-985] - XmlWriterUtil platform independent and consistent (https://redirect.github.com/apache/maven-shared-utils/pull/91;>#91) https://github.com/elharo;>@elharo Dependency updates Bump maven-resources-plugin from 3.1.0 to 3.3.1 (https://redirect.github.com/apache/maven-shared-utils/pull/137;>#137) https://github.com/dependabot;>@dependabot https://issues.apache.org/jira/browse/MSHARED-1196;>[MSHARED-1196] - Bump maven-shared-components from 37 to 39 (https://redirect.github.com/apache/maven-shared-utils/pull/134;>#134) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1197;>[MSHARED-1197] - Bump plexus-utils from 3.5.0 to 3.5.1 (https://redirect.github.com/apache/maven-shared-utils/pull/132;>#132) https://github.com/dependabot;>@dependabot Bump apache/maven-gh-actions-shared from 2 to 3 (https://redirect.github.com/apache/maven-shared-utils/pull/130;>#130)
[jira] [Created] (MNG-7957) Expose checksum service on API
Tamas Cservenak created MNG-7957: Summary: Expose checksum service on API Key: MNG-7957 URL: https://issues.apache.org/jira/browse/MNG-7957 Project: Maven Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 4.0.x-candidate Resolver since 1.8 has extensible checksum SPI: [https://maven.apache.org/resolver/about-checksums.html] I think it would be worth to expose that not directly, but via some sort of Service in new Maven 4 API? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJARSIGNER-48) Make Jar Signer plugin :sign goal threadsafe
[
https://issues.apache.org/jira/browse/MJARSIGNER-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795442#comment-17795442
]
ASF GitHub Bot commented on MJARSIGNER-48:
--
lasselindqvist commented on PR #2:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/2#issuecomment-1850478955
Feel free to redo/rebase this. If no one else does it, I might do it next
week to celebrate the 5 year anniversary of this pull request.
> Make Jar Signer plugin :sign goal threadsafe
>
>
> Key: MJARSIGNER-48
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-48
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Kaloyan Raev
>Priority: Major
> Labels: build
> Fix For: 3.1.0
>
>
> Right now when you execute mvn *-T 4* maven-jarsigner-plugin:1.4:sign you get
> a warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in uDecideSM:
> [WARNING] org.apache.maven.plugins:maven-jarsigner-plugin:1.4
> [WARNING] *
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-48] Mark verify and sign Mojos thread safe [maven-jarsigner-plugin]
lasselindqvist commented on PR #2: URL: https://github.com/apache/maven-jarsigner-plugin/pull/2#issuecomment-1850478955 Feel free to redo/rebase this. If no one else does it, I might do it next week to celebrate the 5 year anniversary of this pull request. -- 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] (MINDEXER-209) Move off EOLd Jetty 9.x to 10.x
[ https://issues.apache.org/jira/browse/MINDEXER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-209. Resolution: Fixed > Move off EOLd Jetty 9.x to 10.x > --- > > Key: MINDEXER-209 > URL: https://issues.apache.org/jira/browse/MINDEXER-209 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.1 > > > Jetty 9.x is being used in UTs as "remote server", but it is EOLd. Move to > some newer and maintained version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-209) Move off EOLd Jetty 9.x to 10.x
[ https://issues.apache.org/jira/browse/MINDEXER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795437#comment-17795437 ] ASF GitHub Bot commented on MINDEXER-209: - cstamas merged PR #345: URL: https://github.com/apache/maven-indexer/pull/345 > Move off EOLd Jetty 9.x to 10.x > --- > > Key: MINDEXER-209 > URL: https://issues.apache.org/jira/browse/MINDEXER-209 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.1 > > > Jetty 9.x is being used in UTs as "remote server", but it is EOLd. Move to > some newer and maintained version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MINDEXER-209] Move off EOLd Jetty, update to 10.x [maven-indexer]
cstamas merged PR #345: URL: https://github.com/apache/maven-indexer/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] [Assigned] (MINDEXER-209) Move off EOLd Jetty 9.x to 10.x
[ https://issues.apache.org/jira/browse/MINDEXER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-209: Assignee: Tamas Cservenak > Move off EOLd Jetty 9.x to 10.x > --- > > Key: MINDEXER-209 > URL: https://issues.apache.org/jira/browse/MINDEXER-209 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.1 > > > Jetty 9.x is being used in UTs as "remote server", but it is EOLd. Move to > some newer and maintained version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-209) Move off EOLd Jetty 9.x to 10.x
[ https://issues.apache.org/jira/browse/MINDEXER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795434#comment-17795434 ] ASF GitHub Bot commented on MINDEXER-209: - cstamas opened a new pull request, #345: URL: https://github.com/apache/maven-indexer/pull/345 Jetty 9.x is EOLd, move to newer version is just bump. --- https://issues.apache.org/jira/browse/MINDEXER-209 > Move off EOLd Jetty 9.x to 10.x > --- > > Key: MINDEXER-209 > URL: https://issues.apache.org/jira/browse/MINDEXER-209 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 7.1.1 > > > Jetty 9.x is being used in UTs as "remote server", but it is EOLd. Move to > some newer and maintained version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINDEXER-209) Move off EOLd Jetty 9.x to 10.x
Tamas Cservenak created MINDEXER-209: Summary: Move off EOLd Jetty 9.x to 10.x Key: MINDEXER-209 URL: https://issues.apache.org/jira/browse/MINDEXER-209 Project: Maven Indexer Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 7.1.1 Jetty 9.x is being used in UTs as "remote server", but it is EOLd. Move to some newer and maintained version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Return Java 21 to CI matrix [maven-indexer]
cstamas merged PR #344: URL: https://github.com/apache/maven-indexer/pull/344 -- 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] (MRESOLVER-451) Expose version range processing strategies
Tamas Cservenak created MRESOLVER-451: - Summary: Expose version range processing strategies Key: MRESOLVER-451 URL: https://issues.apache.org/jira/browse/MRESOLVER-451 Project: Maven Resolver Issue Type: New Feature Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0 Look into exposing some of the range processing logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MINDEXER-208) Apache Lucene 9.9.0 and other minor dependency bumps
[ https://issues.apache.org/jira/browse/MINDEXER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-208: Assignee: Tamas Cservenak > Apache Lucene 9.9.0 and other minor dependency bumps > > > Key: MINDEXER-208 > URL: https://issues.apache.org/jira/browse/MINDEXER-208 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.1.1 > > > * lucene 9.8.0 to 9.9.0 changes: > [https://lucene.apache.org/core/9_9_0/changes/Changes.html] > * this also switches javac source/target to release > * didn't touch guice since it 7.0 changes namespace -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MINDEXER-208) Apache Lucene 9.9.0 and other minor dependency bumps
[ https://issues.apache.org/jira/browse/MINDEXER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-208. Resolution: Fixed > Apache Lucene 9.9.0 and other minor dependency bumps > > > Key: MINDEXER-208 > URL: https://issues.apache.org/jira/browse/MINDEXER-208 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Priority: Major > Fix For: 7.1.1 > > > * lucene 9.8.0 to 9.9.0 changes: > [https://lucene.apache.org/core/9_9_0/changes/Changes.html] > * this also switches javac source/target to release > * didn't touch guice since it 7.0 changes namespace -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Return Java 21 to CI matrix [maven-indexer]
cstamas opened a new pull request, #344: URL: https://github.com/apache/maven-indexer/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
Re: [PR] Bump org.codehaus.plexus:plexus-utils from 3.5.1 to 4.0.0 [maven-indexer]
dependabot[bot] closed pull request #343: Bump org.codehaus.plexus:plexus-utils from 3.5.1 to 4.0.0 URL: https://github.com/apache/maven-indexer/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] Bump maven.version from 3.9.5 to 3.9.6 [maven-indexer]
dependabot[bot] closed pull request #341: Bump maven.version from 3.9.5 to 3.9.6 URL: https://github.com/apache/maven-indexer/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
Re: [PR] Bump org.apache.maven:maven-parent from 40 to 41 [maven-indexer]
dependabot[bot] closed pull request #342: Bump org.apache.maven:maven-parent from 40 to 41 URL: https://github.com/apache/maven-indexer/pull/342 -- 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-parent from 40 to 41 [maven-indexer]
dependabot[bot] commented on PR #342: URL: https://github.com/apache/maven-indexer/pull/342#issuecomment-1850420131 Looks like org.apache.maven:maven-parent is up-to-date now, so this is no longer needed. -- 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.codehaus.plexus:plexus-utils from 3.5.1 to 4.0.0 [maven-indexer]
cstamas commented on PR #343: URL: https://github.com/apache/maven-indexer/pull/343#issuecomment-1850419934 @dependabot close -- 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 maven.version from 3.9.5 to 3.9.6 [maven-indexer]
dependabot[bot] commented on PR #341: URL: https://github.com/apache/maven-indexer/pull/341#issuecomment-1850419944 Looks like these dependencies are up-to-date now, so this is no longer needed. -- 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-cli:commons-cli from 1.5.0 to 1.6.0 [maven-indexer]
dependabot[bot] closed pull request #339: Bump commons-cli:commons-cli from 1.5.0 to 1.6.0 URL: https://github.com/apache/maven-indexer/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
Re: [PR] Bump commons-cli:commons-cli from 1.5.0 to 1.6.0 [maven-indexer]
dependabot[bot] commented on PR #339: URL: https://github.com/apache/maven-indexer/pull/339#issuecomment-1850419694 Looks like commons-cli:commons-cli is up-to-date now, so this is no longer needed. -- 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-parent from 40 to 41 [maven-indexer]
cstamas commented on PR #342: URL: https://github.com/apache/maven-indexer/pull/342#issuecomment-1850419598 @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-cli:commons-cli from 1.5.0 to 1.6.0 [maven-indexer]
cstamas commented on PR #339: URL: https://github.com/apache/maven-indexer/pull/339#issuecomment-1850419140 @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 maven.version from 3.9.5 to 3.9.6 [maven-indexer]
cstamas commented on PR #341: URL: https://github.com/apache/maven-indexer/pull/341#issuecomment-1850419376 @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 org.jsoup:jsoup from 1.16.2 to 1.17.1 [maven-indexer]
dependabot[bot] closed pull request #336: Bump org.jsoup:jsoup from 1.16.2 to 1.17.1 URL: https://github.com/apache/maven-indexer/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.jsoup:jsoup from 1.16.2 to 1.17.1 [maven-indexer]
dependabot[bot] commented on PR #336: URL: https://github.com/apache/maven-indexer/pull/336#issuecomment-1850419013 Looks like org.jsoup:jsoup is up-to-date now, so this is no longer needed. -- 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 lucene.version from 9.8.0 to 9.9.0 [maven-indexer]
dependabot[bot] commented on PR #338: URL: https://github.com/apache/maven-indexer/pull/338#issuecomment-1850419017 Looks like this PR is closed. If you re-open it, I'll rebase it, as long as no-one else has edited 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 resolver.version from 1.9.16 to 1.9.18 [maven-indexer]
dependabot[bot] closed pull request #340: Bump resolver.version from 1.9.16 to 1.9.18 URL: https://github.com/apache/maven-indexer/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: [PR] Bump resolver.version from 1.9.16 to 1.9.18 [maven-indexer]
dependabot[bot] commented on PR #340: URL: https://github.com/apache/maven-indexer/pull/340#issuecomment-1850418935 Looks like these dependencies are up-to-date now, so this is no longer needed. -- 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 lucene.version from 9.8.0 to 9.9.0 [maven-indexer]
cstamas commented on PR #338: URL: https://github.com/apache/maven-indexer/pull/338#issuecomment-1850418920 @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 lucene.version from 9.8.0 to 9.9.0 [maven-indexer]
dependabot[bot] closed pull request #338: Bump lucene.version from 9.8.0 to 9.9.0 URL: https://github.com/apache/maven-indexer/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 lucene.version from 9.8.0 to 9.9.0 [maven-indexer]
dependabot[bot] commented on PR #338: URL: https://github.com/apache/maven-indexer/pull/338#issuecomment-1850418848 Looks like these dependencies are up-to-date now, so this is no longer needed. -- 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.2 to 1.17.1 [maven-indexer]
cstamas commented on PR #336: URL: https://github.com/apache/maven-indexer/pull/336#issuecomment-1850418436 @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] Apache Lucene 9.9.0 and other minor dependency bumps [maven-indexer]
cstamas merged PR #337: URL: https://github.com/apache/maven-indexer/pull/337 -- 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] (MINDEXER-208) Apache Lucene 9.9.0 and other minor dependency bumps
Tamas Cservenak created MINDEXER-208: Summary: Apache Lucene 9.9.0 and other minor dependency bumps Key: MINDEXER-208 URL: https://issues.apache.org/jira/browse/MINDEXER-208 Project: Maven Indexer Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 7.1.1 * lucene 9.8.0 to 9.9.0 changes: [https://lucene.apache.org/core/9_9_0/changes/Changes.html] * this also switches javac source/target to release * didn't touch guice since it 7.0 changes namespace -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJARSIGNER-48) Make Jar Signer plugin :sign goal threadsafe
[
https://issues.apache.org/jira/browse/MJARSIGNER-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795400#comment-17795400
]
ASF GitHub Bot commented on MJARSIGNER-48:
--
elharo commented on PR #2:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/2#issuecomment-1850233077
Needs to be updated to current master
> Make Jar Signer plugin :sign goal threadsafe
>
>
> Key: MJARSIGNER-48
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-48
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 1.4
>Reporter: Kaloyan Raev
>Priority: Major
> Labels: build
> Fix For: 3.1.0
>
>
> Right now when you execute mvn *-T 4* maven-jarsigner-plugin:1.4:sign you get
> a warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in uDecideSM:
> [WARNING] org.apache.maven.plugins:maven-jarsigner-plugin:1.4
> [WARNING] *
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-48] Mark verify and sign Mojos thread safe [maven-jarsigner-plugin]
elharo commented on PR #2: URL: https://github.com/apache/maven-jarsigner-plugin/pull/2#issuecomment-1850233077 Needs to be updated to current master -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795390#comment-17795390
]
Tamas Cservenak commented on MNG-7771:
--
There are several of these:
[https://github.com/apache/maven/blob/master/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolutionException.java]
But we talk about resolver one:
[https://github.com/apache/maven-resolver/blob/master/maven-resolver-api/src/main/java/org/eclipse/aether/resolution/ArtifactResolutionException.java]
Yes, Resolver 2.0.0 makes possible now to create more meaningful (and precise)
messages, as this new method is added:
https://github.com/apache/maven-resolver/blob/master/maven-resolver-api/src/main/java/org/eclipse/aether/resolution/ArtifactResult.java#L141
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
>
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0, 4.0.0-alpha-10
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795385#comment-17795385
]
Michael Osipov commented on MNG-7771:
-
[~cstamas]
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
>
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0, 4.0.0-alpha-10
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7771:
Fix Version/s: 4.0.0
4.0.0-alpha-10
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
>
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0, 4.0.0-alpha-10
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7758) o.e.aether.resolution.ArtifactResolutionException incorrectly examined when multiple repositories are involved
[
https://issues.apache.org/jira/browse/MNG-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7758:
Fix Version/s: 4.0.0
4.0.0-alpha-10
> o.e.aether.resolution.ArtifactResolutionException incorrectly examined when
> multiple repositories are involved
> --
>
> Key: MNG-7758
> URL: https://issues.apache.org/jira/browse/MNG-7758
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, Performance
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-10
>
> Attachments: 1.png, 2.png, Exception hierarchy.png
>
>
> Consider you have three repos defined in your build (could be POM or
> settings), evaluated in following order:
> 1. repo A: serves custom artifacts with group id {{com.example}}, due to repo
> partitioning in Nexus rejects requests to all other group ids with 403
> 1. repo B: serves third party artifacts without any restriction from a Nexus
> repo
> 1. repo C: serves Central mirror, last one quried, no restrictions
> Note that order is important! Now add a non-existing dependency to your POM
> and receive the following behavior:
> {{ArtifactResolutionException}} will contain an {{ArtifactResult}} with three
> exceptions:
> - {{TransferException}} with nested {{AuthorizationException}},
> - {{ArtifactNotFoundException}},
> - {{ArtifactNotFoundException}}.
> {{ArtifactResolutionException#getCause()}} will be populated with the
> {{TransferException}} so will
> {{org.eclipse.aether.resolution.ArtifactResult.isMissing()}} take the first
> exception only into account. E.g., {{DefaultArtifactDescriptorReader}} will
> do {{if (e.getCause() instanceof ArtifactNotFoundException)}} which is
> deceiving.
> Here is a sample for a non-existing artifact:
> {noformat}
> [INFO] --- maven-site-plugin:4.0.0-M7-SNAPSHOT:site (default-site) @
> mskins-222 ---
> [INFO] Configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.2
> [WARNING] index report is declared twice in default reportSet
> [INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.2:
> index, summary, dependency-info, modules, team, scm, issue-management,
> mailing-lists, dependency-management, dependencies, dependency-convergence,
> ci-management, plugin-management, plugins, distribution-management
> [INFO] Rendering site for default locale
> Downloading from lda-public:
> https://deblndw011x.ad001.siemens.net/nexus/content/groups/lda-public/org/apache/apache/29/apache-29-site.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.214 s
> [INFO] Finished at: 2023-04-02T12:51:02+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:4.0.0-M7-SNAPSHOT:site
> (default-site) on project mskins-222: SiteToolException: The site descriptor
> cannot be resolved from the repository: Unable to locate site descriptor:
> Could not transfer artifact org.apache:apache:xml:site:29 from/to lda-public
> (https://deblndw011x.ad001.siemens.net/nexus/content/groups/lda-public/):
> authorization failed for
> https://deblndw011x.ad001.siemens.net/nexus/content/groups/lda-public/org/apache/apache/29/apache-29-site.xml,
> status: 403 Forbidden -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> for a dependency:
> {noformat}
> [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
>
> [ERROR] org.apache.maven.cli.MavenCli - Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:4.0.0-M7-SNAPSHOT:site
> (default-site) on project mskins-222: Failed to get report for
> org.apache.maven.plugins:maven-project-plugin: Plugin
> org.apache.maven.plugins:maven-project-plugin:3.4.2 or one of its
> dependencies could not be resolved: Failed to read artifact descriptor for
> org.apache.maven.plugins:maven-project-plugin:jar:3.4.2: Could not transfer
> artifact org.apache.maven.plugins:maven-project-plugin:pom:3.4.2 from/to
> lda-public
>
[jira] [Commented] (MNG-7758) o.e.aether.resolution.ArtifactResolutionException incorrectly examined when multiple repositories are involved
[
https://issues.apache.org/jira/browse/MNG-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795383#comment-17795383
]
Michael Osipov commented on MNG-7758:
-
[~cstamas]
> o.e.aether.resolution.ArtifactResolutionException incorrectly examined when
> multiple repositories are involved
> --
>
> Key: MNG-7758
> URL: https://issues.apache.org/jira/browse/MNG-7758
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, Performance
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-10
>
> Attachments: 1.png, 2.png, Exception hierarchy.png
>
>
> Consider you have three repos defined in your build (could be POM or
> settings), evaluated in following order:
> 1. repo A: serves custom artifacts with group id {{com.example}}, due to repo
> partitioning in Nexus rejects requests to all other group ids with 403
> 1. repo B: serves third party artifacts without any restriction from a Nexus
> repo
> 1. repo C: serves Central mirror, last one quried, no restrictions
> Note that order is important! Now add a non-existing dependency to your POM
> and receive the following behavior:
> {{ArtifactResolutionException}} will contain an {{ArtifactResult}} with three
> exceptions:
> - {{TransferException}} with nested {{AuthorizationException}},
> - {{ArtifactNotFoundException}},
> - {{ArtifactNotFoundException}}.
> {{ArtifactResolutionException#getCause()}} will be populated with the
> {{TransferException}} so will
> {{org.eclipse.aether.resolution.ArtifactResult.isMissing()}} take the first
> exception only into account. E.g., {{DefaultArtifactDescriptorReader}} will
> do {{if (e.getCause() instanceof ArtifactNotFoundException)}} which is
> deceiving.
> Here is a sample for a non-existing artifact:
> {noformat}
> [INFO] --- maven-site-plugin:4.0.0-M7-SNAPSHOT:site (default-site) @
> mskins-222 ---
> [INFO] Configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.2
> [WARNING] index report is declared twice in default reportSet
> [INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.2:
> index, summary, dependency-info, modules, team, scm, issue-management,
> mailing-lists, dependency-management, dependencies, dependency-convergence,
> ci-management, plugin-management, plugins, distribution-management
> [INFO] Rendering site for default locale
> Downloading from lda-public:
> https://deblndw011x.ad001.siemens.net/nexus/content/groups/lda-public/org/apache/apache/29/apache-29-site.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.214 s
> [INFO] Finished at: 2023-04-02T12:51:02+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:4.0.0-M7-SNAPSHOT:site
> (default-site) on project mskins-222: SiteToolException: The site descriptor
> cannot be resolved from the repository: Unable to locate site descriptor:
> Could not transfer artifact org.apache:apache:xml:site:29 from/to lda-public
> (https://deblndw011x.ad001.siemens.net/nexus/content/groups/lda-public/):
> authorization failed for
> https://deblndw011x.ad001.siemens.net/nexus/content/groups/lda-public/org/apache/apache/29/apache-29-site.xml,
> status: 403 Forbidden -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> for a dependency:
> {noformat}
> [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
>
> [ERROR] org.apache.maven.cli.MavenCli - Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:4.0.0-M7-SNAPSHOT:site
> (default-site) on project mskins-222: Failed to get report for
> org.apache.maven.plugins:maven-project-plugin: Plugin
> org.apache.maven.plugins:maven-project-plugin:3.4.2 or one of its
> dependencies could not be resolved: Failed to read artifact descriptor for
> org.apache.maven.plugins:maven-project-plugin:jar:3.4.2: Could not transfer
> artifact org.apache.maven.plugins:maven-project-plugin:pom:3.4.2 from/to
> lda-public
>
[jira] [Updated] (MNG-7770) Implement workaround for MNG-7758/MRESOLVER-335
[ https://issues.apache.org/jira/browse/MNG-7770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7770: Fix Version/s: 4.0.0-alpha-10 > Implement workaround for MNG-7758/MRESOLVER-335 > --- > > Key: MNG-7770 > URL: https://issues.apache.org/jira/browse/MNG-7770 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5 >Reporter: Michael Osipov >Priority: Major > Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0-alpha-10 > > > Details see tickets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7770) Implement workaround for MNG-7758/MRESOLVER-335
[ https://issues.apache.org/jira/browse/MNG-7770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795382#comment-17795382 ] Michael Osipov commented on MNG-7770: - [~cstamas] > Implement workaround for MNG-7758/MRESOLVER-335 > --- > > Key: MNG-7770 > URL: https://issues.apache.org/jira/browse/MNG-7770 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5 >Reporter: Michael Osipov >Priority: Major > Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0-alpha-10 > > > Details see tickets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-783) Invalid path when using TagletArtifact and TagletPath
[
https://issues.apache.org/jira/browse/MJAVADOC-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795378#comment-17795378
]
Michael Osipov commented on MJAVADOC-783:
-
I fully agree with [~elharo], HTML is the worst ever happened to email. We all
know who's fault is this.
> Invalid path when using TagletArtifact and TagletPath
> -
>
> Key: MJAVADOC-783
> URL: https://issues.apache.org/jira/browse/MJAVADOC-783
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.6.3
>Reporter: Rob Gordon
>Priority: Major
>
> I’m trying to use the Javadoc plugin with both a tagletartifact and a
> tagletpath but I get an InvliadPathException from the Javadoc goal.
> I can see from the generated options file that there is no separator between
> the end of the artifact path and the taglet path.
> I think the problem is that getTagletPath method of AbstractJavadocMojo
> should check for an existing path before adding the tagletpath. Something
> like:
> {code:java}
> if (tagletpath != null && !tagletpath.isEmpty()) {
> if (path.length() > 0)
> { path.append(File.pathSeparator); }
> path.append(JavadocUtil.unifyPathSeparator(tagletpath));
> }
> {code}
> I looked at creating a pull request but I can’t work out how to create a
> suitable test. I found a taglet-test-plugin-config.xml, but not where it’s
> used.
> Could someone familiar with this codebase possibly take a look at this
> problem please?
> My configuration can be seen here:
> [https://github.com/robjg/oj-parent/blob/d3e2328ca285516f1a4f6ee2bce94b44ba89b748/pom.xml#L304]
> I attempted to report this problem via 'us...@maven.apache.org' however my
> mail did not make it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Implement maxTries parameter [maven-jarsigner-plugin]
jcompagner commented on PR #1: URL: https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1850085171 as i said, for us multiply TSA is way more important then retries, it just need to roll over the TSA once Because last week Thursday, 1 or 2 projects builds where broken (that where using a ant sign script instead of mvn) and that ant sign script doesn't have that multiply tsa support and i had to change: http://timestamp.sectigo.com to http://sha256timestamp.ws.symantec.com/sha256/timestamp because starting in the night until the whole morning the sectigo one failed, so that was many ours.. -- 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] Implement maxTries parameter [maven-jarsigner-plugin]
schedin commented on PR #1: URL: https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1850075000 @jcompagner: You have a good point. Since this pull request is now closed (because most of the feature request was implemented in https://github.com/apache/maven-jarsigner-plugin/pull/13), do you think the existing ticket https://issues.apache.org/jira/projects/MJARSIGNER/issues/MJARSIGNER-74 (that links to the patch) is enough to track this? Since I did not have direct need for multiple TSA URLs I did not implement it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MJARSIGNER-75) maven-shared-utils to 3.4.2
[ https://issues.apache.org/jira/browse/MJARSIGNER-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MJARSIGNER-75: Fix Version/s: 3.1.0 > maven-shared-utils to 3.4.2 > --- > > Key: MJARSIGNER-75 > URL: https://issues.apache.org/jira/browse/MJARSIGNER-75 > Project: Maven Jar Signer Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJARSIGNER-75) maven-shared-utils to 3.4.2
Elliotte Rusty Harold created MJARSIGNER-75: --- Summary: maven-shared-utils to 3.4.2 Key: MJARSIGNER-75 URL: https://issues.apache.org/jira/browse/MJARSIGNER-75 Project: Maven Jar Signer Plugin Issue Type: Dependency upgrade Reporter: Elliotte Rusty Harold -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MJARSIGNER-59) increase reliability when contacting timestamp service over unreliable network
[
https://issues.apache.org/jira/browse/MJARSIGNER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MJARSIGNER-59.
-
Resolution: Duplicate
> increase reliability when contacting timestamp service over unreliable network
> --
>
> Key: MJARSIGNER-59
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-59
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Andrew Peter Marlow
>Priority: Major
> Attachments:
> 0001-Added-retries-upon-failure-and-support-multiple-TSA-.patch
>
>
> {color:#00}The signing plugin fails in the presence of an unreliable
> network. Could retries be added please? I am thinking of something like up to
> 3 retries,{color} sleeping for one second between.{color:#00}
>
>
>
> I have just started to use this plugin and this is a major issue. It makes
> my overnight builds fail more often than not. Prior to me making this change
> the project produced unsigned jars during the java build and later on via a
> python script added the signing. Once the {color}
> {color:#00}unreliable network issue was identified the python script was
> changed, adding retries (the network issue will most likely never be fixed).
> These retries in the python script fixed the issue. Now I am using the maven
> plugin the issue is back.{color}
>
> Some people might think that if this is happening in a wired corporate
> network then the network issue ought to be identified and resolved by the
> corporation. Well, maybe. But this issue could easily strike on networks that
> are inherently less reliable such as wifi and mobile. So I really think that
> the retries should be there to cater for that.
>
> {color:#00} {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MJARSIGNER-59) increase reliability when contacting timestamp service over unreliable network
[
https://issues.apache.org/jira/browse/MJARSIGNER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold closed MJARSIGNER-59.
---
fixed on duplicate issue
> increase reliability when contacting timestamp service over unreliable network
> --
>
> Key: MJARSIGNER-59
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-59
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Andrew Peter Marlow
>Priority: Major
> Attachments:
> 0001-Added-retries-upon-failure-and-support-multiple-TSA-.patch
>
>
> {color:#00}The signing plugin fails in the presence of an unreliable
> network. Could retries be added please? I am thinking of something like up to
> 3 retries,{color} sleeping for one second between.{color:#00}
>
>
>
> I have just started to use this plugin and this is a major issue. It makes
> my overnight builds fail more often than not. Prior to me making this change
> the project produced unsigned jars during the java build and later on via a
> python script added the signing. Once the {color}
> {color:#00}unreliable network issue was identified the python script was
> changed, adding retries (the network issue will most likely never be fixed).
> These retries in the python script fixed the issue. Now I am using the maven
> plugin the issue is back.{color}
>
> Some people might think that if this is happening in a wired corporate
> network then the network issue ought to be identified and resolved by the
> corporation. Well, maybe. But this issue could easily strike on networks that
> are inherently less reliable such as wifi and mobile. So I really think that
> the retries should be there to cater for that.
>
> {color:#00} {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Implement maxTries parameter [maven-jarsigner-plugin]
elharo closed pull request #1: Implement maxTries parameter URL: https://github.com/apache/maven-jarsigner-plugin/pull/1 -- 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] adds maxTries and retryDelay [maven-jarsigner-plugin]
elharo closed pull request #3: adds maxTries and retryDelay URL: https://github.com/apache/maven-jarsigner-plugin/pull/3 -- 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] (MJARSIGNER-62) additionalArguments should not have double quotes
[
https://issues.apache.org/jira/browse/MJARSIGNER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795362#comment-17795362
]
ASF GitHub Bot commented on MJARSIGNER-62:
--
elharo merged PR #17:
URL: https://github.com/apache/maven-jarsigner-plugin/pull/17
> additionalArguments should not have double quotes
> -
>
> Key: MJARSIGNER-62
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-62
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: Windows
>Reporter: Manfred Koch
>Priority: Major
>
> Adding additional arguments to the jarsigner with the arguments option will
> be double qouted in the command line. That causes errors and should be
> avoided.
>
> *Example:*
>
> {code:java}
> -certchain c:\chain.crt
> {code}
>
> Results in
> {noformat}
> c:\Jenkins\tools\hudson.model.JDK\jdk-1.8.0_144-windows-x64\jre\..\bin\jarsigner.exe
> -keystore NONE -storepass *** -storetype PKCS11 -providerClass
> sun.security.pkcs11.SunPKCS11 -providerArg C:\config.conf "-certchain
> c:\chain.crt" -tsa http://timestamp.digicert.com library.jar alias{noformat}
> That can't be executed. I check that manually on the system.
> But without double qoutes
> {noformat}
> c:\Jenkins\tools\hudson.model.JDK\jdk-1.8.0_144-windows-x64\jre\..\bin\jarsigner.exe
> -keystore NONE -storepass *** -storetype PKCS11 -providerClass
> sun.security.pkcs11.SunPKCS11 -providerArg C:\config.conf -certchain
> c:\chain.crt -tsa http://timestamp.digicert.com library.jar alias{noformat}
> it is possible to execute the command. I have checked the source code of the
> *AbstractJarsignerMojo.* All *additionalArguments* should not be double
> quoted.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-62] Enhanced documentation for usage of arguments [maven-jarsigner-plugin]
elharo merged PR #17: URL: https://github.com/apache/maven-jarsigner-plugin/pull/17 -- 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] Implement maxTries parameter [maven-jarsigner-plugin]
elharo commented on PR #1: URL: https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1850065065 superseded by https://github.com/apache/maven-jarsigner-plugin/pull/13 -- 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] adds maxTries and retryDelay [maven-jarsigner-plugin]
elharo commented on PR #3: URL: https://github.com/apache/maven-jarsigner-plugin/pull/3#issuecomment-1850064336 superseded by https://github.com/apache/maven-jarsigner-plugin/pull/13 -- 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] [MJARSIGNER-41] Retry and delay feature when signing [maven-jarsigner-plugin]
elharo merged PR #13: URL: https://github.com/apache/maven-jarsigner-plugin/pull/13 -- 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] [MJARSIGNER-41] Retry and delay feature when signing [maven-jarsigner-plugin]
elharo commented on code in PR #13:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/13#discussion_r1421831151
##
src/main/java/org/apache/maven/plugins/jarsigner/JarsignerSignMojo.java:
##
@@ -126,4 +155,62 @@ protected JarSignerRequest createRequest(File archive)
throws MojoExecutionExcep
request.setKeypass(decrypt(keypass));
return request;
}
+
+/**
+ * {@inheritDoc}
+ *
+ * Will retry signing up to maxTries times if it fails.
+ *
+ * @throws MojoExecutionException If all signing attempts fail.
+ */
+@Override
+protected void executeJarSigner(JarSigner jarSigner, JarSignerRequest
request)
+throws JavaToolException, MojoExecutionException {
+Commandline commandLine = null;
+int resultCode = 0;
+for (int attempt = 0; attempt < maxTries; attempt++) {
+JavaToolResult result = jarSigner.execute(request);
+resultCode = result.getExitCode();
+commandLine = result.getCommandline();
+if (resultCode == 0) {
+return;
+}
+if (attempt < maxTries - 1) { // If not last attempt
+waitStrategy.waitAfterFailure(attempt,
Duration.ofSeconds(maxRetryDelaySeconds));
+}
+}
+throw new MojoExecutionException(getMessage("failure",
getCommandlineInfo(commandLine), resultCode));
+}
+
+/** Set current WaitStrategy. Package private for testing. */
+void setWaitStrategy(WaitStrategy waitStrategy) {
+this.waitStrategy = waitStrategy;
+}
+
+/** Wait/sleep after a signing failure before the next re-try should
happen. */
+@FunctionalInterface
+interface WaitStrategy {
+/**
+ * Will be called after a signing failure, if a re-try is about to
happen. May as a side effect sleep current
+ * thread for some time.
+ * @param attempt the attempt number (0 is the first).
+ * @param maxRetryDelay The maximum duration to sleep (may be zero).
+ * @throws MojoExecutionException If the sleep was interrupted.
+ */
+void waitAfterFailure(int attempt, Duration maxRetryDelay) throws
MojoExecutionException;
+}
+
+private void defaultWaitStrategy(int attempt, Duration maxRetryDelay)
throws MojoExecutionException {
+long delayMillis = (long) (Duration.ofSeconds(1).toMillis() *
Math.pow(2, attempt));
Review Comment:
Maybe. Math.pow(2, attempt) still worries me. That can get very big very
fast. Perhaps set a maximum on attempts here. That is, don't go above a few
minutes. attempt <= 20. You can retry more, though I wouldn't wait more than a
few minutes between attempts, no matter how many times.
One or two retries might be OK. But if it fails three times, do we really
want to just keep trying?
--
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] [Resolved] (MJAVADOC-775) Option 'tagletpath' not working, completely ignored
[
https://issues.apache.org/jira/browse/MJAVADOC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MJAVADOC-775.
Resolution: Duplicate
Duping against 783 since that includes a little more info for a potential fix.
> Option 'tagletpath' not working, completely ignored
> ---
>
> Key: MJAVADOC-775
> URL: https://issues.apache.org/jira/browse/MJAVADOC-775
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.6.0
>Reporter: Alexander Kriegisch
>Priority: Major
>
> The [{{tagletpath}}
> option|https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#tagletpath]
> seems to be completely ignored, despite being documented. It looks as if
> this never worked before. It is also utterly untested. There is an old bug
> MJAVADOC-231, but whatever that was meant to fix, it seems to be unrelated to
> this one. If I have a local JAR unavailable on Maven Central sitting in a
> libraries folder, I cannot use it in any other way than to contrive to put a
> copy into my local Maven repository and use {{tagletArtifact}} instead of
> {{tagletpath}}.
> I noticed this, when trying to help someone asking a question on the [Maven
> users mailing
> list|https://lists.apache.org/thread/zv25z3hx9gbmbt6wwhby6cy0t5lr542l]. In
> his [sample repository|https://github.com/jkesselm/xalan-java-mvn], an effort
> to convert the Xalan Ant Build to Maven, the commit to check out is is
> [6daf2890|https://github.com/jkesselm/xalan-java-mvn/tree/6daf2890bc03b13cd741b963d33897d61dcf4e5f].
> Just run {{mvn -DskipTests=true site}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MJAVADOC-775) Option 'tagletpath' not working, completely ignored
[
https://issues.apache.org/jira/browse/MJAVADOC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold closed MJAVADOC-775.
--
> Option 'tagletpath' not working, completely ignored
> ---
>
> Key: MJAVADOC-775
> URL: https://issues.apache.org/jira/browse/MJAVADOC-775
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.6.0
>Reporter: Alexander Kriegisch
>Priority: Major
>
> The [{{tagletpath}}
> option|https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#tagletpath]
> seems to be completely ignored, despite being documented. It looks as if
> this never worked before. It is also utterly untested. There is an old bug
> MJAVADOC-231, but whatever that was meant to fix, it seems to be unrelated to
> this one. If I have a local JAR unavailable on Maven Central sitting in a
> libraries folder, I cannot use it in any other way than to contrive to put a
> copy into my local Maven repository and use {{tagletArtifact}} instead of
> {{tagletpath}}.
> I noticed this, when trying to help someone asking a question on the [Maven
> users mailing
> list|https://lists.apache.org/thread/zv25z3hx9gbmbt6wwhby6cy0t5lr542l]. In
> his [sample repository|https://github.com/jkesselm/xalan-java-mvn], an effort
> to convert the Xalan Ant Build to Maven, the commit to check out is is
> [6daf2890|https://github.com/jkesselm/xalan-java-mvn/tree/6daf2890bc03b13cd741b963d33897d61dcf4e5f].
> Just run {{mvn -DskipTests=true site}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (MJAVADOC-775) Option 'tagletpath' not working, completely ignored
[ https://issues.apache.org/jira/browse/MJAVADOC-775 ]
Elliotte Rusty Harold deleted comment on MJAVADOC-775:
was (Author: elharo):
Call me a luddite, but developers work in plain text for good reason, and that
should include email. We'd all be better off if HTML email had never been
invented.
> Option 'tagletpath' not working, completely ignored
> ---
>
> Key: MJAVADOC-775
> URL: https://issues.apache.org/jira/browse/MJAVADOC-775
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.6.0
>Reporter: Alexander Kriegisch
>Priority: Major
>
> The [{{tagletpath}}
> option|https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#tagletpath]
> seems to be completely ignored, despite being documented. It looks as if
> this never worked before. It is also utterly untested. There is an old bug
> MJAVADOC-231, but whatever that was meant to fix, it seems to be unrelated to
> this one. If I have a local JAR unavailable on Maven Central sitting in a
> libraries folder, I cannot use it in any other way than to contrive to put a
> copy into my local Maven repository and use {{tagletArtifact}} instead of
> {{tagletpath}}.
> I noticed this, when trying to help someone asking a question on the [Maven
> users mailing
> list|https://lists.apache.org/thread/zv25z3hx9gbmbt6wwhby6cy0t5lr542l]. In
> his [sample repository|https://github.com/jkesselm/xalan-java-mvn], an effort
> to convert the Xalan Ant Build to Maven, the commit to check out is is
> [6daf2890|https://github.com/jkesselm/xalan-java-mvn/tree/6daf2890bc03b13cd741b963d33897d61dcf4e5f].
> Just run {{mvn -DskipTests=true site}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-783) Invalid path when using TagletArtifact and TagletPath
[
https://issues.apache.org/jira/browse/MJAVADOC-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795347#comment-17795347
]
Elliotte Rusty Harold commented on MJAVADOC-783:
Call me a luddite, but developers work in plain text for good reason, and that
should include email. We'd all be better off if HTML email had never been
invented.
> Invalid path when using TagletArtifact and TagletPath
> -
>
> Key: MJAVADOC-783
> URL: https://issues.apache.org/jira/browse/MJAVADOC-783
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.6.3
>Reporter: Rob Gordon
>Priority: Major
>
> I’m trying to use the Javadoc plugin with both a tagletartifact and a
> tagletpath but I get an InvliadPathException from the Javadoc goal.
> I can see from the generated options file that there is no separator between
> the end of the artifact path and the taglet path.
> I think the problem is that getTagletPath method of AbstractJavadocMojo
> should check for an existing path before adding the tagletpath. Something
> like:
> {code:java}
> if (tagletpath != null && !tagletpath.isEmpty()) {
> if (path.length() > 0)
> { path.append(File.pathSeparator); }
> path.append(JavadocUtil.unifyPathSeparator(tagletpath));
> }
> {code}
> I looked at creating a pull request but I can’t work out how to create a
> suitable test. I found a taglet-test-plugin-config.xml, but not where it’s
> used.
> Could someone familiar with this codebase possibly take a look at this
> problem please?
> My configuration can be seen here:
> [https://github.com/robjg/oj-parent/blob/d3e2328ca285516f1a4f6ee2bce94b44ba89b748/pom.xml#L304]
> I attempted to report this problem via 'us...@maven.apache.org' however my
> mail did not make it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-775) Option 'tagletpath' not working, completely ignored
[
https://issues.apache.org/jira/browse/MJAVADOC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795346#comment-17795346
]
Elliotte Rusty Harold commented on MJAVADOC-775:
Call me a luddite, but developers work in plain text for good reason, and that
should include email. We'd all be better off if HTML email had never been
invented.
> Option 'tagletpath' not working, completely ignored
> ---
>
> Key: MJAVADOC-775
> URL: https://issues.apache.org/jira/browse/MJAVADOC-775
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.6.0
>Reporter: Alexander Kriegisch
>Priority: Major
>
> The [{{tagletpath}}
> option|https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#tagletpath]
> seems to be completely ignored, despite being documented. It looks as if
> this never worked before. It is also utterly untested. There is an old bug
> MJAVADOC-231, but whatever that was meant to fix, it seems to be unrelated to
> this one. If I have a local JAR unavailable on Maven Central sitting in a
> libraries folder, I cannot use it in any other way than to contrive to put a
> copy into my local Maven repository and use {{tagletArtifact}} instead of
> {{tagletpath}}.
> I noticed this, when trying to help someone asking a question on the [Maven
> users mailing
> list|https://lists.apache.org/thread/zv25z3hx9gbmbt6wwhby6cy0t5lr542l]. In
> his [sample repository|https://github.com/jkesselm/xalan-java-mvn], an effort
> to convert the Xalan Ant Build to Maven, the commit to check out is is
> [6daf2890|https://github.com/jkesselm/xalan-java-mvn/tree/6daf2890bc03b13cd741b963d33897d61dcf4e5f].
> Just run {{mvn -DskipTests=true site}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7944) Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2 out of bounds for length 2
[
https://issues.apache.org/jira/browse/MNG-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795313#comment-17795313
]
Filipe Roque commented on MNG-7944:
---
I created [https://github.com/froque/MNG-7944-reproducer] to reproduce this.
While attempting to debug this the following seems to be relevant:
{code:java}
[[FATAL] Non-parseable POM
/home/froque/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/3.0.0-M5/jaxb-parent-3.0.0-M5.pom:
Undeclared namespace prefix "Xlint" at [row,col {unknown-source}]: [436,45] @
/home/froque/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/3.0.0-M5/jaxb-parent-3.0.0-M5.pom,
line 436, column 45] {code}
> Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2
>
>
> Key: MNG-7944
> URL: https://issues.apache.org/jira/browse/MNG-7944
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-8
>Reporter: Filipe Roque
>Priority: Major
>
> It only affects apache-maven-4.0.0-alpha-8
> pom.xml
> {code:java}
>
> 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
> mvn4-assembly-index
> 1.0-SNAPSHOT
>
> 17
> 17
> UTF-8
>
>
>
> org.ehcache
> ehcache
> 3.10.8
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 3.6.0
>
>
>
> src/main/assembly/descriptor.xml
>
> false
>
>
>
> package
>
> single
>
>
>
>
>
>
> {code}
> descriptor.xml
> {code:java}
> http://maven.apache.org/ASSEMBLY/2.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0
> http://maven.apache.org/xsd/assembly-2.1.0.xsd;>
> assembly
>
> dir
>
> false
> .
>
>
> /
> false
> runtime
>
>
>
> {code}
> {code:java}
> ❯ /opt/maven/apache-maven-4.0.0-alpha-8/bin/mvn -q package
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (default) on
> project mvn4-assembly-index: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
> switch
> [ERROR] Re-run Maven using the '-X' switch to enable verbose output
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7956) Support resolver changes regarding resolution error
[ https://issues.apache.org/jira/browse/MNG-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795301#comment-17795301 ] Tamas Cservenak commented on MNG-7956: -- Sure, I just created this issue (and put into alpha-10) to not have this forgotten. Please put your issue into alpha-10 as well. > Support resolver changes regarding resolution error > --- > > Key: MNG-7956 > URL: https://issues.apache.org/jira/browse/MNG-7956 > Project: Maven > Issue Type: Task >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-10 > > > Implemented in MRESOLVER-335, needs changes in Maven. Currently > ArtifactResolutionException message (thrown by Resolver) is used directly to > be output to console. > Instead doing this, Maven should make use of exposed info to build more > meaningful (and less misleading) message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7956) Support resolver changes regarding resolution error
[ https://issues.apache.org/jira/browse/MNG-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795298#comment-17795298 ] Michael Osipov commented on MNG-7956: - There is an open issue from me, please try to put it into consideration, especially the use case I have described in there. I can test a potential change. > Support resolver changes regarding resolution error > --- > > Key: MNG-7956 > URL: https://issues.apache.org/jira/browse/MNG-7956 > Project: Maven > Issue Type: Task >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-10 > > > Implemented in MRESOLVER-335, needs changes in Maven. Currently > ArtifactResolutionException message (thrown by Resolver) is used directly to > be output to console. > Instead doing this, Maven should make use of exposed info to build more > meaningful (and less misleading) message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-335) Better resolver errors for Artifact Not Found
[
https://issues.apache.org/jira/browse/MRESOLVER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MRESOLVER-335.
-
Assignee: Tamas Cservenak
Resolution: Fixed
> Better resolver errors for Artifact Not Found
> -
>
> Key: MRESOLVER-335
> URL: https://issues.apache.org/jira/browse/MRESOLVER-335
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
>Reporter: Slawomir Jaranowski
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0
>
>
> When we have many remote repositories only first
> {{ArtifactNotFoundException}} is returned, all checks for other repositories
> are hidden.
> When we have errors for many artifacts in one request - list of problematic
> artifacts is present in message and only first exception for one artifact.
> Next case is with remote repository filtering, checks for remote repository
> according to filtering also produce {{ArtifactNotFoundException}}, this is
> done at the beginning so exception is first on list.
> In logs and exception we have:
> {code}
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.pom
> [WARNING] The POM for org.apache.commons:commons-lang3:jar:4.4.4 is missing,
> no dependency information available
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.jar
> [ERROR] Failed to execute goal on project maven-3.9: Could not resolve
> dependencies for project org.test:maven-3.9:jar:1.0.0-SNAPSHOT: Prefix org
> NOT allowed from mayrepo (https://artifactory.../artifactory/myrepo/,
> default, releases+snapshots)
> {code}
> As we see artefact was not found in {{my-mirror}}, but in error report we
> have information about not allowed prefixes - it can be confusing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7956) Support resolver changes regarding resolution error
[ https://issues.apache.org/jira/browse/MNG-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7956: - Description: Implemented in MRESOLVER-335, needs changes in Maven. Currently ArtifactResolutionException message (thrown by Resolver) is used directly to be output to console. Instead doing this, Maven should make use of exposed info to build more meaningful (and less misleading) message. was: Implemented in MRESOLVER-335, needs changes in Maven. Currently ArtifactResolutionException message (thrown by Resolver) is used directly to be output to console. Instead doing this, Maven should make use of exposed info to build meaningful message. > Support resolver changes regarding resolution error > --- > > Key: MNG-7956 > URL: https://issues.apache.org/jira/browse/MNG-7956 > Project: Maven > Issue Type: Task >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-10 > > > Implemented in MRESOLVER-335, needs changes in Maven. Currently > ArtifactResolutionException message (thrown by Resolver) is used directly to > be output to console. > Instead doing this, Maven should make use of exposed info to build more > meaningful (and less misleading) message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-308) HTTP transport showdown
[ https://issues.apache.org/jira/browse/MRESOLVER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795294#comment-17795294 ] ASF GitHub Bot commented on MRESOLVER-308: -- cstamas closed pull request #231: [MRESOLVER-308] HTTP transport showdown. URL: https://github.com/apache/maven-resolver/pull/231 > HTTP transport showdown > --- > > Key: MRESOLVER-308 > URL: https://issues.apache.org/jira/browse/MRESOLVER-308 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-alpha-2 > > > For HTTP protocol resolver currently provides following transports: > * transport-wagon that uses Maven 2.x Wagon, that among other protocols > supports HTTP/1.1 as well > * transport-http that uses directly Apache HttpClient 4.x supporting > HTTP/1.1 but provides enhancements in form of "checksum strategy" (almost all > of remote repositories emit those in headers, sparing one HTTP round-trip) > As we saw, is very easy to outperform these as: > * Maven Central supports HTTP/1.1 but also HTTP/2 > * HTTP/3 is on the way as well > An experiment involving Jetty Client far outperformed both of existing > transports, most probably due HTTP/2 support. > So, clients we should consider: > * Jetty Client > * OkHTTP > * Java 11 HttpClient > Point is, to invest into something that (ideally) transparently supports > HTTP/1.1 and HTTP/2, and more ideal would be if even HTTP/3 would be > transparently supported (Jetty 12 works on that). We could then simply > compare these implementations, count in pros and cons, and decide where we > want to go, -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-308) HTTP transport showdown
[ https://issues.apache.org/jira/browse/MRESOLVER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795295#comment-17795295 ] ASF GitHub Bot commented on MRESOLVER-308: -- cstamas commented on PR #231: URL: https://github.com/apache/maven-resolver/pull/231#issuecomment-1849874520 We are past this, so no reason to keep it anymore, closing it. > HTTP transport showdown > --- > > Key: MRESOLVER-308 > URL: https://issues.apache.org/jira/browse/MRESOLVER-308 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-alpha-2 > > > For HTTP protocol resolver currently provides following transports: > * transport-wagon that uses Maven 2.x Wagon, that among other protocols > supports HTTP/1.1 as well > * transport-http that uses directly Apache HttpClient 4.x supporting > HTTP/1.1 but provides enhancements in form of "checksum strategy" (almost all > of remote repositories emit those in headers, sparing one HTTP round-trip) > As we saw, is very easy to outperform these as: > * Maven Central supports HTTP/1.1 but also HTTP/2 > * HTTP/3 is on the way as well > An experiment involving Jetty Client far outperformed both of existing > transports, most probably due HTTP/2 support. > So, clients we should consider: > * Jetty Client > * OkHTTP > * Java 11 HttpClient > Point is, to invest into something that (ideally) transparently supports > HTTP/1.1 and HTTP/2, and more ideal would be if even HTTP/3 would be > transparently supported (Jetty 12 works on that). We could then simply > compare these implementations, count in pros and cons, and decide where we > want to go, -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRESOLVER-308] HTTP transport showdown. [maven-resolver]
cstamas commented on PR #231: URL: https://github.com/apache/maven-resolver/pull/231#issuecomment-1849874520 We are past this, so no reason to keep it anymore, closing 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] [MRESOLVER-308] HTTP transport showdown. [maven-resolver]
cstamas closed pull request #231: [MRESOLVER-308] HTTP transport showdown. URL: https://github.com/apache/maven-resolver/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
Re: [PR] Fix Maven 3.9.6 announce link in history page [maven-site]
cstamas merged PR #475: URL: https://github.com/apache/maven-site/pull/475 -- 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] (MRESOLVER-335) Better resolver errors for Artifact Not Found
[
https://issues.apache.org/jira/browse/MRESOLVER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795276#comment-17795276
]
ASF GitHub Bot commented on MRESOLVER-335:
--
cstamas merged PR #394:
URL: https://github.com/apache/maven-resolver/pull/394
> Better resolver errors for Artifact Not Found
> -
>
> Key: MRESOLVER-335
> URL: https://issues.apache.org/jira/browse/MRESOLVER-335
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 2.0.0
>
>
> When we have many remote repositories only first
> {{ArtifactNotFoundException}} is returned, all checks for other repositories
> are hidden.
> When we have errors for many artifacts in one request - list of problematic
> artifacts is present in message and only first exception for one artifact.
> Next case is with remote repository filtering, checks for remote repository
> according to filtering also produce {{ArtifactNotFoundException}}, this is
> done at the beginning so exception is first on list.
> In logs and exception we have:
> {code}
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.pom
> [WARNING] The POM for org.apache.commons:commons-lang3:jar:4.4.4 is missing,
> no dependency information available
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.jar
> [ERROR] Failed to execute goal on project maven-3.9: Could not resolve
> dependencies for project org.test:maven-3.9:jar:1.0.0-SNAPSHOT: Prefix org
> NOT allowed from mayrepo (https://artifactory.../artifactory/myrepo/,
> default, releases+snapshots)
> {code}
> As we see artefact was not found in {{my-mirror}}, but in error report we
> have information about not allowed prefixes - it can be confusing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MRESOLVER-335] Proposal for better errors (addendum) [maven-resolver]
cstamas merged PR #394: URL: https://github.com/apache/maven-resolver/pull/394 -- 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
[PR] [MRESOLVER-335] Proposal for better errors (addendum) [maven-resolver]
cstamas opened a new pull request, #394: URL: https://github.com/apache/maven-resolver/pull/394 Undo most of the changes to ArtifactResolutionException, as Maven Core depends on it's logic (is flawed for message, but is not to drive logic by checking cause). Previos main PR did expose all the needed things anyway, so basically it is now Maven turn to instead reusing the (flawed) message to emit it to end user/console, build some better message using new methods. --- https://issues.apache.org/jira/browse/MRESOLVER-335 -- 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] (MRESOLVER-335) Better resolver errors for Artifact Not Found
[
https://issues.apache.org/jira/browse/MRESOLVER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795274#comment-17795274
]
ASF GitHub Bot commented on MRESOLVER-335:
--
cstamas opened a new pull request, #394:
URL: https://github.com/apache/maven-resolver/pull/394
Undo most of the changes to ArtifactResolutionException, as Maven Core
depends on it's logic (is flawed for message, but is not to drive logic by
checking cause).
Previos main PR did expose all the needed things anyway, so basically it is
now Maven turn to instead reusing the (flawed) message to emit it to end
user/console, build some better message using new methods.
---
https://issues.apache.org/jira/browse/MRESOLVER-335
> Better resolver errors for Artifact Not Found
> -
>
> Key: MRESOLVER-335
> URL: https://issues.apache.org/jira/browse/MRESOLVER-335
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 2.0.0
>
>
> When we have many remote repositories only first
> {{ArtifactNotFoundException}} is returned, all checks for other repositories
> are hidden.
> When we have errors for many artifacts in one request - list of problematic
> artifacts is present in message and only first exception for one artifact.
> Next case is with remote repository filtering, checks for remote repository
> according to filtering also produce {{ArtifactNotFoundException}}, this is
> done at the beginning so exception is first on list.
> In logs and exception we have:
> {code}
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.pom
> [WARNING] The POM for org.apache.commons:commons-lang3:jar:4.4.4 is missing,
> no dependency information available
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.jar
> [ERROR] Failed to execute goal on project maven-3.9: Could not resolve
> dependencies for project org.test:maven-3.9:jar:1.0.0-SNAPSHOT: Prefix org
> NOT allowed from mayrepo (https://artifactory.../artifactory/myrepo/,
> default, releases+snapshots)
> {code}
> As we see artefact was not found in {{my-mirror}}, but in error report we
> have information about not allowed prefixes - it can be confusing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.apache.maven:maven-archiver from 3.6.0 to 3.6.1 [maven-ear-plugin]
dependabot[bot] opened a new pull request, #103: URL: https://github.com/apache/maven-ear-plugin/pull/103 Bumps [org.apache.maven:maven-archiver](https://github.com/apache/maven-archiver) from 3.6.0 to 3.6.1. Release notes Sourced from https://github.com/apache/maven-archiver/releases;>org.apache.maven:maven-archiver's releases. 3.6.1 What's Changed [MSHARED-1179] - Upgrade Parent to 39 by https://github.com/jorsol;>@jorsol in https://redirect.github.com/apache/maven-archiver/pull/27;>apache/maven-archiver#27 [MSHARED-1179] Back to 3.6.1-SNAPSHOT by https://github.com/elharo;>@elharo in https://redirect.github.com/apache/maven-archiver/pull/31;>apache/maven-archiver#31 Bump plexus-archiver from 1.0-alpha-7 to 3.6.0 in /src/test/resources by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/26;>apache/maven-archiver#26 Bump plexus-utils from 3.4.2 to 3.5.1 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/30;>apache/maven-archiver#30 Bump plexus-io from 3.4.0 to 3.4.1 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/28;>apache/maven-archiver#28 Bump junit-jupiter from 5.9.2 to 5.9.3 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/32;>apache/maven-archiver#32 [MNG-6829] Replace StringUtils#isEmpty(String) #isNotEmpty(String) by https://github.com/timtebeek;>@timtebeek in https://redirect.github.com/apache/maven-archiver/pull/34;>apache/maven-archiver#34 [MSHARED-1251] - Deprecate the JAR Index feature (JDK-8302819) by https://github.com/jorsol;>@jorsol in https://redirect.github.com/apache/maven-archiver/pull/33;>apache/maven-archiver#33 [MSHARED-1291] Bump org.junit:junit-bom from 5.9.3 to 5.10.0 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/37;>apache/maven-archiver#37 [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver from 4.4.0 to 4.8.0 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/39;>apache/maven-archiver#39 [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver from 3.6.0 to 4.8.0 in /src/test/resources by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/38;>apache/maven-archiver#38 [MSHARED-1294] Upgrade Parent to 40 by https://github.com/slawekjaranowski;>@slawekjaranowski in https://redirect.github.com/apache/maven-archiver/pull/40;>apache/maven-archiver#40 [MSHARED-1293] Refresh download page by https://github.com/slawekjaranowski;>@slawekjaranowski in https://redirect.github.com/apache/maven-archiver/pull/41;>apache/maven-archiver#41 [MSHARED-1297] Prefer JDK features over plexus-utils, plexus-io by https://github.com/slawekjaranowski;>@slawekjaranowski in https://redirect.github.com/apache/maven-archiver/pull/42;>apache/maven-archiver#42 New Contributors https://github.com/dependabot;>@dependabot made their first contribution in https://redirect.github.com/apache/maven-archiver/pull/26;>apache/maven-archiver#26 https://github.com/timtebeek;>@timtebeek made their first contribution in https://redirect.github.com/apache/maven-archiver/pull/34;>apache/maven-archiver#34 https://github.com/slawekjaranowski;>@slawekjaranowski made their first contribution in https://redirect.github.com/apache/maven-archiver/pull/40;>apache/maven-archiver#40 Full Changelog: https://github.com/apache/maven-archiver/compare/maven-archiver-3.6.0...maven-archiver-3.6.1;>https://github.com/apache/maven-archiver/compare/maven-archiver-3.6.0...maven-archiver-3.6.1 Commits https://github.com/apache/maven-archiver/commit/1602aa4d149d318f992433ca9f0a660ff55e95c5;>1602aa4 [maven-release-plugin] prepare release maven-archiver-3.6.1 https://github.com/apache/maven-archiver/commit/482ec069255bb49e7ccaa1c50eb9ea5ed38c6cb4;>482ec06 [MSHARED-1297] Prefer JDK features over plexus-utils, plexus-io https://github.com/apache/maven-archiver/commit/87edd76eab050c75ac3bb7619678b32a5503e2e8;>87edd76 [MSHARED-1293] Refresh download page https://github.com/apache/maven-archiver/commit/b459dae7964ddabff60e2d166fef9828ca745b5a;>b459dae [MSHARED-1294] Upgrade Parent to 40 https://github.com/apache/maven-archiver/commit/c8a2edb7387a22f3b92a1f9d1103e3e679bdcdf6;>c8a2edb [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver in /src/test/resource... https://github.com/apache/maven-archiver/commit/0fcec499b3d484f7e493972d60908fed9e4a800b;>0fcec49 [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver from 4.4.0 to 4.8.0 (... https://github.com/apache/maven-archiver/commit/6528ddb5c047d4e883b18f894d46f9ccc0f381e2;>6528ddb [MSHARED-1291] Bump org.junit:junit-bom from 5.9.3 to 5.10.0
Re: [PR] Implement maxTries parameter [maven-jarsigner-plugin]
jcompagner commented on PR #1: URL: https://github.com/apache/maven-jarsigner-plugin/pull/1#issuecomment-1849690136 that multi tsa is more important then just a retry, that is because if a tsa service is not working then it can be not working for quite some time (not minutes but more hours or half days) thats why we use now a patch version of the jarsigner: https://github.com/Servoy/maven-jarsigner-plugin/commit/bcb2b6a4be674f2c21acb2898747732dc93afc7d that does retries but first over all tsa urls that are given (comma separated list) so my jar signer property is something like: http://timestamp.sectigo.com,http://rfc3161timestamp.globalsign.com/advanced,http://timestamp.digicert.com and then with: 3 5 but those last 2 are not that important it could even have retry once, because if the first tsa fails then retrying it over the other 2 will almost all the time work fine -- 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] [MRESOLVER-335] Proposal for better errors [maven-resolver]
cstamas merged PR #386: URL: https://github.com/apache/maven-resolver/pull/386 -- 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] (MRESOLVER-335) Better resolver errors for Artifact Not Found
[
https://issues.apache.org/jira/browse/MRESOLVER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795259#comment-17795259
]
ASF GitHub Bot commented on MRESOLVER-335:
--
cstamas merged PR #386:
URL: https://github.com/apache/maven-resolver/pull/386
> Better resolver errors for Artifact Not Found
> -
>
> Key: MRESOLVER-335
> URL: https://issues.apache.org/jira/browse/MRESOLVER-335
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
>Reporter: Slawomir Jaranowski
>Priority: Major
> Fix For: 2.0.0
>
>
> When we have many remote repositories only first
> {{ArtifactNotFoundException}} is returned, all checks for other repositories
> are hidden.
> When we have errors for many artifacts in one request - list of problematic
> artifacts is present in message and only first exception for one artifact.
> Next case is with remote repository filtering, checks for remote repository
> according to filtering also produce {{ArtifactNotFoundException}}, this is
> done at the beginning so exception is first on list.
> In logs and exception we have:
> {code}
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.pom
> [WARNING] The POM for org.apache.commons:commons-lang3:jar:4.4.4 is missing,
> no dependency information available
> Downloading from my-mirror:
> https://artifactory.../artifactory/remote-repos/org/apache/commons/commons-lang3/4.4.4/commons-lang3-4.4.4.jar
> [ERROR] Failed to execute goal on project maven-3.9: Could not resolve
> dependencies for project org.test:maven-3.9:jar:1.0.0-SNAPSHOT: Prefix org
> NOT allowed from mayrepo (https://artifactory.../artifactory/myrepo/,
> default, releases+snapshots)
> {code}
> As we see artefact was not found in {{my-mirror}}, but in error report we
> have information about not allowed prefixes - it can be confusing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7956) Support resolver changes regarding resolution error
Tamas Cservenak created MNG-7956: Summary: Support resolver changes regarding resolution error Key: MNG-7956 URL: https://issues.apache.org/jira/browse/MNG-7956 Project: Maven Issue Type: Task Reporter: Tamas Cservenak Fix For: 4.0.0, 4.0.0-alpha-10 Implemented in MRESOLVER-335, needs changes in Maven. Currently ArtifactResolutionException message (thrown by Resolver) is used directly to be output to console. Instead doing this, Maven should make use of exposed info to build meaningful message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-450) Add a RepositoryCache#computeIfAbsent method
[ https://issues.apache.org/jira/browse/MRESOLVER-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-450. - Resolution: Fixed > Add a RepositoryCache#computeIfAbsent method > > > Key: MRESOLVER-450 > URL: https://issues.apache.org/jira/browse/MRESOLVER-450 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > Similar to MRESOLVER-204, improvement for RepositoryCache -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-450) Add a RepositoryCache#computeIfAbsent method
[ https://issues.apache.org/jira/browse/MRESOLVER-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795258#comment-17795258 ] ASF GitHub Bot commented on MRESOLVER-450: -- cstamas merged PR #392: URL: https://github.com/apache/maven-resolver/pull/392 > Add a RepositoryCache#computeIfAbsent method > > > Key: MRESOLVER-450 > URL: https://issues.apache.org/jira/browse/MRESOLVER-450 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > Similar to MRESOLVER-204, improvement for RepositoryCache -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRESOLVER-450] Enhance RepositoryCache [maven-resolver]
cstamas merged PR #392: URL: https://github.com/apache/maven-resolver/pull/392 -- 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
