[jira] [Commented] (MPOM-215) Create a new parent POM to lock down plugins versions of default lifecycle bindings
[ https://issues.apache.org/jira/browse/MPOM-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253318#comment-17253318 ] Herve Boutemy commented on MPOM-215: the fact that there is an issue to have a simple way of locking plugins: yes the solution of a parent POM: there is no real agreement on any solution yet issue will appear more once Maven 4 is released, then warnings appear: perhaps at that time there will be energy to look for solutions > Create a new parent POM to lock down plugins versions of default lifecycle > bindings > --- > > Key: MPOM-215 > URL: https://issues.apache.org/jira/browse/MPOM-215 > Project: Maven POMs > Issue Type: New Feature >Reporter: Herve Boutemy >Priority: Major > > while working on version upgrade of default plugin bindings, we found that: > 1. a warning should be displayed MNG-6562 > 2. a parent POM would be the easiest solution to lock down every plugins at > once, instead of letting users lock down each plugin separately > let's create this parent POM -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-200) remove Apache Resource Bundles parent POM
[ https://issues.apache.org/jira/browse/MPOM-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253316#comment-17253316 ] Herve Boutemy commented on MPOM-200: see https://lists.apache.org/thread.html/re427294dcd348bd8a991c6e502fbc3f9d5f030f942d7c261c31825e5%40%3Cdev.maven.apache.org%3E > remove Apache Resource Bundles parent POM > - > > Key: MPOM-200 > URL: https://issues.apache.org/jira/browse/MPOM-200 > Project: Maven POMs > Issue Type: Task >Affects Versions: MAVEN-32 >Reporter: Herve Boutemy >Priority: Major > > as part of migration to Git MASFRES-20 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven] rmannibucau commented on pull request #408: [MNG-7045] - Drop useless and outdated cdi-api from maven
rmannibucau commented on pull request #408: URL: https://github.com/apache/maven/pull/408#issuecomment-749390858 I also have some stability issues with testing suite - but even without these PR - but from a first review it looks really unrelated so I would move forward with this PR and maybe open a track about IT to mayve use docker/testcontainers - to have the expected setup which is not trivial and was causing some issues with my local build for ex. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] closed pull request #13: Bump xmlunit-core from 2.7.0 to 2.8.1
dependabot[bot] closed pull request #13: URL: https://github.com/apache/maven-antrun-plugin/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] opened a new pull request #16: Bump xmlunit-core from 2.7.0 to 2.8.2
dependabot[bot] opened a new pull request #16: URL: https://github.com/apache/maven-antrun-plugin/pull/16 Bumps [xmlunit-core](https://github.com/xmlunit/xmlunit) from 2.7.0 to 2.8.2. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases";>xmlunit-core's releases. XMLUnit for Java 2.8.2 This release fixes a bug in the new AssertJ 3.x module. CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210";>#210 by https://github.com/f-lopes";>@f-lopes XMLUnit for Java 2.8.1 The only real change when compared to XMLUnit for Java 2.8.0 is the introduction of a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later in order to address a problem with running AssertJ tests in an OSGi environment. The original xmlunit-assertj module will still be supported. The full changelog of XMLUnit for Java 2.8.1 added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/203";>#203. The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead. The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3. Many thanks to https://github.com/Zegveld";>@Zegveld, https://github.com/scordio";>@scordio and https://github.com/joel-costigliola";>@joel-costigliola. XMLUnit for Java 2.8.0 This release now requires Java 7 for all modules and updates some dependencies - the changed JAXB dependency is a breaking change. It also fixes a few bugs. Details of changes: changed optional JAXB dependency to use Jakarta XML Binding API PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/186";>#186 by https://github.com/endrejeges";>@endrejeges bumped the bytebuddy dependency to 1.10.10 for the AssertJ module in the hope it would help with https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/188";>#188 and change its scope from provided to compile time, which should finally fix the issue. added a new extractingText method to MultipleNodeAssert to make it possible to write AssertJ assertions against the textual content of nodes more easily. Issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/192";>#192 and PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/193";>#193 by https://github.com/keesvandieren";>@keesvandieren changed the minimum Java version required from Java 6 to Java 7 for all modules (it has already been Java 7 for the AssertJ module before). DefaultNodeMatcher with multiple ElementSelectors could fail to find the best matches as the order of ElementSelectors should select them. https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/197";>#197 Input builder now supports java.nio.file.Path https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/196";>#196 ... (truncated) Changelog Sourced from https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md";>xmlunit-core's changelog. XMLUnit for Java 2.8.2 - /Released 2020-12-21/ CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210";>#210 by https://github.com/f-lopes";>@f-lopes XMLUnit for Java 2.8.1 - /Released 2020-11-15/ added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/203";>#203. The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead. The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3. Many thanks to https://github.com/Zegveld";>@Zegveld, https://github.com/scordio";>@scordio and https://github.com/joel-costigliola";>@joel-costigliola. XMLUni
[GitHub] [maven-antrun-plugin] dependabot[bot] commented on pull request #13: Bump xmlunit-core from 2.7.0 to 2.8.1
dependabot[bot] commented on pull request #13: URL: https://github.com/apache/maven-antrun-plugin/pull/13#issuecomment-749350913 Superseded by #16. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] commented on pull request #14: Bump xmlunit-matchers from 2.7.0 to 2.8.1
dependabot[bot] commented on pull request #14: URL: https://github.com/apache/maven-antrun-plugin/pull/14#issuecomment-749350852 Superseded by #15. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] opened a new pull request #15: Bump xmlunit-matchers from 2.7.0 to 2.8.2
dependabot[bot] opened a new pull request #15: URL: https://github.com/apache/maven-antrun-plugin/pull/15 Bumps [xmlunit-matchers](https://github.com/xmlunit/xmlunit) from 2.7.0 to 2.8.2. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases";>xmlunit-matchers's releases. XMLUnit for Java 2.8.2 This release fixes a bug in the new AssertJ 3.x module. CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210";>#210 by https://github.com/f-lopes";>@f-lopes XMLUnit for Java 2.8.1 The only real change when compared to XMLUnit for Java 2.8.0 is the introduction of a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later in order to address a problem with running AssertJ tests in an OSGi environment. The original xmlunit-assertj module will still be supported. The full changelog of XMLUnit for Java 2.8.1 added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/203";>#203. The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead. The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3. Many thanks to https://github.com/Zegveld";>@Zegveld, https://github.com/scordio";>@scordio and https://github.com/joel-costigliola";>@joel-costigliola. XMLUnit for Java 2.8.0 This release now requires Java 7 for all modules and updates some dependencies - the changed JAXB dependency is a breaking change. It also fixes a few bugs. Details of changes: changed optional JAXB dependency to use Jakarta XML Binding API PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/186";>#186 by https://github.com/endrejeges";>@endrejeges bumped the bytebuddy dependency to 1.10.10 for the AssertJ module in the hope it would help with https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/188";>#188 and change its scope from provided to compile time, which should finally fix the issue. added a new extractingText method to MultipleNodeAssert to make it possible to write AssertJ assertions against the textual content of nodes more easily. Issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/192";>#192 and PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/193";>#193 by https://github.com/keesvandieren";>@keesvandieren changed the minimum Java version required from Java 6 to Java 7 for all modules (it has already been Java 7 for the AssertJ module before). DefaultNodeMatcher with multiple ElementSelectors could fail to find the best matches as the order of ElementSelectors should select them. https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/197";>#197 Input builder now supports java.nio.file.Path https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/196";>#196 ... (truncated) Changelog Sourced from https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md";>xmlunit-matchers's changelog. XMLUnit for Java 2.8.2 - /Released 2020-12-21/ CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210";>#210 by https://github.com/f-lopes";>@f-lopes XMLUnit for Java 2.8.1 - /Released 2020-11-15/ added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/203";>#203. The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead. The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3. Many thanks to https://github.com/Zegveld";>@Zegveld, https://github.com/scordio";>@scordio and https://github.com/joel-costigliola";>@joel-costigliola.
[GitHub] [maven-antrun-plugin] dependabot[bot] closed pull request #14: Bump xmlunit-matchers from 2.7.0 to 2.8.1
dependabot[bot] closed pull request #14: URL: https://github.com/apache/maven-antrun-plugin/pull/14 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shade-plugin] dependabot[bot] commented on pull request #77: Bump xmlunit-legacy from 2.7.0 to 2.8.1
dependabot[bot] commented on pull request #77: URL: https://github.com/apache/maven-shade-plugin/pull/77#issuecomment-749325270 Superseded by #81. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shade-plugin] dependabot[bot] opened a new pull request #81: Bump xmlunit-legacy from 2.7.0 to 2.8.2
dependabot[bot] opened a new pull request #81: URL: https://github.com/apache/maven-shade-plugin/pull/81 Bumps [xmlunit-legacy](https://github.com/xmlunit/xmlunit) from 2.7.0 to 2.8.2. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases";>xmlunit-legacy's releases. XMLUnit for Java 2.8.2 This release fixes a bug in the new AssertJ 3.x module. CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210";>#210 by https://github.com/f-lopes";>@f-lopes XMLUnit for Java 2.8.1 The only real change when compared to XMLUnit for Java 2.8.0 is the introduction of a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later in order to address a problem with running AssertJ tests in an OSGi environment. The original xmlunit-assertj module will still be supported. The full changelog of XMLUnit for Java 2.8.1 added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/203";>#203. The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead. The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3. Many thanks to https://github.com/Zegveld";>@Zegveld, https://github.com/scordio";>@scordio and https://github.com/joel-costigliola";>@joel-costigliola. XMLUnit for Java 2.8.0 This release now requires Java 7 for all modules and updates some dependencies - the changed JAXB dependency is a breaking change. It also fixes a few bugs. Details of changes: changed optional JAXB dependency to use Jakarta XML Binding API PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/186";>#186 by https://github.com/endrejeges";>@endrejeges bumped the bytebuddy dependency to 1.10.10 for the AssertJ module in the hope it would help with https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/188";>#188 and change its scope from provided to compile time, which should finally fix the issue. added a new extractingText method to MultipleNodeAssert to make it possible to write AssertJ assertions against the textual content of nodes more easily. Issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/192";>#192 and PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/193";>#193 by https://github.com/keesvandieren";>@keesvandieren changed the minimum Java version required from Java 6 to Java 7 for all modules (it has already been Java 7 for the AssertJ module before). DefaultNodeMatcher with multiple ElementSelectors could fail to find the best matches as the order of ElementSelectors should select them. https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/197";>#197 Input builder now supports java.nio.file.Path https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/196";>#196 ... (truncated) Changelog Sourced from https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md";>xmlunit-legacy's changelog. XMLUnit for Java 2.8.2 - /Released 2020-12-21/ CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210";>#210 by https://github.com/f-lopes";>@f-lopes XMLUnit for Java 2.8.1 - /Released 2020-11-15/ added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/203";>#203. The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead. The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3. Many thanks to https://github.com/Zegveld";>@Zegveld, https://github.com/scordio";>@scordio and https://github.com/joel-costigliola";>@joel-costigliola.
[GitHub] [maven-shade-plugin] dependabot[bot] closed pull request #77: Bump xmlunit-legacy from 2.7.0 to 2.8.1
dependabot[bot] closed pull request #77: URL: https://github.com/apache/maven-shade-plugin/pull/77 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia] dependabot[bot] commented on pull request #44: Bump xmlunit-core from 2.7.0 to 2.8.1
dependabot[bot] commented on pull request #44: URL: https://github.com/apache/maven-doxia/pull/44#issuecomment-749325150 Superseded by #48. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia] dependabot[bot] commented on pull request #45: Bump xmlunit-matchers from 2.7.0 to 2.8.1
dependabot[bot] commented on pull request #45: URL: https://github.com/apache/maven-doxia/pull/45#issuecomment-749325110 Superseded by #47. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] famod opened a new pull request #89: Fix mng-3259 test on JDK 16
famod opened a new pull request #89: URL: https://github.com/apache/maven-integration-testing/pull/89 Popped up here: https://github.com/apache/maven/pull/413#issuecomment-748678853 /cc @michael-o This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] famod edited a comment on pull request #413: [MNG-6843] Thread-safe artifacts in MavenProject
famod edited a comment on pull request #413: URL: https://github.com/apache/maven/pull/413#issuecomment-749262668 @michael-o How come other PRs don't show this failure? I also had a brief look at your Jenkins jobs and I couldn't find anything there either (but I may have looked in the wrong place). I have a fix, simply updating xstream to 1.4.15 in `core-it-suite/src/test/resources/mng-3259/parent/pom.xml` does the trick. ~~Do you want a separate PR for that?~~ _Edit: Of course you do, it's a separate repo._ 🤦 If yes, I hope I don't need a MNG ticket...? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] famod commented on pull request #413: [MNG-6843] Thread-safe artifacts in MavenProject
famod commented on pull request #413: URL: https://github.com/apache/maven/pull/413#issuecomment-749262668 @michael-o How come other PRs don't show this failure? I also had a brief look at your Jenkins jobs and I couldn't find anything there either (but I may have looked in the wrong place). I have a fix, simply updating xstream to 1.4.15 in `core-it-suite/src/test/resources/mng-3259/parent/pom.xml` does the trick. Do you want a separate PR for that? If yes, I hope I don't need a MNG ticket...? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MPH-169) effective-pom should show imported dependencies
[
https://issues.apache.org/jira/browse/MPH-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MPH-169.
Resolution: Invalid
> effective-pom should show imported dependencies
> ---
>
> Key: MPH-169
> URL: https://issues.apache.org/jira/browse/MPH-169
> Project: Maven Help Plugin
> Issue Type: Bug
> Components: effective-pom
>Affects Versions: 3.2.0
>Reporter: Konrad Windszus
>Priority: Major
>
> All dependencies imported like outlined
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
> do not appear in the effective pom.xml currently. They should be resolved
> and listed individually in the effective {{dependencyManagement}} instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MCOMPILER-447) Unable to compile modularized test for a multi-version jar that is not a java module by default
[
https://issues.apache.org/jira/browse/MCOMPILER-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253146#comment-17253146
]
Benjamin Marwell commented on MCOMPILER-447:
[~ccorsi]
Sorry that I just know realized what you actually meant in this issue:
{quote}The following changes resolves two different issues. The first is the
case that
the we are creating a multi-version jar file that by default is not modularized.
{quote}
There is no need to do such a thing. A
{color:#0747a6}{{module-info.class}}{color} in the root folder will be ignored
by Java 7 and Java 8. See the [second example
here|https://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html].
{quote}a multi-version jar file that by default is not modularized.
{quote}
What is the use case here?
> Unable to compile modularized test for a multi-version jar that is not a java
> module by default
> ---
>
> Key: MCOMPILER-447
> URL: https://issues.apache.org/jira/browse/MCOMPILER-447
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.1
>Reporter: Claudio Corsi
>Priority: Blocker
>
> I have a single module project that is creating a mult-version jar file. By
> default the multi-version jar is not a java module because it is being built
> for jdk 7 or newer. The multi-version jar does contain a java module
> definition within the /META-INF/versions/9 directory. I am trying to create
> a integration test that uses the java module of the code. When I tried
> building the module tests I got the UnsupportedOperationException with the
> message:
>
> Can't compile test sources when main sources are missing a module descriptor
>
> The issue was that the main module does not contain a module descriptor but
> the test does contain a module descriptor.
>
> I then forked a copy of the maven compiler plugin. I created an integration
> test and was able to fix this issue. The issue was that I needed to find the
> latest version of the java-module for the module generated multi-version jar
> file. This because the module descriptor and was added to the javac command.
>
> I then tried to build my test source again and this time it stated that it
> was not able to find a class because it is part of a jar file that does not
> contain any java module definition. I updated the integration test and was
> able to add another fix to the forked copy that resolved that issue. The
> issue was that all non-java-module jar files should be included as part of
> the class path. They were all being included as part of the module path.
>
> I then used the fixed jar file to build my project and it failed again
> because of it accessing a unnamed module. I had to finally update my pom to
> include a --add-reads command line option. I will not try to add a fix to
> this issue since this issue has a workaround unlike the other two that didn't.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Moved] (MNG-7055) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MNG-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov moved MSHARED-943 to MNG-7055:
-
Component/s: (was: maven-artifact-transfer)
Plugins and Lifecycle
Artifacts and Repositories
Key: MNG-7055 (was: MSHARED-943)
Project: Maven (was: Maven Shared Components)
> Breaks Maven core integration tests
> ---
>
> Key: MNG-7055
> URL: https://issues.apache.org/jira/browse/MNG-7055
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Plugins and Lifecycle
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253138#comment-17253138
]
Robert Scholte commented on MSHARED-943:
issue is unrelated to maven-artifact-transfer, so go ahead.
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253136#comment-17253136
]
Michael Osipov commented on MSHARED-943:
So this should be moved to MNG and I can perform a release of this component?
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MCOMPILER-444) Dependency that should be on modulepath sometime put on classpath
[
https://issues.apache.org/jira/browse/MCOMPILER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253133#comment-17253133
]
Benjamin Marwell commented on MCOMPILER-444:
Ah, I tried that earlier but missed that I still had
{color:#0747a6}{{true}}{color} active.
🤦🏻♂️ Thanks!
> Dependency that should be on modulepath sometime put on classpath
> -
>
> Key: MCOMPILER-444
> URL: https://issues.apache.org/jira/browse/MCOMPILER-444
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.1
>Reporter: Benjamin Marwell
>Priority: Major
>
> See https://issues.apache.org/jira/browse/MCOMPILER-336
> I can still recreate this with a test dependency.
> I believe the jakarta.activation module should have been on the module path,
> but is only on the classpath. This leads to this error:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project surefire-module-test: Compilation failure
> [ERROR] module not found: jakarta.activation
> {quote}
> demo project: [https://github.com/bmarwell/jaxrs-surefire-module-showcase]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253129#comment-17253129
]
Michael Osipov commented on MSHARED-943:
Thanks, this is really something to be very nice in 4.0.0. Let me know if I can
help.
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253123#comment-17253123
]
Robert Scholte commented on MSHARED-943:
IMO this belongs in Maven itself, not in a library or plugin. I'll need ito
investigate if there is a clean way for plugin artifacts to hook into MAven
Artifact Resolver
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253121#comment-17253121
]
Michael Osipov commented on MSHARED-943:
I agree with that because this is packaging specific. The problem is the it
currently not possible to install or deploy that piece of information with
MINSTALL/MDEPLOY 3.0.0-x. Maven needs this metadata to work properly, so we
have to solve this problem somehow.
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253118#comment-17253118
]
Robert Scholte commented on MSHARED-943:
Artifact Transfer is just a bridge, to make it possible to work with Sonetype
Aether and Eclipse Aether. The logic for plugin metadata doesn't belong there.
I don't know where it should be now.
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MCOMPILER-444) Dependency that should be on modulepath sometime put on classpath
[
https://issues.apache.org/jira/browse/MCOMPILER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253107#comment-17253107
]
Robert Scholte commented on MCOMPILER-444:
--
exclude jaxb-api?
> Dependency that should be on modulepath sometime put on classpath
> -
>
> Key: MCOMPILER-444
> URL: https://issues.apache.org/jira/browse/MCOMPILER-444
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.1
>Reporter: Benjamin Marwell
>Priority: Major
>
> See https://issues.apache.org/jira/browse/MCOMPILER-336
> I can still recreate this with a test dependency.
> I believe the jakarta.activation module should have been on the module path,
> but is only on the classpath. This leads to this error:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project surefire-module-test: Compilation failure
> [ERROR] module not found: jakarta.activation
> {quote}
> demo project: [https://github.com/bmarwell/jaxrs-surefire-module-showcase]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEPLOY-231) Move checksum generation from install to deploy plugin
[
https://issues.apache.org/jira/browse/MDEPLOY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253097#comment-17253097
]
Michael Osipov commented on MDEPLOY-231:
I'd like to partially revert this change because it does not make sense.
MDEPLOY does not create any checksums therefore it does not have to check them.
The checksums are an inplementation detail of MRESOLVER. Consider this example:
{noformat}
mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven-deploy-plugin (master *%=)
$ git status
Auf Branch master
Ihr Branch ist auf demselben Stand wie 'origin/master'.
Unversionierte Dateien:
(benutzen Sie "git add ...", um die Änderungen zum Commit vorzumerken)
src/it/attach-jar-checksum-release/invoker.properties
keine Änderungen zum Commit vorgemerkt (benutzen Sie "git add" und/oder "git
commit -a")
mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven-deploy-plugin (master *%=)
$ cat src/it/attach-jar-checksum-release/invoker.properties
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
invoker.goals = deploy -Daether.checksums.algorithms=SHA-256
{noformat}
output:
{noformat}
[INFO] The post-build script did not succeed.
/var/mosipov/Projekte/maven-deploy-plugin/target/it/attach-jar-checksum-release/target/remoterepo/org/apache/maven/its/deploy/ajc/test/1.0/test-1.0.pom.md5
(No such file or directory)
[INFO] attach-jar-checksum-release/pom.xml .. FAILED (2.5
s)
...
[ERROR] The following builds failed:
[ERROR] * attach-jar-checksum-release/pom.xml
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:27 min
[INFO] Finished at: 2020-12-21T15:08:20+01:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:3.2.1:verify (integration-test)
on project maven-deploy-plugin: 1 build failed. See console output above for
details. -> [Help 1]
{noformat}
> Move checksum generation from install to deploy plugin
> --
>
> Key: MDEPLOY-231
> URL: https://issues.apache.org/jira/browse/MDEPLOY-231
> Project: Maven Deploy Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0-M1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.0-M1
>
>
> It is need to consistently move the checksum generation into
> maven-deploy-plugin which means to change the maven-artifact-transfer
> component accordingly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MCOMPILER-444) Dependency that should be on modulepath sometime put on classpath
[
https://issues.apache.org/jira/browse/MCOMPILER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253091#comment-17253091
]
Benjamin Marwell commented on MCOMPILER-444:
Wow, that was enormously fast! Thanks a lot! I will wait as soon as there is a
plexus-languages release and create a dep update commit here.
Btw, is there a workaround?
> Dependency that should be on modulepath sometime put on classpath
> -
>
> Key: MCOMPILER-444
> URL: https://issues.apache.org/jira/browse/MCOMPILER-444
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.1
>Reporter: Benjamin Marwell
>Priority: Major
>
> See https://issues.apache.org/jira/browse/MCOMPILER-336
> I can still recreate this with a test dependency.
> I believe the jakarta.activation module should have been on the module path,
> but is only on the classpath. This leads to this error:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project surefire-module-test: Compilation failure
> [ERROR] module not found: jakarta.activation
> {quote}
> demo project: [https://github.com/bmarwell/jaxrs-surefire-module-showcase]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MCOMPILER-444) Dependency that should be on modulepath sometime put on classpath
[
https://issues.apache.org/jira/browse/MCOMPILER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253089#comment-17253089
]
Robert Scholte commented on MCOMPILER-444:
--
Found the bug in
https://github.com/codehaus-plexus/plexus-languages/blob/master/plexus-java/src/main/java/org/codehaus/plexus/languages/java/jpms/LocationManager.java#L215
With test dependencies, a second module with the name java.xml.bind is
available: next to jakarta.xml.bind-api,jar there's now also a jaxb-api.jar.
The first one should win, but with the current LocationManager the last one
will win.
> Dependency that should be on modulepath sometime put on classpath
> -
>
> Key: MCOMPILER-444
> URL: https://issues.apache.org/jira/browse/MCOMPILER-444
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.1
>Reporter: Benjamin Marwell
>Priority: Major
>
> See https://issues.apache.org/jira/browse/MCOMPILER-336
> I can still recreate this with a test dependency.
> I believe the jakarta.activation module should have been on the module path,
> but is only on the classpath. This leads to this error:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project surefire-module-test: Compilation failure
> [ERROR] module not found: jakarta.activation
> {quote}
> demo project: [https://github.com/bmarwell/jaxrs-surefire-module-showcase]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-compiler-plugin] bmarwell commented on a change in pull request #36: [MCOMPILER-447] Unable to compile modularized test for a multi-version jar that is not a java module by default
bmarwell commented on a change in pull request #36:
URL:
https://github.com/apache/maven-compiler-plugin/pull/36#discussion_r546900913
##
File path: src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java
##
@@ -319,7 +352,42 @@ else if ( Double.valueOf( getTarget() ) < Double.valueOf(
MODULE_INFO_TARGET ) )
if ( testModuleDescriptor != null )
{
modulepathElements = testPath;
-classpathElements = Collections.emptyList();
+classpathElements = null;
+for ( String path : modulepathElements )
+{
+File file = new File( path );
+if ( file.exists() && ! file.isDirectory() &&
file.getName().endsWith( ".jar" ) )
+{
+// check if the jar file contains the module-info.class
+try
+{
+JarFile jarFile = new JarFile( file );
+if ( jarFile.getJarEntry( "module-info.class" ) ==
null )
+{
+if ( getLog().isDebugEnabled() )
+{
+getLog().debug( "Add non-module jar dependency
" + path
++ " to class path." );
+}
+if ( classpathElements == null )
+{
+classpathElements = new ArrayList();
+}
+// add the path to the classpathElements list.
+classpathElements.add( path );
+}
Review comment:
Well, now you have the same amount of indentation in a loop. But I will
not complain anymore about indentation unless another committer does. ;-)
The comment in the new method is helpful. Nit: You could have added it as
Javadoc while you were at it.
I will check it out locally in a few days to inspect the changes further.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on a change in pull request #82: [MNG-6957] support build/consumer with modules in reverse order
michael-o commented on a change in pull request #82:
URL:
https://github.com/apache/maven-integration-testing/pull/82#discussion_r546899813
##
File path:
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5576CdFriendlyVersions.java
##
@@ -66,4 +67,33 @@ public void
testContinuousDeliveryFriendlyVersionsAreWarningFree()
}
}
+/**
+ * Verifies that property references with dotted notation work within
+ * POM interpolation.
+ */
+public void
testContinuousDeliveryFriendlyVersionsAreWarningFreeWithBuildConsumer()
+throws Exception
+{
+File testDir = ResourceExtractor.simpleExtractResources( getClass(),
"/mng-5576-cd-friendly-versions" );
+
+Verifier verifier = newVerifier( testDir.getAbsolutePath() );
+verifier.setLogFileName( "log-bc.txt" );
+verifier.setAutoclean( false );
+verifier.deleteDirectory( "target" );
+verifier.addCliOption( "-Dchangelist=changelist" );
+verifier.addCliOption( "-Dmaven.experimental.buildconsumer=true" );
+verifier.executeGoal( "validate" );
+verifier.verifyErrorFreeLog();
+verifier.resetStreams();
+
+Properties props = verifier.loadProperties( "target/pom.properties" );
+assertEquals( "1.0.0.changelist", props.getProperty( "project.version"
) );
+
+List lines = verifier.loadFile( new File( testDir,
"log-bc.txt" ), false );
+for( String line : lines )
Review comment:
Indeed!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253079#comment-17253079
]
Michael Osipov commented on MSHARED-943:
It seems, but it is not. Artifact Manager did take care of plugin metadata in
the repo while Artifact Transfer does not anymore. Can we completely get rid of
Artifact Transfer?
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MCOMPILER-444) Dependency that should be on modulepath sometime put on classpath
[
https://issues.apache.org/jira/browse/MCOMPILER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253075#comment-17253075
]
Robert Scholte commented on MCOMPILER-444:
--
Comparing both module paths, it looks like the following line disappears during
test-compile:
[DEBUG]
d:\maven_repo\.m2\repository\jakarta\activation\jakarta.activation-api\1.2.2\jakarta.activation-api-1.2.2.jar
> Dependency that should be on modulepath sometime put on classpath
> -
>
> Key: MCOMPILER-444
> URL: https://issues.apache.org/jira/browse/MCOMPILER-444
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.8.1
>Reporter: Benjamin Marwell
>Priority: Major
>
> See https://issues.apache.org/jira/browse/MCOMPILER-336
> I can still recreate this with a test dependency.
> I believe the jakarta.activation module should have been on the module path,
> but is only on the classpath. This leads to this error:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) on project surefire-module-test: Compilation failure
> [ERROR] module not found: jakarta.activation
> {quote}
> demo project: [https://github.com/bmarwell/jaxrs-surefire-module-showcase]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-compiler-plugin] ccorsi commented on a change in pull request #36: [MCOMPILER-447] Unable to compile modularized test for a multi-version jar that is not a java module by default
ccorsi commented on a change in pull request #36:
URL:
https://github.com/apache/maven-compiler-plugin/pull/36#discussion_r546883926
##
File path: src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java
##
@@ -319,7 +352,42 @@ else if ( Double.valueOf( getTarget() ) < Double.valueOf(
MODULE_INFO_TARGET ) )
if ( testModuleDescriptor != null )
{
modulepathElements = testPath;
-classpathElements = Collections.emptyList();
+classpathElements = null;
+for ( String path : modulepathElements )
+{
+File file = new File( path );
+if ( file.exists() && ! file.isDirectory() &&
file.getName().endsWith( ".jar" ) )
+{
+// check if the jar file contains the module-info.class
+try
+{
+JarFile jarFile = new JarFile( file );
+if ( jarFile.getJarEntry( "module-info.class" ) ==
null )
+{
+if ( getLog().isDebugEnabled() )
+{
+getLog().debug( "Add non-module jar dependency
" + path
++ " to class path." );
+}
+if ( classpathElements == null )
+{
+classpathElements = new ArrayList();
+}
+// add the path to the classpathElements list.
+classpathElements.add( path );
+}
Review comment:
I went a step further, I ended up extracting the for loop into a
separate method.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Closed] (MDOCCK-34) make build Reproducible
[ https://issues.apache.org/jira/browse/MDOCCK-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDOCCK-34. Resolution: Fixed Fixed in [610e70f4532ad2d264a14ad4741c725b68d36a01|https://gitbox.apache.org/repos/asf?p=maven-docck-plugin.git;a=commit;h=610e70f4532ad2d264a14ad4741c725b68d36a01] > make build Reproducible > --- > > Key: MDOCCK-34 > URL: https://issues.apache.org/jira/browse/MDOCCK-34 > Project: Maven Documentation Checker Plugin > Issue Type: Improvement >Affects Versions: 1.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MJDEPRSCAN-2) make build Reproducible
[ https://issues.apache.org/jira/browse/MJDEPRSCAN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MJDEPRSCAN-2. --- Resolution: Fixed Fixed in [7ca566abc25bef95d6e203f4fcf72c50b68d124d|https://gitbox.apache.org/repos/asf?p=maven-jdeprscan-plugin.git;a=commit;h=7ca566abc25bef95d6e203f4fcf72c50b68d124d] > make build Reproducible > --- > > Key: MJDEPRSCAN-2 > URL: https://issues.apache.org/jira/browse/MJDEPRSCAN-2 > Project: Maven JDeprScan Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-alpha-1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-jlink-plugin] dependabot[bot] commented on pull request #27: Bump mavenVersion from 3.1.1 to 3.6.3
dependabot[bot] commented on pull request #27: URL: https://github.com/apache/maven-jlink-plugin/pull/27#issuecomment-749102699 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] bmarwell closed pull request #27: Bump mavenVersion from 3.1.1 to 3.6.3
bmarwell closed pull request #27: URL: https://github.com/apache/maven-jlink-plugin/pull/27 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rfscholte commented on a change in pull request #391: Mng 6957: Support Build Consumer while defining modules in reverse order
rfscholte commented on a change in pull request #391:
URL: https://github.com/apache/maven/pull/391#discussion_r546808802
##
File path:
maven-core/src/main/java/org/apache/maven/project/ReactorModelCache.java
##
@@ -113,7 +107,48 @@ public int hashCode()
{
return hashCode;
}
+}
+
+private static final class GACacheKey
+{
+private final String groupId;
+
+private final String artifactId;
+
+private final int hashCode;
+GACacheKey( String groupId, String artifactId )
+{
+super();
Review comment:
yes, it is there already implicitly, but I'll remove it.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-integration-testing] rfscholte commented on a change in pull request #82: [MNG-6957] support build/consumer with modules in reverse order
rfscholte commented on a change in pull request #82:
URL:
https://github.com/apache/maven-integration-testing/pull/82#discussion_r546804763
##
File path:
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5576CdFriendlyVersions.java
##
@@ -66,4 +67,33 @@ public void
testContinuousDeliveryFriendlyVersionsAreWarningFree()
}
}
+/**
+ * Verifies that property references with dotted notation work within
+ * POM interpolation.
+ */
+public void
testContinuousDeliveryFriendlyVersionsAreWarningFreeWithBuildConsumer()
+throws Exception
+{
+File testDir = ResourceExtractor.simpleExtractResources( getClass(),
"/mng-5576-cd-friendly-versions" );
+
+Verifier verifier = newVerifier( testDir.getAbsolutePath() );
+verifier.setLogFileName( "log-bc.txt" );
+verifier.setAutoclean( false );
+verifier.deleteDirectory( "target" );
+verifier.addCliOption( "-Dchangelist=changelist" );
+verifier.addCliOption( "-Dmaven.experimental.buildconsumer=true" );
+verifier.executeGoal( "validate" );
+verifier.verifyErrorFreeLog();
+verifier.resetStreams();
+
+Properties props = verifier.loadProperties( "target/pom.properties" );
+assertEquals( "1.0.0.changelist", props.getProperty( "project.version"
) );
+
+List lines = verifier.loadFile( new File( testDir,
"log-bc.txt" ), false );
+for( String line : lines )
Review comment:
It has never been implemented and it is a shared component, so requires
an extra step to make it available. See
https://maven.apache.org/shared/maven-verifier/apidocs/org/apache/maven/it/Verifier.html
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-compiler-plugin] bmarwell commented on a change in pull request #36: [MCOMPILER-447] Unable to compile modularized test for a multi-version jar that is not a java module by default
bmarwell commented on a change in pull request #36:
URL:
https://github.com/apache/maven-compiler-plugin/pull/36#discussion_r546799029
##
File path: src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java
##
@@ -319,7 +352,42 @@ else if ( Double.valueOf( getTarget() ) < Double.valueOf(
MODULE_INFO_TARGET ) )
if ( testModuleDescriptor != null )
{
modulepathElements = testPath;
-classpathElements = Collections.emptyList();
+classpathElements = null;
+for ( String path : modulepathElements )
+{
+File file = new File( path );
+if ( file.exists() && ! file.isDirectory() &&
file.getName().endsWith( ".jar" ) )
+{
+// check if the jar file contains the module-info.class
+try
+{
+JarFile jarFile = new JarFile( file );
+if ( jarFile.getJarEntry( "module-info.class" ) ==
null )
+{
+if ( getLog().isDebugEnabled() )
+{
+getLog().debug( "Add non-module jar dependency
" + path
++ " to class path." );
+}
+if ( classpathElements == null )
+{
+classpathElements = new ArrayList();
+}
+// add the path to the classpathElements list.
+classpathElements.add( path );
+}
Review comment:
Yes that is what I had in mind. A small comment why stuff happens there
would be helpful as well. I would start a little above in the "try" statement
with the comment: `// check if the jar file contains the
module-info.class.`.
I think the whole try statement would make a nice method. A simple comment
why the jars are explicitly added to the classpath would absolutely suffice.
Also:
`new ArrayList();` -- you can just use the diamond operator: `new
ArrayList<>();`. We are on Java 7, not 5. ;-)
Thanks!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252946#comment-17252946
]
Robert Scholte commented on MSHARED-943:
Looking at it, this looks like this is the start of dropping the Maven2
mechanism to install artifacts and to start using Aether/Maven Artifact
Resolver. Looks unrelated to the error.
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-dependency-plugin] asfgit closed pull request #117: Bump wagon-http-lightweight from 3.4.0 to 3.4.2
asfgit closed pull request #117: URL: https://github.com/apache/maven-dependency-plugin/pull/117 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #117: Bump wagon-http-lightweight from 3.4.0 to 3.4.2
dependabot[bot] commented on pull request #117: URL: https://github.com/apache/maven-dependency-plugin/pull/117#issuecomment-749027405 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] ofarganc opened a new pull request #64: [MJAVADOC-667] Fix broken links in Javadocs comments and site page.
ofarganc opened a new pull request #64: URL: https://github.com/apache/maven-javadoc-plugin/pull/64 Following this checklist to help us incorporate your contribution quickly and easily: - [X ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAVADOC) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X ] Each commit in the pull request should have a meaningful subject line and body. - [X ] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MJAVADOC-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X ] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [X ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MDEPLOY-258) Unable to deploy artifacts of package type bundle
[
https://issues.apache.org/jira/browse/MDEPLOY-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEPLOY-258.
--
Resolution: Incomplete
No reaction for a year.
> Unable to deploy artifacts of package type bundle
> -
>
> Key: MDEPLOY-258
> URL: https://issues.apache.org/jira/browse/MDEPLOY-258
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 3.0.0-M1
> Environment: Windows 10, Maven 3.5.3, Java 1.8
>Reporter: George McCone
>Priority: Major
>
> We have a mixture of artifacts that are basic java jar and osgi bundles. When
> perfoming a deploy:deploy on the bundle project and specifying the
> -DaltDeploymentRepository, we receive the following error.
> {code:java}
> Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy)
> on project com.test.dummy: ArtifactDeployerException: Failed to retrieve
> remote metadata
> com.test.dummy:com.test.dummy:1.0.1-SNAPSHOT/maven-metadata.xml: Could not
> transfer metadata
> com.test.dummy:com.test.dummy:1.0.1-SNAPSHOT/maven-metadata.xml from/to
> snapshots::default (http://repo01:8081/artifactory/libs-snapshot-local):
> C:\Users\svc-jenkins\.m2\repository\com.test.dummy\com.test.dummy\1.0.1-SNAPSHOT\maven-metadata-snapshots::default.xml.part.lock
> (The filename, directory name, or volume label syntax is incorrect) -> [Help
> 1]
> {code}
> Previous artifacts in the project properly deployed, but these artifacts were
> of packaging jar, fails on the first artifact of packaging of type bundle.
> Same error occurs is we try and deploy just the bundle artifact as well.
> if we specify the altDeploymentRepository within the
> section of the pom instead of a -D parameter it works.
> If I change the package type from bundle to jar and use the -D parameter, the
> artifact then deploys properly, but then the maven-bundle-plugin then doesn't
> properly generate the MANIFEST.MF file.
> Example of the parameter that fails.
> -DaltDeploymentRepository=snapshots::default::http://repo01:8081/artifactory/libs-snapshot-local
>
> pom file exhibiting the problem.
>
> {noformat}
> 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
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
>
> com.test.dummy
> dummy-parent
> 1.0.1-SNAPSHOT
>
> com.test.dummy
> bundle
>
>
>
> org.apache.felix
> maven-bundle-plugin
> 4.2.0
> true
>
> META-INF
>
>
> dummy-foss;scope=compile|runtime
> com.test.dummy,
> com.test.dummy.annotation,
> com.test.dummy.statistics
>
>
>
>
>
>
>
> com.test.dummy
> dummy-annotations
> 1.0.1-SNAPSHOT
>
>
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MJAVADOC-667) Broken links in javadoc comments
Oscar Farga created MJAVADOC-667: Summary: Broken links in javadoc comments Key: MJAVADOC-667 URL: https://issues.apache.org/jira/browse/MJAVADOC-667 Project: Maven Javadoc Plugin Issue Type: Bug Reporter: Oscar Farga Some class references in the javadocs comments are pointing to the wrong package ./apidocs/org/apache/maven/plugin/javadoc/options/Group.html where it should be /apidocs/org/apache/maven/plugins/javadoc/options/Group.html There are 11 occurrences of this bug in the AbstractJavadocMojo and 1 in the faq.apt file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-compiler-plugin] ccorsi commented on a change in pull request #36: [MCOMPILER-447] Unable to compile modularized test for a multi-version jar that is not a java module by default
ccorsi commented on a change in pull request #36:
URL:
https://github.com/apache/maven-compiler-plugin/pull/36#discussion_r546706179
##
File path: src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java
##
@@ -319,7 +352,42 @@ else if ( Double.valueOf( getTarget() ) < Double.valueOf(
MODULE_INFO_TARGET ) )
if ( testModuleDescriptor != null )
{
modulepathElements = testPath;
-classpathElements = Collections.emptyList();
+classpathElements = null;
+for ( String path : modulepathElements )
+{
+File file = new File( path );
+if ( file.exists() && ! file.isDirectory() &&
file.getName().endsWith( ".jar" ) )
+{
+// check if the jar file contains the module-info.class
+try
+{
+JarFile jarFile = new JarFile( file );
+if ( jarFile.getJarEntry( "module-info.class" ) ==
null )
+{
+if ( getLog().isDebugEnabled() )
+{
+getLog().debug( "Add non-module jar dependency
" + path
++ " to class path." );
+}
+if ( classpathElements == null )
+{
+classpathElements = new ArrayList();
+}
+// add the path to the classpathElements list.
+classpathElements.add( path );
+}
Review comment:
Not sure exactly how you want me to refactor this code. The build
checkstyle definition forced me into this code style. I did combine the debug
statement within a single line. The only other option is to extract this set
of code and create a private method. That would reduce the indentation. Is
this what you were thinking?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-compiler-plugin] ccorsi commented on a change in pull request #36: [MCOMPILER-447] Unable to compile modularized test for a multi-version jar that is not a java module by default
ccorsi commented on a change in pull request #36:
URL:
https://github.com/apache/maven-compiler-plugin/pull/36#discussion_r546704475
##
File path: src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java
##
@@ -319,7 +352,42 @@ else if ( Double.valueOf( getTarget() ) < Double.valueOf(
MODULE_INFO_TARGET ) )
if ( testModuleDescriptor != null )
{
modulepathElements = testPath;
-classpathElements = Collections.emptyList();
+classpathElements = null;
+for ( String path : modulepathElements )
+{
+File file = new File( path );
+if ( file.exists() && ! file.isDirectory() &&
file.getName().endsWith( ".jar" ) )
+{
+// check if the jar file contains the module-info.class
+try
+{
+JarFile jarFile = new JarFile( file );
+if ( jarFile.getJarEntry( "module-info.class" ) ==
null )
+{
+if ( getLog().isDebugEnabled() )
+{
+getLog().debug( "Add non-module jar dependency
" + path
++ " to class path." );
+}
+if ( classpathElements == null )
+{
+classpathElements = new ArrayList();
Review comment:
Done
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-compiler-plugin] ccorsi commented on a change in pull request #36: [MCOMPILER-447] Unable to compile modularized test for a multi-version jar that is not a java module by default
ccorsi commented on a change in pull request #36: URL: https://github.com/apache/maven-compiler-plugin/pull/36#discussion_r546704328 ## File path: src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java ## @@ -27,11 +27,13 @@ import java.util.Collection; import java.util.Collections; import java.util.HashSet; +import java.util.Iterator; Review comment: Done. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252859#comment-17252859
]
Michael Osipov commented on MSHARED-943:
[~rfscholte], I know it has been many years, but do you remember anything
special with that change?
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252849#comment-17252849
]
Michael Osipov edited comment on MSHARED-943 at 12/21/20, 1:21 PM:
---
I did more investigation and the cause of this is:
{noformat}
commit 55f1f640dff5e2dbdd44d53949bb0735a7e78d26
Author: Robert Scholte
Date: 2015-10-11T20:39:20+02:00
Merge with 3.0-branch
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@1708008
13f79535-47bb-0310-9956-ffa450edef68
{noformat}
With this change Maven Artifact Manager has been replaced with Manager Artifact
Transfer. It does not touch group repository metadata at all, it simply ignores
plugins.
was (Author: michael-o):
I did more investigation and the cause of this is:
{noformat}
commit 55f1f640dff5e2dbdd44d53949bb0735a7e78d26
Author: Robert Scholte
Date: 2015-10-11T20:39:20+02:00
Merge with 3.0-branch
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@1708008
13f79535-47bb-0310-9956-ffa450edef68
{noformat}
With this change Maven Artifact Manager has been replaced with Manager Artifact
Transfer. It does not touch group repository metadata at all.
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.j
[jira] [Commented] (MSHARED-943) Breaks Maven core integration tests
[
https://issues.apache.org/jira/browse/MSHARED-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252849#comment-17252849
]
Michael Osipov commented on MSHARED-943:
I did more investigation and the cause of this is:
{noformat}
commit 55f1f640dff5e2dbdd44d53949bb0735a7e78d26
Author: Robert Scholte
Date: 2015-10-11T20:39:20+02:00
Merge with 3.0-branch
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@1708008
13f79535-47bb-0310-9956-ffa450edef68
{noformat}
With this change Maven Artifact Manager has been replaced with Manager Artifact
Transfer. It does not touch group repository metadata at all.
> Breaks Maven core integration tests
> ---
>
> Key: MSHARED-943
> URL: https://issues.apache.org/jira/browse/MSHARED-943
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Reporter: Elliotte Rusty Harold
>Priority: Blocker
>
> Copying @mosipov's comment from mailing list on HEAD with Maven core ITs:
> https://markmail.org/message/ggcioupa6yaet4xe#query:+page:1+mid:noyp5d3iyclrfgyp+state:results
> {noformat}[ERROR] Tests run: 834, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 287.261 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testitMNG3372(org.apache.maven.it.MavenITmng3372DirectInvocationOfPluginsTest)
> Time elapsed: 1.5 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -s
> /var/osipovmi/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3372/direct-using-prefix/settings.xml
> -e --batch-mode
> -Dmaven.repo.local=/net/home/osipovmi/var/Projekte/maven-integration-testing/repo
> mng3372:test
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for
> org.apache.maven.its.mng3372:project:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins [maven-clean-plugin,
> maven-resources-plugin, maven-jar-plugin, maven-compiler-plugin,
> maven-surefire-plugin, maven-install-plugin, maven-deploy-plugin,
> maven-site-plugin], you should define versions in pluginManagement section of
> your pom.xml or parent @ line 6, column 14
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/its/mng3372/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloading from central:
> file:target/null/org/codehaus/mojo/maven-metadata.xml
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.056 s
> [INFO] Finished at: 2020-06-04T22:03:01+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'mng3372' in the current project and in the
> plugin groups [org.apache.maven.its.mng3372, org.apache.maven.plugins,
> org.codehaus.mojo] available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)] -> [Help 1]
> org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin
> found
> for prefix 'mng3372' in the current project and in the plugin groups
> [org.apache.maven.its.mng3372, org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local
> (/net/home/osipovmi/var/Projekte/maven-integration-testing/repo), central
> (file:target/null)]
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:98)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:269)
> at
> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescript{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MDEP-732) unpack - artifactItem type attribute ignored
Zoltán Forgó created MDEP-732:
-
Summary: unpack - artifactItem type attribute ignored
Key: MDEP-732
URL: https://issues.apache.org/jira/browse/MDEP-732
Project: Maven Dependency Plugin
Issue Type: Bug
Components: unpack
Affects Versions: 3.1.2
Reporter: Zoltán Forgó
If an existing artifact which has other types (e.g. test-jar) needs to be
unpacked the type attribute is getting ignored. Always jar type used.
{code:xml}
org.apache.maven.plugins
maven-dependency-plugin
3.1.2
share-tests
generate-test-sources
unpack
io.github.zforgo.stackoverflow
shared-tests
0.1.0-SNAPSHOT
test-jar
${project.build.directory}/alternateLocation
{code}
While running {{mvn install}} the log says
{noformat}
[INFO]
[INFO] --- maven-dependency-plugin:3.1.2:unpack (share-tests) @ project ---
[INFO] Configured Artifact:
io.github.zforgo.stackoverflow:shared-tests:0.1.0-SNAPSHOT:test-jar
[INFO] Unpacking [...]
shared-tests/0.1.0-SNAPSHOT/shared-tests-0.1.0-SNAPSHOT.jar to [...] with
includes "" and excludes ""
[INFO]
{noformat}
It seems {{ArtifactItem}} was configured well but the {{Artifact}} is wrong.
After some debugging it seems {{AbstractFromConfigurationMojo}} didn't set type
attribute when creating {{Artifact}} from {{ArtifactItem}}.
Related code:
{code:java}
protected Artifact getArtifact( ArtifactItem artifactItem )
throws MojoExecutionException
{
Artifact artifact;
try
{
// ...
ProjectBuildingRequest buildingRequest =
newResolveArtifactProjectBuildingRequest();
if ( localRepositoryDirectory != null )
{
buildingRequest =
repositoryManager.setLocalRepositoryBasedir(
buildingRequest, localRepositoryDirectory );
}
// Map dependency to artifact coordinate
DefaultArtifactCoordinate coordinate = new
DefaultArtifactCoordinate();
coordinate.setGroupId( artifactItem.getGroupId() );
coordinate.setArtifactId( artifactItem.getArtifactId() );
coordinate.setVersion( artifactItem.getVersion() );
coordinate.setClassifier( artifactItem.getClassifier() );
final String extension;
ArtifactHandler artifactHandler =
artifactHandlerManager.getArtifactHandler( artifactItem.getType() );
//...
}
catch ( ArtifactResolverException e )
{
throw new MojoExecutionException( "Unable to find/resolve
artifact.", e );
}
return artifact;
}{code}
The {{DefaultArtifactCoordinate}} sets type to {{jar}} and there is no place
where it was updated. Because of this wrong artifact will be unpacked.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MPOM-257) Upgrade maven-ear-plugin to 3.1.0
[ https://issues.apache.org/jira/browse/MPOM-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPOM-257: - Assignee: Sylwester Lachiewicz > Upgrade maven-ear-plugin to 3.1.0 > - > > Key: MPOM-257 > URL: https://issues.apache.org/jira/browse/MPOM-257 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MPOM-256) Drop org.codehaus.mojo:clirr-maven-plugin
[ https://issues.apache.org/jira/browse/MPOM-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPOM-256: - Assignee: Sylwester Lachiewicz > Drop org.codehaus.mojo:clirr-maven-plugin > - > > Key: MPOM-256 > URL: https://issues.apache.org/jira/browse/MPOM-256 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > > Remove deprecated plugin without support for newer Java versions. > > Latest releases: > clirr-maven-plugin 2.8 2016-09-13 > Clirr latest release: 06 2005-10-27 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-200) remove Apache Resource Bundles parent POM
[ https://issues.apache.org/jira/browse/MPOM-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252799#comment-17252799 ] Sylwester Lachiewicz commented on MPOM-200: --- How to do the migration? > remove Apache Resource Bundles parent POM > - > > Key: MPOM-200 > URL: https://issues.apache.org/jira/browse/MPOM-200 > Project: Maven POMs > Issue Type: Task >Affects Versions: MAVEN-32 >Reporter: Herve Boutemy >Priority: Major > > as part of migration to Git MASFRES-20 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-253) issue management URL incorrect
[ https://issues.apache.org/jira/browse/MPOM-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-253: -- Fix Version/s: MAVEN-35 > issue management URL incorrect > -- > > Key: MPOM-253 > URL: https://issues.apache.org/jira/browse/MPOM-253 > Project: Maven POMs > Issue Type: Bug > Components: maven >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: MAVEN-35 > > > on this page: https://maven.apache.org/pom/maven/issue-management.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-253) issue management URL incorrect
[ https://issues.apache.org/jira/browse/MPOM-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-253: -- Component/s: maven > issue management URL incorrect > -- > > Key: MPOM-253 > URL: https://issues.apache.org/jira/browse/MPOM-253 > Project: Maven POMs > Issue Type: Bug > Components: maven >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Minor > > on this page: https://maven.apache.org/pom/maven/issue-management.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-215) Create a new parent POM to lock down plugins versions of default lifecycle bindings
[ https://issues.apache.org/jira/browse/MPOM-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252797#comment-17252797 ] Sylwester Lachiewicz commented on MPOM-215: --- Is it still valid? > Create a new parent POM to lock down plugins versions of default lifecycle > bindings > --- > > Key: MPOM-215 > URL: https://issues.apache.org/jira/browse/MPOM-215 > Project: Maven POMs > Issue Type: New Feature >Reporter: Herve Boutemy >Priority: Major > > while working on version upgrade of default plugin bindings, we found that: > 1. a warning should be displayed MNG-6562 > 2. a parent POM would be the easiest solution to lock down every plugins at > once, instead of letting users lock down each plugin separately > let's create this parent POM -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MPOM-254) Shade Plugin Does Not Support JDK11
[ https://issues.apache.org/jira/browse/MPOM-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPOM-254. - Resolution: Duplicate > Shade Plugin Does Not Support JDK11 > --- > > Key: MPOM-254 > URL: https://issues.apache.org/jira/browse/MPOM-254 > Project: Maven POMs > Issue Type: Improvement >Reporter: David Mollitor >Priority: Major > Fix For: ASF-24 > > > https://blogs.apache.org/maven/entry/apache-maven-shade-plugin-version2 > Must be version 3.2.1 (Current version is 3.2.4) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-254) Shade Plugin Does Not Support JDK11
[ https://issues.apache.org/jira/browse/MPOM-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-254: -- Fix Version/s: ASF-24 > Shade Plugin Does Not Support JDK11 > --- > > Key: MPOM-254 > URL: https://issues.apache.org/jira/browse/MPOM-254 > Project: Maven POMs > Issue Type: Improvement >Reporter: David Mollitor >Priority: Major > Fix For: ASF-24 > > > https://blogs.apache.org/maven/entry/apache-maven-shade-plugin-version2 > Must be version 3.2.1 (Current version is 3.2.4) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-ear-plugin] elharo commented on a change in pull request #32: remove deprecated methods by not stubbing value objects
elharo commented on a change in pull request #32:
URL: https://github.com/apache/maven-ear-plugin/pull/32#discussion_r546667976
##
File path: src/test/java/org/apache/maven/plugins/ear/AbstractEarTestBase.java
##
@@ -33,88 +35,42 @@
public static final String DEFAULT_GROUPID = "eartest";
Review comment:
done
##
File path: src/test/java/org/apache/maven/plugins/ear/AbstractEarTestBase.java
##
@@ -33,88 +35,42 @@
public static final String DEFAULT_GROUPID = "eartest";
-public static final String DEFAULT_TYPE = "jar";
+private static final String DEFAULT_TYPE = "jar";
protected void setUri( EarModule module, String uri )
{
( (AbstractEarModule) module ).setUri( uri );
}
-protected Set createArtifacts( String[] artifactsId )
+protected Set createArtifacts( String[] artifactIds )
{
-return createArtifacts( artifactsId, null );
+return createArtifacts( artifactIds, null );
}
-protected Set createArtifacts( String[] artifactsId, String[]
types )
-{
-return createArtifacts( artifactsId, types, null );
-}
-
-protected Set createArtifacts( String[] artifactsId, String[]
types, String[] groupsId )
-{
-return createArtifacts( artifactsId, types, groupsId, null );
-}
-
-protected Set createArtifacts( String[] artifactsId, String[]
types, String[] groupsId,
- String[] classifiers )
+protected Set createArtifacts( String[] artifactIds, String[]
classifiers )
{
Set result = new TreeSet();
-if ( artifactsId == null || artifactsId.length == 0 )
-{
-return result;
-}
-for ( int i = 0; i < artifactsId.length; i++ )
+ArtifactHandlerTestStub artifactHandler = new ArtifactHandlerTestStub(
"jar" );
+for ( int i = 0; i < artifactIds.length; i++ )
{
-String artifactId = artifactsId[i];
-String type = getData( types, i, DEFAULT_TYPE );
-String groupId = getData( groupsId, i, DEFAULT_GROUPID );
-String classifier = getData( classifiers, i, null );
-result.add( new ArtifactTestStub( groupId, artifactId, type,
classifier ) );
+String artifactId = artifactIds[i];
+String classifier = classifiers == null ? null : classifiers[i];
+Artifact artifactTestStub = new DefaultArtifact(
+DEFAULT_GROUPID, artifactId, "1.0", "compile", DEFAULT_TYPE,
classifier, artifactHandler );
+
Review comment:
done
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (MPOM-251) Set minimum enforced Maven version to 3.1.1
[ https://issues.apache.org/jira/browse/MPOM-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-251: -- Fix Version/s: ASF-24 > Set minimum enforced Maven version to 3.1.1 > --- > > Key: MPOM-251 > URL: https://issues.apache.org/jira/browse/MPOM-251 > Project: Maven POMs > Issue Type: Dependency upgrade > Environment: per discussion on mailing list >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > Fix For: ASF-24 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MPOM-257) Upgrade maven-ear-plugin to 3.1.0
Sylwester Lachiewicz created MPOM-257: - Summary: Upgrade maven-ear-plugin to 3.1.0 Key: MPOM-257 URL: https://issues.apache.org/jira/browse/MPOM-257 Project: Maven POMs Issue Type: Dependency upgrade Components: asf Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-apache-parent] slachiewicz opened a new pull request #27: [MPOM-256] Remove outdated clirr-maven-plugin
slachiewicz opened a new pull request #27: URL: https://github.com/apache/maven-apache-parent/pull/27 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MPOM-256) Drop org.codehaus.mojo:clirr-maven-plugin
[ https://issues.apache.org/jira/browse/MPOM-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-256: -- Component/s: asf > Drop org.codehaus.mojo:clirr-maven-plugin > - > > Key: MPOM-256 > URL: https://issues.apache.org/jira/browse/MPOM-256 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Reporter: Sylwester Lachiewicz >Priority: Minor > > Remove deprecated plugin without support for newer Java versions. > > Latest releases: > clirr-maven-plugin 2.8 2016-09-13 > Clirr latest release: 06 2005-10-27 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MPOM-256) Drop org.codehaus.mojo:clirr-maven-plugin
Sylwester Lachiewicz created MPOM-256: - Summary: Drop org.codehaus.mojo:clirr-maven-plugin Key: MPOM-256 URL: https://issues.apache.org/jira/browse/MPOM-256 Project: Maven POMs Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Remove deprecated plugin without support for newer Java versions. Latest releases: clirr-maven-plugin 2.8 2016-09-13 Clirr latest release: 06 2005-10-27 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MEAR-292) skipClassPathModification option should prevent adding Class-Path entry into MANIFEST.mf
[
https://issues.apache.org/jira/browse/MEAR-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MEAR-292:
---
Fix Version/s: 3.2.0
> skipClassPathModification option should prevent adding Class-Path entry into
> MANIFEST.mf
>
>
> Key: MEAR-292
> URL: https://issues.apache.org/jira/browse/MEAR-292
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10 x64
>Reporter: Marat Abrarov
>Priority: Major
> Fix For: 3.2.0
>
>
> It looks like there is a bug in implementation of
> {{skipClassPathModification}} option introduced in MEAR-182 - if
> {{skipClassPathModification}} is {{true}} and original MANIFEST.mf of EAR
> module artifact has no {{Class-Path}} entry, then empty {{Class-Path}} entry
> is added into EAR module. I believe that {{Class-Path}} entry should not be
> added in this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MEAR-294) JAR with provided scope should be removed from Class-Path entry of EAR module MANIFEST.mf
[
https://issues.apache.org/jira/browse/MEAR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MEAR-294:
---
Fix Version/s: 3.2.0
> JAR with provided scope should be removed from Class-Path entry of EAR module
> MANIFEST.mf
> -
>
> Key: MEAR-294
> URL: https://issues.apache.org/jira/browse/MEAR-294
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Marat Abrarov
>Priority: Major
> Fix For: 3.2.0
>
>
> JAR dependency of EAR with provided scope should be removed from
> {{Class-Path}} entry of MANIFEST.mf of EAR module if {{skinnyWars}} or
> {{skinnyModules}} option is turned on or if EAR module doesn't contain all of
> its dependencies (like EJB module). This issue looks to be a bug of solution
> of MEAR-243 bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MDEPLOY-269) make build Reproducible
[ https://issues.apache.org/jira/browse/MDEPLOY-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MDEPLOY-269. - Resolution: Fixed done in https://github.com/apache/maven-deploy-plugin/commit/b58ff3c9e5cf80948d0f9180a30132c8871192ff > make build Reproducible > --- > > Key: MDEPLOY-269 > URL: https://issues.apache.org/jira/browse/MDEPLOY-269 > Project: Maven Deploy Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-M1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJAVADOC-468) Please provide an example for the userproperty groups
[
https://issues.apache.org/jira/browse/MJAVADOC-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252779#comment-17252779
]
Oscar Farga commented on MJAVADOC-468:
--
I have been checking and I think this is not valid anymore, the groups
userproperty was removed as part of MJAVADOC-578
> Please provide an example for the userproperty groups
> -
>
> Key: MJAVADOC-468
> URL: https://issues.apache.org/jira/browse/MJAVADOC-468
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
>Affects Versions: 2.10.3
>Reporter: Oliver B. Fischer
>Priority: Minor
> Labels: docs, up-for-grabs
>
> Groups can by configured via the {{group}} element of the configuration and
> via the userproperty {{groups}}.
> Please provide an example how to use this property with one and multiple
> groups.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCHECKSTYLE-393) upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHECKSTYLE-393: - Fix Version/s: 3.2.0 > upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts > --- > > Key: MCHECKSTYLE-393 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-393 > Project: Maven Checkstyle Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Herve Boutemy >Priority: Major > Labels: up-for-grabs > Fix For: 3.2.0 > > > to benefit from dependencies removal in DOXIASITETOOLS-215 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DOXIASITETOOLS-221) CLIRR can't find previous version
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252760#comment-17252760 ] Michael Osipov commented on DOXIASITETOOLS-221: --- Please follow this discussion: http://mail-archives.apache.org/mod_mbox/hc-dev/202012.mbox/%3Ca5d25fd037f3381042674080f5d479ed52e277b5.camel%40apache.org%3E > CLIRR can't find previous version > - > > Key: DOXIASITETOOLS-221 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-221 > Project: Maven Doxia Sitetools > Issue Type: Bug > Components: Integration Tools, Skin model >Reporter: Elliotte Rusty Harold >Priority: Minor > > [INFO] --- clirr-maven-plugin:2.8:check (default) @ doxia-skin-model --- > [INFO] Comparing to version: 1.1 > [WARNING] Impossible to find previous version > [INFO] Succeeded with 0 errors; 0 warnings; and 0 other changes. > [INFO] > > [INFO] --- clirr-maven-plugin:2.8:check (default) @ doxia-integration-tools > --- > [INFO] Comparing to version: 1.1 > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-integration-tools/1.1/doxia-integration-tools-1.1.jar > [WARNING] Impossible to find previous version > [INFO] Succeeded with 0 errors; 0 wa -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6512-build-11 #18 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6512-build-11/18/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » Bananeweizen-MNG-6907 #6 See https://builds.apache.org/job/maven-box/job/maven/job/Bananeweizen-MNG-6907/6/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #44 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/44/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #47 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/47/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6909 #11 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6909/11/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6965 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6965/2/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6952 #4 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6952/4/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6553 #41 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/41/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MODELTESTS_IMPROVEMENT #29 See https://builds.apache.org/job/maven-box/job/maven/job/MODELTESTS_IMPROVEMENT/29/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6829 #27 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6829/27/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6548 #25 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6548/25/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build failed in Jenkins: Maven TLP » maven » MPOM-215 #36 See https://builds.apache.org/job/maven-box/job/maven/job/MPOM-215/36/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6552 #41 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/41/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #47 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/47/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6555 #48 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/48/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6554 #40 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/40/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6889 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6889/6/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MRESOLVER-94 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MRESOLVER-94/6/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build failed in Jenkins: Maven TLP » maven » MNG-6888 #6 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6888/6/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-6012-Missing-Profile-At-End #60 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/60/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #58 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/58/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven » Maven TLP » maven » MRESOLVER-94 #5 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MRESOLVER-94/5/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven TLP » maven » mng-5668-poc #27 See https://builds.apache.org/job/maven-box/job/maven/job/mng-5668-poc/27/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (MNG-6974) IT for MNG-5175 (Wagon HTTP) fails with JDK 14
[ https://issues.apache.org/jira/browse/MNG-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6974: Comment: was deleted (was: Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6512-build-11 #5 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6512-build-11/5/) > IT for MNG-5175 (Wagon HTTP) fails with JDK 14 > -- > > Key: MNG-6974 > URL: https://issues.apache.org/jira/browse/MNG-6974 > Project: Maven > Issue Type: Bug > Components: Integration Tests >Reporter: Michael Kroll >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available, test > > [ERROR] Tests run: 846, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 210.078 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > [ERROR] > testmng5175_ReadTimeOutFromSettings(org.apache.maven.it.MavenITmng5175WagonHttpTest) > Time elapsed: 0.166 s <<< ERROR! > org.apache.maven.it.VerificationException: Text not found in log: Could not > transfer artifact > org.apache.maven.its.mng5175:fake-dependency:pom:1.0-SNAPSHOT > at > org.apache.maven.it.MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings(MavenITmng5175WagonHttpTest.java:128) > https://github.com/apache/maven/pull/368/checks?check_run_id=941247515 -- This message was sent by Atlassian Jira (v8.3.4#803005)
