[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[
https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378946#comment-17378946
]
Herve Boutemy commented on MPOM-255:
{quote}but to be honest reproducible builds for pom only projects don't seem to
be that reasonable.
{quote}
Apache official release is source = source-release.zip: do you think it is not
reasonable to achieve reproducibility for Apache official release?
And I will anticipate a little bit: with Maven 4 differentiating build vs
consumer POM, in the future, the published pom.xml will be different from
pom.xml in Git, then checking its reproducibility won't seem so trivial
And even for now: did you know that from one unique content in Git, there can
be 2 different pom.xml content published to Central, based on the OS from the
release manager (Windows or not)?
do you confirm "reproducible builds for pom only projects don't seem to be that
reasonable"?
{quote}This is not that easy to achieve as the rule requireProperty does not
distinguish between inherited and local properties
{quote}
I know I know, that's why I should have reviewed this issue before because I
should have anticipated there was something broken in the implementation
Notice: I don't judge, I'm not angry, I know that all was done with best
intentions and I hoped that you had found the right way to do the check because
I loved the intent. Thank you for all your efforts
> Enforce local property "project.build.outputTimestamp" for reproducible builds
> --
>
> Key: MPOM-255
> URL: https://issues.apache.org/jira/browse/MPOM-255
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-23
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
> Fix For: ASF-24
>
>
> In case the release's root pom.xml doesn't overwrite
> "project.build.outputTimestamp" it takes the value from
> [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.]
> Instead of the fallback an enforcer rule should be added to require a
> property "project.build.outputTimestamp" to be set in the right format for
> reproducible builds to work
> ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build])
> for every pom.xml locally.
> Only that way the timestamps are automatically adjusted with each release
> (https://issues.apache.org/jira/browse/MRELEASE-1029)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request #144: Bump maven-dependency-tree from 3.0.1 to 3.1.0
dependabot[bot] opened a new pull request #144: URL: https://github.com/apache/maven-dependency-plugin/pull/144 Bumps [maven-dependency-tree](https://github.com/apache/maven-dependency-tree) from 3.0.1 to 3.1.0. Commits https://github.com/apache/maven-dependency-tree/commit/7a40679ba52ba06a797f38a92d7b82c49e93d652;>7a40679 [maven-release-plugin] prepare release maven-dependency-tree-3.1.0 https://github.com/apache/maven-dependency-tree/commit/d31f0ca4ae9aeb29cf972d728689b56b1ced1fc8;>d31f0ca Move javadoc-plugin configuration to build-plugins due to javadoc:jar https://github.com/apache/maven-dependency-tree/commit/bf27a32551c4b58dd23c1711ab471a3d14c8d8d8;>bf27a32 [maven-release-plugin] rollback the release of maven-dependency-tree-3.1.0 https://github.com/apache/maven-dependency-tree/commit/4f6e5bfa567b6efe8e9e22f3d722a9452473ac06;>4f6e5bf [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-dependency-tree/commit/7223b5287a48f0755b1e10b17aa96950d707663f;>7223b52 [maven-release-plugin] prepare release maven-dependency-tree-3.1.0 https://github.com/apache/maven-dependency-tree/commit/02a17408ac3ee0f8fb9244f5008137c571139453;>02a1740 Fix JavaDoc https://github.com/apache/maven-dependency-tree/commit/b75341e94a3da823a69e7457228d20cdcb15b26d;>b75341e [maven-release-plugin] rollback the release of maven-dependency-tree-3.1.0 https://github.com/apache/maven-dependency-tree/commit/a49eae29b3bc1e7d1012877f9436bc423199889a;>a49eae2 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-dependency-tree/commit/3bd2fbdd69b373203ce428f77252cd770ec21c7f;>3bd2fbd [maven-release-plugin] prepare release maven-dependency-tree-3.1.0 https://github.com/apache/maven-dependency-tree/commit/4a64259b8e4113c28593ee8c02ec028e8751d194;>4a64259 Fix regression for Maven 3.0.5 Additional commits viewable in https://github.com/apache/maven-dependency-tree/compare/maven-dependency-tree-3.0.1...maven-dependency-tree-3.1.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-189) Using semaphore-redisson followed by rwlock-redisson on many parallel build of the same project triggers redisson error
[
https://issues.apache.org/jira/browse/MRESOLVER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378823#comment-17378823
]
Jacques-Etienne Beaudet commented on MRESOLVER-189:
---
You were right, I ran it 50 times back to back and got something like 4
failures. Logs sent for those too but I couldn't take a thread dump for them.
> Using semaphore-redisson followed by rwlock-redisson on many parallel build
> of the same project triggers redisson error
> ---
>
> Key: MRESOLVER-189
> URL: https://issues.apache.org/jira/browse/MRESOLVER-189
> Project: Maven Resolver
> Issue Type: Bug
>Reporter: Jacques-Etienne Beaudet
>Assignee: Michael Osipov
>Priority: Major
> Attachments: create_lock_events.sql, etl.sql, schema.sql
>
>
> While testing performance for in
> [https://github.com/apache/maven-resolver/pull/68|https://github.com/apache/maven-resolver/pull/68,]
> , I ran into an error using rwlock-redisson. Here are the steps to reproduce
> (hopefully it's easily reproducible on your end) and the logs of the run
> (trace enabled on org.eclipse.aether) at the end :
> * `redis-cli flushall` to get a clean slate
> * Clone a repository with a fair size
> * Make 4 copy of this repository (I ran my test with 4 copies, but 2 might
> be enough?)
> * `mvn clean` on all repositories
> * run a parallel build with semaphore-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=semaphore-redisson`) on all repositories
> * `mvn clean` all repositories
> * run a parallel build with rwlock-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=rwlock-redisson`) on all repositories
> By doing this, I ran into this and the only way out was running a `redis-cli
> flushall`.
>
> The way I ran my parallel build was really dumb and simple, something like
> that :
>
> {code:java}
> cd repo1 ; mvn clean > /tmp/log1 2>&1 & cd ../repo2 ; mvn clean > /tmp/log2
> 2>&1 & cd ../repo3 ; mvn clean > /tmp/log3 2>&1 & cd ../repo4 ; mvn clean >
> /tmp/log4 2>&1 & cd .. ;
> {code}
>
>
> Let me know if you can't reproduce, I might be able to provide you with
> traces logs of the semaphore build as well.
> {code:java}
> [INFO] Redisson 3.15.6
> [INFO] 1 connections initialized for localhost/127.0.0.1:6379
> [INFO] 24 connections initialized for localhost/127.0.0.1:6379
> [TRACE] Created Redisson client with id '42934566-3759-4f73-9fbc-a2d0a8368e1f'
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> /root/.m2/repository
> [INFO] Scanning for projects...
> [TRACE] Need 1 write lock(s) for
> [artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0]
> [TRACE] Acquiring write lock for
> 'artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0'
> [ERROR] Internal error: org.redisson.client.RedisException: ERR Error running
> script (call to f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1:
> WRONGTYPE Operation against a key holding the wrong kind of value. channel:
> [id: 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command:
> (EVAL), params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode
> == false) then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> org.redisson.client.RedisException: ERR Error running script (call to
> f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1: WRONGTYPE
> Operation against a key holding the wrong kind of value. channel: [id:
> 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command: (EVAL),
> params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode == false)
> then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write]
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at
[jira] [Comment Edited] (MCOMPILER-461) Compile fails when class references a class generated by an annotation processor and module-info.java is present
[
https://issues.apache.org/jira/browse/MCOMPILER-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378813#comment-17378813
]
Matt Sicker edited comment on MCOMPILER-461 at 7/11/21, 11:42 PM:
--
In my scenario, I added a second annotation processor, and based on some
inexplicable changes (absolutely nothing in the diff hints at anything useful),
I'm getting the old compiler error you discovered here despite all the maven
compiler configurations present in master right now. See attached [^wtf] where
seemingly innocuous changes are causing a completely unrelated and entirely
untouched file to cause the given compile error. Modifying the Activator class
to stop referencing the generated class still causes the log4j-core module to
fail with a fairly useless stacktrace:
{noformat}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile)
on project log4j-core: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:78)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:567)
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.compiler.CompilationFailureException:
Compilation failure
at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
(AbstractCompilerMojo.java:1224)
at org.apache.maven.plugin.compiler.CompilerMojo.execute
(CompilerMojo.java:187)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:78)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:567)
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)
{noformat}
was (Author:
[jira] [Commented] (MCOMPILER-461) Compile fails when class references a class generated by an annotation processor and module-info.java is present
[
https://issues.apache.org/jira/browse/MCOMPILER-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378813#comment-17378813
]
Matt Sicker commented on MCOMPILER-461:
---
In my scenario, I added a second annotation processor, and based on some
inexplicable changes (absolutely nothing in the diff hints at anything useful),
I'm getting the old compiler error you discovered here despite all the maven
compiler configurations present in master right now. See attached [^wtf] where
seemingly innocuous changes are causing a completely unrelated and entirely
untouched file to cause the given compile error. Modifying the Activator class
to stop referencing the generated class still causes the log4j-core module to
fail with a fairly useless stacktrace:
{{org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
(default-compile) on project log4j-core: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:78)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:567)
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.compiler.CompilationFailureException:
Compilation failure
at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
(AbstractCompilerMojo.java:1224)
at org.apache.maven.plugin.compiler.CompilerMojo.execute
(CompilerMojo.java:187)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:78)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:567)
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)}}
> Compile fails when class references a class generated by an annotation
> processor
[jira] [Updated] (MCOMPILER-461) Compile fails when class references a class generated by an annotation processor and module-info.java is present
[ https://issues.apache.org/jira/browse/MCOMPILER-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated MCOMPILER-461: -- Attachment: wtf > Compile fails when class references a class generated by an annotation > processor and module-info.java is present > > > Key: MCOMPILER-461 > URL: https://issues.apache.org/jira/browse/MCOMPILER-461 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.1 > Environment: MacOS 10.15.7. > Maven home: /opt/maven/maven > Java version: 11.0.10, vendor: Amazon.com Inc., runtime: > /Library/Java/JavaVirtualMachines/amazon-corretto-11.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac" >Reporter: Ralph Goers >Priority: Major > Attachments: mvn.txt, wtf > > > While trying to convert Log4j-core to a JPMS module I have run into an issue > where I have a class that references a class that is generated by Log4j's > annotation processor and that class gets an error saying the referenced class > cannot be found. However, after the compile fails I can see that the file was > generated. > To reproduce: > git clone [https://github.com/apache/logging-log4j2.git > ]cd logging-log4j2 > git checkout module-compile-fails > mvn clean install > The compile will fail in log4j-core. Some appear to be errors in javac for > which I have opened an issue with openjdk. But if I do "mvn -X clean install" > and copy the compile command line and prepend it with javac when it runs I no > longer see > [ERROR] > /Users/rgoers/projects/apache/logging/log4j/logging-log4j2/log4j-core/src/main/java/org/apache/logging/log4j/core/osgi/Activator.java:[29,44] > error: cannot find symbol symbol: class Log4jPlugins location: package > org.apache.logging.log4j.core.plugins > which indicates that Maven is somehow causing that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MCOMPILER-461) Compile fails when class references a class generated by an annotation processor and module-info.java is present
[ https://issues.apache.org/jira/browse/MCOMPILER-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378812#comment-17378812 ] Matt Sicker commented on MCOMPILER-461: --- These error messages don't even help explain what failed, where, why, or really any reason why it failed besides telling me to go fuck myself. What is up with this issue? > Compile fails when class references a class generated by an annotation > processor and module-info.java is present > > > Key: MCOMPILER-461 > URL: https://issues.apache.org/jira/browse/MCOMPILER-461 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.1 > Environment: MacOS 10.15.7. > Maven home: /opt/maven/maven > Java version: 11.0.10, vendor: Amazon.com Inc., runtime: > /Library/Java/JavaVirtualMachines/amazon-corretto-11.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac" >Reporter: Ralph Goers >Priority: Major > Attachments: mvn.txt > > > While trying to convert Log4j-core to a JPMS module I have run into an issue > where I have a class that references a class that is generated by Log4j's > annotation processor and that class gets an error saying the referenced class > cannot be found. However, after the compile fails I can see that the file was > generated. > To reproduce: > git clone [https://github.com/apache/logging-log4j2.git > ]cd logging-log4j2 > git checkout module-compile-fails > mvn clean install > The compile will fail in log4j-core. Some appear to be errors in javac for > which I have opened an issue with openjdk. But if I do "mvn -X clean install" > and copy the compile command line and prepend it with javac when it runs I no > longer see > [ERROR] > /Users/rgoers/projects/apache/logging/log4j/logging-log4j2/log4j-core/src/main/java/org/apache/logging/log4j/core/osgi/Activator.java:[29,44] > error: cannot find symbol symbol: class Log4jPlugins location: package > org.apache.logging.log4j.core.plugins > which indicates that Maven is somehow causing that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MENFORCER-387) Require Java 8
[ https://issues.apache.org/jira/browse/MENFORCER-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378788#comment-17378788 ] Hudson commented on MENFORCER-387: -- Build failed in Jenkins: Maven » Maven TLP » maven-enforcer » master #65 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/65/ > Require Java 8 > -- > > Key: MENFORCER-387 > URL: https://issues.apache.org/jira/browse/MENFORCER-387 > Project: Maven Enforcer Plugin > Issue Type: Task >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 3.0.0 > > > Maven Dependency Tree 3.1.0 requires Java 8, so a good reason to increase > this requirement for the plugin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-265) re-enable reproducible builds for ASF parent POM source-release.zip
[ https://issues.apache.org/jira/browse/MPOM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378787#comment-17378787 ] Benjamin Marwell commented on MPOM-265: --- Hervé, Is this a good idea for a parent pom? Wouldn't all Apache projects not setting/overriding this property be having a problem? It is probably a similar question to what we had a month ago with the spring boot pom. The license from the parent pom is being inherited… > re-enable reproducible builds for ASF parent POM source-release.zip > --- > > Key: MPOM-265 > URL: https://issues.apache.org/jira/browse/MPOM-265 > Project: Maven POMs > Issue Type: Bug > Components: asf >Affects Versions: ASF-24 >Reporter: Herve Boutemy >Priority: Major > Fix For: ASF-25 > > > project.build.outputTimestamp property was removed in MPOM-255 > need to add it back for ASF parent POM source-release zip file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MENFORCER-387) Require Java 8
[ https://issues.apache.org/jira/browse/MENFORCER-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-387. Resolution: Fixed Fixed in [fbc505a3df144464d9210839409e856af27fcb50|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=fbc505a3df144464d9210839409e856af27fcb50] > Require Java 8 > -- > > Key: MENFORCER-387 > URL: https://issues.apache.org/jira/browse/MENFORCER-387 > Project: Maven Enforcer Plugin > Issue Type: Task >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 3.0.0 > > > Maven Dependency Tree 3.1.0 requires Java 8, so a good reason to increase > this requirement for the plugin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378783#comment-17378783
]
Hudson commented on MNG-7115:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6727 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6727/12/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378784#comment-17378784
]
Hudson commented on MNG-7056:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6727 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6727/12/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378781#comment-17378781
]
Hudson commented on MNG-7115:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6829 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6829/26/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378780#comment-17378780
]
Hudson commented on MNG-7056:
-
Build failed in Jenkins: Maven » Maven TLP » maven » mng-5668-poc #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/mng-5668-poc/26/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378782#comment-17378782
]
Hudson commented on MNG-7056:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6829 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6829/26/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378775#comment-17378775
]
Hudson commented on MNG-7115:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-5567 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5567/26/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378779#comment-17378779
]
Hudson commented on MNG-7115:
-
Build failed in Jenkins: Maven » Maven TLP » maven » mng-5668-poc #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/mng-5668-poc/26/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378778#comment-17378778
]
Hudson commented on MNG-7056:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-4645 #17
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645/17/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378776#comment-17378776
]
Hudson commented on MNG-7115:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-4645 #17
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645/17/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378777#comment-17378777
]
Hudson commented on MNG-7056:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-5567 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-5567/26/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378772#comment-17378772
]
Hudson commented on MNG-7115:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MRESOLVER-94 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MRESOLVER-94/26/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378773#comment-17378773
]
Hudson commented on MNG-7056:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MRESOLVER-94 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MRESOLVER-94/26/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378769#comment-17378769
]
Hudson commented on MNG-7115:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6889 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6889/26/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378770#comment-17378770
]
Hudson commented on MNG-7056:
-
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-6889 #26
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6889/26/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378766#comment-17378766
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
MNG-7173-resolver-guice-module #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7173-resolver-guice-module/3/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378764#comment-17378764
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MODELTESTS_IMPROVEMENT
#27
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MODELTESTS_IMPROVEMENT/27/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378765#comment-17378765
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven »
MNG-7173-resolver-guice-module #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7173-resolver-guice-module/3/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378763#comment-17378763
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MODELTESTS_IMPROVEMENT
#27
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MODELTESTS_IMPROVEMENT/27/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378762#comment-17378762
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645+MNG-6772 #13
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645+MNG-6772/13/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378761#comment-17378761
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-4645+MNG-6772 #13
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-4645+MNG-6772/13/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378759#comment-17378759
]
Hudson commented on MNG-7056:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7177 #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7177/3/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-6071) GetResource ('/) returns 'null' if build is started with -f
[
https://issues.apache.org/jira/browse/MNG-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378757#comment-17378757
]
Hudson commented on MNG-6071:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7177 #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7177/3/
> GetResource ('/) returns 'null' if build is started with -f
> ---
>
> Key: MNG-6071
> URL: https://issues.apache.org/jira/browse/MNG-6071
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.1, 3.3.1, 3.3.9
> Environment: Windows 10 x64
> Tested in cmd.exe, git bash.
>Reporter: Alexander Bender
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.8.2, 4.0.0, 4.0.0-alpha-1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I set up a very simple test maven project with only a dependency to testNG.
> {code}
> public class TestTest {
> @Test
> public void test() {
> System.out.println(getClass().getResource("/"));
> {code}
> Depending on how I build this, the call either returns null or the expected
> directory. How is that?
> {code}
> // Prints: file:/C:/workspace/test/testproject/target/test-classes/
> mvn clean test -Dtest=TestTest -f pom.xml
> // Prints: file:/C:/workspace/test/testproject/target/test-classes/
> mvn clean test -Dtest=TestTest -f testproject/pom.xml
> // Prints: null
> mvn clean test -Dtest=TestTest -f ./pom.xml
> // Prints: null
> mvn clean test -Dtest=TestTest -f ./testproject/pom.xml
> {code}
> Note that the second call includes "./" after -f.
> I actually want to find out the /target folder regardless of scenario (testNG
> in IntelliJ, Maven, Jenkins Buid, ...). So far, this way has proven the most
> reliable.
> {code}
> System.out.println(getClass().getResource("./"));
> {code}
> This seems to reliably point to
> file:/C:/workspace/test/testproject/target/test-classes/com/testproject/test.
> Would this be safer to use?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-5868) Adding serval times the same artifact via MavenProjectHelper (attachArtifact) keep adding to the List duplicate artifacts
[
https://issues.apache.org/jira/browse/MNG-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378756#comment-17378756
]
Hudson commented on MNG-5868:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7177 #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7177/3/
> Adding serval times the same artifact via MavenProjectHelper (attachArtifact)
> keep adding to the List duplicate artifacts
> -
>
> Key: MNG-5868
> URL: https://issues.apache.org/jira/browse/MNG-5868
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.2.3
>Reporter: Karl Heinz Marbaise
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.8.2, 4.0.0, 4.0.0-alpha-1
>
>
> During the check of an issue MSHADE-195 i stumbled over several things...
> If you take a look here and the log output excerpt:
> {noformat}
> INFO] Minimized 2341 -> 1293
> [INFO] Minimized 3282 -> 2234
> [INFO] Replacing original artifact with shaded artifact.
> [INFO] Replacing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT.jar
> with
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-shaded.jar
> [INFO] Replacing original source artifact with shaded source artifact.
> [INFO] Replacing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-sources.jar
> with
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-shaded-sources.jar
> [INFO] Dependency-reduced POM written at:
> /Users/kama/ws-git/apache/mshade/mshade-195/dependency-reduced-pom.xml
> [INFO]
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> MSHADE-195-example ---
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT.jar
> to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT.jar
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/dependency-reduced-pom.xml to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT.pom
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-sources.jar
> to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT-sources.jar
> [INFO] Installing
> /Users/kama/ws-git/apache/mshade/mshade-195/target/MSHADE-195-example-1-SNAPSHOT-sources.jar
> to
> /Users/kama/.m2/repository/com/example/MSHADE-195-example/1-SNAPSHOT/MSHADE-195-example-1-SNAPSHOT-sources.jar
> [INFO]
> {noformat}
> Install plugin tries to install two identical artifacts which will work for
> maven-install-plugin but would fail a deploy to repository manager (for
> releases) etc.
> So after diving into the problem i found the following code in maven-core
> (MavenProject.java):
> {code:java}
> /**
> * Add or replace an artifact. This method is now deprecated. Use the
> @{MavenProjectHelper} to attach artifacts to a
> * project. In spite of the 'throws' declaration on this API, this method
> has never thrown an exception since Maven
> * 3.0.x. Historically, it logged and ignored a second addition of the
> same g/a/v/c/t. Now it replaces the file for
> * the artifact, so that plugins (e.g. shade) can change the pathname of
> the file for a particular set of
> * coordinates.
> *
> * @param artifact the artifact to add or replace.
> * @throws DuplicateArtifactAttachmentException
> */
> public void addAttachedArtifact( Artifact artifact )
> throws DuplicateArtifactAttachmentException
> {
> getAttachedArtifacts().add( artifact );
> }
> public List getAttachedArtifacts()
> {
> if ( attachedArtifacts == null )
> {
> attachedArtifacts = new ArrayList<>();
> }
> return attachedArtifacts;
> }
> {code}
> So taking a look into MavenProjectHelper.java and the implementation
> (DefaultMavenProjectHelper.java).
> {code:java}
> /**
> * Add an attached artifact or replace the file for an existing artifact.
> *
> * @see
> MavenProject#addAttachedArtifact(org.apache.maven.artifact.Artifact)
> * @param project project reference.
> * @param artifact artifact to add or replace.
> */
> public void attachArtifact( MavenProject project, Artifact artifact )
> {
> project.addAttachedArtifact( artifact );
> }
> {code}
> which means that there is not check if an artifacts is already attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378758#comment-17378758
]
Hudson commented on MNG-7115:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7177 #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7177/3/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MRESOLVER-189) Using semaphore-redisson followed by rwlock-redisson on many parallel build of the same project triggers redisson error
[
https://issues.apache.org/jira/browse/MRESOLVER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378754#comment-17378754
]
Michael Osipov commented on MRESOLVER-189:
--
Please run the rwlock at least 50 times. Maybe the error will surface here too.
Will review your logs.
> Using semaphore-redisson followed by rwlock-redisson on many parallel build
> of the same project triggers redisson error
> ---
>
> Key: MRESOLVER-189
> URL: https://issues.apache.org/jira/browse/MRESOLVER-189
> Project: Maven Resolver
> Issue Type: Bug
>Reporter: Jacques-Etienne Beaudet
>Assignee: Michael Osipov
>Priority: Major
> Attachments: create_lock_events.sql, etl.sql, schema.sql
>
>
> While testing performance for in
> [https://github.com/apache/maven-resolver/pull/68|https://github.com/apache/maven-resolver/pull/68,]
> , I ran into an error using rwlock-redisson. Here are the steps to reproduce
> (hopefully it's easily reproducible on your end) and the logs of the run
> (trace enabled on org.eclipse.aether) at the end :
> * `redis-cli flushall` to get a clean slate
> * Clone a repository with a fair size
> * Make 4 copy of this repository (I ran my test with 4 copies, but 2 might
> be enough?)
> * `mvn clean` on all repositories
> * run a parallel build with semaphore-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=semaphore-redisson`) on all repositories
> * `mvn clean` all repositories
> * run a parallel build with rwlock-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=rwlock-redisson`) on all repositories
> By doing this, I ran into this and the only way out was running a `redis-cli
> flushall`.
>
> The way I ran my parallel build was really dumb and simple, something like
> that :
>
> {code:java}
> cd repo1 ; mvn clean > /tmp/log1 2>&1 & cd ../repo2 ; mvn clean > /tmp/log2
> 2>&1 & cd ../repo3 ; mvn clean > /tmp/log3 2>&1 & cd ../repo4 ; mvn clean >
> /tmp/log4 2>&1 & cd .. ;
> {code}
>
>
> Let me know if you can't reproduce, I might be able to provide you with
> traces logs of the semaphore build as well.
> {code:java}
> [INFO] Redisson 3.15.6
> [INFO] 1 connections initialized for localhost/127.0.0.1:6379
> [INFO] 24 connections initialized for localhost/127.0.0.1:6379
> [TRACE] Created Redisson client with id '42934566-3759-4f73-9fbc-a2d0a8368e1f'
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> /root/.m2/repository
> [INFO] Scanning for projects...
> [TRACE] Need 1 write lock(s) for
> [artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0]
> [TRACE] Acquiring write lock for
> 'artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0'
> [ERROR] Internal error: org.redisson.client.RedisException: ERR Error running
> script (call to f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1:
> WRONGTYPE Operation against a key holding the wrong kind of value. channel:
> [id: 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command:
> (EVAL), params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode
> == false) then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> org.redisson.client.RedisException: ERR Error running script (call to
> f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1: WRONGTYPE
> Operation against a key holding the wrong kind of value. channel: [id:
> 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command: (EVAL),
> params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode == false)
> then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write]
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at
[jira] [Closed] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository
[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHADE-395. - Resolution: Not A Problem > 3.3.0-SNAPSHOT not available in repository > -- > > Key: MSHADE-395 > URL: https://issues.apache.org/jira/browse/MSHADE-395 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Gabriel Wolf >Priority: Major > Labels: 16, 3.3.0, java, snapshot > Attachments: image-2021-07-11-18-58-13-943.png > > > Hey, i am one of the developers from BetonQuest > [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin. > Not we want/need to update to java 16. > First i had the following issue: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project > betonquest: Error creating shaded jar: Unsupported class file major version > 60 -> [Help 1] > After a small research i found the following: > [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/] > So it seems that 3.3.0-SNAPSHOT > ([https://repository.apache.org/content/repositories/snapshots/]) solved my > problem, but i run into the same problem, that the snapshot can not be > downloaded. > As a workaround, i tried to run mvn install by my own, and everything works > as wanted. > But this is not working on my buildserver (github actions). > Is the artifact broken in the repository or is there something else wrong? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378753#comment-17378753
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7166 #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7166/3/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378752#comment-17378752
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7166 #3
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7166/3/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378750#comment-17378750
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7032_versioncolours
#16
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7032_versioncolours/16/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378751#comment-17378751
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7032_versioncolours
#16
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7032_versioncolours/16/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378748#comment-17378748
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7063 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7063/11/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378747#comment-17378747
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7063 #11
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7063/11/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MRESOLVER-189) Using semaphore-redisson followed by rwlock-redisson on many parallel build of the same project triggers redisson error
[
https://issues.apache.org/jira/browse/MRESOLVER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378746#comment-17378746
]
Jacques-Etienne Beaudet commented on MRESOLVER-189:
---
Logs sent via email. Once again, it's only reproducible with the semaphore so
I've only included that this time.
> Using semaphore-redisson followed by rwlock-redisson on many parallel build
> of the same project triggers redisson error
> ---
>
> Key: MRESOLVER-189
> URL: https://issues.apache.org/jira/browse/MRESOLVER-189
> Project: Maven Resolver
> Issue Type: Bug
>Reporter: Jacques-Etienne Beaudet
>Assignee: Michael Osipov
>Priority: Major
> Attachments: create_lock_events.sql, etl.sql, schema.sql
>
>
> While testing performance for in
> [https://github.com/apache/maven-resolver/pull/68|https://github.com/apache/maven-resolver/pull/68,]
> , I ran into an error using rwlock-redisson. Here are the steps to reproduce
> (hopefully it's easily reproducible on your end) and the logs of the run
> (trace enabled on org.eclipse.aether) at the end :
> * `redis-cli flushall` to get a clean slate
> * Clone a repository with a fair size
> * Make 4 copy of this repository (I ran my test with 4 copies, but 2 might
> be enough?)
> * `mvn clean` on all repositories
> * run a parallel build with semaphore-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=semaphore-redisson`) on all repositories
> * `mvn clean` all repositories
> * run a parallel build with rwlock-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=rwlock-redisson`) on all repositories
> By doing this, I ran into this and the only way out was running a `redis-cli
> flushall`.
>
> The way I ran my parallel build was really dumb and simple, something like
> that :
>
> {code:java}
> cd repo1 ; mvn clean > /tmp/log1 2>&1 & cd ../repo2 ; mvn clean > /tmp/log2
> 2>&1 & cd ../repo3 ; mvn clean > /tmp/log3 2>&1 & cd ../repo4 ; mvn clean >
> /tmp/log4 2>&1 & cd .. ;
> {code}
>
>
> Let me know if you can't reproduce, I might be able to provide you with
> traces logs of the semaphore build as well.
> {code:java}
> [INFO] Redisson 3.15.6
> [INFO] 1 connections initialized for localhost/127.0.0.1:6379
> [INFO] 24 connections initialized for localhost/127.0.0.1:6379
> [TRACE] Created Redisson client with id '42934566-3759-4f73-9fbc-a2d0a8368e1f'
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> /root/.m2/repository
> [INFO] Scanning for projects...
> [TRACE] Need 1 write lock(s) for
> [artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0]
> [TRACE] Acquiring write lock for
> 'artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0'
> [ERROR] Internal error: org.redisson.client.RedisException: ERR Error running
> script (call to f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1:
> WRONGTYPE Operation against a key holding the wrong kind of value. channel:
> [id: 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command:
> (EVAL), params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode
> == false) then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> org.redisson.client.RedisException: ERR Error running script (call to
> f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1: WRONGTYPE
> Operation against a key holding the wrong kind of value. channel: [id:
> 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command: (EVAL),
> params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode == false)
> then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write]
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378738#comment-17378738
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6471 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6471/12/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378739#comment-17378739
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6471 #12
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6471/12/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378737#comment-17378737
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7122 #9
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7122/9/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378736#comment-17378736
]
Hudson commented on MNG-7115:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-7122 #9
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7122/9/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MENFORCER-387) Require Java 8
Robert Scholte created MENFORCER-387: Summary: Require Java 8 Key: MENFORCER-387 URL: https://issues.apache.org/jira/browse/MENFORCER-387 Project: Maven Enforcer Plugin Issue Type: Task Reporter: Robert Scholte Assignee: Robert Scholte Fix For: 3.0.0 Maven Dependency Tree 3.1.0 requires Java 8, so a good reason to increase this requirement for the plugin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository
[
https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378735#comment-17378735
]
Gabriel Wolf commented on MSHADE-395:
-
Ok, turns out that it was my error. What I did was setting up the plugin
repository as follows:
{code:xml}
maven-apache-snapshot-repo
https://repository.apache.org/content/repositories/snapshots/
{code}
while it should've been
{code:xml}
apache-snapshot-repo
https://repository.apache.org/content/repositories/snapshots/
{code}
Thus you can close this issue.
> 3.3.0-SNAPSHOT not available in repository
> --
>
> Key: MSHADE-395
> URL: https://issues.apache.org/jira/browse/MSHADE-395
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gabriel Wolf
>Priority: Major
> Labels: 16, 3.3.0, java, snapshot
> Attachments: image-2021-07-11-18-58-13-943.png
>
>
> Hey, i am one of the developers from BetonQuest
> [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
> Not we want/need to update to java 16.
> First i had the following issue:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project
> betonquest: Error creating shaded jar: Unsupported class file major version
> 60 -> [Help 1]
> After a small research i found the following:
> [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]
> So it seems that 3.3.0-SNAPSHOT
> ([https://repository.apache.org/content/repositories/snapshots/]) solved my
> problem, but i run into the same problem, that the snapshot can not be
> downloaded.
> As a workaround, i tried to run mvn install by my own, and everything works
> as wanted.
> But this is not working on my buildserver (github actions).
> Is the artifact broken in the repository or is there something else wrong?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7115) MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
[
https://issues.apache.org/jira/browse/MNG-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378732#comment-17378732
]
Hudson commented on MNG-7115:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » ver #7
See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/ver/7/
> MavenITmng5771CoreExtensionsTest fails on maven-3.8.x branch
>
>
> Key: MNG-7115
> URL: https://issues.apache.org/jira/browse/MNG-7115
> Project: Maven
> Issue Type: Bug
> Components: core, Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The IT fails reliably because of:
> {noformat}
> [INFO] --- maven-it-plugin-core-extensions-client:0.1:validate-component
> (validate-extensions) @ test ---
> [DEBUG]
> org.apache.maven.its.it-core-extensions:maven-it-plugin-core-extensions-client:jar:0.1
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> [INFO] Downloading from repoman:
> http://localhost:11669/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> 75193 [qtp1198759714-300] WARN org.eclipse.jetty.server.HttpChannel -
> /org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> java.io.FileNotFoundException:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-5771-core-extensions/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at
> org.apache.maven.it.HttpServer$HttpServerBuilder$2.stream(HttpServer.java:174)
> at
> org.apache.maven.it.HttpServer$StreamSourceHandler.handle(HttpServer.java:210)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:529)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:445)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:267)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.029 s
> [INFO] Finished at: 2021-03-14T14:04:20+01:00
> [INFO]
>
> {noformat}
> The reason is that Maven Core constantly adds Plexus Utils 1.1 dynamically to
> the extension classpath. This annoyance has been fixed for Maven 4 in:
> {noformat}
> commit c61e63032f71c32c4060c8a94ce792bf47824e3c (slawekjaranowski/master)
> Author: Sylwester Lachiewicz
> Date: 2020-07-24T01:59:50+02:00
> [MNG-6965] Extensions suddenly have
> org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
> This closes #367
> {noformat}
> I don't know what the best solution would be here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378733#comment-17378733
]
Hudson commented on MNG-7056:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » ver #7
See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/ver/7/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
> ./core-it-suite/src/test/resources/mng-4148/remote-repository/org/apache/maven/its/mng4148/module/1.0.0/module-1.0.0.pom
>
[jira] [Commented] (MNG-7056) Replace tabs in IT files
[
https://issues.apache.org/jira/browse/MNG-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378731#comment-17378731
]
Hudson commented on MNG-7056:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #43
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/43/
> Replace tabs in IT files
>
>
> Key: MNG-7056
> URL: https://issues.apache.org/jira/browse/MNG-7056
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> These files:
> {noformat}
> $ grep -rl '^I' . | sort -u | grep -v -e '.jar$' -e Makefile -e '.war$'
> ./core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3642DynamicResourcesTest.java
> ./core-it-suite/src/test/resources/bootstrap/group-11/pom.xml
> ./core-it-suite/src/test/resources/bootstrap/group-12/pom.xml
> ./core-it-suite/src/test/resources/it0038/pom.xml
> ./core-it-suite/src/test/resources/mng-0612/project/pom.xml
> ./core-it-suite/src/test/resources/mng-0773/settings.xml
> ./core-it-suite/src/test/resources/mng-2196/pom.xml
> ./core-it-suite/src/test/resources/mng-2289/issue/src/main/java/mng/Issue2289.java
> ./core-it-suite/src/test/resources/mng-2305/keystore
> ./core-it-suite/src/test/resources/mng-2771/project/pom.xml
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/its/mng2926/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/apache/maven/plugins/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-2926/repo/org/codehaus/mojo/mng-2926/0.1/mng-2926-0.1.pom
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/App.java
> ./core-it-suite/src/test/resources/mng-3203/src/main/java/org/apache/maven/it/mng3203/Diamond.java
> ./core-it-suite/src/test/resources/mng-3259/module1/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module1/src/main/java/mng/XStreamTestCase.java
> ./core-it-suite/src/test/resources/mng-3259/module2/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module2/src/main/java/mng/Module2.java
> ./core-it-suite/src/test/resources/mng-3259/module3/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module3/src/main/java/mng/Module3.java
> ./core-it-suite/src/test/resources/mng-3259/module3/src/test/java/mng/Module3TestUtil.java
> ./core-it-suite/src/test/resources/mng-3259/module4/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4.java
> ./core-it-suite/src/test/resources/mng-3259/module4/src/main/java/mng/Module4Bean.java
> ./core-it-suite/src/test/resources/mng-3259/module5/pom.xml
> ./core-it-suite/src/test/resources/mng-3259/module5/src/main/java/mng/Module5.java
> ./core-it-suite/src/test/resources/mng-3259/module5/src/test/java/mng/Module5Test.java
> ./core-it-suite/src/test/resources/mng-3259/parent/pom.xml
> ./core-it-suite/src/test/resources/mng-3372/dependency-tree/pom.xml
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.1/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/main/java/org/apache/maven/its/mng3506/App.java
> ./core-it-suite/src/test/resources/mng-3506/mng-3506.2/src/test/java/org/apache/maven/its/mng3506/AppTest.java
> ./core-it-suite/src/test/resources/mng-3652/test-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3684/maven-mng3684-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/maven-mng3693-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3693/projects/app/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3694/maven-mng3694-plugin/src/main/java/plugin/MyMojo.java
> ./core-it-suite/src/test/resources/mng-3703/maven-mng3703-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3704/maven-mng3704-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/original-model/plugins/maven-mng3710-originalModel-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3710/pom-inheritance/projects/middle/pom.xml
> ./core-it-suite/src/test/resources/mng-3716/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/maven-mng3723-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3723/projects/pom.xml
> ./core-it-suite/src/test/resources/mng-3724/maven-mng3724-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/maven-mng3743-report-plugin/pom.xml
> ./core-it-suite/src/test/resources/mng-3743/plugins/pom.xml
> ./core-it-suite/src/test/resources/mng-3814/plugin-a/pom.xml
>
[jira] [Commented] (MNG-7184) document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable
[ https://issues.apache.org/jira/browse/MNG-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378730#comment-17378730 ] Hudson commented on MNG-7184: - Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #43 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/43/ > document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment > variable > -- > > Key: MNG-7184 > URL: https://issues.apache.org/jira/browse/MNG-7184 > Project: Maven > Issue Type: Task > Components: Command Line >Affects Versions: 2.0-alpha-1, 2.0, 3.0-alpha-1, 3.8.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.2, 4.0.0-alpha-1 > > > these scripts are called by mvn since Maven 1, even if this was never really > documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[
https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378726#comment-17378726
]
Konrad Windszus commented on MPOM-255:
--
bq. this commit breaks ASF parent POM reproducible build
Right, but to be honest reproducible builds for pom only projects don't seem to
be that reasonable. It would be easy to fix though if you really think that pom
only releases should be reproducible as well (by adding the property in a
profile only active when building asf parent)
bq. just to force parent POM users to make effort to have nicer config by also
defining a property value
This is not that easy to achieve as the rule {{requireProperty}} does not
distinguish between inherited and local properties and also
{{requirePropertyDiverges}}
(https://www.mojohaus.org/extra-enforcer-rules/requirePropertyDiverges.html)
does not seem to be a fit for this use case
> Enforce local property "project.build.outputTimestamp" for reproducible builds
> --
>
> Key: MPOM-255
> URL: https://issues.apache.org/jira/browse/MPOM-255
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-23
>Reporter: Konrad Windszus
>Assignee: Michael Osipov
>Priority: Major
> Fix For: ASF-24
>
>
> In case the release's root pom.xml doesn't overwrite
> "project.build.outputTimestamp" it takes the value from
> [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.]
> Instead of the fallback an enforcer rule should be added to require a
> property "project.build.outputTimestamp" to be set in the right format for
> reproducible builds to work
> ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build])
> for every pom.xml locally.
> Only that way the timestamps are automatically adjusted with each release
> (https://issues.apache.org/jira/browse/MRELEASE-1029)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7184) document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable
[ https://issues.apache.org/jira/browse/MNG-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378724#comment-17378724 ] Hudson commented on MNG-7184: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #183 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/183/ > document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment > variable > -- > > Key: MNG-7184 > URL: https://issues.apache.org/jira/browse/MNG-7184 > Project: Maven > Issue Type: Task > Components: Command Line >Affects Versions: 2.0-alpha-1, 2.0, 3.0-alpha-1, 3.8.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.2, 4.0.0-alpha-1 > > > these scripts are called by mvn since Maven 1, even if this was never really > documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNG-7184) document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable
[ https://issues.apache.org/jira/browse/MNG-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-7184. -- Resolution: Fixed done in https://github.com/apache/maven/commit/1052ec5d871963cd662e7b6a4608cab30a63d79e for Maven 4 done in https://github.com/apache/maven/commit/0635e92665cbd247a4144c328321b0e9f058398e for Maven 3.8.x > document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment > variable > -- > > Key: MNG-7184 > URL: https://issues.apache.org/jira/browse/MNG-7184 > Project: Maven > Issue Type: Task > Components: Command Line >Affects Versions: 2.0-alpha-1, 2.0, 3.0-alpha-1, 3.8.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.2, 4.0.0-alpha-1 > > > these scripts are called by mvn since Maven 1, even if this was never really > documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNG-7184) document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable
[ https://issues.apache.org/jira/browse/MNG-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7184: --- Affects Version/s: 2.0 > document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment > variable > -- > > Key: MNG-7184 > URL: https://issues.apache.org/jira/browse/MNG-7184 > Project: Maven > Issue Type: Task > Components: Command Line >Affects Versions: 2.0, 3.0-alpha-1, 3.8.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.2, 4.0.0-alpha-1 > > > these scripts are called by mvn since Maven 1, even if this was never really > documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNG-7184) document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable
[ https://issues.apache.org/jira/browse/MNG-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7184: --- Affects Version/s: 2.0-alpha-1 > document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment > variable > -- > > Key: MNG-7184 > URL: https://issues.apache.org/jira/browse/MNG-7184 > Project: Maven > Issue Type: Task > Components: Command Line >Affects Versions: 2.0-alpha-1, 2.0, 3.0-alpha-1, 3.8.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.2, 4.0.0-alpha-1 > > > these scripts are called by mvn since Maven 1, even if this was never really > documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNG-7184) document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable
[ https://issues.apache.org/jira/browse/MNG-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7184: --- Affects Version/s: 3.0-alpha-1 > document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment > variable > -- > > Key: MNG-7184 > URL: https://issues.apache.org/jira/browse/MNG-7184 > Project: Maven > Issue Type: Task > Components: Command Line >Affects Versions: 3.0-alpha-1, 3.8.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.2, 4.0.0-alpha-1 > > > these scripts are called by mvn since Maven 1, even if this was never really > documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository
[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonas updated MSHADE-395: - Attachment: (was: image-2021-07-11-18-58-08-935.png) > 3.3.0-SNAPSHOT not available in repository > -- > > Key: MSHADE-395 > URL: https://issues.apache.org/jira/browse/MSHADE-395 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Gabriel Wolf >Priority: Major > Labels: 16, 3.3.0, java, snapshot > Attachments: image-2021-07-11-18-58-13-943.png > > > Hey, i am one of the developers from BetonQuest > [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin. > Not we want/need to update to java 16. > First i had the following issue: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project > betonquest: Error creating shaded jar: Unsupported class file major version > 60 -> [Help 1] > After a small research i found the following: > [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/] > So it seems that 3.3.0-SNAPSHOT > ([https://repository.apache.org/content/repositories/snapshots/]) solved my > problem, but i run into the same problem, that the snapshot can not be > downloaded. > As a workaround, i tried to run mvn install by my own, and everything works > as wanted. > But this is not working on my buildserver (github actions). > Is the artifact broken in the repository or is there something else wrong? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNG-7184) document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable
[ https://issues.apache.org/jira/browse/MNG-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7184: --- Summary: document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable (was: document .mavenrc/maven_pre.bat|cmd) > document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment > variable > -- > > Key: MNG-7184 > URL: https://issues.apache.org/jira/browse/MNG-7184 > Project: Maven > Issue Type: Task > Components: Command Line >Affects Versions: 3.8.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.8.2, 4.0.0-alpha-1 > > > these scripts are called by mvn since Maven 1, even if this was never really > documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNG-7184) document .mavenrc/maven_pre.bat|cmd
Herve Boutemy created MNG-7184: -- Summary: document .mavenrc/maven_pre.bat|cmd Key: MNG-7184 URL: https://issues.apache.org/jira/browse/MNG-7184 Project: Maven Issue Type: Task Components: Command Line Affects Versions: 3.8.1 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 3.8.2, 4.0.0-alpha-1 these scripts are called by mvn since Maven 1, even if this was never really documented... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository
[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonas updated MSHADE-395: - Attachment: image-2021-07-11-18-58-08-935.png > 3.3.0-SNAPSHOT not available in repository > -- > > Key: MSHADE-395 > URL: https://issues.apache.org/jira/browse/MSHADE-395 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Gabriel Wolf >Priority: Major > Labels: 16, 3.3.0, java, snapshot > Attachments: image-2021-07-11-18-58-08-935.png, > image-2021-07-11-18-58-13-943.png > > > Hey, i am one of the developers from BetonQuest > [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin. > Not we want/need to update to java 16. > First i had the following issue: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project > betonquest: Error creating shaded jar: Unsupported class file major version > 60 -> [Help 1] > After a small research i found the following: > [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/] > So it seems that 3.3.0-SNAPSHOT > ([https://repository.apache.org/content/repositories/snapshots/]) solved my > problem, but i run into the same problem, that the snapshot can not be > downloaded. > As a workaround, i tried to run mvn install by my own, and everything works > as wanted. > But this is not working on my buildserver (github actions). > Is the artifact broken in the repository or is there something else wrong? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository
[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378702#comment-17378702 ] Jonas commented on MSHADE-395: -- No offense, really like this project but this conversation is in my opinion just a complete meme so I could not resist. !image-2021-07-11-18-58-13-943.png! > 3.3.0-SNAPSHOT not available in repository > -- > > Key: MSHADE-395 > URL: https://issues.apache.org/jira/browse/MSHADE-395 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Gabriel Wolf >Priority: Major > Labels: 16, 3.3.0, java, snapshot > Attachments: image-2021-07-11-18-58-08-935.png, > image-2021-07-11-18-58-13-943.png > > > Hey, i am one of the developers from BetonQuest > [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin. > Not we want/need to update to java 16. > First i had the following issue: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project > betonquest: Error creating shaded jar: Unsupported class file major version > 60 -> [Help 1] > After a small research i found the following: > [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/] > So it seems that 3.3.0-SNAPSHOT > ([https://repository.apache.org/content/repositories/snapshots/]) solved my > problem, but i run into the same problem, that the snapshot can not be > downloaded. > As a workaround, i tried to run mvn install by my own, and everything works > as wanted. > But this is not working on my buildserver (github actions). > Is the artifact broken in the repository or is there something else wrong? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository
[ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonas updated MSHADE-395: - Attachment: image-2021-07-11-18-58-13-943.png > 3.3.0-SNAPSHOT not available in repository > -- > > Key: MSHADE-395 > URL: https://issues.apache.org/jira/browse/MSHADE-395 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Gabriel Wolf >Priority: Major > Labels: 16, 3.3.0, java, snapshot > Attachments: image-2021-07-11-18-58-08-935.png, > image-2021-07-11-18-58-13-943.png > > > Hey, i am one of the developers from BetonQuest > [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin. > Not we want/need to update to java 16. > First i had the following issue: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project > betonquest: Error creating shaded jar: Unsupported class file major version > 60 -> [Help 1] > After a small research i found the following: > [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/] > So it seems that 3.3.0-SNAPSHOT > ([https://repository.apache.org/content/repositories/snapshots/]) solved my > problem, but i run into the same problem, that the snapshot can not be > downloaded. > As a workaround, i tried to run mvn install by my own, and everything works > as wanted. > But this is not working on my buildserver (github actions). > Is the artifact broken in the repository or is there something else wrong? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892083#comment-16892083 ] Herve Boutemy edited comment on MNGSITE-246 at 7/11/21, 4:37 PM: - OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b when working on Maven 3.0-RC1, but from manual checks, it was already there in Maven 2.2.1 and even in 2.0-alpha-1 and Maven 1.0.2... was (Author: ascheman): OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b when working on Maven 3.0-RC1, but from manual checks, it was already there in Maven 2.2.1 and even in 2.0.10... > Documentation of mavenrc_pre / .mavenrc > --- > > Key: MNGSITE-246 > URL: https://issues.apache.org/jira/browse/MNGSITE-246 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > Labels: up-for-grabs > > The usage and the intention of mavenrc_pre and .maverc should be documented > somehow. cause at the moment it does not exist any documenation about this > (which from history research was there from Maven 1 times... ). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNGSITE-246: -- Description: The usage and the intention of mavenrc_pre and .maverc should be documented somehow. cause at the moment it does not exist any documenation about this (which from history research was there from Maven 1 times... ). (was: The usage and the intention of mavenrc_pre and .maverc should be documented somehow. cause at the moment it does not exist any documenation about this.) > Documentation of mavenrc_pre / .mavenrc > --- > > Key: MNGSITE-246 > URL: https://issues.apache.org/jira/browse/MNGSITE-246 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > Labels: up-for-grabs > > The usage and the intention of mavenrc_pre and .maverc should be documented > somehow. cause at the moment it does not exist any documenation about this > (which from history research was there from Maven 1 times... ). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892083#comment-16892083 ] Herve Boutemy edited comment on MNGSITE-246 at 7/11/21, 4:31 PM: - OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b when working on Maven 3.0-RC1, but from manual checks, it was already there in Maven 2.2.1 and even in 2.0.10... was (Author: ascheman): OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b when working on Maven 3.0-RC1, but from manual checks, it was already there in Maven 2.2.1 > Documentation of mavenrc_pre / .mavenrc > --- > > Key: MNGSITE-246 > URL: https://issues.apache.org/jira/browse/MNGSITE-246 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > Labels: up-for-grabs > > The usage and the intention of mavenrc_pre and .maverc should be documented > somehow. cause at the moment it does not exist any documenation about this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892083#comment-16892083 ] Herve Boutemy edited comment on MNGSITE-246 at 7/11/21, 4:24 PM: - OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b when working on Maven 3.0-RC1, but from manual checks, it was already there in Maven 2.2.1 was (Author: ascheman): OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b when working on Maven 3.0-RC1 > Documentation of mavenrc_pre / .mavenrc > --- > > Key: MNGSITE-246 > URL: https://issues.apache.org/jira/browse/MNGSITE-246 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > Labels: up-for-grabs > > The usage and the intention of mavenrc_pre and .maverc should be documented > somehow. cause at the moment it does not exist any documenation about this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892083#comment-16892083 ] Herve Boutemy edited comment on MNGSITE-246 at 7/11/21, 4:22 PM: - OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b when working on Maven 3.0-RC1 was (Author: ascheman): OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b > Documentation of mavenrc_pre / .mavenrc > --- > > Key: MNGSITE-246 > URL: https://issues.apache.org/jira/browse/MNGSITE-246 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > Labels: up-for-grabs > > The usage and the intention of mavenrc_pre and .maverc should be documented > somehow. cause at the moment it does not exist any documenation about this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892083#comment-16892083 ] Herve Boutemy edited comment on MNGSITE-246 at 7/11/21, 4:21 PM: - OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... = https://github.com/apache/maven/commit/3bd3bb5b79d40e52d30b6640ffd488ae9c51731b was (Author: ascheman): OK, [~michael-o], it seems to go back to changes from [~ja...@tesla.io] from 2007: [https://svn.apache.org/viewvc?view=revision=514296] ... > Documentation of mavenrc_pre / .mavenrc > --- > > Key: MNGSITE-246 > URL: https://issues.apache.org/jira/browse/MNGSITE-246 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > Labels: up-for-grabs > > The usage and the intention of mavenrc_pre and .maverc should be documented > somehow. cause at the moment it does not exist any documenation about this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378684#comment-17378684 ] Herve Boutemy edited comment on MPOM-255 at 7/11/21, 4:11 PM: -- either really have a solution that checks that local pom has a property (not an inherited value) = what I thought was coded, which was a real improvement or let as it was before: parent POM build is reproducible and every child also by default even when they did not really realize (and it just costs them that they don't realize the timestamp value: it proves nobody looks at timestamps...). sorry: I don't have any better solution than revert while we search for a real solution was (Author: hboutemy): either really have a solution that checks that local pom has a property (not an inherited value) = what I thought was coded, which was a real improvement or let as it was before: parent POM build is reproducible and every child also by default even when they did not really realize (and it just costs them that they don't realize the timestamp value: it proves nobody looks at timestamps...). sorry: I don't have any better solution that revert while we search for a real solution > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MRESOLVER-189) Using semaphore-redisson followed by rwlock-redisson on many parallel build of the same project triggers redisson error
[
https://issues.apache.org/jira/browse/MRESOLVER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MRESOLVER-189:
-
Attachment: schema.sql
etl.sql
create_lock_events.sql
> Using semaphore-redisson followed by rwlock-redisson on many parallel build
> of the same project triggers redisson error
> ---
>
> Key: MRESOLVER-189
> URL: https://issues.apache.org/jira/browse/MRESOLVER-189
> Project: Maven Resolver
> Issue Type: Bug
>Reporter: Jacques-Etienne Beaudet
>Assignee: Michael Osipov
>Priority: Major
> Attachments: create_lock_events.sql, etl.sql, schema.sql
>
>
> While testing performance for in
> [https://github.com/apache/maven-resolver/pull/68|https://github.com/apache/maven-resolver/pull/68,]
> , I ran into an error using rwlock-redisson. Here are the steps to reproduce
> (hopefully it's easily reproducible on your end) and the logs of the run
> (trace enabled on org.eclipse.aether) at the end :
> * `redis-cli flushall` to get a clean slate
> * Clone a repository with a fair size
> * Make 4 copy of this repository (I ran my test with 4 copies, but 2 might
> be enough?)
> * `mvn clean` on all repositories
> * run a parallel build with semaphore-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=semaphore-redisson`) on all repositories
> * `mvn clean` all repositories
> * run a parallel build with rwlock-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=rwlock-redisson`) on all repositories
> By doing this, I ran into this and the only way out was running a `redis-cli
> flushall`.
>
> The way I ran my parallel build was really dumb and simple, something like
> that :
>
> {code:java}
> cd repo1 ; mvn clean > /tmp/log1 2>&1 & cd ../repo2 ; mvn clean > /tmp/log2
> 2>&1 & cd ../repo3 ; mvn clean > /tmp/log3 2>&1 & cd ../repo4 ; mvn clean >
> /tmp/log4 2>&1 & cd .. ;
> {code}
>
>
> Let me know if you can't reproduce, I might be able to provide you with
> traces logs of the semaphore build as well.
> {code:java}
> [INFO] Redisson 3.15.6
> [INFO] 1 connections initialized for localhost/127.0.0.1:6379
> [INFO] 24 connections initialized for localhost/127.0.0.1:6379
> [TRACE] Created Redisson client with id '42934566-3759-4f73-9fbc-a2d0a8368e1f'
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> /root/.m2/repository
> [INFO] Scanning for projects...
> [TRACE] Need 1 write lock(s) for
> [artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0]
> [TRACE] Acquiring write lock for
> 'artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0'
> [ERROR] Internal error: org.redisson.client.RedisException: ERR Error running
> script (call to f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1:
> WRONGTYPE Operation against a key holding the wrong kind of value. channel:
> [id: 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command:
> (EVAL), params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode
> == false) then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> org.redisson.client.RedisException: ERR Error running script (call to
> f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1: WRONGTYPE
> Operation against a key holding the wrong kind of value. channel: [id:
> 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command: (EVAL),
> params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode == false)
> then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write]
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> 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
>
[jira] [Commented] (MRESOLVER-189) Using semaphore-redisson followed by rwlock-redisson on many parallel build of the same project triggers redisson error
[
https://issues.apache.org/jira/browse/MRESOLVER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378690#comment-17378690
]
Michael Osipov commented on MRESOLVER-189:
--
Went through the data and the data is partially unusable because the executor
service reuses threads and therefore the same thread appear more then once in
the log making analysis im possible. Please build Maven from branch
{{3.8.x/MNG-6471}}. I will likely backport this to 3.8.x.
Please retry with patch.
As far as I was able to analyze dumps and and logs, the hang is again in
Redisson code. You simply provide an overview over lock events:
{noformat}
for run in {1..4} ; do \
grep -e Acquiring -e Releasing -e "Failed to acquire" semaphore-$nameMapper$run
| sed -e 's# \[#;[#g' -e 's#\] #];#' | sed 's#\[TRACE\];##' > data.txt; \
cat etl.sql | sqlite3; mv data.db data$run.db; done
{noformat}
The have a look at the SQLite database in the {{lock_events}} table you'll see
when and what is happening. If you see no previous lock held (interleaving
locks) then this is a bug in Redisson.
Waiting for new data
> Using semaphore-redisson followed by rwlock-redisson on many parallel build
> of the same project triggers redisson error
> ---
>
> Key: MRESOLVER-189
> URL: https://issues.apache.org/jira/browse/MRESOLVER-189
> Project: Maven Resolver
> Issue Type: Bug
>Reporter: Jacques-Etienne Beaudet
>Assignee: Michael Osipov
>Priority: Major
>
> While testing performance for in
> [https://github.com/apache/maven-resolver/pull/68|https://github.com/apache/maven-resolver/pull/68,]
> , I ran into an error using rwlock-redisson. Here are the steps to reproduce
> (hopefully it's easily reproducible on your end) and the logs of the run
> (trace enabled on org.eclipse.aether) at the end :
> * `redis-cli flushall` to get a clean slate
> * Clone a repository with a fair size
> * Make 4 copy of this repository (I ran my test with 4 copies, but 2 might
> be enough?)
> * `mvn clean` on all repositories
> * run a parallel build with semaphore-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=semaphore-redisson`) on all repositories
> * `mvn clean` all repositories
> * run a parallel build with rwlock-redis (`mvn compile -T1C
> -Daether.syncContext.named.factory=rwlock-redisson`) on all repositories
> By doing this, I ran into this and the only way out was running a `redis-cli
> flushall`.
>
> The way I ran my parallel build was really dumb and simple, something like
> that :
>
> {code:java}
> cd repo1 ; mvn clean > /tmp/log1 2>&1 & cd ../repo2 ; mvn clean > /tmp/log2
> 2>&1 & cd ../repo3 ; mvn clean > /tmp/log3 2>&1 & cd ../repo4 ; mvn clean >
> /tmp/log4 2>&1 & cd .. ;
> {code}
>
>
> Let me know if you can't reproduce, I might be able to provide you with
> traces logs of the semaphore build as well.
> {code:java}
> [INFO] Redisson 3.15.6
> [INFO] 1 connections initialized for localhost/127.0.0.1:6379
> [INFO] 24 connections initialized for localhost/127.0.0.1:6379
> [TRACE] Created Redisson client with id '42934566-3759-4f73-9fbc-a2d0a8368e1f'
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> /root/.m2/repository
> [INFO] Scanning for projects...
> [TRACE] Need 1 write lock(s) for
> [artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0]
> [TRACE] Acquiring write lock for
> 'artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0'
> [ERROR] Internal error: org.redisson.client.RedisException: ERR Error running
> script (call to f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1:
> WRONGTYPE Operation against a key holding the wrong kind of value. channel:
> [id: 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command:
> (EVAL), params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode
> == false) then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> org.redisson.client.RedisException: ERR Error running script (call to
> f_6306ba3bf1f563b284bed52d305fce615c6664d9): @user_script:1: WRONGTYPE
> Operation against a key holding the wrong kind of value. channel: [id:
> 0x69ea1187, L:/127.0.0.1:60800 - R:localhost/127.0.0.1:6379] command: (EVAL),
> params: [local mode = redis.call('hget', KEYS[1], 'mode'); if (mode == false)
> then redis.call('hset', KEYS[1]..., 1,
> maven:resolver:artifact:com.coveo:coveo-cloud-base-service-pom:40.123.0,
> 3, 42934566-3759-4f73-9fbc-a2d0a8368e1f:1:write]
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378687#comment-17378687 ] Herve Boutemy commented on MPOM-255: notice: just be aware that this improvement will create friction for projects upgrading (I hate that reproducible builds will be seen as a friction) > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378686#comment-17378686 ] Michael Osipov commented on MPOM-255: - That's fine. > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378684#comment-17378684 ] Herve Boutemy edited comment on MPOM-255 at 7/11/21, 4:05 PM: -- either really have a solution that checks that local pom has a property (not an inherited value) = what I thought was coded, which was a real improvement or let as it was before: parent POM build is reproducible and every child also by default even when they did not really realize (and it just costs them that they don't realize the timestamp value: it proves nobody looks at timestamps...). sorry: I don't have any better solution that revert while we search for a real solution was (Author: hboutemy): either really have a solution that checks that local pom has a property (not an inherited value) = what I thought was coded, which was a real improvement or let as it was before: parent POM build is reproducible and every child also by default even when they did not really realize. sorry: I don't have any better solution that revert while we search for a real solution > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378684#comment-17378684 ] Herve Boutemy commented on MPOM-255: either really have a solution that checks that local pom has a property (not an inherited value) = what I thought was coded, which was a real improvement or let as it was before: parent POM build is reproducible and every child also by default even when they did not really realize. sorry: I don't have any better solution that revert while we search for a real solution > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378681#comment-17378681 ] Michael Osipov commented on MPOM-255: - Please feel free to provide a better solution. We'd be happy to review. > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378677#comment-17378677 ] Herve Boutemy commented on MPOM-255: I just reviewed (stupid me, I should have done before): it's not a chicken and egg problem, this issue just de-activated reproducible builds by default :( just to force parent POM users to make effort to have nicer config by also defining a property value this is not a nice way of improving the users config > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378674#comment-17378674 ] Michael Osipov commented on MPOM-255: - As far as I remember, it produced a chicked and egg problem which [~kwin] tried to solved with a profile. > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-265) re-enable reproducible builds for ASF parent POM source-release.zip
[ https://issues.apache.org/jira/browse/MPOM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-265: --- Summary: re-enable reproducible builds for ASF parent POM source-release.zip (was: re-enable reproducible builds for ASF parent POM) > re-enable reproducible builds for ASF parent POM source-release.zip > --- > > Key: MPOM-265 > URL: https://issues.apache.org/jira/browse/MPOM-265 > Project: Maven POMs > Issue Type: Bug > Components: asf >Affects Versions: ASF-24 >Reporter: Herve Boutemy >Priority: Major > Fix For: ASF-25 > > > project.build.outputTimestamp property was removed in MPOM-255 > need to add it back for ASF parent POM source-release zip file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven] MartinKanters commented on a change in pull request #486: [MNG-7182] Use a pull parser during the build/consumer transformation
MartinKanters commented on a change in pull request #486:
URL: https://github.com/apache/maven/pull/486#discussion_r667495020
##
File path:
maven-model-transform/src/main/java/org/apache/maven/model/transform/FastForwardFilter.java
##
@@ -53,75 +53,50 @@
private int domDepth = 0;
-private ContentHandler originalHandler;
-
-FastForwardFilter()
+FastForwardFilter( XmlPullParser xmlPullParser )
{
-super();
-}
-
-FastForwardFilter( AbstractSAXFilter parent )
-{
-super( parent );
+super( xmlPullParser );
}
@Override
-public void startElement( String uri, String localName, String qName,
Attributes atts )
-throws SAXException
+protected boolean accept() throws XmlPullParserException, IOException
{
-super.startElement( uri, localName, qName, atts );
-if ( domDepth > 0 )
+if ( xmlPullParser.getEventType() == START_TAG )
{
-domDepth++;
-}
-else
-{
-final String key = state.peek() + '.' + localName;
-switch ( key )
+String localName = xmlPullParser.getName();
+if ( domDepth > 0 )
{
-case "execution.configuration":
-case "plugin.configuration":
-case "plugin.goals":
-case "profile.reports":
-case "project.reports":
-case "reportSet.configuration":
-domDepth++;
-
-originalHandler = getContentHandler();
-
-ContentHandler outputContentHandler = getContentHandler();
-while ( outputContentHandler instanceof XMLFilter )
-{
-outputContentHandler = ( (XMLFilter)
outputContentHandler ).getContentHandler();
-}
-setContentHandler( outputContentHandler );
-break;
-default:
-break;
+domDepth++;
}
-state.push( localName );
-}
-}
-
-@Override
-public void endElement( String uri, String localName, String qName )
-throws SAXException
-{
-if ( domDepth > 0 )
-{
-domDepth--;
-
-if ( domDepth == 0 )
+else
{
-setContentHandler( originalHandler );
+final String key = state.peek() + '/' + localName;
+switch ( key )
+{
+case "execution/configuration":
+case "plugin/configuration":
+case "plugin/goals":
+case "profile/reports":
+case "project/reports":
+case "reportSet/configuration":
+domDepth++;
+disable();
+break;
+default:
+break;
+}
}
+state.add( localName );
}
-else
+else if ( xmlPullParser.getEventType() == END_TAG )
{
+if ( --domDepth == 0 )
Review comment:
Small one, I prefer splitting up decreasing the variable and having this
condition. It might be just me, but my brain takes a couple of extra cycles
remembering whether the return value is before or after the operation.
##
File path:
maven-model-builder/src/main/java/org/apache/maven/model/io/DefaultModelReader.java
##
@@ -137,24 +122,66 @@ private TransformerContext getTransformerContext(
Map options )
return (TransformerContext) value;
}
-private Model read( Reader reader, boolean strict, InputSource source )
+private Model read( Reader reader, Path pomFile, Map options )
throws IOException
{
try
{
-if ( source != null )
+XmlPullParser parser = new MXParser(
EntityReplacementMap.defaultEntityReplacementMap );
+parser.setInput( reader );
+
+TransformerContext context = getTransformerContext( options );
+if ( context != null )
+{
+parser = transformer.transform( parser, pomFile, context );
+}
+
+// TODO: avoid or at least cache reflection data
+InputSource source = getSource( options );
+boolean strict = isStrict( options );
+try
{
-return new MavenXpp3ReaderEx().read( reader, strict, source );
+if ( source != null )
+{
+MavenXpp3ReaderEx mr = new MavenXpp3ReaderEx();
+Method readMethod = mr.getClass().getDeclaredMethod(
"read",
+XmlPullParser.class, boolean.class,
InputSource.class );
+readMethod.setAccessible( true );
+
[jira] [Created] (MPOM-265) re-enable reproducible builds for ASF parent POM
Herve Boutemy created MPOM-265: -- Summary: re-enable reproducible builds for ASF parent POM Key: MPOM-265 URL: https://issues.apache.org/jira/browse/MPOM-265 Project: Maven POMs Issue Type: Bug Components: asf Affects Versions: ASF-24 Reporter: Herve Boutemy Fix For: ASF-25 project.build.outputTimestamp property was removed in MPOM-255 need to add it back for ASF parent POM source-release zip file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-255) Enforce local property "project.build.outputTimestamp" for reproducible builds
[ https://issues.apache.org/jira/browse/MPOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378671#comment-17378671 ] Herve Boutemy commented on MPOM-255: this commit breaks ASF parent POM reproducible build itself as it was done in MPOM-229, by removing the property: why remove the property? > Enforce local property "project.build.outputTimestamp" for reproducible builds > -- > > Key: MPOM-255 > URL: https://issues.apache.org/jira/browse/MPOM-255 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: ASF-24 > > > In case the release's root pom.xml doesn't overwrite > "project.build.outputTimestamp" it takes the value from > [https://github.com/apache/maven-apache-parent/blob/4813409e6a1ecfea11c8eb22a5f0443f790f1454/pom.xml#L95.] > Instead of the fallback an enforcer rule should be added to require a > property "project.build.outputTimestamp" to be set in the right format for > reproducible builds to work > ([https://maven.apache.org/guides/mini/guide-reproducible-builds.html#how-do-i-configure-my-maven-build]) > for every pom.xml locally. > Only that way the timestamps are automatically adjusted with each release > (https://issues.apache.org/jira/browse/MRELEASE-1029) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-dependency-plugin] bmarwell commented on a change in pull request #135: [MDEP-568] go offline filter
bmarwell commented on a change in pull request #135: URL: https://github.com/apache/maven-dependency-plugin/pull/135#discussion_r667494130 ## File path: src/main/java/org/apache/maven/plugins/dependency/filters/AbstractDependencyFilter.java ## @@ -0,0 +1,50 @@ +package org.apache.maven.plugins.dependency.filters; + +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +import java.util.HashSet; +import java.util.Locale; +import java.util.Set; + + +abstract class AbstractDependencyFilter implements DependencyFilter Review comment: I was thinking of closing this PR. We would need the same logic for other goals as well, and this goal could be replaced with the combination of two other goals. I think you could just create a PR to my branch of you're interested to keep it up. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MENFORCER-329) Example for writing a custom rule should be upgraded
[ https://issues.apache.org/jira/browse/MENFORCER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378647#comment-17378647 ] Hudson commented on MENFORCER-329: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer » master #64 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/64/ > Example for writing a custom rule should be upgraded > > > Key: MENFORCER-329 > URL: https://issues.apache.org/jira/browse/MENFORCER-329 > Project: Maven Enforcer Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-M2 >Reporter: Karl Heinz Marbaise >Assignee: Robert Scholte >Priority: Minor > Fix For: 3.0.0 > > > https://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MENFORCER-329) Example for writing a custom rule should be upgraded
[ https://issues.apache.org/jira/browse/MENFORCER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-329. Assignee: Robert Scholte (was: Karl Heinz Marbaise) Resolution: Fixed Unclear what should be updated, but at least the maven version now uses the prerequisite of the plugin. Now it will always be in sync with this requirement of the enforcer-plugin. Fixed in [a6949503a48702d59dabdf68cc37a87ed17a8b21|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=a6949503a48702d59dabdf68cc37a87ed17a8b21] > Example for writing a custom rule should be upgraded > > > Key: MENFORCER-329 > URL: https://issues.apache.org/jira/browse/MENFORCER-329 > Project: Maven Enforcer Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-M2 >Reporter: Karl Heinz Marbaise >Assignee: Robert Scholte >Priority: Minor > Fix For: 3.0.0 > > > https://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MENFORCER-311) enforce-dependency-rules performance dropdown for maven 3.5.x
[ https://issues.apache.org/jira/browse/MENFORCER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-311. Assignee: Robert Scholte Resolution: Incomplete There's no feedback, so I'll close this one. MENFORCER-332 looks like a duplicate with more concrete information. > enforce-dependency-rules performance dropdown for maven 3.5.x > - > > Key: MENFORCER-311 > URL: https://issues.apache.org/jira/browse/MENFORCER-311 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin, Standard Rules >Affects Versions: 1.4.1 > Environment: Linux OS, Debian Jessie, 64bit > Oracle Java 1.8.0_144 > Maven 3.5.4 >Reporter: Petr Hribal >Assignee: Robert Scholte >Priority: Major > Attachments: logs.339.zip, logs.zip > > > Hi guys, since we have started using Maven 3.5.x (3.5.0, 3.5.2, 3.5.4) on our > project, we're experiencing significant performance dropdown of our build > process. It is mainly caused by maven-enforcer-plugin, which we use to > enforce dependency rules. > I run the maven with -X debug option and based on that, I can say it spends > all the time analyzing project dependencies. > See the attached logs. > The build on Maven 3.3.9 takes round about 30s, but on 3.5.x it is almost > 7mins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MENFORCER-376) Add support for excludes/includes in requireJavaVendor rule
[ https://issues.apache.org/jira/browse/MENFORCER-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MENFORCER-376: Assignee: Robert Scholte > Add support for excludes/includes in requireJavaVendor rule > --- > > Key: MENFORCER-376 > URL: https://issues.apache.org/jira/browse/MENFORCER-376 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Standard Rules >Affects Versions: 3.0.0-M3 >Reporter: Krosheninnikov Artem >Assignee: Robert Scholte >Priority: Major > > There was a suggestion here [1] to add includes/excludes support in > requireJavaVendor rule. Right now it's not clear how it would work if you > define the same vendor name in exclude and include lists but implementation > can be more or less copied from BannedDependencies rule. > [1] > https://issues.apache.org/jira/browse/MENFORCER-338?focusedCommentId=17169044=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17169044 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MENFORCER-370) should not take resolved properties as Java string, but escape backslashes
[
https://issues.apache.org/jira/browse/MENFORCER-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MENFORCER-370.
Assignee: Robert Scholte
Resolution: Won't Fix
This is actually a "Can't fix". The conditon is first evaluated by the
[PluginParameterExpressionEvaluator|https://maven.apache.org/ref/current/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html]
to replace the known expressions. This result, a script, is being fed to
Beanshell.
The PluginParameterExpressionEvaluator only works with getters, so
${project.basedir.path.replace('\\','/')} won't work either.
Instead I suggest to switch to the [Maven Scripting
Plguin|http://maven.apache.org/plugins/maven-scripting-plugin/index.html]. I'm
not sure if there's a JSR223 Scripting engine available for BeanShell, but at
least there's one for Groovy.
This uses a
[context|https://maven.apache.org/plugins/maven-scripting-plugin/script-context.html],
so values are Objects instead of preresolved Strings.
> should not take resolved properties as Java string, but escape
> backslashes
> ---
>
> Key: MENFORCER-370
> URL: https://issues.apache.org/jira/browse/MENFORCER-370
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0-M2
> Environment: Apache Maven 3.6.3
> (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Java version: 11.0.9.1, vendor: ojdkbuild
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Damian
>Assignee: Robert Scholte
>Priority: Major
>
> Running Maven with {{${project.basedir}}} in the
> {{}} in a pom.xml fails under Windows, while
> Linux is fine.
> Already
> {code:xml}
>
>
> print(java.nio.file.Paths.get("${project.basedir}/".replace("\\",
> "/"));
> 1==1
>
>
> {code}
> fails with {{Couldn't evaluate condition...}} as {{$\{project.basedir}}} is
> apparently taken as a Java string directly, w/o escaping the backslashes.
> While the {{message}} part
> {code:xml}
>
>
> 1==0
>
> condition failed,
> project.basedir=${project.basedir}
>
> {code}
> logs the Windows path correctly:
> {code:bash}
> [WARNING] Rule 2: org.apache.maven.plugins.enforcer.EvaluateBeanshell
> failed with message:
> condition failed,
> project.basedir=C:\Users\me\git\project\dir_with_pom_file
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MENFORCER-173) Create an Groovy equivalent to evaluateBeanshell
[
https://issues.apache.org/jira/browse/MENFORCER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MENFORCER-173.
Fix Version/s: (was: 3.0.1)
Assignee: Robert Scholte
Resolution: Won't Fix
Scripting should be done by the [Maven Scripting
Plugin|http://maven.apache.org/plugins/maven-scripting-plugin/index.html],
which is much more powerful.
> Create an Groovy equivalent to evaluateBeanshell
>
>
> Key: MENFORCER-173
> URL: https://issues.apache.org/jira/browse/MENFORCER-173
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Components: Documentation, Plugin, Rule API, Standard Rules
> Environment: all
>Reporter: Karl Heinz Marbaise
>Assignee: Robert Scholte
>Priority: Minor
>
> It would be nice having a Groovy equivalent to
> {code}
> ${project.artifactId} == foo
> {code}
> like this:
> {code}
>
> ${project.artifactId} == foo
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
