[jira] [Updated] (MNG-6935) maven3.6.1 deploy fail
[
https://issues.apache.org/jira/browse/MNG-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hb0730 updated MNG-6935:
Description:
When using Maven 3.6.1 native deployment, there will be errors, but maven 3.3.9
deployment can be accessed normally, but I can only use HTTP
{code:java}
Failed to dispatch transfer event 'PUT PROGRESSED
http://nexus.hohofast.natapp1.cc/repository/maven-snapshots/com/hohofast/hohofast-recovery/1.0.0-SNAPSHOT/hohofast-recovery-1.0.0-20200608.031900-4.jar
<>
E:\IdeaWork\hohofast-work\hohofast-recovery\target\hohofast-recovery-1.0.0-SNAPSHOT.jar'
to org.apache.maven.cli.transfer.ConsoleMavenTransferListener
java.lang.IllegalArgumentException: progressed file size cannot be greater than
size: 131304578 > 85167234 at org.apache.commons.lang3.Validate.isTrue
(Validate.java:158) at
org.apache.maven.cli.transfer.AbstractMavenTransferListener$FileSizeFormat.formatProgress
(AbstractMavenTransferListener.java:195) at
org.apache.maven.cli.transfer.ConsoleMavenTransferListener.getStatus
(ConsoleMavenTransferListener.java:117) at
org.apache.maven.cli.transfer.ConsoleMavenTransferListener.transferProgressed
(ConsoleMavenTransferListener.java:90) at
org.eclipse.aether.internal.impl.SafeTransferListener.transferProgressed
(SafeTransferListener.java:105) at
org.eclipse.aether.connector.basic.TransferTransportListener.transportProgressed
(TransferTransportListener.java:95) at
org.eclipse.aether.transport.wagon.WagonTransferListener.transferProgress
(WagonTransferListener.java:64) at
org.apache.maven.wagon.events.TransferEventSupport.fireTransferProgress
(TransferEventSupport.java:121) at
org.apache.maven.wagon.AbstractWagon.fireTransferProgress
(AbstractWagon.java:658) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.access$200
(AbstractHttpClientWagon.java:112) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon$RequestEntityImplementation.writeTo
(AbstractHttpClientWagon.java:214) at
org.apache.maven.wagon.providers.http.httpclient.impl.DefaultBHttpClientConnection.sendRequestEntity
(DefaultBHttpClientConnection.java:156) at
org.apache.maven.wagon.providers.http.httpclient.impl.conn.CPoolProxy.sendRequestEntity
(CPoolProxy.java:152) at
org.apache.maven.wagon.providers.http.httpclient.protocol.HttpRequestExecutor.doSendRequest
(HttpRequestExecutor.java:238) at
org.apache.maven.wagon.providers.http.httpclient.protocol.HttpRequestExecutor.execute
(HttpRequestExecutor.java:123) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.execute
(MainClientExec.java:272) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.ProtocolExec.execute
(ProtocolExec.java:185) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec.execute
(RetryExec.java:89) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RedirectExec.execute
(RedirectExec.java:110) at
org.apache.maven.wagon.providers.http.httpclient.impl.client.InternalHttpClient.doExecute
(InternalHttpClient.java:185) at
org.apache.maven.wagon.providers.http.httpclient.impl.client.CloseableHttpClient.execute
(CloseableHttpClient.java:83) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.execute
(AbstractHttpClientWagon.java:958) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:713) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:670) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:652) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:646) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:626) at
org.eclipse.aether.transport.wagon.WagonTransporter$PutTaskRunner.run
(WagonTransporter.java:686) at
org.eclipse.aether.transport.wagon.WagonTransporter.execute
(WagonTransporter.java:435) at
org.eclipse.aether.transport.wagon.WagonTransporter.put
(WagonTransporter.java:418) at
org.eclipse.aether.connector.basic.BasicRepositoryConnector$PutTaskRunner.runTask
(BasicRepositoryConnector.java:554) at
org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run
(BasicRepositoryConnector.java:363) at
org.eclipse.aether.connector.basic.BasicRepositoryConnector.put
(BasicRepositoryConnector.java:287) at
org.eclipse.aether.internal.impl.DefaultDeployer.deploy
(DefaultDeployer.java:295) at
org.eclipse.aether.internal.impl.DefaultDeployer.deploy
(DefaultDeployer.java:211) at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy
(DefaultRepositorySystem.java:381) at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
[jira] [Created] (MNG-6935) maven3.6.1 deploy fail
hb0730 created MNG-6935:
---
Summary: maven3.6.1 deploy fail
Key: MNG-6935
URL: https://issues.apache.org/jira/browse/MNG-6935
Project: Maven
Issue Type: Bug
Components: Deployment
Affects Versions: 3.6.1
Environment: maven3.6.1
nexus3
nginx 1.15
os: windows10
Reporter: hb0730
When using Maven 3.6.1 native deployment, there will be errors, but maven 3.3.9
deployment can be accessed normally, but I can only use HTTP
{code:java}
//代码占位符
{code}
Failed to dispatch transfer event 'PUT PROGRESSED
http://nexus.hohofast.natapp1.cc/repository/maven-snapshots/com/hohofast/hohofast-recovery/1.0.0-SNAPSHOT/hohofast-recovery-1.0.0-20200608.031900-4.jar
<>
E:\IdeaWork\hohofast-work\hohofast-recovery\target\hohofast-recovery-1.0.0-SNAPSHOT.jar'
to org.apache.maven.cli.transfer.ConsoleMavenTransferListener
java.lang.IllegalArgumentException: progressed file size cannot be greater than
size: 131304578 > 85167234 at org.apache.commons.lang3.Validate.isTrue
(Validate.java:158) at
org.apache.maven.cli.transfer.AbstractMavenTransferListener$FileSizeFormat.formatProgress
(AbstractMavenTransferListener.java:195) at
org.apache.maven.cli.transfer.ConsoleMavenTransferListener.getStatus
(ConsoleMavenTransferListener.java:117) at
org.apache.maven.cli.transfer.ConsoleMavenTransferListener.transferProgressed
(ConsoleMavenTransferListener.java:90) at
org.eclipse.aether.internal.impl.SafeTransferListener.transferProgressed
(SafeTransferListener.java:105) at
org.eclipse.aether.connector.basic.TransferTransportListener.transportProgressed
(TransferTransportListener.java:95) at
org.eclipse.aether.transport.wagon.WagonTransferListener.transferProgress
(WagonTransferListener.java:64) at
org.apache.maven.wagon.events.TransferEventSupport.fireTransferProgress
(TransferEventSupport.java:121) at
org.apache.maven.wagon.AbstractWagon.fireTransferProgress
(AbstractWagon.java:658) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.access$200
(AbstractHttpClientWagon.java:112) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon$RequestEntityImplementation.writeTo
(AbstractHttpClientWagon.java:214) at
org.apache.maven.wagon.providers.http.httpclient.impl.DefaultBHttpClientConnection.sendRequestEntity
(DefaultBHttpClientConnection.java:156) at
org.apache.maven.wagon.providers.http.httpclient.impl.conn.CPoolProxy.sendRequestEntity
(CPoolProxy.java:152) at
org.apache.maven.wagon.providers.http.httpclient.protocol.HttpRequestExecutor.doSendRequest
(HttpRequestExecutor.java:238) at
org.apache.maven.wagon.providers.http.httpclient.protocol.HttpRequestExecutor.execute
(HttpRequestExecutor.java:123) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.execute
(MainClientExec.java:272) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.ProtocolExec.execute
(ProtocolExec.java:185) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec.execute
(RetryExec.java:89) at
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RedirectExec.execute
(RedirectExec.java:110) at
org.apache.maven.wagon.providers.http.httpclient.impl.client.InternalHttpClient.doExecute
(InternalHttpClient.java:185) at
org.apache.maven.wagon.providers.http.httpclient.impl.client.CloseableHttpClient.execute
(CloseableHttpClient.java:83) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.execute
(AbstractHttpClientWagon.java:958) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:713) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:670) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:652) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:646) at
org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put
(AbstractHttpClientWagon.java:626) at
org.eclipse.aether.transport.wagon.WagonTransporter$PutTaskRunner.run
(WagonTransporter.java:686) at
org.eclipse.aether.transport.wagon.WagonTransporter.execute
(WagonTransporter.java:435) at
org.eclipse.aether.transport.wagon.WagonTransporter.put
(WagonTransporter.java:418) at
org.eclipse.aether.connector.basic.BasicRepositoryConnector$PutTaskRunner.runTask
(BasicRepositoryConnector.java:554) at
org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run
(BasicRepositoryConnector.java:363) at
org.eclipse.aether.connector.basic.BasicRepositoryConnector.put
(BasicRepositoryConnector.java:287) at
org.eclipse.aether.internal.impl.DefaultDeployer.deploy
(DefaultDeployer.java:295) at
[jira] [Updated] (MSHADE-371) Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LICENSE].md
[ https://issues.apache.org/jira/browse/MSHADE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSHADE-371: Summary: Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LICENSE].md (was: Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md) > Update Shade Apache[Notice/LISENCE]ResourceTransformer to use > [NOTICE/LICENSE].md > - > > Key: MSHADE-371 > URL: https://issues.apache.org/jira/browse/MSHADE-371 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: John Millner >Priority: Trivial > > for > * org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer > * org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer > there is no check for LISENCE.md or NOTICE.md > small PR wanted to add that in along with the checks for LISENCE/LISENCE.txt > and NOTICE/NOTICE.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MWAR-429) Failed to execute goal org.apache.maven.plugins:maven-war-plugin:3.2.3:exploded (pre-exploded-war) on project alfresco-platform
[
https://issues.apache.org/jira/browse/MWAR-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MWAR-429:
---
Priority: Major (was: Blocker)
> Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:3.2.3:exploded (pre-exploded-war)
> on project alfresco-platform
> ---
>
> Key: MWAR-429
> URL: https://issues.apache.org/jira/browse/MWAR-429
> Project: Maven WAR Plugin
> Issue Type: Bug
>Affects Versions: 3.2.3
> Environment: NAME="Ubuntu"
> VERSION="16.04.6 LTS (Xenial Xerus)"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 16.04.6 LTS"
> VERSION_ID="16.04"
> # arch
> x86_64
> # java -version
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09)
> OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.232-b09, mixed mode)
> # mvn --version
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /root/apache-maven-3.6.3
> Java version: 1.8.0_232, vendor: AdoptOpenJDK, runtime: /root/jdk8u232-b09/jre
> Default locale: en_US, platform encoding: ANSI_X3.4-1968
> OS name: "linux", version: "4.15.0-66-generic", arch: "amd64", family: "unix"
>
>Reporter: Abhay Singh
>Priority: Major
>
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:3.2.3:exploded (pre-exploded-war)
> on project alfresco-platform: Exection pre-exploded-war of goal
> org.apache.maven.plugins:maven-war-plugin:3.2.3:exploded failed:}}
> {{[ERROR] Debugging information }}
> {{[ERROR] cause-exception :
> com.thoughtworks.xstream.mapper.CannotResolveClassException}}
> {{[ERROR] cause-message : org.apache.maven.plugin.war.util.DependencyInfo}}
> {{[ERROR] class : java.util.ArrayList}}
> {{[ERROR] required-type : java.util.ArrayList}}
> {{[ERROR] converter-type :
> com.thoughtworks.xstream.converters.collections.CollectionConverter}}
> {{[ERROR] path :
> /webapp-structure/dependenciesInfo/org.apache.maven.plugin.war.util.DependencyInfo}}
> {{[ERROR] class[1] : org.apache.maven.plugins.war.util.WebappStructure}}
> {{[ERROR] converter-type[1] :
> com.thoughtworks.xstream.converters.reflection.ReflectionConverter}}
> {{[ERROR] version : 3.2.3}}
> {{[ERROR] ---}}
> {{[ERROR] -> [Help 1]}}
> {{[ERROR]}}
> {{[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.}}
> {{[ERROR] Re-run Maven using the -X switch to enable full debug logging.}}
> {{[ERROR]}}
> {{[ERROR] For more information about the errors and possible solutions,
> please read the following articles:}}
> {{[ERROR] [Help 1]
> [http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException]}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1228) rerunFailingTestsCount + TestNG + @DataProvider = failed tests pass
[
https://issues.apache.org/jira/browse/SUREFIRE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127792#comment-17127792
]
Tibor Digana commented on SUREFIRE-1228:
[~cmorris_partnet] possibly yes in the future. Currently the users want us to
fork the reruns in separate JVMs. So many people have many other requirements.
But yes, your requirement is visible too.
> rerunFailingTestsCount + TestNG + @DataProvider = failed tests pass
> ---
>
> Key: SUREFIRE-1228
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1228
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.19.1
>Reporter: Cam Morris
>Assignee: Tibor Digana
>Priority: Major
> Attachments: TestRandomFail.java, pom.xml
>
>
> Surefire confuses tests run with a data-provider with rerun tests so only one
> of the data-provided tests need to pass.
> Steps to reproduce:
> # Create a testNG test with a data provider that passes with some of the data
> and fails with others
> {code:title=TestNG example|language=java}
> @Test(dataProvider = "succeed")
> public void fail(boolean succeed) {
> if (!succeed) {
> Assert.fail("nope");
> }
> }
> @DataProvider(name="succeed")
> public Object[][] arrayIndex() {
> return new Object[][]{ {true}, {false}};
> }
> {code}
> # Configure surefire to rerun failed tests
> {code:title=pom.xml example|language=xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> cam.test
> testng-retry
> 1.0-SNAPSHOT
>
>
> org.testng
> testng
> 6.9.10
> test
>
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.19.1
>
> 1
>
>
>
>
>
> {code}
> - *Expected results*: "Tests run: 2, Failures: 1..." The tests should not
> pass.
> - *Actual results*: "Tests run: 1, Failures: 0, Errors: 0, Skipped: 0,
> Flakes: 1" The rerun confuses test runs with different data for retry
> attempts. Just one of the data provider tests needs to succeed for the test
> to be deemed a success.
> {code}mvn test
> ...
> ---
> T E S T S
> ---
> Running TestRandomFail
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.267 sec <<<
> FAILURE! - in TestRandomFail
> fail(TestRandomFail) Time elapsed: 0.007 sec <<< FAILURE!
> java.lang.AssertionError: nope
> at TestRandomFail.fail(TestRandomFail.java:14)
> Results :
> Flaked tests:
> TestRandomFail.fail(TestRandomFail)
> Run 1: PASS
> Run 2: TestRandomFail.fail:14 nope
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Flakes: 1
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 2.251 s
> [INFO] Finished at: 2016-02-10T07:39:21-07:00
> [INFO] Final Memory: 9M/244M
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127790#comment-17127790 ] Elliotte Rusty Harold commented on MNGSITE-413: --- Can this be expanded on? This seems to say we need a website for maven. We have one. What is being proposed here? > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Assignee: Robert Scholte >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-5315) Artifact resolution sporadically fails in parallel builds
[
https://issues.apache.org/jira/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127787#comment-17127787
]
Michael Osipov commented on MNG-5315:
-
Read my description on the issue:
https://issues.apache.org/jira/browse/MRESOLVER-114?focusedCommentId=17127769=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17127769
> Artifact resolution sporadically fails in parallel builds
> -
>
> Key: MNG-5315
> URL: https://issues.apache.org/jira/browse/MNG-5315
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.4
>Reporter: Ivan Dubrov
>Priority: Minor
> Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch
>
>
> Artifact resolution can fail during the parallel build if it was downloaded
> during the same session.
> Scenario:
> 1) Delete the whole Maven local repository.
> 2) Run build "mvn compile -T1.5C"
> 3) Build fails (see log extracts below)
> 4) If I run build again, it succeeds.
> It seems like the problem is due to two thread trying to resolve same
> artifact concurrently. This problem never happens once I have all
> dependencies cached in the local repository.
> Extracts from the log output:
> {noformat}Downloading:
> http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
> 12444/13937 KB ...
> ...
> [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2,
> already updated during this session.
> [DEBUG] Skipped remote update check for
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this
> session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4,
> already updated during this session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4,
> already updated during this session.
> ...
> [ERROR] Failed to execute goal on project util: Could not resolve
> dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The
> following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project util: Could not resolve dependencies for project
> com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not
> be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at
[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #300: [SUREFIRE-1796] The session of TCP channel should be authenticated
Tibor17 edited a comment on pull request #300: URL: https://github.com/apache/maven-surefire/pull/300#issuecomment-640286858 Now we use `sessionId` and `localhost` in mock tests or IP address of localhost. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on pull request #300: [SUREFIRE-1796] The session of TCP channel should be authenticated
Tibor17 commented on pull request #300: URL: https://github.com/apache/maven-surefire/pull/300#issuecomment-640286858 Now we use `sessionId` and `localhost` in mock tetss or IP address of localhost. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-663) mark ReportPlugin and ReportSet package private
[
https://issues.apache.org/jira/browse/MSHARED-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127780#comment-17127780
]
Hudson commented on MSHARED-663:
Build failed in Jenkins: Maven TLP » maven-reporting-exec » master #40
See
https://builds.apache.org/job/maven-box/job/maven-reporting-exec/job/master/40/
> mark ReportPlugin and ReportSet package private
> ---
>
> Key: MSHARED-663
> URL: https://issues.apache.org/jira/browse/MSHARED-663
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-reporting-exec
>Affects Versions: maven-reporting-exec-1.4
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: maven-reporting-exec-1.5
>
>
> once MSHARED-628 is done, maven-site-plugin 3.7 won't use
> {{org.apache.maven.reporting.exec.ReportPlugin}} nor
> {{org.apache.maven.reporting.exec.ReportSet}}
> These classes remain useful for decoupling, but are now pure internal details
> of {{maven-reporting-exec}}: they should just be now package private
> This could not be done for {{maven-reporting-exec}} version 1.4 since
> maven-site-plugin 3.7 is not released yet
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-project-info-reports-plugin] michael-o closed pull request #15: [MPIR-374] No logging of stacktrace in non debug mode
michael-o closed pull request #15: URL: https://github.com/apache/maven-project-info-reports-plugin/pull/15 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-114) ArtifactNotFoundExceptions when building in parallel
[
https://issues.apache.org/jira/browse/MRESOLVER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1712#comment-1712
]
Michael Osipov commented on MRESOLVER-114:
--
According to {{AetherModule}} {{SyncContextFactory}} is a singleton. Even if
we'd have multiple DefaultArtifactResolver instances this would be OK.
> ArtifactNotFoundExceptions when building in parallel
>
>
> Key: MRESOLVER-114
> URL: https://issues.apache.org/jira/browse/MRESOLVER-114
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: 1.4.2
>Reporter: Rainer Reich
>Priority: Major
> Attachments: maven-debug-log.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have a multi-module project with quite many modules and many dependencies
> and observe pretty random {{ArtifactNotFoundExceptions}} when building in
> parallel with an empty local repository.
> The "funny" thing is that Maven did in fact download the jar that it
> complained about not finding.
> In this example Maven said it could not find
> {{edu.tum.cs:cup-runtime:jar:11a}} (see stacktrace below)
> But it also said: {{Downloaded from central-mirror:
> [https://mirror.xy.com/repository/maven-all-mirror/edu/tum/cs/cup-runtime/11a/cup-runtime-11a.jar]}}.
> When looking into the local repository after the failed build we found the
> cup-runtime.jar in the correct place with the correct checksum.
> We tried the following to "fix" the problem:
> * build with and without the takari extensions ({{takari-local-repository}}
> & {{takari-smart-builder}}) using {{--builder smart}}
> * also build with {{io.takari.aether:aether-connector-okhttp}} extension
> * only execute goal package instead of install
> * build with these properties: {{-Daether.connector.basic.threads=1
> -Daether.connector.resumeDownloads=false}}
> But nothing helped.
> Unfortunately it seems to be a race condition and we cannot reproduce it
> consistently but it happens in about 1 out of 5 builds.
> {code:java}
> ...
> [2019-11-18T16:46:29.370Z] [INFO] Downloaded from central-mirror:
> https://mirror.xy.com/repository/maven-all-mirror/edu/tum/cs/cup-runtime/11a/cup-runtime-11a.jar
> (13 kB at 738 kB/s)
> ...
> [2019-11-18T16:46:30.894Z] [ERROR] Failed to execute goal on project xy:
> Could not resolve dependencies for project xy: The following artifacts could
> not be resolved: edu.tum.cs:cup-runtime:jar:11a,
> org.checkerframework:checker-qual:jar:2.5.7, org.ow2.asm:asm:jar:7.2,
> cglib:cglib:jar:3.3.0: Could not find artifact edu.tum.cs:cup-runtime:jar:11a
> -> [Help 1]
> [2019-11-18T16:46:30.894Z]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project xy: Could not resolve dependencies for project xy: The
> following artifacts could not be resolved: edu.tum.cs:cup-runtime:jar:11a,
> org.checkerframework:checker-qual:jar:2.5.7, org.ow2.asm:asm:jar:7.2,
> cglib:cglib:jar:3.3.0: Could not find artifact edu.tum.cs:cup-runtime:jar:11a
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResolver.java:269)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
> (LifecycleDependencyResolver.java:147)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
> (MojoExecutor.java:248)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:202)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> [2019-11-18T16:46:30.894Z] at
> io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
> (SmartBuilderImpl.java:205)
> [2019-11-18T16:46:30.894Z] at
> io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
> (SmartBuilderImpl.java:77)
> [2019-11-18T16:46:30.894Z] at
> java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
> [2019-11-18T16:46:30.894Z] at java.util.concurrent.FutureTask.run
> (FutureTask.java:264)
> [2019-11-18T16:46:30.894Z] at
> java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1128)
> [2019-11-18T16:46:30.894Z] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:628)
> [2019-11-18T16:46:30.894Z] at java.lang.Thread.run
[jira] [Closed] (MSHARED-921) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1
[ https://issues.apache.org/jira/browse/MSHARED-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSHARED-921. - Resolution: Fixed fixed in https://github.com/apache/maven-reporting-exec/commit/6f06039bd9439ce06fd702ece8d8894a3a684626/ by shading Xpp3DomUtils class in a version that does not require the new Xpp3Dom input location tracking > NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1 > --- > > Key: MSHARED-921 > URL: https://issues.apache.org/jira/browse/MSHARED-921 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-reporting-exec >Affects Versions: maven-reporting-exec-1.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: maven-reporting-exec-1.5 > > > see MSITE-863 for context > > this is caused by Xpp3Dom class incompatibility with > Xpp3DomUtils.mergeXpp3Dom(...) > > Xpp3Dom version is taken from Maven core classloader as exported: see > [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] > Xpp3DomUtils is taken from current plugin classloader > > with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils > is a recent version (plexus-utils >= 3.2.0) that expects to merge the input > location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] > but older Maven core versions don't have this input location field in > Xpp3Dom, since they provide older plexus-utils that was upgraded to add > location tracking in MNG-6597 for Maven 3.6.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRESOLVER-114) ArtifactNotFoundExceptions when building in parallel
[
https://issues.apache.org/jira/browse/MRESOLVER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127770#comment-17127770
]
Michael Osipov commented on MRESOLVER-114:
--
[~rfscholte], can you share your opinion please?
> ArtifactNotFoundExceptions when building in parallel
>
>
> Key: MRESOLVER-114
> URL: https://issues.apache.org/jira/browse/MRESOLVER-114
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: 1.4.2
>Reporter: Rainer Reich
>Priority: Major
> Attachments: maven-debug-log.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have a multi-module project with quite many modules and many dependencies
> and observe pretty random {{ArtifactNotFoundExceptions}} when building in
> parallel with an empty local repository.
> The "funny" thing is that Maven did in fact download the jar that it
> complained about not finding.
> In this example Maven said it could not find
> {{edu.tum.cs:cup-runtime:jar:11a}} (see stacktrace below)
> But it also said: {{Downloaded from central-mirror:
> [https://mirror.xy.com/repository/maven-all-mirror/edu/tum/cs/cup-runtime/11a/cup-runtime-11a.jar]}}.
> When looking into the local repository after the failed build we found the
> cup-runtime.jar in the correct place with the correct checksum.
> We tried the following to "fix" the problem:
> * build with and without the takari extensions ({{takari-local-repository}}
> & {{takari-smart-builder}}) using {{--builder smart}}
> * also build with {{io.takari.aether:aether-connector-okhttp}} extension
> * only execute goal package instead of install
> * build with these properties: {{-Daether.connector.basic.threads=1
> -Daether.connector.resumeDownloads=false}}
> But nothing helped.
> Unfortunately it seems to be a race condition and we cannot reproduce it
> consistently but it happens in about 1 out of 5 builds.
> {code:java}
> ...
> [2019-11-18T16:46:29.370Z] [INFO] Downloaded from central-mirror:
> https://mirror.xy.com/repository/maven-all-mirror/edu/tum/cs/cup-runtime/11a/cup-runtime-11a.jar
> (13 kB at 738 kB/s)
> ...
> [2019-11-18T16:46:30.894Z] [ERROR] Failed to execute goal on project xy:
> Could not resolve dependencies for project xy: The following artifacts could
> not be resolved: edu.tum.cs:cup-runtime:jar:11a,
> org.checkerframework:checker-qual:jar:2.5.7, org.ow2.asm:asm:jar:7.2,
> cglib:cglib:jar:3.3.0: Could not find artifact edu.tum.cs:cup-runtime:jar:11a
> -> [Help 1]
> [2019-11-18T16:46:30.894Z]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project xy: Could not resolve dependencies for project xy: The
> following artifacts could not be resolved: edu.tum.cs:cup-runtime:jar:11a,
> org.checkerframework:checker-qual:jar:2.5.7, org.ow2.asm:asm:jar:7.2,
> cglib:cglib:jar:3.3.0: Could not find artifact edu.tum.cs:cup-runtime:jar:11a
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResolver.java:269)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
> (LifecycleDependencyResolver.java:147)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
> (MojoExecutor.java:248)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:202)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> [2019-11-18T16:46:30.894Z] at
> io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
> (SmartBuilderImpl.java:205)
> [2019-11-18T16:46:30.894Z] at
> io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
> (SmartBuilderImpl.java:77)
> [2019-11-18T16:46:30.894Z] at
> java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
> [2019-11-18T16:46:30.894Z] at java.util.concurrent.FutureTask.run
> (FutureTask.java:264)
> [2019-11-18T16:46:30.894Z] at
> java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1128)
> [2019-11-18T16:46:30.894Z] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:628)
> [2019-11-18T16:46:30.894Z] at java.lang.Thread.run (Thread.java:834)
> [2019-11-18T16:46:30.894Z] Caused by:
>
[jira] [Commented] (MRESOLVER-114) ArtifactNotFoundExceptions when building in parallel
[
https://issues.apache.org/jira/browse/MRESOLVER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127769#comment-17127769
]
Michael Osipov commented on MRESOLVER-114:
--
I have put some effort into it analyzed the issue and it is disappointing.
First of all, I think we suffer from
[this|https://stackoverflow.com/q/21739080/696632] problem and both PRs are
wrong while the retry approach is, IMHO, even worse even if it/both "solves"
the issue. I was not able to find logically the code spot in question, but
there *is* a race condition. Unfortunately, Resolver has very little logging
which would help us to narrow down the issue.
Now let me go into detail what I have figured out:
When we go the callstack up from #resolve() we land in public ...
resolveArtifacts(...) which does the following:
{code:java}
try ( SyncContext syncContext = syncContextFactory.newInstance( session, false
) )
{
Collection artifacts = new ArrayList<>( requests.size() );
for ( ArtifactRequest request : requests )
{
if ( request.getArtifact().getProperty(
ArtifactProperties.LOCAL_PATH, null ) != null )
{
continue;
}
artifacts.add( request.getArtifact() );
}
syncContext.acquire( artifacts, null );
return resolve( session, requests );
}
{code}
Wait a minute, there is synchronization already, why does it still fail?
Well...let's have a look at SyncContextFactory and SyncContext first:
SyncContextFactory shall create a reentrant read write lock for the given
session. The boolean flag says read or write. SyncContext#acquire() shall
perform the lock operation on the values (GAV keys) (!) of the given
artifacts/metadata. This approach is used everywhere in the code where
interaction with the filesytem is necessary. So #resolve() is *not* intended to
be thread safe and it would be wrong to try to change it. Back to the question:
When we now look for all impls of SyncContext we find only DefaultSyncContext
which does nothing, i.e., no synchronization at all. Why do other operations
not fail with SyncContext? I assume that most either don't use a degree a
concurrency where it would fail on the same artifacts or it runs so fast that
we don't see race conditions.
How can this now be fixed? We have two challenges here:
1. #newInstance() implies that syncContext is always new (other identity), but
how shall #acquire() work multithreaded if no global locking on the artifacts
can be maintained? Weird. The only solution which comes to my mind is to
initialize a suitable lock implementation when #newInstance() is called in a
synchronized block and put into RepositorySystemSession#getData().If this
cannot be maintained we still will have the same race condition.
2. A suitable lock approach, if selfwritted, would require something like a
concurrent hash map with weak refs onto muteces which represent the value
(hashcode) of an artifact. On #acquire() the lock for that mutex is obtained
and #lock() called. When the try block is left #release() is called
automatically.
Alternatively, one needs to use a KeyedReadWriteLock or StripedReadWriteLock
because we cannot maintain a lock per artifacts. This could end with thousands
of locks.
I think even for someone who does concurrency on a daily basis, it would take
some days to solve these points, for me whose concurrency skills are weak,
weeks. I cannot provide this one.
It has also to be noted that DefaultArtifactResolver is not marked with
@Singleton. I don't know whether there could be multiple instances used in
Maven which means that only a global lock will work because synchronized will
not have any effect or if SyncContextFactory is a singleton it could hold the
global lock and pass it to the SyncContext objects.
See also:
https://guava.dev/releases/19.0/api/docs/com/google/common/util/concurrent/Striped.html
A completely alternative approach is to write lock files for those objects
instead of an in-memory lock. SyncContext says "Note that the level of actual
synchronization is subject to the implementation and might range from OS-wide
to none."
Unless someone can provide something very smart, I will do the following:
* Add FIXMEs to all invocations of SyncContextFactory#newInstance() to a new
issue which describes this problem.
* Accept the compromise of PR #41.
Opinions?
> ArtifactNotFoundExceptions when building in parallel
>
>
> Key: MRESOLVER-114
> URL: https://issues.apache.org/jira/browse/MRESOLVER-114
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: 1.4.2
>Reporter: Rainer Reich
>Priority: Major
> Attachments: maven-debug-log.txt
>
> Time Spent:
[jira] [Comment Edited] (MSHADE-371) Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md
[
https://issues.apache.org/jira/browse/MSHADE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127765#comment-17127765
]
John Millner edited comment on MSHADE-371 at 6/7/20, 9:20 PM:
--
problem noticed after receiving this warning in a project:
{noformat}
jakarta.activation-api-1.2.1.jar, jakarta.xml.bind-api-2.3.2.jar define 2
overlapping resources:
META-INF/LICENSE.md
META-INF/NOTICE.md
{noformat}
was (Author: johnmillner):
problem noticed after receiving this warning in a project:
```
jakarta.activation-api-1.2.1.jar, jakarta.xml.bind-api-2.3.2.jar define 2
overlapping resources:
- META-INF/LICENSE.md
- META-INF/NOTICE.md
```
> Update Shade Apache[Notice/LISENCE]ResourceTransformer to use
> [NOTICE/LISENCE].md
> -
>
> Key: MSHADE-371
> URL: https://issues.apache.org/jira/browse/MSHADE-371
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Reporter: John Millner
>Priority: Trivial
>
> for
> * org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer
> * org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer
> there is no check for LISENCE.md or NOTICE.md
> small PR wanted to add that in along with the checks for LISENCE/LISENCE.txt
> and NOTICE/NOTICE.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHADE-371) Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md
[ https://issues.apache.org/jira/browse/MSHADE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127765#comment-17127765 ] John Millner commented on MSHADE-371: - problem noticed after receiving this warning in a project: ``` jakarta.activation-api-1.2.1.jar, jakarta.xml.bind-api-2.3.2.jar define 2 overlapping resources: - META-INF/LICENSE.md - META-INF/NOTICE.md ``` > Update Shade Apache[Notice/LISENCE]ResourceTransformer to use > [NOTICE/LISENCE].md > - > > Key: MSHADE-371 > URL: https://issues.apache.org/jira/browse/MSHADE-371 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: John Millner >Priority: Trivial > > for > * org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer > * org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer > there is no check for LISENCE.md or NOTICE.md > small PR wanted to add that in along with the checks for LISENCE/LISENCE.txt > and NOTICE/NOTICE.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-shade-plugin] johnmillner commented on pull request #51: MSHADE-371 - Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md
johnmillner commented on pull request #51: URL: https://github.com/apache/maven-shade-plugin/pull/51#issuecomment-640279945 https://issues.apache.org/jira/browse/MSHADE-371 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHADE-371) Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md
[ https://issues.apache.org/jira/browse/MSHADE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127759#comment-17127759 ] John Millner commented on MSHADE-371: - [https://github.com/apache/maven-shade-plugin/pull/51] > Update Shade Apache[Notice/LISENCE]ResourceTransformer to use > [NOTICE/LISENCE].md > - > > Key: MSHADE-371 > URL: https://issues.apache.org/jira/browse/MSHADE-371 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: John Millner >Priority: Trivial > > for > * org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer > * org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer > there is no check for LISENCE.md or NOTICE.md > small PR wanted to add that in along with the checks for LISENCE/LISENCE.txt > and NOTICE/NOTICE.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-shade-plugin] johnmillner opened a new pull request #51: MSHADE-371 - Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md
johnmillner opened a new pull request #51: URL: https://github.com/apache/maven-shade-plugin/pull/51 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MSHADE) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MSHADE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MSHADE-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). for * org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer * org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer there is no check for LISENCE.md or NOTICE.md small PR wanted to add that in along with the checks for LISENCE/LISENCE.txt and NOTICE/NOTICE.txt This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSITE-828) Jdk 1.8 required
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127755#comment-17127755 ] Herve Boutemy commented on MSITE-828: - please wait for 3.9.1 release (required by major issue MSITE-863) before merging this, for future 3.10.0 thank you > Jdk 1.8 required > > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Fix For: 3.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSITE-863) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running reports with Maven versions < 3.6.1
[
https://issues.apache.org/jira/browse/MSITE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-863:
Priority: Blocker (was: Major)
> NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running reports with
> Maven versions < 3.6.1
>
>
> Key: MSITE-863
> URL: https://issues.apache.org/jira/browse/MSITE-863
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: Maven 3
>Affects Versions: 3.9.0
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Blocker
> Fix For: 3.9.1
>
>
> [https://lists.apache.org/thread.html/rbba90de4703f8109b543500a5ee9e5b17b6a1258d95c6b5815b9257a%40%3Cdev.maven.apache.org%3E]
> {noformat}
> mojo-parent (issue-105)$ mvn site site:stage
> ..
> [INFO]
> [INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-plugin-plugin:3.6.0
> [INFO] preparing maven-plugin-plugin:report report requires 'process-classes'
> forked phase execution
> [INFO]
> [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @mojo-parent >>>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules)
> @mojo-parent ---
> [INFO]
> [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @mojo-parent <<<
> [INFO] 'process-classes' forked phase execution for
> maven-plugin-plugin:report report preparation done
> [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-changes-plugin:2.11
> [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-checkstyle-plugin:2.16
> [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.144 s
> [INFO] Finished at: 2020-05-24T11:50:11+02:00
> [INFO] Final Memory: 30M/128M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
> project mojo-parent: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site:java.lang.NoSuchMethodError:
> 'java.lang.Object org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar{noformat}
> This can be reproduced with 3.0.5 up to 3.6.0.
> Versions 3.6.1, 3.6.2 and 3.6.3 are working fine.
> This means using maven-site-plugin 3.9.0 only working with Maven 3.6.1+
> ...in contradiction to the site[1] which says it is requirement 3.0..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MSHADE-371) Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md
John Millner created MSHADE-371: --- Summary: Update Shade Apache[Notice/LISENCE]ResourceTransformer to use [NOTICE/LISENCE].md Key: MSHADE-371 URL: https://issues.apache.org/jira/browse/MSHADE-371 Project: Maven Shade Plugin Issue Type: Improvement Reporter: John Millner for * org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer * org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer there is no check for LISENCE.md or NOTICE.md small PR wanted to add that in along with the checks for LISENCE/LISENCE.txt and NOTICE/NOTICE.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSITE-828) Jdk 1.8 required
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-828: Fix Version/s: (was: 3.9.1) 3.10.0 > Jdk 1.8 required > > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Fix For: 3.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSITE-829) Upgrade Jetty to 9.4.x
[ https://issues.apache.org/jira/browse/MSITE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-829: Fix Version/s: (was: 3.9.1) 3.10.0 > Upgrade Jetty to 9.4.x > -- > > Key: MSITE-829 > URL: https://issues.apache.org/jira/browse/MSITE-829 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Fix For: 3.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSITE-863) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running reports with Maven versions < 3.6.1
[
https://issues.apache.org/jira/browse/MSITE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-863:
Description:
[https://lists.apache.org/thread.html/rbba90de4703f8109b543500a5ee9e5b17b6a1258d95c6b5815b9257a%40%3Cdev.maven.apache.org%3E]
{noformat}
mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-plugin-plugin:3.6.0
[INFO] preparing maven-plugin-plugin:report report requires 'process-classes'
forked phase execution
[INFO]
[INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @mojo-parent >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @mojo-parent
---
[INFO]
[INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @mojo-parent <<<
[INFO] 'process-classes' forked phase execution for maven-plugin-plugin:report
report preparation done
[INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-changes-plugin:2.11
[INFO] 1 report configured for maven-changes-plugin:2.11: github-report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-checkstyle-plugin:2.16
[INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
[INFO] configuring report plugin
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.144 s
[INFO] Finished at: 2020-05-24T11:50:11+02:00
[INFO] Final Memory: 30M/128M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on project
mojo-parent: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.9.0:site:java.lang.NoSuchMethodError:
'java.lang.Object org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar{noformat}
This can be reproduced with 3.0.5 up to 3.6.0.
Versions 3.6.1, 3.6.2 and 3.6.3 are working fine.
This means using maven-site-plugin 3.9.0 only working with Maven 3.6.1+
...in contradiction to the site[1] which says it is requirement 3.0..
was:
[https://lists.apache.org/thread.html/rbba90de4703f8109b543500a5ee9e5b17b6a1258d95c6b5815b9257a%40%3Cdev.maven.apache.org%3E]
{noformat}
mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-plugin-plugin:3.6.0
[INFO] preparing maven-plugin-plugin:report report requires 'process-classes'
forked phase execution
[INFO]
[INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @mojo-parent >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @mojo-parent
---
[INFO]
[INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @mojo-parent <<<
[INFO] 'process-classes' forked phase execution for maven-plugin-plugin:report
report preparation done
[INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-changes-plugin:2.11
[INFO] 1 report configured for maven-changes-plugin:2.11: github-report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-checkstyle-plugin:2.16
[INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
[INFO] configuring report plugin
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.144 s
[INFO] Finished at: 2020-05-24T11:50:11+02:00
[INFO] Final Memory: 30M/128M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on project
mojo-parent: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.9.0:site:java.lang.NoSuchMethodError:
'java.lang.Object org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
[jira] [Commented] (MSHARED-921) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1
[ https://issues.apache.org/jira/browse/MSHARED-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127743#comment-17127743 ] Hudson commented on MSHARED-921: Build succeeded in Jenkins: Maven TLP » maven-reporting-exec » master #38 See https://builds.apache.org/job/maven-box/job/maven-reporting-exec/job/master/38/ > NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1 > --- > > Key: MSHARED-921 > URL: https://issues.apache.org/jira/browse/MSHARED-921 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-reporting-exec >Affects Versions: maven-reporting-exec-1.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: maven-reporting-exec-1.5 > > > see MSITE-863 for context > > this is caused by Xpp3Dom class incompatibility with > Xpp3DomUtils.mergeXpp3Dom(...) > > Xpp3Dom version is taken from Maven core classloader as exported: see > [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] > Xpp3DomUtils is taken from current plugin classloader > > with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils > is a recent version (plexus-utils >= 3.2.0) that expects to merge the input > location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] > but older Maven core versions don't have this input location field in > Xpp3Dom, since they provide older plexus-utils that was upgraded to add > location tracking in MNG-6597 for Maven 3.6.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHARED-921) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1
[ https://issues.apache.org/jira/browse/MSHARED-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-921: -- Description: see MSITE-863 for context this is caused by Xpp3Dom class incompatibility with Xpp3DomUtils.mergeXpp3Dom(...) Xpp3Dom version is taken from Maven core classloader as exported: see [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] Xpp3DomUtils is taken from current plugin classloader with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils is a recent version (plexus-utils >= 3.2.0) that expects to merge the input location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] but older Maven core versions don't have this input location field in Xpp3Dom, since they provide older plexus-utils that was upgraded to add location tracking in MNG-6597 for Maven 3.6.1 was: see MSITE-863 for context this is caused by Xpp3Dom class incompatibility with Xpp3DomUtils.mergeXpp3Dom(...) Xpp3Dom version is taken from Maven core classloader as exported: see [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] Xpp3DomUtils is taken from current plugin classloader with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils is a recent version (>= 3.2.0) that expects to merge the input location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] but older Maven core versions don't have this input location field in Xpp3Dom, since they provide older plexus-utils that was upgraded to add location tracking in MNG-6597 > NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1 > --- > > Key: MSHARED-921 > URL: https://issues.apache.org/jira/browse/MSHARED-921 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-reporting-exec >Affects Versions: maven-reporting-exec-1.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: maven-reporting-exec-1.5 > > > see MSITE-863 for context > > this is caused by Xpp3Dom class incompatibility with > Xpp3DomUtils.mergeXpp3Dom(...) > > Xpp3Dom version is taken from Maven core classloader as exported: see > [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] > Xpp3DomUtils is taken from current plugin classloader > > with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils > is a recent version (plexus-utils >= 3.2.0) that expects to merge the input > location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] > but older Maven core versions don't have this input location field in > Xpp3Dom, since they provide older plexus-utils that was upgraded to add > location tracking in MNG-6597 for Maven 3.6.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHARED-921) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1
[ https://issues.apache.org/jira/browse/MSHARED-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-921: -- Summary: NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1 (was: NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.2) > NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1 > --- > > Key: MSHARED-921 > URL: https://issues.apache.org/jira/browse/MSHARED-921 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-reporting-exec >Affects Versions: maven-reporting-exec-1.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: maven-reporting-exec-1.5 > > > see MSITE-863 for context > > this is caused by Xpp3Dom class incompatibility with > Xpp3DomUtils.mergeXpp3Dom(...) > > Xpp3Dom version is taken from Maven core classloader as exported: see > [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] > Xpp3DomUtils is taken from current plugin classloader > > with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils > is a recent version (>= 3.2.0) that expects to merge the input location (see > [https://github.com/codehaus-plexus/plexus-utils/issues/61)] > but older Maven core versions don't have this input location field in > Xpp3Dom, since they provide older plexus-utils that was upgraded to add > location tracking in MNG-6597 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSITE-863) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running reports with Maven versions < 3.6.1
[
https://issues.apache.org/jira/browse/MSITE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-863:
Summary: NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running
reports with Maven versions < 3.6.1 (was: NoSuchMethodError:
'Xpp3Dom.getInputLocation()' when running report)
> NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running reports with
> Maven versions < 3.6.1
>
>
> Key: MSITE-863
> URL: https://issues.apache.org/jira/browse/MSITE-863
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: Maven 3
>Affects Versions: 3.9.0
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.1
>
>
> [https://lists.apache.org/thread.html/rbba90de4703f8109b543500a5ee9e5b17b6a1258d95c6b5815b9257a%40%3Cdev.maven.apache.org%3E]
> {noformat}
> mojo-parent (issue-105)$ mvn site site:stage
> ..
> [INFO]
> [INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-plugin-plugin:3.6.0
> [INFO] preparing maven-plugin-plugin:report report requires 'process-classes'
> forked phase execution
> [INFO]
> [INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @mojo-parent >>>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules)
> @mojo-parent ---
> [INFO]
> [INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @mojo-parent <<<
> [INFO] 'process-classes' forked phase execution for
> maven-plugin-plugin:report report preparation done
> [INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-changes-plugin:2.11
> [INFO] 1 report configured for maven-changes-plugin:2.11: github-report
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-checkstyle-plugin:2.16
> [INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.144 s
> [INFO] Finished at: 2020-05-24T11:50:11+02:00
> [INFO] Final Memory: 30M/128M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
> project mojo-parent: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.9.0:site:java.lang.NoSuchMethodError:
> 'java.lang.Object org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
> [ERROR] -
> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar{noformat}
> This can be reproduced with 3.0.5 up to 3.6.1.
> Versions 3.6.2 and 3.6.3 are working fine.
> This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
> ...in contradiction to the site[1] which says it is requirement 3.0..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHARED-921) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.2
[ https://issues.apache.org/jira/browse/MSHARED-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-921: -- Description: see MSITE-863 for context this is caused by Xpp3Dom class incompatibility with Xpp3DomUtils.mergeXpp3Dom(...) Xpp3Dom version is taken from Maven core classloader as exported: see [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] Xpp3DomUtils is taken from current plugin classloader with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils is a recent version (>= 3.2.0) that expects to merge the input location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] but older Maven core versions don't have this input location field in Xpp3Dom, since they provide older plexus-utils that was upgraded to add location tracking in MNG-6597 was: see MSITE-863 for context this is caused by Xpp3Dom class incompatibility with Xpp3DomUtils.mergeXpp3Dom(...) Xpp3Dom version is taken from Maven core classloader as exported: see [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] Xpp3DomUtils is taken from current plugin classloader then with recent maven-site-plugin, Xpp3DomUtils is a recent version that expects to merge the input location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] but older Maven core versions don't have this input location field in Xpp3Dom > NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.2 > --- > > Key: MSHARED-921 > URL: https://issues.apache.org/jira/browse/MSHARED-921 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-reporting-exec >Affects Versions: maven-reporting-exec-1.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: maven-reporting-exec-1.5 > > > see MSITE-863 for context > > this is caused by Xpp3Dom class incompatibility with > Xpp3DomUtils.mergeXpp3Dom(...) > > Xpp3Dom version is taken from Maven core classloader as exported: see > [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] > Xpp3DomUtils is taken from current plugin classloader > > with recent upgrade of plexus-utils in maven-site-plugin 3.9.0, Xpp3DomUtils > is a recent version (>= 3.2.0) that expects to merge the input location (see > [https://github.com/codehaus-plexus/plexus-utils/issues/61)] > but older Maven core versions don't have this input location field in > Xpp3Dom, since they provide older plexus-utils that was upgraded to add > location tracking in MNG-6597 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MSHARED-921) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.2
Herve Boutemy created MSHARED-921: - Summary: NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.2 Key: MSHARED-921 URL: https://issues.apache.org/jira/browse/MSHARED-921 Project: Maven Shared Components Issue Type: Bug Components: maven-reporting-exec Affects Versions: maven-reporting-exec-1.4 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: maven-reporting-exec-1.5 see MSITE-863 for context this is caused by Xpp3Dom class incompatibility with Xpp3DomUtils.mergeXpp3Dom(...) Xpp3Dom version is taken from Maven core classloader as exported: see [http://maven.apache.org/ref/3.6.3/maven-core/core-extensions.html] Xpp3DomUtils is taken from current plugin classloader then with recent maven-site-plugin, Xpp3DomUtils is a recent version that expects to merge the input location (see [https://github.com/codehaus-plexus/plexus-utils/issues/61)] but older Maven core versions don't have this input location field in Xpp3Dom -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSITE-863) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running report
[
https://issues.apache.org/jira/browse/MSITE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-863:
Description:
[https://lists.apache.org/thread.html/rbba90de4703f8109b543500a5ee9e5b17b6a1258d95c6b5815b9257a%40%3Cdev.maven.apache.org%3E]
{noformat}
mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-plugin-plugin:3.6.0
[INFO] preparing maven-plugin-plugin:report report requires 'process-classes'
forked phase execution
[INFO]
[INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @mojo-parent >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @mojo-parent
---
[INFO]
[INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @mojo-parent <<<
[INFO] 'process-classes' forked phase execution for maven-plugin-plugin:report
report preparation done
[INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-changes-plugin:2.11
[INFO] 1 report configured for maven-changes-plugin:2.11: github-report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-checkstyle-plugin:2.16
[INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
[INFO] configuring report plugin
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.144 s
[INFO] Finished at: 2020-05-24T11:50:11+02:00
[INFO] Final Memory: 30M/128M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on project
mojo-parent: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.9.0:site:java.lang.NoSuchMethodError:
'java.lang.Object org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar{noformat}
This can be reproduced with 3.0.5 up to 3.6.1.
Versions 3.6.2 and 3.6.3 are working fine.
This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
...in contradiction to the site[1] which says it is requirement 3.0..
was:
https://lists.apache.org/thread.html/rbba90de4703f8109b543500a5ee9e5b17b6a1258d95c6b5815b9257a%40%3Cdev.maven.apache.org%3E
{noformat}mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-plugin-plugin:3.6.0
[INFO] preparing maven-plugin-plugin:report report requires
'process-classes' forked phase execution
[INFO]
[INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
mojo-parent >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
mojo-parent ---
[INFO]
[INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
mojo-parent <<<
[INFO] 'process-classes' forked phase execution for
maven-plugin-plugin:report report preparation done
[INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-changes-plugin:2.11
[INFO] 1 report configured for maven-changes-plugin:2.11: github-report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-checkstyle-plugin:2.16
[INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
[INFO] configuring report plugin
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.144 s
[INFO] Finished at: 2020-05-24T11:50:11+02:00
[INFO] Final Memory: 30M/128M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
project mojo-parent: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
java.lang.NoSuchMethodError: 'java.lang.Object
org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
[ERROR]
[jira] [Created] (MSITE-863) NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when running report
Herve Boutemy created MSITE-863:
---
Summary: NoSuchMethodError: 'Xpp3Dom.getInputLocation()' when
running report
Key: MSITE-863
URL: https://issues.apache.org/jira/browse/MSITE-863
Project: Maven Site Plugin
Issue Type: Bug
Components: Maven 3
Affects Versions: 3.9.0
Reporter: Herve Boutemy
Assignee: Herve Boutemy
Fix For: 3.9.1
https://lists.apache.org/thread.html/rbba90de4703f8109b543500a5ee9e5b17b6a1258d95c6b5815b9257a%40%3Cdev.maven.apache.org%3E
{noformat}mojo-parent (issue-105)$ mvn site site:stage
..
[INFO]
[INFO] --- maven-site-plugin:3.9.0:site (default-site) @ mojo-parent ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-plugin-plugin:3.6.0
[INFO] preparing maven-plugin-plugin:report report requires
'process-classes' forked phase execution
[INFO]
[INFO] >>> maven-plugin-plugin:3.6.0:report > process-classes @
mojo-parent >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.4:enforce (mojo-enforcer-rules) @
mojo-parent ---
[INFO]
[INFO] <<< maven-plugin-plugin:3.6.0:report < process-classes @
mojo-parent <<<
[INFO] 'process-classes' forked phase execution for
maven-plugin-plugin:report report preparation done
[INFO] 1 report detected for maven-plugin-plugin:3.6.0: report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-changes-plugin:2.11
[INFO] 1 report configured for maven-changes-plugin:2.11: github-report
[INFO] configuring report plugin
org.apache.maven.plugins:maven-checkstyle-plugin:2.16
[INFO] 1 report configured for maven-checkstyle-plugin:2.16: checkstyle
[INFO] configuring report plugin
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.144 s
[INFO] Finished at: 2020-05-24T11:50:11+02:00
[INFO] Final Memory: 30M/128M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site (default-site) on
project mojo-parent: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.9.0:site failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.9.0:site:
java.lang.NoSuchMethodError: 'java.lang.Object
org.codehaus.plexus.util.xml.Xpp3Dom.getInputLocation()'
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.9.0
[ERROR] strategy =
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/khmarbaise/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.9.0/maven-site-plugin-3.9.0.jar{noformat}
This can be reproduced with 3.0.5 up to 3.6.1.
Versions 3.6.2 and 3.6.3 are working fine.
This means using maven-site-plugin 3.9.0 only working with Maven 3.6.2+
...in contradiction to the site[1] which says it is requirement 3.0..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MSITE-862) log Doxia source when rendering with site:run
[ https://issues.apache.org/jira/browse/MSITE-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-862. --- Resolution: Fixed done in https://github.com/apache/maven-site-plugin/commit/bb0f9c5044d168f7729a5b244e34f837c748b89c/ > log Doxia source when rendering with site:run > - > > Key: MSITE-862 > URL: https://issues.apache.org/jira/browse/MSITE-862 > Project: Maven Site Plugin > Issue Type: Improvement > Components: site:run >Affects Versions: 3.9.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.1 > > > logging source rendered during site:run can be useful to see the work done > behind the scene -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MSITE-862) log Doxia source when rendering with site:run
[ https://issues.apache.org/jira/browse/MSITE-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127734#comment-17127734 ] Hudson commented on MSITE-862: -- Build failed in Jenkins: Maven TLP » maven-site-plugin » master #106 See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/106/ > log Doxia source when rendering with site:run > - > > Key: MSITE-862 > URL: https://issues.apache.org/jira/browse/MSITE-862 > Project: Maven Site Plugin > Issue Type: Improvement > Components: site:run >Affects Versions: 3.9.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.9.1 > > > logging source rendered during site:run can be useful to see the work done > behind the scene -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MSITE-862) log Doxia source when rendering with site:run
Herve Boutemy created MSITE-862: --- Summary: log Doxia source when rendering with site:run Key: MSITE-862 URL: https://issues.apache.org/jira/browse/MSITE-862 Project: Maven Site Plugin Issue Type: Improvement Components: site:run Affects Versions: 3.9.0 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 3.9.1 logging source rendered during site:run can be useful to see the work done behind the scene -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-script-interpreter] slawekjaranowski opened a new pull request #6: [MSHARED-914] Detailed message from failed script shouldn't be propagated
slawekjaranowski opened a new pull request #6: URL: https://github.com/apache/maven-script-interpreter/pull/6 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127705#comment-17127705 ] Robert Scholte commented on MNGSITE-413: Let me assign the ticket to myself, so people can ask me for the status. And when there's something to share, I'll put it on the dev mailing list. This ticket is here, so we have something to refer to. > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MNGSITE-413: -- Assignee: Robert Scholte > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Assignee: Robert Scholte >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127701#comment-17127701 ] Amelia Eiras edited comment on MNGSITE-413 at 6/7/20, 4:09 PM: --- Hola everyone屢, currently the document is only documenting the past. It was written by Robert, who is the one who can export it to pdf to this ticket. thus far, I haven given view access to anyone who request access. the website ticket is here as a tracing of what we aim to achieve before 2020 is completed. We aim at working with the Maven community in Q42020 to bring Maven a website that is fully OSS. ☀️淋 was (Author: aeiras): Hola everyone屢, currently the document is only documenting the past. It was written by Robert, who is the one who can export it to pdf to this ticket. thus far, I give view access to anyone who request access. the website ticket is here as a tracing of what we aim to achieve before 2020 is completed. We aim at working with the Maven community in Q42020 to bring Maven a website that is fully OSS. ☀️淋 > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127701#comment-17127701 ] Amelia Eiras commented on MNGSITE-413: -- Hola everything 屢, currently the document is only documenting the past. It was written by Robert, who is the one who can export it to pdf to this ticket. thus far, I give view access to anyone who request access. the website ticket is here as a tracing of what we aim to achieve before 2020 is completed. We aim at working with the Maven community in Q42020 to bring Maven a website that is fully OSS. ☀️淋 > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127701#comment-17127701 ] Amelia Eiras edited comment on MNGSITE-413 at 6/7/20, 4:08 PM: --- Hola everyone屢, currently the document is only documenting the past. It was written by Robert, who is the one who can export it to pdf to this ticket. thus far, I give view access to anyone who request access. the website ticket is here as a tracing of what we aim to achieve before 2020 is completed. We aim at working with the Maven community in Q42020 to bring Maven a website that is fully OSS. ☀️淋 was (Author: aeiras): Hola everything 屢, currently the document is only documenting the past. It was written by Robert, who is the one who can export it to pdf to this ticket. thus far, I give view access to anyone who request access. the website ticket is here as a tracing of what we aim to achieve before 2020 is completed. We aim at working with the Maven community in Q42020 to bring Maven a website that is fully OSS. ☀️淋 > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MSHARED-53) Maven2OsgiConverter can leak JarFiles
[ https://issues.apache.org/jira/browse/MSHARED-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSHARED-53. --- Resolution: Abandoned > Maven2OsgiConverter can leak JarFiles > - > > Key: MSHARED-53 > URL: https://issues.apache.org/jira/browse/MSHARED-53 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-osgi (RETIRED) >Reporter: Stuart McCulloch >Priority: Minor > Attachments: MOD > > > The default Maven2OsgiConverter can leak JarFiles, because they are sometimes > opened but never closed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MEJB-112) JDK 9 WARNING in Integration Test
[
https://issues.apache.org/jira/browse/MEJB-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MEJB-112:
---
Fix Version/s: (was: 3.1.0)
more-investigation
> JDK 9 WARNING in Integration Test
> -
>
> Key: MEJB-112
> URL: https://issues.apache.org/jira/browse/MEJB-112
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: more-investigation
>
>
> Currently running on JDK 9 (EA+181) give the following warning during running
> via {{mvn -Prun-its clean verify}}:
> {code}
> [INFO] ..SUCCESS (3.8 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass$3$1
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy/2.0.1/groovy-2.0.1.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass$3$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] ..SUCCESS (4.1 s)
> [INFO] Building: reactor/pom.xml
> [INFO] run script verify.bsh
> [INFO] ..SUCCESS (3.4 s)
> {code}
> Upgrading to maven-invoker-plugin:3.0.1:
> {code}
> [INFO] run post-build script verify.bsh
> [INFO] MEJB-72/pom.xml .. SUCCESS
> (3.7 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run post-build script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy-all/2.4.8/groovy-all-2.4.8.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] mejb-93/pom.xml .. SUCCESS
> (4.1 s)
> [INFO] Building: reactor/pom.xml
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6930) Cannot use lambda as argument in a method in Mojo
[
https://issues.apache.org/jira/browse/MNG-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127698#comment-17127698
]
Abel Salgado Romero commented on MNG-6930:
--
Forgot to come back, I got confused with some other errors and just today saw
the problem was in `plexus-component-metadata`, v1.7 already fixed this.
If I want to keep my plugin Java8 compatible are the latest versions safe?
> Cannot use lambda as argument in a method in Mojo
> -
>
> Key: MNG-6930
> URL: https://issues.apache.org/jira/browse/MNG-6930
> Project: Maven
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.6.0
>Reporter: Abel Salgado Romero
>Priority: Major
>
> I have a plugin with uses a component that receives a lambda as argument.
> When passing any lamba, for example the following empty one
>
> {code:java}
>
> Optional sourceDir = new SourceDirectoryLocator(sourceDirectory,
> project.getBasedir(), file -> {})
> .find();
> {code}
>
> `maven-plugin-plugin` fails with the error:
>
> {code:java}
>
> [ERROR] Failed to execute goal
> org.codehaus.plexus:plexus-component-metadata:1.5.5:generate-metadata
> (default) on project asciidoctor-maven-plugin: Error generating metadata: :
> Failed to extract descriptors: Index 9578 out of bounds for length 999 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.plexus:plexus-component-metadata:1.5.5:generate-metadata
> (default) on project asciidoctor-maven-plugin: Error generating metadata:
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
>
> {code}
>
>
> Passing `null` or an anonymous class like shown below works however.
>
> {code:java}
>
> Optional sourceDir = new SourceDirectoryLocator(sourceDirectory,
> project.getBasedir(),
> new Consumer() {
> @Override
> public void accept(File file) {
> getLog().info("sourceDirectory " + file + " does not exist");
> }
> })
> .find();
>
> {code}
>
>
> Also tested with the current SNAPSHOT and the issue still happens
> Here is the code to reprodude:
> [https://github.com/abelsromero/asciidoctor-maven-plugin/tree/maven-plugin-plugin-lambda-issue]
> . Just run `mvn clean test-compile` to see the error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNG-6828) DependencyResolutionException breaks serialization
[ https://issues.apache.org/jira/browse/MNG-6828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6828: -- Fix Version/s: 3.7.0-candidate > DependencyResolutionException breaks serialization > -- > > Key: MNG-6828 > URL: https://issues.apache.org/jira/browse/MNG-6828 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.6.3 >Reporter: James R. Ratzlaff >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.7.0-candidate > > > In class > [DependencyResolutionException|https://github.com/apache/maven/blob/a2b800de32cdb9adc1e64a43a0fc32e3ba878103/maven-core/src/main/java/org/apache/maven/project/DependencyResolutionException.java] > , the field > "[result|https://github.com/apache/maven/blob/a2b800de32cdb9adc1e64a43a0fc32e3ba878103/maven-core/src/main/java/org/apache/maven/project/DependencyResolutionException.java#L29]; > is the non-serializable type DependencyResolution. This causes serialization > to fail (since its super class, Exception, is inherently Serializable). This > field should have [transient access similar to the > DependencyResolutionException in the > maven-resolver-api.|https://github.com/apache/maven-resolver/blob/2a1f4a134f7d7784f2a64bf58bddd2732bb599a4/maven-resolver-api/src/main/java/org/eclipse/aether/resolution/DependencyResolutionException.java#L31] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MNGSITE-403) Combine APT documentation
[ https://issues.apache.org/jira/browse/MNGSITE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127693#comment-17127693 ] Herve Boutemy edited comment on MNGSITE-403 at 6/7/20, 3:57 PM: notice that I just understood what you called "weird JavaScript is swapping content when the link is clicked": I did not get it was in the Jira issue description in fact, if you edit as "Text" instead of "Visual", you'll better see the link vs the text: I just updated the issue description to change your initial [https://maven.apache.org/doxia/references/apt-format.html|https://maven.apache.org/doxia/references/doxia-apt.html] to [https://maven.apache.org/doxia/references/doxia-apt.html] was (Author: hboutemy): notice that I just understood what you called "weird JavaScript is swapping content when the link is clicked": I did not get it was in the Jira issue in fact, if you edit as "Text" instead of "Visual", you'll better see the link vs the text: I just updated the issue description to change your initial [https://maven.apache.org/doxia/references/apt-format.html|https://maven.apache.org/doxia/references/doxia-apt.html] to [https://maven.apache.org/doxia/references/doxia-apt.html] > Combine APT documentation > - > > Key: MNGSITE-403 > URL: https://issues.apache.org/jira/browse/MNGSITE-403 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > merge [https://maven.apache.org/doxia/references/apt-format.html] and > [https://maven.apache.org/doxia/references/doxia-apt.html] > > We should document exactly the apt format we support, no more, no less. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-403) Combine APT documentation
[ https://issues.apache.org/jira/browse/MNGSITE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127693#comment-17127693 ] Herve Boutemy commented on MNGSITE-403: --- notice that I just understood what you called "weird JavaScript is swapping content when the link is clicked": I did not get it was in the Jira issue in fact, if you edit as "Text" instead of "Visual", you'll better see the link vs the text: I just updated the issue description to change your initial [https://maven.apache.org/doxia/references/apt-format.html|https://maven.apache.org/doxia/references/doxia-apt.html] to [https://maven.apache.org/doxia/references/doxia-apt.html] > Combine APT documentation > - > > Key: MNGSITE-403 > URL: https://issues.apache.org/jira/browse/MNGSITE-403 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > merge [https://maven.apache.org/doxia/references/apt-format.html] and > [https://maven.apache.org/doxia/references/doxia-apt.html] > > We should document exactly the apt format we support, no more, no less. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNGSITE-403) Combine APT documentation
[ https://issues.apache.org/jira/browse/MNGSITE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNGSITE-403: -- Description: merge [https://maven.apache.org/doxia/references/apt-format.html] and [https://maven.apache.org/doxia/references/doxia-apt.html] We should document exactly the apt format we support, no more, no less. was: merge [https://maven.apache.org/doxia/references/apt-format.html] and [https://maven.apache.org/doxia/references/apt-format.html|https://maven.apache.org/doxia/references/doxia-apt.html] We should document exactly the apt format we support, no more, no less. > Combine APT documentation > - > > Key: MNGSITE-403 > URL: https://issues.apache.org/jira/browse/MNGSITE-403 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > merge [https://maven.apache.org/doxia/references/apt-format.html] and > [https://maven.apache.org/doxia/references/doxia-apt.html] > > We should document exactly the apt format we support, no more, no less. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-403) Combine APT documentation
[ https://issues.apache.org/jira/browse/MNGSITE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127690#comment-17127690 ] Herve Boutemy commented on MNGSITE-403: --- you're probably right: nowadays, who knows the original APT format? :) I never really investigated history of APT and how the extension to the format would really better be integrated > Combine APT documentation > - > > Key: MNGSITE-403 > URL: https://issues.apache.org/jira/browse/MNGSITE-403 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > merge [https://maven.apache.org/doxia/references/apt-format.html] and > [https://maven.apache.org/doxia/references/apt-format.html|https://maven.apache.org/doxia/references/doxia-apt.html] > > We should document exactly the apt format we support, no more, no less. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-244) Upload SHA-512 to Staging Repository
[ https://issues.apache.org/jira/browse/MPOM-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MPOM-244: - Description: As now the ASF staging repository supports SHA2 hashes (https://issues.apache.org/jira/browse/INFRA-14923) they should be generated for - all attached artifacts and - deployed to the Staging repository was:The manual generation of SHA512 checksums introduced with MPOM-205 is no longer necessary as now the ASF staging repository will generate those automatically (https://issues.apache.org/jira/browse/INFRA-14923). > Upload SHA-512 to Staging Repository > > > Key: MPOM-244 > URL: https://issues.apache.org/jira/browse/MPOM-244 > Project: Maven POMs > Issue Type: Improvement >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Priority: Major > > As now the ASF staging repository supports SHA2 hashes > (https://issues.apache.org/jira/browse/INFRA-14923) they should be generated > for > - all attached artifacts and > - deployed to the Staging repository -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-244) Upload SHA-512 to Staging Repository
[ https://issues.apache.org/jira/browse/MPOM-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MPOM-244: - Summary: Upload SHA-512 to Staging Repository (was: Remove manual generation of SHA512 checksums) > Upload SHA-512 to Staging Repository > > > Key: MPOM-244 > URL: https://issues.apache.org/jira/browse/MPOM-244 > Project: Maven POMs > Issue Type: Improvement >Affects Versions: ASF-23 >Reporter: Konrad Windszus >Priority: Major > > The manual generation of SHA512 checksums introduced with MPOM-205 is no > longer necessary as now the ASF staging repository will generate those > automatically (https://issues.apache.org/jira/browse/INFRA-14923). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127688#comment-17127688 ] Herve Boutemy commented on MNGSITE-413: --- great, we can improve the issue: I already changed priority to Major, we'll see later regarding the document, I already have asked access, but you're right, having a public document would make sense: [~aeiras], please? > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNGSITE-413: -- Priority: Major (was: Critical) > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Major > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-403) Combine APT documentation
[ https://issues.apache.org/jira/browse/MNGSITE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127687#comment-17127687 ] Elliotte Rusty Harold commented on MNGSITE-403: --- yes, that's the one. > Combine APT documentation > - > > Key: MNGSITE-403 > URL: https://issues.apache.org/jira/browse/MNGSITE-403 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > merge [https://maven.apache.org/doxia/references/apt-format.html] and > [https://maven.apache.org/doxia/references/apt-format.html|https://maven.apache.org/doxia/references/doxia-apt.html] > > We should document exactly the apt format we support, no more, no less. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-403) Combine APT documentation
[ https://issues.apache.org/jira/browse/MNGSITE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127686#comment-17127686 ] Herve Boutemy commented on MNGSITE-403: --- you mean https://maven.apache.org/doxia/references/doxia-apt.html ? > Combine APT documentation > - > > Key: MNGSITE-403 > URL: https://issues.apache.org/jira/browse/MNGSITE-403 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > merge [https://maven.apache.org/doxia/references/apt-format.html] and > [https://maven.apache.org/doxia/references/apt-format.html|https://maven.apache.org/doxia/references/doxia-apt.html] > > We should document exactly the apt format we support, no more, no less. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNG-6907) endless loop in StringSearchModelInterpolator
[ https://issues.apache.org/jira/browse/MNG-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6907: -- Fix Version/s: 3.7.0-candidate > endless loop in StringSearchModelInterpolator > - > > Key: MNG-6907 > URL: https://issues.apache.org/jira/browse/MNG-6907 > Project: Maven > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.6.3 >Reporter: Michael Keppler >Priority: Major > Fix For: 3.7.0-candidate > > > I have some company confidential projects (therefore no reproduction pom), > which cause an endless loop when running > mvn versions:display-plugin-updates > The endless loop happens in > [StringSearchModelInterpolator.traverseObjectWithParents|https://github.com/apache/maven/blob/5397fb66e7ea45dd756cd48c18f7dc476e2a06a6/maven-model-builder/src/main/java/org/apache/maven/model/interpolation/StringSearchModelInterpolator.java#L176] > calling itself (which I can see by attaching a profiler to the process). > Please add a check for whether the superClass is identical to the class, > before entering the recursion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6915) Maven console output could be wider
[ https://issues.apache.org/jira/browse/MNG-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127683#comment-17127683 ] Sylwester Lachiewicz commented on MNG-6915: --- same problem with mvn help:help output > Maven console output could be wider > --- > > Key: MNG-6915 > URL: https://issues.apache.org/jira/browse/MNG-6915 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 3.6.3 > Environment: Apache Maven 3.6.3 > (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: C:\Java\apache-maven-3.6.3\bin\.. > Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program > Files\Java\jdk1.8.0_251\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" >Reporter: Gary D. Gregory >Priority: Minor > Attachments: 2020-05-22 18_14_44-Command Prompt.png > > > Maven console output could be wider, either generally or by asking the > console its width. For example, when we build Log4j 2 3.0.0-SNAPSHOT, we get > the non-aligned summary attached as a screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6921) Maven compile with properties ${artifactId} and ${project.build.finalName} occurs java.lang.NullPointerException
[
https://issues.apache.org/jira/browse/MNG-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127682#comment-17127682
]
Sylwester Lachiewicz commented on MNG-6921:
---
It should be fixed with MNG-6819, can you check?
> Maven compile with properties ${artifactId} and ${project.build.finalName}
> occurs java.lang.NullPointerException
>
>
> Key: MNG-6921
> URL: https://issues.apache.org/jira/browse/MNG-6921
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.2, 3.6.3
> Environment: MacOS 10.15.2
>Reporter: anruence
>Priority: Major
> Labels: NPE
> Fix For: 3.7.0
>
> Attachments: maven-demo.zip
>
>
> with maven 3.3.9，this project with command "mvn compile" can process
> normally，but NPE when change to 3.6.3
> after debug :
> ${artifactId} and ${project.build.finalName} define at same time will cause
> InterpolationCycleException
> PS: ${project.build.finalName} will be parse to
> ${project.artifactId}-${project.version} with default config.
> this problem can replay with attach project
> {code:java}
> Caused by: java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap$MapEntry.setValue
> (ConcurrentHashMap.java:3539)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:1429)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:1027)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:170)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator.interpolateModel
> (StringVisitorModelInterpolator.java:107)
> at org.apache.maven.model.building.DefaultModelBuilder.interpolateModel
> (DefaultModelBuilder.java:789)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:393)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:448)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:414)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:558)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:414)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:377)
> at org.apache.maven.graph.DefaultGraphBuilder.collectProjects
> (DefaultGraphBuilder.java:414)
> at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
> (DefaultGraphBuilder.java:405)
> at org.apache.maven.graph.DefaultGraphBuilder.build
> (DefaultGraphBuilder.java:82)
> at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (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:62)
> 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){code}
>
> pom.xml
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>
> com.example
> maven-demo
> 0.0.1-SNAPSHOT
>
> 0.0.1-SNAPSHOT
> maven-demo-api
> Demo project for Maven
> jar
>
> com.example
> maven-demo-api
> maven-demo-api
> ${project.build.finalName}
>
> ${artifactId}
>
>
>
> org.springframework.boot
> spring-boot-maven-plugin
>
[jira] [Updated] (MNG-6921) Maven compile with properties ${artifactId} and ${project.build.finalName} occurs java.lang.NullPointerException
[
https://issues.apache.org/jira/browse/MNG-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MNG-6921:
--
Fix Version/s: 3.7.0
> Maven compile with properties ${artifactId} and ${project.build.finalName}
> occurs java.lang.NullPointerException
>
>
> Key: MNG-6921
> URL: https://issues.apache.org/jira/browse/MNG-6921
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.6.2, 3.6.3
> Environment: MacOS 10.15.2
>Reporter: anruence
>Priority: Major
> Labels: NPE
> Fix For: 3.7.0
>
> Attachments: maven-demo.zip
>
>
> with maven 3.3.9，this project with command "mvn compile" can process
> normally，but NPE when change to 3.6.3
> after debug :
> ${artifactId} and ${project.build.finalName} define at same time will cause
> InterpolationCycleException
> PS: ${project.build.finalName} will be parse to
> ${project.artifactId}-${project.version} with default config.
> this problem can replay with attach project
> {code:java}
> Caused by: java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap$MapEntry.setValue
> (ConcurrentHashMap.java:3539)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:1429)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:1027)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator$ModelVisitor.visit
> (StringVisitorModelInterpolator.java:170)
> at
> org.apache.maven.model.interpolation.StringVisitorModelInterpolator.interpolateModel
> (StringVisitorModelInterpolator.java:107)
> at org.apache.maven.model.building.DefaultModelBuilder.interpolateModel
> (DefaultModelBuilder.java:789)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:393)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:448)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:414)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:558)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:414)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:377)
> at org.apache.maven.graph.DefaultGraphBuilder.collectProjects
> (DefaultGraphBuilder.java:414)
> at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
> (DefaultGraphBuilder.java:405)
> at org.apache.maven.graph.DefaultGraphBuilder.build
> (DefaultGraphBuilder.java:82)
> at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (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:62)
> 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){code}
>
> pom.xml
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> https://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>
> com.example
> maven-demo
> 0.0.1-SNAPSHOT
>
> 0.0.1-SNAPSHOT
> maven-demo-api
> Demo project for Maven
> jar
>
> com.example
> maven-demo-api
> maven-demo-api
> ${project.build.finalName}
>
> ${artifactId}
>
>
>
> org.springframework.boot
> spring-boot-maven-plugin
>
>
> org.apache.maven.plugins
>
[jira] [Commented] (MNG-6930) Cannot use lambda as argument in a method in Mojo
[
https://issues.apache.org/jira/browse/MNG-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127681#comment-17127681
]
Sylwester Lachiewicz commented on MNG-6930:
---
Can you try to upgrade to a newer version like 2.1.0 ?
> Cannot use lambda as argument in a method in Mojo
> -
>
> Key: MNG-6930
> URL: https://issues.apache.org/jira/browse/MNG-6930
> Project: Maven
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.6.0
>Reporter: Abel Salgado Romero
>Priority: Major
>
> I have a plugin with uses a component that receives a lambda as argument.
> When passing any lamba, for example the following empty one
>
> {code:java}
>
> Optional sourceDir = new SourceDirectoryLocator(sourceDirectory,
> project.getBasedir(), file -> {})
> .find();
> {code}
>
> `maven-plugin-plugin` fails with the error:
>
> {code:java}
>
> [ERROR] Failed to execute goal
> org.codehaus.plexus:plexus-component-metadata:1.5.5:generate-metadata
> (default) on project asciidoctor-maven-plugin: Error generating metadata: :
> Failed to extract descriptors: Index 9578 out of bounds for length 999 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.plexus:plexus-component-metadata:1.5.5:generate-metadata
> (default) on project asciidoctor-maven-plugin: Error generating metadata:
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
>
> {code}
>
>
> Passing `null` or an anonymous class like shown below works however.
>
> {code:java}
>
> Optional sourceDir = new SourceDirectoryLocator(sourceDirectory,
> project.getBasedir(),
> new Consumer() {
> @Override
> public void accept(File file) {
> getLog().info("sourceDirectory " + file + " does not exist");
> }
> })
> .find();
>
> {code}
>
>
> Also tested with the current SNAPSHOT and the issue still happens
> Here is the code to reprodude:
> [https://github.com/abelsromero/asciidoctor-maven-plugin/tree/maven-plugin-plugin-lambda-issue]
> . Just run `mvn clean test-compile` to see the error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNG-6512) Checking possibility to require Java 11 to run Maven
[ https://issues.apache.org/jira/browse/MNG-6512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6512: -- Fix Version/s: (was: 3.7.0-candidate) > Checking possibility to require Java 11 to run Maven > > > Key: MNG-6512 > URL: https://issues.apache.org/jira/browse/MNG-6512 > Project: Maven > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > > Based on Maven Core - verify code and plugins how they work with classes > compiled for only Java 11+. > MNG-3699 Require Java 8 - now works fine and pass all tests, also in MNG-6481 > we verified that Maven can be compiled and pass ITs with Java 11. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNG-6512) Checking possibility to require Java 11 to run Maven
[ https://issues.apache.org/jira/browse/MNG-6512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MNG-6512. - Resolution: Fixed > Checking possibility to require Java 11 to run Maven > > > Key: MNG-6512 > URL: https://issues.apache.org/jira/browse/MNG-6512 > Project: Maven > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > > Based on Maven Core - verify code and plugins how they work with classes > compiled for only Java 11+. > MNG-3699 Require Java 8 - now works fine and pass all tests, also in MNG-6481 > we verified that Maven can be compiled and pass ITs with Java 11. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-394) Link for Jenkins introduction should be updated to jenkins.io
[ https://issues.apache.org/jira/browse/MPIR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127678#comment-17127678 ] Hudson commented on MPIR-394: - Build failed in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #118 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/118/ > Link for Jenkins introduction should be updated to jenkins.io > - > > Key: MPIR-394 > URL: https://issues.apache.org/jira/browse/MPIR-394 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: ci-management >Reporter: Erik Brangs >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.1.1 > > > The link for Jenkins currently uses https://jenkins-ci.org . The link still > works but sends a 301 redirect. The current link is https://www.jenkins.io . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPIR-395) Add TeamCity as a possibility for ciManagement entry
[ https://issues.apache.org/jira/browse/MPIR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-395: -- Labels: up-for-grabs (was: ) > Add TeamCity as a possibility for ciManagement entry > > > Key: MPIR-395 > URL: https://issues.apache.org/jira/browse/MPIR-395 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature > Components: ci-management >Reporter: Erik Brangs >Priority: Trivial > Labels: up-for-grabs > > The ciManagement entry doesn't support TeamCity. TeamCity ( > [https://teamcity.com/] ) is a CI server by JetBrains. Could support for it > be added? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-395) Add TeamCity as a possibility for ciManagement entry
[ https://issues.apache.org/jira/browse/MPIR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127677#comment-17127677 ] Sylwester Lachiewicz commented on MPIR-395: --- We need to change here: [https://github.com/apache/maven-project-info-reports-plugin/blob/master/src/main/java/org/apache/maven/report/projectinfo/CiManagementReport.java#L129] and add to all resource bundle [https://github.com/apache/maven-project-info-reports-plugin/tree/master/src/main/resources] > Add TeamCity as a possibility for ciManagement entry > > > Key: MPIR-395 > URL: https://issues.apache.org/jira/browse/MPIR-395 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature > Components: ci-management >Reporter: Erik Brangs >Priority: Trivial > > The ciManagement entry doesn't support TeamCity. TeamCity ( > [https://teamcity.com/] ) is a CI server by JetBrains. Could support for it > be added? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MPIR-394) Link for Jenkins introduction should be updated to jenkins.io
[ https://issues.apache.org/jira/browse/MPIR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-394. - Resolution: Fixed > Link for Jenkins introduction should be updated to jenkins.io > - > > Key: MPIR-394 > URL: https://issues.apache.org/jira/browse/MPIR-394 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: ci-management >Reporter: Erik Brangs >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.1.1 > > > The link for Jenkins currently uses https://jenkins-ci.org . The link still > works but sends a 301 redirect. The current link is https://www.jenkins.io . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-394) Link for Jenkins introduction should be updated to jenkins.io
[ https://issues.apache.org/jira/browse/MPIR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127676#comment-17127676 ] Sylwester Lachiewicz commented on MPIR-394: --- Done in [7843b22bc4bb34837c6ed4ca41ebf266e8bdd7bd|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=7843b22bc4bb34837c6ed4ca41ebf266e8bdd7bd] > Link for Jenkins introduction should be updated to jenkins.io > - > > Key: MPIR-394 > URL: https://issues.apache.org/jira/browse/MPIR-394 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: ci-management >Reporter: Erik Brangs >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.1.1 > > > The link for Jenkins currently uses https://jenkins-ci.org . The link still > works but sends a 301 redirect. The current link is https://www.jenkins.io . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MPIR-394) Link for Jenkins introduction should be updated to jenkins.io
[ https://issues.apache.org/jira/browse/MPIR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPIR-394: - Assignee: Sylwester Lachiewicz > Link for Jenkins introduction should be updated to jenkins.io > - > > Key: MPIR-394 > URL: https://issues.apache.org/jira/browse/MPIR-394 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: ci-management >Reporter: Erik Brangs >Assignee: Sylwester Lachiewicz >Priority: Trivial > > The link for Jenkins currently uses https://jenkins-ci.org . The link still > works but sends a 301 redirect. The current link is https://www.jenkins.io . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPIR-394) Link for Jenkins introduction should be updated to jenkins.io
[ https://issues.apache.org/jira/browse/MPIR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-394: -- Fix Version/s: 3.1.1 > Link for Jenkins introduction should be updated to jenkins.io > - > > Key: MPIR-394 > URL: https://issues.apache.org/jira/browse/MPIR-394 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: ci-management >Reporter: Erik Brangs >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.1.1 > > > The link for Jenkins currently uses https://jenkins-ci.org . The link still > works but sends a 301 redirect. The current link is https://www.jenkins.io . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MPIR-393) MailiingListReport.getArchiveServer is weird
[ https://issues.apache.org/jira/browse/MPIR-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-393. - Resolution: Fixed > MailiingListReport.getArchiveServer is weird > > > Key: MPIR-393 > URL: https://issues.apache.org/jira/browse/MPIR-393 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.1 > > Time Spent: 10m > Remaining Estimate: 0h > > # Does a lot of work just to extract the host name from a URI. We can use the > URI class instead and probably be more reliable. > > 2. The test case pulls in an extra dependency from 2006 for accessing private > methods. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127672#comment-17127672 ] Elliotte Rusty Harold commented on MNGSITE-413: --- There's no actual issue here. It's not critical though marked as so. It links to a privte go0ogle doc we can't see. There's nothing to be done here. > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Critical > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MSHARED-920) NPE in DefaultArtifactInstaller.install - missing injection of RepositoryManager
[ https://issues.apache.org/jira/browse/MSHARED-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127670#comment-17127670 ] Hudson commented on MSHARED-920: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #106 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/106/ > NPE in DefaultArtifactInstaller.install - missing injection of > RepositoryManager > > > Key: MSHARED-920 > URL: https://issues.apache.org/jira/browse/MSHARED-920 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.12.0, > maven-artifact-transfer-0.13.0 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > > Add missing \@Requirement annotation > @Requirement > private RepositoryManager repositoryManager; > > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to install > artifact: org.apache.maven.plugins:maven-plugins:pom:34 > at org.apache.maven.plugins.invoker.InstallMojo.installArtifact > (InstallMojo.java:264) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom > (InstallMojo.java:410) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents > (InstallMojo.java:379) > at org.apache.maven.plugins.invoker.InstallMojo.execute > (InstallMojo.java:199) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:136) > > Caused by: java.lang.NullPointerException > at > org.apache.maven.shared.transfer.artifact.install.internal.DefaultArtifactInstaller.install > (DefaultArtifactInstaller.java:81) > at org.apache.maven.plugins.invoker.InstallMojo.installArtifact > (InstallMojo.java:254) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom > (InstallMojo.java:410) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents > (InstallMojo.java:379) > at org.apache.maven.plugins.invoker.InstallMojo.execute > (InstallMojo.java:199) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:136) > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MSHARED-920) NPE in DefaultArtifactInstaller.install - missing injection of RepositoryManager
[ https://issues.apache.org/jira/browse/MSHARED-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127668#comment-17127668 ] Sylwester Lachiewicz commented on MSHARED-920: -- Done in [87842f9c712eb6496b32d4aff09307d0970d9f7b|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commit;h=87842f9c712eb6496b32d4aff09307d0970d9f7b] > NPE in DefaultArtifactInstaller.install - missing injection of > RepositoryManager > > > Key: MSHARED-920 > URL: https://issues.apache.org/jira/browse/MSHARED-920 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.12.0, > maven-artifact-transfer-0.13.0 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > > Add missing \@Requirement annotation > @Requirement > private RepositoryManager repositoryManager; > > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to install > artifact: org.apache.maven.plugins:maven-plugins:pom:34 > at org.apache.maven.plugins.invoker.InstallMojo.installArtifact > (InstallMojo.java:264) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom > (InstallMojo.java:410) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents > (InstallMojo.java:379) > at org.apache.maven.plugins.invoker.InstallMojo.execute > (InstallMojo.java:199) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:136) > > Caused by: java.lang.NullPointerException > at > org.apache.maven.shared.transfer.artifact.install.internal.DefaultArtifactInstaller.install > (DefaultArtifactInstaller.java:81) > at org.apache.maven.plugins.invoker.InstallMojo.installArtifact > (InstallMojo.java:254) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom > (InstallMojo.java:410) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents > (InstallMojo.java:379) > at org.apache.maven.plugins.invoker.InstallMojo.execute > (InstallMojo.java:199) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:136) > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MSHARED-920) NPE in DefaultArtifactInstaller.install - missing injection of RepositoryManager
[ https://issues.apache.org/jira/browse/MSHARED-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MSHARED-920: Assignee: Sylwester Lachiewicz > NPE in DefaultArtifactInstaller.install - missing injection of > RepositoryManager > > > Key: MSHARED-920 > URL: https://issues.apache.org/jira/browse/MSHARED-920 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.12.0, > maven-artifact-transfer-0.13.0 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > > Add missing \@Requirement annotation > @Requirement > private RepositoryManager repositoryManager; > > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to install > artifact: org.apache.maven.plugins:maven-plugins:pom:34 > at org.apache.maven.plugins.invoker.InstallMojo.installArtifact > (InstallMojo.java:264) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom > (InstallMojo.java:410) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents > (InstallMojo.java:379) > at org.apache.maven.plugins.invoker.InstallMojo.execute > (InstallMojo.java:199) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:136) > > Caused by: java.lang.NullPointerException > at > org.apache.maven.shared.transfer.artifact.install.internal.DefaultArtifactInstaller.install > (DefaultArtifactInstaller.java:81) > at org.apache.maven.plugins.invoker.InstallMojo.installArtifact > (InstallMojo.java:254) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom > (InstallMojo.java:410) > at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents > (InstallMojo.java:379) > at org.apache.maven.plugins.invoker.InstallMojo.execute > (InstallMojo.java:199) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:136) > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127657#comment-17127657
]
Sylwester Lachiewicz commented on MPIR-374:
---
Done in
[3e139cdbafc944932407ae349da0c54fbf433e50|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=3e139cdbafc944932407ae349da0c54fbf433e50]
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0, 3.1.0
> Environment: Java 10
>Reporter: Peter Lamby
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.0.1, 3.1.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[GitHub] [maven-project-info-reports-plugin] slachiewicz commented on pull request #15: [MPIR-374] No logging of stacktrace in non debug mode
slachiewicz commented on pull request #15: URL: https://github.com/apache/maven-project-info-reports-plugin/pull/15#issuecomment-640224292 thx - meged in 3e139cdbafc944932407ae349da0c54fbf433e50 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MPIR-374.
-
Resolution: Fixed
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0, 3.1.0
> Environment: Java 10
>Reporter: Peter Lamby
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.1.1, 3.0.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
>
[jira] [Commented] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127653#comment-17127653
]
Hudson commented on MPIR-374:
-
Build failed in Jenkins: Maven TLP » maven-project-info-reports-plugin » master
#117
See
https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/117/
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0, 3.1.0
> Environment: Java 10
>Reporter: Peter Lamby
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.0.1, 3.1.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Assigned] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MPIR-374:
-
Assignee: Sylwester Lachiewicz
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0, 3.1.0
> Environment: Java 10
>Reporter: Peter Lamby
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.0.1, 3.1.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
>
[jira] [Updated] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MPIR-374:
--
Fix Version/s: 3.1.1
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0, 3.1.0
> Environment: Java 10
>Reporter: Peter Lamby
>Priority: Minor
> Fix For: 3.0.1, 3.1.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
>
[jira] [Updated] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MPIR-374:
--
Fix Version/s: (was: 3.1.0)
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0, 3.1.0
> Environment: Java 10
>Reporter: Peter Lamby
>Priority: Minor
> Fix For: 3.0.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
>
[jira] [Updated] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MPIR-374:
--
Affects Version/s: 3.1.0
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0, 3.1.0
> Environment: Java 10
>Reporter: Peter Lamby
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
>
[jira] [Created] (MSHARED-920) NPE in DefaultArtifactInstaller.install - missing injection of RepositoryManager
Sylwester Lachiewicz created MSHARED-920: Summary: NPE in DefaultArtifactInstaller.install - missing injection of RepositoryManager Key: MSHARED-920 URL: https://issues.apache.org/jira/browse/MSHARED-920 Project: Maven Shared Components Issue Type: Bug Components: maven-artifact-transfer Affects Versions: maven-artifact-transfer-0.12.0, maven-artifact-transfer-0.13.0 Reporter: Sylwester Lachiewicz Add missing \@Requirement annotation @Requirement private RepositoryManager repositoryManager; Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to install artifact: org.apache.maven.plugins:maven-plugins:pom:34 at org.apache.maven.plugins.invoker.InstallMojo.installArtifact (InstallMojo.java:264) at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom (InstallMojo.java:410) at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents (InstallMojo.java:379) at org.apache.maven.plugins.invoker.InstallMojo.execute (InstallMojo.java:199) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:136) Caused by: java.lang.NullPointerException at org.apache.maven.shared.transfer.artifact.install.internal.DefaultArtifactInstaller.install (DefaultArtifactInstaller.java:81) at org.apache.maven.plugins.invoker.InstallMojo.installArtifact (InstallMojo.java:254) at org.apache.maven.plugins.invoker.InstallMojo.installProjectPom (InstallMojo.java:410) at org.apache.maven.plugins.invoker.InstallMojo.installProjectParents (InstallMojo.java:379) at org.apache.maven.plugins.invoker.InstallMojo.execute (InstallMojo.java:199) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:136) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1733) Surefire and Failsafe JPMS additions for JUnit 5.x execution
[
https://issues.apache.org/jira/browse/SUREFIRE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127643#comment-17127643
]
Gili commented on SUREFIRE-1733:
{quote}No. Never tune your main code (module-info in src/main/java is just
that) to needs of your test code!
Your (example based) test code should be 1.) as close as possible to real code
using your main code and 2.) make sure your testing frameworks of choice work
with it.
{quote}
I agree, if and only if the developer is doing black box testing. It sounds
like the only point of contention is with respect to white box testing. In my
opinion, the main module may define qualified exports (e.g. exports secret to
tests) for white box testing. I assume you have a different approach in mind so
let's see if we can support it as well. What did you have in mind for white box
testing?
> Surefire and Failsafe JPMS additions for JUnit 5.x execution
>
>
> Key: SUREFIRE-1733
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1733
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.22.2, 3.0.0-M4
>Reporter: John Patrick
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 3.0.0-M5
>
> Attachments: surefire-v2.22.2_junit-v5.5.2.txt,
> surefire-v2.22.2_junit-v5.6.0-M1.txt, surefire-v3.0.0-M4_junit-v5.5.2.txt,
> surefire-v3.0.0-M4_junit-v5.6.0-M1.txt
>
>
> Following on from SUREFIRE-1731 it was highlighted that some projects need
> extra '--add-open' options for JUnit to execute correctly, lots have already
> been handled or added or supported in previous releases but I'm needing to
> add these for a project to run correctly.
> I'm happy to start looking at a patch, but need help with where repo or class
> to start looking at.
> This is what extra arguments I'm needing to pass to surefire/failsafe.
> {code}
> --add-opens
> ${project.Automatic-Module-Name}/${project.Automatic-Module-Name}=ALL-UNNAMED
> --add-opens
> ${project.Automatic-Module-Name}/${project.Automatic-Module-Name}=org.junit.platform.commons
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
> {code}
> Luckly my module names and package names are all on the same standard and
> I've got a maven property for each sub module defining what
> 'project.Automatic-Module-Name' is.
> The 2nd two are probably easy and will work for everyone, the 1st two might
> require some discussion and maybe define two variables that surefire and
> failsafe can use, one for the module name and one for the package name if
> they can dynamically scan the source code and work it out.
> This is the stacktrace I'm seeing;
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
> project PROJECT: There are test failures.
> [ERROR]
> [ERROR] Please refer to PATH/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date].dump,
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] java.lang.IllegalAccessError: class
> org.junit.platform.launcher.core.LauncherFactory (in unnamed module
> @0x6eceb130) cannot access class
> org.junit.platform.commons.util.Preconditions (in module
> org.junit.platform.commons) because module org.junit.platform.commons does
> not export org.junit.platform.commons.util to unnamed module @0x6eceb130
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR] java.lang.IllegalAccessError: class
> org.junit.platform.launcher.core.LauncherFactory (in unnamed module
> @0x6eceb130) cannot access class
> org.junit.platform.commons.util.Preconditions (in module
> org.junit.platform.commons) because module org.junit.platform.commons does
> not export org.junit.platform.commons.util to unnamed module @0x6eceb130
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:656)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
> [ERROR] at
>
[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=17127641#comment-17127641
]
Hudson commented on MNG-5868:
-
Build unstable in Jenkins: Maven TLP » maven » MNG-6656 #70
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6656/70/
> 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.7.0-candidate
>
>
> 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-5937) Maven-Wrapper for unified project environments (analog the Gradle wrapper)
[ https://issues.apache.org/jira/browse/MNG-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127642#comment-17127642 ] Hudson commented on MNG-5937: - Build unstable in Jenkins: Maven TLP » maven » MNG-6656 #70 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6656/70/ > Maven-Wrapper for unified project environments (analog the Gradle wrapper) > -- > > Key: MNG-5937 > URL: https://issues.apache.org/jira/browse/MNG-5937 > Project: Maven > Issue Type: Improvement > Components: Command Line >Reporter: Robert Weiser >Assignee: Robert Scholte >Priority: Major > Fix For: 3.7.0 > > > It would be nice to provide a wrapper for maven which behaves similarily to > the wrapper Gradle has. This would allow projects to share Maven in a certain > version along with some project-specific Maven options like for example the > location of the user or the global settings files or the maximum java heap > size to use. > There already are projects on github (e.g.: > https://github.com/takari/maven-wrapper) providing said feature, however it > would be nice to have it developed and maintained by the very people > providing us with the offical Maven release. > Cheers, Robert -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRESOLVER-114) ArtifactNotFoundExceptions when building in parallel
[
https://issues.apache.org/jira/browse/MRESOLVER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127640#comment-17127640
]
Michael Osipov commented on MRESOLVER-114:
--
bq. It might be a symptom fix. I'm trying to understand it again, but by
reading code I'm unable to see how Thread A is affected by Thread B at all (but
obviously it is).
Same here.
bq. Unfortunately I wasn't able to reproduce it often enough on my machine to
debug, so I can only say, the resolve method has race conditions that we cannot
observe after applying one of the two provided patches anymore.
I assume that you can't provide a stripped down project to reproduce issue on
my machine?
bq. If you understand where the concurrency and shared state is hiding, please
give me a pointer.
Unfortunately, I haven't yet found a possible spot for race conditions. I am
inclined to merge PR #41 for now since we don't understand the cause.
> ArtifactNotFoundExceptions when building in parallel
>
>
> Key: MRESOLVER-114
> URL: https://issues.apache.org/jira/browse/MRESOLVER-114
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Affects Versions: 1.4.2
>Reporter: Rainer Reich
>Priority: Major
> Attachments: maven-debug-log.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have a multi-module project with quite many modules and many dependencies
> and observe pretty random {{ArtifactNotFoundExceptions}} when building in
> parallel with an empty local repository.
> The "funny" thing is that Maven did in fact download the jar that it
> complained about not finding.
> In this example Maven said it could not find
> {{edu.tum.cs:cup-runtime:jar:11a}} (see stacktrace below)
> But it also said: {{Downloaded from central-mirror:
> [https://mirror.xy.com/repository/maven-all-mirror/edu/tum/cs/cup-runtime/11a/cup-runtime-11a.jar]}}.
> When looking into the local repository after the failed build we found the
> cup-runtime.jar in the correct place with the correct checksum.
> We tried the following to "fix" the problem:
> * build with and without the takari extensions ({{takari-local-repository}}
> & {{takari-smart-builder}}) using {{--builder smart}}
> * also build with {{io.takari.aether:aether-connector-okhttp}} extension
> * only execute goal package instead of install
> * build with these properties: {{-Daether.connector.basic.threads=1
> -Daether.connector.resumeDownloads=false}}
> But nothing helped.
> Unfortunately it seems to be a race condition and we cannot reproduce it
> consistently but it happens in about 1 out of 5 builds.
> {code:java}
> ...
> [2019-11-18T16:46:29.370Z] [INFO] Downloaded from central-mirror:
> https://mirror.xy.com/repository/maven-all-mirror/edu/tum/cs/cup-runtime/11a/cup-runtime-11a.jar
> (13 kB at 738 kB/s)
> ...
> [2019-11-18T16:46:30.894Z] [ERROR] Failed to execute goal on project xy:
> Could not resolve dependencies for project xy: The following artifacts could
> not be resolved: edu.tum.cs:cup-runtime:jar:11a,
> org.checkerframework:checker-qual:jar:2.5.7, org.ow2.asm:asm:jar:7.2,
> cglib:cglib:jar:3.3.0: Could not find artifact edu.tum.cs:cup-runtime:jar:11a
> -> [Help 1]
> [2019-11-18T16:46:30.894Z]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project xy: Could not resolve dependencies for project xy: The
> following artifacts could not be resolved: edu.tum.cs:cup-runtime:jar:11a,
> org.checkerframework:checker-qual:jar:2.5.7, org.ow2.asm:asm:jar:7.2,
> cglib:cglib:jar:3.3.0: Could not find artifact edu.tum.cs:cup-runtime:jar:11a
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResolver.java:269)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
> (LifecycleDependencyResolver.java:147)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
> (MojoExecutor.java:248)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:202)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> [2019-11-18T16:46:30.894Z] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> [2019-11-18T16:46:30.894Z] at
> io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
> (SmartBuilderImpl.java:205)
> [2019-11-18T16:46:30.894Z] at
>
[jira] [Reopened] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MPIR-374:
-
Reopening as per request.
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0
> Environment: Java 10
>Reporter: Peter Lamby
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
>
[GitHub] [maven-project-info-reports-plugin] bmaehr opened a new pull request #15: [MPIR-374] No logging of stacktrace in non debug mode
bmaehr opened a new pull request #15: URL: https://github.com/apache/maven-project-info-reports-plugin/pull/15 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127627#comment-17127627
]
Bernhard Mähr edited comment on MPIR-374 at 6/7/20, 12:37 PM:
--
Not solved yet, my patch is not applied.
{code:java}
// [INFO] Generating "Dependency Management" report ---
maven-project-info-reports-plugin:3.1.0:dependency-management
[WARNING] Unable to create Maven project for
com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.11.0 from
repository.
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[ERROR] Unknown packaging: bundle @ line 6, column 16
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:205)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:340)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
(RepositoryUtils.java:125)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
(DependencyManagementRenderer.java:253)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
(DependencyManagementRenderer.java:202)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
(DependencyManagementRenderer.java:151)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
(DependencyManagementRenderer.java:144)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
(DependencyManagementRenderer.java:130)
at org.apache.maven.reporting.AbstractMavenReportRenderer.render
(AbstractMavenReportRenderer.java:80)
at
org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport
(DependencyManagementReport.java:108)
at org.apache.maven.reporting.AbstractMavenReport.generate
(AbstractMavenReport.java:251)
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:267)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:349)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:198)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:147)
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.jvnet.hudson.maven3.launcher.Maven35Launcher.main
(Maven35Launcher.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at jenkins.maven3.agent.Maven35Main.launch (Maven35Main.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at hudson.maven.Maven3Builder.call (Maven3Builder.java:139)
at hudson.maven.Maven3Builder.call (Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform (UserRequest.java:211)
at hudson.remoting.UserRequest.perform (UserRequest.java:54)
at hudson.remoting.Request$2.run (Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call
(InterceptingExecutorService.java:72)
at
[jira] [Comment Edited] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127627#comment-17127627
]
Bernhard Mähr edited comment on MPIR-374 at 6/7/20, 12:37 PM:
--
Not solved yet, my patch is not applied.
{code:java}
[INFO] Generating "Dependency Management" report ---
maven-project-info-reports-plugin:3.1.0:dependency-management
[WARNING] Unable to create Maven project for
com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.11.0 from
repository.
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[ERROR] Unknown packaging: bundle @ line 6, column 16
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:205)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:340)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
(RepositoryUtils.java:125)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
(DependencyManagementRenderer.java:253)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
(DependencyManagementRenderer.java:202)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
(DependencyManagementRenderer.java:151)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
(DependencyManagementRenderer.java:144)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
(DependencyManagementRenderer.java:130)
at org.apache.maven.reporting.AbstractMavenReportRenderer.render
(AbstractMavenReportRenderer.java:80)
at
org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport
(DependencyManagementReport.java:108)
at org.apache.maven.reporting.AbstractMavenReport.generate
(AbstractMavenReport.java:251)
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:267)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:349)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:198)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:147)
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.jvnet.hudson.maven3.launcher.Maven35Launcher.main
(Maven35Launcher.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at jenkins.maven3.agent.Maven35Main.launch (Maven35Main.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at hudson.maven.Maven3Builder.call (Maven3Builder.java:139)
at hudson.maven.Maven3Builder.call (Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform (UserRequest.java:211)
at hudson.remoting.UserRequest.perform (UserRequest.java:54)
at hudson.remoting.Request$2.run (Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call
(InterceptingExecutorService.java:72)
at
[jira] [Commented] (MPIR-374) Unknown packaging: bundle when creating report
[
https://issues.apache.org/jira/browse/MPIR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127627#comment-17127627
]
Bernhard Mähr commented on MPIR-374:
Not solved yet, my patch is not applied.
> Unknown packaging: bundle when creating report
> --
>
> Key: MPIR-374
> URL: https://issues.apache.org/jira/browse/MPIR-374
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 3.0.0
> Environment: Java 10
>Reporter: Peter Lamby
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After I upgraded the plugin to 3.0.0 I get the following errors:
> {noformat}
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.0.0:dependency-management
> [WARNING] Unable to create Maven project for
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] Unknown packaging: bundle @ line 6, column 16
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:192)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:253)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:202)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:151)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:144)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:130)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:80)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:107)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 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:956)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
>
[GitHub] [maven-project-info-reports-plugin] bmaehr commented on pull request #15: [MPIR-374] No logging of stacktrace in non debug mode
bmaehr commented on pull request #15: URL: https://github.com/apache/maven-project-info-reports-plugin/pull/15#issuecomment-640211793 As I expected, it is NOT solved yet. My patch solves it. ``` [INFO] Generating "Dependency Management" report --- maven-project-info-reports-plugin:3.1.0:dependency-management [WARNING] Unable to create Maven project for com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.11.0 from repository. org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [ERROR] Unknown packaging: bundle @ line 6, column 16 at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:205) at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:340) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository (RepositoryUtils.java:125) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow (DependencyManagementRenderer.java:253) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope (DependencyManagementRenderer.java:202) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes (DependencyManagementRenderer.java:151) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies (DependencyManagementRenderer.java:144) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody (DependencyManagementRenderer.java:130) at org.apache.maven.reporting.AbstractMavenReportRenderer.render (AbstractMavenReportRenderer.java:80) at org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport (DependencyManagementReport.java:108) at org.apache.maven.reporting.AbstractMavenReport.generate (AbstractMavenReport.java:251) at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument (ReportDocumentRenderer.java:267) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render (DefaultSiteRenderer.java:349) at org.apache.maven.plugins.site.render.SiteMojo.renderLocale (SiteMojo.java:198) at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:147) 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.jvnet.hudson.maven3.launcher.Maven35Launcher.main (Maven35Launcher.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at jenkins.maven3.agent.Maven35Main.launch (Maven35Main.java:178) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at hudson.maven.Maven3Builder.call (Maven3Builder.java:139) at hudson.maven.Maven3Builder.call (Maven3Builder.java:70) at hudson.remoting.UserRequest.perform (UserRequest.java:211) at hudson.remoting.UserRequest.perform (UserRequest.java:54) at hudson.remoting.Request$2.run (Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call
[GitHub] [maven-script-interpreter] slawekjaranowski opened a new pull request #5: [MSHARED-917] Remove dependency to plexus-component-annotations
slawekjaranowski opened a new pull request #5: URL: https://github.com/apache/maven-script-interpreter/pull/5 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Reopened] (MNGSITE-413) [CREATE] Maven Website (2020)
[ https://issues.apache.org/jira/browse/MNGSITE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy reopened MNGSITE-413: --- [~elharo] closing the issue is probably a little bit rude, isn't it? > [CREATE] Maven Website (2020) > -- > > Key: MNGSITE-413 > URL: https://issues.apache.org/jira/browse/MNGSITE-413 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Amelia Eiras >Priority: Critical > > Maven is such a formidable project that requires everyone: > users/coders/contributors alike to properly THANK this ecosystem. > As such, Tomitribe has happily volunteered to collaborate with the wonderful > MavenCommitters on the creation of the Maven website in 2020. > Documentation on requirements [HERE > |https://drive.google.com/drive/folders/1LZyHFJ4XD-mMkL8rcMnfoGj7GMhB0ZIJ?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-402) Issue Tracking Links for Maven shared components are 404
[ https://issues.apache.org/jira/browse/MNGSITE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127624#comment-17127624 ] Hudson commented on MNGSITE-402: Build succeeded in Jenkins: Maven TLP » maven-site » master #324 See https://builds.apache.org/job/maven-box/job/maven-site/job/master/324/ > Issue Tracking Links for Maven shared components are 404 > > > Key: MNGSITE-402 > URL: https://issues.apache.org/jira/browse/MNGSITE-402 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Herve Boutemy >Priority: Minor > > Rightmost column on https://maven.apache.org/shared/index.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNGSITE-402) Issue Tracking Links for Maven shared components are 404
[ https://issues.apache.org/jira/browse/MNGSITE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-402. - Assignee: Herve Boutemy Resolution: Fixed links updated > Issue Tracking Links for Maven shared components are 404 > > > Key: MNGSITE-402 > URL: https://issues.apache.org/jira/browse/MNGSITE-402 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Herve Boutemy >Priority: Minor > > Rightmost column on https://maven.apache.org/shared/index.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-402) Issue Tracking Links for Maven shared components are 404
[ https://issues.apache.org/jira/browse/MNGSITE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127613#comment-17127613 ] Hudson commented on MNGSITE-402: Build succeeded in Jenkins: Maven TLP » maven-site » master #323 See https://builds.apache.org/job/maven-box/job/maven-site/job/master/323/ > Issue Tracking Links for Maven shared components are 404 > > > Key: MNGSITE-402 > URL: https://issues.apache.org/jira/browse/MNGSITE-402 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > Rightmost column on https://maven.apache.org/shared/index.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
