[jira] [Commented] (MPOM-418) Cannot deploy snapshot - do I miss some config?
[
https://issues.apache.org/jira/browse/MPOM-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727332#comment-17727332
]
Herve Boutemy commented on MPOM-418:
[~tison] do you know if there is some documentation at Incubator level? how did
[~xuanwo] know that INFRA-24347 had to be done (and sadly concluded it was
finally not necessary)?
trying to figure out how to best link to existing documentation before writing
something additional that people won't find/read
> Cannot deploy snapshot - do I miss some config?
> ---
>
> Key: MPOM-418
> URL: https://issues.apache.org/jira/browse/MPOM-418
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Reporter: Zili Chen
>Priority: Major
>
> https://github.com/apache/incubator-opendal/pull/2301 Here is the branch I'm
> testing for deploying a snapshot Maven artifact.
> When I run it locally by `mvn -X -P apache-release clean deploy`, it fails in
> the uploading step with log:
> {noformat}
> [DEBUG] Using transporter HttpTransporter with priority 5.0 for
> https://repository.apache.org/content/repositories/snapshots
> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for
> https://repository.apache.org/content/repositories/snapshots with
> username=tison, password=***
> Downloading from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/maven-metadata.xml
> [DEBUG] Could not find metadata
> org.apache.opendal:opendal-java:0.1.0-SNAPSHOT/maven-metadata.xml in
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots)
> [DEBUG] Writing tracking file
> '/Users/chenzili/.m2/repository/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/resolver-status.properties'
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.jar
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.pom
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 50.971 s
> [INFO] Finished at: 2023-05-24T09:47:17+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project opendal-java: Failed to deploy artifacts: Could not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project opendal-java: Failed to deploy artifacts: Could
> not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:160)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute
[jira] [Updated] (MPOM-418) Cannot deploy snapshot - do I miss some config?
[
https://issues.apache.org/jira/browse/MPOM-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPOM-418:
---
Component/s: asf
(was: maven)
> Cannot deploy snapshot - do I miss some config?
> ---
>
> Key: MPOM-418
> URL: https://issues.apache.org/jira/browse/MPOM-418
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Reporter: Zili Chen
>Priority: Major
>
> https://github.com/apache/incubator-opendal/pull/2301 Here is the branch I'm
> testing for deploying a snapshot Maven artifact.
> When I run it locally by `mvn -X -P apache-release clean deploy`, it fails in
> the uploading step with log:
> {noformat}
> [DEBUG] Using transporter HttpTransporter with priority 5.0 for
> https://repository.apache.org/content/repositories/snapshots
> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for
> https://repository.apache.org/content/repositories/snapshots with
> username=tison, password=***
> Downloading from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/maven-metadata.xml
> [DEBUG] Could not find metadata
> org.apache.opendal:opendal-java:0.1.0-SNAPSHOT/maven-metadata.xml in
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots)
> [DEBUG] Writing tracking file
> '/Users/chenzili/.m2/repository/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/resolver-status.properties'
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.jar
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.pom
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 50.971 s
> [INFO] Finished at: 2023-05-24T09:47:17+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project opendal-java: Failed to deploy artifacts: Could not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project opendal-java: Failed to deploy artifacts: Could
> not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:160)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
>
[jira] [Commented] (MPOM-418) Cannot deploy snapshot - do I miss some config?
[
https://issues.apache.org/jira/browse/MPOM-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727331#comment-17727331
]
Herve Boutemy commented on MPOM-418:
documentation on repository.apache.org is really sparse
[https://infra.apache.org/services.html#code-dist]
discovering how to register a new staging area for a new project is not so easy
currently
> Cannot deploy snapshot - do I miss some config?
> ---
>
> Key: MPOM-418
> URL: https://issues.apache.org/jira/browse/MPOM-418
> Project: Maven POMs
> Issue Type: Improvement
> Components: maven
>Reporter: Zili Chen
>Priority: Major
>
> https://github.com/apache/incubator-opendal/pull/2301 Here is the branch I'm
> testing for deploying a snapshot Maven artifact.
> When I run it locally by `mvn -X -P apache-release clean deploy`, it fails in
> the uploading step with log:
> {noformat}
> [DEBUG] Using transporter HttpTransporter with priority 5.0 for
> https://repository.apache.org/content/repositories/snapshots
> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for
> https://repository.apache.org/content/repositories/snapshots with
> username=tison, password=***
> Downloading from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/maven-metadata.xml
> [DEBUG] Could not find metadata
> org.apache.opendal:opendal-java:0.1.0-SNAPSHOT/maven-metadata.xml in
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots)
> [DEBUG] Writing tracking file
> '/Users/chenzili/.m2/repository/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/resolver-status.properties'
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.jar
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.pom
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 50.971 s
> [INFO] Finished at: 2023-05-24T09:47:17+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project opendal-java: Failed to deploy artifacts: Could not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project opendal-java: Failed to deploy artifacts: Could
> not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:160)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at
[jira] [Closed] (SUREFIRE-2173) Update compiler source/target in integration tests to version 8
[ https://issues.apache.org/jira/browse/SUREFIRE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed SUREFIRE-2173. -- Resolution: Fixed > Update compiler source/target in integration tests to version 8 > --- > > Key: SUREFIRE-2173 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.2 > > > To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2173) Update compiler source/target in integration tests to version 8
[ https://issues.apache.org/jira/browse/SUREFIRE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727328#comment-17727328 ] ASF GitHub Bot commented on SUREFIRE-2173: -- slachiewicz merged PR #648: URL: https://github.com/apache/maven-surefire/pull/648 > Update compiler source/target in integration tests to version 8 > --- > > Key: SUREFIRE-2173 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.2 > > > To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-surefire] slachiewicz merged pull request #648: [SUREFIRE-2173] Pass build and tests with Java 20
slachiewicz merged PR #648: URL: https://github.com/apache/maven-surefire/pull/648 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727326#comment-17727326 ] Herve Boutemy commented on MPIR-445: more importantly: we don't care about UT output issue is definitively candidate to close > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > Reduce to debug or remove completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-surefire] elharo commented on pull request #654: Remove more details about Maven 2 and old versions
elharo commented on PR #654: URL: https://github.com/apache/maven-surefire/pull/654#issuecomment-1567584040 Looks like CI is being flaky: Run ./mvnw --errors --batch-mode --show-version -D"invoker.streamLogsOnFailures" clean install -nsu -P run-its Error: Exception in thread "main" java.net.SocketException: An established connection was aborted by the software in your host machine at java.base/sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:420) at java.base/sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:440) at java.base/sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:826) at java.base/java.net.Socket$SocketOutputStream.write(Socket.java:1035) at java.base/sun.security.ssl.SSLSocketOutputRecord.flush(SSLSocketOutputRecord.java:271) at java.base/sun.security.ssl.HandshakeOutStream.flush(HandshakeOutStream.java:89) at java.base/sun.security.ssl.Finished$T12FinishedProducer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MSHADE-445) Be smarter about non .class files
Elliotte Rusty Harold created MSHADE-445:
Summary: Be smarter about non .class files
Key: MSHADE-445
URL: https://issues.apache.org/jira/browse/MSHADE-445
Project: Maven Shade Plugin
Issue Type: Improvement
Reporter: Elliotte Rusty Harold
Building maven surefire plugin shows these warnings:
{{[WARNING] commons-compress-1.21.jar, commons-io-2.11.0.jar,
commons-lang3-3.12.0.jar define 2 overlapping resources:
[WARNING] - META-INF/LICENSE.txt
[WARNING] - META-INF/NOTICE.txt
[WARNING] maven-shared-utils-3.3.4.jar,
surefire-shared-utils-3.1.2-SNAPSHOT.jar define 3 overlapping resources:
[WARNING] - META-INF/DEPENDENCIES
[WARNING] - META-INF/LICENSE
[WARNING] - META-INF/NOTICE
[WARNING] commons-compress-1.21.jar, commons-io-2.11.0.jar,
commons-lang3-3.12.0.jar, maven-shared-utils-3.3.4.jar,
surefire-shared-utils-3.1.2-SNAPSHOT.jar define 1 overlapping resource:
[WARNING] - META-INF/MANIFEST.MF
[WARNING] maven-shade-plugin has detected that some class files are
[WARNING] present in two or more JARs. When this happens, only one
[WARNING] single version of the class is copied to the uber jar.
[WARNING] Usually this is not harmful and you can skip these warnings,
[WARNING] otherwise try to manually exclude artifacts based on
[WARNING] mvn dependency:tree -Ddetail=true and the above output.
[WARNING] See https://maven.apache.org/plugins/maven-shade-plugin/}}
This got me to thinking:
1. For LICENSES and NOTICES the files are likely byte-per-byte identical. Don't
warn in that case.
2. DEPENDENCIES and MANIFEST.MF should perhaps be rewritten and/or merged as
common special cases, rather than simply copied as is.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-surefire] michael-o opened a new pull request, #651: Simplify method
michael-o opened a new pull request, #651: URL: https://github.com/apache/maven-surefire/pull/651 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/SUREFIRE) 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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `SUREFIRE-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. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean install` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean install`). 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. - [ ] 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) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SUREFIRE-1442) report icons missing
[ https://issues.apache.org/jira/browse/SUREFIRE-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SUREFIRE-1442. Assignee: Michael Osipov (was: Tibor Digana) Resolution: Cannot Reproduce Cannot reproduce with 3.0.0 in site mode and standalone mode. > report icons missing > - > > Key: SUREFIRE-1442 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1442 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.20.1 > Environment: linux >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > > pom: > > org.apache.maven.plugins > maven-surefire-report-plugin > 2.20.1 > > > false > > > mvn surefire-report:report > Then in reports the icons which can be seen in the docs are missing. > I suspect, that in the docs one must add the information > how to add the icons. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-archiver] dependabot[bot] opened a new pull request, #35: Bump plexus-archiver from 4.4.0 to 4.7.1
dependabot[bot] opened a new pull request, #35: URL: https://github.com/apache/maven-archiver/pull/35 Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.4.0 to 4.7.1. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases;>plexus-archiver's releases. Plexus Archiver 4.7.1 Bug Fixes don't apply umask on unknown perms (Win) (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/273;>#273) https://github.com/hboutemy;>@hboutemy Plexus Archiver 4.7.0 New features and improvements add umask support and use 022 in RB mode (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/271;>#271) https://github.com/hboutemy;>@hboutemy Use NIO Files for creating temporary files (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/270;>#270) https://github.com/slawekjaranowski;>@slawekjaranowski Deprecate the JAR Index feature (JDK-8302819) (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/268;>#268) https://github.com/jorsol;>@jorsol Add Archiver aliases for tar.* (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/266;>#266) https://github.com/slawekjaranowski;>@slawekjaranowski Dependency updates Bump junitVersion from 5.9.2 to 5.9.3 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/267;>#267) https://github.com/dependabot;>@dependabot Bump zstd-jni from 1.5.5-1 to 1.5.5-2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/265;>#265) https://github.com/dependabot;>@dependabot Bump zstd-jni from 1.5.4-2 to 1.5.5-1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/263;>#263) https://github.com/dependabot;>@dependabot Bump commons-compress from 1.22 to 1.23.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/262;>#262) https://github.com/dependabot;>@dependabot Maintenance Use JUnit TempDir to manage temporary files in tests (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/269;>#269) https://github.com/slawekjaranowski;>@slawekjaranowski Override uId and gId for Tar in test (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/264;>#264) https://github.com/slawekjaranowski;>@slawekjaranowski Bump maven-resources-plugin from 2.7 to 3.3.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/223;>#223) https://github.com/dependabot;>@dependabot Plexus Archiver 4.6.3 New features and improvements Fix path traversal vulnerability (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/261;>#261) https://github.com/plamentotev;>@plamentotev Thanks to https://github.com/Fewword;>@Fewword for reporting the vulnerability and suggesting a fix. The vulnerability affects only directories whose name begins with the same prefix as the destination directory. For example malicious archive may extract file in /opt/directory instead of /opt/dir. Dependency updates Bump plexus-utils from 3.5.0 to 3.5.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/257;>#257) https://github.com/dependabot;>@dependabot Plexus Archiver 4.6.2 Bug Fixes Fix regression in handling symbolic links. See https://redirect.github.com/codehaus-plexus/plexus-io/issues/89;>codehaus-plexus/plexus-io#89 Dependency updates Bump plexus-io from 3.4.0 to 3.4.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/256;>#256) https://github.com/dependabot;>@dependabot Bump zstd-jni from 1.5.2-5 to 1.5.4-2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/254;>#254) https://github.com/dependabot;>@dependabot, (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/255;>#255) https://github.com/dependabot;>@dependabot Plexus Archiver 4.6.1 Bug Fixes ... (truncated) Commits https://github.com/codehaus-plexus/plexus-archiver/commit/e7cbadba1b5c78192677da95b355dd790f3a4535;>e7cbadb [maven-release-plugin] prepare release plexus-archiver-4.7.1 https://github.com/codehaus-plexus/plexus-archiver/commit/9e8faac956c98b3534328ba963ab7b3e75e03657;>9e8faac don't apply umask on unknown perms (Win) https://github.com/codehaus-plexus/plexus-archiver/commit/eded2d8d83d3783095448b4f191019ccc345b0d6;>eded2d8 [maven-release-plugin] prepare for next development iteration https://github.com/codehaus-plexus/plexus-archiver/commit/2de3b1605127090c948117bdc64745a8c3f98e00;>2de3b16 [maven-release-plugin] prepare release plexus-archiver-4.7.0 https://github.com/codehaus-plexus/plexus-archiver/commit/e3b02db232f773cf85cacbd9a0a49de23401c5af;>e3b02db add umask support and use 022 in RB mode https://github.com/codehaus-plexus/plexus-archiver/commit/53f6d2a73cd9ebad37b2e95da6436a3986d84fb8;>53f6d2a Use NIO Files for creating
[GitHub] [maven-surefire] dependabot[bot] opened a new pull request, #650: Bump jacocoVersion from 0.8.8 to 0.8.10
dependabot[bot] opened a new pull request, #650: URL: https://github.com/apache/maven-surefire/pull/650 Bumps `jacocoVersion` from 0.8.8 to 0.8.10. Updates `org.jacoco.agent` from 0.8.8 to 0.8.10 Release notes Sourced from https://github.com/jacoco/jacoco/releases;>org.jacoco.agent's releases. 0.8.10 Fixed bugs Agent should not require configuration of permissions for SecurityManager outside of its codeBase (GitHub https://redirect.github.com/jacoco/jacoco/issues/1425;>#1425). 0.8.9 New Features JaCoCo now officially supports Java 19 and 20 (GitHub https://redirect.github.com/jacoco/jacoco/issues/1371;>#1371, https://redirect.github.com/jacoco/jacoco/issues/1386;>#1386). Experimental support for Java 21 class files (GitHub https://redirect.github.com/jacoco/jacoco/issues/1386;>#1386). Add parameter to include the current project in the report-aggregate Maven goal (GitHub https://redirect.github.com/jacoco/jacoco/issues/1007;>#1007). Component accessors generated by the Java compilers for records are filtered out during generation of report. Contributed by Tesla Zhang (GitHub https://redirect.github.com/jacoco/jacoco/issues/1393;>#1393). Fixed bugs Agent should not open java.lang package to unnamed module of the application class loader (GitHub https://redirect.github.com/jacoco/jacoco/issues/1334;>#1334). Non-functional Changes JaCoCo now depends on ASM 9.5 (GitHub https://redirect.github.com/jacoco/jacoco/issues/1299;>#1299, https://redirect.github.com/jacoco/jacoco/issues/1368;>#1368, https://redirect.github.com/jacoco/jacoco/issues/1416;>#1416). JaCoCo build now requires JDK 11 (GitHub https://redirect.github.com/jacoco/jacoco/issues/1413;>#1413). Commits https://github.com/jacoco/jacoco/commit/8ea9668fa0272a6649e031f580c04ede04a7f17c;>8ea9668 Prepare release 0.8.10 https://github.com/jacoco/jacoco/commit/8f1daf972bc193ce0e10ef57000d112ccaaa4c7a;>8f1daf9 AgentModule should set ProtectionDomain when defining classes (https://redirect.github.com/jacoco/jacoco/issues/1425;>#1425) https://github.com/jacoco/jacoco/commit/31f16d834819526cf1e8ffbafed4b7e3fe5ed502;>31f16d8 Upgrade ECJ to 3.33.0 (https://redirect.github.com/jacoco/jacoco/issues/1423;>#1423) https://github.com/jacoco/jacoco/commit/3d58c42e6b80be9765a385afb44065f91ef48951;>3d58c42 Prepare for next development iteration https://github.com/jacoco/jacoco/commit/c0ad7810555f4c19ab8da68e94d4bf9344481564;>c0ad781 Prepare release 0.8.9 https://github.com/jacoco/jacoco/commit/c561c13f07a544a3a8cd4430c2bb8eae7deea229;>c561c13 Fix validation test for Java 21 (https://redirect.github.com/jacoco/jacoco/issues/1422;>#1422) https://github.com/jacoco/jacoco/commit/461ebf312620799a3815807e09cb84e4e43a39aa;>461ebf3 Add validation test for JEP 432: Record Patterns (https://redirect.github.com/jacoco/jacoco/issues/1415;>#1415) https://github.com/jacoco/jacoco/commit/5f12145bffb2b965618f9b0f05e73336fbed3f85;>5f12145 Upgrade ASM to 9.5 (https://redirect.github.com/jacoco/jacoco/issues/1416;>#1416) https://github.com/jacoco/jacoco/commit/b865890d566c55832def986bb800b0b2f98200de;>b865890 Agent should not open java.lang package to unnamed module of the applicatio... https://github.com/jacoco/jacoco/commit/5bc2fae5cf3500312b003bc2cc13c438a3313c79;>5bc2fae Upgrade spotless-maven-plugin to 2.35.0 and Eclipse JDT Formatter to 4.27 (https://redirect.github.com/jacoco/jacoco/issues/1;>#1... Additional commits viewable in https://github.com/jacoco/jacoco/compare/v0.8.8...v0.8.10;>compare view Updates `jacoco-maven-plugin` from 0.8.8 to 0.8.10 Release notes Sourced from https://github.com/jacoco/jacoco/releases;>jacoco-maven-plugin's releases. 0.8.10 Fixed bugs Agent should not require configuration of permissions for SecurityManager outside of its codeBase (GitHub https://redirect.github.com/jacoco/jacoco/issues/1425;>#1425). 0.8.9 New Features JaCoCo now officially supports Java 19 and 20 (GitHub https://redirect.github.com/jacoco/jacoco/issues/1371;>#1371, https://redirect.github.com/jacoco/jacoco/issues/1386;>#1386). Experimental support for Java 21 class files (GitHub https://redirect.github.com/jacoco/jacoco/issues/1386;>#1386). Add parameter to include the current project in the report-aggregate Maven goal (GitHub https://redirect.github.com/jacoco/jacoco/issues/1007;>#1007). Component accessors generated by the Java compilers for records are filtered out during generation of report. Contributed by Tesla Zhang (GitHub https://redirect.github.com/jacoco/jacoco/issues/1393;>#1393). Fixed bugs Agent should not open java.lang package to unnamed module of the application class loader (GitHub https://redirect.github.com/jacoco/jacoco/issues/1334;>#1334). Non-functional Changes JaCoCo now depends on ASM 9.5
[GitHub] [maven-surefire] dependabot[bot] opened a new pull request, #649: Bump aetherVersion from 1.0.0.v20140518 to 1.1.0
dependabot[bot] opened a new pull request, #649: URL: https://github.com/apache/maven-surefire/pull/649 Bumps `aetherVersion` from 1.0.0.v20140518 to 1.1.0. Updates `aether-impl` from 1.0.0.v20140518 to 1.1.0 Updates `aether-connector-basic` from 1.0.0.v20140518 to 1.1.0 Updates `aether-transport-wagon` from 1.0.0.v20140518 to 1.1.0 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SUREFIRE-1421) no test in html report however TEST-...xml list 7 tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1421.
Resolution: Incomplete
No reaction for a long time.
> no test in html report however TEST-...xml list 7 tests
> ---
>
> Key: SUREFIRE-1421
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1421
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.19.1, 2.20.1
>Reporter: Rodrigo Jimenez
>Assignee: Tibor Digana
>Priority: Minor
> Attachments: TEST-com.siemens.remu.sockets.SocketTranceiverTest.xml,
> surefire-report.html
>
>
> Dear all, I've been struggling already a couple of hours to get a html test
> report with no lucky
> is listing zero test when in the xml file there are 7 listed. What I'm doing
> wrong.
> {code}
> mvn -X test -Dmaven.checkstyle.skip=true
> -Dmaven.surefire.failIfNoTests=false
> -Dmaven.surefire.parallelTestsTimeoutInSeconds=60
> -Dmaven.surefire.parallelTestsTimeoutForcedInSeconds=60
> -Dmaven.test.failure.ignore=true
> -DreportsDirectories=target/surefire-reports/ -DskipSurefireReport=false
> -DalwaysGenerateSurefireReport=true -DshowSuccess=true -DlinkXRef=false
> {code}
> does not report any error
> I have a test file generated in target/surefire-reports/TEST-...xml
> {code}
> classname="com.siemens.remu.sockets.SocketTranceiverTest" time="4.416"/>
>classname="com.siemens.remu.sockets.SocketTranceiverTest" time="3.019"/>
>classname="com.siemens.remu.sockets.SocketTranceiverTest" time="0.014"/>
>classname="com.siemens.remu.sockets.SocketTranceiverTest" time="0.001"/>
>classname="com.siemens.remu.sockets.SocketTranceiverTest" time="0.001"/>
>classname="com.siemens.remu.sockets.SocketTranceiverTest" time="2.017"/>
>classname="com.siemens.remu.sockets.SocketTranceiverTest" time="0.009"/>
> {code}
> and a html report is generated target/site/surefire-report.html
> {code}
>
> Surefire Report
>
> Summary
>
>
> Tests
> Errors
> Failures
> Skipped
> Success Rate
> Time
>
> 0
> 0
> 0
> 0
> 0%
> 0
> {code}
> Currently my pom conf is as follows:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.20.1
>
>
> org.apache.maven.plugins
> maven-surefire-report-plugin
> 2.20.1
>
>
> test
>
> report-only
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (SUREFIRE-1533) surefire-test-report.xsd has too narrow a definition for testcase time attribute
[
https://issues.apache.org/jira/browse/SUREFIRE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727187#comment-17727187
]
Michael Osipov edited comment on SUREFIRE-1533 at 5/29/23 7:35 PM:
---
I believe that this is now addressed it will now support {{xs:float}} and parse
in Java whatever {{Float}} will parse.
Fixed with
[2a0e80de9af441e35b8fc226769574e2077251a9|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=2a0e80de9af441e35b8fc226769574e2077251a9].
was (Author: michael-o):
I believe that this is now addressed it will now support {{xs:float}} and parse
in Java whatever {{Float}} will parse.
> surefire-test-report.xsd has too narrow a definition for testcase time
> attribute
>
>
> Key: SUREFIRE-1533
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1533
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 5.x support
>Reporter: Thomas Sondergaard
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.1.2
>
>
> The jenkins xunit plugin uses the surefire jenkins schema for validation.
> [http://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd]
> Many test tools, also outside the Java world, use the junit format, but it
> has (apparently) not been well-specified so a number of tools generate junit
> reports that do not match the xsd above. Specifically I have run into the
> problem that the time attribute is much too narrowly defined in the schema.
> It does not allow specifying time with sub-millisecond precision or use of
> scientific notation for the time.
> Are there any reason not to allow any floating point number for the
> (testcase) time attribute?
> If you do not want to allow scientific notation at least allow more than
> three decimals.
> See also https://issues.jenkins-ci.org/browse/JENKINS-52152
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-toolchains-plugin] gnodet commented on a diff in pull request #14: Add a mojo to display discovered toolchains
gnodet commented on code in PR #14:
URL:
https://github.com/apache/maven-toolchains-plugin/pull/14#discussion_r1209525853
##
pom.xml:
##
@@ -67,28 +67,66 @@ under the License.
-8
-3.2.5
+11
+4.0.0-alpha-6-SNAPSHOT
2022-06-18T21:03:59Z
org.apache.maven
- maven-plugin-api
+ maven-api-core
${mavenVersion}
provided
org.apache.maven
- maven-core
+ maven-toolchain-builder
${mavenVersion}
provided
org.apache.maven.plugin-tools
maven-plugin-annotations
+ 3.8.1
provided
+
+ org.eclipse.sisu
+ org.eclipse.sisu.plexus
+ 0.9.0.M2
+
+
+
+
+
+org.apache.maven.plugins
+maven-plugin-plugin
+3.8.1
+
+
+org.apache.maven.plugins
+maven-invoker-plugin
+3.5.0
+
+
Review Comment:
I don't think this is related to spotless, but rather the switch to the v4
api.
This is actually not really required, though the `ToolchainDiscoverer`
service will only be available in maven 4, so imho, it makes sense.
I've just added a bunch of commits, so that makes things a bit harder to
follow, but if you kinda ignore the first commit (which is more or less
https://github.com/apache/maven-toolchains-plugin/pull/13), the patch is
smaller.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Assigned] (SUREFIRE-2173) Update compiler source/target in integration tests to version 8
[ https://issues.apache.org/jira/browse/SUREFIRE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned SUREFIRE-2173: -- Assignee: Sylwester Lachiewicz > Update compiler source/target in integration tests to version 8 > --- > > Key: SUREFIRE-2173 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.2 > > > To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (SUREFIRE-1533) surefire-test-report.xsd has too narrow a definition for testcase time attribute
[
https://issues.apache.org/jira/browse/SUREFIRE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727187#comment-17727187
]
Michael Osipov edited comment on SUREFIRE-1533 at 5/29/23 7:27 PM:
---
I believe that this is now addressed it will now support {{xs:float}} and parse
in Java whatever {{Float}} will parse.
was (Author: michael-o):
I believe that this is now addressed.
> surefire-test-report.xsd has too narrow a definition for testcase time
> attribute
>
>
> Key: SUREFIRE-1533
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1533
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 5.x support
>Reporter: Thomas Sondergaard
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.1.2
>
>
> The jenkins xunit plugin uses the surefire jenkins schema for validation.
> [http://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd]
> Many test tools, also outside the Java world, use the junit format, but it
> has (apparently) not been well-specified so a number of tools generate junit
> reports that do not match the xsd above. Specifically I have run into the
> problem that the time attribute is much too narrowly defined in the schema.
> It does not allow specifying time with sub-millisecond precision or use of
> scientific notation for the time.
> Are there any reason not to allow any floating point number for the
> (testcase) time attribute?
> If you do not want to allow scientific notation at least allow more than
> three decimals.
> See also https://issues.jenkins-ci.org/browse/JENKINS-52152
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-1533) surefire-test-report.xsd has too narrow a definition for testcase time attribute
[ https://issues.apache.org/jira/browse/SUREFIRE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SUREFIRE-1533. Resolution: Fixed I believe that this is now addressed. > surefire-test-report.xsd has too narrow a definition for testcase time > attribute > > > Key: SUREFIRE-1533 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1533 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support >Reporter: Thomas Sondergaard >Assignee: Michael Osipov >Priority: Major > Fix For: 3.1.2 > > > The jenkins xunit plugin uses the surefire jenkins schema for validation. > [http://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd] > Many test tools, also outside the Java world, use the junit format, but it > has (apparently) not been well-specified so a number of tools generate junit > reports that do not match the xsd above. Specifically I have run into the > problem that the time attribute is much too narrowly defined in the schema. > It does not allow specifying time with sub-millisecond precision or use of > scientific notation for the time. > Are there any reason not to allow any floating point number for the > (testcase) time attribute? > If you do not want to allow scientific notation at least allow more than > three decimals. > See also https://issues.jenkins-ci.org/browse/JENKINS-52152 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2175) Turn time attribute to xs:float in Surefire test report schema
[
https://issues.apache.org/jira/browse/SUREFIRE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2175.
Resolution: Fixed
Fixed with
[96dedb306e4a299bfa007674c4970938eb084f10|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=96dedb306e4a299bfa007674c4970938eb084f10].
> Turn time attribute to xs:float in Surefire test report schema
> --
>
> Key: SUREFIRE-2175
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2175
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Surefire Plugin, xml generation
>Affects Versions: 3.1.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.1.2
>
>
> Since in SUREFIRE-2164 and SUREFIRE-2167 we work now with pure Java floats we
> can change the {{time}} simple type to {{xs:float}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2175) Turn time attribute to xs:float in Surefire test report schema
[
https://issues.apache.org/jira/browse/SUREFIRE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-2175:
-
Summary: Turn time attribute to xs:float in Surefire test report schema
(was: Turn time attribute to xs:float)
> Turn time attribute to xs:float in Surefire test report schema
> --
>
> Key: SUREFIRE-2175
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2175
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Surefire Plugin, xml generation
>Affects Versions: 3.1.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.1.2
>
>
> Since in SUREFIRE-2164 and SUREFIRE-2167 we work now with pure Java floats we
> can change the {{time}} simple type to {{xs:float}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SUREFIRE-2175) Turn time attribute to xs:float
Michael Osipov created SUREFIRE-2175:
Summary: Turn time attribute to xs:float
Key: SUREFIRE-2175
URL: https://issues.apache.org/jira/browse/SUREFIRE-2175
Project: Maven Surefire
Issue Type: Task
Components: Maven Surefire Plugin, xml generation
Affects Versions: 3.1.1
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.1.2
Since in SUREFIRE-2164 and SUREFIRE-2167 we work now with pure Java floats we
can change the {{time}} simple type to {{xs:float}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2173) Update compiler source/target in integration tests to version 8
[ https://issues.apache.org/jira/browse/SUREFIRE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727184#comment-17727184 ] ASF GitHub Bot commented on SUREFIRE-2173: -- slachiewicz opened a new pull request, #648: URL: https://github.com/apache/maven-surefire/pull/648 (no comment) > Update compiler source/target in integration tests to version 8 > --- > > Key: SUREFIRE-2173 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.2 > > > To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2174) Remove legacy Surefire test report schema file and make 3.0 default
[ https://issues.apache.org/jira/browse/SUREFIRE-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SUREFIRE-2174. Resolution: Fixed Fixed with [1355988759fd7edeac361b67f0b84669da4e5c54|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=1355988759fd7edeac361b67f0b84669da4e5c54]. > Remove legacy Surefire test report schema file and make 3.0 default > --- > > Key: SUREFIRE-2174 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2174 > Project: Maven Surefire > Issue Type: Task > Components: documentation, Maven Surefire Plugin, xml generation >Affects Versions: 3.1.1 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.1.2 > > > Since 2.x is superseded with 3.0 and 3.1 is out of the door, we can remove > the old schema and use the 3.0 one as default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-surefire] slachiewicz opened a new pull request, #648: [SUREFIRE-2173] Pass build and tests with Java 20
slachiewicz opened a new pull request, #648: URL: https://github.com/apache/maven-surefire/pull/648 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SUREFIRE-2174) Remove legacy Surefire test report schema file and make 3.0 default
Michael Osipov created SUREFIRE-2174: Summary: Remove legacy Surefire test report schema file and make 3.0 default Key: SUREFIRE-2174 URL: https://issues.apache.org/jira/browse/SUREFIRE-2174 Project: Maven Surefire Issue Type: Task Components: documentation, Maven Surefire Plugin, xml generation Affects Versions: 3.1.1 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.1.2 Since 2.x is superseded with 3.0 and 3.1 is out of the door, we can remove the old schema and use the 3.0 one as default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-1533) surefire-test-report.xsd has too narrow a definition for testcase time attribute
[ https://issues.apache.org/jira/browse/SUREFIRE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SUREFIRE-1533: Assignee: Michael Osipov > surefire-test-report.xsd has too narrow a definition for testcase time > attribute > > > Key: SUREFIRE-1533 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1533 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support >Reporter: Thomas Sondergaard >Assignee: Michael Osipov >Priority: Major > > The jenkins xunit plugin uses the surefire jenkins schema for validation. > [http://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd] > Many test tools, also outside the Java world, use the junit format, but it > has (apparently) not been well-specified so a number of tools generate junit > reports that do not match the xsd above. Specifically I have run into the > problem that the time attribute is much too narrowly defined in the schema. > It does not allow specifying time with sub-millisecond precision or use of > scientific notation for the time. > Are there any reason not to allow any floating point number for the > (testcase) time attribute? > If you do not want to allow scientific notation at least allow more than > three decimals. > See also https://issues.jenkins-ci.org/browse/JENKINS-52152 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-1533) surefire-test-report.xsd has too narrow a definition for testcase time attribute
[
https://issues.apache.org/jira/browse/SUREFIRE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727182#comment-17727182
]
Michael Osipov commented on SUREFIRE-1533:
--
These two issues simplify the serialization/deserialization of the elapsed time
value to a Java float to the rules of {{Float#parseFloat()}}, so technically
you can now have sub-millisecond precision and even use engineering notation,
for the schema change to {{xs:float}} I will create a new issue.
> surefire-test-report.xsd has too narrow a definition for testcase time
> attribute
>
>
> Key: SUREFIRE-1533
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1533
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 5.x support
>Reporter: Thomas Sondergaard
>Priority: Major
>
> The jenkins xunit plugin uses the surefire jenkins schema for validation.
> [http://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd]
> Many test tools, also outside the Java world, use the junit format, but it
> has (apparently) not been well-specified so a number of tools generate junit
> reports that do not match the xsd above. Specifically I have run into the
> problem that the time attribute is much too narrowly defined in the schema.
> It does not allow specifying time with sub-millisecond precision or use of
> scientific notation for the time.
> Are there any reason not to allow any floating point number for the
> (testcase) time attribute?
> If you do not want to allow scientific notation at least allow more than
> three decimals.
> See also https://issues.jenkins-ci.org/browse/JENKINS-52152
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-1533) surefire-test-report.xsd has too narrow a definition for testcase time attribute
[ https://issues.apache.org/jira/browse/SUREFIRE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SUREFIRE-1533: - Fix Version/s: 3.1.2 > surefire-test-report.xsd has too narrow a definition for testcase time > attribute > > > Key: SUREFIRE-1533 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1533 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support >Reporter: Thomas Sondergaard >Assignee: Michael Osipov >Priority: Major > Fix For: 3.1.2 > > > The jenkins xunit plugin uses the surefire jenkins schema for validation. > [http://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd] > Many test tools, also outside the Java world, use the junit format, but it > has (apparently) not been well-specified so a number of tools generate junit > reports that do not match the xsd above. Specifically I have run into the > problem that the time attribute is much too narrowly defined in the schema. > It does not allow specifying time with sub-millisecond precision or use of > scientific notation for the time. > Are there any reason not to allow any floating point number for the > (testcase) time attribute? > If you do not want to allow scientific notation at least allow more than > three decimals. > See also https://issues.jenkins-ci.org/browse/JENKINS-52152 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2173) Update compiler source/target in integration tests to version 8
[ https://issues.apache.org/jira/browse/SUREFIRE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated SUREFIRE-2173: --- Summary: Update compiler source/target in integration tests to version 8 (was: Update java source/target in integration tests to version 8) > Update compiler source/target in integration tests to version 8 > --- > > Key: SUREFIRE-2173 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.2 > > > To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2173) Update java source/target in integration tests to version 8
[ https://issues.apache.org/jira/browse/SUREFIRE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated SUREFIRE-2173: --- Issue Type: Improvement (was: Task) > Update java source/target in integration tests to version 8 > --- > > Key: SUREFIRE-2173 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Priority: Minor > > To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2173) Update java source/target in integration tests to version 8
[ https://issues.apache.org/jira/browse/SUREFIRE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated SUREFIRE-2173: --- Fix Version/s: 3.1.2 > Update java source/target in integration tests to version 8 > --- > > Key: SUREFIRE-2173 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.2 > > > To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SUREFIRE-2173) Update java source/target in integration tests to version 8
Sylwester Lachiewicz created SUREFIRE-2173: -- Summary: Update java source/target in integration tests to version 8 Key: SUREFIRE-2173 URL: https://issues.apache.org/jira/browse/SUREFIRE-2173 Project: Maven Surefire Issue Type: Task Reporter: Sylwester Lachiewicz To be able build project and pass tests with Java 20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2157) Upgrade JUnit 5 to 5.9.2
[ https://issues.apache.org/jira/browse/SUREFIRE-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated SUREFIRE-2157: --- Summary: Upgrade JUnit 5 to 5.9.2 (was: Upgrade to 5.9.2 ) > Upgrade JUnit 5 to 5.9.2 > - > > Key: SUREFIRE-2157 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2157 > Project: Maven Surefire > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2157) Upgrade JUnit 5 to 5.9.3 (or 5.10.x..)
[ https://issues.apache.org/jira/browse/SUREFIRE-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated SUREFIRE-2157: --- Summary: Upgrade JUnit 5 to 5.9.3 (or 5.10.x..) (was: Upgrade JUnit 5 to 5.9.2 ) > Upgrade JUnit 5 to 5.9.3 (or 5.10.x..) > -- > > Key: SUREFIRE-2157 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2157 > Project: Maven Surefire > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SUREFIRE-1558) IOException not caught/declared in StatelessXmlReporter.java after maven-shared-utils update
[
https://issues.apache.org/jira/browse/SUREFIRE-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1558.
Resolution: Not A Problem
We are at 3.3.4 now, I don't consider it as a problem anymore.
> IOException not caught/declared in StatelessXmlReporter.java after
> maven-shared-utils update
>
>
> Key: SUREFIRE-1558
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1558
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.21.0, 2.22.0
> Environment: debian testing and unstable, ubuntu cosmic
>Reporter: Tiago Stürmer Daitx
>Priority: Major
> Attachments: surefire_2.21.0-1.rbuild.log
>
>
> maven-surefire-common fails to build with the following error message:
> {{maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/StatelessXmlReporter.java:[482,28]
> error: unreported exception IOException; must be caught or declared to be
> thrown
> }}
> This seems to be caused by maven-shared-utils update from 3.1 to 3.2, in
> particular by the fix of [maven-shared-util's
> MSHARED-610|https://issues.apache.org/jira/browse/MSHARED-610].
> More details and [full build logs are available in
> Debian|https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/surefire_2.21.0-1.rbuild.log.gz]
> and
> [Ubuntu|https://launchpadlibrarian.net/385098232/buildlog_ubuntu-cosmic-amd64.surefire_2.21.0-1_BUILDING.txt.gz].
> The reproducible builds bot in Debian also [opened a bug
> report|https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906411] in case you
> want to add something there or ask additional questions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-1572) Found dump files in surefire-reports folder
[
https://issues.apache.org/jira/browse/SUREFIRE-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1572.
Resolution: Cannot Reproduce
Closing as it does not reappear anymore. If it does, retry with 3.1.0 and
re-report. I will reopen.
> Found dump files in surefire-reports folder
> ---
>
> Key: SUREFIRE-1572
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1572
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.0
> Environment: Java 1.8
>Reporter: Marcus Ackermann
>Priority: Major
> Attachments: 2018-09-17T15-28-03_759-jvmRun1.dump,
> 2018-09-17T15-28-41_096-jvmRun1.dump
>
>
> After updating the surefire-plugin from 2.19.1 to 2.22.0 there are dump files
> in the folder {{surefire-reports}}. This behavior is non-deterministig. The
> maven build does not fail, and there is nothing written into {{testing.log}}.
> This seems to be related to the new _monitoring_ mechanism for the forked VM
> introduced in 2.20.1 with SUREFIRE-1302.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-1572) Found dump files in surefire-reports folder
[
https://issues.apache.org/jira/browse/SUREFIRE-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-1572:
-
Labels: (was: waiting-for-feedback)
> Found dump files in surefire-reports folder
> ---
>
> Key: SUREFIRE-1572
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1572
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.0
> Environment: Java 1.8
>Reporter: Marcus Ackermann
>Priority: Major
> Attachments: 2018-09-17T15-28-03_759-jvmRun1.dump,
> 2018-09-17T15-28-41_096-jvmRun1.dump
>
>
> After updating the surefire-plugin from 2.19.1 to 2.22.0 there are dump files
> in the folder {{surefire-reports}}. This behavior is non-deterministig. The
> maven build does not fail, and there is nothing written into {{testing.log}}.
> This seems to be related to the new _monitoring_ mechanism for the forked VM
> introduced in 2.20.1 with SUREFIRE-1302.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-1940) PpidChecker doesn't work with MacOS Docker Desktop
[
https://issues.apache.org/jira/browse/SUREFIRE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1940.
Resolution: Incomplete
No reaction for more than a year.
> PpidChecker doesn't work with MacOS Docker Desktop
> --
>
> Key: SUREFIRE-1940
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1940
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.22.2
> Environment: Jenkins, Mac OSx Big Sur, Docker Desktop
>Reporter: Marc Batchelor
>Priority: Major
> Labels: Docker, macOS
>
> Executing surefire in Jenkins OceanBlue pipeline in a docker container on
> MacOSX, PpidChecker executes /bin/ps -o etime= -p
>
> The result has leading spaces which the matcher fails to account for:
> {noformat}
> macthebuilder:platform_main@tmp jenkins$ docker exec -it 171938c2fca2 /bin/sh
> $ ps -ef
> UIDPID PPID C STIME TTY TIME CMD
> 502 1 0 0 Aug26 pts/000:00:00 cat
> 502165 0 0 Aug26 pts/100:00:00 /bin/bash
> 502 1133 0 0 11:23 pts/200:00:00 /bin/sh
> 502 1140 1133 0 11:23 pts/200:00:00 ps -ef
> $ /bin/ps -o etime= -p 165
>19:03:02{noformat}
> Suggest changing the ps to add a :1, or trimming the output.
> {noformat}
> $ /bin/ps -o etime:1= -p 165
> 19:05:49 {noformat}
> Note - this also affects your master branch which now looks like this:
> {noformat}
> $ /bin/ps -o etime,pid -p 165
> ELAPSED PID
>20:42:20 165 {noformat}
> Changing it to include :1 looks like this:
> {noformat}
> $ /bin/ps -o etime:1,pid:1 -p 165
> ELAPSED PID
> 20:43:28 165
> {noformat}
> Of course, you could trim leading spaces before you apply the matcher, or add
> 0 or more spaces at the beginning of the pattern(s).
> One other thing - it would be mighty helpful to have some kind of
> configuration work-around for this in the future. I wish I could just supply
> the ps statement that works in our environment in the surefire configuration
> in the POM. Right now, it looks like I'll have to disable forking in our
> surefire configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-1940) PpidChecker doesn't work with MacOS Docker Desktop
[
https://issues.apache.org/jira/browse/SUREFIRE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-1940:
-
Labels: Docker macOS (was: Docker macOS waiting-for-feedback)
> PpidChecker doesn't work with MacOS Docker Desktop
> --
>
> Key: SUREFIRE-1940
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1940
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.22.2
> Environment: Jenkins, Mac OSx Big Sur, Docker Desktop
>Reporter: Marc Batchelor
>Priority: Major
> Labels: Docker, macOS
>
> Executing surefire in Jenkins OceanBlue pipeline in a docker container on
> MacOSX, PpidChecker executes /bin/ps -o etime= -p
>
> The result has leading spaces which the matcher fails to account for:
> {noformat}
> macthebuilder:platform_main@tmp jenkins$ docker exec -it 171938c2fca2 /bin/sh
> $ ps -ef
> UIDPID PPID C STIME TTY TIME CMD
> 502 1 0 0 Aug26 pts/000:00:00 cat
> 502165 0 0 Aug26 pts/100:00:00 /bin/bash
> 502 1133 0 0 11:23 pts/200:00:00 /bin/sh
> 502 1140 1133 0 11:23 pts/200:00:00 ps -ef
> $ /bin/ps -o etime= -p 165
>19:03:02{noformat}
> Suggest changing the ps to add a :1, or trimming the output.
> {noformat}
> $ /bin/ps -o etime:1= -p 165
> 19:05:49 {noformat}
> Note - this also affects your master branch which now looks like this:
> {noformat}
> $ /bin/ps -o etime,pid -p 165
> ELAPSED PID
>20:42:20 165 {noformat}
> Changing it to include :1 looks like this:
> {noformat}
> $ /bin/ps -o etime:1,pid:1 -p 165
> ELAPSED PID
> 20:43:28 165
> {noformat}
> Of course, you could trim leading spaces before you apply the matcher, or add
> 0 or more spaces at the beginning of the pattern(s).
> One other thing - it would be mighty helpful to have some kind of
> configuration work-around for this in the future. I wish I could just supply
> the ps statement that works in our environment in the surefire configuration
> in the POM. Right now, it looks like I'll have to disable forking in our
> surefire configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-1586) Surefire eating away Java 11 illegal reflective access warnings
[ https://issues.apache.org/jira/browse/SUREFIRE-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SUREFIRE-1586. Fix Version/s: (was: waiting-for-feedback) Resolution: Incomplete No reaction for a year. > Surefire eating away Java 11 illegal reflective access warnings > --- > > Key: SUREFIRE-1586 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1586 > Project: Maven Surefire > Issue Type: Bug >Reporter: Andrea Aime >Priority: Major > > Java 11 is emitting a number of warnings about "Illegal Reflective Access", > which, I believe, are written on the standard error. > We upgraded surefire from 2.12.3, where the warnings were visible, to 2.22.1, > and the warnings just disappeared from the build output, while they are still > visible in target/surefire-reports/.dumpstream files. > Surefire is configured with > false > The last version of surefire that emits the warnings on console is 2.19.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1251) Deprecate the JAR Index feature (JDK-8302819)
[
https://issues.apache.org/jira/browse/MSHARED-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727153#comment-17727153
]
ASF GitHub Bot commented on MSHARED-1251:
-
jorsol commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209467462
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
Well, adding Javadoc to private fields could be helpful in some cases,
especially if the comment is succinct.
Yet, even if adding a Javadoc on a private field is just a cosmetic change,
it doesn't hurt in any way to have it, more when it signals to future
developers that touch the code that the field should no longer be used for
anything (or with extra care).
I don't mind removing the Javadoc from the field, but there is no real need
to remove it, in the end, is just a matter of code convention, just like adding
Javadoc to a private method is valid.
Maven plugins even recommend adding Javadoc on private fields as the
documentation of `@Parameter` is generated from there.
> Deprecate the JAR Index feature (JDK-8302819)
> -
>
> Key: MSHARED-1251
> URL: https://issues.apache.org/jira/browse/MSHARED-1251
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> See https://bugs.openjdk.org/browse/JDK-8305597
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-archiver] jorsol commented on a diff in pull request #33: [MSHARED-1251] - Deprecate the JAR Index feature (JDK-8302819)
jorsol commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209467462
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
Well, adding Javadoc to private fields could be helpful in some cases,
especially if the comment is succinct.
Yet, even if adding a Javadoc on a private field is just a cosmetic change,
it doesn't hurt in any way to have it, more when it signals to future
developers that touch the code that the field should no longer be used for
anything (or with extra care).
I don't mind removing the Javadoc from the field, but there is no real need
to remove it, in the end, is just a matter of code convention, just like adding
Javadoc to a private method is valid.
Maven plugins even recommend adding Javadoc on private fields as the
documentation of `@Parameter` is generated from there.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MSHARED-1251) Deprecate the JAR Index feature (JDK-8302819)
[
https://issues.apache.org/jira/browse/MSHARED-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727152#comment-17727152
]
ASF GitHub Bot commented on MSHARED-1251:
-
jorsol commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209467462
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
Well, adding Javadoc to private fields could be helpful in some cases,
especially if the comment is succinct.
Yet, even if adding a Javadoc on a private field is just a cosmetic change,
it doesn't hurt in any way to have it, more when it signals to future
developers that touch the code that the field should no longer be used for
anything (or with extra care).
I don't mind removing the Javadoc from the field, but there is no real need
to remove it, in the end, is just a matter of code convention, just like adding
Javadoc to a private method is valid, and that very same class contains Javadoc
with an unhelpful `@since` comment.
> Deprecate the JAR Index feature (JDK-8302819)
> -
>
> Key: MSHARED-1251
> URL: https://issues.apache.org/jira/browse/MSHARED-1251
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> See https://bugs.openjdk.org/browse/JDK-8305597
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-archiver] jorsol commented on a diff in pull request #33: [MSHARED-1251] - Deprecate the JAR Index feature (JDK-8302819)
jorsol commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209467462
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
Well, adding Javadoc to private fields could be helpful in some cases,
especially if the comment is succinct.
Yet, even if adding a Javadoc on a private field is just a cosmetic change,
it doesn't hurt in any way to have it, more when it signals to future
developers that touch the code that the field should no longer be used for
anything (or with extra care).
I don't mind removing the Javadoc from the field, but there is no real need
to remove it, in the end, is just a matter of code convention, just like adding
Javadoc to a private method is valid, and that very same class contains Javadoc
with an unhelpful `@since` comment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (SUREFIRE-2172) StringUtils: yet more of them
Elliotte Rusty Harold created SUREFIRE-2172: --- Summary: StringUtils: yet more of them Key: SUREFIRE-2172 URL: https://issues.apache.org/jira/browse/SUREFIRE-2172 Project: Maven Surefire Issue Type: Improvement Reporter: Elliotte Rusty Harold This project contains not one, not two, but **three** different StringUtils classes that duplicate functionality in the JDK and elsewhere. One or two of them imght be built by shading other classes. They're even sometimes both imported in the same classes such as LegacyPojoStackTraceWriter: import org.apache.maven.surefire.api.util.internal.StringUtils; import static org.apache.maven.surefire.shared.utils.StringUtils.isNotEmpty; Figure out what to do about this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727137#comment-17727137 ] Michael Osipov commented on MPIR-445: - [~hboutemy], yes with Maven Plugin Testing it runs the mojos are UTs, therefore, each test method is one m-r-impl invocation with searching for the skin. > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > Reduce to debug or remove completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-surefire] dependabot[bot] closed pull request #623: Bump commons-compress from 1.21 to 1.23.0
dependabot[bot] closed pull request #623: Bump commons-compress from 1.21 to 1.23.0 URL: https://github.com/apache/maven-surefire/pull/623 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] dependabot[bot] commented on pull request #623: Bump commons-compress from 1.21 to 1.23.0
dependabot[bot] commented on PR #623: URL: https://github.com/apache/maven-surefire/pull/623#issuecomment-1567317819 Looks like org.apache.commons:commons-compress is no longer updatable, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-393) Remove references to Maven 2.x
[ https://issues.apache.org/jira/browse/MNGSITE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727135#comment-17727135 ] ASF GitHub Bot commented on MNGSITE-393: elharo opened a new pull request, #647: URL: https://github.com/apache/maven-surefire/pull/647 (no comment) > Remove references to Maven 2.x > -- > > Key: MNGSITE-393 > URL: https://issues.apache.org/jira/browse/MNGSITE-393 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > Time Spent: 4h > Remaining Estimate: 0h > > Maven 3.x is over a decade old now and we're talking about Maven 4. It's time > to clean out all the random discussion here and there about how Maven 2.x did > things, differences between Maven 2 and 3, what works in Maven 3 but not 2, > etc. > Assume Maven 3.0 as the minimum, probably Maven 3.1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1251) Deprecate the JAR Index feature (JDK-8302819)
[
https://issues.apache.org/jira/browse/MSHARED-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727134#comment-17727134
]
ASF GitHub Bot commented on MSHARED-1251:
-
elharo commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209439247
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
Deprecating the method is enough. Private fields can be changed freely
without worrying about compatibility when they're no longer used. Adding
Javadoc to private fields, deprecation warnings included, is painting the lily.
> Deprecate the JAR Index feature (JDK-8302819)
> -
>
> Key: MSHARED-1251
> URL: https://issues.apache.org/jira/browse/MSHARED-1251
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> See https://bugs.openjdk.org/browse/JDK-8305597
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-archiver] elharo commented on a diff in pull request #33: [MSHARED-1251] - Deprecate the JAR Index feature (JDK-8302819)
elharo commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209439247
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
Deprecating the method is enough. Private fields can be changed freely
without worrying about compatibility when they're no longer used. Adding
Javadoc to private fields, deprecation warnings included, is painting the lily.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727126#comment-17727126 ] Herve Boutemy commented on MPIR-445: it's during unit tests execution in Surefire? I really did not expect that looking at plugin build could trigger that issue: we don't care about unit tests output, it's not by looking at these that the output of real use has to be evaluated > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > Reduce to debug or remove completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1251) Deprecate the JAR Index feature (JDK-8302819)
[
https://issues.apache.org/jira/browse/MSHARED-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727118#comment-17727118
]
ASF GitHub Bot commented on MSHARED-1251:
-
khmarbaise commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209374152
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
The point is that the usage of index.list has been marked deprecated and is
not being used starting with JDK18
https://www.oracle.com/java/technologies/javase/18-relnote-issues.html
Furthermore as already referenced in JDK21 it will be completely being
removed. Also it's good to have a reminder here...
> Deprecate the JAR Index feature (JDK-8302819)
> -
>
> Key: MSHARED-1251
> URL: https://issues.apache.org/jira/browse/MSHARED-1251
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> See https://bugs.openjdk.org/browse/JDK-8305597
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHARED-1251) Deprecate the JAR Index feature (JDK-8302819)
[
https://issues.apache.org/jira/browse/MSHARED-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727104#comment-17727104
]
ASF GitHub Bot commented on MSHARED-1251:
-
jorsol commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209280099
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
It's an internal mark that the field should no longer be used, it helps to
detect the places where it's used and is a reminder that in the future it could
be removed.
> Deprecate the JAR Index feature (JDK-8302819)
> -
>
> Key: MSHARED-1251
> URL: https://issues.apache.org/jira/browse/MSHARED-1251
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> See https://bugs.openjdk.org/browse/JDK-8305597
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-archiver] jorsol commented on a diff in pull request #33: [MSHARED-1251] - Deprecate the JAR Index feature (JDK-8302819)
jorsol commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209280099
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
It's an internal mark that the field should no longer be used, it helps to
detect the places where it's used and is a reminder that in the future it could
be removed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Resolved] (MSHARED-1260) Deprecate FileUtils.copyFile and FilterWrapper
[ https://issues.apache.org/jira/browse/MSHARED-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MSHARED-1260. Resolution: Fixed > Deprecate FileUtils.copyFile and FilterWrapper > -- > > Key: MSHARED-1260 > URL: https://issues.apache.org/jira/browse/MSHARED-1260 > Project: Maven Shared Components > Issue Type: Task > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > In favor of nearly identical methods in > org.apache.maven.shared.filtering.FilteringUtils -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1260) Deprecate FileUtils.copyFile and FilterWrapper
[ https://issues.apache.org/jira/browse/MSHARED-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MSHARED-1260. -- > Deprecate FileUtils.copyFile and FilterWrapper > -- > > Key: MSHARED-1260 > URL: https://issues.apache.org/jira/browse/MSHARED-1260 > Project: Maven Shared Components > Issue Type: Task > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > In favor of nearly identical methods in > org.apache.maven.shared.filtering.FilteringUtils -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1260) Deprecate FileUtils.copyFile and FilterWrapper
[ https://issues.apache.org/jira/browse/MSHARED-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727094#comment-17727094 ] ASF GitHub Bot commented on MSHARED-1260: - elharo merged PR #147: URL: https://github.com/apache/maven-shared-utils/pull/147 > Deprecate FileUtils.copyFile and FilterWrapper > -- > > Key: MSHARED-1260 > URL: https://issues.apache.org/jira/browse/MSHARED-1260 > Project: Maven Shared Components > Issue Type: Task > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > In favor of nearly identical methods in > org.apache.maven.shared.filtering.FilteringUtils -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-shared-utils] elharo merged pull request #147: [MSHARED-1260] Deprecate FileUtils.copyFile and FilterWrapper in favor of org.apache.maven.shared.filtering
elharo merged PR #147: URL: https://github.com/apache/maven-shared-utils/pull/147 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MSHARED-1254) Deprecate WriterFactory
[ https://issues.apache.org/jira/browse/MSHARED-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MSHARED-1254. -- > Deprecate WriterFactory > --- > > Key: MSHARED-1254 > URL: https://issues.apache.org/jira/browse/MSHARED-1254 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > Every method and public field in this class has a trivial, obvious, one-line > replacement in Java 8 and later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MSHARED-1254) Deprecate WriterFactory
[ https://issues.apache.org/jira/browse/MSHARED-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MSHARED-1254. Resolution: Fixed > Deprecate WriterFactory > --- > > Key: MSHARED-1254 > URL: https://issues.apache.org/jira/browse/MSHARED-1254 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > Every method and public field in this class has a trivial, obvious, one-line > replacement in Java 8 and later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSHARED-1254) Deprecate WriterFactory
[ https://issues.apache.org/jira/browse/MSHARED-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold reassigned MSHARED-1254: -- Assignee: Elliotte Rusty Harold > Deprecate WriterFactory > --- > > Key: MSHARED-1254 > URL: https://issues.apache.org/jira/browse/MSHARED-1254 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > Every method and public field in this class has a trivial, obvious, one-line > replacement in Java 8 and later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1254) Deprecate WriterFactory
[ https://issues.apache.org/jira/browse/MSHARED-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727092#comment-17727092 ] ASF GitHub Bot commented on MSHARED-1254: - elharo merged PR #146: URL: https://github.com/apache/maven-shared-utils/pull/146 > Deprecate WriterFactory > --- > > Key: MSHARED-1254 > URL: https://issues.apache.org/jira/browse/MSHARED-1254 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Priority: Major > > Every method and public field in this class has a trivial, obvious, one-line > replacement in Java 8 and later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-archiver] elharo closed pull request #29: Bump plexus-archiver from 4.4.0 to 4.6.3
elharo closed pull request #29: Bump plexus-archiver from 4.4.0 to 4.6.3 URL: https://github.com/apache/maven-archiver/pull/29 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-archiver] dependabot[bot] commented on pull request #29: Bump plexus-archiver from 4.4.0 to 4.6.3
dependabot[bot] commented on PR #29: URL: https://github.com/apache/maven-archiver/pull/29#issuecomment-1567019003 Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request `@dependabot recreate`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-1251) Deprecate the JAR Index feature (JDK-8302819)
[
https://issues.apache.org/jira/browse/MSHARED-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727079#comment-17727079
]
ASF GitHub Bot commented on MSHARED-1251:
-
elharo commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209224945
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
no real need to deprecate a private field
> Deprecate the JAR Index feature (JDK-8302819)
> -
>
> Key: MSHARED-1251
> URL: https://issues.apache.org/jira/browse/MSHARED-1251
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> See https://bugs.openjdk.org/browse/JDK-8305597
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-archiver] elharo commented on a diff in pull request #33: [MSHARED-1251] - Deprecate the JAR Index feature (JDK-8302819)
elharo commented on code in PR #33:
URL: https://github.com/apache/maven-archiver/pull/33#discussion_r1209224945
##
src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java:
##
@@ -35,6 +35,10 @@ public class MavenArchiveConfiguration {
private boolean recompressAddedZips = true;
+/**
+ * @deprecated See https://bugs.openjdk.org/browse/JDK-8305597;>JDK-8305597
+ */
+@Deprecated
Review Comment:
no real need to deprecate a private field
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MSHARED-1260) Deprecate FileUtils.copyFile and FilterWrapper
[ https://issues.apache.org/jira/browse/MSHARED-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727077#comment-17727077 ] ASF GitHub Bot commented on MSHARED-1260: - elharo opened a new pull request, #147: URL: https://github.com/apache/maven-shared-utils/pull/147 (no comment) > Deprecate FileUtils.copyFile and FilterWrapper > -- > > Key: MSHARED-1260 > URL: https://issues.apache.org/jira/browse/MSHARED-1260 > Project: Maven Shared Components > Issue Type: Task > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > In favor of nearly identical methods in > org.apache.maven.shared.filtering.FilteringUtils -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-799) improve mvn dependency:tree - add optional JSON output of the results
[ https://issues.apache.org/jira/browse/MDEP-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727076#comment-17727076 ] ASF GitHub Bot commented on MDEP-799: - MartinWitt commented on PR #325: URL: https://github.com/apache/maven-dependency-plugin/pull/325#issuecomment-1567008233 As I am a first-time contributor, someone has to approve the workflow run before we see CI results. > improve mvn dependency:tree - add optional JSON output of the results > - > > Key: MDEP-799 > URL: https://issues.apache.org/jira/browse/MDEP-799 > Project: Maven Dependency Plugin > Issue Type: New Feature > Components: tree >Reporter: Zhenxu Ke >Priority: Major > > I'd like to add an output type JSON, will open a pull request soon -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-799) improve mvn dependency:tree - add optional JSON output of the results
[
https://issues.apache.org/jira/browse/MDEP-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727075#comment-17727075
]
ASF GitHub Bot commented on MDEP-799:
-
MartinWitt commented on code in PR #325:
URL:
https://github.com/apache/maven-dependency-plugin/pull/325#discussion_r1209218850
##
src/main/java/org/apache/maven/plugins/dependency/tree/TreeMojo.java:
##
@@ -380,6 +380,8 @@ public DependencyNodeVisitor
getSerializingDependencyNodeVisitor(Writer writer)
return new TGFDependencyNodeVisitor(writer);
} else if ("dot".equals(outputType)) {
return new DOTDependencyNodeVisitor(writer);
+} else if ("json".equals(outputType)) {
+return new JsonDependencyNodeVisitor(writer);
} else {
return new SerializingDependencyNodeVisitor(writer,
toGraphTokens(tokens));
Review Comment:
In the other PR someone asked for a switch case instead. Shall I convert
this to a switch statement?
> improve mvn dependency:tree - add optional JSON output of the results
> -
>
> Key: MDEP-799
> URL: https://issues.apache.org/jira/browse/MDEP-799
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: tree
>Reporter: Zhenxu Ke
>Priority: Major
>
> I'd like to add an output type JSON, will open a pull request soon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHARED-1254) Deprecate WriterFactory
[ https://issues.apache.org/jira/browse/MSHARED-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727073#comment-17727073 ] ASF GitHub Bot commented on MSHARED-1254: - elharo opened a new pull request, #146: URL: https://github.com/apache/maven-shared-utils/pull/146 No longer needed in Java 8+. > Deprecate WriterFactory > --- > > Key: MSHARED-1254 > URL: https://issues.apache.org/jira/browse/MSHARED-1254 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Priority: Major > > Every method and public field in this class has a trivial, obvious, one-line > replacement in Java 8 and later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-446) Update SCM to 2.0.1
[ https://issues.apache.org/jira/browse/MPIR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727074#comment-17727074 ] Michael Osipov commented on MPIR-446: - I'd say that we need a list of all of our components using SCM and upgrade piece by piece. > Update SCM to 2.0.1 > --- > > Key: MPIR-446 > URL: https://issues.apache.org/jira/browse/MPIR-446 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Priority: Major > > Currently blocked waiting for more providers — perforce, starteam, CVS — to > be updated to 2.0.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727072#comment-17727072 ] Michael Osipov commented on MPIR-445: - ...and that is correct because there are multiple *standalone* invocations of the reporting plugin. > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > Reduce to debug or remove completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-446) Update SCM to 2.0.1
[ https://issues.apache.org/jira/browse/MPIR-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727069#comment-17727069 ] Elliotte Rusty Harold commented on MPIR-446: Are we ready to drop support for those in the next release? > Update SCM to 2.0.1 > --- > > Key: MPIR-446 > URL: https://issues.apache.org/jira/browse/MPIR-446 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Priority: Major > > Currently blocked waiting for more providers — perforce, starteam, CVS — to > be updated to 2.0.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727068#comment-17727068 ] Elliotte Rusty Harold commented on MPIR-445: Run `mvn test` on maven-project-info-reports-plugin. By my count that log message appears 17 times: ``` [INFO] Running org.apache.maven.report.projectinfo.MailingListsReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [WARNING] Invalid mailing list link provided 'test at maven.apache.org': Illegal character in path at index 4: test at maven.apache.org [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.094 s - in org.apache.maven.report.projectinfo.MailingListsReportTest [INFO] Running org.apache.maven.report.projectinfo.ScmReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.336 s - in org.apache.maven.report.projectinfo.ScmReportTest [INFO] Running org.apache.maven.report.projectinfo.DependencyManagementReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 s - in org.apache.maven.report.projectinfo.DependencyManagementReportTest [INFO] Running org.apache.maven.report.projectinfo.PluginManagementReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.662 s - in org.apache.maven.report.projectinfo.PluginManagementReportTest [INFO] Running org.apache.maven.report.projectinfo.DependencyConvergenceReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.189 s - in org.apache.maven.report.projectinfo.DependencyConvergenceReportTest [INFO] Running org.apache.maven.report.projectinfo.ModulesReportTest [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.242 s - in org.apache.maven.report.projectinfo.ModulesReportTest [INFO] Running org.apache.maven.report.projectinfo.IndexReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.147 s - in org.apache.maven.report.projectinfo.IndexReportTest [INFO] Running org.apache.maven.report.projectinfo.IssueManagementReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.122 s - in org.apache.maven.report.projectinfo.IssueManagementReportTest [INFO] Running org.apache.maven.report.projectinfo.CiManagementReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.226 s - in org.apache.maven.report.projectinfo.CiManagementReportTest [INFO] Running org.apache.maven.report.projectinfo.SummaryReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.116 s - in org.apache.maven.report.projectinfo.SummaryReportTest [INFO] Running org.apache.maven.report.projectinfo.TeamReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.176 s - in org.apache.maven.report.projectinfo.TeamReportTest [INFO] Running org.apache.maven.report.projectinfo.LicensesReportTest [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. [INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3 skin. ``` > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3
[jira] [Commented] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727055#comment-17727055 ] Michael Osipov commented on MPIR-445: - [~hboutemy], +1. > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > Reduce to debug or remove completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-418) Cannot deploy snapshot - do I miss some config?
[
https://issues.apache.org/jira/browse/MPOM-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727037#comment-17727037
]
Herve Boutemy commented on MPOM-418:
perhaps we can improve our documentation on this requirement at
repository.apache.org
I imagine the list of registered projects is visible here
[https://repository.apache.org/content/groups/maven-staging-group/org/apache/opendal/]
and Jira issues for that
[https://issues.apache.org/jira/issues/?jql=project%20%3D%20INFRA%20AND%20component%20%3D%20Nexus]
(notice that INFRA-24347 had been opened in March but abandoned :) )
> Cannot deploy snapshot - do I miss some config?
> ---
>
> Key: MPOM-418
> URL: https://issues.apache.org/jira/browse/MPOM-418
> Project: Maven POMs
> Issue Type: Improvement
> Components: maven
>Reporter: Zili Chen
>Priority: Major
>
> https://github.com/apache/incubator-opendal/pull/2301 Here is the branch I'm
> testing for deploying a snapshot Maven artifact.
> When I run it locally by `mvn -X -P apache-release clean deploy`, it fails in
> the uploading step with log:
> {noformat}
> [DEBUG] Using transporter HttpTransporter with priority 5.0 for
> https://repository.apache.org/content/repositories/snapshots
> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for
> https://repository.apache.org/content/repositories/snapshots with
> username=tison, password=***
> Downloading from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/maven-metadata.xml
> [DEBUG] Could not find metadata
> org.apache.opendal:opendal-java:0.1.0-SNAPSHOT/maven-metadata.xml in
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots)
> [DEBUG] Writing tracking file
> '/Users/chenzili/.m2/repository/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/resolver-status.properties'
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.jar
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.pom
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 50.971 s
> [INFO] Finished at: 2023-05-24T09:47:17+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project opendal-java: Failed to deploy artifacts: Could not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project opendal-java: Failed to deploy artifacts: Could
> not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:160)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
[jira] [Commented] (MPOM-418) Cannot deploy snapshot - do I miss some config?
[
https://issues.apache.org/jira/browse/MPOM-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727035#comment-17727035
]
Herve Boutemy commented on MPOM-418:
FTR, discussion happened on the dev ML
[https://lists.apache.org/thread/t1f5wws6o4moy0p9kt4726ng5tsgzgln]
500 Internal Server Error caused by incubator project not being configured yet
in repository.apache.org: fixed by INFRA-24630
> Cannot deploy snapshot - do I miss some config?
> ---
>
> Key: MPOM-418
> URL: https://issues.apache.org/jira/browse/MPOM-418
> Project: Maven POMs
> Issue Type: Improvement
> Components: maven
>Reporter: Zili Chen
>Priority: Major
>
> https://github.com/apache/incubator-opendal/pull/2301 Here is the branch I'm
> testing for deploying a snapshot Maven artifact.
> When I run it locally by `mvn -X -P apache-release clean deploy`, it fails in
> the uploading step with log:
> {noformat}
> [DEBUG] Using transporter HttpTransporter with priority 5.0 for
> https://repository.apache.org/content/repositories/snapshots
> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for
> https://repository.apache.org/content/repositories/snapshots with
> username=tison, password=***
> Downloading from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/maven-metadata.xml
> [DEBUG] Could not find metadata
> org.apache.opendal:opendal-java:0.1.0-SNAPSHOT/maven-metadata.xml in
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots)
> [DEBUG] Writing tracking file
> '/Users/chenzili/.m2/repository/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/resolver-status.properties'
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.jar
> Uploading to apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/opendal/opendal-java/0.1.0-SNAPSHOT/opendal-java-0.1.0-20230524.014626-1.pom
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 50.971 s
> [INFO] Finished at: 2023-05-24T09:47:17+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project opendal-java: Failed to deploy artifacts: Could not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project opendal-java: Failed to deploy artifacts: Could
> not transfer artifact
> org.apache.opendal:opendal-java:jar:0.1.0-20230524.014626-1 from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): status code:
> 500, reason phrase: Internal Server Error (500)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:160)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute
[jira] [Comment Edited] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727032#comment-17727032 ] Herve Boutemy edited comment on MPIR-445 at 5/29/23 7:44 AM: - I disagree: * it's not in pom.xml but site.xml * there is a default value when omitted that people don't know about * yes, it's not about debugging failure, but about understanding the magic that happens when rendering a site * it costs 1 info line of info that is worth it: for sure, not "junk" again, please show it int the global output of a m-site-p run (or something else if you saw in in another context: when the report is invoked as a direct goal, it could be maven-reporting-impl that does the equivalent site rendering), move it eventually to the right Jira project, and we'll see what is noisy and what is info about the running process But out of context, I just see bad unjustified judgement without clear view on the context was (Author: hboutemy): I disagree: * it's not in pom.xml but site.xml * there is a default value when omitted that people don't know about * yes, it's not about debugging failure, but about understanding the magic that happens when rendering a site * it costs 1 info line of info that is worth it: for sure, not "junk" again, please show it int the global output of a m-site-p run (or something else if you saw in in another context), move it eventually to the right Jira project, and we'll see what is noisy and what is info about the running process But out of context, I just see bad unjustified judgement > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > Reduce to debug or remove completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-445) Rendering content log junk
[ https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727032#comment-17727032 ] Herve Boutemy commented on MPIR-445: I disagree: * it's not in pom.xml but site.xml * there is a default value when omitted that people don't know about * yes, it's not about debugging failure, but about understanding the magic that happens when rendering a site * it costs 1 info line of info that is worth it: for sure, not "junk" again, please show it int the global output of a m-site-p run (or something else if you saw in in another context), move it eventually to the right Jira project, and we'll see what is noisy and what is info about the running process But out of context, I just see bad unjustified judgement > Rendering content log junk > -- > > Key: MPIR-445 > URL: https://issues.apache.org/jira/browse/MPIR-445 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Another log message that's unneeded and simply clutters the output: > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > Reduce to debug or remove completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
