[jira] [Commented] (SUREFIRE-2180) Surefire not invoking tests with TestNG DataProvider
[
https://issues.apache.org/jira/browse/SUREFIRE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733726#comment-17733726
]
Karl Heinz Marbaise commented on SUREFIRE-2180:
---
Please create a full working example otherwise it's impossible to help.. We
don't know which version of surefire/failsafe plugin you are using, how your
pom file looks like etc. also the code of the test is not includes...
> Surefire not invoking tests with TestNG DataProvider
>
>
> Key: SUREFIRE-2180
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2180
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 3.1.2
>Reporter: Javier A. Ortiz
>Priority: Major
>
> I'm having a weird issue I can't figure out. It's driving me insane.
> I have a Maven project for which I'm running the same command both locally
> and on Jenkins. The environment is the same as far as I can tell:
> - Maven 3.9.2 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - JDK 11 (On Jenkins: Docker image maven:3.9.2-eclipse-temurin-11)
> - TestNG 7.8.0
> Command:
> {code:java}
> mvn -Ddependency.surefire.verbose=10 -Pcoverage verify -B -U -Dgroup=PLATFORM
> {code}
> Relevant POM section:
> {code:java}
>
>
>
>
> org.jacoco
> jacoco-maven-plugin
> 0.8.10
>
> ...
>
>
> ...
>
> ...
>
>
> coverage
>
>
>
> org.jacoco
> jacoco-maven-plugin
>
>
> com/XXX/framework/dataproviders/**/*
> com/XXX/v2/basetest/**/*
> **/*Exception*
>
>
>
>
>
> prepare-agent
>
>
>
>
> report
> test
>
> report
>
>
>
>
> jacoco-check
>
> check
>
>
>
>
> BUNDLE
>
>
> INSTRUCTION
> COVEREDRATIO
> 60%
>
>
> CLASS
> MISSEDCOUNT
> 0
>
>
>
>
> PACKAGE
>
>
> LINE
> COVEREDRATIO
> 60%
>
>
>
>
> ${skipTests}
>
>
>
>
>
>
>
> {code}
> One of the tests that have the issue (only tests with DataProviders) show
> this pattern in the logs. Enabled verbose to level 10 in hopes that something
> would show up.
> Locally:
> {code:java}
> [2023-06-06 16:55:46.795] [INFO] [TestClass] Creating TestClass for
> [ClassImpl class=com.XXX.framework.utils.TimeUtilsTest]
> [2023-06-06 16:55:46.796] [INFO] Method public java.lang.Object[][]
> com.XXX.framework.utils.TimeUtilsTest.getTimeData() has a @Test annotation
> but also a return value: ignoring it. Use
> to fix this
> [2023-06-06 16:55:46.797] [INFO] [TestClass] Adding method
> TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
> instance:null] on TestClass class com.XXX.framework.utils.TimeUtilsTest
> {code}
> ...
> {code:java}
> [2023-06-06 16:55:47.316] [INFO] = Test class
> com.XXX.framework.utils.TimeUtilsTest
> [2023-06-06 16:55:47.316] [INFO] @Test
> TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)[pri:0,
> instance:com.XXX.framework.utils.TimeUtilsTest@283eb984]
> [2023-06-06 16:55:47.316] [INFO] ==
> {code}
> ...
> {code:java}
> [TestNG] INVOKING: "Surefire test" -
> com.XXX.framework.utils.TimeUtilsTest.testToFormattedString(java.util.concurrent.TimeUnit,int,java.lang.String,com.XXX.framework.annotations.TestNameParameter)(value(s):
> NANOSECONDS, 60, "60ns", TestNameParameter(customName=60 NANOSECONDS))
> {code}
> ...
> Test executes and results, etc.
> On Jenkins:
> {code:java}
> [2023-06-06 21:02:29.270] [INFO] [TestClass] Creating TestClass for
> [ClassImpl class=c
[jira] [Closed] (MNG-7766) Migrate to use mockito-bom 4.11.0
[ https://issues.apache.org/jira/browse/MNG-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-7766. Resolution: Done > Migrate to use mockito-bom 4.11.0 > - > > Key: MNG-7766 > URL: https://issues.apache.org/jira/browse/MNG-7766 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-5 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0-alpha-6 > > > We can not upgrade to the most recent version of Mockito 5.3.0 because the > last versions of Mockito which supports JDK8 ist Mockito 4.11.0. All version > beyond require at minimum JDK11. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7766) Migrate to use mockito-bom 4.11.0
[ https://issues.apache.org/jira/browse/MNG-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712790#comment-17712790 ] Karl Heinz Marbaise commented on MNG-7766: -- Done in [5c750eacb44af8e2c5e6d49e7b38a9f38d10d624|https://gitbox.apache.org/repos/asf?p=maven.git;a=commitdiff;h=5c750eacb44af8e2c5e6d49e7b38a9f38d10d624] > Migrate to use mockito-bom 4.11.0 > - > > Key: MNG-7766 > URL: https://issues.apache.org/jira/browse/MNG-7766 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-5 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0-alpha-6 > > > We can not upgrade to the most recent version of Mockito 5.3.0 because the > last versions of Mockito which supports JDK8 ist Mockito 4.11.0. All version > beyond require at minimum JDK11. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7451) Remove public modifier from test methods / test classes
[ https://issues.apache.org/jira/browse/MNG-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-7451. Resolution: Done > Remove public modifier from test methods / test classes > --- > > Key: MNG-7451 > URL: https://issues.apache.org/jira/browse/MNG-7451 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7451) Remove public modifier from test methods / test classes
[ https://issues.apache.org/jira/browse/MNG-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712778#comment-17712778 ] Karl Heinz Marbaise commented on MNG-7451: -- Done in [c49c4e0b18b70abb42c0bbf463d958a6567c4166|https://gitbox.apache.org/repos/asf?p=maven.git;a=commitdiff;h=c49c4e0b18b70abb42c0bbf463d958a6567c4166] > Remove public modifier from test methods / test classes > --- > > Key: MNG-7451 > URL: https://issues.apache.org/jira/browse/MNG-7451 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7766) Migrate to use mockito-bom 4.11.0
[ https://issues.apache.org/jira/browse/MNG-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNG-7766: - Summary: Migrate to use mockito-bom 4.11.0 (was: Migrate to use mockito-bom) > Migrate to use mockito-bom 4.11.0 > - > > Key: MNG-7766 > URL: https://issues.apache.org/jira/browse/MNG-7766 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-5 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0-alpha-6 > > > We can not upgrade to the most recent version of Mockito 5.3.0 because the > last versions of Mockito which supports JDK8 ist Mockito 4.11.0. All version > beyond require at minimum JDK11. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7766) Migrate to use mockito-bom
[ https://issues.apache.org/jira/browse/MNG-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNG-7766: - Description: We can not upgrade to the most recent version of Mockito 5.3.0 because the last versions of Mockito which supports JDK8 ist Mockito 4.11.0. All version beyond require at minimum JDK11. > Migrate to use mockito-bom > -- > > Key: MNG-7766 > URL: https://issues.apache.org/jira/browse/MNG-7766 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-5 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0-alpha-6 > > > We can not upgrade to the most recent version of Mockito 5.3.0 because the > last versions of Mockito which supports JDK8 ist Mockito 4.11.0. All version > beyond require at minimum JDK11. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7766) Migrate to use mockito-bom
Karl Heinz Marbaise created MNG-7766: Summary: Migrate to use mockito-bom Key: MNG-7766 URL: https://issues.apache.org/jira/browse/MNG-7766 Project: Maven Issue Type: Improvement Affects Versions: 4.0.0-alpha-5 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 4.0.0-alpha-6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7765) Minimum Build Requirement is wrong
[ https://issues.apache.org/jira/browse/MNG-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-7765. Resolution: Done > Minimum Build Requirement is wrong > -- > > Key: MNG-7765 > URL: https://issues.apache.org/jira/browse/MNG-7765 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-5 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 4.0.0-alpha-6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7765) Minimum Build Requirement is wrong
[ https://issues.apache.org/jira/browse/MNG-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712645#comment-17712645 ] Karl Heinz Marbaise commented on MNG-7765: -- Done in [d7d854466952021c9db070f0a9026defb9bbd0d7|https://gitbox.apache.org/repos/asf?p=maven.git;a=commitdiff;h=d7d854466952021c9db070f0a9026defb9bbd0d7] > Minimum Build Requirement is wrong > -- > > Key: MNG-7765 > URL: https://issues.apache.org/jira/browse/MNG-7765 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-5 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 4.0.0-alpha-6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MRELEASE-1119) release plugin ignores developmentVersion
[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712387#comment-17712387
]
Karl Heinz Marbaise edited comment on MRELEASE-1119 at 4/14/23 1:28 PM:
No. The property file contained the same versions as your pom file already
contained (next release versions implied by the existing SNAPSHOT versions)
which looks like it's working but it does not working that way. Just set your
version in your pom file to lets say {{3.2.0-SNAPSHOT}} commit that and then
define the content of your {{release.properties}} file with the following:
{code}
tag=release-3.3.0
releaseVersion=3.3.0
developmentVersion=3.4.0-SNAPSHOT
{code}
and just try to run: {{mvn -B release:prepare}} and look in the pom and the
created tag etc... it will tag: 3.2.0 and your pom (last commit will be 3.2.0)
etc. so not workgin at all...as documented...
If you in contradiction fill the {{release.properties}} file with correct
key/value pairs like this:
{code}
scm.tag=release-3.3.0
project.dev.io.rhpatrick.test\:mrp-test=3.4.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.3.0
{code}
and run {{mvn -B release:prepare}} you will see the difference...
was (Author: khmarbaise):
No. The property file contained the same versions as your pom file already
contained (next release versions implied by the existing SNAPSHOT versions)
which looks like it's working but it does not working that way. Just set your
version in your pom file to lets say {{3.2.0-SNAPSHOT}} commit that and then
define the content of your {{release.properties}} file with the following:
{code}
tag=release-3.3.0
releaseVersion=3.3.0
developmentVersion=3.4.0-SNAPSHOT {code}
{code}
and just try to run: {{mvn -B release:prepare}} and look in the pom and the
created tag etc... it will tag: 3.2.0 and your pom (last commit will be 3.2.0)
etc. so not workgin at all...as documented...
If you in contradiction fill the {{release.properties}} file with correct
key/value pairs like this:
{code}
scm.tag=release-3.3.0
project.dev.io.rhpatrick.test\:mrp-test=3.4.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.3.0
{code}
and run {{mvn -B release:prepare}} you will see the difference...
> release plugin ignores developmentVersion
> -
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Patrick
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1119) release plugin ignores developmentVersion
[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712387#comment-17712387
]
Karl Heinz Marbaise commented on MRELEASE-1119:
---
No. The property file contained the same versions as your pom file already
contained (next release versions implied by the existing SNAPSHOT versions)
which looks like it's working but it does not working that way. Just set your
version in your pom file to lets say {{3.2.0-SNAPSHOT}} commit that and then
define the content of your {{release.properties}} file with the following:
{code}
tag=release-3.3.0
releaseVersion=3.3.0
developmentVersion=3.4.0-SNAPSHOT {code}
{code}
and just try to run: {{mvn -B release:prepare}} and look in the pom and the
created tag etc... it will tag: 3.2.0 and your pom (last commit will be 3.2.0)
etc. so not workgin at all...as documented...
If you in contradiction fill the {{release.properties}} file with correct
key/value pairs like this:
{code}
scm.tag=release-3.3.0
project.dev.io.rhpatrick.test\:mrp-test=3.4.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.3.0
{code}
and run {{mvn -B release:prepare}} you will see the difference...
> release plugin ignores developmentVersion
> -
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Patrick
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7765) Minimum Build Requirement is wrong
Karl Heinz Marbaise created MNG-7765: Summary: Minimum Build Requirement is wrong Key: MNG-7765 URL: https://issues.apache.org/jira/browse/MNG-7765 Project: Maven Issue Type: Improvement Affects Versions: 4.0.0-alpha-5 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 4.0.0-alpha-6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MRELEASE-1119) release plugin ignores developmentVersion
[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712129#comment-17712129
]
Karl Heinz Marbaise edited comment on MRELEASE-1119 at 4/14/23 12:08 AM:
-
Ah great [~rhpatrick00] thanks for those detailed information that helps a lot
to understand your problem. The issue was that your {{release.properties}} did
not contained the correct information... if you create a {{release.properties}}
file like this:
{code}
scm.tag=release-3.0.4
project.dev.org.apache.maven.plugin.release.its\:mrelease-1119=3.1.0-SNAPSHOT
project.rel.org.apache.maven.plugin.release.its\:mrelease-1119=3.0.4
{code}
where the part: {{org.apache.maven.plugin.release.its}} represents the groupId
of your project and the {{mrelease-1119}} is the artifactId of your project.
The prefixing part {{project.dev.}} is the development version and the
{{project.rel.}} is the project release version. By using that it creates the
correct results.
By using the wrong {{release.properties}} the integration tests exactly shows
the described (from your point of view) wrong behaviour. Using the correct
content it behaves exactly as it should...
So the {{release.properties}} file for your test project (mrpm-test) should
look like this:(assumed your starting version in your project is
{{3.0.4-SNAPSHOT}}):
{code}
scm.tag=release-3.0.4
project.dev.io.rhpatrick.test\:mrp-test=3.1.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.0.4
{code}
This is also documented here:
https://maven.apache.org/maven-release/maven-release-plugin/usage/non-interactive-release.html#using-a-properties-file
It might be easier to just define the new development version via command like
this: {{mvn -B -DdevelopmentVersion=3.1.0-SNAPSHOT release:prepare
release:perform}} and the rest will be taken from the {{pom.xml}} and the
increment will be done by default on the patch level...
was (Author: khmarbaise):
Ah great [~rhpatrick00] thanks for those detailed information that helps a lot
to understand your problem. The issue was that your {{release.properties}} did
not contained the correct information... if you create a {{release.properties}}
file like this:
{code:text}
scm.tag=release-3.0.4
project.dev.org.apache.maven.plugin.release.its\:mrelease-1119=3.1.0-SNAPSHOT
project.rel.org.apache.maven.plugin.release.its\:mrelease-1119=3.0.4
{code}
where the part: {{org.apache.maven.plugin.release.its}} represents the groupId
of your project and the {{mrelease-1119}} is the artifactId of your project.
The prefixing part {{project.dev.}} is the development version and the
{{project.rel.}} is the project release version. By using that it creates the
correct results.
By using the wrong {{release.properties}} the integration tests exactly shows
the described (from your point of view) wrong behaviour. Using the correct
content it behaves exactly as it should...
So the {{release.properties}} file for your test project (mrpm-test) should
look like this:(assumed your starting version in your project is
{{3.0.4-SNAPSHOT}}):
{code}
scm.tag=release-3.0.4
project.dev.io.rhpatrick.test\:mrp-test=3.1.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.0.4
{code}
This is also documented here:
https://maven.apache.org/maven-release/maven-release-plugin/usage/non-interactive-release.html#using-a-properties-file
It might be easier to just define the new development version via command like
this: {{mvn -B -DdevelopmentVersion=3.1.0-SNAPSHOT release:prepare
release:perform}} and the rest will be taken from the {{pom.xml}} and the
increment will be done by default on the patch level...
> release plugin ignores developmentVersion
> -
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Patrick
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1119) release plugin ignores developmentVersion
[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712129#comment-17712129
]
Karl Heinz Marbaise commented on MRELEASE-1119:
---
Ah great [~rhpatrick00] thanks for those detailed information that helps a lot
to understand your problem. The issue was that your {{release.properties}} did
not contained the correct information... if you create a {{release.properties}}
file like this:
{code:text}
scm.tag=release-3.0.4
project.dev.org.apache.maven.plugin.release.its\:mrelease-1119=3.1.0-SNAPSHOT
project.rel.org.apache.maven.plugin.release.its\:mrelease-1119=3.0.4
{code}
where the part: {{org.apache.maven.plugin.release.its}} represents the groupId
of your project and the {{mrelease-1119}} is the artifactId of your project.
The prefixing part {{project.dev.}} is the development version and the
{{project.rel.}} is the project release version. By using that it creates the
correct results.
By using the wrong {{release.properties}} the integration tests exactly shows
the described (from your point of view) wrong behaviour. Using the correct
content it behaves exactly as it should...
So the {{release.properties}} file for your test project (mrpm-test) should
look like this:(assumed your starting version in your project is
{{3.0.4-SNAPSHOT}}):
{code}
scm.tag=release-3.0.4
project.dev.io.rhpatrick.test\:mrp-test=3.1.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.0.4
{code}
This is also documented here:
https://maven.apache.org/maven-release/maven-release-plugin/usage/non-interactive-release.html#using-a-properties-file
It might be easier to just define the new development version via command like
this: {{mvn -B -DdevelopmentVersion=3.1.0-SNAPSHOT release:prepare
release:perform}} and the rest will be taken from the {{pom.xml}} and the
increment will be done by default on the patch level...
> release plugin ignores developmentVersion
> -
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Patrick
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7764) Small Code Improvments.
Karl Heinz Marbaise created MNG-7764: Summary: Small Code Improvments. Key: MNG-7764 URL: https://issues.apache.org/jira/browse/MNG-7764 Project: Maven Issue Type: Improvement Affects Versions: 4.0.0-alpha-5 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 4.0.0-alpha-6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRELEASE-1119) release plugin ignores developmentVersion
[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711751#comment-17711751
]
Karl Heinz Marbaise commented on MRELEASE-1119:
---
The question is not if you like to type that. I have asked how you have called
the maven-release-plugin? Via configuraiton in pom file or how? If I take the
not existing configuration in the referernced project it can not change the
developmentVersion like that because it's not defined at all which means it
uses the defaults which means simply incrementing the patch version...
> release plugin ignores developmentVersion
> -
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Patrick
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1119) release plugin ignores developmentVersion
[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711600#comment-17711600
]
Karl Heinz Marbaise commented on MRELEASE-1119:
---
Hi [~rhpatrick00] Have you called the release plugin via:
{code}
mvn -Drelease=... -DdevelopmentVersion=3.1.0-SNAPSHOT release:prepare
release:perform
{code}
Can you give more context on the problem maybe an example project? I've created
an IT's which seemed to be working...
> release plugin ignores developmentVersion
> -
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Patrick
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MRELEASE-1119) release plugin ignores developmentVersion
[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MRELEASE-1119:
-
Assignee: Karl Heinz Marbaise
> release plugin ignores developmentVersion
> -
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Robert Patrick
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRELEASE-1120) Upgrade surefire version to 3.0.0
[ https://issues.apache.org/jira/browse/MRELEASE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRELEASE-1120. - Resolution: Done > Upgrade surefire version to 3.0.0 > - > > Key: MRELEASE-1120 > URL: https://issues.apache.org/jira/browse/MRELEASE-1120 > Project: Maven Release Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRELEASE-1120) Upgrade surefire version to 3.0.0
[ https://issues.apache.org/jira/browse/MRELEASE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711586#comment-17711586 ] Karl Heinz Marbaise commented on MRELEASE-1120: --- Done in [5d3f9b769ee8b0b3d9f94c6bcce100bbda97b443|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commitdiff;h=5d3f9b769ee8b0b3d9f94c6bcce100bbda97b443] > Upgrade surefire version to 3.0.0 > - > > Key: MRELEASE-1120 > URL: https://issues.apache.org/jira/browse/MRELEASE-1120 > Project: Maven Release Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRELEASE-1120) Upgrade surefire version to 3.0.0
Karl Heinz Marbaise created MRELEASE-1120: - Summary: Upgrade surefire version to 3.0.0 Key: MRELEASE-1120 URL: https://issues.apache.org/jira/browse/MRELEASE-1120 Project: Maven Release Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MCOMPILER-529) Improve the docs about usage 1.8 vs. 8 for source/target
Karl Heinz Marbaise created MCOMPILER-529:
-
Summary: Improve the docs about usage 1.8 vs. 8 for source/target
Key: MCOMPILER-529
URL: https://issues.apache.org/jira/browse/MCOMPILER-529
Project: Maven Compiler Plugin
Issue Type: Improvement
Affects Versions: 3.10.1
Reporter: Karl Heinz Marbaise
The current descriptions/docs only mentioned the usage of {{1.8}} for
source/target. But it looks like I can use also {{8}} instead. But all the
examples on the usage page etc. using {{1.8}}... even the error message tells
me to do:
{{code}}
use -source 8 ...
{{code}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MTOOLCHAINS-45) Upgrade maven-plugin parent to 39
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MTOOLCHAINS-45. -- Resolution: Done > Upgrade maven-plugin parent to 39 > - > > Key: MTOOLCHAINS-45 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-45 > Project: Maven Toolchains Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MTOOLCHAINS-45) Upgrade maven-plugin parent to 39
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686127#comment-17686127 ] Karl Heinz Marbaise commented on MTOOLCHAINS-45: Done in [e225090c3b7eb6b5730821c04faad00825a9ac18|https://gitbox.apache.org/repos/asf?p=maven-toolchains-plugin.git;a=commitdiff;h=e225090c3b7eb6b5730821c04faad00825a9ac18] > Upgrade maven-plugin parent to 39 > - > > Key: MTOOLCHAINS-45 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-45 > Project: Maven Toolchains Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MTOOLCHAINS-45) Upgrade maven-plugin parent to 39
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MTOOLCHAINS-45: --- Fix Version/s: 3.2.0 > Upgrade maven-plugin parent to 39 > - > > Key: MTOOLCHAINS-45 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-45 > Project: Maven Toolchains Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MTOOLCHAINS-45) Upgrade maven-plugin parent to 39
Karl Heinz Marbaise created MTOOLCHAINS-45: -- Summary: Upgrade maven-plugin parent to 39 Key: MTOOLCHAINS-45 URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-45 Project: Maven Toolchains Plugin Issue Type: Dependency upgrade Affects Versions: 3.2.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MSHADE-437) Add clean Mojo to remove the dependency-reduced-pom.xml
[
https://issues.apache.org/jira/browse/MSHADE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684333#comment-17684333
]
Karl Heinz Marbaise edited comment on MSHADE-437 at 2/5/23 6:09 PM:
It might be a better solution to think about moving those generated files into
the {{target}} directory instead (which is a breaking change; so only with
major version change) ... than creating a {{clean}} goal... also [there is a
configuration to change that
location|https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation]
(can be done in a pluginManagement)
was (Author: khmarbaise):
It might be a better solution to think about moving those generated files into
the {{target}} directory instead (which is a breaking change; so only with
major version change) ... than creating a {{clean}} goal...
> Add clean Mojo to remove the dependency-reduced-pom.xml
> ---
>
> Key: MSHADE-437
> URL: https://issues.apache.org/jira/browse/MSHADE-437
> Project: Maven Shade Plugin
> Issue Type: New Feature
>Reporter: Niels Basjes
>Priority: Major
>
> The shade plugin generates files as part of the shade mojo that live outside
> the standard directories cleaned by the maven-clean-plugin.
> I propose to add a clean mojo that makes it a lot easier to correctly remove
> these generated files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHADE-437) Add clean Mojo to remove the dependency-reduced-pom.xml
[
https://issues.apache.org/jira/browse/MSHADE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684333#comment-17684333
]
Karl Heinz Marbaise commented on MSHADE-437:
It might be a better solution to think about moving those generated files into
the {{target}} directory instead (which is a breaking change; so only with
major version change) ... than creating a {{clean}} goal...
> Add clean Mojo to remove the dependency-reduced-pom.xml
> ---
>
> Key: MSHADE-437
> URL: https://issues.apache.org/jira/browse/MSHADE-437
> Project: Maven Shade Plugin
> Issue Type: New Feature
>Reporter: Niels Basjes
>Priority: Major
>
> The shade plugin generates files as part of the shade mojo that live outside
> the standard directories cleaned by the maven-clean-plugin.
> I propose to add a clean mojo that makes it a lot easier to correctly remove
> these generated files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MASSEMBLY-972) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MASSEMBLY-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MASSEMBLY-972: - Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 38 > - > > Key: MASSEMBLY-972 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-972 > Project: Maven Assembly Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MASSEMBLY-972) Upgrade maven-plugin parent to 38
Karl Heinz Marbaise created MASSEMBLY-972: - Summary: Upgrade maven-plugin parent to 38 Key: MASSEMBLY-972 URL: https://issues.apache.org/jira/browse/MASSEMBLY-972 Project: Maven Assembly Plugin Issue Type: Dependency upgrade Reporter: Karl Heinz Marbaise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MCLEAN-103. -- Resolution: Done > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638857#comment-17638857 ] Karl Heinz Marbaise commented on MCLEAN-103: Done in [e62edebff1ea91539b10fae219d87ebe085e72d8|https://gitbox.apache.org/repos/asf?p=maven-clean-plugin.git;a=commitdiff;h=e62edebff1ea91539b10fae219d87ebe085e72d8] > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MENFORCER-438: -- Affects Version/s: 3.1.0 > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MENFORCER-438: -- Fix Version/s: next-release > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MCLEAN-103: --- Affects Version/s: 3.2.0 > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MCLEAN-103: --- Fix Version/s: 3.3.0 > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MENFORCER-438. - Resolution: Done > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638845#comment-17638845 ] Karl Heinz Marbaise commented on MENFORCER-438: --- Done in [40637c64ae6e60de8bbef101991e2840903286da|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commitdiff;h=40637c64ae6e60de8bbef101991e2840903286da] > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MCLEAN-103: -- Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MCLEAN-103) Upgrade maven-plugin parent to 38
Karl Heinz Marbaise created MCLEAN-103: -- Summary: Upgrade maven-plugin parent to 38 Key: MCLEAN-103 URL: https://issues.apache.org/jira/browse/MCLEAN-103 Project: Maven Clean Plugin Issue Type: Dependency upgrade Reporter: Karl Heinz Marbaise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MENFORCER-438: - Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MENFORCER-438) Upgrade maven-plugin parent to 38
Karl Heinz Marbaise created MENFORCER-438: - Summary: Upgrade maven-plugin parent to 38 Key: MENFORCER-438 URL: https://issues.apache.org/jira/browse/MENFORCER-438 Project: Maven Enforcer Plugin Issue Type: Dependency upgrade Reporter: Karl Heinz Marbaise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MDEP-832) Remove commons-collections-4
[
https://issues.apache.org/jira/browse/MDEP-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MDEP-832:
Assignee: Karl Heinz Marbaise
> Remove commons-collections-4
>
>
> Key: MDEP-832
> URL: https://issues.apache.org/jira/browse/MDEP-832
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.3.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.4.0
>
>
> Remove the dependency:
> {code:xml}
>
> org.apache.commons
> commons-collections4
> 4.2
>
> {code}
> which is used only for a single method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MDEP-832) Remove commons-collections-4
Karl Heinz Marbaise created MDEP-832:
Summary: Remove commons-collections-4
Key: MDEP-832
URL: https://issues.apache.org/jira/browse/MDEP-832
Project: Maven Dependency Plugin
Issue Type: Improvement
Affects Versions: 3.3.0
Reporter: Karl Heinz Marbaise
Fix For: 3.4.0
Remove the dependency:
{code:xml}
org.apache.commons
commons-collections4
4.2
{code}
which is used only for a single method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MDEP-831) Remove not used dependencies / Replace parts
[
https://issues.apache.org/jira/browse/MDEP-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MDEP-831:
Assignee: Karl Heinz Marbaise
> Remove not used dependencies / Replace parts
>
>
> Key: MDEP-831
> URL: https://issues.apache.org/jira/browse/MDEP-831
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.3.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.4.0
>
>
> Currently the dependency is not used at all:
> {code:xml}
>
> commons-beanutils
> commons-beanutils
> 1.9.4
>
> {code}
> The dependency is only used for a single method:
> {code:xml}
>
> org.apache.commons
> commons-collections4
> 4.2
>
> {code}
> The dependency is only used for two methods of StringUtils.
> {code:xml}
>
> org.apache.commons
> commons-lang3
> 3.12.0
>
> {code}
> The dependency is only used in tests for deleting a directory.
> {code:xml}
>
> commons-io
> commons-io
> 2.11.0
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MDEP-831) Remove not used dependencies / Replace parts
Karl Heinz Marbaise created MDEP-831:
Summary: Remove not used dependencies / Replace parts
Key: MDEP-831
URL: https://issues.apache.org/jira/browse/MDEP-831
Project: Maven Dependency Plugin
Issue Type: Improvement
Affects Versions: 3.3.0
Reporter: Karl Heinz Marbaise
Fix For: 3.4.0
Currently the dependency is not used at all:
{code:xml}
commons-beanutils
commons-beanutils
1.9.4
{code}
The dependency is only used for a single method:
{code:xml}
org.apache.commons
commons-collections4
4.2
{code}
The dependency is only used for two methods of StringUtils.
{code:xml}
org.apache.commons
commons-lang3
3.12.0
{code}
The dependency is only used in tests for deleting a directory.
{code:xml}
commons-io
commons-io
2.11.0
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7543) Upgrade JUnit Jupiter Version 5.9.1
[ https://issues.apache.org/jira/browse/MNG-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNG-7543: - Summary: Upgrade JUnit Jupiter Version 5.9.1 (was: Upgrade JUnit Jupiter Version 5.9.0) > Upgrade JUnit Jupiter Version 5.9.1 > --- > > Key: MNG-7543 > URL: https://issues.apache.org/jira/browse/MNG-7543 > Project: Maven > Issue Type: Dependency upgrade >Affects Versions: 4.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7546) A NullPointerException on recursive propety definition
[
https://issues.apache.org/jira/browse/MNG-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609013#comment-17609013
]
Karl Heinz Marbaise commented on MNG-7546:
--
Can you please create an example project on github or alike...
> A NullPointerException on recursive propety definition
> --
>
> Key: MNG-7546
> URL: https://issues.apache.org/jira/browse/MNG-7546
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.8.6
>Reporter: Ondrej
>Priority: Trivial
>
> A NPE occured when I have changed some versions to a ${...} expression using
> find & replace.
> That also replaced the property definition:
> <{color:#002586}version.testcontainers{color}>${version.testcontainers}
> ...
> <{color:#002586}dependency{color}><{color:#002586}groupId{color}>org.testcontainers<{color:#002586}artifactId{color}>testcontainers<{color:#002586}type{color}>pom<{color:#002586}version{color}>${version.testcontainers}<{color:#002586}scope{color}>test
> This resulted in the following NPE:
> {code:java}
> /usr/lib/jvm/java-1.18.0-openjdk-amd64/bin/java
> -Dmaven.multiModuleProjectDirectory=/home/o/work/tracker-service/tracker-service
> -Dmaven.home=/snap/intellij-idea-community/387/plugins/maven/lib/maven3
> -Dclassworlds.conf=/snap/intellij-idea-community/387/plugins/maven/lib/maven3/bin/m2.conf
>
> -Dmaven.ext.class.path=/snap/intellij-idea-community/387/plugins/maven/lib/maven-event-listener.jar
>
> -javaagent:/snap/intellij-idea-community/387/lib/idea_rt.jar=46145:/snap/intellij-idea-community/387/bin
> -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8
> -Dsun.stderr.encoding=UTF-8 -classpath
> /snap/intellij-idea-community/387/plugins/maven/lib/maven3/boot/plexus-classworlds-2.6.0.jar:/snap/intellij-idea-community/387/plugins/maven/lib/maven3/boot/plexus-classworlds.license
> org.codehaus.classworlds.Launcher -Didea.version=2022.2.2 compile
> [INFO] Scanning for projects...
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:577)
> 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)
> at org.codehaus.classworlds.Launcher.main (Launcher.java:47)
> Caused by: java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap$MapEntry.setValue
> (ConcurrentHashMap.java:3546)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:1429)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:1027)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:170)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator.interpolateModel
> (StringVisitorModelInterpolator.java:107)
> at org.apache.maven.model.building.DefaultModelBuilder.interpolateModel
> (DefaultModelBuilder.java:789)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:393)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:448)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:414)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:377)
> at org.apache.maven.graph.DefaultGraphBuilder.collectProjects
> (DefaultGraphBuilder.java:414)
> at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
> (DefaultGraphBuilder.java:405)
> at org.apache.maven.graph.DefaultGraphBuilder.build
> (DefaultGraphBuilder.java:82)
> at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute
[jira] [Assigned] (MNG-7543) Upgrade JUnit Jupiter Version 5.9.0
[ https://issues.apache.org/jira/browse/MNG-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MNG-7543: Assignee: Karl Heinz Marbaise > Upgrade JUnit Jupiter Version 5.9.0 > --- > > Key: MNG-7543 > URL: https://issues.apache.org/jira/browse/MNG-7543 > Project: Maven > Issue Type: Dependency upgrade >Affects Versions: 4.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7543) Upgrade JUnit Jupiter Version 5.9.0
Karl Heinz Marbaise created MNG-7543: Summary: Upgrade JUnit Jupiter Version 5.9.0 Key: MNG-7543 URL: https://issues.apache.org/jira/browse/MNG-7543 Project: Maven Issue Type: Dependency upgrade Affects Versions: 4.0.0 Reporter: Karl Heinz Marbaise Fix For: 4.0.0-alpha-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7539) Validate/Download SNAPSHOT dependencies once
[
https://issues.apache.org/jira/browse/MNG-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606295#comment-17606295
]
Karl Heinz Marbaise commented on MNG-7539:
--
If your update of the SNAPSHOT's is always it means you have either configured
that in your {{settings.xml}} ([Update
Policy|https://maven.apache.org/settings.html#repositories]) or you are using
{{-U}} during your build..The update intervall can already being defined via
{{settings.xml}} (see updatePolicy)...
Furthermore:
{quote}Maven Repository (a local Nexus instance), and artifact resolution could
slow down the build 2x-3x.{quote}
That sounds like if your repository manager has not enough power to handle such
simple load... Also the question is: Does the build of your multi module build
(30-40 modules) takes really 10-15 minutes?
>From my point of view you could solve the whole issue by using releases of the
>needed components in your projects... and test updates (new release versions)
>on a separate branch... and hopefully having appropriate tests to verify ...
>... The other question might be if your project heavily relies on other
>componenets (high coupling) it might be an option to reconsider to integrate
>those components in your multi modules builds...
> Validate/Download SNAPSHOT dependencies once
>
>
> Key: MNG-7539
> URL: https://issues.apache.org/jira/browse/MNG-7539
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
>Reporter: Adrian Tarau
>Priority: Critical
>
> Building an unreleased multi-module project (30-40 modules) that depends on
> various other unreleased modules puts significant pressure on the Maven
> Repository (a local Nexus instance), and artifact resolution could slow down
> the build 2x-3x.
> I do acknowledge that it is the job of the repository to cache and serve
> those responses fast, and for some reason, sometimes it slows down without an
> apparent reason.
> However, the whole build process will be faster if Maven validates a SNAPSHOT
> once for multi-module (when the dependency is reached the first time) and
> then use that version. Even if Maven Repository is relative fast, there is
> still network traffic done. Outside the fact that it should not be done, it
> might also introduce flaky behaviors:
> * one module downloads a version of artifact A, works with it, and
> everything is fine
> * 10 minutes later, another module needs artifact A and gets a newer
> version, which has some issues, and various (test) failures will be raised
> For consistency, on a multi-module build, all modules should _see_ the same
> version of a SNAPSHOT artifact. It will be faster, and it will be consistent
> (which is very important).
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7542) Wrong Information - multi-module project
Karl Heinz Marbaise created MNG-7542:
Summary: Wrong Information - multi-module project
Key: MNG-7542
URL: https://issues.apache.org/jira/browse/MNG-7542
Project: Maven
Issue Type: Bug
Affects Versions: 4.0.0-alpha-1
Environment: Apache Maven 4.0.0-alpha-1-SNAPSHOT
(1ca65c79fa4e25c4b7da027c8f8eef1b95ceced4)
Maven home: /Users/khm/tools/maven
Java version: 17.0.4, vendor: Eclipse Adoptium, runtime:
/Users/khm/.sdkman/candidates/java/17.0.4-tem
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "12.4", arch: "aarch64", family: "mac"
Reporter: Karl Heinz Marbaise
Fix For: 4.0.0
I have simple [single module spring boot project for testing
purposes|https://github.com/khmarbaise/m4/tree/main/spring-boot-plus-spring-data]
which produces during the build the following information at the beginning of
the build:
{code}
[INFO] Scanning for projects...
[INFO] Maven detected that the requested POM file is part of a multi-module
project, but could not find a pom.xml file in the multi-module root directory
'/Users/khm/ws-git-soebes'.
[INFO] The reactor is limited to all projects under:
/Users/khm/ws-git-soebes/examples/spring-boot-plus-spring-data
[INFO]
{code}
If I put the same project into a different directory:
{{/Users/khm/ws-git-bugs-maven/m4/spring-boot-plus-spring-data}} it does
**NOT** produce the output.
I have defined in the pom file the parent exactly like this:
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.springframework.boot
spring-boot-starter-parent
3.0.0-M4
com.soebes.spring.example
employee
0.0.1-SNAPSHOT
{code}
Based on the configuration via {{}} it should never try to find
a parent project...which means this is simple separated single module
project... Unfortunately the given output is misleading here...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7414) Maven version 3.8.3 + 3.8.4 have jsoup vulnerability
[ https://issues.apache.org/jira/browse/MNG-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNG-7414: - Fix Version/s: waiting-for-feedback wontfix-candidate > Maven version 3.8.3 + 3.8.4 have jsoup vulnerability > > > Key: MNG-7414 > URL: https://issues.apache.org/jira/browse/MNG-7414 > Project: Maven > Issue Type: Bug >Reporter: Ksenia Hershkovici >Priority: Major > Fix For: waiting-for-feedback, wontfix-candidate > > > Hi Team, > We are facing jsoup component vulnerability with maven versions 3.8.3 and > 3.8.4 which is the latest released version of maven. The CVE details are: > CVE-2021-37714 > Jsoup version which is getting installed while installing maven 3.8.3 and > 3.8.4 is v1.12.1. > We noticed that both versions have wagon 3.4.3 that is probably installing > Jsoup v1.12.1. > Can you please provide the details of next maven version release with this > fix in it? > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7533) jar v2.6 has medium (CVE-2021-29425) Prisma vulnerability associated with maven v3.8.6
[
https://issues.apache.org/jira/browse/MNG-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606277#comment-17606277
]
Karl Heinz Marbaise commented on MNG-7533:
--
The given image references a file {{wagon-http-3.5.1-shaded.jar}} and signals
the [CVE|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425] which
describes explicit the usage of {{FileNameUtils.normalize}}. The referenced
{{wagon-http-3.5.1-shaded.jar}} file does not even contain commons io code.
Also the Maven code does not use the described way of code.
> jar v2.6 has medium (CVE-2021-29425) Prisma vulnerability associated with
> maven v3.8.6
> --
>
> Key: MNG-7533
> URL: https://issues.apache.org/jira/browse/MNG-7533
> Project: Maven
> Issue Type: Bug
> Environment: Production
>Reporter: John Roddy
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Attachments: MicrosoftTeams-image (5).png
>
>
> jar v2.6 has medium (CVE-2021-29425) Prisma vulnerability associated with
> maven v3.8.6. We're using the latest for maven which is v3.8.6. Please
> upgrade jar to the latest to remediate the Prisma vulnerability associated
> with maven v3.8.6. Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-7535) Latest release of Maven contain EOL component - EOL-Google Guava 25.1
[ https://issues.apache.org/jira/browse/MNG-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-7535. Resolution: Won't Fix > Latest release of Maven contain EOL component - EOL-Google Guava 25.1 > - > > Key: MNG-7535 > URL: https://issues.apache.org/jira/browse/MNG-7535 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.8.6 >Reporter: Chris Campbell >Priority: Minor > Fix For: waiting-for-feedback, wontfix-candidate > > > We are utilizing the latest maven releases and getting EOL findings ( > EOL-Google Guava 25.1 ) from our internal Enterprise Security team that we > must remediate. > Will maven releases update to a newer, non-EOL of these components? If not, > is there anything we can do ourselves to remediate and use non-EOL versions? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7533) jar v2.6 has medium (CVE-2021-29425) Prisma vulnerability associated with maven v3.8.6
[ https://issues.apache.org/jira/browse/MNG-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNG-7533: - Fix Version/s: 3.9.0 > jar v2.6 has medium (CVE-2021-29425) Prisma vulnerability associated with > maven v3.8.6 > -- > > Key: MNG-7533 > URL: https://issues.apache.org/jira/browse/MNG-7533 > Project: Maven > Issue Type: Bug > Environment: Production >Reporter: John Roddy >Priority: Major > Fix For: 3.9.0, waiting-for-feedback, wontfix-candidate > > Attachments: MicrosoftTeams-image (5).png > > > jar v2.6 has medium (CVE-2021-29425) Prisma vulnerability associated with > maven v3.8.6. We're using the latest for maven which is v3.8.6. Please > upgrade jar to the latest to remediate the Prisma vulnerability associated > with maven v3.8.6. Thank you! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7535) Latest release of Maven contain EOL component - EOL-Google Guava 25.1
[ https://issues.apache.org/jira/browse/MNG-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606274#comment-17606274 ] Karl Heinz Marbaise commented on MNG-7535: -- There is nothing mentioned in https://github.com/google/guava nor something which indicates that on https://guava.dev/ > Latest release of Maven contain EOL component - EOL-Google Guava 25.1 > - > > Key: MNG-7535 > URL: https://issues.apache.org/jira/browse/MNG-7535 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.8.6 >Reporter: Chris Campbell >Priority: Minor > Fix For: waiting-for-feedback > > > We are utilizing the latest maven releases and getting EOL findings ( > EOL-Google Guava 25.1 ) from our internal Enterprise Security team that we > must remediate. > Will maven releases update to a newer, non-EOL of these components? If not, > is there anything we can do ourselves to remediate and use non-EOL versions? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPH-189) Get rid of commons-lang3
[ https://issues.apache.org/jira/browse/MPH-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MPH-189: Fix Version/s: 3.3.1 > Get rid of commons-lang3 > > > Key: MPH-189 > URL: https://issues.apache.org/jira/browse/MPH-189 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEPLOY-299) Upgrade maven-plugin parent to 37
[ https://issues.apache.org/jira/browse/MDEPLOY-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEPLOY-299. --- Resolution: Done > Upgrade maven-plugin parent to 37 > - > > Key: MDEPLOY-299 > URL: https://issues.apache.org/jira/browse/MDEPLOY-299 > Project: Maven Deploy Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEPLOY-299) Upgrade maven-plugin parent to 37
[ https://issues.apache.org/jira/browse/MDEPLOY-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576348#comment-17576348 ] Karl Heinz Marbaise commented on MDEPLOY-299: - Done in [4a72d8e9778c1878058435bdb919d40d65c879dd|https://gitbox.apache.org/repos/asf?p=maven-deploy-plugin.git;a=commitdiff;h=4a72d8e9778c1878058435bdb919d40d65c879dd] > Upgrade maven-plugin parent to 37 > - > > Key: MDEPLOY-299 > URL: https://issues.apache.org/jira/browse/MDEPLOY-299 > Project: Maven Deploy Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MDEPLOY-299) Upgrade maven-plugin parent to 37
[ https://issues.apache.org/jira/browse/MDEPLOY-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MDEPLOY-299: --- Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 37 > - > > Key: MDEPLOY-299 > URL: https://issues.apache.org/jira/browse/MDEPLOY-299 > Project: Maven Deploy Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEPLOY-299) Upgrade maven-plugin parent to 37
Karl Heinz Marbaise created MDEPLOY-299: --- Summary: Upgrade maven-plugin parent to 37 Key: MDEPLOY-299 URL: https://issues.apache.org/jira/browse/MDEPLOY-299 Project: Maven Deploy Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEPLOY-277) better deploy-file integration
[ https://issues.apache.org/jira/browse/MDEPLOY-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEPLOY-277: Fix Version/s: waiting-for-feedback > better deploy-file integration > -- > > Key: MDEPLOY-277 > URL: https://issues.apache.org/jira/browse/MDEPLOY-277 > Project: Maven Deploy Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-M1 >Reporter: Delany >Priority: Minor > Fix For: waiting-for-feedback > > > I have a script which deploys hundreds of static JARs to a Nexus repo. I use > the deploy-file goal, which requires the *url* and *repositoryId* properties. > Currently I have to hard-code these into the script. > I want to be able to use the repository url and id I set in the > distributionManagement of my project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEPLOY-217) Add option buildNumber
[ https://issues.apache.org/jira/browse/MDEPLOY-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEPLOY-217. --- Resolution: Won't Fix > Add option buildNumber > -- > > Key: MDEPLOY-217 > URL: https://issues.apache.org/jira/browse/MDEPLOY-217 > Project: Maven Deploy Plugin > Issue Type: New Feature >Reporter: Karol Gołąb >Priority: Major > > Add possibility to set the parameter buildNumber in maven-metadata.xml > > 20170209.142901 > 4 > > With this option it will be possible to synchronize this parameter with > jenkins BUILD_NUMBER -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEPLOY-124) Deploy without build
[ https://issues.apache.org/jira/browse/MDEPLOY-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEPLOY-124. --- Resolution: Won't Fix > Deploy without build > > > Key: MDEPLOY-124 > URL: https://issues.apache.org/jira/browse/MDEPLOY-124 > Project: Maven Deploy Plugin > Issue Type: New Feature >Reporter: Paul Gier >Priority: Major > Labels: contributers-welcome > Fix For: waiting-for-feedback > > > We have a use case where we would like to run a build (up to the install > phase) and then deploy at a later time. Currently, the deploy plugin > requires that a full build be re-run in order to deploy. Since the build > does not record the list of attached artifacts, the deploy plugin would need > some way to record the list of attached artifacts, and then read them later > for deployment. > Possibly a new goal could be introduced which would create a list of attached > artfiacts. Then the deploy goal could optionally read from this list. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEPLOY-251) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MDEPLOY-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MDEPLOY-251.
---
Resolution: Won't Fix
> generatePom=false not working with 3.0.0-M1
> ---
>
> Key: MDEPLOY-251
> URL: https://issues.apache.org/jira/browse/MDEPLOY-251
> Project: Maven Deploy Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-M1
>Reporter: Robert Lieske
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Steps to reproduce:
> {{mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
> -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4
> -DgroupId=test1 -DartifactId=test1 -Dversion=1.0-SNAPSHOT}}
>
> {{mvn clean package deploy:deploy-file -Dfile=target/test1-1.0-SNAPSHOT.jar
> -DgeneratePom=false -DgroupId=test1 -DartifactId=test1 -Dversion=1.0-SNAPSHOT
> -DrepositoryId=snapshotRepository -Durl=${snapshotRepositoryUrl}}}
> produces:
> {quote}[INFO] --- maven-deploy-plugin:2.8.2:deploy-file (default-cli) @ test1
> ---
> Downloading from snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> Downloaded from snapshotRepository:
> http://de01-xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> (583 B at 2.0 kB/s)
> Uploading to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162443-2.jar
> Uploaded to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162443-2.jar
> (2.4 kB at 8.1 kB/s)
> Downloading from snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
> Downloaded from snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 1.8
> kB/s)
> Uploading to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> Uploaded to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> (583 B at 3.3 kB/s)
> Uploading to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
> Uploaded to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 1.4
> kB/s)
> [INFO]
>
> {quote}
>
> changing the version of the maven-deploy-plugin in pom.xml to
> {{}}
> maven-deploy-plugin
> 3.0.0-M1
>
>
> the same call to
> {{mvn clean package deploy:deploy-file -Dfile=target/test1-1.0-SNAPSHOT.jar
> -DgeneratePom=false -DgroupId=test1 -DartifactId=test1 -Dversion=1.0-SNAPSHOT
> -DrepositoryId=snapshotRepository -Durl=${snapshotRepositoryUrl}}}
> produces:
> {quote}[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy-file (default-cli) @
> test1 ---
> Downloading from snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> Downloaded from snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> (583 B at 1.6 kB/s)
> Uploading to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.jar
> Uploaded to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.jar
> (2.4 kB at 7.7 kB/s)
> {color:#d04437}Uploading to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.pom{color}
> {color:#d04437}Uploaded to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.pom
> (2.7 kB at 9.6 kB/s){color}
> Downloading from snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
> Downloaded from snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 2.6
> kB/s)
> Uploading to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> Uploaded to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
> (754 B at 4.0 kB/s)
> Uploading to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
> Uploaded to snapshotRepository:
> http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 1.5
> kB/s)
> [INFO]
>
> {quote}
>
> Which also deploys a POM - which is not what we want!
>
> NOTE: there is a similar issue with the maven-install-plugin
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MDEPLOY-259) maven-deploy-plugin uses wrong project in deploy-file goal for multi-module project
[
https://issues.apache.org/jira/browse/MDEPLOY-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MDEPLOY-259.
---
Resolution: Won't Fix
> maven-deploy-plugin uses wrong project in deploy-file goal for multi-module
> project
> ---
>
> Key: MDEPLOY-259
> URL: https://issues.apache.org/jira/browse/MDEPLOY-259
> Project: Maven Deploy Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-M1
>Reporter: Sameer Mene
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Multi-Module project
> A
> | - B
> | | - B1
> | | - B2
> | - C
>
> There is a deploy-file goal in project B1 and C using maven-deploy-plugin. B1
> is able to upload the file properly but while uploading C's file it uses the
> artifact name of B2 or B1 (random)
>
> In DeployFileMojo.java
> {code:java}
> DefaultProjectBuildingRequest buildingRequest =
> new DefaultProjectBuildingRequest(
> getSession().getProjectBuildingRequest() );{code}
>
> returns the wrong ProjectBuildingRequest and so it take a differnt project
> name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEPLOY-292) Require Java 8
[ https://issues.apache.org/jira/browse/MDEPLOY-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEPLOY-292: Fix Version/s: 3.1.0 (was: more-investigation) > Require Java 8 > -- > > Key: MDEPLOY-292 > URL: https://issues.apache.org/jira/browse/MDEPLOY-292 > Project: Maven Deploy Plugin > Issue Type: Task >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHADE-414) Upgrade mrm-maven-plugin to 1.3.0
[ https://issues.apache.org/jira/browse/MSHADE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-414. -- Resolution: Done > Upgrade mrm-maven-plugin to 1.3.0 > - > > Key: MSHADE-414 > URL: https://issues.apache.org/jira/browse/MSHADE-414 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHADE-418) Jackson-databind version is being picked as 2.12.6 instead of 2.12.6.1
[ https://issues.apache.org/jira/browse/MSHADE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-418: --- Fix Version/s: waiting-for-feedback > Jackson-databind version is being picked as 2.12.6 instead of 2.12.6.1 > --- > > Key: MSHADE-418 > URL: https://issues.apache.org/jira/browse/MSHADE-418 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Saikrishna Kosna >Priority: Major > Fix For: waiting-for-feedback > > Attachments: pom.xml > > > There was a security issue in jackson-databind, which needs to be upgraded to > 2.12.6.1 version. When the version is updated and the Jar file is generated, > the security issue still exists as part of the Jar file and the version is > being shown as 2.12.6 instead of 2.12.6.1. Attaching the pom.xml file, > please let me know if I am doing something wrong. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHADE-418) Jackson-databind version is being picked as 2.12.6 instead of 2.12.6.1
[
https://issues.apache.org/jira/browse/MSHADE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576214#comment-17576214
]
Karl Heinz Marbaise commented on MSHADE-418:
Based on your {{pom.xml}} file you have defined two dependencies:
{code:xml}
com.fasterxml.jackson.core
jackson-core
2.12.6
com.fasterxml.jackson.core
jackson-databind
2.12.6.1
{code}
which means only {{jackson-databind}} will be used with the upgraded version.
If you analyse your pom via:
{code}
$ mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:tree
[INFO] Scanning for projects...
[INFO]
[INFO] ---< sign.core.opentext.com:digital-signer >
[INFO] Building Digital-Signer 1.0-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-dependency-plugin:3.3.0:tree (default-cli) @ digital-signer ---
[INFO] sign.core.opentext.com:digital-signer:jar:1.0-SNAPSHOT
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] +- commons-codec:commons-codec:jar:1.13:compile
[INFO] +- com.microsoft.azure:azure-keyvault-core:jar:1.2.4:compile
[INFO] | +- org.apache.commons:commons-lang3:jar:3.8.1:compile
[INFO] | \- com.google.guava:guava:jar:24.1.1-jre:compile
[INFO] | +- com.google.code.findbugs:jsr305:jar:1.3.9:compile
[INFO] | +- org.checkerframework:checker-compat-qual:jar:2.0.0:compile
[INFO] | +- com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
[INFO] | +- com.google.j2objc:j2objc-annotations:jar:1.1:compile
[INFO] | \- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
[INFO] +- com.microsoft.azure:azure-keyvault-cryptography:jar:1.2.4:compile
[INFO] +- com.microsoft.azure:azure-mgmt-keyvault:jar:1.22.0:compile
[INFO] | +- com.microsoft.azure:azure-client-runtime:jar:1.6.4:compile
[INFO] | +- com.microsoft.azure:azure-mgmt-resources:jar:1.22.0:compile
[INFO] | | +- io.reactivex:rxjava:jar:1.3.8:compile
[INFO] | | \- com.microsoft.azure:azure-annotations:jar:1.8.0:compile
[INFO] | \- com.microsoft.azure:azure-mgmt-graph-rbac:jar:1.22.0:compile
[INFO] +- com.microsoft.azure:azure-keyvault:jar:1.2.4:compile
[INFO] | \- com.microsoft.rest:client-runtime:jar:1.7.4:compile
[INFO] | +- com.squareup.retrofit2:retrofit:jar:2.7.2:compile
[INFO] | +- com.squareup.okhttp3:okhttp:jar:3.12.6:compile
[INFO] | | \- com.squareup.okio:okio:jar:1.15.0:compile
[INFO] | +- com.squareup.okhttp3:logging-interceptor:jar:3.12.2:compile
[INFO] | +- com.squareup.okhttp3:okhttp-urlconnection:jar:3.12.2:compile
[INFO] | +- com.squareup.retrofit2:converter-jackson:jar:2.7.2:compile
[INFO] | +-
com.fasterxml.jackson.datatype:jackson-datatype-joda:jar:2.10.1:compile
[INFO] | | \- joda-time:joda-time:jar:2.9.9:compile
[INFO] | \- com.squareup.retrofit2:adapter-rxjava:jar:2.7.2:compile
[INFO] +- com.microsoft.azure:azure-keyvault-webkey:jar:1.2.4:compile
[INFO] | \- com.fasterxml.jackson.core:jackson-annotations:jar:2.10.1:compile
[INFO] +- com.microsoft.azure:azure-keyvault-extensions:jar:1.2.4:compile
[INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.12.6:compile
[INFO] +- com.fasterxml.jackson.core:jackson-databind:jar:2.12.6.1:compile
[INFO] +- com.microsoft.aad:adal4j:jar:0.0.2:compile
[INFO] | +- com.nimbusds:oauth2-oidc-sdk:jar:4.5:compile
[INFO] | | +- javax.mail:mail:jar:1.4.7:compile
[INFO] | | | \- javax.activation:activation:jar:1.1:compile
[INFO] | | +- net.jcip:jcip-annotations:jar:1.0:compile
[INFO] | | \- com.nimbusds:lang-tag:jar:1.4:compile
[INFO] | +- com.google.code.gson:gson:jar:2.2.4:compile
[INFO] | \- org.slf4j:slf4j-api:jar:1.7.5:compile
[INFO] +- com.nimbusds:nimbus-jose-jwt:jar:8.22.1:compile
[INFO] | +- com.github.stephenc.jcip:jcip-annotations:jar:1.0-1:compile
[INFO] | \- net.minidev:json-smart:jar:2.4.7:compile
[INFO] | \- net.minidev:accessors-smart:jar:2.4.7:compile
[INFO] |\- org.ow2.asm:asm:jar:9.1:compile
[INFO] +- org.apache.pdfbox:pdfbox-tools:jar:2.0.17:compile
[INFO] | \- org.apache.pdfbox:pdfbox-debugger:jar:2.0.17:compile
[INFO] | \- org.apache.pdfbox:pdfbox:jar:2.0.17:compile
[INFO] |\- org.apache.pdfbox:fontbox:jar:2.0.17:compile
[INFO] +- org.apache.httpcomponents:httpclient:jar:4.5.13:compile
[INFO] | \- commons-logging:commons-logging:jar:1.2:compile
[INFO] +- org.apache.httpcomponents:httpcore:jar:4.4.11:compile
[INFO] +- org.apache.pdfbox:jbig2-imageio:jar:3.0.2:compile
[INFO] +- org.bouncycastle:bcpkix-jdk15on:jar:1.70:compile
[INFO] | \- org.bouncycastle:bcutil-jdk15on:jar:1.70:compile
[INFO] +- org.bouncycastle:bcmail-jdk15on:jar:1.70:compile
[INFO] +- org.bouncycastle:bcprov-jdk15on:jar:1.70:compile
[INFO] +- org.bouncycastle:bcprov-ext-jdk15on:jar:1.70:compile
[INFO] \- com.beust:jcommander:jar:1.72:compile
[INFO] -
[jira] [Commented] (MTOOLCHAINS-43) Cleanup - Pom
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576185#comment-17576185 ] Karl Heinz Marbaise commented on MTOOLCHAINS-43: Done in [90acdc8bac3042ef3f266a7ee6abfb4b83ad1d7d|https://gitbox.apache.org/repos/asf?p=maven-toolchains-plugin.git;a=commitdiff;h=90acdc8bac3042ef3f266a7ee6abfb4b83ad1d7d] > Cleanup - Pom > - > > Key: MTOOLCHAINS-43 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-43 > Project: Maven Toolchains Plugin > Issue Type: Task >Affects Versions: 3.1.0, 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MTOOLCHAINS-43) Cleanup - Pom
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MTOOLCHAINS-43. -- Resolution: Done > Cleanup - Pom > - > > Key: MTOOLCHAINS-43 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-43 > Project: Maven Toolchains Plugin > Issue Type: Task >Affects Versions: 3.1.0, 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MTOOLCHAINS-43) Cleanup - Pom
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MTOOLCHAINS-43: -- Assignee: Karl Heinz Marbaise > Cleanup - Pom > - > > Key: MTOOLCHAINS-43 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-43 > Project: Maven Toolchains Plugin > Issue Type: Task >Affects Versions: 3.1.0, 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MTOOLCHAINS-43) Cleanup - Pom
Karl Heinz Marbaise created MTOOLCHAINS-43: -- Summary: Cleanup - Pom Key: MTOOLCHAINS-43 URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-43 Project: Maven Toolchains Plugin Issue Type: Task Affects Versions: 3.1.0, 3.2.0 Reporter: Karl Heinz Marbaise Fix For: 3.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MTOOLCHAINS-42) Upgrade maven-plugin parent to 37
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MTOOLCHAINS-42. -- Resolution: Done > Upgrade maven-plugin parent to 37 > - > > Key: MTOOLCHAINS-42 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-42 > Project: Maven Toolchains Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MTOOLCHAINS-42) Upgrade maven-plugin parent to 37
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576173#comment-17576173 ] Karl Heinz Marbaise commented on MTOOLCHAINS-42: Done in [d2cf7b31317ac2be521b15b7ea5909b246609b3d|https://gitbox.apache.org/repos/asf?p=maven-toolchains-plugin.git;a=commitdiff;h=d2cf7b31317ac2be521b15b7ea5909b246609b3d] > Upgrade maven-plugin parent to 37 > - > > Key: MTOOLCHAINS-42 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-42 > Project: Maven Toolchains Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MTOOLCHAINS-42) Upgrade maven-plugin parent to 37
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MTOOLCHAINS-42: -- Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 37 > - > > Key: MTOOLCHAINS-42 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-42 > Project: Maven Toolchains Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MTOOLCHAINS-42) Upgrade maven-plugin parent to 37
Karl Heinz Marbaise created MTOOLCHAINS-42: -- Summary: Upgrade maven-plugin parent to 37 Key: MTOOLCHAINS-42 URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-42 Project: Maven Toolchains Plugin Issue Type: Dependency upgrade Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Fix For: 3.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MTOOLCHAINS-41) Broken link to JDK toolchain version range definitions
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MTOOLCHAINS-41: --- Affects Version/s: 3.1.0 3.0.0 > Broken link to JDK toolchain version range definitions > -- > > Key: MTOOLCHAINS-41 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-41 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 3.0.0, 3.1.0 >Reporter: Andrey >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.2.0 > > Attachments: image-2022-07-05-15-46-17-107.png > > > [https://maven.apache.org/plugins/maven-toolchains-plugin/toolchains/jdk.html] > !image-2022-07-05-15-46-17-107.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MTOOLCHAINS-41) Broken link to JDK toolchain version range definitions
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MTOOLCHAINS-41: --- Priority: Minor (was: Major) > Broken link to JDK toolchain version range definitions > -- > > Key: MTOOLCHAINS-41 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-41 > Project: Maven Toolchains Plugin > Issue Type: Bug >Affects Versions: 3.0.0, 3.1.0 >Reporter: Andrey >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.2.0 > > Attachments: image-2022-07-05-15-46-17-107.png > > > [https://maven.apache.org/plugins/maven-toolchains-plugin/toolchains/jdk.html] > !image-2022-07-05-15-46-17-107.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MTOOLCHAINS-41) Broken link to JDK toolchain version range definitions
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MTOOLCHAINS-41: --- Fix Version/s: 3.2.0 > Broken link to JDK toolchain version range definitions > -- > > Key: MTOOLCHAINS-41 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-41 > Project: Maven Toolchains Plugin > Issue Type: Bug >Reporter: Andrey >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.2.0 > > Attachments: image-2022-07-05-15-46-17-107.png > > > [https://maven.apache.org/plugins/maven-toolchains-plugin/toolchains/jdk.html] > !image-2022-07-05-15-46-17-107.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MTOOLCHAINS-41) Broken link to JDK toolchain version range definitions
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MTOOLCHAINS-41. -- Resolution: Done > Broken link to JDK toolchain version range definitions > -- > > Key: MTOOLCHAINS-41 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-41 > Project: Maven Toolchains Plugin > Issue Type: Bug >Reporter: Andrey >Assignee: Karl Heinz Marbaise >Priority: Major > Attachments: image-2022-07-05-15-46-17-107.png > > > [https://maven.apache.org/plugins/maven-toolchains-plugin/toolchains/jdk.html] > !image-2022-07-05-15-46-17-107.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MTOOLCHAINS-41) Broken link to JDK toolchain version range definitions
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576169#comment-17576169 ] Karl Heinz Marbaise commented on MTOOLCHAINS-41: Done in [d75aa046c1b6d252c2afce9f64537d70ab5a64c3|https://gitbox.apache.org/repos/asf?p=maven-toolchains-plugin.git;a=commitdiff;h=d75aa046c1b6d252c2afce9f64537d70ab5a64c3] > Broken link to JDK toolchain version range definitions > -- > > Key: MTOOLCHAINS-41 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-41 > Project: Maven Toolchains Plugin > Issue Type: Bug >Reporter: Andrey >Assignee: Karl Heinz Marbaise >Priority: Major > Attachments: image-2022-07-05-15-46-17-107.png > > > [https://maven.apache.org/plugins/maven-toolchains-plugin/toolchains/jdk.html] > !image-2022-07-05-15-46-17-107.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MTOOLCHAINS-41) Broken link to JDK toolchain version range definitions
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MTOOLCHAINS-41: -- Assignee: Karl Heinz Marbaise > Broken link to JDK toolchain version range definitions > -- > > Key: MTOOLCHAINS-41 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-41 > Project: Maven Toolchains Plugin > Issue Type: Bug >Reporter: Andrey >Assignee: Karl Heinz Marbaise >Priority: Major > Attachments: image-2022-07-05-15-46-17-107.png > > > [https://maven.apache.org/plugins/maven-toolchains-plugin/toolchains/jdk.html] > !image-2022-07-05-15-46-17-107.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPH-189) Get rid of commons-lang3
[ https://issues.apache.org/jira/browse/MPH-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MPH-189: --- Assignee: Karl Heinz Marbaise > Get rid of commons-lang3 > > > Key: MPH-189 > URL: https://issues.apache.org/jira/browse/MPH-189 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPH-189) Get rid of commons-lang3
Karl Heinz Marbaise created MPH-189: --- Summary: Get rid of commons-lang3 Key: MPH-189 URL: https://issues.apache.org/jira/browse/MPH-189 Project: Maven Help Plugin Issue Type: Task Affects Versions: 3.2.0 Reporter: Karl Heinz Marbaise Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHADE-424) Upgrade jdependency 2.8.0
[ https://issues.apache.org/jira/browse/MSHADE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-424. -- Resolution: Done > Upgrade jdependency 2.8.0 > - > > Key: MSHADE-424 > URL: https://issues.apache.org/jira/browse/MSHADE-424 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHADE-424) Upgrade jdependency 2.8.0
[ https://issues.apache.org/jira/browse/MSHADE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575187#comment-17575187 ] Karl Heinz Marbaise commented on MSHADE-424: Done in [cd9c24bd2440a0f447ecf933e7f0126390d03c37|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=cd9c24bd2440a0f447ecf933e7f0126390d03c37] > Upgrade jdependency 2.8.0 > - > > Key: MSHADE-424 > URL: https://issues.apache.org/jira/browse/MSHADE-424 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSHADE-424) Upgrade jdependency 2.8.0
[ https://issues.apache.org/jira/browse/MSHADE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MSHADE-424: -- Assignee: Karl Heinz Marbaise > Upgrade jdependency 2.8.0 > - > > Key: MSHADE-424 > URL: https://issues.apache.org/jira/browse/MSHADE-424 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHADE-424) Upgrade jdependency 2.8.0
Karl Heinz Marbaise created MSHADE-424: -- Summary: Upgrade jdependency 2.8.0 Key: MSHADE-424 URL: https://issues.apache.org/jira/browse/MSHADE-424 Project: Maven Shade Plugin Issue Type: Dependency upgrade Affects Versions: 3.3.0 Reporter: Karl Heinz Marbaise Fix For: 3.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPH-188) Cleanup - Pom
[ https://issues.apache.org/jira/browse/MPH-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573907#comment-17573907 ] Karl Heinz Marbaise commented on MPH-188: - Done in [17687e315f6e43b7b3c1bb8115c4366fc5df3e5c|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=17687e315f6e43b7b3c1bb8115c4366fc5df3e5c] > Cleanup - Pom > - > > Key: MPH-188 > URL: https://issues.apache.org/jira/browse/MPH-188 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPH-188) Cleanup - Pom
[ https://issues.apache.org/jira/browse/MPH-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-188. --- Resolution: Done > Cleanup - Pom > - > > Key: MPH-188 > URL: https://issues.apache.org/jira/browse/MPH-188 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHADE-423) Get rid of commons-lang3
[ https://issues.apache.org/jira/browse/MSHADE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-423. -- Resolution: Done > Get rid of commons-lang3 > > > Key: MSHADE-423 > URL: https://issues.apache.org/jira/browse/MSHADE-423 > Project: Maven Shade Plugin > Issue Type: Task >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHADE-423) Get rid of commons-lang3
[ https://issues.apache.org/jira/browse/MSHADE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573905#comment-17573905 ] Karl Heinz Marbaise commented on MSHADE-423: Done in [5ae83a04d570416f9e5604e400fb8aa4c633f331|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=5ae83a04d570416f9e5604e400fb8aa4c633f331] > Get rid of commons-lang3 > > > Key: MSHADE-423 > URL: https://issues.apache.org/jira/browse/MSHADE-423 > Project: Maven Shade Plugin > Issue Type: Task >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSHADE-423) Get rid of commons-lang3
[ https://issues.apache.org/jira/browse/MSHADE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MSHADE-423: -- Assignee: Karl Heinz Marbaise > Get rid of commons-lang3 > > > Key: MSHADE-423 > URL: https://issues.apache.org/jira/browse/MSHADE-423 > Project: Maven Shade Plugin > Issue Type: Task >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHADE-423) Get rid of commons-lang3
Karl Heinz Marbaise created MSHADE-423: -- Summary: Get rid of commons-lang3 Key: MSHADE-423 URL: https://issues.apache.org/jira/browse/MSHADE-423 Project: Maven Shade Plugin Issue Type: Task Affects Versions: 3.3.0 Reporter: Karl Heinz Marbaise Fix For: 3.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPH-187) Upgrade to JDK minimum
[ https://issues.apache.org/jira/browse/MPH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-187. --- Resolution: Done > Upgrade to JDK minimum > -- > > Key: MPH-187 > URL: https://issues.apache.org/jira/browse/MPH-187 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPH-187) Upgrade to JDK minimum
[ https://issues.apache.org/jira/browse/MPH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573262#comment-17573262 ] Karl Heinz Marbaise commented on MPH-187: - Done in [3974cd1cc5c99143d035663a91012bf09f62f845|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=3974cd1cc5c99143d035663a91012bf09f62f845] > Upgrade to JDK minimum > -- > > Key: MPH-187 > URL: https://issues.apache.org/jira/browse/MPH-187 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
