[jira] [Closed] (MJAR-285) versioned files do not use project.build.outputTimestamp
[
https://issues.apache.org/jira/browse/MJAR-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MJAR-285.
--
Resolution: Duplicate
ok, issue closed as Duplicate
> versioned files do not use project.build.outputTimestamp
> --
>
> Key: MJAR-285
> URL: https://issues.apache.org/jira/browse/MJAR-285
> Project: Maven JAR Plugin
> Issue Type: Sub-task
>Affects Versions: 3.2.2
>Reporter: Ceki Gülcü
>Priority: Major
>
> Hello,
> It looks like the addition of compressed files under META-INF/versions/ or
> module-info.class does not use the value of {{project.build.outputTimestamp}}
> but the local time instead.
> In any case, in logback project's build,
> {{META-INF/versions/9/module-info.class}} has a different timestamp than
> other files.
> This prevents reproducible builds.
> Could you please have a look?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-mvnd] shalousun commented on issue #596: mvnd doesn't work in alpine
shalousun commented on issue #596: URL: https://github.com/apache/maven-mvnd/issues/596#issuecomment-1024813968 @ppalaga After I entered the container, I did the following test, and it always doesn't work in the alpine container, but it works fine in the non-alpine container, for example: debian-based image (docker pull jenkins/inbound-agent:latest-jdk8) ``` bash-5.1# mvnd bash: /opt/mvnd/bin/mvnd: No such file or directory bash-5.1# ls /opt/mvnd/bin mvnd mvnd-bash-completion.bash mvnd-sync mvnd.cmd mvnd.sh bash-5.1# /opt/mvnd/bin/mvnd --help bash: /opt/mvnd/bin/mvnd: No such file or directory bash-5.1# /opt/mvnd/bin/mvnd -v bash: /opt/mvnd/bin/mvnd: No such file or directory bash-5.1# echo $JAVA_HOME /opt/java/openjdk bash-5.1# mvnd --version bash: /opt/mvnd/bin/mvnd: No such file or directory bash-5.1# java -version openjdk version "11.0.12" 2021-07-20 OpenJDK Runtime Environment (build 11.0.12+7-alpine-r0) OpenJDK 64-Bit Server VM (build 11.0.12+7-alpine-r0, mixed mode) ``` -- 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] Tibor17 commented on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024732489 @sman-81 I can confirm [the plugin](https://repo1.maven.org/maven2/org/javacc/plugin/javacc-maven-plugin/3.0.3/) was maintained in 2020 and 2021. The Codehaus plugin was last time released in 2009. Feel free to open a new PR regarding the new plugin as a substitute of codehaus plugin. -- 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] (MDEP-732) unpack - artifactItem type attribute ignored
[
https://issues.apache.org/jira/browse/MDEP-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483991#comment-17483991
]
Arjan Tijms commented on MDEP-732:
--
Just a ping, any updates here?
> unpack - artifactItem type attribute ignored
>
>
> Key: MDEP-732
> URL: https://issues.apache.org/jira/browse/MDEP-732
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
>Affects Versions: 3.1.2
>Reporter: Zoltán Forgó
>Priority: Major
>
> If an existing artifact which has other types (e.g. test-jar) needs to be
> unpacked the type attribute is getting ignored. Always jar type used.
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.1.2
>
>
> share-tests
> generate-test-sources
>
> unpack
>
>
>
>
> io.github.zforgo.stackoverflow
> shared-tests
> 0.1.0-SNAPSHOT
> test-jar
>
> ${project.build.directory}/alternateLocation
>
>
>
>
>
>
> {code}
> While running {{mvn install}} the log says
> {noformat}
> [INFO]
> [INFO] --- maven-dependency-plugin:3.1.2:unpack (share-tests) @ project ---
> [INFO] Configured Artifact:
> io.github.zforgo.stackoverflow:shared-tests:0.1.0-SNAPSHOT:test-jar
> [INFO] Unpacking [...]
> shared-tests/0.1.0-SNAPSHOT/shared-tests-0.1.0-SNAPSHOT.jar to [...] with
> includes "" and excludes ""
> [INFO]
> {noformat}
> It seems {{ArtifactItem}} was configured well but the {{Artifact}} is wrong.
> After some debugging it seems {{AbstractFromConfigurationMojo}} didn't set
> type attribute when creating {{Artifact}} from {{ArtifactItem}}.
> Related code:
> {code:java}
> protected Artifact getArtifact( ArtifactItem artifactItem )
> throws MojoExecutionException
> {
> Artifact artifact;
> try
> {
> // ...
> ProjectBuildingRequest buildingRequest =
> newResolveArtifactProjectBuildingRequest();
> if ( localRepositoryDirectory != null )
> {
> buildingRequest =
> repositoryManager.setLocalRepositoryBasedir(
> buildingRequest, localRepositoryDirectory );
> }
> // Map dependency to artifact coordinate
> DefaultArtifactCoordinate coordinate = new
> DefaultArtifactCoordinate();
> coordinate.setGroupId( artifactItem.getGroupId() );
> coordinate.setArtifactId( artifactItem.getArtifactId() );
> coordinate.setVersion( artifactItem.getVersion() );
> coordinate.setClassifier( artifactItem.getClassifier() );
> final String extension;
> ArtifactHandler artifactHandler =
> artifactHandlerManager.getArtifactHandler( artifactItem.getType() );
> //...
> }
> catch ( ArtifactResolverException e )
> {
> throw new MojoExecutionException( "Unable to find/resolve
> artifact.", e );
> }
> return artifact;
> }{code}
> The {{DefaultArtifactCoordinate}} sets type to {{jar}} and there is no place
> where it was updated. Because of this wrong artifact will be unpacked.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (DOXIASITETOOLS-242) Remove all deprecated code
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-242.
-
Resolution: Fixed
Fixed with
[f0ce5f25e899de3fdce465ca52d76edaea4a0fa3|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git&a=commit&h=f0ce5f25e899de3fdce465ca52d76edaea4a0fa3].
> Remove all deprecated code
> --
>
> Key: DOXIASITETOOLS-242
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-242
> Project: Maven Doxia Sitetools
> Issue Type: Task
>Affects Versions: 1.11.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0-M1
>
>
> To be removed:
> * All Java code marked with {{@Deprecated}}
> * Unqualified ({{project.}}) project model interpolation
> * Deprecated rendering context properties: currentDate, dateRevision,
> dateFormat, FileUtils, i18n, creationDate, dateCreation
> * Usage of {{i18n}} in favor of {{ResourceTool}} ({{text}}) in Velocity
> templates
> * Incur document properties to empty string rather than {{null}} which is not
> properly handled in Velocity templates (empty string always evaluates to
> {{true}})
> {{org.apache.maven.doxia.tools.DefaultSiteTool.getRelativePath(String,
> String)}} will remain because it requires extra work to be replaced.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-doxia-sitetools] michael-o closed pull request #25: [DOXIASITETOOLS-242] Remove all deprecated code
michael-o closed pull request #25: URL: https://github.com/apache/maven-doxia-sitetools/pull/25 -- 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] (DOXIASITETOOLS-156) Fail if deprecated ${reports}, ${parentProject} or ${modules} is found
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-156.
-
Resolution: Fixed
Fixed with
[1770550840711d891460b1fdb4b4f59de7a53a30|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git&a=commit&h=1770550840711d891460b1fdb4b4f59de7a53a30].
> Fail if deprecated ${reports}, ${parentProject} or ${modules} is found
> --
>
> Key: DOXIASITETOOLS-156
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-156
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Integration Tools
>Affects Versions: 1.7
>Reporter: Herve Boutemy
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 2.0.0-M1
>
>
> we say for long that this feature is deprecated: doing a clear failure with a
> notice is easy to do and will help users update their site.xml
> we could have done a warning in DOXIASITETOOLS-163...
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DOXIASITETOOLS-156) Fail if deprecated ${reports}, ${parentProject} or ${modules} is found
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483949#comment-17483949
]
Michael Osipov commented on DOXIASITETOOLS-156:
---
Almost 6 years later this is addressed. More than enough time to fix site
descriptors.
> Fail if deprecated ${reports}, ${parentProject} or ${modules} is found
> --
>
> Key: DOXIASITETOOLS-156
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-156
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Integration Tools
>Affects Versions: 1.7
>Reporter: Herve Boutemy
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 2.0.0-M1
>
>
> we say for long that this feature is deprecated: doing a clear failure with a
> notice is easy to do and will help users update their site.xml
> we could have done a warning in DOXIASITETOOLS-163...
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-doxia-sitetools] michael-o closed pull request #24: [DOXIASITETOOLS-156] Fail if deprecated ${reports}, ${parentProject} …
michael-o closed pull request #24: URL: https://github.com/apache/maven-doxia-sitetools/pull/24 -- 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] [Updated] (SUREFIRE-1993) Failsafe fails to detect module dependencies
[
https://issues.apache.org/jira/browse/SUREFIRE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders updated SUREFIRE-1993:
--
Description:
Please see the attached project. It has three Maven modules, each defining its
own JPMS module. The *application* module depends on an interface from the
*studentservice* module, and the implementation for that interface lives in
{*}studentservice-provider{*}. The {{module-info.java}} for the
*studentservice-provider* module declares the implementation of that interface.
When you run the application using {{{}./manually.sh{}}}, it correctly loads
the *studentservice-provider* module. When you run the IT, it does not.
The application prints the module path to standard out.
>From the test script it prints:
{code:java}
application/target/application-1.jar
studentservice/target/studentservice-1.jar
studentservice-provider/target/studentservice-provider-1.jar{code}
>From the integration test, which starts the same application, it prints:
{code:java}
application/target/application-1.jar
studentservice/target/studentservice-1.jar{code}
Note how in the integration test the *studentservice-provider* is missing in
the output.
was:Please see the attached project. It has three Maven modules, each
defining its own JPMS module. When you run the application using
`./manually.sh`, it correctly loads the "provider" module. When you run the IT,
it does not.
> Failsafe fails to detect module dependencies
>
>
> Key: SUREFIRE-1993
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1993
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 3.0.0-M5
> Environment: Java 17
> Maven 4.0.0-alpha-SNAPSHOT and 3.8.4
>Reporter: Maarten Mulders
>Priority: Minor
> Attachments: reproducer.zip
>
>
> Please see the attached project. It has three Maven modules, each defining
> its own JPMS module. The *application* module depends on an interface from
> the *studentservice* module, and the implementation for that interface lives
> in {*}studentservice-provider{*}. The {{module-info.java}} for the
> *studentservice-provider* module declares the implementation of that
> interface.
> When you run the application using {{{}./manually.sh{}}}, it correctly loads
> the *studentservice-provider* module. When you run the IT, it does not.
> The application prints the module path to standard out.
> From the test script it prints:
> {code:java}
> application/target/application-1.jar
> studentservice/target/studentservice-1.jar
> studentservice-provider/target/studentservice-provider-1.jar{code}
> From the integration test, which starts the same application, it prints:
> {code:java}
> application/target/application-1.jar
> studentservice/target/studentservice-1.jar{code}
>
> Note how in the integration test the *studentservice-provider* is missing in
> the output.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SUREFIRE-1993) Failsafe fails to detect module dependencies
[ https://issues.apache.org/jira/browse/SUREFIRE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders updated SUREFIRE-1993: -- Attachment: reproducer-1.zip > Failsafe fails to detect module dependencies > > > Key: SUREFIRE-1993 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1993 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin >Affects Versions: 3.0.0-M5 > Environment: Java 17 > Maven 4.0.0-alpha-SNAPSHOT (but I'm sure if you upgrade the compiler plugin > it'll happen with 3.8.4 as well) >Reporter: Maarten Mulders >Priority: Minor > Attachments: reproducer.zip > > > Please see the attached project. It has three Maven modules, each defining > its own JPMS module. When you run the application using `./manually.sh`, it > correctly loads the "provider" module. When you run the IT, it does not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SUREFIRE-1993) Failsafe fails to detect module dependencies
[ https://issues.apache.org/jira/browse/SUREFIRE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders updated SUREFIRE-1993: -- Attachment: reproducer.zip > Failsafe fails to detect module dependencies > > > Key: SUREFIRE-1993 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1993 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin >Affects Versions: 3.0.0-M5 > Environment: Java 17 > Maven 4.0.0-alpha-SNAPSHOT (but I'm sure if you upgrade the compiler plugin > it'll happen with 3.8.4 as well) >Reporter: Maarten Mulders >Priority: Minor > Attachments: reproducer.zip > > > Please see the attached project. It has three Maven modules, each defining > its own JPMS module. When you run the application using `./manually.sh`, it > correctly loads the "provider" module. When you run the IT, it does not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SUREFIRE-1993) Failsafe fails to detect module dependencies
[ https://issues.apache.org/jira/browse/SUREFIRE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders updated SUREFIRE-1993: -- Environment: Java 17 Maven 4.0.0-alpha-SNAPSHOT and 3.8.4 was: Java 17 Maven 4.0.0-alpha-SNAPSHOT (but I'm sure if you upgrade the compiler plugin it'll happen with 3.8.4 as well) > Failsafe fails to detect module dependencies > > > Key: SUREFIRE-1993 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1993 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin >Affects Versions: 3.0.0-M5 > Environment: Java 17 > Maven 4.0.0-alpha-SNAPSHOT and 3.8.4 >Reporter: Maarten Mulders >Priority: Minor > Attachments: reproducer.zip > > > Please see the attached project. It has three Maven modules, each defining > its own JPMS module. When you run the application using `./manually.sh`, it > correctly loads the "provider" module. When you run the IT, it does not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SUREFIRE-1993) Failsafe fails to detect module dependencies
[ https://issues.apache.org/jira/browse/SUREFIRE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders updated SUREFIRE-1993: -- Attachment: (was: reproducer-1.zip) > Failsafe fails to detect module dependencies > > > Key: SUREFIRE-1993 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1993 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin >Affects Versions: 3.0.0-M5 > Environment: Java 17 > Maven 4.0.0-alpha-SNAPSHOT (but I'm sure if you upgrade the compiler plugin > it'll happen with 3.8.4 as well) >Reporter: Maarten Mulders >Priority: Minor > Attachments: reproducer.zip > > > Please see the attached project. It has three Maven modules, each defining > its own JPMS module. When you run the application using `./manually.sh`, it > correctly loads the "provider" module. When you run the IT, it does not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SUREFIRE-1993) Failsafe fails to detect module dependencies
[ https://issues.apache.org/jira/browse/SUREFIRE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders updated SUREFIRE-1993: -- Attachment: (was: reproducer.zip) > Failsafe fails to detect module dependencies > > > Key: SUREFIRE-1993 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1993 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin >Affects Versions: 3.0.0-M5 > Environment: Java 17 > Maven 4.0.0-alpha-SNAPSHOT (but I'm sure if you upgrade the compiler plugin > it'll happen with 3.8.4 as well) >Reporter: Maarten Mulders >Priority: Minor > Attachments: reproducer.zip > > > Please see the attached project. It has three Maven modules, each defining > its own JPMS module. When you run the application using `./manually.sh`, it > correctly loads the "provider" module. When you run the IT, it does not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-toolchains-plugin] michael-o commented on pull request #8: [MTOOLCHAINS-31] - Not threadsafe for parallel execution
michael-o commented on pull request #8: URL: https://github.com/apache/maven-toolchains-plugin/pull/8#issuecomment-1024438537 And this will make it threadsafe? -- 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] sman-81 commented on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
sman-81 commented on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024430602 ## re: IDE Setup In Eclipse, right-click on project -> Maven -> Select Maven Profiles ..., pick `ide-development` Despite this still 194 errors. Eclipse keeps building in an endless loop. CPU usage is high. A major source of errors is missing `GroupMatcherParser` which gets generated into `surefire-grouper/target/generated-sources/javacc/org/apache/maven/surefire/group/parse/GroupMatcherParser.java` (in Eclipse) Thus this source is not part of any source folder. The POM relies on `org.codehaus.mojo:javacc-maven-plugin`. This plugin is ancient ... We should consider moving to `org.javacc.plugin:javacc-maven-plugin` and placing generated sources in a different location. Maybe `build-helper-maven-plugin` can help in a solution. Anyways, any pointers how to set up in Eclipse are welcome. -- 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-1993) Failsafe fails to detect module dependencies
Maarten Mulders created SUREFIRE-1993: - Summary: Failsafe fails to detect module dependencies Key: SUREFIRE-1993 URL: https://issues.apache.org/jira/browse/SUREFIRE-1993 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin Affects Versions: 3.0.0-M5 Environment: Java 17 Maven 4.0.0-alpha-SNAPSHOT (but I'm sure if you upgrade the compiler plugin it'll happen with 3.8.4 as well) Reporter: Maarten Mulders Attachments: reproducer.zip Please see the attached project. It has three Maven modules, each defining its own JPMS module. When you run the application using `./manually.sh`, it correctly loads the "provider" module. When you run the IT, it does not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-mvnd] ppalaga commented on issue #596: mvnd doesn't work in alpine
ppalaga commented on issue #596: URL: https://github.com/apache/maven-mvnd/issues/596#issuecomment-1024396358 Maybe it is due to the way how executables are found on Linux? You may want to try to add the directory containing `mvnd` executable to `PATH` or you may try to call `mvnd` with the full path. -- 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] (MTOOLCHAINS-31) Not threadsafe for parallel execution
[
https://issues.apache.org/jira/browse/MTOOLCHAINS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483839#comment-17483839
]
Thomas Reinhardt commented on MTOOLCHAINS-31:
-
I marked the plugin as threadSafe:
[https://github.com/apache/maven-toolchains-plugin/pull/8]
this is trivially correct, as the plugin has the default InstantiationStrategy
(PER_LOOKUP). Also no static variables exist so no state could be shared across
executions.
> Not threadsafe for parallel execution
> -
>
> Key: MTOOLCHAINS-31
> URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-31
> Project: Maven Toolchains Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
> Environment: maven 3.6.1
>Reporter: Hüseyin Kartal
>Priority: Major
>
> Running maven in parallel mode result in following output which also includes
> TOOLCHAINS plugin.
> {noformat}
> *
> * Your build is requesting parallel execution, but project *
> * contains the following plugin(s) that have goals not marked *
> * as @threadSafe to support parallel building. *
> * While this /may/ work fine, please look for plugin updates*
> * and/or request plugins be made thread-safe. *
> * If reporting an issue, report it against the plugin in*
> * question, not against maven-core *
> *
> The following plugins are not marked @threadSafe in Application component:
> core:
> com.sun.xml.ws:jaxws-maven-plugin:2.3.2
> org.apache.maven.plugins:maven-jxr-plugin:3.0.0
> org.apache.maven.plugins:maven-toolchains-plugin:3.0.0
> Enable debug to see more precisely which goals are not marked @threadSafe.
> *{noformat}
> Toolchains plugin should made and/or marked threadSafe.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SUREFIRE-1992) Increase output length of test errors/failures in summary
[
https://issues.apache.org/jira/browse/SUREFIRE-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Spann updated SUREFIRE-1992:
---
Description:
A {{StackTraceWriter}} writes test failures and errors to stderr. The output is
abbreviated to 78 characters and suffixed by three dots. It is often difficult
if not impossible to quickly understand the test failure due to this
abbreviation.
This JUnit test:
{code:java}
class FailingTest {
@Test
void throwsRTException() {
throw new
RuntimeException("123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.");
}
}
{code}
results in following output:
{code:java}
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] FailingTest.throwsRTException:12 Runtime
123456789.123456789.123456789.1234567...
[INFO]
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0{code}
The abbreviation is done in class {{SmartStackTraceParser}} (and/or
{{{}LegacyPojoStackTraceWriter{}}}). Both have:
{code:java}
MAX_LINE_LENGTH = 77{code}
The actual output is 78 characters long ;)
This behavior is true for all errors/failures except:
AssertionError, AssertionFailedError, ComparisonFailure and org.opentest4j.*
Why these should receive special treatment is not obvious.
was:
A {{StackTraceWriter}} writes test failures and errors to stderr. The output is
abbreviated to 78 characters and suffixed by three dots. It is often difficult
if not impossible to quickly understand the test failure due to this
abbreviation.
This JUnit5 test:
{code:java}
class FailingTest {
@Test
void throwsRTException() {
throw new
RuntimeException("123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.");
}
}
{code}
results in this output:
{code:java}
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] FailingTest.throwsRTException:12 Runtime
123456789.123456789.123456789.1234567...
[INFO]
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0{code}
The abbreviation is done in class {{SmartStackTraceParser}} (and/or
{{{}LegacyPojoStackTraceWriter{}}}). Both have:
{code:java}
MAX_LINE_LENGTH = 77{code}
The actual output is 78 characters long ;)
This behavior is true for all errors/failures except:
AssertionError, AssertionFailedError, ComparisonFailure and org.opentest4j.*
Why these should receive special treatment is not obvious.
> Increase output length of test errors/failures in summary
> -
>
> Key: SUREFIRE-1992
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1992
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Markus Spann
>Priority: Minor
>
> A {{StackTraceWriter}} writes test failures and errors to stderr. The output
> is abbreviated to 78 characters and suffixed by three dots. It is often
> difficult if not impossible to quickly understand the test failure due to
> this abbreviation.
> This JUnit test:
> {code:java}
> class FailingTest {
> @Test
> void throwsRTException() {
> throw new
> RuntimeException("123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.");
> }
> }
> {code}
> results in following output:
> {code:java}
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] FailingTest.throwsRTException:12 Runtime
> 123456789.123456789.123456789.1234567...
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0{code}
> The abbreviation is done in class {{SmartStackTraceParser}} (and/or
> {{{}LegacyPojoStackTraceWriter{}}}). Both have:
> {code:java}
> MAX_LINE_LENGTH = 77{code}
> The actual output is 78 characters long ;)
> This behavior is true for all errors/failures except:
> AssertionError, AssertionFailedError, ComparisonFailure and org.opentest4j.*
> Why these should receive special treatment is not obvious.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-mvnd] shalousun opened a new issue #596: mvnd doesn't work in alpine
shalousun opened a new issue #596: URL: https://github.com/apache/maven-mvnd/issues/596 I installed mvnd into the alpine image (docker pull jenkins/inbound-agent:latest-alpine-jdk11) and it cannot be executed. The error message is mvnd not found. But I can view the mvnd installation file through the ls command. -- 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] Tibor17 commented on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024326337 @sman-81 yes, we will add it to README. Let's wait fo the CI. -- 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] sman-81 edited a comment on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
sman-81 edited a comment on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024310461 > we should add instruction to readme ... that would be helpful @Tibor17 My latest commit limits error/failure messages to first line. Also added a new test. -- 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] sman-81 commented on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
sman-81 commented on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024310461 > we should add instruction to readme ... that would be helpful @Tibor17 My latest commit limits error/failure messages to first line. Also added a new test. -- 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] slawekjaranowski commented on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
slawekjaranowski commented on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024283894 we should add instruction to readme ... -- 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-resolver] gnodet commented on pull request #147: Auto formatting
gnodet commented on pull request #147: URL: https://github.com/apache/maven-resolver/pull/147#issuecomment-1024281630 > I like it, but could we somehow share this setup (at least the huge config)? The amount of added LOC is not trivial, and have it copy-pasted over all reposes seems like a nightmare. Agreed. I suppose the best location would be https://github.com/apache/maven-shared-resources/tree/master/src/main/resources/config ? -- 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-compiler-plugin] dependabot[bot] opened a new pull request #83: Bump mockito-core from 4.2.0 to 4.3.1
dependabot[bot] opened a new pull request #83: URL: https://github.com/apache/maven-compiler-plugin/pull/83 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.2.0 to 4.3.1. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.3.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.3.1 2022-01-25 - https://github.com/mockito/mockito/compare/v4.3.0...v4.3.1";>1 commit(s) by Stefano Cordio Add mockito-core to the BOM [(https://github-redirect.dependabot.com/mockito/mockito/issues/2550";>#2550)](https://github-redirect.dependabot.com/mockito/mockito/pull/2550";>mockito/mockito#2550) v4.3.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.3.0 2022-01-24 - https://github.com/mockito/mockito/compare/v4.2.0...v4.3.0";>20 commit(s) by Andrew Kozel, John Pyeatt, Liam Miller-Cushon, Thomas Keller, Tim van der Lippe, dependabot[bot], temp-droid Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2489";>#2489 : Fixed issue related to exceptions thrown from the nested spies [(https://github-redirect.dependabot.com/mockito/mockito/issues/2546";>#2546)](https://github-redirect.dependabot.com/mockito/mockito/pull/2546";>mockito/mockito#2546) Issue 2544 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2545";>#2545)](https://github-redirect.dependabot.com/mockito/mockito/pull/2545";>mockito/mockito#2545) Bump versions.bytebuddy from 1.12.6 to 1.12.7 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2543";>#2543)](https://github-redirect.dependabot.com/mockito/mockito/pull/2543";>mockito/mockito#2543) Bump com.diffplug.spotless from 6.1.2 to 6.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2542";>#2542)](https://github-redirect.dependabot.com/mockito/mockito/pull/2542";>mockito/mockito#2542) Bump material from 1.4.0 to 1.5.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2541";>#2541)](https://github-redirect.dependabot.com/mockito/mockito/pull/2541";>mockito/mockito#2541) Bump appcompat from 1.4.0 to 1.4.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2539";>#2539)](https://github-redirect.dependabot.com/mockito/mockito/pull/2539";>mockito/mockito#2539) Bump com.diffplug.spotless from 6.1.1 to 6.1.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2536";>#2536)](https://github-redirect.dependabot.com/mockito/mockito/pull/2536";>mockito/mockito#2536) Remove an @link [(https://github-redirect.dependabot.com/mockito/mockito/issues/2535";>#2535)](https://github-redirect.dependabot.com/mockito/mockito/pull/2535";>mockito/mockito#2535) Bump com.diffplug.spotless from 6.1.0 to 6.1.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2534";>#2534)](https://github-redirect.dependabot.com/mockito/mockito/pull/2534";>mockito/mockito#2534) Bump com.github.ben-manes.versions from 0.40.0 to 0.41.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2533";>#2533)](https://github-redirect.dependabot.com/mockito/mockito/pull/2533";>mockito/mockito#2533) Bump assertj-core from 3.21.0 to 3.22.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2531";>#2531)](https://github-redirect.dependabot.com/mockito/mockito/pull/2531";>mockito/mockito#2531) Bump com.github.ben-manes.versions from 0.39.0 to 0.40.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2529";>#2529)](https://github-redirect.dependabot.com/mockito/mockito/pull/2529";>mockito/mockito#2529) Bump com.diffplug.spotless from 6.0.5 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2527";>#2527)](https://github-redirect.dependabot.com/mockito/mockito/pull/2527";>mockito/mockito#2527) Bump kotlinx-coroutines-core from 1.5.2-native-mt to 1.6.0-native-mt [(https://github-redirect.dependabot.com/mockito/mockito/issues/2526";>#2526)](https://github-redirect.dependabot.com/mockito/mockito/pull/2526";>mockito/mockito#2526) Bump versions.bytebuddy from 1.12.5 to 1.12.6 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2524";>#2524)](https://github-redirect.dependabot.com/mockito/mockito/pull/2524";>mockito/mockito#2524) Bump com.diffplug.spotless from 6.0.4 to 6.0.5 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2520";>#2520)](https://github-redirect.dependabot.com/mockito/mockito/pull/2520";>mockito/mockito#2520) Bump versions.bytebuddy from 1.12.4 to 1.12.5 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2519";>#2519)](https://github-redirect.dependabot.com/mockito/mockito/pull/2519";>mockito/mockito#2519) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2510";>#2510: Remove ExpectedException from internal test suite [(https://github-redirect.dependabo
[GitHub] [maven-surefire] Tibor17 commented on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024280276 @sman-81 Enable the profile `ide-development` and install the module `surefire-shared-utils` and reimport the project in your IDE. Then you can run the tests in the IDE and compile. -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794544268 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); if ( throwable.getTarget() instanceof AssertionError ) +if ( throwable.getTarget() instanceof AssertionError Review comment: The exception message may have multiple lines. They may produce a huge report on the console. My advice is to print only the first line if exists. -- 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] sman-81 commented on pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
sman-81 commented on pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#issuecomment-1024261368 Thanks for your feedback! I couldn't get the project to compile in Eclipse, but should have at least built it with Maven on the command line. The latest commit should address all the issues you raised with my pr. -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794536083 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); if ( throwable.getTarget() instanceof AssertionError ) +if ( throwable.getTarget() instanceof AssertionError Review comment: @sman-81 I am not sure why the author of `smartTrimmedStackTrace()` ignores other exceptions. Try to open a new PR and try to turn the IF statement to: `if ( throwable.getTarget() != null )` I want to know if the old code makes strong sense to the tests. -- 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-resolver] cstamas commented on pull request #147: Auto formatting
cstamas commented on pull request #147: URL: https://github.com/apache/maven-resolver/pull/147#issuecomment-1024259405 I like it, but could we somehow share this setup (at least the huge config)? The amount of added LOC is not trivial, and have it copy-pasted over all reposes seems like a nightmare. -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794528075 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); if ( throwable.getTarget() instanceof AssertionError ) +if ( throwable.getTarget() instanceof AssertionError Review comment: Feel free to open a new Jira and PR with acceptance of asserions exceptions. -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794518079 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); Review comment: Hint: try to use Java 1.8 `Optional`. -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452:
URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794516311
##
File path:
surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java
##
@@ -81,10 +79,15 @@ public String smartTrimmedStackTrace()
result.append( "#" );
result.append( testMethod );
SafeThrowable throwable = getThrowable();
+final String excClassName = throwable.getTarget().getClass().getName();
if ( throwable.getTarget() instanceof AssertionError )
+if ( throwable.getTarget() instanceof AssertionError
+|| "junit.framework.AssertionFailedError".equals( excClassName
)
+|| "junit.framework.ComparisonFailure".equals( excClassName )
+|| excClassName.startsWith( "org.opentest4j." ) )
{
result.append( " " );
-result.append( getTruncatedMessage( throwable.getMessage(),
MAX_LINE_LENGTH - result.length() ) );
+result.append( throwable.getMessage() );
Review comment:
See the previous code.
Why you did not see `null` in the console log?
You are missing the null check here!
--
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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794516999 ## File path: surefire-providers/common-java5/src/main/java/org/apache/maven/surefire/report/SmartStackTraceParser.java ## @@ -149,7 +147,7 @@ public String getString() result.append( rootIsInclass() ? " " : " » " ) .append( toMinimalThrowableMiniMessage( excType ) ); -result.append( truncateMessage( msg, MAX_LINE_LENGTH - result.length() ) ); +result.append( msg ); Review comment: null check -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452:
URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794516788
##
File path:
surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java
##
@@ -93,7 +96,7 @@ public String smartTrimmedStackTrace()
{
result.append( " " );
result.append( target.getClass().getSimpleName() );
-result.append( getTruncatedMessage( throwable.getMessage(),
MAX_LINE_LENGTH - result.length() ) );
+result.append( throwable.getMessage() );
Review comment:
Again missing the null check.
--
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] sman-81 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
sman-81 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794514561 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); if ( throwable.getTarget() instanceof AssertionError ) +if ( throwable.getTarget() instanceof AssertionError Review comment: unintentional. I'll amend the PR -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794513922 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); Review comment: This may throw NPE. -- 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] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794513496 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); if ( throwable.getTarget() instanceof AssertionError ) +if ( throwable.getTarget() instanceof AssertionError Review comment: This section of code is suited for another Jira ticket. The way we split the fix purpose we can better separate commits per issue in the git history. -- 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-antrun-plugin] dependabot[bot] opened a new pull request #40: Bump xmlunit-matchers from 2.8.4 to 2.9.0
dependabot[bot] opened a new pull request #40: URL: https://github.com/apache/maven-antrun-plugin/pull/40 Bumps [xmlunit-matchers](https://github.com/xmlunit/xmlunit) from 2.8.4 to 2.9.0. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases";>xmlunit-matchers's releases. XMLUnit for Java 2.9.0 The major change of XMLUnit for Java 2.9.0 is the addition of a new module xmlunit-jakarta-jaxb-impl that can be used in addition to xmlunit-core when you want to use the Jakarta XML Binding API in version 3. For details please see the https://github.com/xmlunit/user-guide/wiki/JAXB";>user's guide. The full list of changes of XMLUnit for Java 2.9.0 is: added a new module xmlunit-jakarta-jaxb-impl that makes Input.fromJaxb use jakarta.xml.bind rather than javax.xml.bind. For more details see the https://github.com/xmlunit/user-guide/wiki/JAXB";>User's Guide. This change is not fully backwards compatible. The JaxbBuilder class has become abstract and the withMarshaller method has changed its signature. For most cases the change will not be noticed and for almost all other cases it should be enough to re-compile your code against XMLUnit 2.9.x. Issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/227";>#227 and PR https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/247";>#247 added NodeFilters#satisfiesAll and satifiesAny methods to make it easier to combine multiple node filters. added to simplify the use case of https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/249";>#249 Changelog Sourced from https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md";>xmlunit-matchers's changelog. XMLUnit for Java 2.9.0 - /Released 2022-01-25/ added a new module xmlunit-jakarta-jaxb-impl that makes Input.fromJaxb use jakarta.xml.bind rather than javax.xml.bind. For more details see the https://github.com/xmlunit/user-guide/wiki/JAXB";>User's Guide. This change is not fully backwards compatible. The JaxbBuilder class has become abstract and the withMarshaller method has changed its signature. For most cases the change will not be noticed and for almost all other cases it should be enough to re-compile your code against XMLUnit 2.9.x. Issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/227";>#227 and PR https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/247";>#247 added NodeFilters#satisfiesAll and satifiesAny methods to make it easier to combine multiple node filters. added to simplify the use case of https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/249";>#249 Commits https://github.com/xmlunit/xmlunit/commit/cc4242d06d9dee45abbb5ddaea28d64dd9b0";>cc4242d XMLUnit 2.9.0 https://github.com/xmlunit/xmlunit/commit/e8420e80ed5ff60236d09f2950f5e0c5d8fcc59d";>e8420e8 name profile properly https://github.com/xmlunit/xmlunit/commit/fc9d2cb8e4fe34669bd70c4f0038928b1b2058c4";>fc9d2cb Java9 and 10 seem to require the JAXB RI https://github.com/xmlunit/xmlunit/commit/98444ee320b4cfc7d8615e5638638c50d9b750de";>98444ee I should have known which parameter the shell script expects :-) https://github.com/xmlunit/xmlunit/commit/7638c0787cfcb73514b80d7d13a63e18d5a654c5";>7638c07 trigger Travis CI build https://github.com/xmlunit/xmlunit/commit/4d9a85438bc79c19ecb3348f4505b63de739b5bf";>4d9a854 NodeFilters.satisfyAll and .satisfyAny https://github.com/xmlunit/xmlunit/commit/eb7cc2c042e25273b8901ca425833c04bcdc8f3f";>eb7cc2c explicitly document the withFoo methods are not additive https://github.com/xmlunit/xmlunit/commit/64e55a33c658bc9d902b036f56a2d839fd63fa1d";>64e55a3 JAXB compatibility tests https://github.com/xmlunit/xmlunit/commit/51ee34b6eaeb99cf3668825a6321b501fd64668d";>51ee34b Merge pull request https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/247";>#247 from xmlunit/jakarta-jaxb https://github.com/xmlunit/xmlunit/commit/528ba4f931a143835f540b514aedddee0a350744";>528ba4f document JAXB change Additional commits viewable in https://github.com/xmlunit/xmlunit/compare/v2.8.4...v2.9.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot
[jira] [Updated] (SUREFIRE-1992) Increase output length of test errors/failures in summary
[
https://issues.apache.org/jira/browse/SUREFIRE-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1992:
---
Issue Type: Improvement (was: Task)
> Increase output length of test errors/failures in summary
> -
>
> Key: SUREFIRE-1992
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1992
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Markus Spann
>Priority: Minor
>
> A {{StackTraceWriter}} writes test failures and errors to stderr. The output
> is abbreviated to 78 characters and suffixed by three dots. It is often
> difficult if not impossible to quickly understand the test failure due to
> this abbreviation.
> This JUnit5 test:
> {code:java}
> class FailingTest {
> @Test
> void throwsRTException() {
> throw new
> RuntimeException("123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.");
> }
> }
> {code}
> results in this output:
> {code:java}
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] FailingTest.throwsRTException:12 Runtime
> 123456789.123456789.123456789.1234567...
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0{code}
> The abbreviation is done in class {{SmartStackTraceParser}} (and/or
> {{{}LegacyPojoStackTraceWriter{}}}). Both have:
> {code:java}
> MAX_LINE_LENGTH = 77{code}
> The actual output is 78 characters long ;)
> This behavior is true for all errors/failures except:
> AssertionError, AssertionFailedError, ComparisonFailure and org.opentest4j.*
> Why these should receive special treatment is not obvious.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7399) Intermittent failures on Java 18-EA / 19-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483772#comment-17483772
]
Dmitry Bedrin commented on MNG-7399:
I was in process of updating JIRA - indeed the errors are different.
I have never had a successful build on Windows / x86 / Java 18+ while same
build on Windows x64 or on Linux x86 is 100% fine.
> Intermittent failures on Java 18-EA / 19-EA on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea
> both 64 bit and 32 bit (where available).
>
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed
> that builds on Windows *32bit* are failing with errors like these:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
> [Help 1]{noformat}
>
> Another example with stack trace from compiler plugin (other plugins fail as
> well):
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:577)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
> (DefaultMavenPluginManager.java:644)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
> (DefaultMavenPluginManager.java:597)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:124)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
[jira] [Updated] (MNG-7399) Intermittent failures on Java 18-EA / 19-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Description:
I'm maintaining open-source project (multi-module Maven) and my CI/CD builds it
on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea both 64
bit and 32 bit (where available).
After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed that
builds on Windows *32bit* are failing with errors like these:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
[Help 1]{noformat}
Another example with stack trace from compiler plugin (other plugins fail as
well):
{noformat}[INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
sniffy ---
[DEBUG] Dependency collection stats {ConflictMarker.analyzeTime=9500,
ConflictMarker.markTime=9500, ConflictMarker.nodeCount=17,
ConflictIdSorter.graphTime=5100, ConflictIdSorter.topsortTime=8400,
ConflictIdSorter.conflictIdCount=12, ConflictIdSorter.conflictIdCycleCount=0,
ConflictResolver.totalTime=60300, ConflictResolver.conflictItemCount=17,
DefaultDependencyCollector.collectTime=1351500,
DefaultDependencyCollector.transformTime=101700}
[DEBUG] org.apache.maven.plugins:maven-compiler-plugin:jar:3.9.0
[DEBUG]org.apache.maven.shared:maven-shared-utils:jar:3.3.4:compile
[DEBUG] commons-io:commons-io:jar:2.6:compile
[DEBUG]org.apache.maven.shared:maven-shared-incremental:jar:1.1:compile
[DEBUG]
org.codehaus.plexus:plexus-component-annotations:jar:2.0.0:compile (version
managed from default)
[DEBUG]org.codehaus.plexus:plexus-java:jar:1.1.0:compile
[DEBUG] org.ow2.asm:asm:jar:9.2:compile
[DEBUG] com.thoughtworks.qdox:qdox:jar:2.0.1:compile (version managed
from default)
[DEBUG]org.codehaus.plexus:plexus-compiler-api:jar:2.9.0:compile
[DEBUG] org.codehaus.plexus:plexus-utils:jar:3.3.0:compile
[DEBUG]org.codehaus.plexus:plexus-compiler-manager:jar:2.9.0:compile
[DEBUG]org.codehaus.plexus:plexus-compiler-javac:jar:2.9.0:runtime
[DEBUG] Created new class realm
plugin>org.apache.maven.plugins:maven-compiler-plugin:3.9.0--107150504
[DEBUG] Importing foreign packages into class realm
plugin>org.apache.maven.plugins:maven-compiler-plugin:3.9.0--107150504
[DEBUG] Imported: < project>io.sniffy:sniffy:3.1.13-SNAPSHOT
[DEBUG] Populating class realm
plugin>org.apache.maven.plugins:maven-compiler-plugin:3.9.0--107150504
[DEBUG] Included: org.apache.maven.plugins:maven-compiler-plugin:jar:3.9.0
[DEBUG] Included: org.apache.maven.shared:maven-shared-utils:jar:3.3.4
[DEBUG] Included: commons-io:commons-io:jar:2.6
[DEBUG] Included: org.apache.maven.shared:maven-shared-incremental:jar:1.1
[DEBUG] Included: org.codehaus.plexus:plexus-component-annotations:jar:2.0.0
[DEBUG] Included: org.codehaus.plexus:plexus-java:jar:1.1.0
[DEBUG] Included: org.ow2.asm:asm:jar:9.2
[DEBUG] Included: com.thoughtworks.qdox:qdox:jar:2.0.1
[DEBUG] Included: org.codehaus.plexus:plexus-compiler-api:jar:2.9.0
[DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:3.3.0
[DEBUG] Included: org.codehaus.plexus:plexus-compiler-manager:jar:2.9.0
[DEBUG] Included: org.codehaus.plexus:plexus-compiler-javac:jar:2.9.0
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile from plugin realm
ClassRealm[plugin>org.apache.maven.plugins:maven-compiler-plugin:3.9.0--107150504,
parent: jdk.internal.loader.ClassLoaders$AppClassLoader@1ebdb06]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile' with basic
configurator -->
[DEBUG] (f) basedir = C:\work\github\sniffy\sniffy
[DEBUG] (f) compilePath = []
[DEBUG] (f) compileSourceRoots = []
[DEBUG] (f) compilerId = javac
[DEBUG] (f) debug = true
[DEBUG] (f) encoding = UTF-8
[DEBUG] (f) failOnError = true
[DEBUG] (f) failOnWarning = false
[DEBUG] (f) forceJavacCompilerUse = false
[DEBUG] (f) fork = false
[DEBUG] (f) generatedSourcesDirectory =
C:\work\github\sniffy\sniffy\${project.build.directory}\generated-sources\annotations
[DEBUG] (f) mojoExecution =
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile {execution:
default-compile}
[DEBUG] (f) optimize = false
[DEBUG] (f) parameters = false
[DEBUG] (f) project = MavenProject: io.sniffy:sniffy:3.1.13-SNAPSHOT @
C:\work\github\sniffy\sniffy\pom.xml
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@1033eac
[DEBUG] (f) showDeprecation = false
[DEBUG] (f) showWarnings = false
[DEBUG] (f) skipMultiThreadWarning = false
[DEBUG] (f) source = 1.9
[DEBUG] (f) staleMillis = 0
[DEBUG] (s) target = 1.9
[DEBUG] (f) useIncrementalCompilation = true
[DEBUG
[jira] [Updated] (MNG-7399) Intermittent failures on Java 18-EA / 19-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Summary: Intermittent failures on Java 18-EA / 19-EA on Windows x86
(32-bit) (was: Intermittent failures on Java 18-EA on Windows x86 (32-bit))
> Intermittent failures on Java 18-EA / 19-EA on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea
> both 64 bit and 32 bit (where available).
>
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed
> that builds on Windows *32bit* are failing with errors like these:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
> [Help 1]{noformat}
>
> Another example with stack trace from compiler plugin (other plugins fail as
> well):
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:577)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
> (DefaultMavenPluginManager.java:644)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
> (DefaultMavenPluginManager.java:597)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:124)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilde
[jira] [Updated] (MNG-7399) Intermittent failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Description:
I'm maintaining open-source project (multi-module Maven) and my CI/CD builds it
on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea both 64
bit and 32 bit (where available).
After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed that
builds on Windows *32bit* are failing with errors like these:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
[Help 1]{noformat}
Another example with stack trace from compiler plugin (other plugins fail as
well):
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:577)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
(DefaultMavenPluginManager.java:644)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
(DefaultMavenPluginManager.java:597)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:124)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(
[jira] [Updated] (MNG-7399) Intermittent failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Summary: Intermittent failures on Java 18-EA on Windows x86 (32-bit) (was:
Intermittent "The parameters are missing or invalid" failures on Java 18-EA on
Windows x86 (32-bit))
> Intermittent failures on Java 18-EA on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea
> both 64 bit and 32 bit (where available).
>
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed
> that builds on Windows *32bit* are failing with errors like these:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
> [Help 1]{noformat}
>
> Another example with stack trace from compiler plugin (other plugins fail as
> well):
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:577)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
> (DefaultMavenPluginManager.java:644)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
> (DefaultMavenPluginManager.java:597)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:124)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (Life
[GitHub] [maven-surefire] Tibor17 merged pull request #451: Bump xmlunit-core from 2.6.0 to 2.9.0
Tibor17 merged pull request #451: URL: https://github.com/apache/maven-surefire/pull/451 -- 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] [Updated] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Description:
I'm maintaining open-source project (multi-module Maven) and my CI/CD builds it
on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea both 64
bit and 32 bit (where available).
After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed that
builds on Windows *32bit* are failing with errors like these:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
[Help 1]{noformat}
Another example with stack trace from compiler plugin (other plugins fail as
well):
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:577)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
(DefaultMavenPluginManager.java:644)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
(DefaultMavenPluginManager.java:597)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:124)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(
[GitHub] [maven-surefire] Tibor17 commented on a change in pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
Tibor17 commented on a change in pull request #452: URL: https://github.com/apache/maven-surefire/pull/452#discussion_r794487726 ## File path: surefire-api/src/main/java/org/apache/maven/surefire/api/report/LegacyPojoStackTraceWriter.java ## @@ -81,10 +79,15 @@ public String smartTrimmedStackTrace() result.append( "#" ); result.append( testMethod ); SafeThrowable throwable = getThrowable(); +final String excClassName = throwable.getTarget().getClass().getName(); if ( throwable.getTarget() instanceof AssertionError ) +if ( throwable.getTarget() instanceof AssertionError Review comment: This `if ( ... )` is a pure trojan horse. -- 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] Tibor17 commented on a change in pull request #445: [SUREFIRE-1962] Unit test for ProviderInfo#isApplicable
Tibor17 commented on a change in pull request #445:
URL: https://github.com/apache/maven-surefire/pull/445#discussion_r794479343
##
File path:
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/AbstractSurefireMojoProvidersInfoTest.java
##
@@ -0,0 +1,172 @@
+package org.apache.maven.plugin.surefire;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.maven.artifact.Artifact;
+import org.apache.maven.artifact.DefaultArtifact;
+import org.apache.maven.surefire.providerapi.ProviderInfo;
+import org.junit.Test;
+import org.junit.runner.RunWith;
+import org.mockito.Spy;
+import org.mockito.junit.MockitoJUnitRunner;
+
+import static org.fest.assertions.Assertions.assertThat;
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.verifyNoMoreInteractions;
+
+/**
+ * Testing providerInfo applicable behavior.
+ */
+@RunWith( MockitoJUnitRunner.class )
+public class AbstractSurefireMojoProvidersInfoTest
+{
+
+@Spy
+private AbstractSurefireMojo mojo;
+
+@Test
+public void defaultProviderAreAlwaysAvailable()
+{
+ProviderInfo providerInfo = mojo.new JUnit3ProviderInfo();
+assertThat( providerInfo.isApplicable() ).isTrue();
+}
+
+@Test
+public void dynamicProviderAreAlwaysApplicable()
+{
+ProviderInfo providerInfo = mojo.new DynamicProviderInfo( "test" );
+assertThat( providerInfo.isApplicable() ).isTrue();
+}
+
+@Test
+public void testNgProviderApplicable()
+{
+Artifact testNg = mock( Artifact.class );
+ProviderInfo providerInfo = mojo.new TestNgProviderInfo( testNg );
+
+assertThat( providerInfo.isApplicable() ).isTrue();
+
+// no interaction with artifact only reference are checked
+verifyNoMoreInteractions( testNg );
+}
+
+@Test
+public void testNgProviderNotApplicable()
+{
+ProviderInfo providerInfo = mojo.new TestNgProviderInfo( null );
+assertThat( providerInfo.isApplicable() ).isFalse();
+}
+
+//surefire-junit-platform
+
+@Test
+public void jUnitPlatformProviderApplicable()
+{
+Artifact junitPlatform = mock( Artifact.class );
+ProviderInfo providerInfo = mojo.new JUnitPlatformProviderInfo(
junitPlatform, aTestClassPath() );
+
+assertThat( providerInfo.isApplicable() ).isTrue();
+
+// no interaction with artifact only reference are checked
+verifyNoMoreInteractions( junitPlatform );
+}
+
+@Test
+public void jUnitPlatformProviderNotApplicable()
+{
+ProviderInfo providerInfo = mojo.new JUnitPlatformProviderInfo( null,
aTestClassPath() );
+assertThat( providerInfo.isApplicable() ).isFalse();
+}
+
+// surefire-junit4
+
+@Test
+public void jUnit4ProviderNullArtifacts()
+{
+ProviderInfo providerInfo = mojo.new JUnit4ProviderInfo( null, null );
+assertThat( providerInfo.isApplicable() ).isFalse();
+}
+
+@Test
+public void jUnit4ProviderOnlyJunitDepArtifact()
+{
+Artifact junitDep = mock( Artifact.class );
+ProviderInfo providerInfo = mojo.new JUnit4ProviderInfo( null,
junitDep );
+
+assertThat( providerInfo.isApplicable() ).isTrue();
+
+// no interaction with artifact only reference are checked
+verifyNoMoreInteractions( junitDep );
+}
+
+
+@Test
+public void jUnit4ProviderJunit3WithJDepArtifact()
+{
+Artifact junit = aArtifact( "3.8.1" );
+Artifact junitDep = mock( Artifact.class );
+
+ProviderInfo providerInfo = mojo.new JUnit4ProviderInfo( junit,
junitDep );
+
+// ??? only existing for junitDep in any version is checked
+assertThat( providerInfo.isApplicable() ).isTrue();
+
+// no interaction with artifact only reference are checked
+verifyNoMoreInteractions( junitDep );
+}
+
+@Test
+public void jUnit4ProviderJunit3AsDependencyArtifact()
+{
+Artifact junit = aArtifact( "3.8.1" );
+ProviderInfo providerInfo = mojo.new JUnit4ProviderInfo( junit, null );
+assertThat( providerInfo.isApplicable() ).isFalse();
+}
+
+@Test
+
[jira] [Updated] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Description:
I'm maintaining open-source project (multi-module Maven) and my CI/CD builds it
on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea both 64
bit and 32 bit (where available).
After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed that
builds on Windows *32bit* are failing with errors like these:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
[Help 1]{noformat}
Another example with stack trace from compiler plugin (other plugins fail as
well):
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:577)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
(DefaultMavenPluginManager.java:644)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
(DefaultMavenPluginManager.java:597)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:124)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(
[jira] [Commented] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483752#comment-17483752
]
Tamás Cservenák commented on MNG-7399:
--
Um, in the shade output you have
{noformat}
Caused by: java.lang.NullPointerException: Cannot invoke
"java.io.File.mkdirs()" because the return value of
"java.io.File.getParentFile()" is null {noformat}
Not the error you refer to...
> Intermittent "The parameters are missing or invalid" failures on Java 18-EA
> on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea
> both 64 bit and 32 bit (where available).
>
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed
> that builds on Windows *32bit* are failing with errors like these:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
> [Help 1]{noformat}
>
> Another example with stack trace from compiler plugin (other plugins fail as
> well):
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:577)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
> (DefaultMavenPluginManager.java:644)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
> (DefaultMavenPluginManager.java:597)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:124)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org
[jira] [Commented] (MNG-7398) maven build with long statement is prohibitively slow
[
https://issues.apache.org/jira/browse/MNG-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483751#comment-17483751
]
liuxun commented on MNG-7398:
-
I submit an issue to the java team, it has been accepted, pleaes refer:
[https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8280873]
> maven build with long statement is prohibitively slow
> -
>
> Key: MNG-7398
> URL: https://issues.apache.org/jira/browse/MNG-7398
> Project: Maven
> Issue Type: Bug
> Components: build/consumer
>Affects Versions: 3.5.0, 3.8.1
> Environment: jdk8
>Reporter: liuxun
>Priority: Critical
> Labels: easyfix, performance
> Attachments: build-with-long-statement-is-prohibitively-slow.zip
>
>
> h2. *+Question+*
> maven build with long statement is prohibitively slow.
> h2. +*Step*+
> 1: use the attachment zip file to repeat it, you can run it use
> {code:java}
> mvn clean package -X{code}
> it keeped always in processing, no errors, no timeout, no more info, but in
> processing status.
> 2: please focus on file:
> {code:java}
> com.chwod.robot.action.general.service.relation.RelationMappingService {code}
> there is a static block, it's containts a long statement. if remove it, then
> rebuild as step 1, it build complete quickly;
> so, until now, it seems that the maven build isn't support long statement.
> but, the interesting is:
> 3: keeped the static block containts a long statement in that file, if remove
> parent block from the pom.xml,, it build complete quickly.
> so, now, I can't be sure who's question this is. maven or spring? why not
> maven like spring? if not, I think maven can be fix it.
>
> BTW, I also submit a issue to spring repository, and hope： The two are
> reconciled
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-doxia] dependabot[bot] opened a new pull request #91: Bump xmlunit-matchers from 2.8.4 to 2.9.0
dependabot[bot] opened a new pull request #91: URL: https://github.com/apache/maven-doxia/pull/91 Bumps [xmlunit-matchers](https://github.com/xmlunit/xmlunit) from 2.8.4 to 2.9.0. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases";>xmlunit-matchers's releases. XMLUnit for Java 2.9.0 The major change of XMLUnit for Java 2.9.0 is the addition of a new module xmlunit-jakarta-jaxb-impl that can be used in addition to xmlunit-core when you want to use the Jakarta XML Binding API in version 3. For details please see the https://github.com/xmlunit/user-guide/wiki/JAXB";>user's guide. The full list of changes of XMLUnit for Java 2.9.0 is: added a new module xmlunit-jakarta-jaxb-impl that makes Input.fromJaxb use jakarta.xml.bind rather than javax.xml.bind. For more details see the https://github.com/xmlunit/user-guide/wiki/JAXB";>User's Guide. This change is not fully backwards compatible. The JaxbBuilder class has become abstract and the withMarshaller method has changed its signature. For most cases the change will not be noticed and for almost all other cases it should be enough to re-compile your code against XMLUnit 2.9.x. Issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/227";>#227 and PR https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/247";>#247 added NodeFilters#satisfiesAll and satifiesAny methods to make it easier to combine multiple node filters. added to simplify the use case of https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/249";>#249 Changelog Sourced from https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md";>xmlunit-matchers's changelog. XMLUnit for Java 2.9.0 - /Released 2022-01-25/ added a new module xmlunit-jakarta-jaxb-impl that makes Input.fromJaxb use jakarta.xml.bind rather than javax.xml.bind. For more details see the https://github.com/xmlunit/user-guide/wiki/JAXB";>User's Guide. This change is not fully backwards compatible. The JaxbBuilder class has become abstract and the withMarshaller method has changed its signature. For most cases the change will not be noticed and for almost all other cases it should be enough to re-compile your code against XMLUnit 2.9.x. Issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/227";>#227 and PR https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/247";>#247 added NodeFilters#satisfiesAll and satifiesAny methods to make it easier to combine multiple node filters. added to simplify the use case of https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/249";>#249 Commits https://github.com/xmlunit/xmlunit/commit/cc4242d06d9dee45abbb5ddaea28d64dd9b0";>cc4242d XMLUnit 2.9.0 https://github.com/xmlunit/xmlunit/commit/e8420e80ed5ff60236d09f2950f5e0c5d8fcc59d";>e8420e8 name profile properly https://github.com/xmlunit/xmlunit/commit/fc9d2cb8e4fe34669bd70c4f0038928b1b2058c4";>fc9d2cb Java9 and 10 seem to require the JAXB RI https://github.com/xmlunit/xmlunit/commit/98444ee320b4cfc7d8615e5638638c50d9b750de";>98444ee I should have known which parameter the shell script expects :-) https://github.com/xmlunit/xmlunit/commit/7638c0787cfcb73514b80d7d13a63e18d5a654c5";>7638c07 trigger Travis CI build https://github.com/xmlunit/xmlunit/commit/4d9a85438bc79c19ecb3348f4505b63de739b5bf";>4d9a854 NodeFilters.satisfyAll and .satisfyAny https://github.com/xmlunit/xmlunit/commit/eb7cc2c042e25273b8901ca425833c04bcdc8f3f";>eb7cc2c explicitly document the withFoo methods are not additive https://github.com/xmlunit/xmlunit/commit/64e55a33c658bc9d902b036f56a2d839fd63fa1d";>64e55a3 JAXB compatibility tests https://github.com/xmlunit/xmlunit/commit/51ee34b6eaeb99cf3668825a6321b501fd64668d";>51ee34b Merge pull request https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/247";>#247 from xmlunit/jakarta-jaxb https://github.com/xmlunit/xmlunit/commit/528ba4f931a143835f540b514aedddee0a350744";>528ba4f document JAXB change Additional commits viewable in https://github.com/xmlunit/xmlunit/compare/v2.8.4...v2.9.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions
[GitHub] [maven-doxia] dependabot[bot] opened a new pull request #90: Bump hamcrest-core from 1.3 to 2.2
dependabot[bot] opened a new pull request #90: URL: https://github.com/apache/maven-doxia/pull/90 Bumps [hamcrest-core](https://github.com/hamcrest/JavaHamcrest) from 1.3 to 2.2. Release notes Sourced from https://github.com/hamcrest/JavaHamcrest/releases";>hamcrest-core's releases. hamcrest-java-2.2 Improvements AllOf/AnyOf: Pass the matchers to constructor using varargs ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/245";>#245](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/245";>hamcrest/JavaHamcrest#245)) Matchers.anyOf: Fix generic bounds compatibility for JDK 11 ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/256";>#256](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/256";>hamcrest/JavaHamcrest#256), [Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/257";>#257](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/257";>hamcrest/JavaHamcrest#257)) AssertionError message is unhelpful when match fails for byte type ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/254";>#254](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/254";>hamcrest/JavaHamcrest#254), [Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/255";>#255](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/255";>hamcrest/JavaHamcrest#255)) Use platform specific line breaks ([PR https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/267";>#267](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/267";>hamcrest/JavaHamcrest#267)) Build now checks for consistent use of spaces ([PR https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/217";>#217](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/217";>hamcrest/JavaHamcrest#217)) Bugfixes Fix compatibility issue for development with Android D8 ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/246";>#246](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/246";>hamcrest/JavaHamcrest#246)) Fix typo in license name ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/247";>#247](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/247";>hamcrest/JavaHamcrest#247)) 1.3 compatible constructors for string matchers ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/259";>#259](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/259";>hamcrest/JavaHamcrest#259), [Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/260";>#260](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/260";>hamcrest/JavaHamcrest#260)) Fix for split packages with Java 9 modules ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/269";>#269](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/269";>hamcrest/JavaHamcrest#269), [PR https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/270";>#270](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/270";>hamcrest/JavaHamcrest#270)) hamcrest-java-2.2-rc1 Improvements AllOf/AnyOf: Pass the matchers to constructor using varargs ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/245";>#245](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/245";>hamcrest/JavaHamcrest#245)) Matchers.anyOf: Fix generic bounds compatibility for JDK 11 ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/256";>#256](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/256";>hamcrest/JavaHamcrest#256), [Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/257";>#257](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/257";>hamcrest/JavaHamcrest#257)) AssertionError message is unhelpful when match fails for byte type ([Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/254";>#254](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/254";>hamcrest/JavaHamcrest#254), [Issue https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/255";>#255](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/255";>hamcrest/JavaHamcrest#255)) Use platform specific line breaks ([PR https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/267";>#267](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/267";>hamcrest/JavaHamcrest#267)) Build now checks for consistent use of spaces ([PR https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/issues/217";>#217](https://github-redirect.dependabot.com/hamcrest/JavaHamcrest/pull/217";>hamcrest/JavaHamcrest#217)) Bugfixes Fix compatibility issue for development
[jira] [Updated] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Description:
I'm maintaining open-source project (multi-module Maven) and my CI/CD builds it
on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea both 64
bit and 32 bit (where available).
After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed that
builds on Windows *32bit* are failing with errors like these:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
[Help 1]{noformat}
Another example with stack trace from compiler plugin (other plugins fail as
well):
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:577)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
(DefaultMavenPluginManager.java:644)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
(DefaultMavenPluginManager.java:597)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:124)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(
[jira] [Commented] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483703#comment-17483703
]
Dmitry Bedrin commented on MNG-7399:
Updated with stacktrace, but I'm afraid it doesn't really help a lot - this
error line points to exactly one place in code.
> Intermittent "The parameters are missing or invalid" failures on Java 18-EA
> on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea
> both 64 bit and 32 bit (where available).
>
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed
> that builds on Windows *32bit* are failing with errors like these:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
> [Help 1]{noformat}
>
> Another example with stack trace from compiler plugin (other plugins fail as
> well):
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile
> (default-compile) on project sniffy: The parameters 'outputDirectory',
> 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:104)
> at java.lang.reflect.Method.invoke (Method.java:577)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
> org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
> invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
> (DefaultMavenPluginManager.java:644)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
> (DefaultMavenPluginManager.java:597)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:124)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
[jira] [Updated] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bedrin updated MNG-7399:
---
Description:
I'm maintaining open-source project (multi-module Maven) and my CI/CD builds it
on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea both 64
bit and 32 bit (where available).
After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed that
builds on Windows *32bit* are failing with errors like these:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
[Help 1]{noformat}
Another example with stack trace from compiler plugin (other plugins fail as
well):
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile)
on project sniffy: The parameters 'outputDirectory', 'projectArtifact',
'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:577)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
'outputDirectory', 'projectArtifact', 'buildDirectory' for goal
org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile are missing or
invalid
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields
(DefaultMavenPluginManager.java:644)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
(DefaultMavenPluginManager.java:597)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:124)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(
[jira] [Comment Edited] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483702#comment-17483702
]
Michael Osipov edited comment on MNG-7399 at 1/28/22, 10:32 AM:
All you provide is a single line instead of the entire stacktrace?
was (Author: michael-o):
All you provide a single line instead of the entire stacktrace?
> Intermittent "The parameters are missing or invalid" failures on Java 18-EA
> on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea
> both 64 bit and 32 bit (where available).
>
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed
> that builds on Windows *32bit* are failing with errors like these:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
> [Help 1]{noformat}
>
> Appreciate that Java 18 isn't released yet but worth checking.
> All other platforms as well as 64-bit JDK on Windows are fine.
>
> Happy to provide any further details if required.
>
> Here's the repo to reproduce it: [https://github.com/sniffy/sniffy]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
[
https://issues.apache.org/jira/browse/MNG-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483702#comment-17483702
]
Michael Osipov commented on MNG-7399:
-
All you provide a single line instead of the entire stacktrace?
> Intermittent "The parameters are missing or invalid" failures on Java 18-EA
> on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea
> both 64 bit and 32 bit (where available).
>
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed
> that builds on Windows *32bit* are failing with errors like these:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
> [Help 1]{noformat}
>
> Appreciate that Java 18 isn't released yet but worth checking.
> All other platforms as well as 64-bit JDK on Windows are fine.
>
> Happy to provide any further details if required.
>
> Here's the repo to reproduce it: [https://github.com/sniffy/sniffy]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAR-275) outputTimestamp not applied to module-info; breaks reproducible builds
[
https://issues.apache.org/jira/browse/MJAR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483681#comment-17483681
]
Ceki Gülcü commented on MJAR-275:
-
I can confirm that upgrading to Java 18 seems to have solved the
{{module-info.class}} issue. However, now the produced MANIFEST.MF file seems
to be different at each build (was not the case under Java 17). I will
investigate further later today or next week.
> outputTimestamp not applied to module-info; breaks reproducible builds
> --
>
> Key: MJAR-275
> URL: https://issues.apache.org/jira/browse/MJAR-275
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: Mac OS X 10.14.6
> JDK 15 (build 15+36)
> JDK 11 (build 11.0.8+10)
>Reporter: Anand Beh
>Priority: Minor
> Attachments: MCOMPILER-439.zip, Screenshot 2020-10-25 at 2.35.59
> PM.png
>
>
> Setting {{project.build.outputTimestamp}} to a fixed value allows creating
> reproducible builds per this guide:
> [https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> |https://maven.apache.org/guides/mini/guide-reproducible-builds.html]However,
> if one adds a module-info file to the project, reproducible builds break.
> This is caused by module-info.class using the latest timestamp and not
> {{project.build.outputTimestamp}}. I was able to identify the problem using
> diffoscope: [https://diffoscope.org/.|https://diffoscope.org/] With it I
> determined the timestamp across 2 builds was constant for all but the
> module-info.class:
>
> {code:java}
> -rw 2.0 fat 862 bl defN 20-Oct-17 00:40
> space/arim/libertybans/api/select/SelectionOrder.class
> │ -rw 2.0 fat 1113 bl defN 20-Oct-17 00:40
> space/arim/libertybans/api/select/SelectionOrderBuilder.class
> │ -rw 2.0 fat 2285 bl defN 20-Oct-17 00:40
> META-INF/maven/space.arim.libertybans/bans-api/pom.xml
> │ -rw 2.0 fat 74 bl defN 20-Oct-17 00:40
> META-INF/maven/space.arim.libertybans/bans-api/pom.properties
> │ --rw 2.0 fat 557 bl defN 20-Oct-25 12:39 module-info.class
> │ +-rw 2.0 fat 557 bl defN 20-Oct-25 12:41 module-info.class
> {code}
>
> Note the + and - which are diffoscope's way of indicating the difference
> between the .jar files. Here the {{project.build.outputTimestamp}} is on 17
> October. As shown, module-info has a "rebellious" timestamp.
>
> *EDIT:*
> Example project to reproduce the bug:
> [https://github.com/A248/MJAR-275|https://github.com/A248/MCOMPILER-439]
> (Renamed from [https://github.com/A248/MCOMPILER-439])
> Source code is also provided as an attachment below
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAR-285) versioned files do not use project.build.outputTimestamp
[
https://issues.apache.org/jira/browse/MJAR-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483657#comment-17483657
]
Ceki Gülcü commented on MJAR-285:
-
thank you for your quick response. Much appreciated.
I propose to close this ticket as a duplciate of MJAR-275,
> versioned files do not use project.build.outputTimestamp
> --
>
> Key: MJAR-285
> URL: https://issues.apache.org/jira/browse/MJAR-285
> Project: Maven JAR Plugin
> Issue Type: Sub-task
>Affects Versions: 3.2.2
>Reporter: Ceki Gülcü
>Priority: Major
>
> Hello,
> It looks like the addition of compressed files under META-INF/versions/ or
> module-info.class does not use the value of {{project.build.outputTimestamp}}
> but the local time instead.
> In any case, in logback project's build,
> {{META-INF/versions/9/module-info.class}} has a different timestamp than
> other files.
> This prevents reproducible builds.
> Could you please have a look?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-surefire] sman-81 opened a new pull request #452: [SUREFIRE-1992] - Do not abbreviate test error/failure messages to 78 characters
sman-81 opened a new pull request #452: URL: https://github.com/apache/maven-surefire/pull/452 Pull request for ticket [SUREFIRE-1992] which removes abbreviation of test error/failure messages to 78 characters in two classes that write test results to stdout/stderr. The fix greatly improves usability of surefire when troubleshooting test failures. -- 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] [Comment Edited] (MDEP-764) dependency:dependency:analyze-dep-mgt fails for multi module projects
[
https://issues.apache.org/jira/browse/MDEP-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483627#comment-17483627
]
Delany edited comment on MDEP-764 at 1/28/22, 8:05 AM:
---
Build your project first, or at the same time
{code:java}
mvn install dependency:analyze-dep-mgt {code}
was (Author: delany):
Build your project first, or at the same time
mvn install dependency:analyze-dep-mgt
> dependency:dependency:analyze-dep-mgt fails for multi module projects
> -
>
> Key: MDEP-764
> URL: https://issues.apache.org/jira/browse/MDEP-764
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Jon Edvardsson
>Priority: Major
>
> dependency:dependency:analyze-dep-mgt fails for multi module projects (that
> have yet not been installed?). The goal fail with the same error as MDEP-409.
> {code:sh}
> ➜ my-app git:(master) ✗ mvn dependency:analyze-dep-mgt
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Detecting the operating system and CPU architecture
> [INFO]
>
> [INFO] os.detected.name: osx
> [INFO] os.detected.arch: aarch_64
> [INFO] os.detected.version: 11.5
> [INFO] os.detected.version.major: 11
> [INFO] os.detected.version.minor: 5
> [INFO] os.detected.classifier: osx-aarch_64
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-app [pom]
> [INFO] my-app-api [jar]
> [INFO] my-app-impl[jar]
> [INFO]
> [INFO] < com.example:my-app >-
> [INFO] Building my-app 1.0-SNAPSHOT [1/3]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.2.0:analyze-dep-mgt (default-cli) @
> my-app ---
> [INFO] Found Resolved Dependency/DependencyManagement mismatches:
> [INFO] Ignoring Direct Dependencies.
> [INFO] None
> [INFO]
> [INFO] --< com.example:my-app-api >---
> [INFO] Building my-app-api 1.0-SNAPSHOT [2/3]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.2.0:analyze-dep-mgt (default-cli) @
> my-app-api ---
> [INFO] Found Resolved Dependency/DependencyManagement mismatches:
> [INFO] Ignoring Direct Dependencies.
> [INFO] com.google.code.findbugs:jsr305:jar was excluded in DepMgt, but
> version 3.0.2 has been found in the dependency tree.
> [INFO] javax.annotation:javax.annotation-api:jar was excluded in DepMgt, but
> version 1.3.2 has been found in the dependency tree.
> [INFO] com.google.protobuf:protobuf-java:jar was excluded in DepMgt, but
> version 3.17.3 has been found in the dependency tree.
> [WARNING] Potential problems found in Dependency Management
> [INFO]
> [INFO] -< com.example:my-app-impl >-
> [INFO] Building my-app-impl 1.0-SNAPSHOT [3/3]
> [INFO] [ jar
> ]-
> [INFO]
>
> [INFO] Reactor Summary for my-app 1.0-SNAPSHOT:
> [INFO]
> [INFO] my-app ... SUCCESS [ 0.332 s]
> [INFO] my-app-api ... SUCCESS [ 0.090 s]
> [INFO] my-app-impl FAILURE [ 0.166 s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.871 s
> [INFO] Finished at: 2021-09-08T10:57:57+02:00
> [INFO]
>
> [ERROR] Failed to execute goal on project my-app-impl: Could not resolve
> dependencies for project com.example:my-app-impl:jar:1.0-SNAPSHOT: Could not
> find artifact com.example:my-app-api:jar:1.0-SNAPSHOT -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the b
[jira] [Commented] (MDEP-764) dependency:dependency:analyze-dep-mgt fails for multi module projects
[
https://issues.apache.org/jira/browse/MDEP-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483627#comment-17483627
]
Delany commented on MDEP-764:
-
Build your project first, or at the same time
mvn install dependency:analyze-dep-mgt
> dependency:dependency:analyze-dep-mgt fails for multi module projects
> -
>
> Key: MDEP-764
> URL: https://issues.apache.org/jira/browse/MDEP-764
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Jon Edvardsson
>Priority: Major
>
> dependency:dependency:analyze-dep-mgt fails for multi module projects (that
> have yet not been installed?). The goal fail with the same error as MDEP-409.
> {code:sh}
> ➜ my-app git:(master) ✗ mvn dependency:analyze-dep-mgt
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Detecting the operating system and CPU architecture
> [INFO]
>
> [INFO] os.detected.name: osx
> [INFO] os.detected.arch: aarch_64
> [INFO] os.detected.version: 11.5
> [INFO] os.detected.version.major: 11
> [INFO] os.detected.version.minor: 5
> [INFO] os.detected.classifier: osx-aarch_64
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-app [pom]
> [INFO] my-app-api [jar]
> [INFO] my-app-impl[jar]
> [INFO]
> [INFO] < com.example:my-app >-
> [INFO] Building my-app 1.0-SNAPSHOT [1/3]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.2.0:analyze-dep-mgt (default-cli) @
> my-app ---
> [INFO] Found Resolved Dependency/DependencyManagement mismatches:
> [INFO] Ignoring Direct Dependencies.
> [INFO] None
> [INFO]
> [INFO] --< com.example:my-app-api >---
> [INFO] Building my-app-api 1.0-SNAPSHOT [2/3]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.2.0:analyze-dep-mgt (default-cli) @
> my-app-api ---
> [INFO] Found Resolved Dependency/DependencyManagement mismatches:
> [INFO] Ignoring Direct Dependencies.
> [INFO] com.google.code.findbugs:jsr305:jar was excluded in DepMgt, but
> version 3.0.2 has been found in the dependency tree.
> [INFO] javax.annotation:javax.annotation-api:jar was excluded in DepMgt, but
> version 1.3.2 has been found in the dependency tree.
> [INFO] com.google.protobuf:protobuf-java:jar was excluded in DepMgt, but
> version 3.17.3 has been found in the dependency tree.
> [WARNING] Potential problems found in Dependency Management
> [INFO]
> [INFO] -< com.example:my-app-impl >-
> [INFO] Building my-app-impl 1.0-SNAPSHOT [3/3]
> [INFO] [ jar
> ]-
> [INFO]
>
> [INFO] Reactor Summary for my-app 1.0-SNAPSHOT:
> [INFO]
> [INFO] my-app ... SUCCESS [ 0.332 s]
> [INFO] my-app-api ... SUCCESS [ 0.090 s]
> [INFO] my-app-impl FAILURE [ 0.166 s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.871 s
> [INFO] Finished at: 2021-09-08T10:57:57+02:00
> [INFO]
>
> [ERROR] Failed to execute goal on project my-app-impl: Could not resolve
> dependencies for project com.example:my-app-impl:jar:1.0-SNAPSHOT: Could not
> find artifact com.example:my-app-api:jar:1.0-SNAPSHOT -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :my-app-impl
> ➜ my-app git:(master) ✗
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (MNG-7399) Intermittent "The parameters are missing or invalid" failures on Java 18-EA on Windows x86 (32-bit)
Dmitry Bedrin created MNG-7399:
--
Summary: Intermittent "The parameters are missing or invalid"
failures on Java 18-EA on Windows x86 (32-bit)
Key: MNG-7399
URL: https://issues.apache.org/jira/browse/MNG-7399
Project: Maven
Issue Type: Bug
Affects Versions: 3.8.4
Reporter: Dmitry Bedrin
I'm maintaining open-source project (multi-module Maven) and my CI/CD builds it
on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea both 64
bit and 32 bit (where available).
After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed that
builds on Windows *32bit* are failing with errors like these:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid ->
[Help 1]{noformat}
Appreciate that Java 18 isn't released yet but worth checking.
All other platforms as well as 64-bit JDK on Windows are fine.
Happy to provide any further details if required.
Here's the repo to reproduce it: [https://github.com/sniffy/sniffy]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
