[jira] [Created] (MPOM-468) Remove or provide option to disable checksum-maven-plugin

2024-02-15 Thread Christopher Tubbs (Jira)
Christopher Tubbs created MPOM-468: -- Summary: Remove or provide option to disable checksum-maven-plugin Key: MPOM-468 URL: https://issues.apache.org/jira/browse/MPOM-468 Project: Maven POMs

Re: [PR] Bump org.codehaus.plexus:plexus-resources from 1.1.0 to 1.3.0 [maven-checkstyle-plugin]

2024-02-15 Thread via GitHub
elharo commented on PR #129: URL: https://github.com/apache/maven-checkstyle-plugin/pull/129#issuecomment-1947752132 @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

Re: [PR] Bump org.codehaus.plexus:plexus-resources from 1.1.0 to 1.3.0 [maven-checkstyle-plugin]

2024-02-15 Thread via GitHub
dependabot[bot] commented on PR #129: URL: https://github.com/apache/maven-checkstyle-plugin/pull/129#issuecomment-1947746466 Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request `@dependabot

Re: [PR] Bump org.codehaus.plexus:plexus-resources from 1.1.0 to 1.3.0 [maven-checkstyle-plugin]

2024-02-15 Thread via GitHub
elharo commented on PR #129: URL: https://github.com/apache/maven-checkstyle-plugin/pull/129#issuecomment-1947746425 https://github.com/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

Re: [PR] please add java 21 support [maven-pmd-plugin]

2024-02-15 Thread via GitHub
elharo closed pull request #141: please add java 21 support URL: https://github.com/apache/maven-pmd-plugin/pull/141 -- 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

