[GitHub] [maven-assembly-plugin] baneja opened a new pull request, #131: Refactored code for Maven Assembly Plugin. No code breaks, all test cases passing.
baneja opened a new pull request, #131: URL: https://github.com/apache/maven-assembly-plugin/pull/131 ### I have refactored the code using following techniques in the mentioned classes: 1. Refactoring name: **Extract Method** Location: src/main/java/org/apache/maven/plugins/assembly/utils/AssemblyFileUtils.java Line 69 2. Refactoring name: **Introduce explaining variable** Location: src/main/java/org/apache/maven/plugins/assembly/mojos/SingleAssemblyMojo.java Line 71 3. Refactoring name: **Rename Method** Location: src/main/java/org/apache/maven/plugins/assembly/format/ReaderFormatter.java Line 95 4. Refactoring name: **Replace conditional with Polymorphism** Location: src/main/java/org/apache/maven/plugins/assembly/io/DefaultMessageHolder.java Line 514 5. Refactoring name: **Extract Class** Location: src/main/java/org/apache/maven/plugins/assembly/archive/archiver/PrefixedFileSet.java Line 46 and 82 **Made new classes** RootPrefix.java: src/main/java/org/apache/maven/plugins/assembly/archive/archiver/RootPrefix.java Prefix Prefixed.java: src/main/java/org/apache/maven/plugins/assembly/archive/archiver/PrefixedPrefix.java 6. Refactoring name: **Push Down Method** Location: FileLocation.java: src/main/java/org/apache/maven/plugins/assembly/io/FileLocation.java Line 145 URLLocation.java: src/main/java/org/apache/maven/plugins/assembly/io/URLLocation.java Line 81 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709517#comment-17709517
]
Peter De Maeyer commented on MENFORCER-477:
---
Yes, I tried with 3.3.0, the behavior is the same.
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1, 3.3.0
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent,
> so I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> *Expected:* my snapshot project build succeeds with a snapshot parent.
> *Actual:* my snapshot project build _fails_ with a snapshot parent, despite
> {{onlyWhenRelease=true}}.
> *Workaround:* disable {{failWhenParentIsSnapshot}}, but then I lose the
> enforcement on the parent when I make a release of my project.
> I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
> into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it was a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
> {noformat}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective settings
> [WARNING] Unrecognised tag: 'properties' (position: START_TAG seen
> ...\n\t... @13:14) @ /home/peter/.m2/settings.xml,
> line 13, column 14
> [WARNING]
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for su.pernova:assertions-parent:pom:1.1.0-SNAPSHOT
> [WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must
> be unique but found duplicate declaration of plugin
> org.apache.maven.plugins:maven-failsafe-plugin @
> su.pernova:bom:1.1.0-SNAPSHOT,
> /home/peter/.m2/repository/su/pernova/bom/1.1.0-SNAPSHOT/bom-1.1.0-SNAPSHOT.pom,
> line 263, column 17
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Inspecting build with total of 5 modules...
> [INFO] Installing Nexus Staging features:
> [INFO] ... total of 5 executions of maven-deploy-plugin replaced with
> nexus-staging-maven-plugin
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Supernova Assertions - Parent
> [pom]
> [INFO] Supernova Assertions - Main
> [jar]
> [INFO] Supernova Assertions - JUnit 4
> [jar]
> [INFO] Supernova Assertions - JUnit 5
> [jar]
> [INFO] Supernova Assertions - JUnit 4 + JUnit 5
> [jar]
> [INFO]
> [INFO] < su.pernova:assertions-parent
> >
> [INFO] Building Supernova Assertions - Parent 1.1.0-SNAPSHOT
> [1/5]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ assertions-parent
> ---
> [INFO]
> [INFO] --- flatten-maven-plugin:1.3.0:clean (flatten-clean) @
> assertions-parent ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.2.1:enforce
> (enforce-no-snapshots-in-releases) @ assertions-parent ---
> [INFO]
>
> [INFO] Reactor Summary for Supernova Assertions - Parent 1.1.0-SNAPSHOT:
> [INFO]
> [INFO] Supernova Assertions - Parent .. FAILURE [ 0.464
> s]
> [INFO] Supernova Assertions - Main SKIPPED
> [INFO] Supernova Assertions - JUnit 4 . SKIPPED
> [INFO] Supernova Assertions - JUnit 5 . SKIPPED
> [INFO] Supernova Assertions - JUnit 4 + JUnit 5 ... SKIPPED
> [INFO]
>
> [INFO]
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Affects Version/s: 3.3.0
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1, 3.3.0
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent,
> so I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> *Expected:* my snapshot project build succeeds with a snapshot parent.
> *Actual:* my snapshot project build _fails_ with a snapshot parent, despite
> {{onlyWhenRelease=true}}.
> *Workaround:* disable {{failWhenParentIsSnapshot}}, but then I lose the
> enforcement on the parent when I make a release of my project.
> I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
> into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it was a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
> {noformat}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective settings
> [WARNING] Unrecognised tag: 'properties' (position: START_TAG seen
> ...\n\t... @13:14) @ /home/peter/.m2/settings.xml,
> line 13, column 14
> [WARNING]
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for su.pernova:assertions-parent:pom:1.1.0-SNAPSHOT
> [WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must
> be unique but found duplicate declaration of plugin
> org.apache.maven.plugins:maven-failsafe-plugin @
> su.pernova:bom:1.1.0-SNAPSHOT,
> /home/peter/.m2/repository/su/pernova/bom/1.1.0-SNAPSHOT/bom-1.1.0-SNAPSHOT.pom,
> line 263, column 17
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Inspecting build with total of 5 modules...
> [INFO] Installing Nexus Staging features:
> [INFO] ... total of 5 executions of maven-deploy-plugin replaced with
> nexus-staging-maven-plugin
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Supernova Assertions - Parent
> [pom]
> [INFO] Supernova Assertions - Main
> [jar]
> [INFO] Supernova Assertions - JUnit 4
> [jar]
> [INFO] Supernova Assertions - JUnit 5
> [jar]
> [INFO] Supernova Assertions - JUnit 4 + JUnit 5
> [jar]
> [INFO]
> [INFO] < su.pernova:assertions-parent
> >
> [INFO] Building Supernova Assertions - Parent 1.1.0-SNAPSHOT
> [1/5]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ assertions-parent
> ---
> [INFO]
> [INFO] --- flatten-maven-plugin:1.3.0:clean (flatten-clean) @
> assertions-parent ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.2.1:enforce
> (enforce-no-snapshots-in-releases) @ assertions-parent ---
> [INFO]
>
> [INFO] Reactor Summary for Supernova Assertions - Parent 1.1.0-SNAPSHOT:
> [INFO]
> [INFO] Supernova Assertions - Parent .. FAILURE [ 0.464
> s]
> [INFO] Supernova Assertions - Main SKIPPED
> [INFO] Supernova Assertions - JUnit 4 . SKIPPED
> [INFO] Supernova Assertions - JUnit 5 . SKIPPED
> [INFO] Supernova Assertions - JUnit 4 + JUnit 5 ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
> -
[jira] [Updated] (MSITE-943) Saved processed site content is overwritten when multiple locales are defined
[
https://issues.apache.org/jira/browse/MSITE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-943:
-
Summary: Saved processed site content is overwritten when multiple locales
are defined (was: Saved processed site content is overwritten with multiple
locales)
> Saved processed site content is overwritten when multiple locales are defined
> -
>
> Key: MSITE-943
> URL: https://issues.apache.org/jira/browse/MSITE-943
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: localization
>Affects Versions: 4.0.0-M6
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M7
>
>
> When {{saveProcessedContent}} is requsted the locale is not taken into
> account, thus only the locale is visible and the rest disappears (is
> overwritten).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-941) sitemap.xml is overwritten when multiple locales are defined
[
https://issues.apache.org/jira/browse/MSITE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-941:
-
Description: When more than one locale is defined the code does not
properly take it into account and overwrites the {{sitemap.xml}} which creates
incorrect output at the end. (was: When more than one locale is defined the
code does not properly take it into account and overwrites then {{sitemap.xml}}
which creates incorrect output at the end.)
> sitemap.xml is overwritten when multiple locales are defined
>
>
> Key: MSITE-941
> URL: https://issues.apache.org/jira/browse/MSITE-941
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: localization
>Affects Versions: 4.0.0-M6
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M7
>
>
> When more than one locale is defined the code does not properly take it into
> account and overwrites the {{sitemap.xml}} which creates incorrect output at
> the end.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-941) sitemap.xml is overwritten when multiple locales are defined
[
https://issues.apache.org/jira/browse/MSITE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-941:
-
Summary: sitemap.xml is overwritten when multiple locales are defined
(was: sitemap.xml overwritten when multiple locales are defined)
> sitemap.xml is overwritten when multiple locales are defined
>
>
> Key: MSITE-941
> URL: https://issues.apache.org/jira/browse/MSITE-941
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: localization
>Affects Versions: 4.0.0-M6
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M7
>
>
> When more than one locale is defined the code does not properly take it into
> account and overwrites then {{sitemap.xml}} which creates incorrect output at
> the end.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-site-plugin] michael-o opened a new pull request, #140: Locale awareness
michael-o opened a new pull request, #140: URL: https://github.com/apache/maven-site-plugin/pull/140 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/MSITE) 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 `[MSITE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MSITE-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 verify` 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 verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] 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
[jira] [Updated] (MSITE-935) Upgrade to Doxia Sitetools 2.0.0-M7, Maven Reporting Impl 4.0.0-M6, Maven Reporting Exec 2.0.0-M6
[
https://issues.apache.org/jira/browse/MSITE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-935:
-
Summary: Upgrade to Doxia Sitetools 2.0.0-M7, Maven Reporting Impl
4.0.0-M6, Maven Reporting Exec 2.0.0-M6 (was: Upgrade to Doxia Sitetools
2.0.0-M6, Maven Reporting Impl 4.0.0-M6, Maven Reporting Exec 2.0.0-M6)
> Upgrade to Doxia Sitetools 2.0.0-M7, Maven Reporting Impl 4.0.0-M6, Maven
> Reporting Exec 2.0.0-M6
> -
>
> Key: MSITE-935
> URL: https://issues.apache.org/jira/browse/MSITE-935
> Project: Maven Site Plugin
> Issue Type: Dependency upgrade
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M7
>
>
> This also includes renaming of {{relativizeDecorationLinks}} to
> {{relativizeSiteLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-943) Saved processed site content is overwritten with multiple locales
[
https://issues.apache.org/jira/browse/MSITE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-943:
-
Summary: Saved processed site content is overwritten with multiple locales
(was: Saved processed site content is ignored)
> Saved processed site content is overwritten with multiple locales
> -
>
> Key: MSITE-943
> URL: https://issues.apache.org/jira/browse/MSITE-943
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: localization
>Affects Versions: 4.0.0-M6
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M7
>
>
> When {{saveProcessedContent}} is requsted the locale is not taken into
> account, thus only the locale is visible and the rest disappears (is
> overwritten).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-pmd-plugin] elharo commented on pull request #123: Remove vestigial comment
elharo commented on PR #123: URL: https://github.com/apache/maven-pmd-plugin/pull/123#issuecomment-1499675909 Looks like something broke the integration between Github abd Jenkins: ``` <1s Recording test results [GitHub Checks] Causes for no suitable publisher found: [GitHub Checks] Trying to resolve checks parameters from GitHub SCM... [GitHub Checks] No GitHub app credentials found: '5f95d117-af3b-452a-9e5c-4bddb22a67f4' [GitHub Checks] See: https://github.com/jenkinsci/github-branch-source-plugin/blob/master/docs/github-app.adoc [GitHub Checks] Trying to resolve checks parameters from Git SCM... [GitHub Checks] No GitHub app credentials found: '5f95d117-af3b-452a-9e5c-4bddb22a67f4' [GitHub Checks] See: https://github.com/jenkinsci/github-branch-source-plugin/blob/master/docs/github-app.adoc [GitHub Checks] Job does not have valid credentials [Checks API] No suitable checks publisher found. ``` We really need to get serious about deflaking the CIs. -- 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] (MSITE-943) Saved processed site content is ignored
Michael Osipov created MSITE-943:
Summary: Saved processed site content is ignored
Key: MSITE-943
URL: https://issues.apache.org/jira/browse/MSITE-943
Project: Maven Site Plugin
Issue Type: Bug
Components: localization
Affects Versions: 4.0.0-M6
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 4.0.0-M7
When {{saveProcessedContent}} is requsted the locale is not taken into account,
thus only the locale is visible and the rest disappears (is overwritten).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709500#comment-17709500
]
Slawomir Jaranowski commented on MENFORCER-477:
---
Can you try with version 3.3.0?
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent,
> so I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> *Expected:* my snapshot project build succeeds with a snapshot parent.
> *Actual:* my snapshot project build _fails_ with a snapshot parent, despite
> {{onlyWhenRelease=true}}.
> *Workaround:* disable {{failWhenParentIsSnapshot}}, but then I lose the
> enforcement on the parent when I make a release of my project.
> I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
> into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it was a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
> {noformat}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective settings
> [WARNING] Unrecognised tag: 'properties' (position: START_TAG seen
> ...\n\t... @13:14) @ /home/peter/.m2/settings.xml,
> line 13, column 14
> [WARNING]
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for su.pernova:assertions-parent:pom:1.1.0-SNAPSHOT
> [WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must
> be unique but found duplicate declaration of plugin
> org.apache.maven.plugins:maven-failsafe-plugin @
> su.pernova:bom:1.1.0-SNAPSHOT,
> /home/peter/.m2/repository/su/pernova/bom/1.1.0-SNAPSHOT/bom-1.1.0-SNAPSHOT.pom,
> line 263, column 17
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Inspecting build with total of 5 modules...
> [INFO] Installing Nexus Staging features:
> [INFO] ... total of 5 executions of maven-deploy-plugin replaced with
> nexus-staging-maven-plugin
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Supernova Assertions - Parent
> [pom]
> [INFO] Supernova Assertions - Main
> [jar]
> [INFO] Supernova Assertions - JUnit 4
> [jar]
> [INFO] Supernova Assertions - JUnit 5
> [jar]
> [INFO] Supernova Assertions - JUnit 4 + JUnit 5
> [jar]
> [INFO]
> [INFO] < su.pernova:assertions-parent
> >
> [INFO] Building Supernova Assertions - Parent 1.1.0-SNAPSHOT
> [1/5]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ assertions-parent
> ---
> [INFO]
> [INFO] --- flatten-maven-plugin:1.3.0:clean (flatten-clean) @
> assertions-parent ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.2.1:enforce
> (enforce-no-snapshots-in-releases) @ assertions-parent ---
> [INFO]
>
> [INFO] Reactor Summary for Supernova Assertions - Parent 1.1.0-SNAPSHOT:
> [INFO]
> [INFO] Supernova Assertions - Parent .. FAILURE [ 0.464
> s]
> [INFO] Supernova Assertions - Main SKIPPED
> [INFO] Supernova Assertions - JUnit 4 . SKIPPED
> [INFO] Supernova Assertions - JUnit 5 . SKIPPED
> [INFO] Supernova Assertions - JUnit 4 + JUnit 5 ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [
[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request, #143: Bump maven-resources-plugin from 3.3.0 to 3.3.1
dependabot[bot] opened a new pull request, #143: URL: https://github.com/apache/maven-apache-parent/pull/143 Bumps [maven-resources-plugin](https://github.com/apache/maven-resources-plugin) from 3.3.0 to 3.3.1. Release notes Sourced from https://github.com/apache/maven-resources-plugin/releases";>maven-resources-plugin's releases. 3.3.1 https://issues.apache.org/jira/browse/MRESOURCES-288";>[MRESOURCES-288] - Make tests-jar reproducible (https://redirect.github.com/apache/maven-resources-plugin/pull/56";>#56) https://github.com/cstamas";>@cstamas https://issues.apache.org/jira/browse/MRESOURCES-297";>[MRESOURCES-297] - Update to parent POM 39, reformat (https://redirect.github.com/apache/maven-resources-plugin/pull/55";>#55) https://github.com/cstamas";>@cstamas https://issues.apache.org/jira/browse/MRESOURCES-293";>[MRESOURCES-293] - Make resources param not read-only (https://redirect.github.com/apache/maven-resources-plugin/pull/54";>#54) https://github.com/cstamas";>@cstamas https://issues.apache.org/jira/browse/MRESOURCES-295";>[MRESOURCES-295] - Drop Plexus legacy code (https://redirect.github.com/apache/maven-resources-plugin/pull/53";>#53) https://github.com/cstamas";>@cstamas https://issues.apache.org/jira/browse/MRESOURCES-294";>[MRESOURCES-294] - Upgrade plexus-utils to 3.5.1 (https://redirect.github.com/apache/maven-resources-plugin/pull/52";>#52) https://github.com/slachiewicz";>@slachiewicz 🚨 Removed remove specific IDE m2e files (https://redirect.github.com/apache/maven-resources-plugin/pull/40";>#40) https://github.com/olamy";>@olamy 📦 Dependency updates Bump apache/maven-gh-actions-shared from 2 to 3 (https://redirect.github.com/apache/maven-resources-plugin/pull/46";>#46) https://github.com/dependabot";>@dependabot 📝 Documentation updates doc: adds alternative variable syntax using @ delimiters to the documentation (https://redirect.github.com/apache/maven-resources-plugin/pull/36";>#36) https://github.com/kevin0x90";>@kevin0x90 Commits https://github.com/apache/maven-resources-plugin/commit/978ce1e9a1f4fb60d384a998a6ea473a21bb81d5";>978ce1e [maven-release-plugin] prepare release maven-resources-plugin-3.3.1 https://github.com/apache/maven-resources-plugin/commit/b7cd080d7ba98e5cefe58b1ef78c209cad8ae0fe";>b7cd080 [MRESOURCES-296] Upgrade to maven-filtering 3.3.1 https://github.com/apache/maven-resources-plugin/commit/1c9f610d5c2866fdd7fad182709f4dff2e157787";>1c9f610 [MRESOURCES-288] Make tests-jar reproducible (https://redirect.github.com/apache/maven-resources-plugin/issues/56";>#56) https://github.com/apache/maven-resources-plugin/commit/1946127aac4acb752fd3018dff8c7751434d6ca7";>1946127 [MRESOURCES-293] Rollback https://github.com/apache/maven-resources-plugin/commit/f7a6f229db49673ddd21ff521027b9af49f69bb8";>f7a6f22 [MRESOURCES-297] Update to parent POM 39, reformat (https://redirect.github.com/apache/maven-resources-plugin/issues/55";>#55) https://github.com/apache/maven-resources-plugin/commit/22d64ca56ed38b6e8dd5af7df0d5edb230d6fb86";>22d64ca remove specific IDE m2e files (https://redirect.github.com/apache/maven-resources-plugin/issues/40";>#40) https://github.com/apache/maven-resources-plugin/commit/02c2d010acfaae652bd69f447328ce14287cfbd4";>02c2d01 [MRESOURCES-293] Make resources param not read-only (https://redirect.github.com/apache/maven-resources-plugin/issues/54";>#54) https://github.com/apache/maven-resources-plugin/commit/6bb3e1ffb767eb00f8ebac7dadd64bc090ee3e44";>6bb3e1f [MRESOURCES-295] Drop Plexus legacy code (https://redirect.github.com/apache/maven-resources-plugin/issues/53";>#53) https://github.com/apache/maven-resources-plugin/commit/df7e17212980dfd079024cb7cfdafc1a469f106b";>df7e172 [MRESOURCES-294] Upgrade plexus-utils to 3.5.1 https://github.com/apache/maven-resources-plugin/commit/9354ecd248302c42be4f0822fa1c32b202a50947";>9354ecd Bump apache/maven-gh-actions-shared from 2 to 3 Additional commits viewable in https://github.com/apache/maven-resources-plugin/compare/maven-resources-plugin-3.3.0...maven-resources-plugin-3.3.1";>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
[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request, #142: Bump apache-source-release-assembly-descriptor from 1.0.6 to 1.5
dependabot[bot] opened a new pull request, #142: URL: https://github.com/apache/maven-apache-parent/pull/142 Bumps apache-source-release-assembly-descriptor from 1.0.6 to 1.5. [](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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request, #141: Bump maven-scm-publish-plugin from 3.1.0 to 3.2.1
dependabot[bot] opened a new pull request, #141: URL: https://github.com/apache/maven-apache-parent/pull/141 Bumps [maven-scm-publish-plugin](https://github.com/apache/maven-scm-publish-plugin) from 3.1.0 to 3.2.1. Commits https://github.com/apache/maven-scm-publish-plugin/commit/c35d070cfaf94ba16c65c814844d23dddee6e41f";>c35d070 [maven-release-plugin] prepare release maven-scm-publish-plugin-3.2.1 https://github.com/apache/maven-scm-publish-plugin/commit/f893483a2d9b895bb45f34d864602ce126bfccf7";>f893483 Fix colliding property https://github.com/apache/maven-scm-publish-plugin/commit/d77f1e930cc890ec8e59385d22afbf8c794862b6";>d77f1e9 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-scm-publish-plugin/commit/955d2730cd54582af7d24d3ddd4701dd6e6fa12d";>955d273 [maven-release-plugin] prepare release maven-scm-publish-plugin-3.2.0 https://github.com/apache/maven-scm-publish-plugin/commit/603ee6f149aa066cd0390f2e33f319edc18fec89";>603ee6f [MSCMPUB-58] Upgrade plugins and components (in ITs) https://github.com/apache/maven-scm-publish-plugin/commit/f240e7d1b613dd5d5d944dae095559a3e6d940c0";>f240e7d [MSCMPUB-57] Ignore formatting commit https://github.com/apache/maven-scm-publish-plugin/commit/c8b0849bad958bcc8d3c372c0968c52baa738319";>c8b0849 [MSCMPUB-57] Upgrade misc deps https://github.com/apache/maven-scm-publish-plugin/commit/ef21a970c9cdd66ef8107ad95b886a3d322018a1";>ef21a97 [MSCMPUB-57] Reformat https://github.com/apache/maven-scm-publish-plugin/commit/b96e65d8e2b610c2a595542df7f75ba8fd9e0c94";>b96e65d [MSCMPUB-57] Upgrade parent pom to 39 https://github.com/apache/maven-scm-publish-plugin/commit/08736576b107ac879a5b4d80dda3d332ce22b84d";>0873657 [MSCMPUB-54] Require Maven 3.2.5+ Additional commits viewable in https://github.com/apache/maven-scm-publish-plugin/compare/maven-scm-publish-plugin-3.1.0...maven-scm-publish-plugin-3.2.1";>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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request, #140: Bump maven-release-plugin from 3.0.0-M7 to 3.0.0
dependabot[bot] opened a new pull request, #140: URL: https://github.com/apache/maven-apache-parent/pull/140 Bumps [maven-release-plugin](https://github.com/apache/maven-release) from 3.0.0-M7 to 3.0.0. Commits https://github.com/apache/maven-release/commit/41253314909f1935a72c261d740871c463664c57";>4125331 [maven-release-plugin] prepare release maven-release-3.0.0 https://github.com/apache/maven-release/commit/bd9cdebc6e40f7bb30e0efbb9aaa17d4cf8f7866";>bd9cdeb Improve dependency declarations https://github.com/apache/maven-release/commit/231e949d4ed69aaf8d84f41df5cba550587b61f0";>231e949 [MRELEASE-1118] Upgrade Maven SCM to 2.0.0 https://github.com/apache/maven-release/commit/8c19cdc301fe28804a8a34f095789942c40975d6";>8c19cdc Fix https://github.com/since";>@since https://github.com/apache/maven-release/commit/e2006edbbb9a621d8ed3f2c745f1a9f5bb1c8ec8";>e2006ed update links (https://redirect.github.com/apache/maven-release/issues/175";>#175) https://github.com/apache/maven-release/commit/0da97a2639d6ef72481a486376661607baa91ffe";>0da97a2 use more modern I/O that does not rely on the system encoding (https://redirect.github.com/apache/maven-release/issues/174";>#174) https://github.com/apache/maven-release/commit/422ccc4d6c97a64c4f3e3fda5f2f45ac68d165a0";>422ccc4 http --> https (https://redirect.github.com/apache/maven-release/issues/177";>#177) https://github.com/apache/maven-release/commit/262254ff96f48dff92ab0af3454b8318d7c47307";>262254f grammar nits (https://redirect.github.com/apache/maven-release/issues/178";>#178) https://github.com/apache/maven-release/commit/d60bbc34d0ced1f5005c32f3b9e1d03d0b9582c9";>d60bbc3 Prefer more modern try with resources over IOUtil.close (https://redirect.github.com/apache/maven-release/issues/179";>#179) https://github.com/apache/maven-release/commit/3e077e7064a964f904e24aab8fe57232f503fd81";>3e077e7 Merge pull request https://redirect.github.com/apache/maven-release/issues/171";>#171 from apache/dependabot/maven/org.codehaus.mojo-mrm-ma... Additional commits viewable in https://github.com/apache/maven-release/compare/maven-release-3.0.0-M7...maven-release-3.0.0";>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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MSITE-942) Generated localized site content is ignored
Michael Osipov created MSITE-942:
Summary: Generated localized site content is ignored
Key: MSITE-942
URL: https://issues.apache.org/jira/browse/MSITE-942
Project: Maven Site Plugin
Issue Type: Bug
Components: localization
Affects Versions: 4.0.0-M6
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 4.0.0-M7
When localized content is included from {{generated-site}} the locale is not
taken into account, thus only the default locale is visible and the rest
disappears, e.g., {{sitemap.html}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSITE-941) sitemap.xml overwritten when multiple locales are defined
Michael Osipov created MSITE-941:
Summary: sitemap.xml overwritten when multiple locales are defined
Key: MSITE-941
URL: https://issues.apache.org/jira/browse/MSITE-941
Project: Maven Site Plugin
Issue Type: Bug
Components: localization
Affects Versions: 4.0.0-M6
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 4.0.0-M7
When more than one locale is defined the code does not properly take it into
account and overwrites then {{sitemap.xml}} which creates incorrect output at
the end.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent,
so I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
*Expected:* my snapshot project build succeeds with a snapshot parent.
*Actual:* my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
*Workaround:* disable {{failWhenParentIsSnapshot}}, but then I lose the
enforcement on the parent when I make a release of my project.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it was a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
{noformat}
[WARNING]
[WARNING] Some problems were encountered while building the effective settings
[WARNING] Unrecognised tag: 'properties' (position: START_TAG seen
...\n\t... @13:14) @ /home/peter/.m2/settings.xml, line
13, column 14
[WARNING]
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
su.pernova:assertions-parent:pom:1.1.0-SNAPSHOT
[WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must be
unique but found duplicate declaration of plugin
org.apache.maven.plugins:maven-failsafe-plugin @ su.pernova:bom:1.1.0-SNAPSHOT,
/home/peter/.m2/repository/su/pernova/bom/1.1.0-SNAPSHOT/bom-1.1.0-SNAPSHOT.pom,
line 263, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO] Inspecting build with total of 5 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 5 executions of maven-deploy-plugin replaced with
nexus-staging-maven-plugin
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] Supernova Assertions - Parent [pom]
[INFO] Supernova Assertions - Main[jar]
[INFO] Supernova Assertions - JUnit 4 [jar]
[INFO] Supernova Assertions - JUnit 5 [jar]
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 [jar]
[INFO]
[INFO] < su.pernova:assertions-parent >
[INFO] Building Supernova Assertions - Parent 1.1.0-SNAPSHOT [1/5]
[INFO] [ pom ]-
[INFO]
[INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ assertions-parent
---
[INFO]
[INFO] --- flatten-maven-plugin:1.3.0:clean (flatten-clean) @ assertions-parent
---
[INFO]
[INFO] --- maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) @ assertions-parent ---
[INFO]
[INFO] Reactor Summary for Supernova Assertions - Parent 1.1.0-SNAPSHOT:
[INFO]
[INFO] Supernova Assertions - Parent .. FAILURE [ 0.464 s]
[INFO] Supernova Assertions - Main SKIPPED
[INFO] Supernova Assertions - JUnit 4 . SKIPPED
[INFO] Supernova Assertions - JUnit 5 . SKIPPED
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.023 s
[INFO] Finished at: 2023-04-06T21:12:23+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) on project assertions-parent:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.dependency.RequireReleaseDeps
failed with message:
[ERROR] Parent Cannot be a snapshot: su.pernova:bom:pom:1.1.0-SNAPSHOT
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
swit
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent,
so I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
*Expected:* my snapshot project build succeeds with a snapshot parent.
*Actual:* my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it was a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
{noformat}
[WARNING]
[WARNING] Some problems were encountered while building the effective settings
[WARNING] Unrecognised tag: 'properties' (position: START_TAG seen
...\n\t... @13:14) @ /home/peter/.m2/settings.xml, line
13, column 14
[WARNING]
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
su.pernova:assertions-parent:pom:1.1.0-SNAPSHOT
[WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must be
unique but found duplicate declaration of plugin
org.apache.maven.plugins:maven-failsafe-plugin @ su.pernova:bom:1.1.0-SNAPSHOT,
/home/peter/.m2/repository/su/pernova/bom/1.1.0-SNAPSHOT/bom-1.1.0-SNAPSHOT.pom,
line 263, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO] Inspecting build with total of 5 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 5 executions of maven-deploy-plugin replaced with
nexus-staging-maven-plugin
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] Supernova Assertions - Parent [pom]
[INFO] Supernova Assertions - Main[jar]
[INFO] Supernova Assertions - JUnit 4 [jar]
[INFO] Supernova Assertions - JUnit 5 [jar]
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 [jar]
[INFO]
[INFO] < su.pernova:assertions-parent >
[INFO] Building Supernova Assertions - Parent 1.1.0-SNAPSHOT [1/5]
[INFO] [ pom ]-
[INFO]
[INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ assertions-parent
---
[INFO]
[INFO] --- flatten-maven-plugin:1.3.0:clean (flatten-clean) @ assertions-parent
---
[INFO]
[INFO] --- maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) @ assertions-parent ---
[INFO]
[INFO] Reactor Summary for Supernova Assertions - Parent 1.1.0-SNAPSHOT:
[INFO]
[INFO] Supernova Assertions - Parent .. FAILURE [ 0.464 s]
[INFO] Supernova Assertions - Main SKIPPED
[INFO] Supernova Assertions - JUnit 4 . SKIPPED
[INFO] Supernova Assertions - JUnit 5 . SKIPPED
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.023 s
[INFO] Finished at: 2023-04-06T21:12:23+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) on project assertions-parent:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.dependency.RequireReleaseDeps
failed with message:
[ERROR] Parent Cannot be a snapshot: su.pernova:bom:pom:1.1.0-SNAPSHOT
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and pos
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent,
so I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
*Expected:* my snapshot project build succeeds with a snapshot parent.
*Actual:* my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it was a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
{noformat}
[WARNING]
[WARNING] Some problems were encountered while building the effective settings
[WARNING] Unrecognised tag: 'properties' (position: START_TAG seen
...\n\t... @13:14) @ /home/peter/.m2/settings.xml, line
13, column 14
[WARNING]
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
su.pernova:assertions-parent:pom:1.1.0-SNAPSHOT
[WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must be
unique but found duplicate declaration of plugin
org.apache.maven.plugins:maven-failsafe-plugin @ su.pernova:bom:1.1.0-SNAPSHOT,
/home/peter/.m2/repository/su/pernova/bom/1.1.0-SNAPSHOT/bom-1.1.0-SNAPSHOT.pom,
line 263, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO] Inspecting build with total of 5 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 5 executions of maven-deploy-plugin replaced with
nexus-staging-maven-plugin
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] Supernova Assertions - Parent [pom]
[INFO] Supernova Assertions - Main[jar]
[INFO] Supernova Assertions - JUnit 4 [jar]
[INFO] Supernova Assertions - JUnit 5 [jar]
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 [jar]
[INFO]
[INFO] < su.pernova:assertions-parent >
[INFO] Building Supernova Assertions - Parent 1.1.0-SNAPSHOT [1/5]
[INFO] [ pom ]-
[INFO]
[INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ assertions-parent
---
[INFO]
[INFO] --- flatten-maven-plugin:1.3.0:clean (flatten-clean) @ assertions-parent
---
[INFO]
[INFO] --- maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) @ assertions-parent ---
[INFO]
[INFO] Reactor Summary for Supernova Assertions - Parent 1.1.0-SNAPSHOT:
[INFO]
[INFO] Supernova Assertions - Parent .. FAILURE [ 0.464 s]
[INFO] Supernova Assertions - Main SKIPPED
[INFO] Supernova Assertions - JUnit 4 . SKIPPED
[INFO] Supernova Assertions - JUnit 5 . SKIPPED
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.023 s
[INFO] Finished at: 2023-04-06T21:12:23+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) on project assertions-parent:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.dependency.RequireReleaseDeps
failed with message:
[ERROR] Parent Cannot be a snapshot: su.pernova:bom:pom:1.1.0-SNAPSHOT
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and pos
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent,
so I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
*Expected:* my snapshot project build succeeds with a snapshot parent.
*Actual:* my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
{noformat}
[WARNING]
[WARNING] Some problems were encountered while building the effective settings
[WARNING] Unrecognised tag: 'properties' (position: START_TAG seen
...\n\t... @13:14) @ /home/peter/.m2/settings.xml, line
13, column 14
[WARNING]
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
su.pernova:assertions-parent:pom:1.1.0-SNAPSHOT
[WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must be
unique but found duplicate declaration of plugin
org.apache.maven.plugins:maven-failsafe-plugin @ su.pernova:bom:1.1.0-SNAPSHOT,
/home/peter/.m2/repository/su/pernova/bom/1.1.0-SNAPSHOT/bom-1.1.0-SNAPSHOT.pom,
line 263, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO] Inspecting build with total of 5 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 5 executions of maven-deploy-plugin replaced with
nexus-staging-maven-plugin
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] Supernova Assertions - Parent [pom]
[INFO] Supernova Assertions - Main[jar]
[INFO] Supernova Assertions - JUnit 4 [jar]
[INFO] Supernova Assertions - JUnit 5 [jar]
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 [jar]
[INFO]
[INFO] < su.pernova:assertions-parent >
[INFO] Building Supernova Assertions - Parent 1.1.0-SNAPSHOT [1/5]
[INFO] [ pom ]-
[INFO]
[INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ assertions-parent
---
[INFO]
[INFO] --- flatten-maven-plugin:1.3.0:clean (flatten-clean) @ assertions-parent
---
[INFO]
[INFO] --- maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) @ assertions-parent ---
[INFO]
[INFO] Reactor Summary for Supernova Assertions - Parent 1.1.0-SNAPSHOT:
[INFO]
[INFO] Supernova Assertions - Parent .. FAILURE [ 0.464 s]
[INFO] Supernova Assertions - Main SKIPPED
[INFO] Supernova Assertions - JUnit 4 . SKIPPED
[INFO] Supernova Assertions - JUnit 5 . SKIPPED
[INFO] Supernova Assertions - JUnit 4 + JUnit 5 ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.023 s
[INFO] Finished at: 2023-04-06T21:12:23+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
(enforce-no-snapshots-in-releases) on project assertions-parent:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.dependency.RequireReleaseDeps
failed with message:
[ERROR] Parent Cannot be a snapshot: su.pernova:bom:pom:1.1.0-SNAPSHOT
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and poss
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent,
so I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
*Expected:* my snapshot project build succeeds with a snapshot parent.
*Actual:* my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
was:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent,
so I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent,
> so I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> *Expected:* my snapshot project build succeeds with a snapshot parent.
> *Actual:* my snapshot project build _fails_ with a snapshot parent, despite
> {{onlyWhenRelease=true}}.
> I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
> into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it is a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent,
so I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
was:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent,
> so I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> Expected: my snapshot project build succeeds with a snapshot parent.
> Actual: my snapshot project build _fails_ with a snapshot parent, despite
> {{onlyWhenRelease=true}}.
> I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
> into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it is a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
was:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent.
> So I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> Expected: my snapshot project build succeeds with a snapshot parent.
> Actual: my snapshot project build _fails_ with a snapshot parent, despite
> {{onlyWhenRelease=true}}.
> I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
> into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it is a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelease}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
was:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite the
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take the
{{onlyWhenRelease}} into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent.
> So I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> Expected: my snapshot project build succeeds with a snapshot parent.
> Actual: my snapshot project build _fails_ with a snapshot parent, despite
> {{onlyWhenRelease=true}}.
> I suspect that {{failWhenParentIsSnapshot}} does not take {{onlyWhenRelease}}
> into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it is a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
Peter De Maeyer created MENFORCER-477:
-
Summary: failWhenParentIsSnapshot does not respect onlyWhenRelease
Key: MENFORCER-477
URL: https://issues.apache.org/jira/browse/MENFORCER-477
Project: Maven Enforcer Plugin
Issue Type: Bug
Affects Versions: 3.2.1
Reporter: Peter De Maeyer
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use{{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite the
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take the
{{onlyWhenRelease}} into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MENFORCER-477) failWhenParentIsSnapshot does not respect onlyWhenRelease
[
https://issues.apache.org/jira/browse/MENFORCER-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MENFORCER-477:
--
Description:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use {{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite the
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take the
{{onlyWhenRelease}} into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
was:
I have a snapshot project that has a snapshot parent.
At release time, I want to use the enforcer plugin to make sure the release
version of my project only depends on release versions, including the parent.
So I use{{failWhenParentIsSnapshot=true}}.
For snapshot versions of my project, I want to _allow_ snapshot dependencies
including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
enforcer for snapshot versions.
Expected: my snapshot project build succeeds with a snapshot parent.
Actual: my snapshot project build _fails_ with a snapshot parent, despite the
{{onlyWhenRelease=true}}.
I suspect that {{failWhenParentIsSnapshot}} does not take the
{{onlyWhenRelease}} into account.
The intuitive fix for me would be that the combination of both options behaves
as expected.
I imagine that maybe it is a design choice to keep both options completely
independent of each other, so an acceptable alternative for me would be to
introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
similar to {{onlyWhenRelease}} but applies to the parent only.
> failWhenParentIsSnapshot does not respect onlyWhenRelease
> -
>
> Key: MENFORCER-477
> URL: https://issues.apache.org/jira/browse/MENFORCER-477
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Peter De Maeyer
>Priority: Major
>
> I have a snapshot project that has a snapshot parent.
> At release time, I want to use the enforcer plugin to make sure the release
> version of my project only depends on release versions, including the parent.
> So I use {{failWhenParentIsSnapshot=true}}.
> For snapshot versions of my project, I want to _allow_ snapshot dependencies
> including snapshot parent, so I use {{onlyWhenRelease=true}} to disable the
> enforcer for snapshot versions.
> Expected: my snapshot project build succeeds with a snapshot parent.
> Actual: my snapshot project build _fails_ with a snapshot parent, despite the
> {{onlyWhenRelease=true}}.
> I suspect that {{failWhenParentIsSnapshot}} does not take the
> {{onlyWhenRelease}} into account.
> The intuitive fix for me would be that the combination of both options
> behaves as expected.
> I imagine that maybe it is a design choice to keep both options completely
> independent of each other, so an acceptable alternative for me would be to
> introduce yet another option, e.g. {{onlyWhenParentIsRelase}} that behaves
> similar to {{onlyWhenRelease}} but applies to the parent only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPOM-396) upgrade Maven Assembly Plugin to 3.5.0
[ https://issues.apache.org/jira/browse/MPOM-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MPOM-396. Assignee: Slawomir Jaranowski Resolution: Fixed > upgrade Maven Assembly Plugin to 3.5.0 > -- > > Key: MPOM-396 > URL: https://issues.apache.org/jira/browse/MPOM-396 > Project: Maven POMs > Issue Type: Task > Components: asf >Affects Versions: ASF-29 >Reporter: Herve Boutemy >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-30 > > > to benefit from MASSEMBLY-941 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-apache-parent] slawekjaranowski merged pull request #131: [MPOM-396] Bump maven-assembly-plugin from 3.4.2 to 3.5.0
slawekjaranowski merged PR #131: URL: https://github.com/apache/maven-apache-parent/pull/131 -- 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] (MPOM-404) Bump maven-scm-plugin from 1.13.0 to 2.0.0
Slawomir Jaranowski created MPOM-404: Summary: Bump maven-scm-plugin from 1.13.0 to 2.0.0 Key: MPOM-404 URL: https://issues.apache.org/jira/browse/MPOM-404 Project: Maven POMs Issue Type: Dependency upgrade Components: asf Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: ASF-30 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPOM-403) Bump maven-enforcer-plugin from 3.1.0 to 3.3.0
Slawomir Jaranowski created MPOM-403: Summary: Bump maven-enforcer-plugin from 3.1.0 to 3.3.0 Key: MPOM-403 URL: https://issues.apache.org/jira/browse/MPOM-403 Project: Maven POMs Issue Type: Dependency upgrade Components: asf Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: ASF-30 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPOM-402) Bump maven-javadoc-plugin from 3.4.1 to 3.5.0
[ https://issues.apache.org/jira/browse/MPOM-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MPOM-402. Resolution: Fixed > Bump maven-javadoc-plugin from 3.4.1 to 3.5.0 > - > > Key: MPOM-402 > URL: https://issues.apache.org/jira/browse/MPOM-402 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-30 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-apache-parent] slawekjaranowski merged pull request #130: [MPOM-402] Bump maven-javadoc-plugin from 3.4.1 to 3.5.0
slawekjaranowski merged PR #130: URL: https://github.com/apache/maven-apache-parent/pull/130 -- 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] (MPOM-402) Bump maven-javadoc-plugin from 3.4.1 to 3.5.0
Slawomir Jaranowski created MPOM-402: Summary: Bump maven-javadoc-plugin from 3.4.1 to 3.5.0 Key: MPOM-402 URL: https://issues.apache.org/jira/browse/MPOM-402 Project: Maven POMs Issue Type: Dependency upgrade Components: asf Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: ASF-30 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPOM-395) upgrade Maven Compiler Plugin to 3.11.0
[ https://issues.apache.org/jira/browse/MPOM-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MPOM-395. Assignee: Slawomir Jaranowski Resolution: Fixed > upgrade Maven Compiler Plugin to 3.11.0 > --- > > Key: MPOM-395 > URL: https://issues.apache.org/jira/browse/MPOM-395 > Project: Maven POMs > Issue Type: Task > Components: asf >Affects Versions: ASF-29 >Reporter: Herve Boutemy >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-30 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-apache-parent] slawekjaranowski merged pull request #133: [MPOM-395] Bump maven-compiler-plugin from 3.10.1 to 3.11.0
slawekjaranowski merged PR #133: URL: https://github.com/apache/maven-apache-parent/pull/133 -- 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-7713) Drop option legacy-local-repository
[ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709475#comment-17709475 ] ASF GitHub Bot commented on MNG-7713: - anatolVasin commented on PR #1018: URL: https://github.com/apache/maven/pull/1018#issuecomment-1499458903 > resolver option Hello @cstamas , could you clarify what particular resolver option do you mean? Thanks. Such capabilities really requires for emulate closed environments without access to Maven Central in tests. > Drop option legacy-local-repository > --- > > Key: MNG-7713 > URL: https://issues.apache.org/jira/browse/MNG-7713 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.1, 4.0.0-alpha-5, 4.0.0 > > > The option offers several ways to make Maven 3 use Maven 2 legacy local > repository, the option help text states: "Use Maven 2 Legacy Local Repository > behaviour, ie no use of _remote.repositories. Can also be activated by using > -Dmaven.legacyLocalRepo=true". > Let's drop this option, as there is no need to make Maven 3.9 support Maven 2 > local repository, that is (should be) transient anyway. Also, if really > needed, there IS a resolver configuration that offers somewhat similar > semantics, but Maven CLI should NOT advertise Maven 2 backward compatibility > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] anatolVasin commented on pull request #1018: [maven-3.9.x] [MNG-7713] Drop legacy-local-repository option
anatolVasin commented on PR #1018: URL: https://github.com/apache/maven/pull/1018#issuecomment-1499458903 > resolver option Hello @cstamas , could you clarify what particular resolver option do you mean? Thanks. Such capabilities really requires for emulate closed environments without access to Maven Central in tests. -- 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-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709474#comment-17709474
]
Michael Osipov commented on MNG-7705:
-
Sure, take your time. As soon as we can narrow it down [~cstamas] and can
evaluate the ideas we have.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Major
> Attachments: 2023-02-28_failure.zip, MNG-7705-2023-02-27.zip,
> MNG-7705-2023-03-07.zip, MNG-7705.zip, MNG-7705_strace_2023-02-27.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar-1.gz, failed_plan-377290782-JOB1-15.zip,
> maven-resolver-util-1.9.6-SNAPSHOT.jar, xaa-1.xz, xab-1.xz, xac-1.xz, xad-1.xz
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.depend
[jira] [Comment Edited] (MNG-7131) maven.config doesn't handle arguments with spaces in them
[
https://issues.apache.org/jira/browse/MNG-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709465#comment-17709465
]
Michael Osipov edited comment on MNG-7131 at 4/6/23 5:31 PM:
-
Please look at the commit message it contains a reasonable explanation for the
fix. The approach was wrong from begin with. Many of our components reimplement
shell functions which is wrong.
At the end the formula is simple: one argument == one line. No ambiguity.
Note that the previous behavior wad never formally specified.
was (Author: michael-o):
Please look at the commit message it contains a reasonable explanation for the
fix. The approach was wrong from begin with. Many of our components reimplement
shell functions which is wrong.
At the end the formula is simple: one argument == one line. No ambiguity.
> maven.config doesn't handle arguments with spaces in them
> -
>
> Key: MNG-7131
> URL: https://issues.apache.org/jira/browse/MNG-7131
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.3
>Reporter: Stefan Oehme
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-2, 4.0.0
>
>
> I tried putting a path with a space in the maven.config like so:
> {code:java}
> "-Dmy.path=/some/path with/a/space"
> {code}
> When asking for the my.path property inside Maven, I get the path with a
> trailing quote
> {code:java}
> /some/path with/a/space"
> {code}
> The file is parsed by [splitting it by
> whitespace|https://github.com/apache/maven/blob/c3cf29438e3d65d6ee5c5726f8611af99d9a649a/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L386].
> I suggest replacing that code with the much better
> [CommandLineUtils.translateCommandline(argLine)|https://github.com/codehaus-plexus/plexus-utils/blob/85a4a3c534752919dd97d757d4ef0fdb6d40eb8c/src/main/java/org/codehaus/plexus/util/cli/CommandLineUtils.java#L412]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7131) maven.config doesn't handle arguments with spaces in them
[
https://issues.apache.org/jira/browse/MNG-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709465#comment-17709465
]
Michael Osipov edited comment on MNG-7131 at 4/6/23 5:30 PM:
-
Please look at the commit message it contains a reasonable explanation for the
fix. The approach was wrong from begin with. Many of our components reimplement
shell functions which is wrong.
At the end the formula is simple: one argument == one line. No ambiguity.
was (Author: michael-o):
Please look at the commit message it contains a reasonable explanation for the
fix. The approach was wrong from begin with. Many of our components reimplement
shell functions which is wrong.
> maven.config doesn't handle arguments with spaces in them
> -
>
> Key: MNG-7131
> URL: https://issues.apache.org/jira/browse/MNG-7131
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.3
>Reporter: Stefan Oehme
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-2, 4.0.0
>
>
> I tried putting a path with a space in the maven.config like so:
> {code:java}
> "-Dmy.path=/some/path with/a/space"
> {code}
> When asking for the my.path property inside Maven, I get the path with a
> trailing quote
> {code:java}
> /some/path with/a/space"
> {code}
> The file is parsed by [splitting it by
> whitespace|https://github.com/apache/maven/blob/c3cf29438e3d65d6ee5c5726f8611af99d9a649a/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L386].
> I suggest replacing that code with the much better
> [CommandLineUtils.translateCommandline(argLine)|https://github.com/codehaus-plexus/plexus-utils/blob/85a4a3c534752919dd97d757d4ef0fdb6d40eb8c/src/main/java/org/codehaus/plexus/util/cli/CommandLineUtils.java#L412]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7131) maven.config doesn't handle arguments with spaces in them
[
https://issues.apache.org/jira/browse/MNG-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709465#comment-17709465
]
Michael Osipov commented on MNG-7131:
-
Please look at the commit message it contains a reasonable explanation for the
fix. The approach was wrong from begin with. Many of our components reimplement
shell functions which is wrong.
> maven.config doesn't handle arguments with spaces in them
> -
>
> Key: MNG-7131
> URL: https://issues.apache.org/jira/browse/MNG-7131
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.3
>Reporter: Stefan Oehme
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-2, 4.0.0
>
>
> I tried putting a path with a space in the maven.config like so:
> {code:java}
> "-Dmy.path=/some/path with/a/space"
> {code}
> When asking for the my.path property inside Maven, I get the path with a
> trailing quote
> {code:java}
> /some/path with/a/space"
> {code}
> The file is parsed by [splitting it by
> whitespace|https://github.com/apache/maven/blob/c3cf29438e3d65d6ee5c5726f8611af99d9a649a/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L386].
> I suggest replacing that code with the much better
> [CommandLineUtils.translateCommandline(argLine)|https://github.com/codehaus-plexus/plexus-utils/blob/85a4a3c534752919dd97d757d4ef0fdb6d40eb8c/src/main/java/org/codehaus/plexus/util/cli/CommandLineUtils.java#L412]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7131) maven.config doesn't handle arguments with spaces in them
[
https://issues.apache.org/jira/browse/MNG-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709462#comment-17709462
]
Jeff Pierson commented on MNG-7131:
---
[~michael-o], ok so this is an expected breaking change? I couldn't find much
details in documentation or other discussion other than the change to put
arguments on separate lines. Is the workaround that I found the preferred one
because like the original poster I did try quoting the argument value such as
below which also didn't work.
-s ".mvn/settings.xml"
and
"-s .mvn/settings.xml"
At the same time I see that this issue which is about the allowing spaces with
quoting behavior is marked fixed in previous versions. So I'm now wondering
that if {{-s .mvn/settings.xml}} is not a regression from Maven 3 and an
intentional breaking change on whether my attempt to quote the value as {{"-s
.mvn/settings.xml"}} is a regression somewhere in the Maven 4 Alphas. Is there
somewhere that explains this behavior and the breaking changes so that I can
plan next steps for my projects which will adopt Maven 4 or help to open a new
issue?
> maven.config doesn't handle arguments with spaces in them
> -
>
> Key: MNG-7131
> URL: https://issues.apache.org/jira/browse/MNG-7131
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.3
>Reporter: Stefan Oehme
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-2, 4.0.0
>
>
> I tried putting a path with a space in the maven.config like so:
> {code:java}
> "-Dmy.path=/some/path with/a/space"
> {code}
> When asking for the my.path property inside Maven, I get the path with a
> trailing quote
> {code:java}
> /some/path with/a/space"
> {code}
> The file is parsed by [splitting it by
> whitespace|https://github.com/apache/maven/blob/c3cf29438e3d65d6ee5c5726f8611af99d9a649a/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L386].
> I suggest replacing that code with the much better
> [CommandLineUtils.translateCommandline(argLine)|https://github.com/codehaus-plexus/plexus-utils/blob/85a4a3c534752919dd97d757d4ef0fdb6d40eb8c/src/main/java/org/codehaus/plexus/util/cli/CommandLineUtils.java#L412]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7131) maven.config doesn't handle arguments with spaces in them
[
https://issues.apache.org/jira/browse/MNG-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709460#comment-17709460
]
Michael Osipov commented on MNG-7131:
-
That is expected.
> maven.config doesn't handle arguments with spaces in them
> -
>
> Key: MNG-7131
> URL: https://issues.apache.org/jira/browse/MNG-7131
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.3
>Reporter: Stefan Oehme
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-2, 4.0.0
>
>
> I tried putting a path with a space in the maven.config like so:
> {code:java}
> "-Dmy.path=/some/path with/a/space"
> {code}
> When asking for the my.path property inside Maven, I get the path with a
> trailing quote
> {code:java}
> /some/path with/a/space"
> {code}
> The file is parsed by [splitting it by
> whitespace|https://github.com/apache/maven/blob/c3cf29438e3d65d6ee5c5726f8611af99d9a649a/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L386].
> I suggest replacing that code with the much better
> [CommandLineUtils.translateCommandline(argLine)|https://github.com/codehaus-plexus/plexus-utils/blob/85a4a3c534752919dd97d757d4ef0fdb6d40eb8c/src/main/java/org/codehaus/plexus/util/cli/CommandLineUtils.java#L412]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7131) maven.config doesn't handle arguments with spaces in them
[
https://issues.apache.org/jira/browse/MNG-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709458#comment-17709458
]
Jeff Pierson commented on MNG-7131:
---
I'm seeing a similar issue in Alpha 5 with an existing {{maven.config}} file
that I had used back with Maven 3. The content of the file is as shown below.
{{-s .mvn/settings.xml}}
When I run mvn clean install with Maven 4 I get the following error:
{{[ERROR] Error executing Maven.}}
{{[ERROR] The specified user settings file does not exist:
C:\projects\online-application-service\ .mvn\settings.xml}}
I noticed that there was a space before ".mvn" in the path so I removed it from
maven.config in my .mvn folder and it worked.
maven.conf working in Maven 4 Alpha 5 (notice the space removed after {{-s.}}
{{-s.mvn/settings.xml}}
> maven.config doesn't handle arguments with spaces in them
> -
>
> Key: MNG-7131
> URL: https://issues.apache.org/jira/browse/MNG-7131
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.3
>Reporter: Stefan Oehme
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-2, 4.0.0
>
>
> I tried putting a path with a space in the maven.config like so:
> {code:java}
> "-Dmy.path=/some/path with/a/space"
> {code}
> When asking for the my.path property inside Maven, I get the path with a
> trailing quote
> {code:java}
> /some/path with/a/space"
> {code}
> The file is parsed by [splitting it by
> whitespace|https://github.com/apache/maven/blob/c3cf29438e3d65d6ee5c5726f8611af99d9a649a/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L386].
> I suggest replacing that code with the much better
> [CommandLineUtils.translateCommandline(argLine)|https://github.com/codehaus-plexus/plexus-utils/blob/85a4a3c534752919dd97d757d4ef0fdb6d40eb8c/src/main/java/org/codehaus/plexus/util/cli/CommandLineUtils.java#L412]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709457#comment-17709457
]
Jim Sellers commented on MNG-7705:
--
[~michael-o] No, I've not had a lot of time to get back to this. I've still got
a dev env using the 3.9.x stream for evaluation, but I'm holding everything
else back to 3.8.x for now.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Major
> Attachments: 2023-02-28_failure.zip, MNG-7705-2023-02-27.zip,
> MNG-7705-2023-03-07.zip, MNG-7705.zip, MNG-7705_strace_2023-02-27.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar-1.gz, failed_plan-377290782-JOB1-15.zip,
> maven-resolver-util-1.9.6-SNAPSHOT.jar, xaa-1.xz, xab-1.xz, xac-1.xz, xad-1.xz
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractD
[GitHub] [maven-mvnd] oehme commented on pull request #834: Fix PluginDescriptorCache
oehme commented on PR #834: URL: https://github.com/apache/maven-mvnd/pull/834#issuecomment-1499231154 Ah yes, that makes sense. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet commented on pull request #834: Fix PluginDescriptorCache
gnodet commented on PR #834: URL: https://github.com/apache/maven-mvnd/pull/834#issuecomment-1499229653 > I wonder why we're extending the default class at all? Are there direct references to the default class in Maven core? To avoid duplicating the whole class, including the `CacheKey` inner class ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] elharo opened a new pull request, #123: Remove vestigial comment
elharo opened a new pull request, #123: URL: https://github.com/apache/maven-pmd-plugin/pull/123 as we now require Java 8 -- 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] (MPMD-366) Update parent pom to 39
[ https://issues.apache.org/jira/browse/MPMD-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MPMD-366. -- > Update parent pom to 39 > --- > > Key: MPMD-366 > URL: https://issues.apache.org/jira/browse/MPMD-366 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-366) Update parent pom to 39
[ https://issues.apache.org/jira/browse/MPMD-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MPMD-366. Resolution: Fixed > Update parent pom to 39 > --- > > Key: MPMD-366 > URL: https://issues.apache.org/jira/browse/MPMD-366 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-pmd-plugin] elharo merged pull request #118: [MPMD-366] Update parent pom to 39
elharo merged PR #118: URL: https://github.com/apache/maven-pmd-plugin/pull/118 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] oehme commented on pull request #834: Fix PluginDescriptorCache
oehme commented on PR #834: URL: https://github.com/apache/maven-mvnd/pull/834#issuecomment-1499102045 I wonder why we're extending the default class at all? Are there direct references to the default class in Maven core? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet opened a new issue, #835: Consider reverting to slf4j simple logger for the actual logging to the terminal
gnodet opened a new issue, #835: URL: https://github.com/apache/maven-mvnd/issues/835 This would more closely align with stock maven -- 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
[GitHub] [maven] gnodet opened a new pull request, #1081: Simplify logger creation leveraging Map.computeIfAbsent
gnodet opened a new pull request, #1081: URL: https://github.com/apache/maven/pull/1081 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/MNG) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. - [ ] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`. Best practice is to use the JIRA issue title in both 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 verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] oehme opened a new pull request, #834: Fix PluginDescriptorCache
oehme opened a new pull request, #834: URL: https://github.com/apache/maven-mvnd/pull/834 The second get-method wasn't actually overloaded, but had a different signature than the superclass. This resulted in the superclass cache being filled and never cleared, even when flush is called. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet merged pull request #830: Add MVND_NO_MODEL_CACHE support to mvn39
gnodet merged PR #830: URL: https://github.com/apache/maven-mvnd/pull/830 -- 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-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709365#comment-17709365
]
Michael Osipov commented on MNG-7705:
-
[~sellersj], were you able to get Redis up and running meanwhile?
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Major
> Attachments: 2023-02-28_failure.zip, MNG-7705-2023-02-27.zip,
> MNG-7705-2023-03-07.zip, MNG-7705.zip, MNG-7705_strace_2023-02-27.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar-1.gz, failed_plan-377290782-JOB1-15.zip,
> maven-resolver-util-1.9.6-SNAPSHOT.jar, xaa-1.xz, xab-1.xz, xac-1.xz, xad-1.xz
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDepende
[jira] [Updated] (MNG-7756) The degree of concurrency does not support "2." as a factor
[
https://issues.apache.org/jira/browse/MNG-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7756:
Fix Version/s: 3.8.x-candidate
3.9.x-candidate
> The degree of concurrency does not support "2." as a factor
> ---
>
> Key: MNG-7756
> URL: https://issues.apache.org/jira/browse/MNG-7756
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 3.8.x-candidate, 3.9.x-candidate, 4.0.0-alpha-6, 4.0.0
>
>
> The {{2.}} syntax is supported by {{Float.parseFloat()}} and there's no
> reason why that particular syntax should be rejected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-pmd-plugin] elharo merged pull request #122: [MPMD-369] Make integration tests robust against system encoding
elharo merged PR #122: URL: https://github.com/apache/maven-pmd-plugin/pull/122 -- 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-7756) The degree of concurrency does not support "2." as a factor
[
https://issues.apache.org/jira/browse/MNG-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709315#comment-17709315
]
Michael Osipov commented on MNG-7756:
-
I'd say that must be at least be backported to 3.9.x for consistency reasons.
Commons Lang isn't necessary anymore here, right?
> The degree of concurrency does not support "2." as a factor
> ---
>
> Key: MNG-7756
> URL: https://issues.apache.org/jira/browse/MNG-7756
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-alpha-6, 4.0.0
>
>
> The {{2.}} syntax is supported by {{Float.parseFloat()}} and there's no
> reason why that particular syntax should be rejected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7756) The degree of concurrency does not support "2." as a factor
[
https://issues.apache.org/jira/browse/MNG-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7756:
Fix Version/s: 4.0.0
> The degree of concurrency does not support "2." as a factor
> ---
>
> Key: MNG-7756
> URL: https://issues.apache.org/jira/browse/MNG-7756
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-alpha-6, 4.0.0
>
>
> The {{2.}} syntax is supported by {{Float.parseFloat()}} and there's no
> reason why that particular syntax should be rejected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MCOMPILER-533) Output an error when --release option is used together with --source or --target
[
https://issues.apache.org/jira/browse/MCOMPILER-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arend v. Reinersdorff updated MCOMPILER-533:
Description:
javac outputs an error when the --release option is used together with the
--source or --target option. See
[https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-release]
For example:
{{javac --release 17 --target 17 ...}}
Will fail with this error:
{{error: option --target cannot be used together with --release}}
This is nice because it informs the user of misconfiguration and enforces the
use of only \-\-release or only \-\-source/--target.
Unfortunately, the error is lost when compiling with Maven. Maven uses the
release option and silently ignores source and target. Users don't notice when
they unnecessarily set both. See for example
[https://github.com/spring-projects/spring-boot/pull/34761]
For example:
{{}}
{{ org.apache.maven.plugins}}
{{ maven-compiler-plugin}}
{{ 3.11.0}}
{{ }}
{{ 17}}
{{ 17}}
{{ 17}}
{{ }}
{{}}
Compiles using the release option without any error or warning.
It would be nice to restore the error from javac in Maven, or output a similar
one.
The problem I see is that Maven uses default values for source and target. When
the user sets only the release option, no error or warning should be caused
because of the default values for source and target.
was:
javac outputs an error when the --release option is used together with the
--source or --target option. See
[https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-release]
For example:
{{javac --release 17 --target 17 ...}}
Will fail with this error:
{{error: option --target cannot be used together with --release}}
This is nice because it informs the user of misconfiguration and enforces the
use of only --release or only --source/--target.
Unfortunately, the error is lost when compiling with Maven. Maven uses the
release option and silently ignores source and target. Users don't notice when
they unnecessarily set both. See for example
[https://github.com/spring-projects/spring-boot/pull/34761]
For example:
{{}}
{{ org.apache.maven.plugins}}
{{ maven-compiler-plugin}}
{{ 3.11.0}}
{{ }}
{{ 17}}
{{ 17}}
{{ 17}}
{{ }}
{{}}
Compiles using the release option without any error or warning.
It would be nice to restore the error from javac in Maven, or output a similar
one.
The problem I see is that Maven uses default values for source and target. When
the user sets only the release option, no error or warning should be caused
because of the default values for source and target.
> Output an error when --release option is used together with --source or
> --target
>
>
> Key: MCOMPILER-533
> URL: https://issues.apache.org/jira/browse/MCOMPILER-533
> Project: Maven Compiler Plugin
> Issue Type: Improvement
>Affects Versions: 3.11.0
>Reporter: Arend v. Reinersdorff
>Priority: Major
>
> javac outputs an error when the --release option is used together with the
> --source or --target option. See
> [https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-release]
> For example:
> {{javac --release 17 --target 17 ...}}
> Will fail with this error:
> {{error: option --target cannot be used together with --release}}
> This is nice because it informs the user of misconfiguration and enforces the
> use of only \-\-release or only \-\-source/--target.
> Unfortunately, the error is lost when compiling with Maven. Maven uses the
> release option and silently ignores source and target. Users don't notice
> when they unnecessarily set both. See for example
> [https://github.com/spring-projects/spring-boot/pull/34761]
> For example:
> {{}}
> {{ org.apache.maven.plugins}}
> {{ maven-compiler-plugin}}
> {{ 3.11.0}}
> {{ }}
> {{ 17}}
> {{ 17}}
> {{ 17}}
> {{ }}
> {{}}
> Compiles using the release option without any error or warning.
> It would be nice to restore the error from javac in Maven, or output a
> similar one.
> The problem I see is that Maven uses default values for source and target.
> When the user sets only the release option, no error or warning should be
> caused because of the default values for source and target.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MCOMPILER-533) Output an error when --release option is used together with --source or --target
Arend v. Reinersdorff created MCOMPILER-533:
---
Summary: Output an error when --release option is used together
with --source or --target
Key: MCOMPILER-533
URL: https://issues.apache.org/jira/browse/MCOMPILER-533
Project: Maven Compiler Plugin
Issue Type: Improvement
Affects Versions: 3.11.0
Reporter: Arend v. Reinersdorff
javac outputs an error when the --release option is used together with the
--source or --target option. See
[https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-release]
For example:
{{javac --release 17 --target 17 ...}}
Will fail with this error:
{{error: option --target cannot be used together with --release}}
This is nice because it informs the user of misconfiguration and enforces the
use of only --release or only --source/--target.
Unfortunately, the error is lost when compiling with Maven. Maven uses the
release option and silently ignores source and target. Users don't notice when
they unnecessarily set both. See for example
[https://github.com/spring-projects/spring-boot/pull/34761]
For example:
{{}}
{{ org.apache.maven.plugins}}
{{ maven-compiler-plugin}}
{{ 3.11.0}}
{{ }}
{{ 17}}
{{ 17}}
{{ 17}}
{{ }}
{{}}
Compiles using the release option without any error or warning.
It would be nice to restore the error from javac in Maven, or output a similar
one.
The problem I see is that Maven uses default values for source and target. When
the user sets only the release option, no error or warning should be caused
because of the default values for source and target.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-6825) Cleaning Up dependencies plexus-utils/maven-shared-utils/commons-lang3/commons-io
[
https://issues.apache.org/jira/browse/MNG-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-6825.
Assignee: Guillaume Nodet (was: Karl Heinz Marbaise)
Resolution: Fixed
I think we should close this issue as fixed with the commits on maven-resolver
and maven-core. Other projects deserve their own issues.
> Cleaning Up dependencies
> plexus-utils/maven-shared-utils/commons-lang3/commons-io
> -
>
> Key: MNG-6825
> URL: https://issues.apache.org/jira/browse/MNG-6825
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.6.3
>Reporter: Karl Heinz Marbaise
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-alpha-6
>
>
> Experiment to see if we can get rid of commons-lang3 dependency.
> * Identified code duplication between:
> ** {{org.apache.commons.lang3.StringUtils}} from {{commons-lang3}} (501879
> Bytes commons-lang3-3.8.1.jar)
> ** {{org.codehaus.plexus.util.StringUtil}} from {{plexus-utils}} (261801
> Bytes plexus-utils-3.2.1.jar)
> ** {{org.apache.maven.shared.utils}} from {{maven-shared-utils}} (166562
> Bytes maven-shared-utils-3.2.1.jar)
> ** We should replace the self implemented with
> {{org.codehaus.plexus.util.StringUtil}}. or with {{maven-shared-utils}}
> * {{commons-io}} usage by {{maven-shared-utils}} (208700 Bytes
> commons-io-2.5.jar)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-6825) Cleaning Up dependencies plexus-utils/maven-shared-utils/commons-lang3/commons-io
[
https://issues.apache.org/jira/browse/MNG-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-6825:
-
Fix Version/s: 4.0.0-alpha-6
(was: 4.0.x-candidate)
> Cleaning Up dependencies
> plexus-utils/maven-shared-utils/commons-lang3/commons-io
> -
>
> Key: MNG-6825
> URL: https://issues.apache.org/jira/browse/MNG-6825
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.6.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0-alpha-6
>
>
> Experiment to see if we can get rid of commons-lang3 dependency.
> * Identified code duplication between:
> ** {{org.apache.commons.lang3.StringUtils}} from {{commons-lang3}} (501879
> Bytes commons-lang3-3.8.1.jar)
> ** {{org.codehaus.plexus.util.StringUtil}} from {{plexus-utils}} (261801
> Bytes plexus-utils-3.2.1.jar)
> ** {{org.apache.maven.shared.utils}} from {{maven-shared-utils}} (166562
> Bytes maven-shared-utils-3.2.1.jar)
> ** We should replace the self implemented with
> {{org.codehaus.plexus.util.StringUtil}}. or with {{maven-shared-utils}}
> * {{commons-io}} usage by {{maven-shared-utils}} (208700 Bytes
> commons-io-2.5.jar)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-7756) The degree of concurrency does not support "2." as a factor
[
https://issues.apache.org/jira/browse/MNG-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-7756.
Resolution: Fixed
https://github.com/apache/maven/commit/26056b9b20a402bd0ab0b4461d97b9ceeac7bbdc
> The degree of concurrency does not support "2." as a factor
> ---
>
> Key: MNG-7756
> URL: https://issues.apache.org/jira/browse/MNG-7756
> Project: Maven
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-alpha-6
>
>
> The {{2.}} syntax is supported by {{Float.parseFloat()}} and there's no
> reason why that particular syntax should be rejected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-mvnd] gnodet merged pull request #827: native image: hardening csu for old glibc
gnodet merged PR #827: URL: https://github.com/apache/maven-mvnd/pull/827 -- 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-6825) Cleaning Up dependencies plexus-utils/maven-shared-utils/commons-lang3/commons-io
[
https://issues.apache.org/jira/browse/MNG-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709297#comment-17709297
]
ASF GitHub Bot commented on MNG-6825:
-
gnodet closed pull request #832: [MNG-6825] Replace StringUtils with Commons
Lang3
URL: https://github.com/apache/maven-mvnd/pull/832
> Cleaning Up dependencies
> plexus-utils/maven-shared-utils/commons-lang3/commons-io
> -
>
> Key: MNG-6825
> URL: https://issues.apache.org/jira/browse/MNG-6825
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.6.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.x-candidate
>
>
> Experiment to see if we can get rid of commons-lang3 dependency.
> * Identified code duplication between:
> ** {{org.apache.commons.lang3.StringUtils}} from {{commons-lang3}} (501879
> Bytes commons-lang3-3.8.1.jar)
> ** {{org.codehaus.plexus.util.StringUtil}} from {{plexus-utils}} (261801
> Bytes plexus-utils-3.2.1.jar)
> ** {{org.apache.maven.shared.utils}} from {{maven-shared-utils}} (166562
> Bytes maven-shared-utils-3.2.1.jar)
> ** We should replace the self implemented with
> {{org.codehaus.plexus.util.StringUtil}}. or with {{maven-shared-utils}}
> * {{commons-io}} usage by {{maven-shared-utils}} (208700 Bytes
> commons-io-2.5.jar)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6825) Cleaning Up dependencies plexus-utils/maven-shared-utils/commons-lang3/commons-io
[
https://issues.apache.org/jira/browse/MNG-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709296#comment-17709296
]
ASF GitHub Bot commented on MNG-6825:
-
gnodet commented on PR #832:
URL: https://github.com/apache/maven-mvnd/pull/832#issuecomment-1498711758
Superseded with #833
> Cleaning Up dependencies
> plexus-utils/maven-shared-utils/commons-lang3/commons-io
> -
>
> Key: MNG-6825
> URL: https://issues.apache.org/jira/browse/MNG-6825
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.6.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.x-candidate
>
>
> Experiment to see if we can get rid of commons-lang3 dependency.
> * Identified code duplication between:
> ** {{org.apache.commons.lang3.StringUtils}} from {{commons-lang3}} (501879
> Bytes commons-lang3-3.8.1.jar)
> ** {{org.codehaus.plexus.util.StringUtil}} from {{plexus-utils}} (261801
> Bytes plexus-utils-3.2.1.jar)
> ** {{org.apache.maven.shared.utils}} from {{maven-shared-utils}} (166562
> Bytes maven-shared-utils-3.2.1.jar)
> ** We should replace the self implemented with
> {{org.codehaus.plexus.util.StringUtil}}. or with {{maven-shared-utils}}
> * {{commons-io}} usage by {{maven-shared-utils}} (208700 Bytes
> commons-io-2.5.jar)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-mvnd] gnodet commented on pull request #832: [MNG-6825] Replace StringUtils with Commons Lang3
gnodet commented on PR #832: URL: https://github.com/apache/maven-mvnd/pull/832#issuecomment-1498711758 Superseded with #833 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet closed pull request #832: [MNG-6825] Replace StringUtils with Commons Lang3
gnodet closed pull request #832: [MNG-6825] Replace StringUtils with Commons Lang3 URL: https://github.com/apache/maven-mvnd/pull/832 -- 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-6825) Cleaning Up dependencies plexus-utils/maven-shared-utils/commons-lang3/commons-io
[
https://issues.apache.org/jira/browse/MNG-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709295#comment-17709295
]
ASF GitHub Bot commented on MNG-6825:
-
gnodet merged PR #833:
URL: https://github.com/apache/maven-mvnd/pull/833
> Cleaning Up dependencies
> plexus-utils/maven-shared-utils/commons-lang3/commons-io
> -
>
> Key: MNG-6825
> URL: https://issues.apache.org/jira/browse/MNG-6825
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.6.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.x-candidate
>
>
> Experiment to see if we can get rid of commons-lang3 dependency.
> * Identified code duplication between:
> ** {{org.apache.commons.lang3.StringUtils}} from {{commons-lang3}} (501879
> Bytes commons-lang3-3.8.1.jar)
> ** {{org.codehaus.plexus.util.StringUtil}} from {{plexus-utils}} (261801
> Bytes plexus-utils-3.2.1.jar)
> ** {{org.apache.maven.shared.utils}} from {{maven-shared-utils}} (166562
> Bytes maven-shared-utils-3.2.1.jar)
> ** We should replace the self implemented with
> {{org.codehaus.plexus.util.StringUtil}}. or with {{maven-shared-utils}}
> * {{commons-io}} usage by {{maven-shared-utils}} (208700 Bytes
> commons-io-2.5.jar)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-mvnd] gnodet merged pull request #833: [MNG-6825] Remove plexus-utils and commons-xxx references
gnodet merged PR #833: URL: https://github.com/apache/maven-mvnd/pull/833 -- 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-6825) Cleaning Up dependencies plexus-utils/maven-shared-utils/commons-lang3/commons-io
[
https://issues.apache.org/jira/browse/MNG-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709292#comment-17709292
]
ASF GitHub Bot commented on MNG-6825:
-
gnodet merged PR #1080:
URL: https://github.com/apache/maven/pull/1080
> Cleaning Up dependencies
> plexus-utils/maven-shared-utils/commons-lang3/commons-io
> -
>
> Key: MNG-6825
> URL: https://issues.apache.org/jira/browse/MNG-6825
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 3.6.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.x-candidate
>
>
> Experiment to see if we can get rid of commons-lang3 dependency.
> * Identified code duplication between:
> ** {{org.apache.commons.lang3.StringUtils}} from {{commons-lang3}} (501879
> Bytes commons-lang3-3.8.1.jar)
> ** {{org.codehaus.plexus.util.StringUtil}} from {{plexus-utils}} (261801
> Bytes plexus-utils-3.2.1.jar)
> ** {{org.apache.maven.shared.utils}} from {{maven-shared-utils}} (166562
> Bytes maven-shared-utils-3.2.1.jar)
> ** We should replace the self implemented with
> {{org.codehaus.plexus.util.StringUtil}}. or with {{maven-shared-utils}}
> * {{commons-io}} usage by {{maven-shared-utils}} (208700 Bytes
> commons-io-2.5.jar)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] gnodet merged pull request #1080: [MNG-6825] Get rid of commons-lang
gnodet merged PR #1080: URL: https://github.com/apache/maven/pull/1080 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet merged pull request #829: Sort build times for the whole reactor by decreasing total time
gnodet merged PR #829: URL: https://github.com/apache/maven-mvnd/pull/829 -- 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] (DOXIASITETOOLS-301) Automatically remove the 0-byte site descriptors from the local repo
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708560#comment-17708560
]
Michael Osipov edited comment on DOXIASITETOOLS-301 at 4/6/23 8:01 AM:
---
My .m2/repository is MASSIVE. So I really don't want to do this: {{rm -rf
~/.m2/repository}}. Can you be more specific about what I need to delete? I
don't mind deleting 1 specific plugin and all its versions, but really don't
want to delete the entire repository. Also, if the fix proposed by this ticket
will just fix it, without requiring any repository surgery, I"d prefer to wait
until the release that includes this fix.
was (Author: davewichers):
My .m2/repository is MASSIVE. So I really don't want to do this: {{rm -rf
~/.m2/repository. Can you be more specific about what I need to delete? I don't
mind deleting 1 specific plugin and all its versions, but really don't want to
delete the entire repository. Also, if the fix proposed by this ticket will
just fix it, without requiring any repository surgery, I"d prefer to wait until
the release that includes this fix.}}
> Automatically remove the 0-byte site descriptors from the local repo
>
>
> Key: DOXIASITETOOLS-301
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-301
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
>Affects Versions: 2.0.0-M6
>Reporter: Konrad Windszus
>Priority: Major
>
> As older versions created 0-byte site descriptors in the local repo those
> should be automatically removed if detected. Otherwise you run into the
> following error
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:4.0.0-M6:site
> (generate-site) on project openmeetings-parent: SiteToolException:
> Error reading site descriptor: input contained no data -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-site-plugin:4.0.0-M6:site
> (generate-site) on project openmeetings-parent: SiteToolException:
> Error reading site descriptor
>at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:347)
>at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:330)
>at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
>at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:175)
>at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:76)
>at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:163)
>at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
>at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:160)
>at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
>at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
>at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
>at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
>at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:260)
>at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:172)
>at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:100)
>at org.apache.maven.cli.MavenCli.execute (MavenCli.java:821)
>at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:270)
>at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
>at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
>at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>at java.lang.reflect.Method.invoke (Method.java:568)
>at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
>at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
>at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
>at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException:
> SiteToolException: Error reading site descriptor
>at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel
> (AbstractSiteDescriptorMojo.java:94)
>at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingCon
[jira] [Commented] (MRESOLVER-351) Thread count as core multiplied
[
https://issues.apache.org/jira/browse/MRESOLVER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709244#comment-17709244
]
ASF GitHub Bot commented on MRESOLVER-351:
--
michael-o commented on PR #278:
URL: https://github.com/apache/maven-resolver/pull/278#issuecomment-1498611101
This is not what I mean. I remember that we have agreed that higher level
needs to do such calculations. I can't find the discussion. Maybe @cstamas can
remember.
> Thread count as core multiplied
> ---
>
> Key: MRESOLVER-351
> URL: https://issues.apache.org/jira/browse/MRESOLVER-351
> Project: Maven Resolver
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> Syntax as {{1.5C}} for thread count parameters
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-resolver] michael-o commented on pull request #278: [MRESOLVER-351] Thread count as core multiplied
michael-o commented on PR #278: URL: https://github.com/apache/maven-resolver/pull/278#issuecomment-1498611101 This is not what I mean. I remember that we have agreed that higher level needs to do such calculations. I can't find the discussion. Maybe @cstamas can remember. -- 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] (MPOM-400) Bump maven-invoker-plugin from 3.3.0 to 3.5.1
[ https://issues.apache.org/jira/browse/MPOM-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MPOM-400. Fix Version/s: ASF-30 Assignee: Slawomir Jaranowski Resolution: Fixed > Bump maven-invoker-plugin from 3.3.0 to 3.5.1 > - > > Key: MPOM-400 > URL: https://issues.apache.org/jira/browse/MPOM-400 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: ASF-30 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-apache-parent] slawekjaranowski merged pull request #138: [MPOM-400] Bump maven-invoker-plugin from 3.3.0 to 3.5.1
slawekjaranowski merged PR #138: URL: https://github.com/apache/maven-apache-parent/pull/138 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-351) Thread count as core multiplied
[
https://issues.apache.org/jira/browse/MRESOLVER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709233#comment-17709233
]
ASF GitHub Bot commented on MRESOLVER-351:
--
slawekjaranowski commented on PR #278:
URL: https://github.com/apache/maven-resolver/pull/278#issuecomment-1498587239
On higher level all properties are pass as is, only resolver know which
specific property means.
> Thread count as core multiplied
> ---
>
> Key: MRESOLVER-351
> URL: https://issues.apache.org/jira/browse/MRESOLVER-351
> Project: Maven Resolver
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> Syntax as {{1.5C}} for thread count parameters
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-resolver] slawekjaranowski commented on pull request #278: [MRESOLVER-351] Thread count as core multiplied
slawekjaranowski commented on PR #278: URL: https://github.com/apache/maven-resolver/pull/278#issuecomment-1498587239 On higher level all properties are pass as is, only resolver know which specific property means. -- 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
