[jira] [Commented] (MNG-7906) Dependency Management import (BOM) does not work the "maven way"
[
https://issues.apache.org/jira/browse/MNG-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846005#comment-17846005
]
Lenny Primak commented on MNG-7906:
---
I would think that 4.0 would be *the place* to break the compatibility.
First of all, I don't think it's as big of a deal, as depMgmt import isn't as
nearly widely used, and the actual conflicting use cases are few and far
between (IMHO)
I would put this behind a system property so this can be easily switched back
within settings.xml or an individual pom file, as well as the command line.
> Dependency Management import (BOM) does not work the "maven way"
>
>
> Key: MNG-7906
> URL: https://issues.apache.org/jira/browse/MNG-7906
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Documentation: General
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.x-candidate
>
>
> This affects all released Maven versions so far.
> Problem reproducer: https://github.com/cstamas/MNG-7852 (repo name is wrong,
> obviously).
> In short: unlike with dependencies, where you CAN override some "deep
> transitive" dependency by re-declaring it directly as 1st level dependency in
> POM, for depMgt import this does not work, actually, it works quite the
> opposite ("first comes, wins"). Moreover, Maven remains silent about this, as
> reproducer shows, and all of this goes unnoticed.
> Solution: at least depMgt import should make "the maven way", maybe not by
> default (to not break existing builds) but configurable. Problem is solved if
> in reproducer:
> - with fix enabled, junit 5.9.3 is used, AND
> - with fix disabled, Maven yells about ignored depMgt import
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-8118) Dependency-management "client" exclusions overwrite BOM exclusions
Lenny Primak created MNG-8118: - Summary: Dependency-management "client" exclusions overwrite BOM exclusions Key: MNG-8118 URL: https://issues.apache.org/jira/browse/MNG-8118 Project: Maven Issue Type: Bug Affects Versions: 4.0.0-alpha-13, 4.0.x-candidate Environment: Any Reporter: Lenny Primak When importing BOM and introducing exclusions, they overwrite exclusions already present in the BOM. They should not Slack conversation link: https://the-asf.slack.com/archives/C7Q9JB404/p1714938396499939 Regressed by https://issues.apache.org/jira/browse/MNG-5600 Reproducer app: [https://github.com/lprimak/apps/tree/main/emailmanager] Fixed by: https://github.com/apache/maven/pull/1504 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-587) Java Module warnings for automatic modules when used with Maven 4
[
https://issues.apache.org/jira/browse/MCOMPILER-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828134#comment-17828134
]
Lenny Primak commented on MCOMPILER-587:
No. I know I could reproduce it in a previous version as well.
I think it appeared with the one of the later maven 4 alpha versions though I
am not sure which exact one.
> Java Module warnings for automatic modules when used with Maven 4
> -
>
> Key: MCOMPILER-587
> URL: https://issues.apache.org/jira/browse/MCOMPILER-587
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.13.0
> Environment: When used with Maven 4-alpha-13
>Reporter: Lenny Primak
>Priority: Major
>
> Looks like these warnings are generated when processing modules that have
> automatic module names in their MANIFEST.MF files.
> This only occurs with Maven 4, not maven 3. There is no way to disable these
> warnings.
> {code:java}
> [INFO] --- compiler:3.13.0:compile (default-compile) @ hope-website ---
> [WARNING] Can't extract module name from shiro-core-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.core' is already on the module path!
> [WARNING] Can't extract module name from shiro-web-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.web' is already on the module path!
> [WARNING] Can't extract module name from shiro-cdi-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.cdi' is already on the module path! {code}
>
> Sample project: [https://github.com/lprimak/apps]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MCHECKSTYLE-429) Deprecation warning
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828126#comment-17828126
]
Lenny Primak commented on MCHECKSTYLE-429:
--
This appears to be fixed. You can close this issue, thanks!
> Deprecation warning
> ---
>
> Key: MCHECKSTYLE-429
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-429
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:checkstyle
>Affects Versions: 3.2.1, 3.2.2
>Reporter: Lenny Primak
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M1
>
>
> Every time checkstyle plugin is ran, the following warning occurs:
> {code:java}
> [INFO] --- checkstyle:3.2.1:checkstyle (default) @ shiro-cdi ---
> [WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
> use of ArtifactRepository type. If you need access to local repository,
> switch to '${repositorySystemSession}' expression and get LRM from it instead.
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO] Starting audit...
> Audit done.
> {code}
> Looks like maven 3.9.x deprecated `localRepository` variable and the plugin
> needs to be updated to reflect this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MCOMPILER-587) Java Module warnings for automatic modules when used with Maven 4
[
https://issues.apache.org/jira/browse/MCOMPILER-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenny Primak updated MCOMPILER-587:
---
Description:
Looks like these warnings are generated when processing modules that have
automatic module names in their MANIFEST.MF files.
This only occurs with Maven 4, not maven 3. There is no way to disable these
warnings.
{code:java}
[INFO] --- compiler:3.13.0:compile (default-compile) @ hope-website ---
[WARNING] Can't extract module name from shiro-core-2.0.0-jakarta.jar: Module
'org.apache.shiro.core' is already on the module path!
[WARNING] Can't extract module name from shiro-web-2.0.0-jakarta.jar: Module
'org.apache.shiro.web' is already on the module path!
[WARNING] Can't extract module name from shiro-cdi-2.0.0-jakarta.jar: Module
'org.apache.shiro.cdi' is already on the module path! {code}
Sample project: [https://github.com/lprimak/apps]
was:
Looks like these warnings are generated when processing modules that have
automatic module names in their MANIFEST.MF files.
This only occurs with Maven 4, not maven 3. There is no way to disable these
warnings.
{code:java}
[INFO] --- compiler:3.13.0:compile (default-compile) @ hope-website ---
[WARNING] Can't extract module name from shiro-core-2.0.0-jakarta.jar: Module
'org.apache.shiro.core' is already on the module path!
[WARNING] Can't extract module name from shiro-web-2.0.0-jakarta.jar: Module
'org.apache.shiro.web' is already on the module path!
[WARNING] Can't extract module name from shiro-cdi-2.0.0-jakarta.jar: Module
'org.apache.shiro.cdi' is already on the module path! {code}
> Java Module warnings for automatic modules when used with Maven 4
> -
>
> Key: MCOMPILER-587
> URL: https://issues.apache.org/jira/browse/MCOMPILER-587
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.13.0
> Environment: When used with Maven 4-alpha-13
>Reporter: Lenny Primak
>Priority: Major
>
> Looks like these warnings are generated when processing modules that have
> automatic module names in their MANIFEST.MF files.
> This only occurs with Maven 4, not maven 3. There is no way to disable these
> warnings.
> {code:java}
> [INFO] --- compiler:3.13.0:compile (default-compile) @ hope-website ---
> [WARNING] Can't extract module name from shiro-core-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.core' is already on the module path!
> [WARNING] Can't extract module name from shiro-web-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.web' is already on the module path!
> [WARNING] Can't extract module name from shiro-cdi-2.0.0-jakarta.jar: Module
> 'org.apache.shiro.cdi' is already on the module path! {code}
>
> Sample project: [https://github.com/lprimak/apps]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MCOMPILER-587) Java Module warnings for automatic modules when used with Maven 4
Lenny Primak created MCOMPILER-587:
--
Summary: Java Module warnings for automatic modules when used with
Maven 4
Key: MCOMPILER-587
URL: https://issues.apache.org/jira/browse/MCOMPILER-587
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.13.0
Environment: When used with Maven 4-alpha-13
Reporter: Lenny Primak
Looks like these warnings are generated when processing modules that have
automatic module names in their MANIFEST.MF files.
This only occurs with Maven 4, not maven 3. There is no way to disable these
warnings.
{code:java}
[INFO] --- compiler:3.13.0:compile (default-compile) @ hope-website ---
[WARNING] Can't extract module name from shiro-core-2.0.0-jakarta.jar: Module
'org.apache.shiro.core' is already on the module path!
[WARNING] Can't extract module name from shiro-web-2.0.0-jakarta.jar: Module
'org.apache.shiro.web' is already on the module path!
[WARNING] Can't extract module name from shiro-cdi-2.0.0-jakarta.jar: Module
'org.apache.shiro.cdi' is already on the module path! {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-8078) BOM warnings are emitted on scopes and exclusions
Lenny Primak created MNG-8078:
-
Summary: BOM warnings are emitted on scopes and exclusions
Key: MNG-8078
URL: https://issues.apache.org/jira/browse/MNG-8078
Project: Maven
Issue Type: Bug
Components: Core, Errors
Affects Versions: 4.0.0-alpha-13
Environment: Any
Reporter: Lenny Primak
There a couple of scenarios that are generating warnings that should not:
* BOM dependency entries that have a different scope
* BOM dependency entries that have exclusions
There are many scenarios where multiple BOMs declare the same dependency
versions, although in slightly different ways. Many of these are transient, and
very hard to figure out in the first place. Warnings lead to multiple
unnecessary exclusions and are forcing modifications to POM where they are not
needed.
The above entries should not generate a warning, because the dependencies are
not conflicting.
Examples (BOM):
{code:java}
...
org.junit.jupiter
junit-jupiter-api
${junit.version}
test
org.junit.jupiter
junit-jupiter-params
${junit.version}
test
org.junit.jupiter
junit-jupiter-engine
${junit.version}
test
...
{code}
Warnings:
{code:java}
[WARNING] Some problems were encountered while building the effective model for
'com.flowlogix:hope-website:war:1.x-SNAPSHOT'
[WARNING] Ignored POM import for: org.slf4j:jcl-over-slf4j:jar:2.0.12@test as
already imported org.slf4j:jcl-over-slf4j:jar:2.0.12@compile. Add a the
conflicting managed dependency directly to the dependencyManagement section of
the POM.
WARNING] Ignored POM import for: net.bytebuddy:byte-buddy:jar:1.14.12@compile[1
exclusions] as already imported net.bytebuddy:byte-buddy:jar:1.14.12@compile.
Add a the conflicting managed dependency directly to the dependencyManagement
section of the POM.
[WARNING] Ignored POM import for:
net.bytebuddy:byte-buddy-agent:jar:1.14.12@compile[1 exclusions] as already
imported net.bytebuddy:byte-buddy-agent:jar:1.14.12@compile. Add a the
conflicting managed dependency directly to the dependencyManagement section of
the POM.
[WARNING] Ignored POM import for:
org.junit.jupiter:junit-jupiter-api:jar:5.10.2@compile[1 exclusions] as already
imported org.junit.jupiter:junit-jupiter-api:jar:5.10.2@test. Add a the
conflicting managed dependency directly to the dependencyManagement section of
the POM.
[WARNING] Ignored POM import for:
org.junit.jupiter:junit-jupiter-engine:jar:5.10.2@compile[1 exclusions] as
already imported org.junit.jupiter:junit-jupiter-engine:jar:5.10.2@test. Add a
the conflicting managed dependency directly to the dependencyManagement section
of the POM.
[WARNING] Ignored POM import for:
org.junit.jupiter:junit-jupiter-params:jar:5.10.2@compile[1 exclusions] as
already imported org.junit.jupiter:junit-jupiter-params:jar:5.10.2@test. Add a
the conflicting managed dependency directly to the dependencyManagement section
of the POM. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MPOM-452) Apache Parent POM - Use property for Apache Repository IDs
Lenny Primak created MPOM-452: - Summary: Apache Parent POM - Use property for Apache Repository IDs Key: MPOM-452 URL: https://issues.apache.org/jira/browse/MPOM-452 Project: Maven POMs Issue Type: Improvement Affects Versions: ASF-31 Reporter: Lenny Primak Add ability to override Apache Release and Snapshot repository IDs via properties Useful to deploy to different instances of repositories -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-450) Prevent the SCM elements from being inherited
[ https://issues.apache.org/jira/browse/MPOM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800542#comment-17800542 ] Lenny Primak commented on MPOM-450: --- Yes you are right. I was a little too zealous referencing your issue. I will open a new one > Prevent the SCM elements from being inherited > - > > Key: MPOM-450 > URL: https://issues.apache.org/jira/browse/MPOM-450 > Project: Maven POMs > Issue Type: Bug > Components: asf >Affects Versions: ASF-31 >Reporter: Konrad Windszus >Priority: Major > > Currently the SCM elements are not encapsulated in a profile, i.e. they are > automatically inherited by all derived projects. As those never share > anything with the SCM URLs of the ASF parent it would make sense to only > conditionally set those SCM elements (in a profile). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPOM-451) Please remove repository entry from Apache parent POM
Lenny Primak created MPOM-451: - Summary: Please remove repository entry from Apache parent POM Key: MPOM-451 URL: https://issues.apache.org/jira/browse/MPOM-451 Project: Maven POMs Issue Type: Bug Affects Versions: ASF-31 Reporter: Lenny Primak According to maven documentation, it's "bad form" to have repository entries in POM files. Apache POM includes snapshot repository element. This is interfering with Apache Shiro builds, for example -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-450) Prevent the SCM elements from being inherited
[ https://issues.apache.org/jira/browse/MPOM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800380#comment-17800380 ] Lenny Primak commented on MPOM-450: --- Also, those elements should be based on properties so they can be overridden. This is useful to test releases to private repositories > Prevent the SCM elements from being inherited > - > > Key: MPOM-450 > URL: https://issues.apache.org/jira/browse/MPOM-450 > Project: Maven POMs > Issue Type: Bug > Components: asf >Affects Versions: ASF-31 >Reporter: Konrad Windszus >Priority: Major > > Currently the SCM elements are not encapsulated in a profile, i.e. they are > automatically inherited by all derived projects. As those never share > anything with the SCM URLs of the ASF parent it would make sense to only > conditionally set those SCM elements (in a profile). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"
[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17748243#comment-17748243 ] Lenny Primak commented on MNG-7852: --- Hi, I understand your points, and they are indeed valid. I myself ran into these problems. However, your suggestion to "just remove" them is incomplete at best, as it would "break the world". To make this wish a reality (which I am not sure it's possible) I would try to develop an enhancement of the algorithm that works and doesn't break any current projects. As I said before, not sure that's possible. > Use all the versions for dependency resolution rather than "nearest first" or > "declared first" > -- > > Key: MNG-7852 > URL: https://issues.apache.org/jira/browse/MNG-7852 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Reporter: Vladimir Sitnikov >Priority: Major > > Currently, Maven uses "nearest first", "declared first" rules for conflict > resolution: > https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > I suggest those rules are removed since they produce hard to reason > resolutions for transitive dependencies. > Below I list reasons why both "nearest wins" and "declared first" yield > hard-to-predict behaviours, and they are likely to produce dependency > downgrades and the associated runtime errors. > Here are some examples: > 1) "Nearest first". Even though the rule sounds easy, it is not something the > users can control. For instance, if the project does not use Guava library, > some of the transitive dependencies could add a dependency on Guava. The user > has no control which dependency would be "the nearest" to declare Guava, so > user has literally no way to tell which Guava version will be used. > The only workaround I see for the users is to declare Guava dependency > explicitly even though the project does not need it directly. It sounds like > Maven requires users to re-declare all the possible dependencies, including > the runtime-only ones. > 2) "declared first". Of course, dependency order matters for classpath order, > however, it is not predictable in practice, and it might result in > downgrading dependencies. Imagine the project does not use Guice. However, > transitive dependencies might use Guice. At the same time, they might start > using Guice and stop using Guice, so the user can never tell which will be > the first project that uses Guice. Unfortunately, in Maven, the first project > that declares dependency wins, so it might easily be the case that the first > mention of Guice will reference outdated version that would be incompatible > with the newer one required in another dependency. > 3) Here's a real-life case: Maven downgrades protobuf-java dependency causing > something like NoSuchMethodError at the runtime. The step to reproduce is to > add dependency on dev.sigstore:sigstore-java:0.4.0. See [~hboutemy] analysis > in https://github.com/hboutemy/sigstore-maven-plugin/blob/import/analysis.md > Long story short, sigstore-java does not depend on protobuf-java directly, > however, sigstore-java depends on several third-party libraries that > eventually depend on protobuf-java. Maven's "the first wins" behaviour > results in incoherent set of protobuf dependencies on the classpath. > 4) see "unexpected" in MNG-5988 > To my best understanding, when it comes to transitive dependencies, both > "nearest first" and "declared first" are random variables which user can't > control unless they re-declare all the dependencies in their local pom. I > suggest Maven should not use random variables like "dependency depth" or > "dependency order" to drive conflict resolution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7837) Maven blows up on nested pom attributes
Lenny Primak created MNG-7837:
-
Summary: Maven blows up on nested pom attributes
Key: MNG-7837
URL: https://issues.apache.org/jira/browse/MNG-7837
Project: Maven
Issue Type: Bug
Components: Bootstrap Build
Affects Versions: 4.0.0-alpha-7
Reporter: Lenny Primak
* This started happening in 4.0.0-alpha-7
{{When pom contains nested , maven refuses to build:}}
{code:java}
% mvn clean
[INFO] Scanning for projects...
[ERROR] Some problems were encountered while processing the POMs
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project (/Users/lprimak/Documents/dev/flowlogix/pom.xml) has 1
error
[ERROR] Unrecognised tag: 'project' (position: START_TAG @1:205) @ line 1,
column 205 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
switch
[ERROR] Re-run Maven using the '-X' switch to enable verbose output
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles: {code}
Example:
{code:java}
...
org.commonjava.maven.plugins
directory-maven-plugin
1.0
directories
directory-of
validate
flowlogix.basedir
com.flowlogix
flowlogix
...
{code}
Reproducer: [https://github.com/flowlogix/flowlogix]
Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7818) [REGRESSION] maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735949#comment-17735949
]
Lenny Primak commented on MNG-7818:
---
Fixed!
> [REGRESSION] maven improperly excludes hamcrest-core from junit
> ---
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: Using hamcrest-core 2.2 (as opposed to 1.3 and without exclusions) with
> JUnit 4 works just fine as well, making the exclusion, again, unnecessary
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
> Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7818) [REGRESSION] maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735820#comment-17735820
]
Lenny Primak commented on MNG-7818:
---
This will not cause any issuers since test dependencies are not transitive, as
@cstamas said
> [REGRESSION] maven improperly excludes hamcrest-core from junit
> ---
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: Using hamcrest-core 2.2 (as opposed to 1.3 and without exclusions) with
> JUnit 4 works just fine as well, making the exclusion, again, unnecessary
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
> Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7818) [REGRESSION] maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735819#comment-17735819
]
Lenny Primak commented on MNG-7818:
---
This will not cause any issuers since test dependencies are not transitive, as
@cstamas said
> [REGRESSION] maven improperly excludes hamcrest-core from junit
> ---
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: Using hamcrest-core 2.2 (as opposed to 1.3 and without exclusions) with
> JUnit 4 works just fine as well, making the exclusion, again, unnecessary
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
> Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7818) [REGRESSION] maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenny Primak updated MNG-7818:
--
Description:
junit 4 now has exclusions for hamcrest-core, which causes
ClassNotFouncException
BTW: Using hamcrest-core 2.2 (as opposed to 1.3 and without exclusions) with
JUnit 4 works just fine as well, making the exclusion, again, unnecessary
Traced to https://issues.apache.org/jira/browse/MNG-7670
{code:java}
[INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088 s
<<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
elapsed: 0.009 s <<< ERROR!
java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
at java.base/java.lang.Class.getConstructor0(Class.java:3678)
at java.base/java.lang.Class.getConstructor(Class.java:2368)
at
org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
at
org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
at
org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 28 more {code}
was:
junit 4 now has exclusions for hamcrest-core, which causes
ClassNotFouncException
BTW: upgrading hamcrest-core to 2.2 (without exclusions) works just fine as well
Traced to https://issues.apache.org/jira/browse/MNG-7670
{code:java}
[INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088 s
<<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
elapsed: 0.009 s <<< ERROR!
java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
at
[jira] [Commented] (MNG-7818) [REGRESSION] maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17734169#comment-17734169
]
Lenny Primak commented on MNG-7818:
---
I still don't see why hamcrest-core is excluded from JUnit, which clearly
requires it. Why not just remove the exclusion and be done with it?
Since hamcrest 2.2 is already included, upgrade will still "happen"
> [REGRESSION] maven improperly excludes hamcrest-core from junit
> ---
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: upgrading hamcrest-core to 2.2 (without exclusions) works just fine as
> well
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
> Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7818) Regression: maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733970#comment-17733970
]
Lenny Primak edited comment on MNG-7818 at 6/19/23 12:17 AM:
-
How? Shrinkwrap of course :) It uses maven as a library to produce an
executable to be tested. Since shrinkwrap (minor version) has updated maven to
3.9.2, and 3.9.2 was the one started excluding hamcrest, error showed up here.
Here's a link to reproducer:
[https://github.com/flowlogix/test-arq-suite/blob/JUnit4/pom.xml#L46|https://github.com/flowlogix/test-arq-suite/blob/6541eb3f6943bd223b5048f6f9ec392b58a9954c/pom.xml#L46]
If you have docker, run to reproduce
{code:java}
$ mvn verify{code}
if no docker,
{code:java}
$ mvn verify -Ppayara-server-managed {code}
was (Author: lprimak):
How? Shrinkwrap of course :) It uses maven as a library to produce an
executable to be tested. Since shrinkwrap (minor version) has updated maven to
3.9.2, and 3.9.2 was the one started excluding hamcrest, error showed up here.
Here's a link to reproducer:
[https://github.com/flowlogix/test-arq-suite/blob/JUnit4/pom.xml#L46|https://github.com/flowlogix/test-arq-suite/blob/6541eb3f6943bd223b5048f6f9ec392b58a9954c/pom.xml#L46]
> Regression: maven improperly excludes hamcrest-core from junit
> --
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: upgrading hamcrest-core to 2.2 (without exclusions) works just fine as
> well
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
>
[jira] [Commented] (MNG-7818) Regression: maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733970#comment-17733970
]
Lenny Primak commented on MNG-7818:
---
How? Shrinkwrap of course :) It uses maven as a library to produce an
executable to be tested. Since shrinkwrap (minor version) has updated maven to
3.9.2, and 3.9.2 was the one started excluding hamcrest, error showed up here.
Here's a link to reproducer:
[https://github.com/flowlogix/test-arq-suite/blob/JUnit4/pom.xml#L46|https://github.com/flowlogix/test-arq-suite/blob/6541eb3f6943bd223b5048f6f9ec392b58a9954c/pom.xml#L46]
> Regression: maven improperly excludes hamcrest-core from junit
> --
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: upgrading hamcrest-core to 2.2 (without exclusions) works just fine as
> well
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
> Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7818) Regression: maven improperly excludes hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenny Primak updated MNG-7818:
--
Summary: Regression: maven improperly excludes hamcrest-core from junit
(was: Regression: maven improperly exclude hamcrest-core from junit)
> Regression: maven improperly excludes hamcrest-core from junit
> --
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: upgrading hamcrest-core to 2.2 (without exclusions) works just fine as
> well
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
> Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7818) Regression: maven improperly exclude hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733931#comment-17733931
]
Lenny Primak commented on MNG-7818:
---
[~cstamas] yours :)
> Regression: maven improperly exclude hamcrest-core from junit
> -
>
> Key: MNG-7818
> URL: https://issues.apache.org/jira/browse/MNG-7818
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.9.2
> Environment: Any
>Reporter: Lenny Primak
>Priority: Minor
>
> junit 4 now has exclusions for hamcrest-core, which causes
> ClassNotFouncException
> BTW: upgrading hamcrest-core to 2.2 (without exclusions) works just fine as
> well
> Traced to https://issues.apache.org/jira/browse/MNG-7670
> {code:java}
> [INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088
> s <<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
> [ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
> elapsed: 0.009 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
> at
> java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
> at java.base/java.lang.Class.getConstructor0(Class.java:3678)
> at java.base/java.lang.Class.getConstructor(Class.java:2368)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
> at
> org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
> at
> org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
> Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7818) Regression: maven improperly exclude hamcrest-core from junit
[
https://issues.apache.org/jira/browse/MNG-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenny Primak updated MNG-7818:
--
Description:
junit 4 now has exclusions for hamcrest-core, which causes
ClassNotFouncException
BTW: upgrading hamcrest-core to 2.2 (without exclusions) works just fine as well
Traced to https://issues.apache.org/jira/browse/MNG-7670
{code:java}
[INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088 s
<<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
elapsed: 0.009 s <<< ERROR!
java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
at java.base/java.lang.Class.getConstructor0(Class.java:3678)
at java.base/java.lang.Class.getConstructor(Class.java:2368)
at
org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
at
org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
at
org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 28 more {code}
was:
junit 4 has exclusions for hamcrest-core, which causes ClassNotFouncException
Traced to https://issues.apache.org/jira/browse/MNG-7670
{code:java}
[INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088 s
<<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
elapsed: 0.009 s <<< ERROR!
java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
at
[jira] [Created] (MNG-7818) Regression: maven improperly exclude hamcrest-core from junit
Lenny Primak created MNG-7818:
-
Summary: Regression: maven improperly exclude hamcrest-core from
junit
Key: MNG-7818
URL: https://issues.apache.org/jira/browse/MNG-7818
Project: Maven
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.9.2
Environment: Any
Reporter: Lenny Primak
junit 4 has exclusions for hamcrest-core, which causes ClassNotFouncException
Traced to https://issues.apache.org/jira/browse/MNG-7670
{code:java}
[INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088 s
<<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
elapsed: 0.009 s <<< ERROR!
java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
at java.base/java.lang.Class.getConstructor0(Class.java:3678)
at java.base/java.lang.Class.getConstructor(Class.java:2368)
at
org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
at
org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
at
org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7670) Upgrade misc dependencies
[
https://issues.apache.org/jira/browse/MNG-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733837#comment-17733837
]
Lenny Primak commented on MNG-7670:
---
JUnit 4 still requires hamcrest-core 1.3
{code:java}
[INFO] Running com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.088 s
<<< FAILURE! -- in com.flowlogix.arqsuite.DeploymentOneTest
[ERROR] com.flowlogix.arqsuite.DeploymentOneTest.initializationError -- Time
elapsed: 0.009 s <<< ERROR!
java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1013)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3473)
at java.base/java.lang.Class.getConstructor0(Class.java:3678)
at java.base/java.lang.Class.getConstructor(Class.java:2368)
at
org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
at
org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:37)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:70)
at
org.junit.internal.requests.ClassRequest.createRunner(ClassRequest.java:28)
at
org.junit.internal.requests.MemoizingRequest.getRunner(MemoizingRequest.java:19)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:314)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
Caused by: java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 28 more {code}
> Upgrade misc dependencies
> -
>
> Key: MNG-7670
> URL: https://issues.apache.org/jira/browse/MNG-7670
> Project: Maven
> Issue Type: Dependency upgrade
> Components: Dependencies
>Reporter: Sylwester Lachiewicz
>Assignee: Tamas Cservenak
>Priority: Minor
> Fix For: 3.9.2
>
>
> [INFO] The following dependencies in Dependency Management have newer
> versions:
> [INFO] com.google.guava:guava .. 30.1-jre -> 31.1-jre
> [INFO] org.apache.commons:commons-lang3 . 3.8.1 -> 3.12.0
> [INFO] org.codehaus.plexus:plexus-classworlds 2.6.0 -> 2.7.0
> -[INFO] org.codehaus.plexus:plexus-component-annotations .. 2.1.0 ->
> 2.1.1-
> -[INFO] org.codehaus.plexus:plexus-utils .. 3.4.2 ->
> 3.5.1-
> [INFO] org.hamcrest:hamcrest-core 1.3 -> 2.2
> [INFO] org.hamcrest:hamcrest-library . 1.3 -> 2.2
> [INFO] org.mockito:mockito-core 2.21.0 -> 4.11.0
> [INFO] org.powermock:powermock-reflect ... 1.7.4 -> 2.0.9
> [INFO] org.xmlunit:xmlunit-core .. 2.2.1 -> 2.9.1
> [INFO] org.xmlunit:xmlunit-matchers .. 2.2.1 -> 2.9.1
>
[jira] [Commented] (MNG-7745) NPE when .mvn doesn't exist
[
https://issues.apache.org/jira/browse/MNG-7745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1778#comment-1778
]
Lenny Primak commented on MNG-7745:
---
Alright! That was easy :)
> NPE when .mvn doesn't exist
> ---
>
> Key: MNG-7745
> URL: https://issues.apache.org/jira/browse/MNG-7745
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-4, 4.0.0-alpha-5
> Environment: Any
>Reporter: Lenny Primak
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-alpha-6
>
>
> When maven is executed without a .mvn directory, an NPE appears every time.
> This doesn't seem to affect anything but does pollute the logs:
> {code:java}
> Failed to notify spy org.apache.maven.ReactorReader$ReactorReaderSpy: Cannot
> invoke "java.io.File.toPath()" because the return value of
> "org.apache.maven.project.MavenProject.getFile()" is null {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7632) Regression: combine.children breaks when combining executions
[ https://issues.apache.org/jira/browse/MNG-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated MNG-7632: -- Description: When upgrading from 3.x to 4.x, combine.children behaves differently. When it is declared in the parent pom, the child pom do not correctly combine elements: See [https://github.com/flowlogix/flowlogix/commit/301f428a229f4ab51e55a488bd71ec4aec87bce4] for a reproducer. Prior to maven 4, you could put combine.children into the parent pom and it would work. Since maven 4, combine.children only works when put into the child pom. was: When upgrading from 3.x to 4.x, combine.children behaves differently. When it is declared in the parent pom, the child pom do not correctly combines elements: See [https://github.com/flowlogix/flowlogix/commit/301f428a229f4ab51e55a488bd71ec4aec87bce4] for a reproducer. > Regression: combine.children breaks when combining executions > - > > Key: MNG-7632 > URL: https://issues.apache.org/jira/browse/MNG-7632 > Project: Maven > Issue Type: Bug > Components: Core >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Assignee: Guillaume Nodet >Priority: Minor > > When upgrading from 3.x to 4.x, combine.children behaves differently. > When it is declared in the parent pom, the child pom do not correctly combine > elements: > See > [https://github.com/flowlogix/flowlogix/commit/301f428a229f4ab51e55a488bd71ec4aec87bce4] > for a reproducer. > > Prior to maven 4, you could put combine.children into the parent pom and it > would work. Since maven 4, combine.children only works when put into the > child pom. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7745) NPE when .mvn doesn't exist
[
https://issues.apache.org/jira/browse/MNG-7745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1770#comment-1770
]
Lenny Primak commented on MNG-7745:
---
Easy. Run the following maven command *outside* of any maven project. The
result will be the same:
{code:java}
mvn dependency:copy -Dartifact=org.postgresql:postgresql:LATEST:jar
-Dproject.basedir=. -DoutputDirectory=xxx -DoverWrite=false {code}
> NPE when .mvn doesn't exist
> ---
>
> Key: MNG-7745
> URL: https://issues.apache.org/jira/browse/MNG-7745
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-4, 4.0.0-alpha-5
> Environment: Any
>Reporter: Lenny Primak
>Assignee: Guillaume Nodet
>Priority: Minor
>
> When maven is executed without a .mvn directory, an NPE appears every time.
> This doesn't seem to affect anything but does pollute the logs:
> {code:java}
> Failed to notify spy org.apache.maven.ReactorReader$ReactorReaderSpy: Cannot
> invoke "java.io.File.toPath()" because the return value of
> "org.apache.maven.project.MavenProject.getFile()" is null {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MCHECKSTYLE-429) Deprecation warning
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725481#comment-17725481
]
Lenny Primak commented on MCHECKSTYLE-429:
--
The new version of the plugin works with maven 3.9.2, but not with maven
4.0.0-alpha-5:
{code:java}
[INFO] --- checkstyle:3.3.0:checkstyle (default) @ flowlogix ---
[WARN] Parameter 'localRepository' is deprecated core expression; Avoid use of
ArtifactRepository type. If you need access to local repository, switch to
'${repositorySystemSession}' expression and get LRM from it instead.
[INFO]
{code}
> Deprecation warning
> ---
>
> Key: MCHECKSTYLE-429
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-429
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:checkstyle
>Affects Versions: 3.2.1, 3.2.2
>Reporter: Lenny Primak
>Priority: Major
>
> Every time checkstyle plugin is ran, the following warning occurs:
> {code:java}
> [INFO] --- checkstyle:3.2.1:checkstyle (default) @ shiro-cdi ---
> [WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
> use of ArtifactRepository type. If you need access to local repository,
> switch to '${repositorySystemSession}' expression and get LRM from it instead.
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO] Starting audit...
> Audit done.
> {code}
> Looks like maven 3.9.x deprecated `localRepository` variable and the plugin
> needs to be updated to reflect this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MRELEASE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722624#comment-17722624
]
Lenny Primak commented on MRELEASE-1123:
[~michael-o] Doesn't work with alpha-2 either. Alpha 1 is not available in the
archives.
So, it doesn't work with any of the maven 4 alphas.
Thank you!
> Maven Release plugin doesn't work in maven 4
>
>
> Key: MRELEASE-1123
> URL: https://issues.apache.org/jira/browse/MRELEASE-1123
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0
> Environment: Any
>Reporter: Lenny Primak
>Priority: Blocker
>
> {code:java}
> mvn -B -ntp -C release:prepare release:perform{code}
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
> project flowlogix: Unable to parse configuration of mojo
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
> projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
> org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
> org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
> org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
> to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]{code}
> Maven 4.0.0-alpha-5 and release plugin 3.0.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MRELEASE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722441#comment-17722441
]
Lenny Primak commented on MRELEASE-1123:
Can you please point me? I really can't find them.
> Maven Release plugin doesn't work in maven 4
>
>
> Key: MRELEASE-1123
> URL: https://issues.apache.org/jira/browse/MRELEASE-1123
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0
> Environment: Any
>Reporter: Lenny Primak
>Priority: Blocker
>
> {code:java}
> mvn -B -ntp -C release:prepare release:perform{code}
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
> project flowlogix: Unable to parse configuration of mojo
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
> projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
> org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
> org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
> org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
> to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]{code}
> Maven 4.0.0-alpha-5 and release plugin 3.0.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MRELEASE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722432#comment-17722432
]
Lenny Primak commented on MRELEASE-1123:
Tried alpha-4 but also fails.
Alphas 1-3 are not available for download anywhere I was searching for it.
> Maven Release plugin doesn't work in maven 4
>
>
> Key: MRELEASE-1123
> URL: https://issues.apache.org/jira/browse/MRELEASE-1123
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0
> Environment: Any
>Reporter: Lenny Primak
>Priority: Blocker
>
> {code:java}
> mvn -B -ntp -C release:prepare release:perform{code}
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
> project flowlogix: Unable to parse configuration of mojo
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
> projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
> org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
> org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
> org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
> to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]{code}
> Maven 4.0.0-alpha-5 and release plugin 3.0.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MRELEASE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722402#comment-17722402
]
Lenny Primak commented on MRELEASE-1123:
No, I did not. It's failing with the latest (alpha-5 as of now)
> Maven Release plugin doesn't work in maven 4
>
>
> Key: MRELEASE-1123
> URL: https://issues.apache.org/jira/browse/MRELEASE-1123
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0
> Environment: Any
>Reporter: Lenny Primak
>Priority: Blocker
>
> {code:java}
> mvn -B -ntp -C release:prepare release:perform{code}
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
> project flowlogix: Unable to parse configuration of mojo
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
> projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
> org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
> org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
> org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
> to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]{code}
> Maven 4.0.0-alpha-5 and release plugin 3.0.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MRELEASE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722397#comment-17722397
]
Lenny Primak commented on MRELEASE-1123:
Correct. Maven 4 only.
Thank you!
> Maven Release plugin doesn't work in maven 4
>
>
> Key: MRELEASE-1123
> URL: https://issues.apache.org/jira/browse/MRELEASE-1123
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0
> Environment: Any
>Reporter: Lenny Primak
>Priority: Blocker
>
> {code:java}
> mvn -B -ntp -C release:prepare release:perform{code}
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
> project flowlogix: Unable to parse configuration of mojo
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
> projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
> org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
> org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
> org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
> to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]{code}
> Maven 4.0.0-alpha-5 and release plugin 3.0.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MRELEASE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722333#comment-17722333
]
Lenny Primak commented on MRELEASE-1123:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
project flowlogix: Unable to parse configuration of mojo
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
project flowlogix: Unable to parse configuration of mojo
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
org.apache.maven.plugins.release.PrepareReleaseMojo
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:341)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:324)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:77)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:114)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:60)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:132)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:313)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:228)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:153)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:865)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:284)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:201)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:578)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable to
parse configuration of mojo
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
org.apache.maven.plugins.release.PrepareReleaseMojo
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populateMojoExecutionFields
(DefaultMavenPluginManager.java:655)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
(DefaultMavenPluginManager.java:588)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:132)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:336)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:324)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:77)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:114)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
[jira] [Updated] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MRELEASE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenny Primak updated MRELEASE-1123:
---
Description:
{code:java}
mvn -B -ntp -C release:prepare release:perform{code}
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
project flowlogix: Unable to parse configuration of mojo
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]{code}
Maven 4.0.0-alpha-5 and release plugin 3.0.0
was:
mvn -B -ntp -C release:prepare release:perform
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
project flowlogix: Unable to parse configuration of mojo
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]
Maven 4.0.0-alpha-5 and release plugin 3.0.0
> Maven Release plugin doesn't work in maven 4
>
>
> Key: MRELEASE-1123
> URL: https://issues.apache.org/jira/browse/MRELEASE-1123
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0
> Environment: Any
>Reporter: Lenny Primak
>Priority: Blocker
>
> {code:java}
> mvn -B -ntp -C release:prepare release:perform{code}
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
> project flowlogix: Unable to parse configuration of mojo
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
> projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
> org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
> org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
> org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
> to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]{code}
> Maven 4.0.0-alpha-5 and release plugin 3.0.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7781) Maven Release plugin doesn't work in maven 4
[
https://issues.apache.org/jira/browse/MNG-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722332#comment-17722332
]
Lenny Primak commented on MNG-7781:
---
Please close this. I put the issue in the correct place here:
https://issues.apache.org/jira/browse/MRELEASE-1123
> Maven Release plugin doesn't work in maven 4
>
>
> Key: MNG-7781
> URL: https://issues.apache.org/jira/browse/MNG-7781
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 4.0.0-alpha-5
> Environment: Any
>Reporter: Lenny Primak
>Priority: Blocker
>
> {code:java}
> mvn -B -ntp -C release:prepare release:perform {code}
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
> project flowlogix: Unable to parse configuration of mojo
> org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
> projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
> org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
> org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
> org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
> to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]
> {code}
> Maven 4.0.0-alpha-5 and release plugin 3.0.0
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7627) Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ Maven 4
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722331#comment-17722331 ] Lenny Primak commented on MNG-7627: --- Issue with the maven release plugin: https://issues.apache.org/jira/browse/MRELEASE-1123 > Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ > Maven 4 > > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (MNG-7627) Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ Maven 4
[ https://issues.apache.org/jira/browse/MNG-7627 ] Lenny Primak deleted comment on MNG-7627: --- was (Author: lprimak): Issue with the maven release plugin: https://issues.apache.org/jira/browse/MNG-7781 > Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ > Maven 4 > > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRELEASE-1123) Maven Release plugin doesn't work in maven 4
Lenny Primak created MRELEASE-1123: -- Summary: Maven Release plugin doesn't work in maven 4 Key: MRELEASE-1123 URL: https://issues.apache.org/jira/browse/MRELEASE-1123 Project: Maven Release Plugin Issue Type: Bug Components: prepare Affects Versions: 3.0.0 Environment: Any Reporter: Lenny Primak mvn -B -ntp -C release:prepare release:perform [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on project flowlogix: Unable to parse configuration of mojo org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1] Maven 4.0.0-alpha-5 and release plugin 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7781) Maven Release plugin doesn't work in maven 4
Lenny Primak created MNG-7781:
-
Summary: Maven Release plugin doesn't work in maven 4
Key: MNG-7781
URL: https://issues.apache.org/jira/browse/MNG-7781
Project: Maven
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 4.0.0-alpha-5
Environment: Any
Reporter: Lenny Primak
{code:java}
mvn -B -ntp -C release:prepare release:perform {code}
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare (default-cli) on
project flowlogix: Unable to parse configuration of mojo
org.apache.maven.plugins:maven-release-plugin:3.0.0:prepare for parameter
projectVersionPolicyConfig: Cannot set 'projectVersionPolicyConfig' in class
org.apache.maven.plugins.release.PrepareReleaseMojo: Can not set
org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration field
org.apache.maven.plugins.release.PrepareReleaseMojo.projectVersionPolicyConfig
to org.apache.maven.internal.xml.XmlPlexusConfiguration -> [Help 1]
{code}
Maven 4.0.0-alpha-5 and release plugin 3.0.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7627) Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ Maven 4
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722330#comment-17722330 ] Lenny Primak commented on MNG-7627: --- Issue with the maven release plugin: https://issues.apache.org/jira/browse/MNG-7781 > Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ > Maven 4 > > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7627) Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ Maven 4
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722328#comment-17722328 ] Lenny Primak commented on MNG-7627: --- Tried it, but release plugin doesn't work. Will file another issue for that. > Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ > Maven 4 > > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHECKSTYLE-429) Deprecation warning
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenny Primak updated MCHECKSTYLE-429:
-
Affects Version/s: 3.2.2
> Deprecation warning
> ---
>
> Key: MCHECKSTYLE-429
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-429
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:checkstyle
>Affects Versions: 3.2.1, 3.2.2
>Reporter: Lenny Primak
>Priority: Major
>
> Every time checkstyle plugin is ran, the following warning occurs:
> {code:java}
> [INFO] --- checkstyle:3.2.1:checkstyle (default) @ shiro-cdi ---
> [WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
> use of ArtifactRepository type. If you need access to local repository,
> switch to '${repositorySystemSession}' expression and get LRM from it instead.
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO] Starting audit...
> Audit done.
> {code}
> Looks like maven 3.9.x deprecated `localRepository` variable and the plugin
> needs to be updated to reflect this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MCHECKSTYLE-429) Deprecation warning
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721955#comment-17721955
]
Lenny Primak commented on MCHECKSTYLE-429:
--
Thanks guys! Looking forward to the fix!
> Deprecation warning
> ---
>
> Key: MCHECKSTYLE-429
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-429
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:checkstyle
>Affects Versions: 3.2.1
>Reporter: Lenny Primak
>Priority: Major
>
> Every time checkstyle plugin is ran, the following warning occurs:
> {code:java}
> [INFO] --- checkstyle:3.2.1:checkstyle (default) @ shiro-cdi ---
> [WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
> use of ArtifactRepository type. If you need access to local repository,
> switch to '${repositorySystemSession}' expression and get LRM from it instead.
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO] Starting audit...
> Audit done.
> {code}
> Looks like maven 3.9.x deprecated `localRepository` variable and the plugin
> needs to be updated to reflect this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPOM-344) Update maven-remote-resources-plugin to 3.1.0
[ https://issues.apache.org/jira/browse/MPOM-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704355#comment-17704355 ] Lenny Primak commented on MPOM-344: --- Same here. This plugin is not compatible with maven 3.9.x so please bump > Update maven-remote-resources-plugin to 3.1.0 > - > > Key: MPOM-344 > URL: https://issues.apache.org/jira/browse/MPOM-344 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: ASF-29 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: ASF-30 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MCHECKSTYLE-429) Deprecation warning / incompatible with maven 3.9.x
Lenny Primak created MCHECKSTYLE-429:
Summary: Deprecation warning / incompatible with maven 3.9.x
Key: MCHECKSTYLE-429
URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-429
Project: Maven Checkstyle Plugin
Issue Type: Bug
Components: checkstyle:checkstyle
Affects Versions: 3.2.1
Reporter: Lenny Primak
Every time checkstyle plugin is ran, the following warning occurs:
{code:java}
[INFO] --- checkstyle:3.2.1:checkstyle (default) @ shiro-cdi ---
[WARNING] Parameter 'localRepository' is deprecated core expression; Avoid use
of ArtifactRepository type. If you need access to local repository, switch to
'${repositorySystemSession}' expression and get LRM from it instead.
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin.
[INFO] Starting audit...
Audit done.
{code}
Looks like maven 3.9.x deprecated `localRepository` variable and the plugin
needs to be updated to reflect this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-631) Exclusion of generated code creates reference not found error
[
https://issues.apache.org/jira/browse/MJAVADOC-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703858#comment-17703858
]
Lenny Primak commented on MJAVADOC-631:
---
Same here
> Exclusion of generated code creates reference not found error
> -
>
> Key: MJAVADOC-631
> URL: https://issues.apache.org/jira/browse/MJAVADOC-631
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: javadoc
>Affects Versions: 3.1.1
> Environment: Maven 3.5.3
> Jdk 8
> maven-javadoc-plugin 3.1.1
>Reporter: Antoine Tran
>Priority: Major
>
> Using exclusion files, I excluded some generated code:
> {code:java}
>
> ${javadoc.excludes}
>
> {code}
> with a property for example:
> {code:java}
> **/generated/**{code}
> But the thing is, we reference some generated code classes in javadoc, so of
> course we have these errors of not found reference:
> {code:java}
> /var/lib/jenkins/jobs/[PathToJava].java:19: error: package
> ...mccommon.mcinterface.generated does not exist
> {code}
> {code:java}
> 15:03:08 /var/lib/jenkins/jobs/[PathToJava].java:33: error: cannot find
> symbol{code}
> {code:java}
> 15:03:08 implements HistoricalRequestParameter IFAMQPRequestHistoricDataResponse>
> 15:03:08 symbol: class IFAMQPADMRequestHistoricData{code}
> So either we don't exclude referenced classes, but we have multiple error
> from a generated code (in this case Avro generated code), or we exclude them,
> but in that case, we cannot reference them in the eye of maven-javadoc-plugin.
>
> There should be a way to either:
> * exclude some code and ignore reference to these classes
> * or mark some generated code as special, so that we generated javadoc for
> them too, but we silently ignore any warnings/errors related to them
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7746) Update maven-help-plugin to 3.4.0 or later
[ https://issues.apache.org/jira/browse/MNG-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703222#comment-17703222 ] Lenny Primak commented on MNG-7746: --- I don't seem to have access to close this issue. Please close it. > Update maven-help-plugin to 3.4.0 or later > -- > > Key: MNG-7746 > URL: https://issues.apache.org/jira/browse/MNG-7746 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 4.0.0-alpha-4, 4.0.0-alpha-5 >Reporter: Lenny Primak >Priority: Trivial > > When executing maven help:all-profiles (possibly outside any project), the > default is too old and is incompatible with current 4.x maven builds. Please > upgrade maven to refer to the latest help plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7746) Update maven-help-plugin to 3.4.0 or later
[ https://issues.apache.org/jira/browse/MNG-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated MNG-7746: -- Priority: Trivial (was: Major) > Update maven-help-plugin to 3.4.0 or later > -- > > Key: MNG-7746 > URL: https://issues.apache.org/jira/browse/MNG-7746 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 4.0.0-alpha-4, 4.0.0-alpha-5 >Reporter: Lenny Primak >Priority: Trivial > > When executing maven help:all-profiles (possibly outside any project), the > default is too old and is incompatible with current 4.x maven builds. Please > upgrade maven to refer to the latest help plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7746) Update maven-help-plugin to 3.4.0 or later
[ https://issues.apache.org/jira/browse/MNG-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703221#comment-17703221 ] Lenny Primak commented on MNG-7746: --- ha! Learn something new every day! Thank you > Update maven-help-plugin to 3.4.0 or later > -- > > Key: MNG-7746 > URL: https://issues.apache.org/jira/browse/MNG-7746 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 4.0.0-alpha-4, 4.0.0-alpha-5 >Reporter: Lenny Primak >Priority: Major > > When executing maven help:all-profiles (possibly outside any project), the > default is too old and is incompatible with current 4.x maven builds. Please > upgrade maven to refer to the latest help plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7746) Update maven-help-plugin to 3.4.0 or later
Lenny Primak created MNG-7746: - Summary: Update maven-help-plugin to 3.4.0 or later Key: MNG-7746 URL: https://issues.apache.org/jira/browse/MNG-7746 Project: Maven Issue Type: Dependency upgrade Components: Dependencies Affects Versions: 4.0.0-alpha-4, 4.0.0-alpha-5 Reporter: Lenny Primak When executing maven help:all-profiles (possibly outside any project), the default is too old and is incompatible with current 4.x maven builds. Please upgrade maven to refer to the latest help plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7745) NPE when .mvn doesn't exist
Lenny Primak created MNG-7745:
-
Summary: NPE when .mvn doesn't exist
Key: MNG-7745
URL: https://issues.apache.org/jira/browse/MNG-7745
Project: Maven
Issue Type: Bug
Components: Core
Affects Versions: 4.0.0-alpha-4, 4.0.0-alpha-5
Environment: Any
Reporter: Lenny Primak
When maven is executed without a .mvn directory, an NPE appears every time.
This doesn't seem to affect anything but does pollute the logs:
{code:java}
Failed to notify spy org.apache.maven.ReactorReader$ReactorReaderSpy: Cannot
invoke "java.io.File.toPath()" because the return value of
"org.apache.maven.project.MavenProject.getFile()" is null {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7628) help:all-profiles doesn't work if there are any profiles in setting.xml
[
https://issues.apache.org/jira/browse/MNG-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699368#comment-17699368
]
Lenny Primak commented on MNG-7628:
---
Indeed, it works with Alpha 4.
Thanks for the fix!!!
> help:all-profiles doesn't work if there are any profiles in setting.xml
> ---
>
> Key: MNG-7628
> URL: https://issues.apache.org/jira/browse/MNG-7628
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-2
>Reporter: Lenny Primak
>Assignee: Guillaume Nodet
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> As in title, if any profiles are defined in user's settings.xml, the below
> error is produced
> {code:java}
> % mvn help:all-profiles -N
> [INFO] Scanning for projects...
> [INFO] Inspecting build with total of 1 modules...
> [INFO] Installing Nexus Staging features:
> [INFO] ... total of 1 executions of maven-deploy-plugin replaced with
> nexus-staging-maven-plugin
> [INFO]
> [INFO] ---<
> com.flowlogix:flowlogix >
> [INFO] Building Flow Logix Root 5.x-SNAPSHOT
> [INFO] from pom.xml
> [INFO] -[ pom
> ]--
> [INFO]
> [INFO] --- maven-help-plugin:3.3.0:all-profiles (default-cli) @ flowlogix ---
> [INFO]
> --
> [INFO] BUILD FAILURE
> [INFO]
> --
> [INFO] Total time: 2.041 s
> [INFO] Finished at: 2022-12-13T18:51:46-06:00
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.3.0:all-profiles (default-cli)
> on project flowlogix: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.3.0:all-profiles failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-help-plugin:3.3.0:all-profiles:
> java.lang.NoSuchMethodError: 'org.apache.maven.model.Profile
> org.apache.maven.settings.SettingsUtils.convertFromSettingsProfile(org.apache.maven.settings.Profile)'
> [ERROR] -
> [ERROR] realm = plugin>org.apache.maven.plugins:maven-help-plugin:3.3.0
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/lprimak/.m2/repository/org/apache/maven/plugins/maven-help-plugin/3.3.0/maven-help-plugin-3.3.0.jar
> [ERROR] urls[1] =
> file:/Users/lprimak/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-tools-generators/3.6.4/maven-plugin-tools-generators-3.6.4.jar
> [ERROR] urls[2] =
> file:/Users/lprimak/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-tools-api/3.6.4/maven-plugin-tools-api-3.6.4.jar
> [ERROR] urls[3] =
> file:/Users/lprimak/.m2/repository/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.jar
> [ERROR] urls[4] =
> file:/Users/lprimak/.m2/repository/commons-collections/commons-collections/3.1/commons-collections-3.1.jar
> [ERROR] urls[5] =
> file:/Users/lprimak/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar
> [ERROR] urls[6] =
> file:/Users/lprimak/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> [ERROR] urls[7] =
> file:/Users/lprimak/.m2/repository/net/sf/jtidy/jtidy/r938/jtidy-r938.jar
> [ERROR] urls[8] =
> file:/Users/lprimak/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> [ERROR] urls[9] =
> file:/Users/lprimak/.m2/repository/org/ow2/asm/asm-commons/9.3/asm-commons-9.3.jar
> [ERROR] urls[10] =
> file:/Users/lprimak/.m2/repository/org/ow2/asm/asm-tree/9.3/asm-tree-9.3.jar
> [ERROR] urls[11] =
> file:/Users/lprimak/.m2/repository/org/ow2/asm/asm-analysis/9.3/asm-analysis-9.3.jar
> [ERROR] urls[12] =
> file:/Users/lprimak/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.3.4/maven-shared-utils-3.3.4.jar
> [ERROR] urls[13] =
> file:/Users/lprimak/.m2/repository/commons-io/commons-io/2.6/commons-io-2.6.jar
> [ERROR] urls[14] =
> file:/Users/lprimak/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.1.1/maven-reporting-api-3.1.1.jar
> [ERROR] urls[15] =
> file:/Users/lprimak/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> [ERROR] urls[16] =
> file:/Users/lprimak/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> [ERROR] urls[17] =
>
[jira] [Commented] (MNG-7622) Reimplement Consumer POM feature
[ https://issues.apache.org/jira/browse/MNG-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690571#comment-17690571 ] Lenny Primak commented on MNG-7622: --- I have created a Sonatype ticket for this: [https://issues.sonatype.org/browse/MVNCENTRAL-7850] > Reimplement Consumer POM feature > > > Key: MNG-7622 > URL: https://issues.apache.org/jira/browse/MNG-7622 > Project: Maven > Issue Type: Task > Components: build/consumer >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-4, 4.0.0 > > > Current implementation relies on deprecated resolver API (is deprecated as it > is OOM prone), and also renders use cases like m-gpg-p but also checksum-m-p > broken. > Reimplement consumer POM feature that: > * does not use FileTransformer API > * allows use cases like m-gpg-p -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7622) Reimplement Consumer POM feature
[ https://issues.apache.org/jira/browse/MNG-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690053#comment-17690053 ] Lenny Primak commented on MNG-7622: --- Any workarounds? > Reimplement Consumer POM feature > > > Key: MNG-7622 > URL: https://issues.apache.org/jira/browse/MNG-7622 > Project: Maven > Issue Type: Task > Components: build/consumer >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-4, 4.0.0 > > > Current implementation relies on deprecated resolver API (is deprecated as it > is OOM prone), and also renders use cases like m-gpg-p but also checksum-m-p > broken. > Reimplement consumer POM feature that: > * does not use FileTransformer API > * allows use cases like m-gpg-p -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7622) Reimplement Consumer POM feature
[
https://issues.apache.org/jira/browse/MNG-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690050#comment-17690050
]
Lenny Primak commented on MNG-7622:
---
[~cstamas] This breaks Nexus staging / deployment to maven central:
{code:java}
[INFO] [ERROR] Failed to execute goal
org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy (deploy) on
project jee-examples: Remote staging failed: Failed to deploy artifacts: Could
not transfer artifact com.flowlogix:flowlogix-bom:pom.asc:5.3.3-A2 from/to
flowlogix-maven-central
(https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/comflowlogix-1124):
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/flowlogix-bom/5.3.3-A2/flowlogix-bom-5.3.3-A2-consumer.pom.asc
-> [Help 1] {code}
> Reimplement Consumer POM feature
>
>
> Key: MNG-7622
> URL: https://issues.apache.org/jira/browse/MNG-7622
> Project: Maven
> Issue Type: Task
> Components: build/consumer
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0-alpha-4, 4.0.0
>
>
> Current implementation relies on deprecated resolver API (is deprecated as it
> is OOM prone), and also renders use cases like m-gpg-p but also checksum-m-p
> broken.
> Reimplement consumer POM feature that:
> * does not use FileTransformer API
> * allows use cases like m-gpg-p
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7627) Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ Maven 4
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated MNG-7627: -- Summary: Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ Maven 4 (was: Sonatype Staging plugin does not plug into deploy lifecycle correctly) > Sonatype Staging plugin does not plug into deploy lifecycle correctly w/ > Maven 4 > > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7627) Sonatype Staging plugin does not plug into deploy lifecycle correctly
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated MNG-7627: -- Summary: Sonatype Staging plugin does not plug into deploy lifecycle correctly (was: Maven release plugin doesn't upload artifacts to maven central (sonatype staging plugin)) > Sonatype Staging plugin does not plug into deploy lifecycle correctly > - > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7632) Regression: combine.children breaks when combining executions
Lenny Primak created MNG-7632: - Summary: Regression: combine.children breaks when combining executions Key: MNG-7632 URL: https://issues.apache.org/jira/browse/MNG-7632 Project: Maven Issue Type: Bug Components: Core Affects Versions: 4.0.0-alpha-2 Reporter: Lenny Primak When upgrading from 3.x to 4.x, combine.children behaves differently. When it is declared in the parent pom, the child pom do not correctly combines elements: See [https://github.com/flowlogix/flowlogix/commit/301f428a229f4ab51e55a488bd71ec4aec87bce4] for a reproducer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central (sonatype staging plugin)
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated MNG-7627: -- Summary: Maven release plugin doesn't upload artifacts to maven central (sonatype staging plugin) (was: Maven release plugin doesn't upload artifacts to maven central) > Maven release plugin doesn't upload artifacts to maven central (sonatype > staging plugin) > > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647612#comment-17647612 ] Lenny Primak commented on MNG-7627: --- Filed with Sonatype: [https://issues.sonatype.org/browse/NEXUS-36533] > Maven release plugin doesn't upload artifacts to maven central > -- > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647605#comment-17647605 ] Lenny Primak commented on MNG-7627: --- > For nexus-staging-plugin you should report an issue on Sonatype Jira [~sjaranowski] Maybe... this is more of an integration issue so probably needs to be looked at both Maven and Sonatype teams, since it works on Maven 3 but not maven 4 > Maven release plugin doesn't upload artifacts to maven central > -- > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated MNG-7627: -- Priority: Minor (was: Blocker) > Maven release plugin doesn't upload artifacts to maven central > -- > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646892#comment-17646892 ] Lenny Primak commented on MNG-7627: --- It looks like that nexus-staging-maven-plugin has some magic to replace maven deploy plugin to do deferred deploys, and that magic breaks in maven 4. I was able to work around the problem by disabling maven deploy plugin and adding execution steps to the nexus staging plugin to make deferred uploads work > Maven release plugin doesn't upload artifacts to maven central > -- > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Blocker > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central
[ https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646893#comment-17646893 ] Lenny Primak commented on MNG-7627: --- I have bumped down the priority to minor since there is a workaround > Maven release plugin doesn't upload artifacts to maven central > -- > > Key: MNG-7627 > URL: https://issues.apache.org/jira/browse/MNG-7627 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-2 >Reporter: Lenny Primak >Priority: Minor > > Maven release plugin not working with 4.0-alpha-2 > 3.x works fine with the same configuration. > Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7628) help:all-profiles doesn't work if there are any profiles in setting.xml
Lenny Primak created MNG-7628:
-
Summary: help:all-profiles doesn't work if there are any profiles
in setting.xml
Key: MNG-7628
URL: https://issues.apache.org/jira/browse/MNG-7628
Project: Maven
Issue Type: Bug
Affects Versions: 4.0.0-alpha-2
Reporter: Lenny Primak
As in title, if any profiles are defined in user's settings.xml, the below
error is produced
{code:java}
% mvn help:all-profiles -N
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 1 executions of maven-deploy-plugin replaced with
nexus-staging-maven-plugin
[INFO]
[INFO] ---< com.flowlogix:flowlogix
>
[INFO] Building Flow Logix Root 5.x-SNAPSHOT
[INFO] from pom.xml
[INFO] -[ pom
]--
[INFO]
[INFO] --- maven-help-plugin:3.3.0:all-profiles (default-cli) @ flowlogix ---
[INFO]
--
[INFO] BUILD FAILURE
[INFO]
--
[INFO] Total time: 2.041 s
[INFO] Finished at: 2022-12-13T18:51:46-06:00
[INFO]
--
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-help-plugin:3.3.0:all-profiles (default-cli) on
project flowlogix: Execution default-cli of goal
org.apache.maven.plugins:maven-help-plugin:3.3.0:all-profiles failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-help-plugin:3.3.0:all-profiles:
java.lang.NoSuchMethodError: 'org.apache.maven.model.Profile
org.apache.maven.settings.SettingsUtils.convertFromSettingsProfile(org.apache.maven.settings.Profile)'
[ERROR] -
[ERROR] realm = plugin>org.apache.maven.plugins:maven-help-plugin:3.3.0
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/lprimak/.m2/repository/org/apache/maven/plugins/maven-help-plugin/3.3.0/maven-help-plugin-3.3.0.jar
[ERROR] urls[1] =
file:/Users/lprimak/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-tools-generators/3.6.4/maven-plugin-tools-generators-3.6.4.jar
[ERROR] urls[2] =
file:/Users/lprimak/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-tools-api/3.6.4/maven-plugin-tools-api-3.6.4.jar
[ERROR] urls[3] =
file:/Users/lprimak/.m2/repository/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.jar
[ERROR] urls[4] =
file:/Users/lprimak/.m2/repository/commons-collections/commons-collections/3.1/commons-collections-3.1.jar
[ERROR] urls[5] =
file:/Users/lprimak/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar
[ERROR] urls[6] =
file:/Users/lprimak/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[7] =
file:/Users/lprimak/.m2/repository/net/sf/jtidy/jtidy/r938/jtidy-r938.jar
[ERROR] urls[8] =
file:/Users/lprimak/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
[ERROR] urls[9] =
file:/Users/lprimak/.m2/repository/org/ow2/asm/asm-commons/9.3/asm-commons-9.3.jar
[ERROR] urls[10] =
file:/Users/lprimak/.m2/repository/org/ow2/asm/asm-tree/9.3/asm-tree-9.3.jar
[ERROR] urls[11] =
file:/Users/lprimak/.m2/repository/org/ow2/asm/asm-analysis/9.3/asm-analysis-9.3.jar
[ERROR] urls[12] =
file:/Users/lprimak/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.3.4/maven-shared-utils-3.3.4.jar
[ERROR] urls[13] =
file:/Users/lprimak/.m2/repository/commons-io/commons-io/2.6/commons-io-2.6.jar
[ERROR] urls[14] =
file:/Users/lprimak/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.1.1/maven-reporting-api-3.1.1.jar
[ERROR] urls[15] =
file:/Users/lprimak/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
[ERROR] urls[16] =
file:/Users/lprimak/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
[ERROR] urls[17] =
file:/Users/lprimak/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.6.0/maven-reporting-exec-1.6.0.jar
[ERROR] urls[18] =
file:/Users/lprimak/.m2/repository/javax/enterprise/cdi-api/1.2/cdi-api-1.2.jar
[ERROR] urls[19] =
file:/Users/lprimak/.m2/repository/org/eclipse/sisu/org.eclipse.sisu.inject/0.3.5/org.eclipse.sisu.inject-0.3.5.jar
[ERROR] urls[20] =
file:/Users/lprimak/.m2/repository/org/sonatype/sisu/sisu-guice/3.2.3/sisu-guice-3.2.3-no_aop.jar
[ERROR] urls[21] =
file:/Users/lprimak/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar
[ERROR]
[jira] [Commented] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central
[
https://issues.apache.org/jira/browse/MNG-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646884#comment-17646884
]
Lenny Primak commented on MNG-7627:
---
Yes, snapshots deploy fine with Maven 4.
There are no errors, the nexus-staging-maven-plugin is just not getting invoked
from maven release plugin in Maven 4.
See below, the log from maven 3. Maven 4 just stops (successfully) and doesn't
produce logs like the ones below.
{code:java}
[INFO] [INFO] --- nexus-staging-maven-plugin:1.6.13:deploy
(injected-nexus-deploy) @ jee-examples ---
[INFO] [INFO] Performing local staging (local
stagingDirectory="/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging")...
[INFO] [INFO] + Using server credentials "flowlogix-maven-central" from Maven
settings.
[INFO] [INFO] * Connected to Nexus at https://oss.sonatype.org:443/, is
version 2.15.1-02 and edition "Professional"
[INFO] [INFO] * Using staging profile ID "1019fa80512c9" (matched by Nexus).
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/target/jee-examples-5.2.0-M1.war
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1.war
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/pom.xml
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1.pom
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/target/jee-examples-5.2.0-M1-sources.jar
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1-sources.jar
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/target/jee-examples-5.2.0-M1-javadoc.jar
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1-javadoc.jar
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/target/jee-examples-5.2.0-M1-sources.jar.asc
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1-sources.jar.asc
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/target/jee-examples-5.2.0-M1.pom.asc
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1.pom.asc
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/target/jee-examples-5.2.0-M1-javadoc.jar.asc
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1-javadoc.jar.asc
[INFO] [INFO] Installing
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/jakarta-ee/jee-examples/target/jee-examples-5.2.0-M1.war.asc
to
/Users/software/var/jenkins/workspace/flowlogix-ee-release_main/target/checkout/target/nexus-staging/staging/1019fa80512c9/com/flowlogix/jee-examples/5.2.0-M1/jee-examples-5.2.0-M1.war.asc
[INFO] [INFO] Performing remote staging...
[INFO] [INFO]
[INFO] [INFO] * Remote staging into staging profile ID "1019fa80512c9"
[INFO] [INFO] * Created staging repository with ID "comflowlogix-1164".
[INFO] [INFO] * Staging repository at
https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/comflowlogix-1164
[INFO] [INFO] * Uploading locally staged artifacts to profile com.flowlogix
[INFO] [INFO] Uploading to flowlogix-maven-central:
https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/comflowlogix-1164/com/flowlogix/flowlogix-jee/5.2.0-M1/flowlogix-jee-5.2.0-M1.jar.asc
[INFO] [INFO] Uploaded to flowlogix-maven-central:
https://oss.sonatype.org:443/service/local/stagi {code}
> Maven release plugin doesn't upload artifacts to maven central
> --
>
> Key: MNG-7627
> URL: https://issues.apache.org/jira/browse/MNG-7627
> Project: Maven
> Issue Type:
[jira] [Created] (MNG-7627) Maven release plugin doesn't upload artifacts to maven central
Lenny Primak created MNG-7627: - Summary: Maven release plugin doesn't upload artifacts to maven central Key: MNG-7627 URL: https://issues.apache.org/jira/browse/MNG-7627 Project: Maven Issue Type: Bug Affects Versions: 4.0.0-alpha-2 Reporter: Lenny Primak Maven release plugin not working with 4.0-alpha-2 3.x works fine with the same configuration. Build succeeds but the staging repository on maven central is not uploaded -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7204) Maven might pick up the wrong settings when the plugin happens to include relocation information
[
https://issues.apache.org/jira/browse/MNG-7204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17391239#comment-17391239
]
Lenny Primak commented on MNG-7204:
---
Voted
> Maven might pick up the wrong settings when the plugin happens to include
> relocation information
>
>
> Key: MNG-7204
> URL: https://issues.apache.org/jira/browse/MNG-7204
> Project: Maven
> Issue Type: Bug
>Reporter: S L
>Priority: Critical
> Attachments: MNG-7204.zip
>
>
> h1. Issue Description
> The relocation process is outlined in
> [here|https://maven.apache.org/guides/mini/guide-relocation.html] and IMHO
> boils down to adding the relocation information into the
> distributionManagement.
> For the sake of experimenting assume we want to relocate a plugin from
> {code:java}
> com.example.plugins
> test-plugin
> {code}
> to
> {code:java}
> com.test.plugins
> test-plugin-enhanced
> {code}
> To visualize the issue the plugin needs one configuration parameter (let's
> call it helloString). Based on the relocation guide my understanding is that
> we need two publications. One under the old coordinates and one under the new
> coordinates.
> When invoking the plugin with the old coordinates it will **not** pickup our
> configuration supplied. Consider:
> {code:java}
> com.example.plugins
> test-plugin
> 0.0.1
>
> from Maven!
>
> {code}
> h1. Issue Reproducer
> Attached I have an example that consists of essentially two parts. On a high
> level my understanding is that the the publication under the "old"
> coordinates can have a jar ("01_project_old_coordinates_with_jar"), but
> doesn't need to have one which would then essentially be a relocation pom
> ("01_project_old_coordinates_without_jar").
> The project publication with jar allows to see the expected by running
> {code:java}
> cd 01_project_old_coordinates_with_jar
> mvn clean install
> mvn clean package -Pdemo
> {code}
> which outputs {{Hello from Maven!}} (since this is the setting configured in
> the pom).
> When the relocation is done ("02_project_new_coordinates") and a new version
> under the new coordinates is published (but one still points to the old
> configuration) the configuration will not be picked up.
> {code:java}
> cd 02_project_new_coordinates
> # install the SAME version under new coordinates
> mvn clean install
> # run the demo again which still points to the OLD config
> mvn clean package -Pdemo
> {code}
> which output {{Hello World!}}. World is the default encoded in the Mojo, but
> **not** what was provided to the plugin config!
> This issue can also be observed when the publication under the old
> coordinates is just a relocation pom.
> h1. Reproducible under
> {code:java}
> $ mvn --version
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> Maven home: /usr/share/maven-3.6.1
> Java version: 11.0.11, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-11-oracle
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.4.0-77-generic", arch: "amd64", family: "unix"
> {code}
> {code:java}
> $ mvn --version
> Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
> Maven home: /usr/share/maven-3.8.1
> Java version: 11.0.11, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-11-oracle
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.4.0-77-generic", arch: "amd64", family: "unix"
> {code}
> Potentially many other versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352419#comment-352419 ] Lenny Primak commented on MDEP-451: --- The reason copy-dependencies doesn't work for me is that i have specified additional dependencies in artifactItems section and copy-dependencies does not listen to that element. Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-456) Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451
[ https://jira.codehaus.org/browse/MDEP-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352421#comment-352421 ] Lenny Primak commented on MDEP-456: --- Thanks for your suggestion, but it doesn't work for me for the same reason copy-dependencies doesn't work for me, i.e. it doesn't listen to artifactItems section in the pom Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 Key: MDEP-456 URL: https://jira.codehaus.org/browse/MDEP-456 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Lenny Primak Priority: Minor Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352423#comment-352423 ] Lenny Primak commented on MDEP-451: --- I see I am getting major pushback from you. This is your right, but I would prefer more of a welcoming attitude, I am just trying to contribute to the plugin, and all I am getting from you is defensive posture. Believe me, I have spent a lot of time on this, I'd appreciate something besides no and can't or won't or don't' do this. I know how to read the documentation, sort through source code and google stuff. In any case, you patch from above comments works (thank you!) You obviously know what to do to fix this bug. In the meanwhile I will use a clone of the project. This is critical for me to be fixed. Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352424#comment-352424 ] Lenny Primak commented on MDEP-451: --- Assembly plugin doesn't work for me for the same reason copy-dependencies doen't Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352426#comment-352426 ] Lenny Primak commented on MDEP-451: --- The complete use case is described pretty well here: http://code.google.com/p/flowlogix/wiki/TapestryLibrary#pom.xml:_if_you_are_running_in_Jetty_or_Tomcat,_brings_in_Glassf Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-456) Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451
[ https://jira.codehaus.org/browse/MDEP-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352428#comment-352428 ] Lenny Primak commented on MDEP-456: --- This effort is futile due to personal disagreement with projects' maintainers. Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 Key: MDEP-456 URL: https://jira.codehaus.org/browse/MDEP-456 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Lenny Primak Priority: Minor Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-456) Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451
[ https://jira.codehaus.org/browse/MDEP-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak closed MDEP-456. - Resolution: Won't Fix Maintainers refused to fix this issue Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 Key: MDEP-456 URL: https://jira.codehaus.org/browse/MDEP-456 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Lenny Primak Priority: Minor Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-455) CLONE - Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak closed MDEP-455. - Resolution: Duplicate CLONE - Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-455 URL: https://jira.codehaus.org/browse/MDEP-455 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-455) CLONE - Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
Lenny Primak created MDEP-455: - Summary: CLONE - Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-455 URL: https://jira.codehaus.org/browse/MDEP-455 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352346#comment-352346 ] Lenny Primak commented on MDEP-451: --- This is not accurate. I am pinning the plugin versions in my POM files, While your argument may be correct that it may be interpreted that it works as designed, I don't see anything in the plugin documentation suggesting so. For my project, it is a regression, because all I did is update maven with correctly designed Pom files. This bug makes dependency:copy completely useless to me. This may not be an unusual case anyway because if you want to gather all the dependencies in a multi-module project this is the only way I can see how to do it. Nevertheless I will open a new issue as you suggested. Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-456) Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451
Lenny Primak created MDEP-456: - Summary: Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 Key: MDEP-456 URL: https://jira.codehaus.org/browse/MDEP-456 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Lenny Primak Priority: Critical Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352347#comment-352347 ] Lenny Primak edited comment on MDEP-451 at 9/5/14 3:18 PM: --- Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-456 was (Author: lprimak): Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-456) Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451
[ https://jira.codehaus.org/browse/MDEP-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352357#comment-352357 ] Lenny Primak commented on MDEP-456: --- Maybe. Not 100% sure but it looks promising according to the docs I need to gather all the multi-module project's dependncies in one place Have you tried this plugin and can you confirm that it can accomplish this task? Thanks. Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 Key: MDEP-456 URL: https://jira.codehaus.org/browse/MDEP-456 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Lenny Primak Priority: Critical Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352400#comment-352400 ] Lenny Primak commented on MDEP-451: --- Thanks for the suggestion. I tried copy-dependencies as well but it didn't work for me either. Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352401#comment-352401 ] Lenny Primak commented on MDEP-451: --- I will try assembly and will let you know Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Assignee: Karl-Heinz Marbaise Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352327#comment-352327 ] Lenny Primak commented on MDEP-451: --- Yes, the maven dependency plugin version remained constant. The reason that I noticed the breakage is because my build started failing when upgrading maven, so the behavior definitely changed. I would gladly use a new goal if the change to existing one breaks things. Thanks Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351306#comment-351306 ] Lenny Primak commented on MDEP-451: --- Any updates on this issue? Thanks Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350779#comment-350779 ] Lenny Primak commented on MDEP-451: --- My guess is it's some kind of the plugin - maven interaction that's failing somewhere, due to some code changes in maven itself. I can create a sample project for you, but it's pretty obvious what's going on Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350778#comment-350778 ] Lenny Primak commented on MDEP-451: --- Not sure why this would be a maven-core issue. Other plugins run fine in the same project. It's only dependency:copy that doesn't get run. I would think that this would point squarely at the dependency plugin Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350786#comment-350786 ] Lenny Primak commented on MDEP-451: --- Here is what I did: - followed instruction to generate empty project from archetype from here: http://stackoverflow.com/questions/6328778/how-to-create-an-empty-multi-module-maven-project - added dependency copy config for junit (as simple as can be) - run dependency copy from root (not from the sub-module) $ mvn dependency:copy - see the difference between different versions of maven, dependency:copy doesn't run on sub-module. Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350786#comment-350786 ] Lenny Primak edited comment on MDEP-451 at 7/31/14 3:20 PM: Here is what I did: - followed instruction to generate empty project from archetype from here: http://stackoverflow.com/questions/6328778/how-to-create-an-empty-multi-module-maven-project - added dependency copy config for junit (as simple as can be) - run dependency copy from root (not from the sub-module) $ mvn dependency:copy - see the difference between different versions of maven, dependency:copy doesn't run on sub-module. If you configure any other plugin exactly the same way, it will run in the sub-module, but not the dependency plugin, i.e. this isn't a pure maven-core problem was (Author: lprimak): Here is what I did: - followed instruction to generate empty project from archetype from here: http://stackoverflow.com/questions/6328778/how-to-create-an-empty-multi-module-maven-project - added dependency copy config for junit (as simple as can be) - run dependency copy from root (not from the sub-module) $ mvn dependency:copy - see the difference between different versions of maven, dependency:copy doesn't run on sub-module. Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350786#comment-350786 ] Lenny Primak edited comment on MDEP-451 at 7/31/14 3:22 PM: Here is what I did: - followed instruction to generate empty project from archetype from here: http://stackoverflow.com/questions/6328778/how-to-create-an-empty-multi-module-maven-project - added dependency copy config for junit (as simple as can be) - run dependency copy from root (not from the sub-module) $ mvn dependency:copy surefire:test - see the difference between different versions of maven, dependency:copy doesn't run on sub-module. As you see, surefire will run in the submodule, but dependency:copy will not, under the latest versions of maven,i.e. this isn't a pure maven-core problem was (Author: lprimak): Here is what I did: - followed instruction to generate empty project from archetype from here: http://stackoverflow.com/questions/6328778/how-to-create-an-empty-multi-module-maven-project - added dependency copy config for junit (as simple as can be) - run dependency copy from root (not from the sub-module) $ mvn dependency:copy - see the difference between different versions of maven, dependency:copy doesn't run on sub-module. If you configure any other plugin exactly the same way, it will run in the sub-module, but not the dependency plugin, i.e. this isn't a pure maven-core problem Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350787#comment-350787 ] Lenny Primak commented on MDEP-451: --- The problem is bigger than I originally specified. dependency:copy doesn't recurse into submodules even in the 3.0.3 version of maven. In our own project I forced worked around that issue. Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lenny Primak updated MDEP-451: -- Attachment: deptest.tar Muldi-module project that illustrates this issue Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350791#comment-350791 ] Lenny Primak commented on MDEP-451: --- deptest is the main module module1 is the submodule: dep:copy runs on deptest (good) sep:copy does NOT run on module1 (bad) - blackbird:deptest lprimak$ pwd /Users/lprimak/Documents/devel/mvn_test/deptest blackbird:deptest lprimak$ mvn dependency:copy surefire:test [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] deptest [INFO] module1 [INFO] [INFO] [INFO] Building deptest 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:copy (default-cli) @ deptest --- [INFO] Configured Artifact: junit:junit:3.8.1:jar [INFO] Copying junit-3.8.1.jar to /Volumes/Home/Users/lprimak/Documents/devel/mvn_test/deptest/target/dependency/junit-3.8.1.jar [INFO] [INFO] [INFO] Building deptest 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-cli) @ deptest --- [INFO] No tests to run. [INFO] [INFO] [INFO] Building module1 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-surefire-plugin:2.7.2:test (default-cli) @ module1 --- [INFO] No tests to run. [INFO] Surefire report directory: /Volumes/Home/Users/lprimak/Documents/devel/mvn_test/deptest/module1/target/surefire-reports --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] deptest ... SUCCESS [0.189s] [INFO] module1 ... SUCCESS [0.639s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 2.455s [INFO] Finished at: Thu Jul 31 16:54:12 EDT 2014 [INFO] Final Memory: 12M/191M [INFO] - Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350791#comment-350791 ] Lenny Primak edited comment on MDEP-451 at 7/31/14 3:55 PM: deptest is the main module module1 is the submodule: dependency:copy runs on deptest (good) dependency:copy does NOT run on module1 (bad) - blackbird:deptest lprimak$ pwd /Users/lprimak/Documents/devel/mvn_test/deptest blackbird:deptest lprimak$ mvn dependency:copy surefire:test [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] deptest [INFO] module1 [INFO] [INFO] [INFO] Building deptest 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:copy (default-cli) @ deptest --- [INFO] Configured Artifact: junit:junit:3.8.1:jar [INFO] Copying junit-3.8.1.jar to /Volumes/Home/Users/lprimak/Documents/devel/mvn_test/deptest/target/dependency/junit-3.8.1.jar [INFO] [INFO] [INFO] Building deptest 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-cli) @ deptest --- [INFO] No tests to run. [INFO] [INFO] [INFO] Building module1 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-surefire-plugin:2.7.2:test (default-cli) @ module1 --- [INFO] No tests to run. [INFO] Surefire report directory: /Volumes/Home/Users/lprimak/Documents/devel/mvn_test/deptest/module1/target/surefire-reports --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] deptest ... SUCCESS [0.189s] [INFO] module1 ... SUCCESS [0.639s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 2.455s [INFO] Finished at: Thu Jul 31 16:54:12 EDT 2014 [INFO] Final Memory: 12M/191M [INFO] - was (Author: lprimak): deptest is the main module module1 is the submodule: dep:copy runs on deptest (good) sep:copy does NOT run on module1 (bad) - blackbird:deptest lprimak$ pwd /Users/lprimak/Documents/devel/mvn_test/deptest blackbird:deptest lprimak$ mvn dependency:copy surefire:test [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] deptest [INFO] module1 [INFO] [INFO] [INFO] Building deptest 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:copy (default-cli) @ deptest --- [INFO] Configured Artifact: junit:junit:3.8.1:jar [INFO] Copying junit-3.8.1.jar to /Volumes/Home/Users/lprimak/Documents/devel/mvn_test/deptest/target/dependency/junit-3.8.1.jar [INFO] [INFO] [INFO] Building deptest 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-cli) @ deptest --- [INFO] No tests to run. [INFO] [INFO] [INFO] Building module1 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-surefire-plugin:2.7.2:test (default-cli) @ module1 --- [INFO] No tests to run. [INFO] Surefire report directory: /Volumes/Home/Users/lprimak/Documents/devel/mvn_test/deptest/module1/target/surefire-reports
[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350793#comment-350793 ] Lenny Primak commented on MDEP-451: --- You are not executing the same cmd line: I am executing this: $ mvn dependency:copy surefire:test and you are executing something else. Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.2.2 multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350795#comment-350795 ] Lenny Primak commented on MDEP-451: --- Fantastic! in your case it's skipping the module only if there is nothing else to run, i.e. no surefire:test on the cmd line. If you put that back, the module1 gets run, but dependency:copy does not. I have a special profile that generates dependencies, and it uses defaultGoal to run the dependency:copy among other things. This incompatibility breaks the process in the later versions of maven. I really, really would like to get this fixed. Thank you Regression: mvn dependency:copy doesn't run under maven 3.2.2 multi-module project -- Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350798#comment-350798 ] Lenny Primak commented on MDEP-451: --- There are some other sideffects that make it work with 3.0.x, but it breaks in my project since 3.1 i.e. I can't run my project with maven 3.1+ Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350799#comment-350799 ] Lenny Primak commented on MDEP-451: --- I am hoping for a fix because it's a showstopper for me. Thank you for working with me on this, whether you fix it or not. Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