[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds

2024-02-15 Thread Pino Silvaggio (Jira)
[ https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817836#comment-17817836 ] Pino Silvaggio commented on MNG-7868: - I have this error, since bumping to 3.9.3 and it's under

[jira] [Updated] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds

2024-02-15 Thread Pino Silvaggio (Jira)
[ https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pino Silvaggio updated MNG-7868: Attachment: screenshot-1.png > "Could not acquire lock(s)" error in concurrent maven builds >

Re: [PR] Bump net.sourceforge.plantuml:plantuml from 1.2023.13 to 1.2024.2 [maven-site]

2024-02-15 Thread via GitHub
dependabot[bot] closed pull request #492: Bump net.sourceforge.plantuml:plantuml from 1.2023.13 to 1.2024.2 URL: https://github.com/apache/maven-site/pull/492 -- 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

Re: [PR] Bump net.sourceforge.plantuml:plantuml from 1.2023.13 to 1.2024.2 [maven-site]

2024-02-15 Thread via GitHub
dependabot[bot] commented on PR #492: URL: https://github.com/apache/maven-site/pull/492#issuecomment-1947527203 Superseded by #493. -- 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

[PR] Bump net.sourceforge.plantuml:plantuml from 1.2023.13 to 1.2024.3 [maven-site]

2024-02-15 Thread via GitHub
dependabot[bot] opened a new pull request, #493: URL: https://github.com/apache/maven-site/pull/493 Bumps [net.sourceforge.plantuml:plantuml](https://github.com/plantuml/plantuml) from 1.2023.13 to 1.2024.3. Commits

[jira] [Closed] (MNG-8039) DefaultProjectBuilder should not change given artifact

2024-02-15 Thread Slawomir Jaranowski (Jira)
[ https://issues.apache.org/jira/browse/MNG-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MNG-8039. Fix Version/s: 4.0.0 4.0.0-alpha-13 Resolution: Fixed >

[jira] [Commented] (MNG-8039) DefaultProjectBuilder should not change given artifact

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817796#comment-17817796 ] ASF GitHub Bot commented on MNG-8039: - slawekjaranowski merged PR #1408: URL:

Re: [PR] Remove old maven.plugin.tools.version property [maven-acr-plugin]

2024-02-15 Thread via GitHub
slawekjaranowski merged PR #29: URL: https://github.com/apache/maven-acr-plugin/pull/29 -- 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:

Re: [PR] [MNG-8039] Don't change resolved artifact by DefaultProjectBuilder [maven]

2024-02-15 Thread via GitHub
slawekjaranowski merged PR #1408: URL: https://github.com/apache/maven/pull/1408 -- 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:

Re: [PR] Add Dependabot setup [maven-wagon]

2024-02-15 Thread via GitHub
rmannibucau commented on PR #96: URL: https://github.com/apache/maven-wagon/pull/96#issuecomment-1947406136 Yeah, this is due to the other project XP and the lack of consensus that I think it may not be worth it. -- This is an automated message from the Apache Git Service. To respond to

Re: [PR] Add Dependabot setup [maven-wagon]

2024-02-15 Thread via GitHub
slachiewicz commented on PR #96: URL: https://github.com/apache/maven-wagon/pull/96#issuecomment-1947404713 Not sure If I understand Your question. Commiters will review if It makes sense, decide if its worth to create Jira and merge it. See other out Maven's projects where we use it.

[jira] [Comment Edited] (MJAR-301) maven jar plugin does not support all cases of ISO 8601 dates for project.build.outputTimestamp

2024-02-15 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MJAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817794#comment-17817794 ] Michael Osipov edited comment on MJAR-301 at 2/15/24 9:54 PM: -- Let's go

[jira] [Commented] (MJAR-301) maven jar plugin does not support all cases of ISO 8601 dates for project.build.outputTimestamp

2024-02-15 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MJAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817794#comment-17817794 ] Michael Osipov commented on MJAR-301: - Let's go through: 2022-02-12T15:30:45: Implies local offset, we

[jira] [Updated] (MJAR-301) maven jar plugin does not support all cases of ISO 8601 dates for project.build.outputTimestamp

2024-02-15 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MJAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAR-301: Description: Originally reported in

[jira] [Commented] (SCM-914) InfoItem.lastChangedDate is leaky abstraction

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/SCM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817788#comment-17817788 ] ASF GitHub Bot commented on SCM-914: michael-o commented on code in PR #193: URL:

Re: [PR] [SCM-914] Introduce properly typed last modified date [maven-scm]

2024-02-15 Thread via GitHub
michael-o commented on code in PR #193: URL: https://github.com/apache/maven-scm/pull/193#discussion_r1491006507 ## maven-scm-api/src/main/java/org/apache/maven/scm/command/info/InfoItem.java: ## @@ -18,7 +18,14 @@ */ package org.apache.maven.scm.command.info; +import

[jira] [Updated] (MRESOLVER-497) Investigate possible solutions for build number diffs on deploy

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-497: -- Description: The "snapshot freeze" is a common practice during development: simply

[jira] [Comment Edited] (MRESOLVER-497) Investigate possible solutions for build number diffs on deploy

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817782#comment-17817782 ] Tamas Cservenak edited comment on MRESOLVER-497 at 2/15/24 9:17 PM:

[jira] [Commented] (MRESOLVER-497) Investigate possible solutions for build number diffs on deploy

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817782#comment-17817782 ] Tamas Cservenak commented on MRESOLVER-497: --- Some solutions: * use "root" POM buildNumber

[jira] [Created] (MRESOLVER-497) Investigate possible solutions for build number diffs on deploy

2024-02-15 Thread Tamas Cservenak (Jira)
Tamas Cservenak created MRESOLVER-497: - Summary: Investigate possible solutions for build number diffs on deploy Key: MRESOLVER-497 URL: https://issues.apache.org/jira/browse/MRESOLVER-497

[jira] [Commented] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817776#comment-17817776 ] ASF GitHub Bot commented on MNG-8050: - cstamas commented on PR #1412: URL:

Re: [PR] [MNG-8050] emit warn in case of repo id clashes between settings and POM [maven]

2024-02-15 Thread via GitHub
cstamas commented on PR #1412: URL: https://github.com/apache/maven/pull/1412#issuecomment-1947200728 @gnodet ? -- 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

[jira] [Updated] (MRESOLVER-421) Extend NamedLock API to carry more than one name

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-421: -- Fix Version/s: 2.0.0 > Extend NamedLock API to carry more than one name >

[jira] [Updated] (MRESOLVER-404) New strategy may be needed for Hazelcast named locks

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-404: -- Fix Version/s: 2.0.0 > New strategy may be needed for Hazelcast named locks >

[jira] [Updated] (MRESOLVER-301) Resolver should handle signatures in same way as checksums

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-301: -- Fix Version/s: 2.0.0 > Resolver should handle signatures in same way as checksums >

[jira] [Created] (MJAR-301) maven jar plugin does not support all cases of ISO8601 dates for project.build.outputTimestamp

2024-02-15 Thread S L (Jira)
S L created MJAR-301: Summary: maven jar plugin does not support all cases of ISO8601 dates for project.build.outputTimestamp Key: MJAR-301 URL: https://issues.apache.org/jira/browse/MJAR-301 Project: Maven JAR

[jira] [Updated] (MJAR-301) maven jar plugin does not support all cases of ISO8601 dates for project.build.outputTimestamp

2024-02-15 Thread S L (Jira)
[ https://issues.apache.org/jira/browse/MJAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S L updated MJAR-301: - Attachment: git-plugin-timestamp-problem-demo_minimal.zip > maven jar plugin does not support all cases of ISO8601 dates

Re: [I] Building docker image with "dockerfile-maven-plugin" does not work with private (company) registry [maven-mvnd]

2024-02-15 Thread via GitHub
ppalaga commented on issue #909: URL: https://github.com/apache/maven-mvnd/issues/909#issuecomment-1946576280 Thanks for the investigation @reissseb. Apparently mvnd does not honor .mavenrc. In case of stock Maven it is sourced inside the `mvn` shell script: ``` if

[jira] [Updated] (MRESOLVER-493) Support premanaged of optional, exclusions and properties by DependencyGraphDumper

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-493: -- Component/s: Resolver > Support premanaged of optional, exclusions and properties

[jira] [Commented] (MRESOLVER-480) Update "Upgrading Resolver" page

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817731#comment-17817731 ] ASF GitHub Bot commented on MRESOLVER-480: -- cstamas merged PR #429: URL:

[jira] [Closed] (MRESOLVER-480) Update "Upgrading Resolver" page

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-480. - Resolution: Fixed > Update "Upgrading Resolver" page >

Re: [PR] [MRESOLVER-480] Document latest changes [maven-resolver]

2024-02-15 Thread via GitHub
cstamas merged PR #429: URL: https://github.com/apache/maven-resolver/pull/429 -- 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:

[jira] [Closed] (MRESOLVER-494) LOCAL_PATH Artifact property really belongs to "system" scope (or is at least very related to it)

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-494. - Resolution: Fixed > LOCAL_PATH Artifact property really belongs to "system" scope (or

[jira] [Assigned] (MRESOLVER-496) Move Resolver off java.io.File to NIO2 Paths

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-496: - Assignee: Tamas Cservenak > Move Resolver off java.io.File to NIO2 Paths >

[jira] [Comment Edited] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817700#comment-17817700 ] Guillaume Nodet edited comment on MNG-7038 at 2/15/24 3:44 PM: --- Fwiw, those

[jira] [Comment Edited] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817700#comment-17817700 ] Guillaume Nodet edited comment on MNG-7038 at 2/15/24 3:43 PM: --- Fwiw, those

[jira] [Comment Edited] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817700#comment-17817700 ] Guillaume Nodet edited comment on MNG-7038 at 2/15/24 3:40 PM: --- Fwiw, those

[jira] [Comment Edited] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817700#comment-17817700 ] Guillaume Nodet edited comment on MNG-7038 at 2/15/24 3:39 PM: --- Fwiw, those

[jira] [Comment Edited] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817700#comment-17817700 ] Guillaume Nodet edited comment on MNG-7038 at 2/15/24 3:37 PM: --- {{➜ maven

[jira] [Commented] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817700#comment-17817700 ] Guillaume Nodet commented on MNG-7038: -- {{code}} ➜ maven git:(lifecycle) ✗

[jira] [Comment Edited] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Envious Guest (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817677#comment-17817677 ] Envious Guest edited comment on MNG-7038 at 2/15/24 1:37 PM: - [~gnodet] hi

[jira] [Comment Edited] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Envious Guest (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817677#comment-17817677 ] Envious Guest edited comment on MNG-7038 at 2/15/24 1:37 PM: - [~gnodet] hi

[jira] [Commented] (MNG-7038) Introduce public properties to point to the root and top directories of (multi-module) project

2024-02-15 Thread Envious Guest (Jira)
[ https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817677#comment-17817677 ] Envious Guest commented on MNG-7038: [~gnodet] hi Guillaume, i see this ticket is marked as resolved,

[jira] [Commented] (MNG-8015) Control the type of path where each dependency can be placed

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817653#comment-17817653 ] ASF GitHub Bot commented on MNG-8015: - rmannibucau commented on PR #1401: URL:

Re: [PR] [MNG-8015] Control the type of path where each dependency can be placed [maven]

2024-02-15 Thread via GitHub
rmannibucau commented on PR #1401: URL: https://github.com/apache/maven/pull/1401#issuecomment-1945992269 Ok, so no action needed. side note: it is not random but an heuristic so does not always work indeed - don't ask me why default is not 100% the classpath, it is statically saner

[jira] [Commented] (MNG-8015) Control the type of path where each dependency can be placed

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817651#comment-17817651 ] ASF GitHub Bot commented on MNG-8015: - desruisseaux commented on PR #1401: URL:

Re: [PR] [MNG-8015] Control the type of path where each dependency can be placed [maven]

2024-02-15 Thread via GitHub
desruisseaux commented on PR #1401: URL: https://github.com/apache/maven/pull/1401#issuecomment-1945986433 The workaround is not needed per Java. It is needed because Maven 3 mixes class-path and module-path in an apparently random way. It is an example of case where putting the JAR on the

[jira] [Commented] (MNG-8015) Control the type of path where each dependency can be placed

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817646#comment-17817646 ] ASF GitHub Bot commented on MNG-8015: - rmannibucau commented on PR #1401: URL:

Re: [PR] [MNG-8015] Control the type of path where each dependency can be placed [maven]

2024-02-15 Thread via GitHub
rmannibucau commented on PR #1401: URL: https://github.com/apache/maven/pull/1401#issuecomment-1945954174 @desruisseaux I'm not sure I understand the proposal, the "workaround" is needed per java, do you want surefire to do it implicitly or just use the right path? Isn't it solved by the

[jira] [Commented] (MNG-8015) Control the type of path where each dependency can be placed

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817641#comment-17817641 ] ASF GitHub Bot commented on MNG-8015: - desruisseaux commented on PR #1401: URL:

Re: [PR] [MNG-8015] Control the type of path where each dependency can be placed [maven]

2024-02-15 Thread via GitHub
desruisseaux commented on PR #1401: URL: https://github.com/apache/maven/pull/1401#issuecomment-1945902723 As a real world use case for testing the Maven improvements, there is the following scenario: a project depends on JUnit 5 with `compile` scope (because the project is a conformance

Re: [I] Building docker image with "dockerfile-maven-plugin" does not work with private (company) registry [maven-mvnd]

2024-02-15 Thread via GitHub
reissseb commented on issue #909: URL: https://github.com/apache/maven-mvnd/issues/909#issuecomment-1945779478 The problem is the property `-Ddockerfile.useMavenSettingsForAuth` of the plugin `dockerfile-maven-plugin`. I set it to `true` in my `.mavenrc` file. Setting it as a

[jira] [Updated] (MRESOLVER-496) Move Resolver off java.io.File to NIO2 Paths

2024-02-15 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-496: -- Description: Internally, stop using java.io.File and use NIO2 Paths instead. From

[jira] [Created] (MRESOLVER-496) Move Resolver off java.io.File to NIO2 Paths

2024-02-15 Thread Tamas Cservenak (Jira)
Tamas Cservenak created MRESOLVER-496: - Summary: Move Resolver off java.io.File to NIO2 Paths Key: MRESOLVER-496 URL: https://issues.apache.org/jira/browse/MRESOLVER-496 Project: Maven Resolver

[jira] [Commented] (MNG-8053) Profile activation by packaging in the POM

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-8053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817608#comment-17817608 ] ASF GitHub Bot commented on MNG-8053: - gnodet merged PR #1410: URL:

[jira] [Closed] (MNG-8053) Profile activation by packaging in the POM

2024-02-15 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MNG-8053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8053. Resolution: Fixed > Profile activation by packaging in the POM >

Re: [PR] [MNG-8053] Profile activation by packaging in the POM [maven]

2024-02-15 Thread via GitHub
gnodet merged PR #1410: URL: https://github.com/apache/maven/pull/1410 -- 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:

[jira] [Created] (MNG-8053) Profile activation by packaging in the POM

2024-02-15 Thread Guillaume Nodet (Jira)
Guillaume Nodet created MNG-8053: Summary: Profile activation by packaging in the POM Key: MNG-8053 URL: https://issues.apache.org/jira/browse/MNG-8053 Project: Maven Issue Type: Improvement

[jira] [Commented] (MSHARED-1351) Confusing message when copying resources from project's baseDir

2024-02-15 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817606#comment-17817606 ] ASF GitHub Bot commented on MSHARED-1351: - abelsromero commented on PR #93: URL:

Re: [PR] [MSHARED-1351] Fix console message when origin is baseDir [maven-filtering]

2024-02-15 Thread via GitHub
abelsromero commented on PR #93: URL: https://github.com/apache/maven-filtering/pull/93#issuecomment-1945593859 Hi, all seems green in CI, except for 1 job that was mysteriously canceled. 路 Is there anything else that needs my attention in the PR? Thanks -- This is an automated message

[jira] [Updated] (SUREFIRE-2235) Manage of junit-vintage-engine is inconsistent

2024-02-15 Thread Slawomir Jaranowski (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated SUREFIRE-2235: -- Description: We have such situation {noformat} if junit-platform-engine