[jira] [Updated] (MJARSIGNER-67) Update Maven minimum to 3.6.3
[ https://issues.apache.org/jira/browse/MJARSIGNER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MJARSIGNER-67: --- Fix Version/s: 3.1.0 > Update Maven minimum to 3.6.3 > - > > Key: MJARSIGNER-67 > URL: https://issues.apache.org/jira/browse/MJARSIGNER-67 > Project: Maven Jar Signer Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJARSIGNER-67) Update Maven minimum to 3.6.3
[ https://issues.apache.org/jira/browse/MJARSIGNER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MJARSIGNER-67: --- Summary: Update Maven minimum to 3.6.3 (was: Update Maven minimum to 3.2.5) > Update Maven minimum to 3.6.3 > - > > Key: MJARSIGNER-67 > URL: https://issues.apache.org/jira/browse/MJARSIGNER-67 > Project: Maven Jar Signer Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJARSIGNER-65) Update parent pom to 43
[ https://issues.apache.org/jira/browse/MJARSIGNER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MJARSIGNER-65: --- Summary: Update parent pom to 43 (was: Update parent pom to 39) > Update parent pom to 43 > --- > > Key: MJARSIGNER-65 > URL: https://issues.apache.org/jira/browse/MJARSIGNER-65 > Project: Maven Jar Signer Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPH-189) Get rid of commons-lang3
[ https://issues.apache.org/jira/browse/MPH-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPH-189. Resolution: Fixed > 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.4.2 > > -- 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 ] Sylwester Lachiewicz updated MPH-189: - Fix Version/s: 3.4.2 > 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.4.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSCRIPTING-17) Upgrade parent POM to version 43
[ https://issues.apache.org/jira/browse/MSCRIPTING-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSCRIPTING-17. -- Resolution: Fixed > Upgrade parent POM to version 43 > > > Key: MSCRIPTING-17 > URL: https://issues.apache.org/jira/browse/MSCRIPTING-17 > Project: Maven Scripting > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Labels: pull-request-available > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSCRIPTING-17) Upgrade parent POM to version 43
[ https://issues.apache.org/jira/browse/MSCRIPTING-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSCRIPTING-17: --- Summary: Upgrade parent POM to version 43 (was: Upgrade parent POM to version 42) > Upgrade parent POM to version 43 > > > Key: MSCRIPTING-17 > URL: https://issues.apache.org/jira/browse/MSCRIPTING-17 > Project: Maven Scripting > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJAVADOC-800) Update org.codehaus.plexus:plexus-io to 3.5.0
[ https://issues.apache.org/jira/browse/MJAVADOC-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MJAVADOC-800. - Resolution: Fixed > Update org.codehaus.plexus:plexus-io to 3.5.0 > - > > Key: MJAVADOC-800 > URL: https://issues.apache.org/jira/browse/MJAVADOC-800 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.7.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJAVADOC-800) Update org.codehaus.plexus:plexus-io to 3.5.0
Sylwester Lachiewicz created MJAVADOC-800: - Summary: Update org.codehaus.plexus:plexus-io to 3.5.0 Key: MJAVADOC-800 URL: https://issues.apache.org/jira/browse/MJAVADOC-800 Project: Maven Javadoc Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Fix For: 3.7.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIATOOLS-85) Update commons-cli:commons-cli to 1.8.0
[ https://issues.apache.org/jira/browse/DOXIATOOLS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed DOXIATOOLS-85. -- Assignee: Sylwester Lachiewicz Resolution: Fixed > Update commons-cli:commons-cli to 1.8.0 > --- > > Key: DOXIATOOLS-85 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-85 > Project: Maven Doxia Tools > Issue Type: Dependency upgrade > Components: Doxia Converter >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: doxia-converter-1.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIATOOLS-81) Switch to Junit5
[ https://issues.apache.org/jira/browse/DOXIATOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed DOXIATOOLS-81. -- Assignee: Sylwester Lachiewicz Resolution: Fixed > Switch to Junit5 > > > Key: DOXIATOOLS-81 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-81 > Project: Maven Doxia Tools > Issue Type: Dependency upgrade > Components: Doxia Converter >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: doxia-converter-1.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIATOOLS-85) Update commons-cli:commons-cli to 1.8.0
Sylwester Lachiewicz created DOXIATOOLS-85: -- Summary: Update commons-cli:commons-cli to 1.8.0 Key: DOXIATOOLS-85 URL: https://issues.apache.org/jira/browse/DOXIATOOLS-85 Project: Maven Doxia Tools Issue Type: Dependency upgrade Components: Doxia Converter Reporter: Sylwester Lachiewicz Fix For: doxia-converter-1.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MJDEPS-32) Require Java 8
[ https://issues.apache.org/jira/browse/MJDEPS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MJDEPS-32: -- Assignee: Sylwester Lachiewicz > Require Java 8 > -- > > Key: MJDEPS-32 > URL: https://issues.apache.org/jira/browse/MJDEPS-32 > Project: Maven JDeps Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJDEPS-32) Require Java 8
[ https://issues.apache.org/jira/browse/MJDEPS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MJDEPS-32. -- Resolution: Fixed > Require Java 8 > -- > > Key: MJDEPS-32 > URL: https://issues.apache.org/jira/browse/MJDEPS-32 > Project: Maven JDeps Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJDEPS-32) Require Java 8
[ https://issues.apache.org/jira/browse/MJDEPS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MJDEPS-32: --- Fix Version/s: 3.1.3 > Require Java 8 > -- > > Key: MJDEPS-32 > URL: https://issues.apache.org/jira/browse/MJDEPS-32 > Project: Maven JDeps Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (WAGON-625) Upgrade To commons-io 2.16.1
[ https://issues.apache.org/jira/browse/WAGON-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated WAGON-625: --- Summary: Upgrade To commons-io 2.16.1 (was: Upgrade To commons-io 2.14.0) > Upgrade To commons-io 2.16.1 > > > Key: WAGON-625 > URL: https://issues.apache.org/jira/browse/WAGON-625 > Project: Maven Wagon > Issue Type: Dependency upgrade >Affects Versions: 3.5.1 >Reporter: Ryan Baxter >Priority: Major > Fix For: 4.0.0-M1 > > Attachments: screenshot-1.png > > > commons-io 2.6 is effected by CVE-2021-29425 which is addressed in 2.7 > https://nvd.nist.gov/vuln/detail/CVE-2021-29425 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (WAGON-625) Upgrade To commons-io 2.16.1
[ https://issues.apache.org/jira/browse/WAGON-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned WAGON-625: -- Assignee: Sylwester Lachiewicz > Upgrade To commons-io 2.16.1 > > > Key: WAGON-625 > URL: https://issues.apache.org/jira/browse/WAGON-625 > Project: Maven Wagon > Issue Type: Dependency upgrade >Affects Versions: 3.5.1 >Reporter: Ryan Baxter >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 4.0.0-M1 > > Attachments: screenshot-1.png > > > commons-io 2.6 is effected by CVE-2021-29425 which is addressed in 2.7 > https://nvd.nist.gov/vuln/detail/CVE-2021-29425 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (WAGON-625) Upgrade To commons-io 2.14.0
[ https://issues.apache.org/jira/browse/WAGON-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed WAGON-625. -- Resolution: Fixed > Upgrade To commons-io 2.14.0 > > > Key: WAGON-625 > URL: https://issues.apache.org/jira/browse/WAGON-625 > Project: Maven Wagon > Issue Type: Dependency upgrade >Affects Versions: 3.5.1 >Reporter: Ryan Baxter >Priority: Major > Fix For: 4.0.0-M1 > > Attachments: screenshot-1.png > > > commons-io 2.6 is effected by CVE-2021-29425 which is addressed in 2.7 > https://nvd.nist.gov/vuln/detail/CVE-2021-29425 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSCRIPTING-17) Upgrade parent POM to version 42
Sylwester Lachiewicz created MSCRIPTING-17: -- Summary: Upgrade parent POM to version 42 Key: MSCRIPTING-17 URL: https://issues.apache.org/jira/browse/MSCRIPTING-17 Project: Maven Scripting Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSCRIPTING-17) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MSCRIPTING-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MSCRIPTING-17: -- Assignee: Sylwester Lachiewicz > Upgrade parent POM to version 42 > > > Key: MSCRIPTING-17 > URL: https://issues.apache.org/jira/browse/MSCRIPTING-17 > Project: Maven Scripting > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSCRIPTING-17) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MSCRIPTING-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSCRIPTING-17: --- Fix Version/s: 3.1.0 > Upgrade parent POM to version 42 > > > Key: MSCRIPTING-17 > URL: https://issues.apache.org/jira/browse/MSCRIPTING-17 > Project: Maven Scripting > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1421) Update org.codehaus.plexus:plexus-archiver to 4.10.0
Sylwester Lachiewicz created MSHARED-1421: - Summary: Update org.codehaus.plexus:plexus-archiver to 4.10.0 Key: MSHARED-1421 URL: https://issues.apache.org/jira/browse/MSHARED-1421 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-archiver Reporter: Sylwester Lachiewicz Fix For: maven-archiver-4.0.0-beta-2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJDEPS-32) Require Java 8
Sylwester Lachiewicz created MJDEPS-32: -- Summary: Require Java 8 Key: MJDEPS-32 URL: https://issues.apache.org/jira/browse/MJDEPS-32 Project: Maven JDeps Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MACR-56) Upgrade parent POM to version 42 and dependencies
[ https://issues.apache.org/jira/browse/MACR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MACR-56: - Summary: Upgrade parent POM to version 42 and dependencies (was: Upgrade parent POM to version 39 and dependencies) > Upgrade parent POM to version 42 and dependencies > - > > Key: MACR-56 > URL: https://issues.apache.org/jira/browse/MACR-56 > Project: Maven ACR Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDOAP-68) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MDOAP-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MDOAP-68: -- Summary: Upgrade parent POM to version 42 (was: Upgrade parent POM to version 41) > Upgrade parent POM to version 42 > > > Key: MDOAP-68 > URL: https://issues.apache.org/jira/browse/MDOAP-68 > Project: Maven DOAP Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1417) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MSHARED-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-1417: -- Fix Version/s: maven-archiver-4.0.0 > Upgrade parent POM to version 42 > > > Key: MSHARED-1417 > URL: https://issues.apache.org/jira/browse/MSHARED-1417 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-archiver >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: maven-archiver-4.0.0, maven-archiver-3.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1419) Convert tests to Junit 5
[ https://issues.apache.org/jira/browse/MSHARED-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSHARED-1419. - Resolution: Fixed > Convert tests to Junit 5 > > > Key: MSHARED-1419 > URL: https://issues.apache.org/jira/browse/MSHARED-1419 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-common-artifact-filters >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: maven-common-artifact-filters-3.4.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1419) Convert tests to Junit 5
Sylwester Lachiewicz created MSHARED-1419: - Summary: Convert tests to Junit 5 Key: MSHARED-1419 URL: https://issues.apache.org/jira/browse/MSHARED-1419 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-common-artifact-filters Reporter: Sylwester Lachiewicz Assignee: Sylwester Lachiewicz Fix For: maven-common-artifact-filters-3.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1417) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MSHARED-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSHARED-1417. - Resolution: Fixed > Upgrade parent POM to version 42 > > > Key: MSHARED-1417 > URL: https://issues.apache.org/jira/browse/MSHARED-1417 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-archiver >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: maven-archiver-3.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1417) Upgrade parent POM to version 42
Sylwester Lachiewicz created MSHARED-1417: - Summary: Upgrade parent POM to version 42 Key: MSHARED-1417 URL: https://issues.apache.org/jira/browse/MSHARED-1417 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-archiver Reporter: Sylwester Lachiewicz Fix For: maven-archiver-3.6.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-1219) skipAfterFailureCount should not count flaky tests as failures when using rerunFailingTestsCount
[ https://issues.apache.org/jira/browse/SUREFIRE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned SUREFIRE-1219: -- Assignee: (was: Tibor Digana) > skipAfterFailureCount should not count flaky tests as failures when using > rerunFailingTestsCount > > > Key: SUREFIRE-1219 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1219 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.19.1 >Reporter: Sean Flanigan >Priority: Minor > Attachments: SUREFIRE-1219-tests.zip > > > According to > https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html > "failed tests within re-run phase are not included in > skipAfterFailureCount". For instance, if skipAfterFailureCount is 1, but > every test passes on the second attempt, the tests are "flaky" but not > "failures". This should be reflected in summaries, in XML result files and > in fail fast (skipAfterFailureCount), but this is not the case. > If I have 10 flaky-but-not-failing tests, set rerunFailingTestsCount=1 and > skipAfterFailureCount=5: > 1. I would expect something like this to be printed on the console: > Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Flakes: 10 > 2. The XML report should list s but no . > 3. All tests should be run, not just 5 of them, in other words > skipAfterFailureCount should not count the flaky tests as part of the failure > count. > I have some tests demonstrating the problem, which I will attach to this > issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-1213) MOJO pre-integration-test and post-integration-test
[ https://issues.apache.org/jira/browse/SUREFIRE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned SUREFIRE-1213: -- Assignee: (was: Tibor Digana) > MOJO pre-integration-test and post-integration-test > --- > > Key: SUREFIRE-1213 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1213 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin >Reporter: Tibor Digana >Priority: Major > Fix For: Backlog > > > Introduce MOJO phase pre-integration-test and post-integration-test. > Introduce JSR 223 miscellaneous scriptables (BashShell, JavaScript, Nashorn). > The goal is to run environment setup and cleanup before/after integration > tests. > For the sake of Surefire build already requires JDK 6 (javac 1.5 still used) > these two MOJOs will be added as experimental implementations of Surefire 3.0 > which will be built on the top of Java 1.6. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-1111) The runOrder should accept any value in parallel except for "methods".
[ https://issues.apache.org/jira/browse/SUREFIRE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned SUREFIRE-: -- Assignee: (was: Tibor Digana) > The runOrder should accept any value in parallel except for "methods". > -- > > Key: SUREFIRE- > URL: https://issues.apache.org/jira/browse/SUREFIRE- > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.17 >Reporter: Tibor Digana >Priority: Major > Fix For: Backlog > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-1068) forkNumber in systemPropertyVariables requires prefix
[
https://issues.apache.org/jira/browse/SUREFIRE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned SUREFIRE-1068:
--
Assignee: (was: Tibor Digana)
> forkNumber in systemPropertyVariables requires prefix
> -
>
> Key: SUREFIRE-1068
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1068
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.16
>Reporter: Eric Pederson
>Priority: Minor
>
> The {{$\{surefire.forkNumber\}}} placeholder cannot be used alone in a
> {{systemPropertyVariable}}. The workaround is to prefix the value.
> For example, this doesn't work (the {{surefire.forkNumber}} system property
> does not exist when running the test).
> {code:xml}
>
> ${surefire.forkNumber}
>
> {code}
> But this does:
> {code:xml}
>
> 0${surefire.forkNumber}
>
> {code}
> (note the leading *0*)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned SUREFIRE-1042: -- Assignee: (was: Tibor Digana) > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN >Priority: Major > Fix For: Backlog > > Attachments: test.zip > > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-779) Surefire reports wrong number of failed tests when using JUnit's ErrorCollector rule
[
https://issues.apache.org/jira/browse/SUREFIRE-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned SUREFIRE-779:
-
Assignee: (was: Tibor Digana)
> Surefire reports wrong number of failed tests when using JUnit's
> ErrorCollector rule
>
>
> Key: SUREFIRE-779
> URL: https://issues.apache.org/jira/browse/SUREFIRE-779
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.10
>Reporter: Lieven Doclo
>Priority: Minor
>
> When running a test that contains an ErrorCollector, test failures are not
> correct when an errorcollector contains failures. For example:
> {noformat}
> public class ExampleTest {
> @Rule
> public ErrorCollector errorCollector = new ErrorCollector();
> @Test
> public void testWithErrorCollector() {
> errorCollector.checkThat(true, is(false));
> errorCollector.checkThat(3, is(4));
> }
> }
> {noformat}
> Surefire will reports 2 tests run (of which all failed). However, when you
> fix the same test so that no checks fail, Surefire will report 1 test run.
> This is incorrect, as this will result in false information in systems like
> Hudson or Sonar, the number of testcase should not fluctuate. Surefire should
> only report 1 test run, as that reflects the actual situation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MCOMPILER-590) Upgrade Parent to 42
[ https://issues.apache.org/jira/browse/MCOMPILER-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCOMPILER-590. -- Resolution: Fixed > Upgrade Parent to 42 > > > Key: MCOMPILER-590 > URL: https://issues.apache.org/jira/browse/MCOMPILER-590 > Project: Maven Compiler Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MWRAPPER-36) remove unnecessary CLI code
[ https://issues.apache.org/jira/browse/MWRAPPER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MWRAPPER-36: Assignee: (was: Robert Scholte) > remove unnecessary CLI code > --- > > Key: MWRAPPER-36 > URL: https://issues.apache.org/jira/browse/MWRAPPER-36 > Project: Maven Wrapper > Issue Type: Wish > Components: Maven Wrapper Jar >Affects Versions: 0.5.6 >Reporter: Herve Boutemy >Priority: Major > > CLI code seems unnecessary: > https://github.com/apache/maven-wrapper/tree/abb74e20115252cfa6d9b50fc7ba286c103b452d/src/main/java/org/apache/maven/wrapper/cli -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-7122) Require specific Maven compatibility version for plugins
[ https://issues.apache.org/jira/browse/MNG-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MNG-7122: - Assignee: (was: Robert Scholte) > Require specific Maven compatibility version for plugins > > > Key: MNG-7122 > URL: https://issues.apache.org/jira/browse/MNG-7122 > Project: Maven > Issue Type: New Feature > Components: Plugins and Lifecycle >Reporter: Robert Scholte >Priority: Major > Fix For: 4.0.x-candidate > > > By removing the WagonExcluder (MNG-7020) it could mean that plugins that rely > on Maven2 dependencies might leak an old wagon-version onto the classpath. > Plugins can already define a prerequisite for the Maven version, but we also > need a mechanism to do it the other way around: plugins should at least > require maven dependencies of version x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-6956) Ensure all Apache Maven sub-projects can handle build/consumer
[
https://issues.apache.org/jira/browse/MNG-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MNG-6956:
-
Assignee: (was: Robert Scholte)
> Ensure all Apache Maven sub-projects can handle build/consumer
> --
>
> Key: MNG-6956
> URL: https://issues.apache.org/jira/browse/MNG-6956
> Project: Maven
> Issue Type: Task
>Reporter: Robert Scholte
>Priority: Critical
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> First run based on https://github.com/apache/maven-sources/tree/submodules
> {noformat}
> [INFO] Maven Core ITs suite 2.1-SNAPSHOT .. FAILURE [36:34
> min]
> [INFO] Maven Artifact Resolver Ant Tasks 1.2.2-SNAPSHOT ... FAILURE [ 34.579
> s]
> [INFO] Maven Plugin Testing Mechanism 3.4.0-SNAPSHOT .. FAILURE [ 0.972
> s]
> [INFO] Maven :: Indexer Core 6.1.0-SNAPSHOT ... FAILURE [ 2.874
> s]
> [INFO] Maven Surefire Common 3.0.0-M6-SNAPSHOT FAILURE [ 0.544
> s]
> [INFO] Maven Surefire Integration Tests 3.0.0-M6-SNAPSHOT . FAILURE [ 1.499
> s]
> [INFO] Apache Maven AntRun Plugin 3.1.0-SNAPSHOT .. FAILURE [01:54
> min]
> [INFO] Apache Maven Enforcer API 3.0.0-M4-SNAPSHOT FAILURE [ 0.096
> s]
> [INFO] Apache Maven PDF Plugin 1.5.0-SNAPSHOT . FAILURE [01:49
> min]
> [INFO] Maven Plugin Metadata Model 3.6.1-SNAPSHOT . FAILURE [ 0.083
> s]
> [INFO] Maven Ant Mojo Support 3.6.1-SNAPSHOT .. FAILURE [ 0.440
> s]
> [INFO] Maven Beanshell Mojo Support 3.6.1-SNAPSHOT FAILURE [ 0.171
> s]
> [INFO] Maven Release APIs 3.0.0-SNAPSHOT .. FAILURE [ 0.243
> s]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MSHARED-964) Autogenerate checksums
[ https://issues.apache.org/jira/browse/MSHARED-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MSHARED-964: Assignee: (was: Robert Scholte) > Autogenerate checksums > -- > > Key: MSHARED-964 > URL: https://issues.apache.org/jira/browse/MSHARED-964 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-verifier >Reporter: Robert Scholte >Priority: Major > > When you clone a git repository, by default it'll use the OS line endings for > text files. > This means that cannot rely pre-generated checksums for text files. > Maven ITs are suffering from that once MNG-5728 is implemented. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JXR-145) Support custom codetransformers
[ https://issues.apache.org/jira/browse/JXR-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned JXR-145: Assignee: (was: Robert Scholte) > Support custom codetransformers > --- > > Key: JXR-145 > URL: https://issues.apache.org/jira/browse/JXR-145 > Project: Maven JXR > Issue Type: New Feature >Reporter: Andres Almiray >Priority: Major > > Gradle is also using JXR to create cross reference documentation. Right now > the only supported language is Java. It would be great if other languages > like Kotlin could be supported too. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCOMPILER-372) Unable to compile modularized test code depending on test-jar
[
https://issues.apache.org/jira/browse/MCOMPILER-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MCOMPILER-372:
--
Assignee: (was: Robert Scholte)
> Unable to compile modularized test code depending on test-jar
> -
>
> Key: MCOMPILER-372
> URL: https://issues.apache.org/jira/browse/MCOMPILER-372
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.0
> Environment: Manjaro Linux 64 bit, Open JDK 11, Apache-Maven-3.6.0
>Reporter: Jeronimo Backes
>Priority: Critical
> Attachments: maven-compiler-plugin.MCOMPILER-372.patch,
> univocity-all.zip
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I'm refactoring
> [univocity-parsers|https://github.com/uniVocity/univocity-parsers] into
> multiple projects with modules (attached a zip with everything I got)
> However I'm unable to reliably build the attached project with its unit
> tests. Unpack then cd into "univocity-all-parent", then run "mvn clean
> install".
>
> All projects generate test-jars, but for some reason class
> *com.univocity.parsers.core.routine.ResultSetWritingRoutine* inside
> "univocity-parsers-core/src/test/java/" is not found when compiling the tests
> of projects "univocity-csv", "univocity-tsv" and "univocity-fixedwidth".
>
> Interestingly, the issue doesn't seem to be consistent as I got
> "univocity-csv" and "univocity-tsv" building without errors a few times.
> "univocity-fixedwidth" however failed consistently every single time.
> Some of the errors I get are:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile
> (default-testCompile) on project univocity-csv: Compilation failure:
> Compilation failure: }}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/CsvWriterTest.java:[27,49]
> cannot find symbol}}
> {{[ERROR] symbol: class ResultSetWritingRoutine}}
> {{[ERROR] location: package com.univocity.parsers.core.routine}}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/CsvWriterTest.java:[681,17]
> cannot find symbol}}
> {{[ERROR] symbol: class ResultSetWritingRoutine}}
> {{[ERROR] location: class com.univocity.csv.CsvWriterTest}}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/CsvWriterTest.java:[681,52]
> cannot find symbol}}
> {{[ERROR] symbol: class ResultSetWritingRoutine}}
> {{[ERROR] location: class com.univocity.csv.CsvWriterTest}}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/CsvWriterTest.java:[691,17]
> cannot find symbol}}
> {{[ERROR] symbol: class ResultSetTest}}
> {{[ERROR] location: class com.univocity.csv.CsvWriterTest}}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/CsvWriterTest.java:[691,45]
> cannot find symbol}}
> {{[ERROR] symbol: class ResultSetTest}}
> {{[ERROR] location: class com.univocity.csv.CsvWriterTest}}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/routine/CsvRoutinesTest.java:[123,17]
> cannot find symbol}}
> {{[ERROR] symbol: class ResultSetWritingRoutine}}
> {{[ERROR] location: class com.univocity.csv.routine.CsvRoutinesTest}}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/routine/CsvRoutinesTest.java:[123,52]
> cannot find symbol}}
> {{[ERROR] symbol: class ResultSetWritingRoutine}}
> {{[ERROR] location: class com.univocity.csv.routine.CsvRoutinesTest}}
> {{[ERROR]
> /home/jbax/dev/repository/univocity-all/univocity-oss/univocity-csv/src/test/java/com/univocity/csv/routine/CsvRoutinesTest.java:[124,68]
> package ResultSetWritingRoutine does not exist}}
>
> I was also getting errors saying that the "Example" class was not found, or
> that the "printAndValidate" method was not found (that one comes from the
> univocity-output-tester dependency)..
>
> There's something very weird going on and it's not consistently reproducible.
> If you for example change the code in the failing tests use "*import static
> com.univocity.parsers.core.routine.ResultSetWritingRoutine.** " you may get a
> different set of errors. It's pretty intractable.
> I hope this provides enough information, let me know if you need anything
> else.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNG-6444) Internal code should prefer Path over File
[
https://issues.apache.org/jira/browse/MNG-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MNG-6444:
-
Assignee: (was: Robert Scholte)
> Internal code should prefer Path over File
> --
>
> Key: MNG-6444
> URL: https://issues.apache.org/jira/browse/MNG-6444
> Project: Maven
> Issue Type: Task
>Reporter: Robert Scholte
>Priority: Minor
> Labels: requires-java8
> Fix For: 4.0.x-candidate
>
>
> Goal is to replace all '{{new File(}}' appearances with Path / Paths
> https://docs.oracle.com/javase/7/docs/api/java/nio/file/Path.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MPLUGIN-308) Improve mojo documentation for "plugin:report" on complex parameter types
[
https://issues.apache.org/jira/browse/MPLUGIN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MPLUGIN-308:
Assignee: (was: Robert Scholte)
> Improve mojo documentation for "plugin:report" on complex parameter types
> -
>
> Key: MPLUGIN-308
> URL: https://issues.apache.org/jira/browse/MPLUGIN-308
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.4
>Reporter: Konrad Windszus
>Priority: Major
>
> In case you have a Mojo with a custom complex parameter, i.e. a Parameter of
> type {{MyParam}}, where {{MyParam}} again has some fields annotated with
> {{@Parameter}}, the documentation of {{MyParam}} with its individual pieces
> should be part of the mojo documentation being generated by {{plugin:report}}.
> See also
> http://stackoverflow.com/questions/20696862/inject-parameter-in-different-class-in-maven-plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNG-5667) Either install or deploy
[
https://issues.apache.org/jira/browse/MNG-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MNG-5667:
-
Assignee: (was: Robert Scholte)
> Either install or deploy
>
>
> Key: MNG-5667
> URL: https://issues.apache.org/jira/browse/MNG-5667
> Project: Maven
> Issue Type: Sub-task
> Components: FDPFC, Plugins and Lifecycle
>Reporter: Robert Scholte
>Priority: Major
>
> Original proposal
> {quote}
> PROPOSAL 2: Either install or deploy
> In general one should either run 'mvn verify' or 'mvn deploy', there's often
> no reason to run 'mvn install'. The only reason I can think of is when you
> have 2 separate projects (not part of the same multimodule), one depending on
> the other and you want to test this.
> To ensure that your projects build the same as your co-workers, you should
> always try to deploy it. However, there are several reasons why a deploy
> could fail: network problems, authentication/authorization issues, repository
> manager policies, etc. However, this is still after every install-phase, so
> the local repository is polluted.
> This is as unpleasant as for a developer local repository as for a CI-server
> local repo.
>
> The proposal is to "branch" the final phases.
> Calling any phase up until the verify will stay the same.
> Calling 'mvn install' would call these phases: validate ... verify, install
> (nothing new here)
> Calling 'mvn deploy' would call these phases: validate ... verify, deploy
> (no more install)
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MSHADE-262) Add jpms goal
[ https://issues.apache.org/jira/browse/MSHADE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MSHADE-262: --- Assignee: (was: Robert Scholte) > Add jpms goal > - > > Key: MSHADE-262 > URL: https://issues.apache.org/jira/browse/MSHADE-262 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: Robert Scholte >Priority: Major > > With Java 9 we get module descriptors for strong encapsulation and reliable > configuration. > When shading we should not merge or ignore these descriptors. > In case of an application we should think of the way spring boot works, i.e. > bundle the jars in a jar and provide a new classloader. This is the only way > to preserve the strong encapsulation right now. > After a talk with [~pwebb] and [~dblevins] we came to the conclusion that it > should NOT be combined with the current shade goal. First idea was to make a > new plugin, but after some rethinking I'd prefer to just make a separate goal > for it in this shade-plugin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MDEP-617) Use plexus-java for showing module info during dependency:resolve
[ https://issues.apache.org/jira/browse/MDEP-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MDEP-617: - Assignee: (was: Robert Scholte) > Use plexus-java for showing module info during dependency:resolve > - > > Key: MDEP-617 > URL: https://issues.apache.org/jira/browse/MDEP-617 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade > Components: resolve >Affects Versions: 3.1.1 >Reporter: Robert Scholte >Priority: Major > > The base for plexus-java was in this project. That library is now much > stronger so the code should be replaced. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MJAVADOC-329) Allow generation of empty javadoc JARs
[ https://issues.apache.org/jira/browse/MJAVADOC-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MJAVADOC-329: - Assignee: (was: Robert Scholte) > Allow generation of empty javadoc JARs > -- > > Key: MJAVADOC-329 > URL: https://issues.apache.org/jira/browse/MJAVADOC-329 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Vincent Massol >Priority: Major > > Here's my use case: > * I want to be able to deploy my artifacts to Maven Central. There's a > requirement that a javadoc jar exists for the arifact to deploy > * However I have some maven modules of type packaging = jar that have java > files but these files are located in an "internal" package (internal api that > we don't expose to end users since it's not part of our public API contract) > which we exclude from the javadoc generation > The problem is that the javadoc plugin doesn't generate any JAR if there are > no java files matching (even if I have other files such as a package.html > file in my src/main/javadoc/* directories). > I'd like it to be possible to generate an "empty" javadoc JAR containing only > a package.html file for example. > Thanks a lot -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-5668) post- should always be executed after
[
https://issues.apache.org/jira/browse/MNG-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MNG-5668:
-
Assignee: (was: Robert Scholte)
> post- should always be executed after
>
>
> Key: MNG-5668
> URL: https://issues.apache.org/jira/browse/MNG-5668
> Project: Maven
> Issue Type: Sub-task
> Components: FDPFC, Plugins and Lifecycle
>Reporter: Robert Scholte
>Priority: Major
>
> Original proposal:
> {quote}
> There are right now 3 phases which also have a pre- and post-,
> namely integration-test, clean and site. However, even if one has bound goals
> to the post-phases, they're probably never called.
> When there's an integration-test starting up some server, you'd probably
> always want to kill it no matter what happens during the IT (let say a NPE).
> The proposal is to execute the post- as the finally block in Java. If
> you really want to execute only the integration-test without the post, the
> phase should be marked, e.g. 'mvn [integration-test]', where the brackets
> lock the phase.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNG-5901) Export org.eclipse.aether.util.artifact.SubArtifact
[
https://issues.apache.org/jira/browse/MNG-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MNG-5901:
-
Assignee: (was: Robert Scholte)
> Export org.eclipse.aether.util.artifact.SubArtifact
> ---
>
> Key: MNG-5901
> URL: https://issues.apache.org/jira/browse/MNG-5901
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.3, 3.2.5, 3.3.1, 3.3.3
>Reporter: Robert Scholte
>Priority: Major
> Fix For: 4.0.x-candidate, 4.x / Backlog
>
>
> Without exporting {{org.eclipse.aether.util.artifact.SubArtifact}} you will
> get a {{ClassNotFoundException}} when trying to deploy/upload attachments
> using the pure Aether solution by Eclipse.
> This is also the reason why maven-artifact-transfer shades this class, so
> this component will still work with all Maven versions between 3.1.1 and 3.3.3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJLINK-81) Document requirements history
[ https://issues.apache.org/jira/browse/MJLINK-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MJLINK-81: --- Fix Version/s: (was: 3.3.0) > Document requirements history > - > > Key: MJLINK-81 > URL: https://issues.apache.org/jira/browse/MJLINK-81 > Project: Maven JLink Plugin > Issue Type: Task >Reporter: Benjamin Marwell >Assignee: Benjamin Marwell >Priority: Major > > Add requirement history to info-plugin, like this one: > https://github.com/apache/maven-shade-plugin/blob/a8030f829180f50d4497e42e212a891ec595a059/pom.xml#L308-L355 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJLINK-81) Document requirements history
[ https://issues.apache.org/jira/browse/MJLINK-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MJLINK-81. -- Resolution: Implemented > Document requirements history > - > > Key: MJLINK-81 > URL: https://issues.apache.org/jira/browse/MJLINK-81 > Project: Maven JLink Plugin > Issue Type: Task >Reporter: Benjamin Marwell >Assignee: Benjamin Marwell >Priority: Major > > Add requirement history to info-plugin, like this one: > https://github.com/apache/maven-shade-plugin/blob/a8030f829180f50d4497e42e212a891ec595a059/pom.xml#L308-L355 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2237) Upgrade junit-jupiter to 5.10.2 and junit-platform to 1.10.2
[
https://issues.apache.org/jira/browse/SUREFIRE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated SUREFIRE-2237:
---
Fix Version/s: (was: 3.1.2)
> Upgrade junit-jupiter to 5.10.2 and junit-platform to 1.10.2
>
>
> Key: SUREFIRE-2237
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2237
> Project: Maven Surefire
> Issue Type: Dependency upgrade
>Reporter: Darius Cooper
>Priority: Minor
>
> junit-jupiter 5.10.x introduced some new classes
> Now that [spring-boot-starter-test pulls in that
> version|https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-starter-test/3.2.2],
> tests give an error when we upgrade to the latest Spring. It would make
> things easier if surefire used the latest versions.
> (Cloned SUREFIRE-2157, because that was a very similar change)
> I did [notice
> this|https://github.com/apache/maven-surefire/blob/2fed802397f8c7de4cfc72f49ab4565e72f7aab7/pom.xml]
> *warning comment* in the parent pom:
> {code:java}
>
>
> org.junit
> junit-bom
> 5.9.3
> pom
> import
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-2237) Upgrade junit-jupiter to 5.10.2 and junit-platform to 1.10.2
[
https://issues.apache.org/jira/browse/SUREFIRE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned SUREFIRE-2237:
--
Assignee: (was: Sylwester Lachiewicz)
> Upgrade junit-jupiter to 5.10.2 and junit-platform to 1.10.2
>
>
> Key: SUREFIRE-2237
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2237
> Project: Maven Surefire
> Issue Type: Dependency upgrade
>Reporter: Darius Cooper
>Priority: Minor
> Fix For: 3.1.2
>
>
> junit-jupiter 5.10.x introduced some new classes
> Now that [spring-boot-starter-test pulls in that
> version|https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-starter-test/3.2.2],
> tests give an error when we upgrade to the latest Spring. It would make
> things easier if surefire used the latest versions.
> (Cloned SUREFIRE-2157, because that was a very similar change)
> I did [notice
> this|https://github.com/apache/maven-surefire/blob/2fed802397f8c7de4cfc72f49ab4565e72f7aab7/pom.xml]
> *warning comment* in the parent pom:
> {code:java}
>
>
> org.junit
> junit-bom
> 5.9.3
> pom
> import
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1400) Upgrade maven-shared-components to version 42
[ https://issues.apache.org/jira/browse/MSHARED-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSHARED-1400. - Resolution: Fixed > Upgrade maven-shared-components to version 42 > - > > Key: MSHARED-1400 > URL: https://issues.apache.org/jira/browse/MSHARED-1400 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-3.2.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: maven-dependency-tree-3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSHARED-1400) Upgrade maven-shared-components to version 42
[ https://issues.apache.org/jira/browse/MSHARED-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MSHARED-1400: - Assignee: Sylwester Lachiewicz (was: Karl Heinz Marbaise) > Upgrade maven-shared-components to version 42 > - > > Key: MSHARED-1400 > URL: https://issues.apache.org/jira/browse/MSHARED-1400 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-3.2.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: maven-dependency-tree-3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1400) Upgrade maven-shared-components to version 42
Sylwester Lachiewicz created MSHARED-1400: - Summary: Upgrade maven-shared-components to version 42 Key: MSHARED-1400 URL: https://issues.apache.org/jira/browse/MSHARED-1400 Project: Maven Shared Components Issue Type: Improvement Components: maven-dependency-tree Affects Versions: maven-dependency-tree-3.2.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-dependency-tree-3.2.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1400) Upgrade maven-shared-components to version 42
[ https://issues.apache.org/jira/browse/MSHARED-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-1400: -- Reporter: Sylwester Lachiewicz (was: Karl Heinz Marbaise) > Upgrade maven-shared-components to version 42 > - > > Key: MSHARED-1400 > URL: https://issues.apache.org/jira/browse/MSHARED-1400 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-3.2.1 >Reporter: Sylwester Lachiewicz >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-dependency-tree-3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MASFRES-68) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MASFRES-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MASFRES-68. --- Assignee: Sylwester Lachiewicz Resolution: Fixed > Upgrade parent POM to version 42 > > > Key: MASFRES-68 > URL: https://issues.apache.org/jira/browse/MASFRES-68 > Project: Apache Maven Resource Bundles > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: apache-resources 1.6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MASFRES-68) Upgrade parent POM to version 42
Sylwester Lachiewicz created MASFRES-68: --- Summary: Upgrade parent POM to version 42 Key: MASFRES-68 URL: https://issues.apache.org/jira/browse/MASFRES-68 Project: Apache Maven Resource Bundles Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Fix For: apache-resources 1.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1397) Bump org.apache.maven:maven-archiver from 3.6.1 to 3.6.2
[ https://issues.apache.org/jira/browse/MSHARED-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSHARED-1397. - Resolution: Fixed > Bump org.apache.maven:maven-archiver from 3.6.1 to 3.6.2 > > > Key: MSHARED-1397 > URL: https://issues.apache.org/jira/browse/MSHARED-1397 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: maven-reporting-impl-4.0.0, > maven-reporting-impl-4.0.0-M15 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1397) Bump org.apache.maven:maven-archiver from 3.6.1 to 3.6.2
Sylwester Lachiewicz created MSHARED-1397: - Summary: Bump org.apache.maven:maven-archiver from 3.6.1 to 3.6.2 Key: MSHARED-1397 URL: https://issues.apache.org/jira/browse/MSHARED-1397 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-impl Reporter: Sylwester Lachiewicz Fix For: maven-reporting-impl-4.0.0, maven-reporting-impl-4.0.0-M15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSKINS-214) Publish changelog of 1.11.2 as GitHub release
[ https://issues.apache.org/jira/browse/MSKINS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSKINS-214. --- Resolution: Fixed > Publish changelog of 1.11.2 as GitHub release > - > > Key: MSKINS-214 > URL: https://issues.apache.org/jira/browse/MSKINS-214 > Project: Maven Skins > Issue Type: Wish > Components: Fluido Skin >Reporter: Alexander Brandes >Priority: Minor > > Hey, > maven-fluido-skin 1.11.2 has been released on January the 17th, 2023, but the > latest GitHub release points to 1.11.1: > [https://github.com/apache/maven-fluido-skin/releases] > Would you mind publishing a changelog for 1.11.2 too? > Thanks in advance! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSKINS-214) Publish changelog of 1.11.2 as GitHub release
[ https://issues.apache.org/jira/browse/MSKINS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846388#comment-17846388 ] Sylwester Lachiewicz commented on MSKINS-214: - https://github.com/apache/maven-fluido-skin/releases/tag/maven-fluido-skin-1.11.2 > Publish changelog of 1.11.2 as GitHub release > - > > Key: MSKINS-214 > URL: https://issues.apache.org/jira/browse/MSKINS-214 > Project: Maven Skins > Issue Type: Wish > Components: Fluido Skin >Reporter: Alexander Brandes >Priority: Minor > > Hey, > maven-fluido-skin 1.11.2 has been released on January the 17th, 2023, but the > latest GitHub release points to 1.11.1: > [https://github.com/apache/maven-fluido-skin/releases] > Would you mind publishing a changelog for 1.11.2 too? > Thanks in advance! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIA-718) Apply best security recommendations to xml parsing and validation
[ https://issues.apache.org/jira/browse/DOXIA-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed DOXIA-718. -- Resolution: Not A Problem > Apply best security recommendations to xml parsing and validation > - > > Key: DOXIA-718 > URL: https://issues.apache.org/jira/browse/DOXIA-718 > Project: Maven Doxia > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Priority: Minor > > Apply OWASP recommendation if needed > > [https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIA-436) Remove xhtml-module dependency of markdown module
[ https://issues.apache.org/jira/browse/DOXIA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed DOXIA-436. -- Resolution: Information Provided > Remove xhtml-module dependency of markdown module > - > > Key: DOXIA-436 > URL: https://issues.apache.org/jira/browse/DOXIA-436 > Project: Maven Doxia > Issue Type: Task > Components: Module - Markdown >Reporter: Lukas Theussl >Priority: Major > > The markdown parser in its original form (see DOXIA-426) uses the pegdown > library to get a whole html document which is then piped through the xhtml > parser to produce proper doxia events. This double-parsing should be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIA-60) Use an external XML Pull parser instead of plexus one
[
https://issues.apache.org/jira/browse/DOXIA-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed DOXIA-60.
-
Resolution: Won't Do
> Use an external XML Pull parser instead of plexus one
> -
>
> Key: DOXIA-60
> URL: https://issues.apache.org/jira/browse/DOXIA-60
> Project: Maven Doxia
> Issue Type: Dependency upgrade
> Components: Core
>Reporter: Carlos Sanchez Gonzalez
>Priority: Major
> Labels: intern
>
> To avoid maintaining the plexus XMLPullParser we should move to a standard
> implementation like Codehaus StaX http://stax.codehaus.org
> {code:xml}
> stax
> stax
> 1.2.0_rc2-dev
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-858) Drop maven-artifact-transfer
[ https://issues.apache.org/jira/browse/MDEP-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MDEP-858: -- Priority: Major (was: Minor) > Drop maven-artifact-transfer > > > Key: MDEP-858 > URL: https://issues.apache.org/jira/browse/MDEP-858 > Project: Maven Dependency Plugin > Issue Type: Task >Reporter: Sylwester Lachiewicz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MDEP-926) proxy settings ignored for dependencies
[ https://issues.apache.org/jira/browse/MDEP-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843780#comment-17843780 ] Sylwester Lachiewicz edited comment on MDEP-926 at 5/6/24 3:55 PM: --- The m-dependecy-p is still full of maven-artifact-transfer code. It looks like [~sjaranowski] is doing some cleanups. was (Author: slachiewicz): The m-dependecy-p is still full of maven-artifact-transfer code. It looks like Slawek is doing some cleanups. > proxy settings ignored for dependencies > --- > > Key: MDEP-926 > URL: https://issues.apache.org/jira/browse/MDEP-926 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Patrick Mackinlay >Priority: Major > Attachments: image-2024-04-23-12-02-38-218.png, settings.xml > > > The proxy settings are ignored for dependencies in maven 3.9.6 (working in > 3.9.2). > On a machine with no direct internet access, if you clear your local > repository with a command like: > rm -rf ~/.m2/repository/org/apache/maven/maven-core/2.2.1 > and then try and download the dependency: > mvn dependency:get -DgroupId=org.apache.maven -DartifactId=maven-core > -Dversion=2.2.1 > > It will fail. The proxy settings are ignored. However, it should be noted > that for plugins they are used, its only for dependencies that they are > ignored. > maven version 3.9.2 works, so looks like this was introduced in 3.9.3 > probably when the dependency plugin version was upgraded. > > I used a minimal settings.xml with just one proxy entry. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-926) proxy settings ignored for dependencies
[ https://issues.apache.org/jira/browse/MDEP-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843780#comment-17843780 ] Sylwester Lachiewicz commented on MDEP-926: --- The m-dependecy-p is still full of maven-artifact-transfer code. It looks like Slawek is doing some cleanups. > proxy settings ignored for dependencies > --- > > Key: MDEP-926 > URL: https://issues.apache.org/jira/browse/MDEP-926 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Patrick Mackinlay >Priority: Major > Attachments: image-2024-04-23-12-02-38-218.png, settings.xml > > > The proxy settings are ignored for dependencies in maven 3.9.6 (working in > 3.9.2). > On a machine with no direct internet access, if you clear your local > repository with a command like: > rm -rf ~/.m2/repository/org/apache/maven/maven-core/2.2.1 > and then try and download the dependency: > mvn dependency:get -DgroupId=org.apache.maven -DartifactId=maven-core > -Dversion=2.2.1 > > It will fail. The proxy settings are ignored. However, it should be noted > that for plugins they are used, its only for dependencies that they are > ignored. > maven version 3.9.2 works, so looks like this was introduced in 3.9.3 > probably when the dependency plugin version was upgraded. > > I used a minimal settings.xml with just one proxy entry. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MANTRUN-239) Update parent pom to 42
[ https://issues.apache.org/jira/browse/MANTRUN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MANTRUN-239: - Summary: Update parent pom to 42 (was: Update parent pom to 41) > Update parent pom to 42 > --- > > Key: MANTRUN-239 > URL: https://issues.apache.org/jira/browse/MANTRUN-239 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-8115: -- Description: Apache commons, Classword (was: Plexus Utils 4 Guice 6 Apache commons) > Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Apache commons, Classword -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MEJB-137. - Resolution: Fixed > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MEJB-138. - Resolution: Fixed > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MEJB-112) JDK 9 WARNING in Integration Test
[
https://issues.apache.org/jira/browse/MEJB-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MEJB-112.
-
Resolution: Fixed
> JDK 9 WARNING in Integration Test
> -
>
> Key: MEJB-112
> URL: https://issues.apache.org/jira/browse/MEJB-112
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.2.2
>
>
> Currently running on JDK 9 (EA+181) give the following warning during running
> via {{mvn -Prun-its clean verify}}:
> {code}
> [INFO] ..SUCCESS (3.8 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass$3$1
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy/2.0.1/groovy-2.0.1.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass$3$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] ..SUCCESS (4.1 s)
> [INFO] Building: reactor/pom.xml
> [INFO] run script verify.bsh
> [INFO] ..SUCCESS (3.4 s)
> {code}
> Upgrading to maven-invoker-plugin:3.0.1:
> {code}
> [INFO] run post-build script verify.bsh
> [INFO] MEJB-72/pom.xml .. SUCCESS
> (3.7 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run post-build script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy-all/2.4.8/groovy-all-2.4.8.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] mejb-93/pom.xml .. SUCCESS
> (4.1 s)
> [INFO] Building: reactor/pom.xml
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEJB-112) JDK 9 WARNING in Integration Test
[
https://issues.apache.org/jira/browse/MEJB-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MEJB-112:
--
Fix Version/s: 3.2.2
(was: more-investigation)
> JDK 9 WARNING in Integration Test
> -
>
> Key: MEJB-112
> URL: https://issues.apache.org/jira/browse/MEJB-112
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.2.2
>
>
> Currently running on JDK 9 (EA+181) give the following warning during running
> via {{mvn -Prun-its clean verify}}:
> {code}
> [INFO] ..SUCCESS (3.8 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass$3$1
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy/2.0.1/groovy-2.0.1.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass$3$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] ..SUCCESS (4.1 s)
> [INFO] Building: reactor/pom.xml
> [INFO] run script verify.bsh
> [INFO] ..SUCCESS (3.4 s)
> {code}
> Upgrading to maven-invoker-plugin:3.0.1:
> {code}
> [INFO] run post-build script verify.bsh
> [INFO] MEJB-72/pom.xml .. SUCCESS
> (3.7 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run post-build script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy-all/2.4.8/groovy-all-2.4.8.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] mejb-93/pom.xml .. SUCCESS
> (4.1 s)
> [INFO] Building: reactor/pom.xml
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MEJB-138: - Assignee: Sylwester Lachiewicz > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEJB-137: -- Fix Version/s: 3.2.2 > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEJB-138: -- Fix Version/s: 3.2.2 > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MEJB-137: - Assignee: Sylwester Lachiewicz > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MEJB-138) Upgrade parent POM to version 42
Sylwester Lachiewicz created MEJB-138: - Summary: Upgrade parent POM to version 42 Key: MEJB-138 URL: https://issues.apache.org/jira/browse/MEJB-138 Project: Maven EJB Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MEJB-137) Require Maven 3.6.3+
Sylwester Lachiewicz created MEJB-137: - Summary: Require Maven 3.6.3+ Key: MEJB-137 URL: https://issues.apache.org/jira/browse/MEJB-137 Project: Maven EJB Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MCHANGELOG-144) svn and maven-changelog-plugin results in “The filename, directory name, or volume label syntax is incorrect”
[
https://issues.apache.org/jira/browse/MCHANGELOG-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MCHANGELOG-144.
---
Resolution: Information Provided
> svn and maven-changelog-plugin results in “The filename, directory name, or
> volume label syntax is incorrect”
> -
>
> Key: MCHANGELOG-144
> URL: https://issues.apache.org/jira/browse/MCHANGELOG-144
> Project: Maven Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows Server 2016
> maven 3.5.2
>Reporter: Adrian Wyssmann
>Priority: Major
>
> We are using maven-changelog-plugin:2.3 to generate the changelog. The job is
> triggered by Jenkins but recently the job starts failing. Here is what I see
> in the log
> {code:java}
> ...
> ...
> 22:05:41 [DEBUG] Multipage report: 0 subreports
> 22:05:41 [DEBUG] Generating
> D:\jenkins\workspace\MAVEN-Company-Project\target\site\changelog.html
> 22:05:41 [INFO] Generating "Change Log" report---
> maven-changelog-plugin:2.3:changelog
> 22:05:41 [INFO] Generating changed sets xml to:
> D:\jenkins\workspace\MAVEN-Company-Project\target\changelog.xml
> 22:05:41 [INFO] Executing: cmd.exe /X /C "svn --username CIUSER --password
> * --no-auth-cache --non-interactive log -v -r "{2018-01-29 21:05:41
> +}:{2018-03-01 21:05:41 +}"
> http://svn.mycompany.intra:80/svn/parentpom/trunk/;
> 22:05:41 [INFO] Working directory: D:\jenkins\workspace\MAVEN-Company-Project
> 22:05:41 [ERROR] Provider message:
> 22:05:41 [ERROR] The svn command failed.
> 22:05:41 [ERROR] Command output:
> 22:05:41 [ERROR] The filename, directory name, or volume label syntax is
> incorrect.
> 22:05:41
> 22:05:41 [INFO]
>
> 22:05:41 [INFO] BUILD FAILURE
> 22:05:41 [INFO]
>
> 22:05:41 [INFO] Total time: 13.994 s
> 22:05:41 [INFO] Finished at: 2018-02-28T22:05:41+01:00
> 22:05:41 [INFO] Final Memory: 43M/451M
> 22:05:41 [INFO]
>
> 22:05:41 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on project
> mycompany: Error generating maven-changelog-plugin:2.3:changelog: An error
> has occurred during changelog command : : Command failed. -> [Help 1]
> 22:05:41 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-site-plugin:3.6:site
> (default-cli) on project mycompany: Error generating
> maven-changelog-plugin:2.3:changelog: An error has occurred during changelog
> command :
> 22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> 22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> 22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> 22:05:41 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> 22:05:41 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> 22:05:41 at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> 22:05:41 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> ...{code}
> Running the command manually in the workspace directory
> D:\jenkins\workspace\MAVEN-Company-Project\ works without problems.
> The problems occurs in conjunction with maven 3.5.2. When switching back to
> maven 3.1.1 the error does not appear.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MCHANGELOG-128) Remove the unused commentFormat parameter from changelog mojo
[ https://issues.apache.org/jira/browse/MCHANGELOG-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGELOG-128. --- Resolution: Fixed > Remove the unused commentFormat parameter from changelog mojo > - > > Key: MCHANGELOG-128 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-128 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2, 2.3 >Reporter: Martin D'Aloia >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.0.0 > > Attachments: remove-commentFormat-parameter.patch > > > The parameter commentFormat on the changelog mojo is unused and the javadoc > says that it is used by ClearcaseChangeLogGenerator which not exists on the > project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCHANGELOG-128) Remove the unused commentFormat parameter from changelog mojo
[ https://issues.apache.org/jira/browse/MCHANGELOG-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MCHANGELOG-128: --- Assignee: Sylwester Lachiewicz > Remove the unused commentFormat parameter from changelog mojo > - > > Key: MCHANGELOG-128 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-128 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2, 2.3 >Reporter: Martin D'Aloia >Assignee: Sylwester Lachiewicz >Priority: Trivial > Attachments: remove-commentFormat-parameter.patch > > > The parameter commentFormat on the changelog mojo is unused and the javadoc > says that it is used by ClearcaseChangeLogGenerator which not exists on the > project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-128) Remove the unused commentFormat parameter from changelog mojo
[ https://issues.apache.org/jira/browse/MCHANGELOG-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-128: Fix Version/s: 3.0.0 > Remove the unused commentFormat parameter from changelog mojo > - > > Key: MCHANGELOG-128 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-128 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2, 2.3 >Reporter: Martin D'Aloia >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.0.0 > > Attachments: remove-commentFormat-parameter.patch > > > The parameter commentFormat on the changelog mojo is unused and the javadoc > says that it is used by ClearcaseChangeLogGenerator which not exists on the > project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCHANGELOG-151) Migrate plugin to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MCHANGELOG-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MCHANGELOG-151: --- Assignee: Sylwester Lachiewicz > Migrate plugin to Maven 3.6.3 > - > > Key: MCHANGELOG-151 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-151 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > > * Replacing usage of deprecated APIs > * Renaming the packages to org.apache.maven.plugins > * Removing Maven 2 specific code > * Fixing Javadoc comments > * Removing the use of raw types where possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MCHANGELOG-151) Migrate plugin to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MCHANGELOG-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGELOG-151. --- Resolution: Fixed > Migrate plugin to Maven 3.6.3 > - > > Key: MCHANGELOG-151 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-151 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > > * Replacing usage of deprecated APIs > * Renaming the packages to org.apache.maven.plugins > * Removing Maven 2 specific code > * Fixing Javadoc comments > * Removing the use of raw types where possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-151) Migrate plugin to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MCHANGELOG-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-151: Fix Version/s: 3.0.0 > Migrate plugin to Maven 3.6.3 > - > > Key: MCHANGELOG-151 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-151 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > > * Replacing usage of deprecated APIs > * Renaming the packages to org.apache.maven.plugins > * Removing Maven 2 specific code > * Fixing Javadoc comments > * Removing the use of raw types where possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-151) Migrate plugin to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MCHANGELOG-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-151: Summary: Migrate plugin to Maven 3.6.3 (was: Migrate plugin to Maven 3.2.5) > Migrate plugin to Maven 3.6.3 > - > > Key: MCHANGELOG-151 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-151 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Major > > * Replacing usage of deprecated APIs > * Renaming the packages to org.apache.maven.plugins > * Removing Maven 2 specific code > * Fixing Javadoc comments > * Removing the use of raw types where possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MCHANGELOG-154) Update parent pom to 42
[ https://issues.apache.org/jira/browse/MCHANGELOG-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGELOG-154. --- Resolution: Fixed > Update parent pom to 42 > --- > > Key: MCHANGELOG-154 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-154 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCHANGELOG-154) Update parent pom to 42
[ https://issues.apache.org/jira/browse/MCHANGELOG-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MCHANGELOG-154: --- Assignee: Sylwester Lachiewicz > Update parent pom to 42 > --- > > Key: MCHANGELOG-154 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-154 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-154) Update parent pom to 42
[ https://issues.apache.org/jira/browse/MCHANGELOG-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-154: Fix Version/s: 3.0.0 > Update parent pom to 42 > --- > > Key: MCHANGELOG-154 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-154 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-154) Update parent pom to 42
[ https://issues.apache.org/jira/browse/MCHANGELOG-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-154: Summary: Update parent pom to 42 (was: Update parent pom to 39) > Update parent pom to 42 > --- > > Key: MCHANGELOG-154 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-154 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCHANGELOG-155) Require Java 8
[ https://issues.apache.org/jira/browse/MCHANGELOG-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MCHANGELOG-155: --- Assignee: Sylwester Lachiewicz > Require Java 8 > -- > > Key: MCHANGELOG-155 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-155 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MCHANGELOG-155) Require Java 8
[ https://issues.apache.org/jira/browse/MCHANGELOG-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGELOG-155. --- Resolution: Fixed > Require Java 8 > -- > > Key: MCHANGELOG-155 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-155 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-146) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MCHANGELOG-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-146: Fix Version/s: 3.0.0 (was: future-release) > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MCHANGELOG-146 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-146 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Affects Versions: future-release >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-138) Upgrade to newest Maven SCM
[ https://issues.apache.org/jira/browse/MCHANGELOG-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-138: Fix Version/s: 3.0.0 (was: future-release) > Upgrade to newest Maven SCM > --- > > Key: MCHANGELOG-138 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-138 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > May be do this after the current release has made it to central. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-155) Require Java 8
[ https://issues.apache.org/jira/browse/MCHANGELOG-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-155: Fix Version/s: future-release > Require Java 8 > -- > > Key: MCHANGELOG-155 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-155 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: future-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
