Re: [I] Guide: Update plugins to Maven 4 [maven-site]
hboutemy commented on issue #751: URL: https://github.com/apache/maven-site/issues/751#issuecomment-2781269154 question: is it from a plugin user perspective? or from a plugin maintainer perspective? I'd personally rephrase: we need to clarify that Maven 4 has a compatibility layer for Maven 3 plugins: in general, Maven 3 plugin can run both in Maven 3 and Maven 4. I vaguely heard that there are edge cases: having a list of known plugins with issues would be useful = clarify the situation from a plugin user's perspective first then extend to plugin maintainer perspective: as a plugin maintainer, you should check that your Maven 3 plugin works as expected in Maven 4: if not, there are proabably fixes that can be done. then in the future, plugin maintainer will have choice to create a Maven 4 specific release of their plugin, that won't work in Maven 3 the tricky question being: maintain 2 branches in parallel? for how much time? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Link to "Guide to the Plugin Documentation Standard" more prominently? [maven-site]
hboutemy commented on issue #749: URL: https://github.com/apache/maven-site/issues/749#issuecomment-2781272829 nice finding :) it is not intentional: I overlooked that one when working on the left menu some years ago yes, please propose a PR updating at least the left menu, and adding more links as you find them useful: ping me if you need help to find your way in the site source -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Guide: Update plugins to Maven 4 [maven-site]
hboutemy commented on issue #751: URL: https://github.com/apache/maven-site/issues/751#issuecomment-2781273222 how do you see this issue vs #729 ? -- 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] Enlist missing ones. [maven-sources]
hboutemy commented on PR #10: URL: https://github.com/apache/maven-sources/pull/10#issuecomment-2781265809 still valid, but needs clarification: it's not about "projects" but branches this PR is a bout a few Maven core projects having Maven 3 vs Maven 4 branches = resolver and mvnd this also opens the question of every plugin for now, this PR is fine to me: clarifying how we want to handle plugins is a wider question that we need to clarify separately -- 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 Mimir from 0.4.0 to 0.4.1 [maven]
cstamas merged PR #2203: URL: https://github.com/apache/maven/pull/2203 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] [MDEPLOY-319] Cleanup of test code [maven-deploy-plugin]
jira-importer opened a new issue, #204: URL: https://github.com/apache/maven-deploy-plugin/issues/204 **[Slawomir Jaranowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slawekjaranowski)** opened **[MDEPLOY-319](https://issues.apache.org/jira/browse/MDEPLOY-319?redirect=false)** and commented --- **Remote Links:** - [GitHub Pull Request #58 ](https://github.com/apache/maven-deploy-plugin/pull/58) - [GitHub Pull Request #72 ](https://github.com/apache/maven-deploy-plugin/pull/72) - [GitHub Pull Request #73 ](https://github.com/apache/maven-deploy-plugin/pull/73) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven:maven-parent from 43 to 44 [maven-archetype]
cstamas commented on PR #258: URL: https://github.com/apache/maven-archetype/pull/258#issuecomment-2764643243 Automatic parent update is not possible, is not worth to approve this. At least site descriptor update is needed, but in this case also fixing UT classes as they have formatting violations (this was newly added in new parent). or just disable UT source code validation... -- 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] (SUREFIRE-1643) JUnit 5 in parallel execution mode confuses Surefire reports
[ https://issues.apache.org/jira/browse/SUREFIRE-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-1643. -- Resolution: Fixed > JUnit 5 in parallel execution mode confuses Surefire reports > > > Key: SUREFIRE-1643 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1643 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 5.x support >Affects Versions: 3.0.0-M3 >Reporter: Christian Stein >Assignee: Olivier Lamy >Priority: Major > Labels: triaged > Fix For: next-release > > > Hi I hope somebody here can help me out. I am observing something strange > while using JUNIT 5 parallel execution. I have two test classes TagTests, and > TagTypeTests. When I set the execution mode to CONCURRENT on both classes, > and run them, the test report shows the test cases on the wrong test class. > For example, the test case testA belongs to class TagTests, but it is shown > in the TagTypeTests test report. TagTests has 11 test cases, and TagType has > 13 test cases. But the test report shows there are 22 test cases in > TagTypeTests, and 2 in TagTests. Is this a known issue of parallelism? How to > get around the issue? > Sam Brannen @sbrannen Mar 01 18:00 > How is the test report generated? In an IDE? Using a build tool? > James Zhou @jazhou Mar 01 19:47 > @sbrannen I am using maven surefire plugin(ver 3.0.0-M3) to run the tests. > Here is the results: > [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.42 s > - in org.aaa.test.functional.tests.TagCrudTests > [INFO] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.148 > s - in org.aaa.test.functional.tests.TagTypeTests > [INFO] Results: > [INFO] > [INFO] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0 > @sbrannen there are actually 11 tests under TagCrudTests. Somehow only one > test is shown in the report generated by surefire plugin > Christian Stein @sormuras Mar 01 20:31 > @jazhou Do you have a minimal (failing) example project to share? > James Zhou @jazhou Mar 01 22:56 > @sormuras Sure. Here is the code: > https://github.com/jazhou/junit5-parallel-test -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump com.google.guava:guava from 33.3.0-jre to 33.4.0-jre [maven-indexer]
dependabot[bot] commented on PR #403: URL: https://github.com/apache/maven-indexer/pull/403#issuecomment-2739110347 Superseded by #414. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-202] deploy-file goal insists on deploying source file for previous deploy-file execution [maven-deploy-plugin]
jira-importer commented on issue #222: URL: https://github.com/apache/maven-deploy-plugin/issues/222#issuecomment-2771516376 **[Stephan Leicht Vogt](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=sleicht)** commented Great, it works! Thank you very much. BUILD SUCCESS: https://hudson.eclipse.org/scout/job/org.eclipse.scout.sdk.dependencies/27/ -- 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] Github issues WAR-plugin [maven-site]
Bukama opened a new pull request, #745: URL: https://github.com/apache/maven-site/pull/745 (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: [I] [MDEPLOY-45] Classifier not supported by deploy:deploy [maven-deploy-plugin]
jira-importer commented on issue #134: URL: https://github.com/apache/maven-deploy-plugin/issues/134#issuecomment-2771509409 **[Marat Radchenko](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slonopotamus)** commented A year has passed since this bug was reported. Any hope it will be fixed? -- 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] [MNG-8647] Set the default source directory to `src/${scope}/${lang}` as per documentation [maven]
gnodet commented on code in PR #2180:
URL: https://github.com/apache/maven/pull/2180#discussion_r2011829620
##
api/maven-api-core/src/main/java/org/apache/maven/api/SourceRoot.java:
##
@@ -26,13 +26,23 @@
/**
* A root directory of source files.
* The sources may be Java main classes, test classes, resources or anything
else identified by the scope.
+ *
+ * Default values
+ * The default implementation of all methods in this interface match the
default values
+ * documented in {@code maven.mdo} (the POM model).
Review Comment:
I don't think that's possible, the records cannot inherit from another
record.
--
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] [Comment Edited] (MNG-8638) Properties in repository id/url not supported anymore
[
https://issues.apache.org/jira/browse/MNG-8638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937306#comment-17937306
]
Marc Guillemot edited comment on MNG-8638 at 3/21/25 8:02 AM:
--
Central is naturally not involved here. Using {{settings.xml}} is probably a
way but it complicates the process a little bit.
Side note: is it really a feature to consider repositories declared in
referenced poms? I rather consider it as a bug that causes us tons of requests
to repositories that shoudn't be requested at all.
was (Author: mguille...@yahoo.fr):
Yes, we consume different repositories in nightly build mode versus "normal"
build mode. Using {{settings.xml}} is probably a way but it complicates the
process a little bit.
Side note: is it really a feature to consider repositories declared in
referenced poms? I rather consider it as a bug that causes us tons of requests
to repositories that shoudn't be requested at all.
> Properties in repository id/url not supported anymore
> -
>
> Key: MNG-8638
> URL: https://issues.apache.org/jira/browse/MNG-8638
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-rc-3
>Reporter: Marc Guillemot
>Priority: Major
>
> Following pom.xml can be used with Maven 3.9.x but not mit Maven 4.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> test
> properties-in-repos
> 0.0.1-SNAPSHOT
> pom
>
> snapshotsRepo
>
> https://my.server/snapshotsRepo
>
>
>
> useNightlySnapshot
>
>
> nightlySnapshotsRepo
>
> https://my.server/nightlySnapshotsRepo
>
>
>
>
>
> ${repo.snapshots.id}
> ${repo.snapshots.url}
>
> false
>
>
>
>
> {code}
> Maven 4.0.0-rc-3 fails with following error:
> {code:java}
> [ERROR] Some problems were encountered while processing the POMs
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project test:properties-in-repos:pom:0.0.1-SNAPSHOT
> (C:\dev\eclipse-workspace-okular-bis\poc-dynamic-mvn-deploy\pom.xml) has 1
> error
> [ERROR] 'repositories.repository.[${repo.snapshots.id}].url' contains an
> unsupported expression (only expressions starting with 'project.basedir' or
> 'project.rootDirectory' are supported). @
> test:properties-in-repos:0.0.1-SNAPSHOT,
> file://[sic]/poc-dynamic-mvn-deploy/pom.xml, line 26, column 13
> {code}
> This would block our migration to Maven 4 as we use such a construct to
> deploy snapshots from nightly builds to a separate repository.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-62] deploy on remote repository with linux [maven-deploy-plugin]
jira-importer commented on issue #233: URL: https://github.com/apache/maven-deploy-plugin/issues/233#issuecomment-2771517288 **[Jörg Hohwiller](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jo...@j-hohwiller.de)** commented > public key with scp works with any configuration > does NOT work for me either. I am using maven-deploy-plugin version 2.3 and have a DSA key (.ssh/id_dsa). > The key is perfectly accepted via openssh. However via maven the key is ignored and password is prompted. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-90] Deploy should be allowed in offline mode when the repo is a file: [maven-deploy-plugin]
jira-importer commented on issue #144: URL: https://github.com/apache/maven-deploy-plugin/issues/144#issuecomment-2771510187 **[Alon Bar-Lev](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alon.bar...@gmail.com)** commented Hello, the deploy plugin is a useful way to pack all project artifacts into maven repository structure. It is required for example when you package an application for package manager, so you need the artifacts as maven repository locally so it can be packaged. I see no sense in limiting deploy plugin in case of repository is at file:// protocol, as file:// is not offline. Please support this, or allow another mechanism to create locally maven repository of project artifacts. Methods I tried: create repository using assembly - but binaries cannot be digested, create repository using dependency plugin - but I need to explicitly build the project in unique structure and explicitly specify dependencies. The deploy plugin is the right way to do this, it is just the offline limitation inhibit the use of it. Please push this forward, as far as code is concerned it is trivial. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-74] Add an option to be able to abort if an artifact is already present in the deployment repository [maven-deploy-plugin]
jira-importer commented on issue #141: URL: https://github.com/apache/maven-deploy-plugin/issues/141#issuecomment-2771509958 **[Baptiste MATHUS](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mathu...@mipih.fr)** commented > +1 for regular releases, -1 for snapshots > Well, this is only a problem with -DuniqueVersion=false I guess. > Since default behaviour will generate a timestamp suffix, so that wouldn't override existing artifact. But IMO, this isn't a real problem since SNAPSHOT are unstable by definition, so maybe overriding it should be monitored at all. Maybe an additional option for the additional option could be added to handle this, like -DalsoForSnapshots :-). -- 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] (MNG-8624) Fix dependency not being set correctly for unsupported types
[ https://issues.apache.org/jira/browse/MNG-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8624. Resolution: Fixed > Fix dependency not being set correctly for unsupported types > > > Key: MNG-8624 > URL: https://issues.apache.org/jira/browse/MNG-8624 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-rc-3 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-rc-4 > > > GitHub Pull Request: https://github.com/apache/maven/pull/2153 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump resolverVersion from 1.9.20 to 2.0.7 [maven-plugin-tools]
dependabot[bot] commented on PR #375: URL: https://github.com/apache/maven-plugin-tools/pull/375#issuecomment-2745026456 OK, I won't notify you about version 2.x.x again, unless you re-open this PR. -- 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] (MNG-8663) Bump asmVersion from 9.7.1 to 9.8
[ https://issues.apache.org/jira/browse/MNG-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned MNG-8663: Assignee: Guillaume Nodet > Bump asmVersion from 9.7.1 to 9.8 > - > > Key: MNG-8663 > URL: https://issues.apache.org/jira/browse/MNG-8663 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-rc-4 > > > GitHub Pull Request: https://github.com/apache/maven/pull/2204 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [I] [MDEPLOY-63] Allow disabling deployment for artifacts that should not be deployed [maven-deploy-plugin]
jira-importer commented on issue #267: URL: https://github.com/apache/maven-deploy-plugin/issues/267#issuecomment-2771520306 **[Olivier Lamy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=olamy)** commented fixed in rev 630347. -- 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] [MNG-5102] Add support for POM mixins [maven]
jimisola commented on code in PR #1209: URL: https://github.com/apache/maven/pull/1209#discussion_r2004164811 ## its/core-it-suite/src/test/resources/mng-5102-mixins/gav/project/pom.xml: ## @@ -0,0 +1,60 @@ + + +http://maven.apache.org/POM/4.1.0"; root="true"> + org.apache.maven.its.mng5102 + gav + 0.1 + pom + + Maven Integration Test :: MNG-5102 + Mixins tests. + + + + +org.apache.maven.its.plugins +maven-it-plugin-expression +2.1-SNAPSHOT + + + + eval + +validate + + target/model.properties + +project/properties + + + + + + + + + + + org.apache.maven.its.mng5102 + mixin-2 Review Comment: @talios Our organization use your Maven Tiles (thank you!). Trying to think if there is something in Maven Tiles that this current implementation of Maven Mixins does not support. With Maven Tiles we have issues with profiles (the are active but Maven does not alwats acknowledge them) and properties (properties aren't propagated). From what Guillaume wrote it seems as if mixins, currently not having any restrictions, might function even better that Maven Tiles. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-70] remove copy of plexus-utils' XML encoding support sources [maven-deploy-plugin]
jira-importer commented on issue #140: URL: https://github.com/apache/maven-deploy-plugin/issues/140#issuecomment-2771509881 **[Herve Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented I understand your arguments. IMHO, users who did not migrate are precisely those who won't be able to lock the plugin version: they'll say that "Maven doesn't work", and we'll have to convince them that not specifying plugin version was a bad habit... On the other hand, having these XML encoding support classes copied in 4 components is not so hard for me to maintain: 1 line change in 6 months. And I don't think there will be more change in next months. MSITE-242 has more sources copied (cli, interpolation and introspection): perhaps these classes are more like a problem. Really, now that the compromise is tracked in these 4 Jira issues to be sure it's not forgotten, I think we don't need to hurry: time is our friend. Personally, I don't think changing prerequisite is a good idea before next release of install, deploy and release plugins since last releases are a bit old. For each plugin, when the next release is out, perhaps it will be the good time to look at this issue. -- 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] Improve release-drafter configuration [maven-jar-plugin]
slawekjaranowski merged PR #127: URL: https://github.com/apache/maven-jar-plugin/pull/127 -- 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-io:commons-io from 2.13.0 to 2.17.0 [maven-war-plugin]
slachiewicz commented on PR #76: URL: https://github.com/apache/maven-war-plugin/pull/76#issuecomment-2780368854 @dependabot recreate -- 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-8649) Maven 4 migration tool
[
https://issues.apache.org/jira/browse/MNG-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941208#comment-17941208
]
Matthias Bünger commented on MNG-8649:
--
{quote}
Fix POMs (not necessarily migrate to 4.1.0 model, but fix any deprecated
construct)
{quote}
Just as a note what could be on that if possible
* replace decrecate / no longer existing properties
> Maven 4 migration tool
> --
>
> Key: MNG-8649
> URL: https://issues.apache.org/jira/browse/MNG-8649
> Project: Maven
> Issue Type: Task
>Reporter: Guillaume Nodet
>Priority: Critical
>
> We should be able to help our users to migrate to Maven 4.
> This can be done in several steps:
> * fix POMs (not necessarily migrate to 4.1.0 model, but fix any deprecated
> construct)
> * update to more recent versions of plugins (some are known to have problems
> with Maven 4)
> * if the project is a plugin, we can try applying the draft
> https://gist.github.com/gnodet/c297ccae07dd2ee67dfa98cf1ef128f9
> This may be implemented as a plugin or as a tool in the mvnsh script somehow.
> A lot of failures for the first point can be found at
> https://github.com/gnodet/maven4-testing/issues/2812.
> It would be nice to alter the workflow above so that, in case of failure, the
> migration tool is run and another attempt is done.
> Ideally, the workflow would raise an issue on the project to track progress
> in case the initial build fails (it may be difficult to track the link so
> that we don't create a new issue each time we run the workflow).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump commons-io:commons-io from 2.13.0 to 2.18.0 [maven-war-plugin]
slachiewicz merged PR #76: URL: https://github.com/apache/maven-war-plugin/pull/76 -- 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.plugins:maven-plugins from 41 to 43 [maven-war-plugin]
slachiewicz commented on PR #73: URL: https://github.com/apache/maven-war-plugin/pull/73#issuecomment-2780378634 @dependabot recreate -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-202] deploy-file goal insists on deploying source file for previous deploy-file execution [maven-deploy-plugin]
jira-importer commented on issue #222:
URL:
https://github.com/apache/maven-deploy-plugin/issues/222#issuecomment-2771516379
**[Matthias
Hanisch](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=matze)**
commented
Sorry to jump in late.
We got also hit by the issue above and I gave it a quick try to check if our
scenario is really solved with the upcoming 3.0.0 of deploy plugin.
I created a very simple jar project with a hello world class and a
accompanying bill of materials which should be additionally uploaded using
deploy-file goal.
The pom attaches sources and javadoc jar, executes "default-deploy" to
upload the "hello world" jar and also executes a deploy-file to upload the
corresponding bom.
The "deploy-bom" still uploads sources and javadoc jar again, even with
3.0.0-SNAPSHOT.
Let me just attach the relevant plugin configurations. If more information
is required or if I should create a new issue just let me know.
```xml
maven-javadoc-plugin
2.10.4
attach-javadocs
jar
maven-source-plugin
3.0.0
attach-sources
jar
maven-deploy-plugin
3.0.0-SNAPSHOT
${project.distributionManagementArtifactRepository.url}
${project.distributionManagementArtifactRepository.id}
deploy-bom
deploy
deploy-file
${project.basedir}/bom/pom.xml
${project.basedir}/bom/pom.xml
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [I] [MDEPLOY-90] Deploy should be allowed in offline mode when the repo is a file: [maven-deploy-plugin]
jira-importer commented on issue #144: URL: https://github.com/apache/maven-deploy-plugin/issues/144#issuecomment-2771510192 **[Alon Bar-Lev](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alon.bar...@gmail.com)** commented Patch to deploy plugin, but it is uselss per previous 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: [I] [MDEPLOY-45] Classifier not supported by deploy:deploy [maven-deploy-plugin]
jira-importer commented on issue #134: URL: https://github.com/apache/maven-deploy-plugin/issues/134#issuecomment-2771509447 **[James MacDonald](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jmacdonald801)** commented I too would like this to be released. It's really hard to target different environments with the same build without this functionality. A good example is using profile to set classifiers and dependencyManagement for different J2EE containers. -- 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] (MNG-8666) The deprecated settings builder cannot parse the default settings
[
https://issues.apache.org/jira/browse/MNG-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned MNG-8666:
Assignee: Guillaume Nodet
> The deprecated settings builder cannot parse the default settings
> -
>
> Key: MNG-8666
> URL: https://issues.apache.org/jira/browse/MNG-8666
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-rc-4
>
>
> {code:java}
> [INFO] [stdout] 2025-03-31 22:12:34,709 WARN
> [io.qua.boo.res.mav.BootstrapMavenContext] (build-26) Settings problem
> encountered at
> /Users/gnodet/work/git/maven/apache-maven/target/apache-maven-4.0.0-rc-4-SNAPSHOT/conf/settings.xml,
> line 173, column 17: org.apache.maven.settings.io.SettingsParseException:
> Unrecognised tag: 'repositories' (position: START_TAG seen ...ories that
> maven will search artifacts for.\n -->\n ... @173:17)
> [INFO] [stdout] at
> org.apache.maven.settings.io.DefaultSettingsReader.read(DefaultSettingsReader.java:72)
> [INFO] [stdout] at
> org.apache.maven.settings.building.DefaultSettingsBuilder.readSettings(DefaultSettingsBuilder.java:156)
> [INFO] [stdout] at
> org.apache.maven.settings.building.DefaultSettingsBuilder.build(DefaultSettingsBuilder.java:94)
> [INFO] [stdout] at
> io.quarkus.bootstrap.resolver.maven.BootstrapMavenContext.getEffectiveSettings(BootstrapMavenContext.java:346)
> [INFO] [stdout] at
> io.quarkus.bootstrap.resolver.maven.BootstrapMavenContext.newRepositorySystemSession(BootstrapMavenContext.java:493)
> [INFO] [stdout] at
> io.quarkus.bootstrap.resolver.maven.BootstrapMavenContext.getRepositorySystemSession(BootstrapMavenContext.java:310)
> [INFO] [stdout] at
> io.quarkus.bootstrap.resolver.maven.MavenArtifactResolver.(MavenArtifactResolver.java:115)
> [INFO] [stdout] at
> io.quarkus.bootstrap.BootstrapAppModelFactory.getAppModelResolver(BootstrapAppModelFactory.java:160)
> [INFO] [stdout] at
> io.quarkus.bootstrap.BootstrapAppModelFactory.resolveAppModelForWorkspace(BootstrapAppModelFactory.java:265)
> [INFO] [stdout] at
> io.quarkus.bootstrap.BootstrapAppModelFactory.resolveAppModel(BootstrapAppModelFactory.java:216)
> [INFO] [stdout] at
> io.quarkus.deployment.dev.testing.TestSupport.init(TestSupport.java:213)
> [INFO] [stdout] at
> io.quarkus.deployment.dev.testing.TestSupport.start(TestSupport.java:136)
> [INFO] [stdout] at
> io.quarkus.deployment.dev.testing.TestTracingProcessor.startTesting(TestTracingProcessor.java:108)
> [INFO] [stdout] at
> java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733)
> [INFO] [stdout] at
> io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856)
> [INFO] [stdout] at
> io.quarkus.builder.BuildContext.run(BuildContext.java:255)
> [INFO] [stdout] at
> org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
> [INFO] [stdout] at
> org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2675)
> [INFO] [stdout] at
> org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2654)
> [INFO] [stdout] at
> org.jboss.threads.EnhancedQueueExecutor.runThreadBody(EnhancedQueueExecutor.java:1627)
> [INFO] [stdout] at
> org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1594)
> [INFO] [stdout] at java.base/java.lang.Thread.run(Thread.java:1583)
> [INFO] [stdout] at
> org.jboss.threads.JBossThread.run(JBossThread.java:499)
> [INFO] [stdout] Caused by:
> org.codehaus.plexus.util.xml.pull.XmlPullParserException: Unrecognised tag:
> 'repositories' (position: START_TAG seen ...ories that maven will search
> artifacts for.\n -->\n ... @173:17)
> [INFO] [stdout] at
> org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.checkUnknownElement(SettingsXpp3Reader.java:152)
> [INFO] [stdout] at
> org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.parseSettings(SettingsXpp3Reader.java:1553)
> [INFO] [stdout] at
> org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.read(SettingsXpp3Reader.java:594)
> [INFO] [stdout] at
> org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.read(SettingsXpp3Reader.java:625)
> [INFO] [stdout] at
> org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.read(SettingsXpp3Reader.java:656)
> [INFO] [stdout] at
> org.apache.maven.settings.io.DefaultSettingsReader.read(DefaultSettingsReader.java:70)
> [INFO] [stdout] ... 22 more
> [INFO] [stdout] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MCOMPILER-412) Support --process-module-path
[
https://issues.apache.org/jira/browse/MCOMPILER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937406#comment-17937406
]
Gili edited comment on MCOMPILER-412 at 3/21/25 12:55 PM:
--
Either the parameter name change or there is a typo in the title and
description. I think you meant to refer to {{\--processor-module-path}} not
{{\--process-module-path}}.
was (Author: cowwoc):
Either the parameter name change or there is a typo in the title and
description. I think you meant to refer to *--processor-module-path* not
{*}--process-module-path{*}.
> Support --process-module-path
> -
>
> Key: MCOMPILER-412
> URL: https://issues.apache.org/jira/browse/MCOMPILER-412
> Project: Maven Compiler Plugin (Moved to GitHub)
> Issue Type: Improvement
>Affects Versions: 3.8.0, 3.8.1
>Reporter: remi forax
>Priority: Major
>
> {quote}
> In the modular world, javac will look for annotation processor in the
> module-path (only if the annotation processor module is required by the
> module-info, you can use "required static" or uses with the service) and
> javac will also look to the --processor-module-path with again a nice
> separation because the source code doesn't see the module inside the module.
> Everything works cleanly if there is no module-info.java, if you have a
> module-info.java, you have two cases
> 1) your annotation processor is itself a module, if you do a requires on it,
> Maven will put it in the module-path, so it will work (but there is no nice
> separation provided by --processor-module-path)
> 2) your annotation processor is not a module, you can do a require on it but
> Maven will not put it on the module-path because it's not a module, so you
> have to use the of the Maven compiler plugin
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-252] Deploy current archive without creating new archive (jar, war, ear) [maven-deploy-plugin]
jira-importer commented on issue #188: URL: https://github.com/apache/maven-deploy-plugin/issues/188#issuecomment-2771513692 **[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented Why do you need maven-deploy-plugin. Based on a usual project which uses for example a maven-ear-plugin this will be deployed automatically via `mvn clean deploy` without supplemental configuration needed. Can you please give an example project and the commands, JDK version you are using and Maven version and how you triggered the build.. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-77] Add new option to resolve snapshot dependencies when deploying [maven-deploy-plugin]
jira-importer commented on issue #142: URL: https://github.com/apache/maven-deploy-plugin/issues/142#issuecomment-2771510035 **[Carlo de Wolf](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wolfc)** commented To clarify: Suppose you have the following dependency chain: A -> B -> C Now if you deploy a snapshot of C which passes all unit tests, but for some reason B can't be deployed because of unit test failures then A-SNAPSHOT becomes useless for other projects. Anybody using that one will end up with a 'broken' C-SNAPSHOT. Instead the dependency chain should be: A-1 -> B-1 -> C-1 Then it becomes: A-1 -> B-1 -> C-1, B-2 -> C-2 (where B-2 / SNAPSHOT fails to deploy) Now A-1 / SNAPSHOT still forms a latest stable snapshot chain. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
jira-importer commented on issue #216: URL: https://github.com/apache/maven-deploy-plugin/issues/216#issuecomment-2771515754 **[Julien CARSIQUE](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jcarsique)** commented I don't think so: - MDEPLOY-160 is a generic and clear feature: do not rebuild already built artifacts, take them from the local repository. On implementation side, that can rely on maven-install-plugin (looking at the m2repo given the current GAV) or on maven-deploy-plugin with a specific "two steps" command or option (first execution only reminds the installed artifacts, second execution deploys those artifacts). - MDEPLOY-118 mixes multiple issues and specific cases: POM being deployed twice, adding an alternate artifact (classifier) along with an already deployed artifact, need to define generic classifier use cases... You can set MDEPLOY-118 as depending on MDEPLOY-160. For advanced releasing process purpose in my company (https://jira.nuxeo.com/browse/NXBT-739), I critically need specifically MDEPLOY-124, MDEPLOY-160, MDEPLOY-169 and/or MDEPLOY-172. Whereas when I encountered MDEPLOY-118, I could more easily work around. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-254] Maven Deploy Plugin deploy jar twice : Maven 3.3.3 [maven-deploy-plugin]
jira-importer commented on issue #187: URL: https://github.com/apache/maven-deploy-plugin/issues/187#issuecomment-2771513625 **[Alexander Kriegisch](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kriegaex)** commented Sorry, [Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o), we posted at the same time. I just documented the same fix in my edit above, see links and screenshot. Whatever "CVE fixes" might mean, 3.8.x should contain this fix too. It is rather difficult to understand for users that the upcoming 3.6.4 will contain a fix which in a higher version 3.8.x is not fixed. It might urge people to downgrade, which always feels a bit odd. Sorry for not knowing the ins and outs of Maven version numbers, I am sure there is a good explanation for it - just not an intuitive one. 😉 **Update:** I see, [CVE = Common Vulnerabilities and Exposures](https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-254] Maven Deploy Plugin deploy jar twice : Maven 3.3.3 [maven-deploy-plugin]
jira-importer commented on issue #187: URL: https://github.com/apache/maven-deploy-plugin/issues/187#issuecomment-2771513651 **[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented I hate this bug as well, extremely annoying. Don't worry, everything is fine. I am glad that this was fixed after all these years. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-44] Add uniqueVersion parameter to deploy goal as deploy-file goal [maven-deploy-plugin]
jira-importer commented on issue #133: URL: https://github.com/apache/maven-deploy-plugin/issues/133#issuecomment-2771509314 **[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented The approach described by Kalle is not a workaround but the primary means to control the snapshot naming. The attached demo project works for me. The only pitfall I could imagine here is that people have a dedicated `` configured in their POM but set the `` flag on the `` element instead of ``. > But, it'd be very useful if you could override uniqueVersion setting from the command line. > That's already possible via a profile that overrides ``. Please provide more details (debug log, demo project) if the usage of `false` really does not work. -- 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 43 to 44 [maven]
slawekjaranowski commented on PR #2162: URL: https://github.com/apache/maven/pull/2162#issuecomment-2741682203 > > By the way we need a fix site build eg with profile run-its without it is ok. > > @slawekjaranowski Could you rephrase please ? I'm not sure to understand exactly what you mean. please try ``` mvn site -P run-its ``` will try to build site also in its modules -- 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] (SUREFIRE-2299) Missing tests inside Surefire report for Cucumber scenarios
[
https://issues.apache.org/jira/browse/SUREFIRE-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940023#comment-17940023
]
Piotr Zygielo commented on SUREFIRE-2299:
-
I do not have full understanding of this puzzle yet.
But while SUREFIRE-2298 (for nested tests) seems to at least collect summary
correctly,
this one lets failures to pass without reporting them.
(Perhaps reproducer could be updated to show that case? I'd negate
{{printSummary}}
and {{testFailureIgnore}} as well.)
While the 5aeca19716dedc4cbcab8d68dfc74a99f50ce9ee might be the cause of both,
the responsible line could be different.
FWIW, at this moment, 5aeca19716dedc4cbcab8d68dfc74a99f50ce9ee still reverts
cleanly.
> Missing tests inside Surefire report for Cucumber scenarios
> ---
>
> Key: SUREFIRE-2299
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2299
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.5.3
>Reporter: Florin Slev
>Priority: Major
> Attachments: TEST-io.example.CalculatorTest.xml,
> io.example.CalculatorTest.txt
>
>
> It seems Maven Surefire 3.5.3 no longer generates test reports when executing
> Cucumber scenarios.
> Steps:
> 1.) Git clone the following showcase project
> https://github.com/fslev/cucumber-showcase
> 2.) Run Maven command
> {code}
> mvn clean test
> {code}
> Actual:
> Though the scenarios were successfully executed, there is no related
> information inside target/surefire-reports/io.example.CalculatorTest.txt
> Tests run: 0
> {code}
> ---
> Test set: io.example.CalculatorTest
> ---
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.17 s -- in
> io.example.CalculatorTest
> {code}
> 3.) Downgrade Maven Surefire to 3.5.2
> Actual:
> Everything works fine now.
> Might be related to https://issues.apache.org/jira/browse/SUREFIRE-2298
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNG-8612] Document Node#asString and remove Version#asString and VersionConstraint#asString [maven]
gnodet opened a new pull request, #2172: URL: https://github.com/apache/maven/pull/2172 JIRA issue: [MNG-8612](https://issues.apache.org/jira/browse/MNG-8612) Supersedes #2149 -- 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] (MNG-8661) Bump com.google.guava:guava from 33.4.5-jre to 33.4.6-jre
Guillaume Nodet created MNG-8661: Summary: Bump com.google.guava:guava from 33.4.5-jre to 33.4.6-jre Key: MNG-8661 URL: https://issues.apache.org/jira/browse/MNG-8661 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/2185 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [I] [MDEPLOY-84] NPE when deploy-file with generatePom=false [maven-deploy-plugin]
jira-importer commented on issue #143: URL: https://github.com/apache/maven-deploy-plugin/issues/143#issuecomment-2771510110 **[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented Fixed in [r754784](http://svn.eu.apache.org/viewvc?view=rev&revision=754784). -- 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:maven-parent from 43 to 44 [maven-wagon]
dependabot[bot] opened a new pull request, #156:
URL: https://github.com/apache/maven-wagon/pull/156
Bumps
[org.apache.maven:maven-parent](https://github.com/apache/maven-parent) from 43
to 44.
Release notes
Sourced from https://github.com/apache/maven-parent/releases";>org.apache.maven:maven-parent's
releases.
44
:boom: Breaking changes
Move snapshot repositories in a profile (https://redirect.github.com/apache/maven-parent/pull/451";>#451) https://github.com/slawekjaranowski";>@slawekjaranowski
Check test code by checkstyle (https://redirect.github.com/apache/maven-parent/pull/228";>#228) https://github.com/slawekjaranowski";>@slawekjaranowski
🚀 New features and improvements
Move snapshot repositories in a profile (https://redirect.github.com/apache/maven-parent/pull/451";>#451) https://github.com/slawekjaranowski";>@slawekjaranowski
Introduce property maven.site.path.suffix to allow override site path
(https://redirect.github.com/apache/maven-parent/pull/239";>#239)
https://github.com/slawekjaranowski";>@slawekjaranowski
Use v@{project.version} as tag template for releases (https://redirect.github.com/apache/maven-parent/pull/455";>#455) https://github.com/slawekjaranowski";>@slawekjaranowski
import KEYS history from svn (https://redirect.github.com/apache/maven-parent/pull/240";>#240) https://github.com/hboutemy";>@hboutemy
Add licenseText to modello (https://redirect.github.com/apache/maven-parent/pull/241";>#241) https://github.com/slawekjaranowski";>@slawekjaranowski
Update site descriptor to 2.0 (https://redirect.github.com/apache/maven-parent/pull/232";>#232) https://github.com/slawekjaranowski";>@slawekjaranowski
Check test code by checkstyle (https://redirect.github.com/apache/maven-parent/pull/228";>#228) https://github.com/slawekjaranowski";>@slawekjaranowski
Add issues templates (https://redirect.github.com/apache/maven-parent/pull/226";>#226) https://github.com/slawekjaranowski";>@slawekjaranowski
Accept all line endings with spotless (https://redirect.github.com/apache/maven-parent/pull/217";>#217) https://github.com/kwin";>@kwin
Enable automatic formatter when not on CI (https://redirect.github.com/apache/maven-parent/pull/215";>#215) https://github.com/gnodet";>@gnodet
Bump com.diffplug.spotless:spotless-maven-plugin to enable the
sortpom/quiet option (https://redirect.github.com/apache/maven-parent/pull/213";>#213) https://github.com/gnodet";>@gnodet
🐛 Bug Fixes
Fix asf.yaml syntax (https://redirect.github.com/apache/maven-parent/pull/459";>#459) https://github.com/slawekjaranowski";>@slawekjaranowski
📦 Dependency updates
Bump parent to 34 (https://redirect.github.com/apache/maven-parent/pull/461";>#461) https://github.com/slawekjaranowski";>@slawekjaranowski
Bump org.junit:junit-bom from 5.12.0 to 5.12.1 (https://redirect.github.com/apache/maven-parent/pull/460";>#460) @https://github.com/apps/dependabot";>dependabot[bot]
Bump org.junit:junit-bom from 5.11.4 to 5.12.0 (https://redirect.github.com/apache/maven-parent/pull/236";>#236) @https://github.com/apps/dependabot";>dependabot[bot]
Bump com.diffplug.spotless:spotless-maven-plugin from 2.44.2 to 2.44.3
(https://redirect.github.com/apache/maven-parent/pull/234";>#234)
@https://github.com/apps/dependabot";>dependabot[bot]
Bump org.codehaus.mojo:taglist-maven-plugin from 3.1.0 to 3.2.1 (https://redirect.github.com/apache/maven-parent/pull/208";>#208) @https://github.com/apps/dependabot";>dependabot[bot]
Bump org.codehaus.mojo:extra-enforcer-rules from 1.8.0 to 1.9.0 (https://redirect.github.com/apache/maven-parent/pull/201";>#201) @https://github.com/apps/dependabot";>dependabot[bot]
Bump org.apache.maven.plugins:maven-jxr-plugin from 3.4.0 to 3.6.0 (https://redirect.github.com/apache/maven-parent/pull/210";>#210) @https://github.com/apps/dependabot";>dependabot[bot]
Bump org.apache.maven.plugins:maven-pmd-plugin from 3.23.0 to 3.26.0 (https://redirect.github.com/apache/maven-parent/pull/211";>#211) @https://github.com/apps/dependabot";>dependabot[bot]
Bump com.diffplug.spotless:spotless-maven-plugin from 2.44.0.BETA4 to
2.44.2 (https://redirect.github.com/apache/maven-parent/pull/229";>#229) @https://github.com/apps/dependabot";>dependabot[bot]
Bump org.junit:junit-bom from 5.11.3 to 5.11.4 (https://redirect.github.com/apache/maven-parent/pull/219";>#219) @https://github.com/apps/dependabot";>dependabot[bot]
https://issues.apache.org/jira/browse/MNG-8453";>[MNG-8453]
- Check dependency declarations by default (https://redirect.github.com/apache/maven-parent/pull/220";>#220) https://github.com/elharo";>@elharo
Bump org.codehaus.plexus:plexus-utils from 4.0.1 to 4.0.2 (https://redirect.github.com/apache/maven-parent/pull/202";>#202) @https://github.com/apps/dependabot";>dependabot[bot]
Bump org.cyclonedx:cyclonedx-maven-plugin from 2.9.0 to 2.9.1 (https://redirect.gi
[jira] [Commented] (MNG-8617) sonar-maven-plugin fails with Maven 4.0.0-rc3 with UnsupportedOperationException
[
https://issues.apache.org/jira/browse/MNG-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937364#comment-17937364
]
Guillaume Nodet commented on MNG-8617:
--
I've raised https://github.com/davidB/scala-maven-plugin/issues/836. I haven't
been able to raise any JIRA issue for Sonar though.
> sonar-maven-plugin fails with Maven 4.0.0-rc3 with
> UnsupportedOperationException
>
>
> Key: MNG-8617
> URL: https://issues.apache.org/jira/browse/MNG-8617
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-3
>Reporter: Filipe Roque
>Priority: Major
>
> {code:java}
> ❯ docker run -d \
> --name sonarqube \
> -e SONAR_ES_BOOTSTRAP_CHECKS_DISABLE=true \
> -p 9000:9000 \
> sonarqube:lts-community
> {code}
> {code:java}
> ❯ cat pom.xml
>
> 4.0.0
> com.mycompany.app
> my-app
> 1
>
> {code}
> {code:java}
> ❯ /opt/maven/apache-maven-4.0.0-rc-2/bin/mvn -q \
> org.sonarsource.scanner.maven:sonar-maven-plugin:5.0.0.4389:sonar \
> -Dsonar.login=admin \
> -Dsonar.password=admin \
> -Dsonar.host.url=http://localhost:9000/
> {code}
> {code:java}
> ❯ /opt/maven/apache-maven-4.0.0-rc-3/bin/mvn -q \
> org.sonarsource.scanner.maven:sonar-maven-plugin:5.0.0.4389:sonar \
> -Dsonar.login=admin \
> -Dsonar.password=admin \
> -Dsonar.host.url=http://localhost:9000/
> [ERROR] Failed to execute goal
> org.sonarsource.scanner.maven:sonar-maven-plugin:5.0.0.4389:sonar
> (default-cli) on project my-app: null: MojoExecutionException:
> UnsupportedOperationException -> [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/MojoExecutionException
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6973) Document certain user properties in "mvn --help"
[
https://issues.apache.org/jira/browse/MNG-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939292#comment-17939292
]
Konrad Windszus commented on MNG-6973:
--
[~gnodet] Great, wdyt about adding that URL to the description of
https://github.com/apache/maven/blob/274184803c3726cdc3501237c379901740566bbf/compat/maven-embedder/src/main/java/org/apache/maven/cli/CLIManager.java#L157?
> Document certain user properties in "mvn --help"
>
>
> Key: MNG-6973
> URL: https://issues.apache.org/jira/browse/MNG-6973
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Documentation: Guides
>Affects Versions: 3.6.3
>Reporter: Konrad Windszus
>Priority: Major
>
> There are some user properties which can be used to influence behaviour of
> Maven which is not described via {{mvn --help}}:
> # {{maven.repo.local}}
> (https://github.com/apache/maven/blame/5739b12aa9fc03bdd9eb6482b7a75f98a3c1ba6e/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1603)
> # {{style.color}}
> https://github.com/apache/maven/blame/5739b12aa9fc03bdd9eb6482b7a75f98a3c1ba6e/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L503
> I haven't found any documentation around those anywhere but I consider both
> useful enough to be documented with {{--help}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] surefire shared utils version current version [maven-surefire]
olamy opened a new pull request, #825: URL: https://github.com/apache/maven-surefire/pull/825 - **surefire-shared-utils.version to 3.5.2** - **no need of this extra property** Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/SUREFIRE) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `SUREFIRE-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean install` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean install`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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] Check namespaces when reading XML models [maven]
gnodet opened a new pull request, #2170: URL: https://github.com/apache/maven/pull/2170 * validate namespace consistency in XML * make sure a valid namespace is used for modelVersion > 4.0.0 -- 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-8638) Properties in repository id/url not supported anymore
[
https://issues.apache.org/jira/browse/MNG-8638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937309#comment-17937309
]
Guillaume Nodet commented on MNG-8638:
--
Note that Maven 4 introduces project settings if that can help.
> Properties in repository id/url not supported anymore
> -
>
> Key: MNG-8638
> URL: https://issues.apache.org/jira/browse/MNG-8638
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-rc-3
>Reporter: Marc Guillemot
>Priority: Major
>
> Following pom.xml can be used with Maven 3.9.x but not mit Maven 4.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> test
> properties-in-repos
> 0.0.1-SNAPSHOT
> pom
>
> snapshotsRepo
>
> https://my.server/snapshotsRepo
>
>
>
> useNightlySnapshot
>
>
> nightlySnapshotsRepo
>
> https://my.server/nightlySnapshotsRepo
>
>
>
>
>
> ${repo.snapshots.id}
> ${repo.snapshots.url}
>
> false
>
>
>
>
> {code}
> Maven 4.0.0-rc-3 fails with following error:
> {code:java}
> [ERROR] Some problems were encountered while processing the POMs
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project test:properties-in-repos:pom:0.0.1-SNAPSHOT
> (C:\dev\eclipse-workspace-okular-bis\poc-dynamic-mvn-deploy\pom.xml) has 1
> error
> [ERROR] 'repositories.repository.[${repo.snapshots.id}].url' contains an
> unsupported expression (only expressions starting with 'project.basedir' or
> 'project.rootDirectory' are supported). @
> test:properties-in-repos:0.0.1-SNAPSHOT,
> file://[sic]/poc-dynamic-mvn-deploy/pom.xml, line 26, column 13
> {code}
> This would block our migration to Maven 4 as we use such a construct to
> deploy snapshots from nightly builds to a separate repository.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-226] DeployAtEnd fails when module has extension [maven-deploy-plugin]
jira-importer commented on issue #181: URL: https://github.com/apache/maven-deploy-plugin/issues/181#issuecomment-2771513066 **[Slawomir Jaranowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slawekjaranowski)** commented Probably fixed in previous release in linked issues. I close now as fixed to be reported. There are also exist test which use extensions: https://github.com/apache/maven-deploy-plugin/blob/master/src/it/deploy-at-end-pass/module4/pom.xml -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-55] spaces in local path [maven-deploy-plugin]
jira-importer commented on issue #230: URL: https://github.com/apache/maven-deploy-plugin/issues/230#issuecomment-2771517080 **[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented Feel free to re-open with a test project demonstrating the issue. -- 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] (MNG-7430) mark MojoExecutionException as deprecated
[
https://issues.apache.org/jira/browse/MNG-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-7430.
Resolution: Not A Problem
It will be deprecated when the Maven 4 API becomes official.
> mark MojoExecutionException as deprecated
> -
>
> Key: MNG-7430
> URL: https://issues.apache.org/jira/browse/MNG-7430
> Project: Maven
> Issue Type: Task
> Components: Core
>Reporter: Olivier Lamy
>Priority: Major
>
> since the start of Maven 3.x there is no more difference in the build
> result/output between MojoFailureException and MojoExecutionException.
> Even the javadoc is wrong as it says
> {quote}Throwing this exception causes a "BUILD ERROR" message to be
> displayed.{quote}
>
> https://github.com/apache/maven/blob/14ca7234380f81e54a5643082816048f3b6b67cf/maven-plugin-api/src/main/java/org/apache/maven/plugin/MojoExecutionException.java#L24
> which definitely never happen see sample here
> https://github.com/olamy/maven-exception-plugin
> we could mark it as deprecated for 3.9.x onward.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-156] Add flag to 'ignoreReleaseDeployErrors' to ease multi module release builds with classifiers. [maven-deploy-plugin]
jira-importer commented on issue #165: URL: https://github.com/apache/maven-deploy-plugin/issues/165#issuecomment-2771511747 **[Dominik Richner](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=domi)** commented you'r right, MDEPLOY-118 would be good solution -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-299] Upgrade maven-plugin parent to 37 [maven-deploy-plugin]
jira-importer commented on issue #197: URL: https://github.com/apache/maven-deploy-plugin/issues/197#issuecomment-2771514303 **[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented Done in [4a72d8e9778c1878058435bdb919d40d65c879dd](https://gitbox.apache.org/repos/asf?p=maven-deploy-plugin.git;a=commitdiff;h=4a72d8e9778c1878058435bdb919d40d65c879dd) -- 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] Always refreshes artifacts in MavenITmng7470ResolverTransportTest [maven-integration-testing]
slawekjaranowski merged PR #402: URL: https://github.com/apache/maven-integration-testing/pull/402 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-47] Timeout during SCP upload [maven-deploy-plugin]
jira-importer commented on issue #207: URL: https://github.com/apache/maven-deploy-plugin/issues/207#issuecomment-2771515123 **[Stephen Connolly](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephenc)** commented Is this still a bug? -- 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] Github issues EAR-plugin [maven-site]
Bukama opened a new pull request, #744: URL: https://github.com/apache/maven-site/pull/744 (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: [I] [MDEPLOY-19] Ability to deploy-file as classifier [maven-deploy-plugin]
jira-importer commented on issue #286: URL: https://github.com/apache/maven-deploy-plugin/issues/286#issuecomment-2771521934 **[Jerome Lacoste](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lacostej)** commented What kind of brokeness? It doesn't apply? or it's not considered as a patch? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-972) copy-dependencies could copy signatures
[ https://issues.apache.org/jira/browse/MDEP-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936419#comment-17936419 ] ASF GitHub Bot commented on MDEP-972: - hboutemy commented on PR #514: URL: https://github.com/apache/maven-dependency-plugin/pull/514#issuecomment-2732156517 @Ndacyayisenga-droid CI failed, forgot to `mvn spotless:apply` before creating the commit > copy-dependencies could copy signatures > --- > > Key: MDEP-972 > URL: https://issues.apache.org/jira/browse/MDEP-972 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: copy-dependencies >Reporter: Benjamin Marwell >Assignee: Benjamin Marwell >Priority: Minor > > h2. Use case > Sometimes, the user might wish to keep the signatures for later validation, > eg when creating a distribution. > h2. Compatibility > This feature can be enabled by system property. The default is off (for > compatibility). > > h2. Implementation details > Create a new option, Boolean. Default value is false. > Good name would be something like "copySignatures" or something with > signatures. Make some suggestions. > Don't forget to add the system property name to the annotation, which could > have the prefix "mdep.". -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [I] [MDEPLOY-250] add documentation on managing network issues [maven-deploy-plugin]
jira-importer commented on issue #189: URL: https://github.com/apache/maven-deploy-plugin/issues/189#issuecomment-2771513810 **[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented There is a conceptual proposal how to solve this with HTTP-based wagon. -- 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] (MNG-5668) The concurrent builder should always run `after:xxx` phase if `before:xxx` phase has been started
[
https://issues.apache.org/jira/browse/MNG-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-5668.
Resolution: Fixed
> The concurrent builder should always run `after:xxx` phase if `before:xxx`
> phase has been started
> -
>
> Key: MNG-5668
> URL: https://issues.apache.org/jira/browse/MNG-5668
> Project: Maven
> Issue Type: Sub-task
> Components: FDPFC, Plugins and Lifecycle
>Reporter: Robert Scholte
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-rc-4
>
>
> Original proposal:
> {quote}
> There are right now 3 phases which also have a pre- and post-,
> namely integration-test, clean and site. However, even if one has bound goals
> to the post-phases, they're probably never called.
> When there's an integration-test starting up some server, you'd probably
> always want to kill it no matter what happens during the IT (let say a NPE).
> The proposal is to execute the post- as the finally block in Java. If
> you really want to execute only the integration-test without the post, the
> phase should be marked, e.g. 'mvn [integration-test]', where the brackets
> lock the phase.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNG-8657) GMavenPlus and AspectJ plugins break with 4-rc-3
[
https://issues.apache.org/jira/browse/MNG-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned MNG-8657:
Assignee: Guillaume Nodet
> GMavenPlus and AspectJ plugins break with 4-rc-3
>
>
> Key: MNG-8657
> URL: https://issues.apache.org/jira/browse/MNG-8657
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-3
> Environment: Any
>Reporter: Lenny Primak
>Assignee: Guillaume Nodet
>Priority: Critical
>
> GMavenPlus (latest) and AspectJ plugins are broken with rc-3:
> {code:java}
> [ERROR] Failed to execute goal
> org.codehaus.gmavenplus:gmavenplus-plugin:4.1.1:removeTestStubs (default) on
> project shiro-root: Execution default of goal
> org.codehaus.gmavenplus:gmavenplus-plugin:4.1.1:removeTestStubs failed.:
> UnsupportedOperationException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.gmavenplus:gmavenplus-plugin:4.1.1:removeTestStubs
> (default) on project shiro-root: Execution default of goal
> org.codehaus.gmavenplus:gmavenplus-plugin:4.1.1:removeTestStubs failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:346)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:310)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:214)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:179)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor$1.run(MojoExecutor.java:168)
> at
> org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute(DefaultMojosExecutionStrategy.java:39)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:165)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:110)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:60)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleStarter.execute(DefaultLifecycleStarter.java:123)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:311)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:225)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:149)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.doExecute(MavenInvoker.java:462)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:100)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:81)
> at
> org.apache.maven.cling.invoker.LookupInvoker.doInvoke(LookupInvoker.java:165)
> at
> org.apache.maven.cling.invoker.LookupInvoker.invoke(LookupInvoker.java:135)
> at org.apache.maven.cling.ClingSupport.run(ClingSupport.java:76)
> at org.apache.maven.cling.MavenCling.main(MavenCling.java:51)
> at
> jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke(Method.java:565)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:255)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:201)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:361)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default of goal
> org.codehaus.gmavenplus:gmavenplus-plugin:4.1.1:removeTestStubs failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:152)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:339)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:310)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:214)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:179)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor$1.run(MojoExecutor.java:168)
> at
> org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute(DefaultMojosExecutionStrategy.java:39)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:165)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:110)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at
> org.apache.maven.l
Re: [I] [MDEPLOY-197] deploy:deploy-file in some cases upload a file twice [maven-deploy-plugin]
jira-importer commented on issue #175: URL: https://github.com/apache/maven-deploy-plugin/issues/175#issuecomment-2771512562 **[Jeffrey Dang](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jcdang)** commented What you said makes sense. Go ahead and close. Bad configuration of the pom.xml was how I found this particular use case, but i didn't consider the case when same file was going to multiple URLs. I was using the assembly plugin with the deploy and the URLs were the same. Bad configuration was the cause but it would have been nice for the deploy plugin to be smart about not uploading the same file to the same place twice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-318] version 3.1.2 is uploading jar files to wrong endpoints [maven-deploy-plugin]
jira-importer commented on issue #203: URL: https://github.com/apache/maven-deploy-plugin/issues/203#issuecomment-2771514888 **[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** commented Created MNG-8138 as yet another follow up. -- 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] [MNG-8248] Add enable-native-access to startup scripts [maven]
slawekjaranowski commented on code in PR #2171: URL: https://github.com/apache/maven/pull/2171#discussion_r2007271894 ## apache-maven/src/bin/mvn: ## @@ -196,9 +196,16 @@ export MAVEN_PROJECTBASEDIR MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $@" export MAVEN_CMD_LINE_ARGS +# MNG-8248 +ENABLE_NATIVE_ACCESS="" +if "$JAVACMD" --enable-native-access=ALL-UNNAMED -version >/dev/null 2>&1; then + ENABLE_NATIVE_ACCESS="--enable-native-access=ALL-UNNAMED" Review Comment: good idea -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-97] the always be 1 on maven-metadata.xml [maven-deploy-plugin]
jira-importer commented on issue #256: URL: https://github.com/apache/maven-deploy-plugin/issues/256#issuecomment-2771519126 **[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented Are the permissions on the metadata files OK? For instance, if the existing metadata.xml can't be read, the last build number can't be determined. Some log output for the build when doing the deploy would be nice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-202] deploy-file goal insists on deploying source file for previous deploy-file execution [maven-deploy-plugin]
jira-importer commented on issue #222: URL: https://github.com/apache/maven-deploy-plugin/issues/222#issuecomment-2771516352 **[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented That will the status of the current MavenProject. And I know that someone will ask for the same solution with the `maven-install-plugin`, so that should be a sign that this is not the correct solution. IMHO it is still wrong to use `deploy-file` as part of the build-lifecycle. These jars are static, so there's no need to upload them as part of the lifecycle, right? `deploy-file` was very useful in the past when there were no good repository manager GUIs which gave you the option to upload artifacts. However, I think there's indeed an issue with the code: it should not abuse the current `MavenProject`. It would be better to create a new MavenProject instance in case of the `deploy-file` goal. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-228] Upgrade plexus-utils 3.1.0 [maven-deploy-plugin]
jira-importer commented on issue #180: URL: https://github.com/apache/maven-deploy-plugin/issues/180#issuecomment-2771512947 **[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented Done in [e2843fc249c74a022f00c8010e6d104f6deef976](https://gitbox.apache.org/repos/asf?p=maven-deploy-plugin.git;a=commitdiff;h=e2843fc249c74a022f00c8010e6d104f6deef976) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-44] Add uniqueVersion parameter to deploy goal as deploy-file goal [maven-deploy-plugin]
jira-importer commented on issue #133: URL: https://github.com/apache/maven-deploy-plugin/issues/133#issuecomment-2771509321 **[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented There was indeed a bug with the handling of `` in the Maven core (MNG-3885) in combination with profiles and inheritance. -- 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-8638) Properties in repository id/url not supported anymore
[
https://issues.apache.org/jira/browse/MNG-8638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937090#comment-17937090
]
Tamas Cservenak commented on MNG-8638:
--
That's right, and this is due "build reproducibility" reasons, given
project/repositories/repository is not for deploy but consumptions.
So you consume nightly snapshots from different repositories?
> Properties in repository id/url not supported anymore
> -
>
> Key: MNG-8638
> URL: https://issues.apache.org/jira/browse/MNG-8638
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-rc-3
>Reporter: Marc Guillemot
>Priority: Major
>
> Following pom.xml can be used with Maven 3.9.x but not mit Maven 4.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> test
> properties-in-repos
> 0.0.1-SNAPSHOT
> pom
>
> snapshotsRepo
>
> https://my.server/snapshotsRepo
>
>
>
>
>
> nightlySnapshotsRepo
>
> https://my.server/nightlySnapshotsRepo
>
>
>
>
>
> ${repo.snapshots.id}
> ${repo.snapshots.url}
>
> false
>
>
> {code}
> Maven 4.0.0-rc-3 fails with following error:
> {code:java}
> [ERROR] Some problems were encountered while processing the POMs
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project test:properties-in-repos:pom:0.0.1-SNAPSHOT
> (C:\dev\eclipse-workspace-okular-bis\poc-dynamic-mvn-deploy\pom.xml) has 1
> error
> [ERROR] 'repositories.repository.[${repo.snapshots.id}].url' contains an
> unsupported expression (only expressions starting with 'project.basedir' or
> 'project.rootDirectory' are supported). @
> test:properties-in-repos:0.0.1-SNAPSHOT,
> file://[sic]/poc-dynamic-mvn-deploy/pom.xml, line 26, column 13
> {code}
> This would block our migration to Maven 4 as we use such a construct to
> deploy snapshots from nightly builds to a separate repository.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.apache.maven:maven-parent from 43 to 44 [maven-resolver]
cstamas commented on PR #674: URL: https://github.com/apache/maven-resolver/pull/674#issuecomment-2736660777 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SCM-1028) Vulnerability: Clear text password is logged by JGit provider and by gitexe remoteinfo on a ls-remote failure
[
https://issues.apache.org/jira/browse/SCM-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940014#comment-17940014
]
ASF GitHub Bot commented on SCM-1028:
-
michael-o commented on code in PR #237:
URL: https://github.com/apache/maven-scm/pull/237#discussion_r2022619950
##
maven-scm-providers/maven-scm-providers-git/maven-scm-provider-git-commons/src/main/java/org/apache/maven/scm/provider/git/repository/GitScmProviderRepository.java:
##
@@ -246,21 +259,11 @@ private String getUrl(RepositoryUrl repoUrl) {
}
if (userName != null && userName.length() > 0) {
-String userInfo = userName;
+String userInfo = GitUtil.encodeURIComponent(userName);
if (password != null && password.length() > 0) {
-userInfo += ":" + password;
+userInfo += ":" + GitUtil.encodeURIComponent(password);
Review Comment:
This is a separate improvement, right? If so, can you separate it out? I'd
merge it separately.
##
maven-scm-providers/maven-scm-providers-git/maven-scm-provider-git-commons/src/main/java/org/apache/maven/scm/provider/git/util/GitUtil.java:
##
@@ -77,4 +89,52 @@ public static void setSettingsDirectory(File directory) {
public static File getSettingsFile() {
return new File(settingsDirectory, GIT_SETTINGS_FILENAME);
}
+
+/**
+ * Encodes the passed String as UTF-8 using an algorithm that's
+ * compatible with JavaScript's encodeURIComponent function.
+ * Returns null if the String is null.
+ * See
http://stackoverflow.com/questions/607176/java-equivalent-to-javascripts-encodeuricomponent-that-produces-identical-output
+ *
+ * @author John Topley
+ * @param s The String to be encoded
+ * @return the encoded String
+ */
+public static String encodeURIComponent(String s) {
+String result = s;
+if (s != null) {
+try {
+result = URLEncoder.encode(s, StandardCharsets.UTF_8.name())
// nl
Review Comment:
URLEncoder is not a URI encoder. This is for forms, not for URLs.
> Vulnerability: Clear text password is logged by JGit provider and by gitexe
> remoteinfo on a ls-remote failure
> -
>
> Key: SCM-1028
> URL: https://issues.apache.org/jira/browse/SCM-1028
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-gitexe, maven-scm-provider-jgit
>Affects Versions: 2.1.0
>Reporter: Markus Hoffrogge
>Priority: Critical
> Labels: Vulnerability, vulnerabilities, vulnerability
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> *Issue(s):*
> # {*}JGit provider{*}: If the git password contains special characters which
> are differently encoded by the {{URI class}} than {{{}by
> URLEncode.encode{}}}, then the password masking does not become effective and
> the password is logged in clear URI encoded format by the jgit provider.
> # {*}Gitexe remoteinfo{*}: In case ls-remote is failing, then a
> {{ScmException}} is being thrown with the fetch URL passed as error message
> containing the URI encoded clear password.
> *Root cause(s):*
> # The URL encoding used for the credentials within fetch and push URL
> differs from the encoding being used for masking the password at
> [JGitUtils.prepareSession(...)|https://github.com/apache/maven-scm/blob/55186fdf42f65fd3a1be07161bc198f092386f77/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/src/main/java/org/apache/maven/scm/provider/git/jgit/command/JGitUtils.java#L149]
> # Password is not masked for the exception message passed to the
> ScmException used at
> [GitRemoteInfoCommand.executeRemoteInfoCommand(...)|https://github.com/apache/maven-scm/blob/55186fdf42f65fd3a1be07161bc198f092386f77/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/remoteinfo/GitRemoteInfoCommand.java#L59]
> *Solution:*
> [PR #237|https://github.com/apache/maven-scm/pull/237]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-25] deploy:deploy-file installs the file in the local repository too (but it should not do that) [maven-deploy-plugin]
jira-importer commented on issue #260: URL: https://github.com/apache/maven-deploy-plugin/issues/260#issuecomment-2771519600 **[John Dennis Casey](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdcasey)** commented Deployment always implies installation in Maven. How does it make you wrongly believe the remote repository is alright? I'm not sure I follow...the whole point of this plugin is to write to the remote repository. Or, are you saying that you cannot verify what you put on the remote repository without first removing the locally installed artifact manually? If so, this is always the case in Maven. It's well documented in the lifecycle documentation here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-62] deploy on remote repository with linux [maven-deploy-plugin]
jira-importer commented on issue #233: URL: https://github.com/apache/maven-deploy-plugin/issues/233#issuecomment-2771517313 **[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-222] Issue Tracking in pom.xml points to outdated Codehaus site [maven-deploy-plugin]
jira-importer commented on issue #246: URL: https://github.com/apache/maven-deploy-plugin/issues/246#issuecomment-2771518353 **[Roland Illig](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rillignm)** commented To everyone possibly reporting a duplicate of this issue: The last release of this plugin was in 2014, so it may take some time until this change to the web site is visible. Until then, good luck submitting new issues for this plugin. (In other words, [Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise), could you perhaps trigger a release of this plugin, even if just for providing up-to-date documentation?) -- 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] Fix downloadlink for Daemon [maven-site]
Bukama opened a new pull request, #739: URL: https://github.com/apache/maven-site/pull/739 Follow up of #719 brought up in Slack Download is actually: `https://downloads.apache.org/maven/mvnd/1.0.2/maven-mvnd-1.0.2-src.zip` etc. so `src` instead of `source-release` -- 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-8071) Build in parallel by default
[
https://issues.apache.org/jira/browse/MNG-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939280#comment-17939280
]
Guillaume Nodet commented on MNG-8071:
--
Before activating parallel building by default, I think we should fix the
verbose output, as it's just completely useless in multithreaded build, even
more when using the concurrent builder.
> Build in parallel by default
>
>
> Key: MNG-8071
> URL: https://issues.apache.org/jira/browse/MNG-8071
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Core
>Affects Versions: 4.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
>
> Currently to build in parallel you have to explicitly define {{-T ..}}. What
> about just doing that by default in Maven 4?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-254] Maven Deploy Plugin deploy jar twice : Maven 3.3.3 [maven-deploy-plugin]
jira-importer commented on issue #187: URL: https://github.com/apache/maven-deploy-plugin/issues/187#issuecomment-2771513629 **[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented I will purpsue the fix backport to 3.8.2. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-318] version 3.1.2 is uploading jar files to wrong endpoints [maven-deploy-plugin]
jira-importer commented on issue #203: URL: https://github.com/apache/maven-deploy-plugin/issues/203#issuecomment-2771514841 **[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** commented With 3.1.2 of m-deploy-p same thing: https://gist.github.com/cstamas/a6fa1997c4922981dbced143127dce78 -- 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 com.google.guava:guava from 33.4.0-jre to 33.4.5-jre [maven-mvnd]
dependabot[bot] opened a new pull request, #1299: URL: https://github.com/apache/maven-mvnd/pull/1299 Bumps [com.google.guava:guava](https://github.com/google/guava) from 33.4.0-jre to 33.4.5-jre. Release notes Sourced from https://github.com/google/guava/releases";>com.google.guava:guava's releases. 33.4.5 For those upgrading from Guava 33.4.0 or earlier, be sure to read https://github.com/google/guava/releases/tag/v33.4.1";>the release notes for Guava 33.4.1. MavenJar files https://repo1.maven.org/maven2/com/google/guava/guava/33.4.5-jre/guava-33.4.5-jre.jar";>33.4.5-jre.jar https://repo1.maven.org/maven2/com/google/guava/guava/33.4.5-android/guava-33.4.5-android.jar";>33.4.5-android.jar Guava requires https://github.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies";>one runtime dependency, which you can download here: https://repo1.maven.org/maven2/com/google/guava/failureaccess/1.0.3/failureaccess-1.0.3.jar";>failureaccess-1.0.3.jar Javadoc https://guava.dev/releases/33.4.5-jre/api/docs/";>33.4.5-jre https://guava.dev/releases/33.4.5-android/api/docs/";>33.4.5-android JDiff https://guava.dev/releases/33.4.5-jre/api/diffs/";>33.4.5-jre vs. 33.4.4-jre https://guava.dev/releases/33.4.5-android/api/diffs/";>33.4.5-android vs. 33.4.4-android https://guava.dev/releases/33.4.5-android/api/androiddiffs/";>33.4.5-android vs. 33.4.5-jre Changelog Changed the Guava jar (plus guava-testlib and https://github.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies";>failureaccess jars) to be a modular jar. (7a71ea0bfa, 287c701a86) Changed various classes to stop using sun.misc.Unsafe under Java 9+. (ee63055ddd, 80aab00dc5b7a36785f5e09b6a54397388980cde, 400af25292096746ed3f6164f0ff88209acbb19f, 71d0692d418a5dd001c9b3786275a5f1f94e1971, d1a3cd5037528a2ae990bfceed9cdd009fbc54de, b3bb29a54b8f13d6f6630b6cb929867adbf6b9a0, 1a300f6b2f7ba03ae9bc3620a80c4d4589c65b69) Note that, if you use guava-android on the JVM (instead of using guava-jre), Guava will still try to use sun.misc.Unsafe. We will do https://redirect.github.com/google/guava/issues/6806#issuecomment-2738313040";>further work on this in the future. Belatedly updated the Public Suffix List data. (ee3b9c64382037f72b3a8341915cc64b87850b53, d25d62fc843ece1c3866859bc8639b815093eac8) Special thanks to https://github.com/sgammon";>@sgammon for https://javamodules.dev/";>his modularization efforts. 33.4.4 This is one of a series of releases that improve Guava's nullness annotations. For more information, including troubleshooting help, see https://github.com/google/guava/releases/tag/v33.4.1";>the release notes for Guava 33.4.1. Most users can update directly to Guava 33.4.5. Maven ... (truncated) Commits See full diff in https://github.com/google/guava/commits";>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 com.google.guava guava 33.4.5-jre 33.4.5-android
[jira] [Closed] (MNG-8548) StackOverflowError with Maven DI
[
https://issues.apache.org/jira/browse/MNG-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8548.
Resolution: Fixed
> StackOverflowError with Maven DI
>
>
> Key: MNG-8548
> URL: https://issues.apache.org/jira/browse/MNG-8548
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-2
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-rc-4
>
>
> The following commit generates a {{StackOverflowError}} inside Maven DI:
> [https://github.com/apache/maven-mvnd/pull/1252/commits/2fed30567f636cc9a5db977747d2cd667b1fd63d]
> A proper exception should be thrown.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-318] version 3.1.2 is uploading jar files to wrong endpoints [maven-deploy-plugin]
jira-importer commented on issue #203:
URL:
https://github.com/apache/maven-deploy-plugin/issues/203#issuecomment-2771514914
**[Juan Antonio Brena
Moral](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER307772)**
commented
Hi,
I noticed that the ticket continue opened and I would like to report than 2
weeks ago using the latest maven plugin 3.1.3 included in {_}Spring Boot
3.3.4{_}, it is not working for us when we try to deploy to JFROG Artifactory
or Azure Packages with Azure Pipelines.
The workaround that we had to do in order to deploy was to downgrade the
plugin to `maven-deploy-plugin:3.1.1:`
` - task: Maven@4`
` displayName: Deploy jar`
` inputs:`
` mavenPomFile: 'pom.xml'`
` goals: 'jar:jar
org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy'`
` ...`
I would like to collaborate to evolve the plugin and help in the testing.
Juan Antonio
--
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.plugin-testing:maven-plugin-testing-harness from 4.0.0-beta-2 to 4.0.0-beta-3 [maven-archiver]
dependabot[bot] commented on PR #88: URL: https://github.com/apache/maven-archiver/pull/88#issuecomment-2767283769 Superseded by #90. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-251] generatePom=false not working with 3.0.0-M1 [maven-deploy-plugin]
jira-importer commented on issue #185: URL: https://github.com/apache/maven-deploy-plugin/issues/185#issuecomment-2771513343 **[Robert Lieske](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=robert12345)** commented I have updated my sample to fix the issue with the content of the POM (artifact name differs from filename). Basicly you missed the point, that the uploaded artifacts should have a different name. I have changed the code upload a released version, so you'll see the problem (overwriting uploaded POM is not allowed), when you change the plugin-version to 3.0.0-M1. To make the sample work for you, supply 'releaseRepositoryUrl' and 'releaseRepository' with credentials in your settings.xml -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-157] Add deployAtEnd option for multimodule projects [maven-deploy-plugin]
jira-importer commented on issue #166: URL: https://github.com/apache/maven-deploy-plugin/issues/166#issuecomment-2771511841 **[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented [Dominik Richner](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=domi), I think I've got all the issues I'd like to be part of this release. Yesterday [dennislundberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dennislundberg) and I did some maintainance on the licensing and svn properties. We hit a svn encoding bug, not sure what to do with it yet. Binding the `deployAtEnd` to the `installAtEnd` is more complicated then you probably think. For the same reason I kept their default values to `false`, because I can think of situation where it won't work. You can always create a new issue for it as "improvement". -- 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] [MNG-5102] Add support for POM mixins [maven]
lfvjimisola commented on code in PR #1209: URL: https://github.com/apache/maven/pull/1209#discussion_r2011510361 ## its/core-it-suite/src/test/resources/mng-5102-mixins/gav/project/pom.xml: ## @@ -0,0 +1,60 @@ + + +http://maven.apache.org/POM/4.1.0"; root="true"> + org.apache.maven.its.mng5102 + gav + 0.1 + pom + + Maven Integration Test :: MNG-5102 + Mixins tests. + + + + +org.apache.maven.its.plugins +maven-it-plugin-expression +2.1-SNAPSHOT + + + + eval + +validate + + target/model.properties + +project/properties + + + + + + + + + + + org.apache.maven.its.mng5102 + mixin-2 Review Comment: Both dependencies and plugins. -- 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] (MNG-7280) Refactor DefaultToolchainManager and DefaultToolchainManagerPrivate
[ https://issues.apache.org/jira/browse/MNG-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-7280. Resolution: Fixed The new API only contains a single component. > Refactor DefaultToolchainManager and DefaultToolchainManagerPrivate > --- > > Key: MNG-7280 > URL: https://issues.apache.org/jira/browse/MNG-7280 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.x / Backlog > > > Component extending Component is bad practice. Obviously they need common > ancestor. > Refactor them or figure out is this really needed (according to comment by > original author [~mkleint] is not). -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [I] [MDEPLOY-91] Add option to delete old snapshots from repository during deployment. [maven-deploy-plugin]
jira-importer commented on issue #249: URL: https://github.com/apache/maven-deploy-plugin/issues/249#issuecomment-2771518568 **[Jason van Zyl](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jvanzyl)** commented The deploy plugin should do one thing well, and one thing only and that's deploy. Use a repository manager to do snapshot cleanup, they all do it. Or make a simple plugin to do it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-8547) The API is missing a way to listen to repository events
[
https://issues.apache.org/jira/browse/MNG-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8547:
-
Fix Version/s: 4.1.0
> The API is missing a way to listen to repository events
> ---
>
> Key: MNG-8547
> URL: https://issues.apache.org/jira/browse/MNG-8547
> Project: Maven
> Issue Type: New Feature
> Components: API
>Reporter: Guillaume Nodet
>Priority: Major
> Fix For: 4.1.0
>
>
> The {{Session#registerListener()}} should provide a specific interface to
> listen to resolver events (wrapping somehow the resolver's
> {{org.eclipse.aether.RepositoryListener}} interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] [MDEPLOY-19] Ability to deploy-file as classifier [maven-deploy-plugin]
jira-importer commented on issue #286: URL: https://github.com/apache/maven-deploy-plugin/issues/286#issuecomment-2771521968 **[Anagnostopoulos Kostis](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ankostis)** commented Hello, I have the same problem as Stefan Hübner said: The deploy goal does not take into consideration the \ parameter. We should either re-open this issue or file a new one! What should we do? Regards, Kostis -- 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] [MNG-8510] Avoid duplicate Utils classes [maven]
gnodet opened a new pull request, #2173: URL: https://github.com/apache/maven/pull/2173 - **Rename o.a.m.cling.invoker.Utils to CliUtils** - **Move DefaultPluginXmlFactory into maven-impl and plugin xml reader/writers to maven-support** - **Make Utils package protected and rename them** -- 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 net.bytebuddy:byte-buddy from 1.15.5 to 1.17.2 [maven-plugin-tools]
dependabot[bot] closed pull request #372: Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.17.2 URL: https://github.com/apache/maven-plugin-tools/pull/372 -- 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] [MNG-8663] Bump asmVersion from 9.7.1 to 9.8 [maven]
gnodet merged PR #2204: URL: https://github.com/apache/maven/pull/2204 -- 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] (MNG-8640) Bump org.apache.maven:maven-parent from 43 to 44
Slawomir Jaranowski created MNG-8640: Summary: Bump org.apache.maven:maven-parent from 43 to 44 Key: MNG-8640 URL: https://issues.apache.org/jira/browse/MNG-8640 Project: Maven Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: 3.9.10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8642) Provide the needed infrastructure to write plugins
Guillaume Nodet created MNG-8642: Summary: Provide the needed infrastructure to write plugins Key: MNG-8642 URL: https://issues.apache.org/jira/browse/MNG-8642 Project: Maven Issue Type: Task Reporter: Guillaume Nodet Fix For: 4.0.0-rc-4 In order to simplify plugin developers life, I think we should provide a BOM containing the dependencies needed to write a plugin. Until we have mixins available, the only way is to provide a BOM. The maven-plugin-testing is a very important component to use when writing plugins, and it needs to be part of that BOM, so I think it should be moved inside maven core project along the API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRESOLVER-646] Use Maven 4 internal bits [maven-resolver]
gnodet commented on PR #672: URL: https://github.com/apache/maven-resolver/pull/672#issuecomment-2737290343 > This cannot work as is: "mvn4 bits" are Maven4 annotated, and bridge is not here (is in maven-core which we don't want here)... It may be possible to move the bridge in a separate jar, not sure... Or do we want to use DI annotations for resolver ? -- 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] Enable building with Maven 4 [maven-plugin-testing]
gnodet commented on PR #91: URL: https://github.com/apache/maven-plugin-testing/pull/91#issuecomment-2744317935 > Maybe also add jdk 24? I don't think it's available on all platforms yet. We can make a follow-up PR in the coming days. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MDEPLOY-254] Maven Deploy Plugin deploy jar twice : Maven 3.3.3 [maven-deploy-plugin]
jira-importer commented on issue #187: URL: https://github.com/apache/maven-deploy-plugin/issues/187#issuecomment-2771513578 **[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented Does this still happen with Maven 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] [Updated] (MNG-8569) Deprecate and remove version ranges
[ https://issues.apache.org/jira/browse/MNG-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8569: - Priority: Major (was: Critical) > Deprecate and remove version ranges > --- > > Key: MNG-8569 > URL: https://issues.apache.org/jira/browse/MNG-8569 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > Fix For: 4.x / Backlog > > > To protect Maven users, we should eliminate, or at the very least warn, when > version ranges are used in dependency elements. See > [https://jlbp.dev/JLBP-14] for the rationale. tldr; version ranges make > projects vulnerable to malicious changes of ownership in dependencies that > can lead to remotely exploitable arbitrary code execution. I'd rate this > about a 9.0 on the severity scale. > I don't know of an attack using this vector in Java (yet) but it has > been used multiple times in other ecosystems to steal bitcoins and > install malware. Java has been lucky so far, but we are by no means > immune to it. > Since this is a compatibility breaking change, which I don't take likely but > IMHO is worth it in this case, use a multi-step process: > # Discourage this in the docs for version ranges, especially the POM > reference. > # Warn about this in the build when version ranges are encountered. > # Formally deprecate the relevant code in the repo. (Might not be necessary.) > # Add a switch (system property) to disable version ranges. Switch is off by > default. > # Turn the switch on by default. > # Remove the switch. > This might take a few years, so let's start now. It's also possible an active > attack will push us to do this overnight. If we start now, maybe we'll be > lucky enough to avoid emergency responses in the future. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
