[GitHub] [maven-indexer] slachiewicz merged pull request #153: Bump checkstyle from 9.1 to 9.2.1

[GitBox]

slachiewicz merged pull request #153:
URL: https://github.com/apache/maven-indexer/pull/153


   


-- 
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-mvnd] jayzch commented on issue #547: java 8 can't use

[GitBox]

jayzch commented on issue #547:
URL: https://github.com/apache/maven-mvnd/issues/547#issuecomment-1001910918


   ➜  mvnd git:(master) ✗ java -version
   openjdk version "1.8.0_312"
   OpenJDK Runtime Environment (Zulu 8.58.0.13-CA-macos-aarch64) (build 
1.8.0_312-b07)
   OpenJDK 64-Bit Server VM (Zulu 8.58.0.13-CA-macos-aarch64) (build 
25.312-b07, 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-mvnd] jayzch opened a new issue #547: java 8 can't use

[GitBox]

jayzch opened a new issue #547:
URL: https://github.com/apache/maven-mvnd/issues/547


   Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/mvndaemon/mvnd/client/DefaultClient has been compiled by a more recent 
version of the Java Runtime (class file version 55.0), this version of the Java 
Runtime only recognizes class file versions up to 52.0


-- 
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] (MDEPLOY-254) Maven Deploy Plugin deploy jar twice : Maven 3.3.3

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465981#comment-17465981
 ] 

Michael Osipov commented on MDEPLOY-254:


[~kriegaex], it just means that the root cause had to be fixed outside of this 
plugin.

> Maven Deploy Plugin deploy jar twice : Maven 3.3.3
> --
>
> Key: MDEPLOY-254
> URL: https://issues.apache.org/jira/browse/MDEPLOY-254
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Reporter: Akshay
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Attachments: image-2021-04-11-23-55-48-005.png, 
> log1-mvn_clean_deploy_-Ptwice-source-jar-goal.txt, 
> log2-mvn_clean_deploy_-Psource-and-shade-plugin.txt, sample-project.zip
>
>
> Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
> project ** :
> Failed to retrieve remote metadata **/maven-metadata.xml:
> Could not transfer metadata ** from/to ** 
> {color:#FF} Not authorized , ReasonPhrase:Unauthorized. {color}
>  
> Wanted to know if the fix is out in a later version of Maven?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-mvnd] mthmulders commented on issue #545: git bash show “bash: mvnd: command not found” on win 10

[GitBox]

mthmulders commented on issue #545:
URL: https://github.com/apache/maven-mvnd/issues/545#issuecomment-1001908022


   This is highly unlikely to be an issue in Maven or mvnd, sounds more like 
operating system configuration to me. Please compare the `PATH` environment 
variable on both terminals.


-- 
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-indexer] dependabot[bot] closed pull request #149: Bump checkstyle from 9.1 to 9.2

[GitBox]

dependabot[bot] closed pull request #149:
URL: https://github.com/apache/maven-indexer/pull/149


   


-- 
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-indexer] dependabot[bot] opened a new pull request #153: Bump checkstyle from 9.1 to 9.2.1

[GitBox]

dependabot[bot] opened a new pull request #153:
URL: https://github.com/apache/maven-indexer/pull/153


   Bumps [checkstyle](https://github.com/checkstyle/checkstyle) from 9.1 to 
9.2.1.
   
   Release notes
   Sourced from https://github.com/checkstyle/checkstyle/releases";>checkstyle's 
releases.
   
   checkstyle-9.2.1
   https://checkstyle.org/releasenotes.html#Release_9.2.1";>https://checkstyle.org/releasenotes.html#Release_9.2.1
   checkstyle-9.2
   https://checkstyle.org/releasenotes.html#Release_9.2";>https://checkstyle.org/releasenotes.html#Release_9.2
   
   
   
   Commits
   
   https://github.com/checkstyle/checkstyle/commit/5c70bf79cf56a818119a4627ab92d2393a6b85f9";>5c70bf7
 [maven-release-plugin] prepare release checkstyle-9.2.1
   https://github.com/checkstyle/checkstyle/commit/46ed66d2ac9c50f02330b571afa97500d42fa1d6";>46ed66d
 config: update to 9.2.1-SNAPSHOT
   https://github.com/checkstyle/checkstyle/commit/ae058a9dd6aa862716d2d9e2436354e732c15782";>ae058a9
 doc: releasenote 9.2.1
   https://github.com/checkstyle/checkstyle/commit/9446729c8ab5a8d18cd64ec5b1a0fa7bf4d6f69e";>9446729
 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/10625";>#10625:
 Fixed three input files and removed them from line length suppr...
   https://github.com/checkstyle/checkstyle/commit/14db731a05e2f43062cfd6218c9eb9de34989ead";>14db731
 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/10625";>#10625:
 Fixed an Input file and removed it from line length suppression
   https://github.com/checkstyle/checkstyle/commit/296f051d144fc3c9bbc1887cfe382d168d13c882";>296f051
 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/10625";>#10625:
 Fixed InputMissingOverrideBadOverrideFromOther.java and removed...
   https://github.com/checkstyle/checkstyle/commit/b81dde3c3427bf8c80cd9352dfc4796c7b999cb0";>b81dde3
 doc: extend beginning development with step to build in terminal before 
IDE
   https://github.com/checkstyle/checkstyle/commit/ae4fedd6101f131fc4cdb72617fa96c267297e7c";>ae4fedd
 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/10625";>#10625:
 Fixed InputRedundantModifierFinalInTryWithResource.java and rem...
   https://github.com/checkstyle/checkstyle/commit/f58e10845a12ed937a75d7c94e2ea7dc2bc53305";>f58e108
 infra: print cmd in azure build to clearly see what command is running
   https://github.com/checkstyle/checkstyle/commit/50a74b20423f8dfa8304371c10293a37ead2ff65";>50a74b2
 infra: print cmd in azure build to clearly see what command is running
   Additional commits viewable in https://github.com/checkstyle/checkstyle/compare/checkstyle-9.1...checkstyle-9.2.1";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.puppycrawl.tools:checkstyle&package-manager=maven&previous-version=9.1&new-version=9.2.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-indexer] dependabot[bot] commented on pull request #149: Bump checkstyle from 9.1 to 9.2

[GitBox]

dependabot[bot] commented on pull request #149:
URL: https://github.com/apache/maven-indexer/pull/149#issuecomment-1001864757


   Superseded by #153.


-- 
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-archetype] dependabot[bot] opened a new pull request #104: Bump plexus-velocity from 1.2 to 1.3

[GitBox]

dependabot[bot] opened a new pull request #104:
URL: https://github.com/apache/maven-archetype/pull/104


   Bumps [plexus-velocity](https://github.com/codehaus-plexus/plexus-velocity) 
from 1.2 to 1.3.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-velocity/releases";>plexus-velocity's
 releases.
   
   plexus-velocity-1.3
   
   
   Upgrade to Velocity Engine 2.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-velocity/issues/11";>#11)
 https://github.com/slachiewicz";>@​slachiewicz
   Bump commons-collections from 3.1 to 3.2.2 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-velocity/issues/8";>#8)
 https://github.com/dependabot";>@​dependabot
   
   
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-velocity/commit/a9e943c79fffcc4e16e97131612525494ce9513e";>a9e943c
 [maven-release-plugin] prepare release plexus-velocity-1.3
   https://github.com/codehaus-plexus/plexus-velocity/commit/f69c3f067576f3dd95d5edd54663c9a249717233";>f69c3f0
 (doc) run CI also with Java 16/17-ea
   https://github.com/codehaus-plexus/plexus-velocity/commit/771f324ee090103d0f73869d108f6ae301d20b52";>771f324
 Upgrade to Velocity Engine 2.0
   https://github.com/codehaus-plexus/plexus-velocity/commit/d39abbfec089d759cbfbe4ff31fefde3f0b9ab22";>d39abbf
 Bump actions/cache from 2.1.5 to 2.1.6
   https://github.com/codehaus-plexus/plexus-velocity/commit/4c44349e302a0e2a17038db926bebd12c27e6696";>4c44349
 Bump actions/checkout from 2 to 2.3.4
   https://github.com/codehaus-plexus/plexus-velocity/commit/8d1928a589636f8fdcd3fd5c90fc746bc5a4015f";>8d1928a
 cleanup
   https://github.com/codehaus-plexus/plexus-velocity/commit/4a3b37e50970c3e54f0eb7e08b4b8c31123caffa";>4a3b37e
 fix javadoc
   https://github.com/codehaus-plexus/plexus-velocity/commit/5d0e765515ea37eebe15633048334d432ffb7d57";>5d0e765
 add ghaction, dependabot and release drafter
   https://github.com/codehaus-plexus/plexus-velocity/commit/fa4a96eda39ddf43647c7697ed6949a60f517d05";>fa4a96e
 Create codeql-analysis.yml
   https://github.com/codehaus-plexus/plexus-velocity/commit/42b272a7ccc7498ec64a14b9d13fe0405029f3db";>42b272a
 Bump commons-collections from 3.1 to 3.2.2
   Additional commits viewable in https://github.com/codehaus-plexus/plexus-velocity/compare/plexus-velocity-1.2...plexus-velocity-1.3";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.codehaus.plexus:plexus-velocity&package-manager=maven&previous-version=1.2&new-version=1.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-mvnd] zundaren opened a new issue #546: mvnd maven plugin

[GitBox]

zundaren opened a new issue #546:
URL: https://github.com/apache/maven-mvnd/issues/546


   Is it possible to develop a mvnd maven plugin, which can be used after 
importing it in pom.xml


-- 
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] (MDEPLOY-254) Maven Deploy Plugin deploy jar twice : Maven 3.3.3

[Alexander Kriegisch (Jira)]

[ 
https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465925#comment-17465925
 ] 

Alexander Kriegisch commented on MDEPLOY-254:
-

{quote}Fix was delivered with Maven 3.8.2.{quote}

I successfully verified this in my project, using Maven 3.8.2 and 3.8.4. Thank 
you for cherry-picking the fix.

{quote}Nothing to be fixed here.{quote}

I do not understand that part of your comment. Of course there was something to 
be fixed here, the bug was open since March 2019, i.e. more than 2.5 years.

> Maven Deploy Plugin deploy jar twice : Maven 3.3.3
> --
>
> Key: MDEPLOY-254
> URL: https://issues.apache.org/jira/browse/MDEPLOY-254
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Reporter: Akshay
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Attachments: image-2021-04-11-23-55-48-005.png, 
> log1-mvn_clean_deploy_-Ptwice-source-jar-goal.txt, 
> log2-mvn_clean_deploy_-Psource-and-shade-plugin.txt, sample-project.zip
>
>
> Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
> project ** :
> Failed to retrieve remote metadata **/maven-metadata.xml:
> Could not transfer metadata ** from/to ** 
> {color:#FF} Not authorized , ReasonPhrase:Unauthorized. {color}
>  
> Wanted to know if the fix is out in a later version of Maven?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-mvnd] RongXiong2016 opened a new issue #545: git bash show “bash: mvnd: command not found” on win 10

[GitBox]

RongXiong2016 opened a new issue #545:
URL: https://github.com/apache/maven-mvnd/issues/545


   ` mvnd --version` show  “bash: mvnd: command not found”
   in win10 cmd it's works ok
   but use git bash doesn't work 


-- 
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] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465914#comment-17465914
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/28/21, 12:38 AM:


Due to {{*Test mechanism*}} in the logs, it looks like an internal error in 
JUnit.
But is it really so?

 

[~fl4via] Do you use a custom junit listener?

 
{code:java}
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
 {code}
 

 
{code:java}
public static void rethrowAnyTestMechanismFailures( Result run )
throws TestSetFailedException
{
for ( Failure failure : run.getFailures() )
{
if ( isFailureInsideJUnitItself( failure.getDescription() ) )
{
throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
failure.getException() 
);
}
}
}
{code}


was (Author: tibor17):
Due to {{*Test mechanism*}} in the logs, it looks like an internal error in 
JUnit.
But is it really so?
{code:java}
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
 {code}
 

 
{code:java}
public static void rethrowAnyTestMechanismFailures( Result run )
throws TestSetFailedException
{
for ( Failure failure : run.getFailures() )
{
if ( isFailureInsideJUnitItself( failure.getDescription() ) )
{
throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
failure.getException() 
);
}
}
}
{code}

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.in

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465914#comment-17465914
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/28/21, 12:36 AM:


Due to {{*Test mechanism*}} in the logs, it looks like an internal error in 
JUnit.
But is it really so?
{code:java}
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
 {code}
 

 
{code:java}
public static void rethrowAnyTestMechanismFailures( Result run )
throws TestSetFailedException
{
for ( Failure failure : run.getFailures() )
{
if ( isFailureInsideJUnitItself( failure.getDescription() ) )
{
throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
failure.getException() 
);
}
}
}
{code}


was (Author: tibor17):
Due to {{*Test mechanism*}} in the logs, it looks like an internal error in 
JUnit.
But is it really so?

{code:java}
public static void rethrowAnyTestMechanismFailures( Result run )
throws TestSetFailedException
{
for ( Failure failure : run.getFailures() )
{
if ( isFailureInsideJUnitItself( failure.getDescription() ) )
{
throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
failure.getException() 
);
}
}
}
{code}


> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.in

[jira] [Commented] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465914#comment-17465914
 ] 

Tibor Digana commented on SUREFIRE-1946:


Due to {{Test mechanism}} in the logs, it looks like an internal error in JUnit.
But is it really so?

{code:java}
public static void rethrowAnyTestMechanismFailures( Result run )
throws TestSetFailedException
{
for ( Failure failure : run.getFailures() )
{
if ( isFailureInsideJUnitItself( failure.getDescription() ) )
{
throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
failure.getException() 
);
}
}
}
{code}


> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus.plex

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465914#comment-17465914
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/28/21, 12:24 AM:


Due to {{*Test mechanism*}} in the logs, it looks like an internal error in 
JUnit.
But is it really so?

{code:java}
public static void rethrowAnyTestMechanismFailures( Result run )
throws TestSetFailedException
{
for ( Failure failure : run.getFailures() )
{
if ( isFailureInsideJUnitItself( failure.getDescription() ) )
{
throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
failure.getException() 
);
}
}
}
{code}



was (Author: tibor17):
Due to {{Test mechanism}} in the logs, it looks like an internal error in JUnit.
But is it really so?

{code:java}
public static void rethrowAnyTestMechanismFailures( Result run )
throws TestSetFailedException
{
for ( Failure failure : run.getFailures() )
{
if ( isFailureInsideJUnitItself( failure.getDescription() ) )
{
throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
failure.getException() 
);
}
}
}
{code}


> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.mave

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465845#comment-17465845
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/28/21, 12:01 AM:


[~fl4via]
What you see on the console logs if you run the build with *mvn -e test*, see 
*-e*?
This issue should be handled different way.
This stack trace should be analyzed and the question should be answered: who 
caused the NPE. Was it the test frameworks or Surefire Provider?

{noformat}
[ERROR] org.apache.maven.surefire.api.testset.TestSetFailedException: Test 
mechanism :: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:192)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:436)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:170)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:570)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:556)
[ERROR] Caused by: java.lang.RuntimeException: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
[ERROR] at 
org.junit.runner.notification.RunNotifier$2.notifyListener(RunNotifier.java:103)
[ERROR] at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
[ERROR] at 
org.junit.runner.notification.RunNotifier.fireTestRunFinished(RunNotifier.java:100)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:63)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
[ERROR] ... 8 more
[ERROR] Caused by: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.StopServerWithExternalWorkerUtils.stopWorker(StopServerWithExternalWorkerUtils.java:83)
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:547)
{noformat}



was (Author: tibor17):
[~fl4via]
What you see if you run the build with *mvn -e test*, see *-e*?
This issue should be handled different way.
This stack trace should be analyzed and the question should be answered: who 
caused the NPE. Was it the test frameworks or Surefire Provider?

{noformat}
[ERROR] org.apache.maven.surefire.api.testset.TestSetFailedException: Test 
mechanism :: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:192)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:436)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:170)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:570)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:556)
[ERROR] Caused by: java.lang.RuntimeException: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
[ERROR] at 
org.junit.runner.notification.RunNotifier$2.

[jira] [Commented] (MSHARED-997) Failed / error test DefaultProjectDependencyAnalyzerTest in maven-dependency-analyzer

[Sylwester Lachiewicz (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465909#comment-17465909
 ] 

Sylwester Lachiewicz commented on MSHARED-997:
--

change has been reverted in 557aed1face2ff3467de2f2457eda0847ec693b3 so now 
master should be ok.

> Failed / error test DefaultProjectDependencyAnalyzerTest in 
> maven-dependency-analyzer
> -
>
> Key: MSHARED-997
> URL: https://issues.apache.org/jira/browse/MSHARED-997
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> There is no possibility to build project by:
> {code:java}
> mvn clean verify
> {code}
> Tested last commit: {{b6adba0bcda5036a9bc59e23be2976672b729198}}
> Maven and java versin:
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_302, vendor: Homebrew, runtime: 
> /usr/local/Cellar/openjdk@8/1.8.0+302/libexec/openjdk.jdk/Contents/Home/jre
> {code}
> I have many logs like:
> {code:java}
> 37) No implementation for 
> java.util.Set 
> was bound.
>   while locating 
> java.util.Set
> for parameter 0 at 
> org.eclipse.aether.internal.impl.DefaultLocalRepositoryProvider.(Unknown
>  Source)
>   while locating 
> org.eclipse.aether.internal.impl.DefaultLocalRepositoryProvider
>   at ClassRealm[plexus.core, parent: null]
>   at ClassRealm[plexus.core, parent: null]
>   while locating org.eclipse.aether.impl.LocalRepositoryProvider
> for parameter 8 at 
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.(Unknown 
> Source)
>   while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
>   at ClassRealm[plexus.core, parent: null]
>   at ClassRealm[plexus.core, parent: null]
>   while locating org.eclipse.aether.RepositorySystem
>   while locating org.apache.maven.artifact.resolver.DefaultArtifactResolver
>   at ClassRealm[plexus.core, parent: null]
>   at ClassRealm[plexus.core, parent: null]
> {code}
> and test result:
> {code:java}
> INFO] Results:
> [INFO] 
> [ERROR] Errors: 
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [INFO] 
> [ERROR] Tests run: 101, Failures: 0, Errors: 15, Skipped: 0
> {code}
> h3. Build on Apache Jenkins
> There is also strange behavior that {{jenkins}} build also has similar errors 
> - but failed tests aren't reported.
> [https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-analyzer/job/master/]
> h3. Build on GitHub
> There is also the same problem on GitHub:
>  https://github.com/apache/maven-dependency-analyzer/actions



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-scm] michael-o commented on a change in pull request #132: [SCM-925] Implement RemoveCommand in maven-scm-provider-jgit

[GitBox]

michael-o commented on a change in pull request #132:
URL: https://github.com/apache/maven-scm/pull/132#discussion_r775664327



##
File path: 
maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/pom.xml
##
@@ -88,4 +95,11 @@
   
 
   
+  
+  
+   
+   
5.13.0.202109080827-r

Review comment:
   Since this requires Java 8, it won't happen in 1.x. Can this be done 
with an older version?

##
File path: 
maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/pom.xml
##
@@ -50,9 +50,16 @@
 
   org.eclipse.jgit
   org.eclipse.jgit
-  4.5.4.201711221230-r
+  ${org.eclipse.jgit.version}
 
 
+
+  org.eclipse.jgit
+  org.eclipse.jgit.ssh.jsch
+  ${org.eclipse.jgit.version}

Review comment:
   Why is this necessary? JGit has moved to MINA.




-- 
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] (SCM-974) Upgrade Plexus Utils to 3.3.1

[Michael Osipov (Jira)]

Michael Osipov created SCM-974:
--

 Summary: Upgrade Plexus Utils to 3.3.1
 Key: SCM-974
 URL: https://issues.apache.org/jira/browse/SCM-974
 Project: Maven SCM
  Issue Type: Dependency upgrade
  Components: maven-scm-provider-gitexe, maven-scm-provider-mercurial 
(hg)
Affects Versions: 1.12.0
Reporter: Michael Osipov
Assignee: Michael Osipov
 Fix For: 2.0.0-M1, 1.12.1






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (SCM-973) GitCheckInCommandNoBranchTest fails with Git 2.34.0+

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/SCM-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed SCM-973.
--
Resolution: Fixed

Fixed with 
[ceb0e24ffa6095195ab7acd34b7aa5c807105537|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=ceb0e24ffa6095195ab7acd34b7aa5c807105537]
 and with 
[3743e166a63a4a117c33a3a289bb897551647744|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=3743e166a63a4a117c33a3a289bb897551647744]
 for {{maven-scm-1.x}} branch.

> GitCheckInCommandNoBranchTest fails with Git 2.34.0+
> 
>
> Key: SCM-973
> URL: https://issues.apache.org/jira/browse/SCM-973
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.12.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0-M1, 1.12.1
>
>
> Tests running on FreeBSD and Windows 10 gives me:
> {noformat}
> --
> Provider message
> --
> The git-push command failed.
> --
> --
> Command output
> --
> remote: fatal: bad object refs/empty.txt
> fatal: bad object refs/empty.txt
> To 
> file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/
>  ! [remote rejected] master -> master (missing necessary objects)
> error: Fehler beim Versenden einiger Referenzen nach 
> 'file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/'
> --
> {noformat}
> The reason is in Git 2.34.0:
> {noformat}
>  * The ref iteration code used to optionally allow dangling refs to be
>shown, which has been tightened up.
> {noformat}
> Source: 
> https://github.com/git/git/blob/2ae0a9cb8298185a94e5998086f380a355dd8907/Documentation/RelNotes/2.34.0.txt#L68-L69
> We simply need to replace those broken refs with {{.gitkeep}} to retain dirs.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-scm] asfgit closed pull request #133: [SCM-973] GitCheckInCommandNoBranchTest fails with Git 2.34.0+

[GitBox]

asfgit closed pull request #133:
URL: https://github.com/apache/maven-scm/pull/133


   


-- 
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 opened a new pull request #418: [SUREFIRE-1972] Use current version of surefire-shared-utils

[GitBox]

slawekjaranowski opened a new pull request #418:
URL: https://github.com/apache/maven-surefire/pull/418


   - in tests we can use classes from direct dependency
   - in other case delegate classes which will be shaded
   
   advantage:
   - we see what classes / method is used
   - we can use surefire-shared-utils in the same version as project
   
   disadvantage:
   - new delegated classes for each common / utils
   
   ---
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
- [x] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/SUREFIRE) filed 
  for the change (usually before you start working on it).  Trivial 
changes like typos do not 
  require a JIRA issue.  Your pull request should address just this 
issue, without 
  pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line 
and body.
- [x] Format the pull request title like `[SUREFIRE-XXX] - Fixes bug in 
ApproximateQuantiles`,
  where you replace `SUREFIRE-XXX` with the appropriate JIRA issue. 
Best practice
  is to use the JIRA issue title in the pull request title and in the 
first line of the 
  commit message.
- [x] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
- [x] Run `mvn clean install` to make sure basic checks pass. A more 
thorough check will 
  be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its clean 
install`).
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
- [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
- [x] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
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-scm] michael-o opened a new pull request #133: [SCM-973] GitCheckInCommandNoBranchTest fails with Git 2.34.0+

[GitBox]

michael-o opened a new pull request #133:
URL: https://github.com/apache/maven-scm/pull/133


   This closes #133


-- 
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] (SCM-973) GitCheckInCommandNoBranchTest fails with Git 2.34.0+

[Michael Osipov (Jira)]

Michael Osipov created SCM-973:
--

 Summary: GitCheckInCommandNoBranchTest fails with Git 2.34.0+
 Key: SCM-973
 URL: https://issues.apache.org/jira/browse/SCM-973
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-gitexe
Affects Versions: 1.12.0
Reporter: Michael Osipov
Assignee: Michael Osipov
 Fix For: 2.0.0-M1, 1.12.1


Tests running on FreeBSD and Windows 10 gives me:
{noformat}
--
Provider message
--
The git-push command failed.
--
--
Command output
--
remote: fatal: bad object refs/empty.txt
fatal: bad object refs/empty.txt
To 
file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/
 ! [remote rejected] master -> master (missing necessary objects)
error: Fehler beim Versenden einiger Referenzen nach 
'file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/'

--
{noformat}

The reason is in Git 2.34.0:
{noformat}
 * The ref iteration code used to optionally allow dangling refs to be
   shown, which has been tightened up.
{noformat}

Source: 
https://github.com/git/git/blob/2ae0a9cb8298185a94e5998086f380a355dd8907/Documentation/RelNotes/2.34.0.txt#L68-L69

We simply need to replace those broken refs with {{.gitkeep}} to retain dirs.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (SUREFIRE-1971) Latest 3.0.0-M5 release AND latest junit5 unknown fork error

[Brent Ryan (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465872#comment-17465872
 ] 

Brent Ryan commented on SUREFIRE-1971:
--

Other version info from logs:

[2021-12-27T21:04:15.736Z] [DEBUG] 
---
[2021-12-27T21:04:15.736Z] [DEBUG] Goal:          
org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test)
[2021-12-27T21:04:15.736Z] [DEBUG] Style:         Regular

> Latest 3.0.0-M5 release AND latest junit5 unknown fork error
> 
>
> Key: SUREFIRE-1971
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1971
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: BRENT RYAN
>Priority: Major
> Attachments: error.log
>
>
> See further details here:
> {{[https://github.com/dropwizard/dropwizard/issues/4538]}}
>  
> {{When running latest version of surefire plugin and latest version of junit 
> it causes a failure in the }}{{goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test}}
>  
> {{If you use junit 5.7.2 then it works fine or you can use junit 5.8.2 + 
> maven-surefire-plugin 2.22.2 and it works fine. But if you use both together 
> then it results in:}}
> {code:java}
> 18:47:27  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project *: There are test failures.
> 18:47:27  [ERROR] 
> 18:47:27  [ERROR] Please refer to ***/target/surefire-reports for the 
> individual test results.
> 18:47:27  [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> 18:47:27  [ERROR] There was an error in the forked process
> 18:47:27  [ERROR] 
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> 18:47:27  [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:47:27  [ERROR] at 
> java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:47:27  

[jira] (SUREFIRE-1971) Latest 3.0.0-M5 release AND latest junit5 unknown fork error

[Brent Ryan (Jira)]

[ https://issues.apache.org/jira/browse/SUREFIRE-1971 ]


Brent Ryan deleted comment on SUREFIRE-1971:
--

was (Author: brentryan):
Maven command used:

mvn clean verify -U --batch-mode -Dmaven.javadoc.skip=true -Prelease -X

 

This runs from a jenkins machine on a build farm that runs inside a docker 
container.

 

[2021-12-27T21:04:05.265Z] Maven home: /usr/local/maven

[2021-12-27T21:04:05.265Z] Java version: 11.0.4, vendor: AdoptOpenJDK

[2021-12-27T21:04:05.265Z] Java home: /usr/java/jdk-11.0.4+11

[2021-12-27T21:04:05.265Z] Default locale: en_US, platform encoding: 
ANSI_X3.4-1968

[2021-12-27T21:04:05.265Z] OS name: "linux", version: 
"4.14.256-197.484.amzn2.x86_64", arch: "amd64", family: "unix"

 

A section of the log with "-X" that demonstrates the problem:

[^error.log]

> Latest 3.0.0-M5 release AND latest junit5 unknown fork error
> 
>
> Key: SUREFIRE-1971
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1971
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: BRENT RYAN
>Priority: Major
> Attachments: error.log
>
>
> See further details here:
> {{[https://github.com/dropwizard/dropwizard/issues/4538]}}
>  
> {{When running latest version of surefire plugin and latest version of junit 
> it causes a failure in the }}{{goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test}}
>  
> {{If you use junit 5.7.2 then it works fine or you can use junit 5.8.2 + 
> maven-surefire-plugin 2.22.2 and it works fine. But if you use both together 
> then it results in:}}
> {code:java}
> 18:47:27  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project *: There are test failures.
> 18:47:27  [ERROR] 
> 18:47:27  [ERROR] Please refer to ***/target/surefire-reports for the 
> individual test results.
> 18:47:27  [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> 18:47:27  [ERROR] There was an error in the forked process
> 18:47:27  [ERROR] 
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> 18:47:27  [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorIm

[jira] [Updated] (SUREFIRE-1971) Latest 3.0.0-M5 release AND latest junit5 unknown fork error

[Brent Ryan (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brent Ryan updated SUREFIRE-1971:
-
Attachment: error.log

> Latest 3.0.0-M5 release AND latest junit5 unknown fork error
> 
>
> Key: SUREFIRE-1971
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1971
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: BRENT RYAN
>Priority: Major
> Attachments: error.log
>
>
> See further details here:
> {{[https://github.com/dropwizard/dropwizard/issues/4538]}}
>  
> {{When running latest version of surefire plugin and latest version of junit 
> it causes a failure in the }}{{goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test}}
>  
> {{If you use junit 5.7.2 then it works fine or you can use junit 5.8.2 + 
> maven-surefire-plugin 2.22.2 and it works fine. But if you use both together 
> then it results in:}}
> {code:java}
> 18:47:27  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project *: There are test failures.
> 18:47:27  [ERROR] 
> 18:47:27  [ERROR] Please refer to ***/target/surefire-reports for the 
> individual test results.
> 18:47:27  [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> 18:47:27  [ERROR] There was an error in the forked process
> 18:47:27  [ERROR] 
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> 18:47:27  [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:47:27  [ERROR] at 
> java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:47:27  [ERROR] -> [Help 1] {code}
> I

[jira] [Commented] (SUREFIRE-1971) Latest 3.0.0-M5 release AND latest junit5 unknown fork error

[Brent Ryan (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465871#comment-17465871
 ] 

Brent Ryan commented on SUREFIRE-1971:
--

Maven command used:

mvn clean verify -U --batch-mode -Dmaven.javadoc.skip=true -Prelease -X

 

This runs from a jenkins machine on a build farm that runs inside a docker 
container.

 

[2021-12-27T21:04:05.265Z] Maven home: /usr/local/maven

[2021-12-27T21:04:05.265Z] Java version: 11.0.4, vendor: AdoptOpenJDK

[2021-12-27T21:04:05.265Z] Java home: /usr/java/jdk-11.0.4+11

[2021-12-27T21:04:05.265Z] Default locale: en_US, platform encoding: 
ANSI_X3.4-1968

[2021-12-27T21:04:05.265Z] OS name: "linux", version: 
"4.14.256-197.484.amzn2.x86_64", arch: "amd64", family: "unix"

 

A section of the log with "-X" that demonstrates the problem:

[^error.log]

> Latest 3.0.0-M5 release AND latest junit5 unknown fork error
> 
>
> Key: SUREFIRE-1971
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1971
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: BRENT RYAN
>Priority: Major
> Attachments: error.log
>
>
> See further details here:
> {{[https://github.com/dropwizard/dropwizard/issues/4538]}}
>  
> {{When running latest version of surefire plugin and latest version of junit 
> it causes a failure in the }}{{goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test}}
>  
> {{If you use junit 5.7.2 then it works fine or you can use junit 5.8.2 + 
> maven-surefire-plugin 2.22.2 and it works fine. But if you use both together 
> then it results in:}}
> {code:java}
> 18:47:27  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project *: There are test failures.
> 18:47:27  [ERROR] 
> 18:47:27  [ERROR] Please refer to ***/target/surefire-reports for the 
> individual test results.
> 18:47:27  [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> 18:47:27  [ERROR] There was an error in the forked process
> 18:47:27  [ERROR] 
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> 18:47:27  [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:47:27 

[jira] [Commented] (SUREFIRE-1971) Latest 3.0.0-M5 release AND latest junit5 unknown fork error

[Brent Ryan (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465870#comment-17465870
 ] 

Brent Ryan commented on SUREFIRE-1971:
--

Maven command used:

mvn clean verify -U --batch-mode -Dmaven.javadoc.skip=true -Prelease -X

 

This runs from a jenkins machine on a build farm that runs inside a docker 
container.

 

[2021-12-27T21:04:05.265Z] Maven home: /usr/local/maven

[2021-12-27T21:04:05.265Z] Java version: 11.0.4, vendor: AdoptOpenJDK

[2021-12-27T21:04:05.265Z] Java home: /usr/java/jdk-11.0.4+11

[2021-12-27T21:04:05.265Z] Default locale: en_US, platform encoding: 
ANSI_X3.4-1968

[2021-12-27T21:04:05.265Z] OS name: "linux", version: 
"4.14.256-197.484.amzn2.x86_64", arch: "amd64", family: "unix"

 

A section of the log with "-X" that demonstrates the problem:

[^error.log]

> Latest 3.0.0-M5 release AND latest junit5 unknown fork error
> 
>
> Key: SUREFIRE-1971
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1971
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: BRENT RYAN
>Priority: Major
> Attachments: error.log
>
>
> See further details here:
> {{[https://github.com/dropwizard/dropwizard/issues/4538]}}
>  
> {{When running latest version of surefire plugin and latest version of junit 
> it causes a failure in the }}{{goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test}}
>  
> {{If you use junit 5.7.2 then it works fine or you can use junit 5.8.2 + 
> maven-surefire-plugin 2.22.2 and it works fine. But if you use both together 
> then it results in:}}
> {code:java}
> 18:47:27  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project *: There are test failures.
> 18:47:27  [ERROR] 
> 18:47:27  [ERROR] Please refer to ***/target/surefire-reports for the 
> individual test results.
> 18:47:27  [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> 18:47:27  [ERROR] There was an error in the forked process
> 18:47:27  [ERROR] 
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> 18:47:27  [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:47:27 

[jira] [Updated] (ARCHETYPE-601) Upgrade to commons-lang 3.8.1

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/ARCHETYPE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated ARCHETYPE-601:
-
Summary: Upgrade to commons-lang 3.8.1  (was: Update to commons-lang 3.8.1)

> Upgrade to commons-lang 3.8.1
> -
>
> Key: ARCHETYPE-601
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-601
> Project: Maven Archetype
>  Issue Type: Dependency upgrade
>Reporter: Elliotte Rusty Harold
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.2.1
>
>
> requires code changes to change the imports to the new package, as well as a 
> pom.xml update



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465841#comment-17465841
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/27/21, 7:10 PM:
---

Surefire should not show the stacktrace of the test.
*isErrorInFork* means something different. It means that the JVM exits with non 
zero.
If your test fails, the JVM exists with 0.
If it does not, then it means that the Provider or some test framework has 
crashed.


was (Author: tibor17):
Surefire should not show the stacktrace of the test.
*isErrorInFork* means something different. It means that the JVM exits with non 
zero.
If your test fails, the JVM exists with 0.
If it does not, then it means that the Provider or some test framework crashed.

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus.pl

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465841#comment-17465841
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/27/21, 7:09 PM:
---

Surefire should not show the stacktrace of the test.
*isErrorInFork* means something different. It means that the JVM exits with non 
zero.
If your test fails, the JVM exists with 0.
If it does not, then it means that the Provider or some test framework crashed.


was (Author: tibor17):
Surefire should not show the stacktrace of the test.
*isErrorInFork* means something different. It means that the JVM exits with non 
zero.
If your test fails the JVM exist with 0.
If it does not, then it means that the Provider or something else caused an 
error.

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus.plexu

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465845#comment-17465845
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/27/21, 7:05 PM:
---

[~fl4via]
What you see if you run the build with *mvn -e test*, see *-e*?
This issue should be handled different way.
This stack trace should be analyzed and the question should be answered: who 
caused the NPE. Was it the test frameworks or Surefire Provider?

{noformat}
[ERROR] org.apache.maven.surefire.api.testset.TestSetFailedException: Test 
mechanism :: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:192)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:436)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:170)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:570)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:556)
[ERROR] Caused by: java.lang.RuntimeException: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
[ERROR] at 
org.junit.runner.notification.RunNotifier$2.notifyListener(RunNotifier.java:103)
[ERROR] at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
[ERROR] at 
org.junit.runner.notification.RunNotifier.fireTestRunFinished(RunNotifier.java:100)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:63)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
[ERROR] ... 8 more
[ERROR] Caused by: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.StopServerWithExternalWorkerUtils.stopWorker(StopServerWithExternalWorkerUtils.java:83)
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:547)
{noformat}



was (Author: tibor17):
[~fl4via]
This issue should be handled different way.
This stack trace should be analyzed and the question should be answered: who 
caused the NPE. Was it the test frameworks or Surefire Provider?

{noformat}
[ERROR] org.apache.maven.surefire.api.testset.TestSetFailedException: Test 
mechanism :: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:192)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:436)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:170)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:570)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:556)
[ERROR] Caused by: java.lang.RuntimeException: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
[ERROR] at 
org.junit.runner.notification.RunNotifier$2.notifyListener(RunNotifier.java:103)
[ERROR] at 
org.junit.runner.notification.

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465845#comment-17465845
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/27/21, 7:03 PM:
---

[~fl4via]
This issue should be handled different way.
This stack trace should be analyzed and the question should be answered: who 
caused the NPE. Was it the test frameworks or Surefire Provider?

{noformat}
[ERROR] org.apache.maven.surefire.api.testset.TestSetFailedException: Test 
mechanism :: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:192)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:436)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:170)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:570)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:556)
[ERROR] Caused by: java.lang.RuntimeException: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
[ERROR] at 
org.junit.runner.notification.RunNotifier$2.notifyListener(RunNotifier.java:103)
[ERROR] at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
[ERROR] at 
org.junit.runner.notification.RunNotifier.fireTestRunFinished(RunNotifier.java:100)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:63)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
[ERROR] ... 8 more
[ERROR] Caused by: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.StopServerWithExternalWorkerUtils.stopWorker(StopServerWithExternalWorkerUtils.java:83)
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:547)
{noformat}



was (Author: tibor17):
[~fl4via]
This issue should be handled different way.
This stack trace should be analyzed and the question who caused the NPE.
Is it the test frameworks or Surefire Provider?

{noformat}
[ERROR] org.apache.maven.surefire.api.testset.TestSetFailedException: Test 
mechanism :: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:192)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:436)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:170)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:570)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:556)
[ERROR] Caused by: java.lang.RuntimeException: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
[ERROR] at 
org.junit.runner.notification.RunNotifier$2.notifyListener(RunNotifier.java:103)
[ERROR] at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
[ERROR] at 
org.junit.runner

[jira] [Commented] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465845#comment-17465845
 ] 

Tibor Digana commented on SUREFIRE-1946:


[~fl4via]
This issue should be handled different way.
This stack trace should be analyzed and the question who caused the NPE.
Is it the test frameworks or Surefire Provider?

{noformat}
[ERROR] org.apache.maven.surefire.api.testset.TestSetFailedException: Test 
mechanism :: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:192)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:436)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:170)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:570)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:556)
[ERROR] Caused by: java.lang.RuntimeException: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:549)
[ERROR] at 
io.undertow.testutils.RunDefaultServer$1.testRunFinished(RunDefaultServer.java:69)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testRunFinished(SynchronizedRunListener.java:42)
[ERROR] at 
org.junit.runner.notification.RunNotifier$2.notifyListener(RunNotifier.java:103)
[ERROR] at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
[ERROR] at 
org.junit.runner.notification.RunNotifier.fireTestRunFinished(RunNotifier.java:100)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:63)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
[ERROR] ... 8 more
[ERROR] Caused by: java.lang.NullPointerException
[ERROR] at 
io.undertow.testutils.StopServerWithExternalWorkerUtils.stopWorker(StopServerWithExternalWorkerUtils.java:83)
[ERROR] at 
io.undertow.testutils.DefaultServer.stopServer(DefaultServer.java:547)
{noformat}


> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]

[jira] [Commented] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465843#comment-17465843
 ] 

Tibor Digana commented on SUREFIRE-1946:


The NPE is not the error in ForkStarter. It is misleading.
It is only a message from the fork.

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> [ERROR] 
> [ERROR] -> [Help 1]
> [ERROR] 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465841#comment-17465841
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/27/21, 6:54 PM:
---

Surefire should not show the stacktrace of the test.
*isErrorInFork* means something different. It means that the JVM exits with non 
zero.
If your test fails the JVM exist with 0.
If it does not, then it means that the Provider or something else caused an 
error.


was (Author: tibor17):
Surefire should not show the stacktrace of the test.
*isErrorInFork* means that something different. It means that the JVM exits 
with non zero.
If your test fails the JVM exist with 0.
If it does not, then it means that the Provider or something else caused an 
error.

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehau

[jira] [Comment Edited] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465841#comment-17465841
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/27/21, 6:54 PM:
---

Surefire should not show the stacktrace of the test.
*isErrorInFork* means that something different. It means that the JVM exits 
with non zero.
If your test fails the JVM exist with 0.
If it does not, then it means that the Provider or something else caused an 
error.


was (Author: tibor17):
Surefire should not show the stacktrace of the test.
isErrorInFork means sdomething different. It means that the JVM exits with non 
zero.
If your test fails the JVM exist with 0.
If it does not, then it means that the Provider or something else caused an 
error.

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus

[jira] [Commented] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465841#comment-17465841
 ] 

Tibor Digana commented on SUREFIRE-1946:


Surefire should not show the stacktrace of the test.
isErrorInFork means sdomething different. It means that the JVM exits with non 
zero.
If your test fails the JVM exist with 0.
If it does not, then it means that the Provider or something else caused an 
error.

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> [ERROR] 
> [ERROR] -> [Help 1]
> [ERROR] 
> {code}



--
This message was sent

[jira] [Commented] (MRESOURCES-279) java.io.IOException: Failed to copy full contents from

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MRESOURCES-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465830#comment-17465830
 ] 

Michael Osipov commented on MRESOURCES-279:
---

Upgrade to 3.2.0 and retry.

> java.io.IOException: Failed to copy full contents from
> --
>
> Key: MRESOURCES-279
> URL: https://issues.apache.org/jira/browse/MRESOURCES-279
> Project: Maven Resources Plugin
>  Issue Type: Bug
>Affects Versions: 2.7
> Environment: Linux
>Reporter: Sonu Mishra
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: FileUtilsError.txt
>
>
> Hi,
> I am getting an error "java.io.IOException: Failed to copy full contents 
> from"  (randomly) on my system where file copy happens as and when files are 
> available in the directory. Also the behavior is random so cant reproduce 
> this. 
> The files gets corrupted after this error and no other error is encountered.  
> Is this the known issue ???
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MRESOURCES-279) java.io.IOException: Failed to copy full contents from

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MRESOURCES-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MRESOURCES-279:
--
Fix Version/s: waiting-for-feedback

> java.io.IOException: Failed to copy full contents from
> --
>
> Key: MRESOURCES-279
> URL: https://issues.apache.org/jira/browse/MRESOURCES-279
> Project: Maven Resources Plugin
>  Issue Type: Bug
>Affects Versions: 2.7
> Environment: Linux
>Reporter: Sonu Mishra
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: FileUtilsError.txt
>
>
> Hi,
> I am getting an error "java.io.IOException: Failed to copy full contents 
> from"  (randomly) on my system where file copy happens as and when files are 
> available in the directory. Also the behavior is random so cant reproduce 
> this. 
> The files gets corrupted after this error and no other error is encountered.  
> Is this the known issue ???
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MRESOLVER-224) DefaultVersionResolver is inflicting ArtifactNotFoundException for classifiers with SNAPSHOT version

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MRESOLVER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MRESOLVER-224:
-
Fix Version/s: waiting-for-feedback

> DefaultVersionResolver is inflicting ArtifactNotFoundException for 
> classifiers with SNAPSHOT version
> 
>
> Key: MRESOLVER-224
> URL: https://issues.apache.org/jira/browse/MRESOLVER-224
> Project: Maven Resolver
>  Issue Type: Bug
>  Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Tuomas Kiviaho
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I use classifier artifact along with the artifact itself as a dependency in a 
> Maven Invoker Plugin project. The project that calls the invoker has the 
> artifact itself as a dependency, but no reference to the classifier.
> This causes resolving of the maven-metadata.xml for the project itself plus 
> downloading of the dependency artifact.When invoker is called the artifact is 
> already downloaded to the local repo and cached with SNAPSHOT key.
> This causes the DefaultVersionResolver to merge the version information of 
> the SNAPSHOT:jar artifact that is now being resolved with the 
> already downloaded SNAPSHOT key. Since the local version is newer than the 
> repo version the DefaultVersionResolver thinks SNAPSHOT:jar to 
> be outdated thus overriding it with local repo.
> Since the SNAPSHOT:jar doesn't exist in the local repo there 
> are no remote report left to try the DefaultArtifactResolver fails ultimately 
> to ArtifactNotFoundException since there was no download task.
> {code:java}
> [INFO] [DEBUG] Resolving artifact 
> .:jar::-SNAPSHOT from 
> []{code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MRESOLVER-224) DefaultVersionResolver is inflicting ArtifactNotFoundException for classifiers with SNAPSHOT version

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MRESOLVER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465818#comment-17465818
 ] 

Michael Osipov commented on MRESOLVER-224:
--

[~tuomas_kiviaho], let me know whether you can provide a sample. That would 
make the investigation much simpler.

> DefaultVersionResolver is inflicting ArtifactNotFoundException for 
> classifiers with SNAPSHOT version
> 
>
> Key: MRESOLVER-224
> URL: https://issues.apache.org/jira/browse/MRESOLVER-224
> Project: Maven Resolver
>  Issue Type: Bug
>  Components: Resolver
>Affects Versions: 1.6.3
>Reporter: Tuomas Kiviaho
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I use classifier artifact along with the artifact itself as a dependency in a 
> Maven Invoker Plugin project. The project that calls the invoker has the 
> artifact itself as a dependency, but no reference to the classifier.
> This causes resolving of the maven-metadata.xml for the project itself plus 
> downloading of the dependency artifact.When invoker is called the artifact is 
> already downloaded to the local repo and cached with SNAPSHOT key.
> This causes the DefaultVersionResolver to merge the version information of 
> the SNAPSHOT:jar artifact that is now being resolved with the 
> already downloaded SNAPSHOT key. Since the local version is newer than the 
> repo version the DefaultVersionResolver thinks SNAPSHOT:jar to 
> be outdated thus overriding it with local repo.
> Since the SNAPSHOT:jar doesn't exist in the local repo there 
> are no remote report left to try the DefaultArtifactResolver fails ultimately 
> to ArtifactNotFoundException since there was no download task.
> {code:java}
> [INFO] [DEBUG] Resolving artifact 
> .:jar::-SNAPSHOT from 
> []{code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Slawomir Jaranowski (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465811#comment-17465811
 ] 

Slawomir Jaranowski commented on SUREFIRE-1946:
---

Did you try execute Maven with option {{-e}}, than stack trace should be 
printed.

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> [ERROR] 
> [ERROR] -> [Help 1]
> [ERROR] 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (SUREFIRE-1946) Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork

[Slawomir Jaranowski (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Slawomir Jaranowski updated SUREFIRE-1946:
--
Labels: waiting-for-feedback  (was: )

> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> --
>
> Key: SUREFIRE-1946
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking
>Affects Versions: 3.0.0-M5
>Reporter: Flavia Rainone
>Priority: Major
>  Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]   at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]   at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]   at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]   at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> [ERROR]   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> [ERROR] 
> [ERROR] -> [Help 1]
> [ERROR] 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-surefire] slawekjaranowski commented on a change in pull request #391: [SUREFIRE-1946] At ForkStarter.fork, treat the case forkClient.isErro…

[GitBox]

slawekjaranowski commented on a change in pull request #391:
URL: https://github.com/apache/maven-surefire/pull/391#discussion_r775575790



##
File path: 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java
##
@@ -653,6 +653,12 @@ private RunResult fork( Object testSet, PropertiesWrapper 
providerProperties, Fo
 {
 runResult = timeout( 
reporter.getGlobalRunStatistics().getRunResult() );
 }
+else if ( forkClient.isErrorInFork() )
+{
+final StackTraceWriter stackTrace = 
forkClient.getErrorInFork();
+booterForkException =
+new SurefireBooterForkException( 
stackTrace.writeTraceToString() );
+}

Review comment:
   Please look line 711 - 733
   StackTrace is printed if Maven command is started with -e option




-- 
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] (ARCHETYPE-605) Allow .gitignore file in archetype resources

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/ARCHETYPE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated ARCHETYPE-605:

Fix Version/s: 3.2.1

> Allow .gitignore file in archetype resources
> 
>
> Key: ARCHETYPE-605
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-605
> Project: Maven Archetype
>  Issue Type: Bug
>  Components: Plugin
>Affects Versions: 3.2.0
>Reporter: Piotr Lewandowski
>Priority: Major
> Fix For: 3.2.1
>
>
> Since 3.2.0 (and plexus-archiver:4.2.2) JAR archive with archetype does not 
> include {{.gitignore}} file, despite of fact that this file is located in 
> {{archetype-resources}} directory.
> In {{JarMojo}} Plexus' {{addDirectory(File)}} method is called.
> {code:java}
> archiver.getArchiver().addDirectory( archetypeDirectory );{code}
> This method does not configure default excludes, that are enabled by default.
> {code:java}
> @Override
> public void addDirectory( @Nonnull final File directory )
> throws ArchiverException
> {
> addFileSet(
> fileSet( directory ).prefixed( "" ).includeExclude( null, null 
> ).includeEmptyDirs( includeEmptyDirs ) );
> }{code}
> {{setUsingDefaultExcludes}} method is not called on fileSet here.
> Later on, this fileSet is used to create {{PlexusIoFileResourceCollection}} 
> object. On this object, {{getResources}} method is called that uses Plexus' 
> {{DirectoryScanner}} to find out all resources that should be included into 
> final artifact. This scanner uses {{usingDefaultExcludes}} configuration and 
> excludes [among the 
> others|https://github.com/sonatype/plexus-utils/blob/master/src/main/java/org/codehaus/plexus/util/AbstractScanner.java#L92],
>  {{.gitignore}} file.
> I have not found any way to configure archetype-archiver to disable default 
> excludes. In my opinion current behavior is a regression - custom 
> {{.gitignore}} is useful feature in archetypes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (ARCHETYPE-605) Allow .gitignore file in archetype resources

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/ARCHETYPE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed ARCHETYPE-605.
---
Fix Version/s: (was: backlog)
   Resolution: Fixed

> Allow .gitignore file in archetype resources
> 
>
> Key: ARCHETYPE-605
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-605
> Project: Maven Archetype
>  Issue Type: Bug
>  Components: Plugin
>Affects Versions: 3.2.0
>Reporter: Piotr Lewandowski
>Priority: Major
>
> Since 3.2.0 (and plexus-archiver:4.2.2) JAR archive with archetype does not 
> include {{.gitignore}} file, despite of fact that this file is located in 
> {{archetype-resources}} directory.
> In {{JarMojo}} Plexus' {{addDirectory(File)}} method is called.
> {code:java}
> archiver.getArchiver().addDirectory( archetypeDirectory );{code}
> This method does not configure default excludes, that are enabled by default.
> {code:java}
> @Override
> public void addDirectory( @Nonnull final File directory )
> throws ArchiverException
> {
> addFileSet(
> fileSet( directory ).prefixed( "" ).includeExclude( null, null 
> ).includeEmptyDirs( includeEmptyDirs ) );
> }{code}
> {{setUsingDefaultExcludes}} method is not called on fileSet here.
> Later on, this fileSet is used to create {{PlexusIoFileResourceCollection}} 
> object. On this object, {{getResources}} method is called that uses Plexus' 
> {{DirectoryScanner}} to find out all resources that should be included into 
> final artifact. This scanner uses {{usingDefaultExcludes}} configuration and 
> excludes [among the 
> others|https://github.com/sonatype/plexus-utils/blob/master/src/main/java/org/codehaus/plexus/util/AbstractScanner.java#L92],
>  {{.gitignore}} file.
> I have not found any way to configure archetype-archiver to disable default 
> excludes. In my opinion current behavior is a regression - custom 
> {{.gitignore}} is useful feature in archetypes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (ARCHETYPE-605) Allow .gitignore file in archetype resources

[Herve Boutemy (Jira)]

[ 
https://issues.apache.org/jira/browse/ARCHETYPE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465797#comment-17465797
 ] 

Herve Boutemy commented on ARCHETYPE-605:
-

I'm reviewing before doing the release, to see if low hanging fruits are 
available...

> Allow .gitignore file in archetype resources
> 
>
> Key: ARCHETYPE-605
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-605
> Project: Maven Archetype
>  Issue Type: Bug
>  Components: Plugin
>Affects Versions: 3.2.0
>Reporter: Piotr Lewandowski
>Priority: Major
> Fix For: backlog
>
>
> Since 3.2.0 (and plexus-archiver:4.2.2) JAR archive with archetype does not 
> include {{.gitignore}} file, despite of fact that this file is located in 
> {{archetype-resources}} directory.
> In {{JarMojo}} Plexus' {{addDirectory(File)}} method is called.
> {code:java}
> archiver.getArchiver().addDirectory( archetypeDirectory );{code}
> This method does not configure default excludes, that are enabled by default.
> {code:java}
> @Override
> public void addDirectory( @Nonnull final File directory )
> throws ArchiverException
> {
> addFileSet(
> fileSet( directory ).prefixed( "" ).includeExclude( null, null 
> ).includeEmptyDirs( includeEmptyDirs ) );
> }{code}
> {{setUsingDefaultExcludes}} method is not called on fileSet here.
> Later on, this fileSet is used to create {{PlexusIoFileResourceCollection}} 
> object. On this object, {{getResources}} method is called that uses Plexus' 
> {{DirectoryScanner}} to find out all resources that should be included into 
> final artifact. This scanner uses {{usingDefaultExcludes}} configuration and 
> excludes [among the 
> others|https://github.com/sonatype/plexus-utils/blob/master/src/main/java/org/codehaus/plexus/util/AbstractScanner.java#L92],
>  {{.gitignore}} file.
> I have not found any way to configure archetype-archiver to disable default 
> excludes. In my opinion current behavior is a regression - custom 
> {{.gitignore}} is useful feature in archetypes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (ARCHETYPE-605) Allow .gitignore file in archetype resources

[Piotr Lewandowski (Jira)]

[ 
https://issues.apache.org/jira/browse/ARCHETYPE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465793#comment-17465793
 ] 

Piotr Lewandowski commented on ARCHETYPE-605:
-

Yes, it is. Is there any timeline on when to expect the 3.2.1 release?

> Allow .gitignore file in archetype resources
> 
>
> Key: ARCHETYPE-605
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-605
> Project: Maven Archetype
>  Issue Type: Bug
>  Components: Plugin
>Affects Versions: 3.2.0
>Reporter: Piotr Lewandowski
>Priority: Major
> Fix For: backlog
>
>
> Since 3.2.0 (and plexus-archiver:4.2.2) JAR archive with archetype does not 
> include {{.gitignore}} file, despite of fact that this file is located in 
> {{archetype-resources}} directory.
> In {{JarMojo}} Plexus' {{addDirectory(File)}} method is called.
> {code:java}
> archiver.getArchiver().addDirectory( archetypeDirectory );{code}
> This method does not configure default excludes, that are enabled by default.
> {code:java}
> @Override
> public void addDirectory( @Nonnull final File directory )
> throws ArchiverException
> {
> addFileSet(
> fileSet( directory ).prefixed( "" ).includeExclude( null, null 
> ).includeEmptyDirs( includeEmptyDirs ) );
> }{code}
> {{setUsingDefaultExcludes}} method is not called on fileSet here.
> Later on, this fileSet is used to create {{PlexusIoFileResourceCollection}} 
> object. On this object, {{getResources}} method is called that uses Plexus' 
> {{DirectoryScanner}} to find out all resources that should be included into 
> final artifact. This scanner uses {{usingDefaultExcludes}} configuration and 
> excludes [among the 
> others|https://github.com/sonatype/plexus-utils/blob/master/src/main/java/org/codehaus/plexus/util/AbstractScanner.java#L92],
>  {{.gitignore}} file.
> I have not found any way to configure archetype-archiver to disable default 
> excludes. In my opinion current behavior is a regression - custom 
> {{.gitignore}} is useful feature in archetypes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (SUREFIRE-1971) Latest 3.0.0-M5 release AND latest junit5 unknown fork error

[Slawomir Jaranowski (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465789#comment-17465789
 ] 

Slawomir Jaranowski commented on SUREFIRE-1971:
---

Can you execute build with Maven -X options?
A provide logs from build?

> Latest 3.0.0-M5 release AND latest junit5 unknown fork error
> 
>
> Key: SUREFIRE-1971
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1971
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: BRENT RYAN
>Priority: Major
>
> See further details here:
> {{[https://github.com/dropwizard/dropwizard/issues/4538]}}
>  
> {{When running latest version of surefire plugin and latest version of junit 
> it causes a failure in the }}{{goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test}}
>  
> {{If you use junit 5.7.2 then it works fine or you can use junit 5.8.2 + 
> maven-surefire-plugin 2.22.2 and it works fine. But if you use both together 
> then it results in:}}
> {code:java}
> 18:47:27  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project *: There are test failures.
> 18:47:27  [ERROR] 
> 18:47:27  [ERROR] Please refer to ***/target/surefire-reports for the 
> individual test results.
> 18:47:27  [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> 18:47:27  [ERROR] There was an error in the forked process
> 18:47:27  [ERROR] 
> org.apache.maven.surefire.booter.SurefireBooterForkException: There was an 
> error in the forked process
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> 18:47:27  [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> 18:47:27  [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> 18:47:27  [ERROR] at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> 18:47:27  [ERROR] at 
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> 18:47:27  [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:47:27  [ERROR] at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:47:27  [ERROR] at 
> java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:47:27  [ERROR] at 
> org.codehaus.plexus.classworl

[jira] [Closed] (MDEPLOY-254) Maven Deploy Plugin deploy jar twice : Maven 3.3.3

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MDEPLOY-254.
--
Fix Version/s: (was: waiting-for-feedback)
   (was: wontfix-candidate)
   Resolution: Information Provided

Fix was delivered with Maven 3.8.2. Nothing to be fixed here.

> Maven Deploy Plugin deploy jar twice : Maven 3.3.3
> --
>
> Key: MDEPLOY-254
> URL: https://issues.apache.org/jira/browse/MDEPLOY-254
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Reporter: Akshay
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Attachments: image-2021-04-11-23-55-48-005.png, 
> log1-mvn_clean_deploy_-Ptwice-source-jar-goal.txt, 
> log2-mvn_clean_deploy_-Psource-and-shade-plugin.txt, sample-project.zip
>
>
> Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
> project ** :
> Failed to retrieve remote metadata **/maven-metadata.xml:
> Could not transfer metadata ** from/to ** 
> {color:#FF} Not authorized , ReasonPhrase:Unauthorized. {color}
>  
> Wanted to know if the fix is out in a later version of Maven?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Comment Edited] (MDEPLOY-254) Maven Deploy Plugin deploy jar twice : Maven 3.3.3

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MDEPLOY-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252512#comment-17252512
 ] 

Michael Osipov edited comment on MDEPLOY-254 at 12/27/21, 2:59 PM:
---

I am inclined to close this as not an issue because the description does not 
match the summary. Can someone confirm that Maven master fixes the duplicate 
upload?


was (Author: michael-o):
I am included to close this as not an issue because the description does not 
match the summary. Can someone confirm that Maven master fixes the duplicate 
upload?

> Maven Deploy Plugin deploy jar twice : Maven 3.3.3
> --
>
> Key: MDEPLOY-254
> URL: https://issues.apache.org/jira/browse/MDEPLOY-254
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Reporter: Akshay
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Attachments: image-2021-04-11-23-55-48-005.png, 
> log1-mvn_clean_deploy_-Ptwice-source-jar-goal.txt, 
> log2-mvn_clean_deploy_-Psource-and-shade-plugin.txt, sample-project.zip
>
>
> Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
> project ** :
> Failed to retrieve remote metadata **/maven-metadata.xml:
> Could not transfer metadata ** from/to ** 
> {color:#FF} Not authorized , ReasonPhrase:Unauthorized. {color}
>  
> Wanted to know if the fix is out in a later version of Maven?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (MDEPLOY-288) Deploy is failed when no primary artifact is present

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MDEPLOY-288.
--
  Assignee: Michael Osipov
Resolution: Won't Fix

> Deploy is failed when no primary artifact is present
> 
>
> Key: MDEPLOY-288
> URL: https://issues.apache.org/jira/browse/MDEPLOY-288
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M1
>Reporter: Victoria
>Assignee: Michael Osipov
>Priority: Critical
>
> We have a project without primary artifact.
> Previously, we were using _maven-deploy-plugin:2.7_ and everything worked as 
> expected: attached artifacts were deployed instead.
> Works the same way with version _2.8.2_.
>  
> {quote}{{[16:58:57] : [Step 2/2] [INFO] — maven-deploy-plugin:2.7:deploy 
> (default-deploy) @ project-without-primary-artifact ---}}
> {{[16:58:57] : [Step 2/2] [INFO] No primary artifact to deploy, deploying 
> attached artifacts instead.}}
> {{[16:58:57] : [Step 2/2] Uploading: 
> https:///project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.pom}}
> {{[16:58:57] : [Step 2/2] Uploaded: 
> https:///project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.pom
>  (12 KB at 21.0 KB/sec)}}
> {{[16:58:58] : [Step 2/2] Uploading: 
> https:///project-without-primary-artifact/maven-metadata.xml}}
> {{[16:58:59] : [Step 2/2] Uploaded: 
> https:///project-without-primary-artifact/maven-metadata.xml (2 KB at 
> 4.8 KB/sec)}}
> {{[16:58:59] : [Step 2/2] Uploading: 
> https:///project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.zip}}
> {{[16:58:59] : [Step 2/2] Uploaded: 
> https:///project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.zip
>  (42 KB at 67.3 KB/sec)}}
> {{[16:58:59] : [Step 2/2] [INFO] 
> }}
> {{[16:58:59] : [Step 2/2] [INFO] BUILD SUCCESS}}
> {{[16:58:59] : [Step 2/2] [INFO] 
> }}
> {{[16:58:59] : [Step 2/2] [INFO] Total time: 30.067s}}
> {{[16:58:59] : [Step 2/2] [INFO] Finished at: Tue Feb 25 16:58:59 UTC 2020}}
> {{[16:59:00] : [Step 2/2] [INFO] Final Memory: 68M/724M}}
> {{[16:59:00] : [Step 2/2] [INFO] 
> }}
> {{[16:59:00] : [Step 2/2] Process exited with code 0}}
> {quote}
>  
>   
>  However, after upgrading to _maven-deploy-plugin:3.0.0-M1_ the same build 
> fails:
>   
> {quote}{{[15:44:53] : [Step 2/2] [INFO] — maven-deploy-plugin:3.0.0-M1:deploy 
> (default-deploy) @ project-without-primary-artifact ---}}
> {{[15:44:53]E: [Step 2/2] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) 
> on project project-without-primary-artifact: NoFileAssignedException}}
> {{[15:44:53] : [Step 2/2] [INFO] 
> }}
> {{[15:44:53] : [Step 2/2] [INFO] BUILD FAILURE}}
> {{[15:44:53] : [Step 2/2] [INFO] 
> }}
> {{[15:44:53] : [Step 2/2] [INFO] Total time: 26.250 s}}
> {{[15:44:53] : [Step 2/2] [INFO] Finished at: 2021-10-08T15:44:53+00:00}}
> {{[15:44:54] : [Step 2/2] [INFO] Final Memory: 78M/921M}}{{[15:44:54] : [Step 
> 2/2] [INFO] 
> }}
> {{[15:44:54]W: [Step 2/2] [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) 
> on project project-without-primary-artifact: NoFileAssignedException: The 
> packaging plugin for this project did not assign a main file to the project 
> but it has attachments. Change packaging to 'pom'. -> [Help 1]}}
>   
> {quote}
>  
>  Similar issue appears in _maven-install-plugin:3.0.0-M1_: 
> https://issues.apache.org/jira/browse/MINSTALL-151 
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (MDEPLOY-273) AbstractSiteDeployWebDavTest should not log

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov reassigned MDEPLOY-273:
--

Assignee: Michael Osipov

> AbstractSiteDeployWebDavTest should not log
> ---
>
> Key: MDEPLOY-273
> URL: https://issues.apache.org/jira/browse/MDEPLOY-273
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Michael Osipov
>Priority: Minor
>
> Remove all logging from this class. Passing tests should not produce any 
> output. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MDEPLOY-286) Wrong documentation for format of altDeploymentRepository

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MDEPLOY-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465758#comment-17465758
 ] 

Michael Osipov commented on MDEPLOY-286:


[~lmroil], I plan to roll M2 this year.

> Wrong documentation for format of altDeploymentRepository
> -
>
> Key: MDEPLOY-286
> URL: https://issues.apache.org/jira/browse/MDEPLOY-286
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M1
>Reporter: Roland Illig
>Priority: Minor
>
> [https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html] says:
> > Format: id::layout::url
> As of version 3.0.0-M1, this is wrong. The format is now simply `id::url`. 
> The old format is no longer accepted.
> While here, the documentation for {{altReleaseDeploymentRepository}} and 
> {{altSnapshotDeploymentRepository}}. could be extended to contain the same 
> information as the {{altDeploymentRepository}}. The current documentation is 
> not completely clear on whether the syntax of these 3 properties follows the 
> same rules.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (MDEPLOY-286) Wrong documentation for format of altDeploymentRepository

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov reassigned MDEPLOY-286:
--

Assignee: Michael Osipov

> Wrong documentation for format of altDeploymentRepository
> -
>
> Key: MDEPLOY-286
> URL: https://issues.apache.org/jira/browse/MDEPLOY-286
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M1
>Reporter: Roland Illig
>Assignee: Michael Osipov
>Priority: Minor
>
> [https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html] says:
> > Format: id::layout::url
> As of version 3.0.0-M1, this is wrong. The format is now simply `id::url`. 
> The old format is no longer accepted.
> While here, the documentation for {{altReleaseDeploymentRepository}} and 
> {{altSnapshotDeploymentRepository}}. could be extended to contain the same 
> information as the {{altDeploymentRepository}}. The current documentation is 
> not completely clear on whether the syntax of these 3 properties follows the 
> same rules.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MDEPLOY-269) Make build Reproducible

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MDEPLOY-269:
---
Summary: Make build Reproducible  (was: make build Reproducible)

> Make build Reproducible
> ---
>
> Key: MDEPLOY-269
> URL: https://issues.apache.org/jira/browse/MDEPLOY-269
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-M1
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.0.0-M2
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (MDEPLOY-276) Warning when a pom is not able to be updated in remote repository

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MDEPLOY-276.
--
Fix Version/s: (was: wontfix-candidate)
   Resolution: Incomplete

No reaction for a year.

> Warning when a pom is not able to be updated in remote repository
> -
>
> Key: MDEPLOY-276
> URL: https://issues.apache.org/jira/browse/MDEPLOY-276
> Project: Maven Deploy Plugin
>  Issue Type: New Feature
>  Components: deploy:deploy
>Affects Versions: 3.0.0-M1
>Reporter: sylvain mouquet
>Priority: Major
>
> Hello,
>  
> I explain my context.
> I have some maven projects with a pom parent and modules.
> To speed up the CI/CD pipelines for the CI, we have created a profile foreach 
> module or group of module which allow us to // the build of the maven project
> On the release job we cannot use the // because maven push the parent pom in 
> the release repository and for best practice the release repository is able 
> to write but not re-write/update.
> One solution is to add an option to allow to continue the deploy even if the 
> pom parent is not able to be updated in the remote repository.
> It's possible to add this feature ?
>  
> Currently we don't use the // in the release step due to this 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-antrun-plugin] slachiewicz merged pull request #38: Bump maven-site-plugin from 3.9.1 to 3.10.0

[GitBox]

slachiewicz merged pull request #38:
URL: https://github.com/apache/maven-antrun-plugin/pull/38


   


-- 
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] (MDEPLOY-255) altDeploymentRepository is broken on mingw/cygwin/windows

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MDEPLOY-255.
--
Fix Version/s: (was: waiting-for-feedback)
   (was: wontfix-candidate)
   Resolution: Incomplete

No response for year.

> altDeploymentRepository is broken on mingw/cygwin/windows
> -
>
> Key: MDEPLOY-255
> URL: https://issues.apache.org/jira/browse/MDEPLOY-255
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>Reporter: Valentin titov
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> I'm trying to deploy some patched plugin from github to my internal 
> repository.
> maven-deploy-plugin has nice altDeploymentRepository parameter for such cases.
> I'm  using bash from msys2 (it's windows) and when run mvn with this 
> parameter:
> {code:bash}
> mvn install \
>  org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy\
>  
>  
> -DaltDeploymentRepository=default::http://nexus:8080/nexus/content/repositories/some_repo
> {code}
>  I get error 
> {noformat}
> [INFO] Using alternate deployment repository 
> default;http://nexus;8080\nexus\content\repositories\some_repo
> {noformat}
> ...
> [ERROR] Invalid syntax for alternative repository. Use "idurl".
> {noformat}
> This happens because URL part of parameter becomes broken when read as a 
> string parameter. I do not know if it happens inside ProjectDeployerRequest 
> or not, I do not know if 'native' mvn bat/cmd has the same problem.
> I suppose that URL  should be processed as URL, not string, so I suggest 
> adding separate parameters:
> altDeploymentRepositoryId and altDeploymentRepositoryURL
> see proposed fix in PR#6
> https://github.com/apache/maven-deploy-plugin/pull/6
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (MDEPLOY-281) Deploy only the selected modules using mvn deploy?

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MDEPLOY-281.
--
Fix Version/s: (was: waiting-for-feedback)
   (was: wontfix-candidate)
   Resolution: Incomplete

No reponse received for a year.

> Deploy only the selected modules using mvn deploy?
> --
>
> Key: MDEPLOY-281
> URL: https://issues.apache.org/jira/browse/MDEPLOY-281
> Project: Maven Deploy Plugin
>  Issue Type: Bug
>  Components: deploy:deploy
>Affects Versions: 3.0.0-M1
> Environment: Linux
>Reporter: CHILAKAM PRATHAPA REDDY
>Priority: Critical
>
> We have java project, and we are using maven as build tool. It is multi 
> module and huge legacy project.  and we use mvn -T 4 for building and 
> deploying it.
> Our build takes a lot of time when mvn install deploy happens.
> We really do not require to deploy all the modules to repository and also not 
> require to install to local repository.
> we would like to optimize the build process.  we want to deploy only selected 
> sub modules to repository and save build time and disk space.  
> Please help. 
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MDEPLOY-263) Add .asf.yaml

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MDEPLOY-263:
---
Fix Version/s: (was: 3.0.0-M2)

> Add .asf.yaml 
> --
>
> Key: MDEPLOY-263
> URL: https://issues.apache.org/jira/browse/MDEPLOY-263
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MDEPLOY-263) Add .asf.yaml

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MDEPLOY-263:
---
Affects Version/s: (was: 2.8.2)

> Add .asf.yaml 
> --
>
> Key: MDEPLOY-263
> URL: https://issues.apache.org/jira/browse/MDEPLOY-263
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0-M2
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MDEPLOY-282) Revert MDEPLOY-231

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MDEPLOY-282:
---
Fix Version/s: 3.0.0-M3
   (was: 3.0.0-M2)

> Revert MDEPLOY-231
> --
>
> Key: MDEPLOY-282
> URL: https://issues.apache.org/jira/browse/MDEPLOY-282
> Project: Maven Deploy Plugin
>  Issue Type: Task
>Affects Versions: 3.0.0-M1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> It does not logically make sense to have an IT which verifies the presence of 
> checksums because MDEPLOY does not generate them. MRESOLVER does that.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MDEPLOY-250) add documentation on managing network issues

[Michael Osipov (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEPLOY-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MDEPLOY-250:
---
Fix Version/s: 3.0.0-M3
   (was: 3.0.0-M2)

> add documentation on managing network issues
> 
>
> Key: MDEPLOY-250
> URL: https://issues.apache.org/jira/browse/MDEPLOY-250
> Project: Maven Deploy Plugin
>  Issue Type: Task
>  Components: deploy:deploy
>Affects Versions: 3.0.0-M1
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> network issues are happening sometimes, then there are strategies that have 
> been found to workaround, from simple retries, to 2-steps deploy through 
> local staging, like done by plc4x:
> see in [https://github.com/apache/incubator-plc4x/blob/develop/Jenkinsfile]:
> {noformat}
> // We'll deploy to a relative directory so we can save
> // that and deploy in a later step on a different node
> sh 'mvn -P${JENKINS_PROFILE},development ${MVN_TEST_FAIL_IGNORE} 
> ${JQASSISTANT_NEO4J_VERSION} 
> -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir 
> clean deploy'
> {noformat}
> followed by:
> {noformat}
> // Deploy the artifacts using the wagon-maven-plugin.
> sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload'
> {noformat}
> sharing such strategy can be useful to many



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (MRESOURCES-279) java.io.IOException: Failed to copy full contents from

[Sonu Mishra (Jira)]

Sonu Mishra created MRESOURCES-279:
--

 Summary: java.io.IOException: Failed to copy full contents from
 Key: MRESOURCES-279
 URL: https://issues.apache.org/jira/browse/MRESOURCES-279
 Project: Maven Resources Plugin
  Issue Type: Bug
Affects Versions: 2.7
 Environment: Linux
Reporter: Sonu Mishra
 Attachments: FileUtilsError.txt

Hi,

I am getting an error "java.io.IOException: Failed to copy full contents from"  
(randomly) on my system where file copy happens as and when files are available 
in the directory. Also the behavior is random so cant reproduce this. 

The files gets corrupted after this error and no other error is encountered.  
Is this the known issue ???

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465747#comment-17465747
 ] 

Michael Osipov commented on MNG-7375:
-

WTF: 
https://github.com/codehaus-plexus/modello/blob/8467ab87f95557c8c6409f5ebe613caf240836b3/modello-plugins/modello-plugin-xsd/src/main/java/org/codehaus/modello/plugin/xsd/XsdGenerator.java#L245-L247

> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid/incomplete plugin metadata
> --
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}
> 
> 
> 
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
> 
> 
> filevault-package-maven-plugin
> filevault-package-maven-plugin
> 
> 
> 
> {code}
> This leads to an NPE when trying to deploy a new version with 
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge 
> (Metadata.java:276)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
>  (AbstractRepositoryMetadata.java:121)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
>  (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
> (DefaultArtifactDeployer.java:142)
> {code}
> Although this happened in the context of using 
> "org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
> (https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in 
> Maven.
> The metadata is probably invalid but the Metadata class should be more robust 
> when trying to do the merge in 
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
>  and just ignore all plugin entries without all mandatory elements.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-antrun-plugin] dependabot[bot] opened a new pull request #38: Bump maven-site-plugin from 3.9.1 to 3.10.0

[GitBox]

dependabot[bot] opened a new pull request #38:
URL: https://github.com/apache/maven-antrun-plugin/pull/38


   Bumps [maven-site-plugin](https://github.com/apache/maven-site-plugin) from 
3.9.1 to 3.10.0.
   
   Commits
   
   https://github.com/apache/maven-site-plugin/commit/c56b7b2ad2baecbf4286151c645ff4ee9190f420";>c56b7b2
 [maven-release-plugin] prepare release maven-site-plugin-3.10.0
   https://github.com/apache/maven-site-plugin/commit/7029bab59cac4fe83b62c245e55c37bcb79d9061";>7029bab
 [MSITE-878] Upgrade Doxia to 1.11.1 and Doxia Tools to 1.11.1
   https://github.com/apache/maven-site-plugin/commit/7f8fe7ead4e42b7797eed7eb87c878a16e10b5be";>7f8fe7e
 [MSITE-877] Shared GitHub Actions (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/65";>#65)
   https://github.com/apache/maven-site-plugin/commit/e3302845bd4fac62e7869d1afd0faadd0499becc";>e330284
 require CDATA
   https://github.com/apache/maven-site-plugin/commit/eeba50cf6854c9cca709ae47a626d57d924e463e";>eeba50c
 Add PR template
   https://github.com/apache/maven-site-plugin/commit/7813e8f193131faec8898b54b0e59c82602ab665";>7813e8f
 add Sitetools' integration tool and skin model
   https://github.com/apache/maven-site-plugin/commit/fda2a84b09a6d08ceb26efee963f00a21e02ffc2";>fda2a84
 Updated CI setup
   https://github.com/apache/maven-site-plugin/commit/0cd2070cf4e32086fe936ea09c5f80c7d5a988cb";>0cd2070
 Bump slf4jVersion from 1.7.31 to 1.7.32 (https://github-redirect.dependabot.com/apache/maven-site-plugin/issues/58";>#58)
   https://github.com/apache/maven-site-plugin/commit/9f24d2bd21f3d7a741ea74b4f41aa42ee02ce625";>9f24d2b
 update CI url
   https://github.com/apache/maven-site-plugin/commit/e06aa7822797f6ee54ee4dd309d955c3822df801";>e06aa78
 [MSITE-875] add 3.10.0 in history table
   Additional commits viewable in https://github.com/apache/maven-site-plugin/compare/maven-site-plugin-3.9.1...maven-site-plugin-3.10.0";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.maven.plugins:maven-site-plugin&package-manager=maven&previous-version=3.9.1&new-version=3.10.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-gh-actions-shared] slawekjaranowski merged pull request #26: Use Maven wrapper to set up Maven version for build

[GitBox]

slawekjaranowski merged pull request #26:
URL: https://github.com/apache/maven-gh-actions-shared/pull/26


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MSHARED-997) Failed / error test DefaultProjectDependencyAnalyzerTest in maven-dependency-analyzer

[Slawomir Jaranowski (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465730#comment-17465730
 ] 

Slawomir Jaranowski commented on MSHARED-997:
-

Currently max supported Maven for build is 3.6.3

> Failed / error test DefaultProjectDependencyAnalyzerTest in 
> maven-dependency-analyzer
> -
>
> Key: MSHARED-997
> URL: https://issues.apache.org/jira/browse/MSHARED-997
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> There is no possibility to build project by:
> {code:java}
> mvn clean verify
> {code}
> Tested last commit: {{b6adba0bcda5036a9bc59e23be2976672b729198}}
> Maven and java versin:
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_302, vendor: Homebrew, runtime: 
> /usr/local/Cellar/openjdk@8/1.8.0+302/libexec/openjdk.jdk/Contents/Home/jre
> {code}
> I have many logs like:
> {code:java}
> 37) No implementation for 
> java.util.Set 
> was bound.
>   while locating 
> java.util.Set
> for parameter 0 at 
> org.eclipse.aether.internal.impl.DefaultLocalRepositoryProvider.(Unknown
>  Source)
>   while locating 
> org.eclipse.aether.internal.impl.DefaultLocalRepositoryProvider
>   at ClassRealm[plexus.core, parent: null]
>   at ClassRealm[plexus.core, parent: null]
>   while locating org.eclipse.aether.impl.LocalRepositoryProvider
> for parameter 8 at 
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.(Unknown 
> Source)
>   while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
>   at ClassRealm[plexus.core, parent: null]
>   at ClassRealm[plexus.core, parent: null]
>   while locating org.eclipse.aether.RepositorySystem
>   while locating org.apache.maven.artifact.resolver.DefaultArtifactResolver
>   at ClassRealm[plexus.core, parent: null]
>   at ClassRealm[plexus.core, parent: null]
> {code}
> and test result:
> {code:java}
> INFO] Results:
> [INFO] 
> [ERROR] Errors: 
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [ERROR]   
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 » 
> ComponentLookup
> [INFO] 
> [ERROR] Tests run: 101, Failures: 0, Errors: 15, Skipped: 0
> {code}
> h3. Build on Apache Jenkins
> There is also strange behavior that {{jenkins}} build also has similar errors 
> - but failed tests aren't reported.
> [https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-analyzer/job/master/]
> h3. Build on GitHub
> There is also the same problem on GitHub:
>  https://github.com/apache/maven-dependency-analyzer/actions



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (SUREFIRE-1819) MAVEN_OPTS=-Dmaven.repo.local env variable not used when running tests

[Jira]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465728#comment-17465728
 ] 

Jorge Solórzano commented on SUREFIRE-1819:
---

I think this issue can be closed.

> MAVEN_OPTS=-Dmaven.repo.local env variable not used when running tests
> --
>
> Key: SUREFIRE-1819
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1819
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: Jorge Solórzano
>Priority: Major
>  Labels: waiting-for-feedback
>
> The local repo configuration using:
>  
> {color:#569cd6}MAVEN_OPTS{color}={color:#ce9178}-Dmaven.repo.local=$CI_PROJECT_DIR/.m2/repository{color}
>   
> Is not working when running the tests, it downloads all the dependencies 
> again in the $HOME directory.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-surefire] imonteroperez commented on pull request #400: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile

[GitBox]

imonteroperez commented on pull request #400:
URL: https://github.com/apache/maven-surefire/pull/400#issuecomment-1001526015


   Moving this PR to draft status to achieve some of the feedback provided and 
to include more testing.


-- 
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] findepi commented on pull request #407: [SUREFIRE-1967] Fix parallel test ordering to prevent high resource consumption

[GitBox]

findepi commented on pull request #407:
URL: https://github.com/apache/maven-surefire/pull/407#issuecomment-1001525935


   @Tibor17 @slawekjaranowski let me know what else i should change 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] imonteroperez commented on pull request #400: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile

[GitBox]

imonteroperez commented on pull request #400:
URL: https://github.com/apache/maven-surefire/pull/400#issuecomment-1001524984


   > @imonteroperez We already discussed this feature request with @olamy in 
ASF. This feature brings chaos to the meaning of the config parameter and a 
duplicate to filter `test` which have the space for the method filtering. 
Naturally, `includesFile` cannot be about filtering methods. Instead of those 
parameters pls use `*Test#test*One+testTwo?`. Why you do not 
use the config parameter `test`? Do you want to override or merge this 
parameter with system property `test`?
   
   Hi @Tibor17 I know I can use `-Dtest`, but I was looking for a solution to 
expand the method filtering capabilities to be used on `surefire.excludesFile` 
and (additionally) on `surefire.includesFile`. 


-- 
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] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465721#comment-17465721
 ] 

Michael Osipov commented on MNG-7375:
-

[~rfscholte], I am either stupid or this is some bug in modello. {{minOccurs}} 
cannot be zero in this case.

> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid/incomplete plugin metadata
> --
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}
> 
> 
> 
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
> 
> 
> filevault-package-maven-plugin
> filevault-package-maven-plugin
> 
> 
> 
> {code}
> This leads to an NPE when trying to deploy a new version with 
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge 
> (Metadata.java:276)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
>  (AbstractRepositoryMetadata.java:121)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
>  (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
> (DefaultArtifactDeployer.java:142)
> {code}
> Although this happened in the context of using 
> "org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
> (https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in 
> Maven.
> The metadata is probably invalid but the Metadata class should be more robust 
> when trying to do the merge in 
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
>  and just ignore all plugin entries without all mandatory elements.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465719#comment-17465719
 ] 

Michael Osipov commented on MNG-7375:
-

This schema looks wrong for some reason:
{code:xml}

  Plugin
  1.0.0+
  Mapping information for a single plugin within this 
group
  NOTE: plugin version is _NOT_ included here, since it is 
resolved using a separate algorithm in plugins' artifact.
  

  name
  String
  true
  1.0.0+
  Display name for the plugin.


  prefix
  String
  true
  1.0.0+
  The plugin invocation prefix (i.e. eclipse for 
eclipse:eclipse)


  artifactId
  String
  true
  1.0.0+
  The plugin artifactId

  

{code}

One needs to check Modello's source code why this is the case.

> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid/incomplete plugin metadata
> --
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}
> 
> 
> 
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
> 
> 
> filevault-package-maven-plugin
> filevault-package-maven-plugin
> 
> 
> 
> {code}
> This leads to an NPE when trying to deploy a new version with 
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge 
> (Metadata.java:276)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
>  (AbstractRepositoryMetadata.java:121)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
>  (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
> (DefaultArtifactDeployer.java:142)
> {code}
> Although this happened in the context of using 
> "org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
> (https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in 
> Maven.
> The metadata is probably invalid but the Metadata class should be more robust 
> when trying to do the merge in 
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
>  and just ignore all plugin entries without all mandatory elements.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (ARCHETYPE-624) scope = provided for artifacts provided by Maven Core

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/ARCHETYPE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated ARCHETYPE-624:

Description: 
https://maven.apache.org/ref/3.8.4/maven-core/core-extensions.html

> scope = provided for artifacts provided by Maven Core
> -
>
> Key: ARCHETYPE-624
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-624
> Project: Maven Archetype
>  Issue Type: Improvement
>  Components: Plugin
>Affects Versions: 3.2.0
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.2.1
>
>
> https://maven.apache.org/ref/3.8.4/maven-core/core-extensions.html



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata

[Konrad Windszus (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465710#comment-17465710
 ] 

Konrad Windszus commented on MNG-7375:
--

bq. Where do you have the optional from?

>From the [XSD|https://maven.apache.org/xsd/repository-metadata-1.1.0.xsd]:
{code}

{code}
IMHO the XSD together with 
https://maven.apache.org/ref/3.8.4/maven-repository-metadata/repository-metadata.html
 is the spec.

But even in case it is required an invalid metadata should not lead to an NPE.

> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid/incomplete plugin metadata
> --
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}
> 
> 
> 
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
> 
> 
> filevault-package-maven-plugin
> filevault-package-maven-plugin
> 
> 
> 
> {code}
> This leads to an NPE when trying to deploy a new version with 
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge 
> (Metadata.java:276)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
>  (AbstractRepositoryMetadata.java:121)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
>  (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
> (DefaultArtifactDeployer.java:142)
> {code}
> Although this happened in the context of using 
> "org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
> (https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in 
> Maven.
> The metadata is probably invalid but the Metadata class should be more robust 
> when trying to do the merge in 
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
>  and just ignore all plugin entries without all mandatory elements.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven] michael-o commented on pull request #645: [MNG-7375] prevent potential NPE in Metadata.merge(...)

[GitBox]

michael-o commented on pull request #645:
URL: https://github.com/apache/maven/pull/645#issuecomment-1001510028


   This PR hides the fact that the input data is invalid. Obviously, we need a 
`MetadataValidator`.


-- 
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] kwin opened a new pull request #645: [MNG-7375] prevent potential NPE in Metadata.merge(...)

[GitBox]

kwin opened a new pull request #645:
URL: https://github.com/apache/maven/pull/645


   Add unit tests for merge
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
- [x] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MNG) filed 
  for the change (usually before you start working on it).  Trivial 
changes like typos do not 
  require a JIRA issue.  Your pull request should address just this 
issue, without 
  pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line 
and body.
- [x] Format the pull request title like `[MNG-XXX] - Fixes bug in 
ApproximateQuantiles`,
  where you replace `MNG-XXX` with the appropriate JIRA issue. Best 
practice
  is to use the JIRA issue title in the pull request title and in the 
first line of the 
  commit message.
- [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will 
  be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
- [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
- [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   


-- 
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] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465709#comment-17465709
 ] 

Michael Osipov commented on MNG-7375:
-

??? It is required: 
https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L357
Where do you have the optional from?

> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid/incomplete plugin metadata
> --
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}
> 
> 
> 
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
> 
> 
> filevault-package-maven-plugin
> filevault-package-maven-plugin
> 
> 
> 
> {code}
> This leads to an NPE when trying to deploy a new version with 
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge 
> (Metadata.java:276)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
>  (AbstractRepositoryMetadata.java:121)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
>  (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
> (DefaultArtifactDeployer.java:142)
> {code}
> Although this happened in the context of using 
> "org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
> (https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in 
> Maven.
> The metadata is probably invalid but the Metadata class should be more robust 
> when trying to do the merge in 
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
>  and just ignore all plugin entries without all mandatory elements.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid/incomplete plugin metadata

[Konrad Windszus (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated MNG-7375:
-
Summary: Potential NPE in 
org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
invalid/incomplete plugin metadata  (was: Potential NPE in 
org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid 
metadata)

> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid/incomplete plugin metadata
> --
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}
> 
> 
> 
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
> 
> 
> filevault-package-maven-plugin
> filevault-package-maven-plugin
> 
> 
> 
> {code}
> This leads to an NPE when trying to deploy a new version with 
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge 
> (Metadata.java:276)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
>  (AbstractRepositoryMetadata.java:121)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
>  (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
> (DefaultArtifactDeployer.java:142)
> {code}
> Although this happened in the context of using 
> "org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
> (https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in 
> Maven.
> The metadata is probably invalid but the Metadata class should be more robust 
> when trying to do the merge in 
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
>  and just ignore all plugin entries without all mandatory elements.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid metadata

[Konrad Windszus (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465673#comment-17465673
 ] 

Konrad Windszus commented on MNG-7375:
--

According to the schema at 
https://maven.apache.org/xsd/repository-metadata-1.1.0.xsd, all elements below 
{{plugin}} are optional.

> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid metadata
> 
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}
> 
> 
> 
> Apache Jackrabbit FileVault - Package Maven Plugin
> filevault-package
> filevault-package-maven-plugin
> 
> 
> filevault-package-maven-plugin
> filevault-package-maven-plugin
> 
> 
> 
> {code}
> This leads to an NPE when trying to deploy a new version with 
> {{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.maven.artifact.repository.metadata.Metadata.merge 
> (Metadata.java:276)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
>  (AbstractRepositoryMetadata.java:121)
> at 
> org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
>  (AbstractRepositoryMetadata.java:67)
> at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
> (MetadataBridge.java:65)
> at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
> (DefaultDeployer.java:433)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:321)
> at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
> (DefaultDeployer.java:213)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
> (DefaultRepositorySystem.java:386)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
> (DefaultArtifactDeployer.java:142)
> {code}
> Although this happened in the context of using 
> "org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
> (https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in 
> Maven.
> The metadata is probably invalid but the Metadata class should be more robust 
> when trying to do the merge in 
> https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
>  and just ignore all plugin entries without all mandatory elements.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid metadata

[Konrad Windszus (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated MNG-7375:
-
Description: 
Currently the metadata at 
https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
 contains an invalid entry without a prefix:
{code}



Apache Jackrabbit FileVault - Package Maven Plugin
filevault-package
filevault-package-maven-plugin


filevault-package-maven-plugin
filevault-package-maven-plugin



{code}

This leads to an NPE when trying to deploy a new version with 
{{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:

{code}
Caused by: java.lang.NullPointerException
at org.apache.maven.artifact.repository.metadata.Metadata.merge 
(Metadata.java:276)
at 
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
 (AbstractRepositoryMetadata.java:121)
at 
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
 (AbstractRepositoryMetadata.java:67)
at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
(MetadataBridge.java:65)
at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
(DefaultDeployer.java:433)
at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
(DefaultDeployer.java:321)
at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
(DefaultDeployer.java:213)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
(DefaultRepositorySystem.java:386)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
(DefaultArtifactDeployer.java:142)
{code}

Although this happened in the context of using 
"org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
(https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in Maven.

The metadata is probably invalid but the Metadata class should be more robust 
when trying to do the merge in 
https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100
 and just ignore all plugin entries without all mandatory elements.


  was:
Currently the metadata at 
https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
 contains an invalid entry without a prefix:
{code}



Apache Jackrabbit FileVault - Package Maven Plugin
filevault-package
filevault-package-maven-plugin


filevault-package-maven-plugin
filevault-package-maven-plugin



{code}

This leads to an NPE when trying to deploy a new version with 
{{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:

{code}
Caused by: java.lang.NullPointerException
at org.apache.maven.artifact.repository.metadata.Metadata.merge 
(Metadata.java:276)
at 
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
 (AbstractRepositoryMetadata.java:121)
at 
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
 (AbstractRepositoryMetadata.java:67)
at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
(MetadataBridge.java:65)
at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
(DefaultDeployer.java:433)
at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
(DefaultDeployer.java:321)
at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
(DefaultDeployer.java:213)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
(DefaultRepositorySystem.java:386)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
(DefaultArtifactDeployer.java:142)
{code}

Although this happened in the context of using 
"org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
(https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in Maven 
and should be more robust.

Although the metadata is probably invalid, the Metadata class should be more 
robust when trying to do the merge in 
https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100



> Potential NPE in 
> org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with 
> invalid metadata
> 
>
> Key: MNG-7375
> URL: https://issues.apache.org/jira/browse/MNG-7375
> Project: Maven
>  Issue Type: Improvement
>  Components: Artifacts and Repositories
>Affects Versions: 3.8.4
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the metadata at 
> https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
>  contains an invalid entry without a prefix:
> {code}

[jira] [Created] (MNG-7375) Potential NPE in org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid metadata

[Konrad Windszus (Jira)]

Konrad Windszus created MNG-7375:


 Summary: Potential NPE in 
org.apache.maven.artifact.repository.metadata.Metadata.merge(...) with invalid 
metadata
 Key: MNG-7375
 URL: https://issues.apache.org/jira/browse/MNG-7375
 Project: Maven
  Issue Type: Improvement
  Components: Artifacts and Repositories
Affects Versions: 3.8.4
Reporter: Konrad Windszus


Currently the metadata at 
https://repository.apache.org/service/local/repositories/snapshots/content/org/apache/jackrabbit/maven-metadata.xml
 contains an invalid entry without a prefix:
{code}



Apache Jackrabbit FileVault - Package Maven Plugin
filevault-package
filevault-package-maven-plugin


filevault-package-maven-plugin
filevault-package-maven-plugin



{code}

This leads to an NPE when trying to deploy a new version with 
{{org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(...)}}:

{code}
Caused by: java.lang.NullPointerException
at org.apache.maven.artifact.repository.metadata.Metadata.merge 
(Metadata.java:276)
at 
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata
 (AbstractRepositoryMetadata.java:121)
at 
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository
 (AbstractRepositoryMetadata.java:67)
at org.apache.maven.artifact.repository.metadata.MetadataBridge.merge 
(MetadataBridge.java:65)
at org.eclipse.aether.internal.impl.DefaultDeployer.upload 
(DefaultDeployer.java:433)
at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
(DefaultDeployer.java:321)
at org.eclipse.aether.internal.impl.DefaultDeployer.deploy 
(DefaultDeployer.java:213)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy 
(DefaultRepositorySystem.java:386)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
(DefaultArtifactDeployer.java:142)
{code}

Although this happened in the context of using 
"org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8" 
(https://issues.sonatype.org/browse/NEXUS-30749) the affected code is in Maven 
and should be more robust.

Although the metadata is probably invalid, the Metadata class should be more 
robust when trying to do the merge in 
https://github.com/apache/maven/blob/951b5ee95f40147abbc2bb9d928e408b85d5aef3/maven-repository-metadata/src/main/mdo/metadata.mdo#L100




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (ARCHETYPE-624) scope = provided for artifacts provided by Maven Core

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/ARCHETYPE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed ARCHETYPE-624.
---
  Assignee: Herve Boutemy
Resolution: Fixed

done in 
https://github.com/apache/maven-archetype/commit/caffb9e19b70bf7db4c3aa7e0378dab33a66c8af

> scope = provided for artifacts provided by Maven Core
> -
>
> Key: ARCHETYPE-624
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-624
> Project: Maven Archetype
>  Issue Type: Improvement
>  Components: Plugin
>Affects Versions: 3.2.0
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.2.1
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (ARCHETYPE-624) scope = provided for artifacts provided by Maven Core

[Herve Boutemy (Jira)]

Herve Boutemy created ARCHETYPE-624:
---

 Summary: scope = provided for artifacts provided by Maven Core
 Key: ARCHETYPE-624
 URL: https://issues.apache.org/jira/browse/ARCHETYPE-624
 Project: Maven Archetype
  Issue Type: Improvement
  Components: Plugin
Affects Versions: 3.2.0
Reporter: Herve Boutemy
 Fix For: 3.2.1






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-jar-plugin] dependabot[bot] commented on pull request #31: Bump mavenVersion from 3.1.0 to 3.8.4

[GitBox]

dependabot[bot] commented on pull request #31:
URL: https://github.com/apache/maven-jar-plugin/pull/31#issuecomment-1001438433


   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. You can also ignore all major, minor, or patch 
releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
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-invoker-plugin] dependabot[bot] commented on pull request #86: Bump mavenVersion from 3.2.5 to 3.8.4

[GitBox]

dependabot[bot] commented on pull request #86:
URL: 
https://github.com/apache/maven-invoker-plugin/pull/86#issuecomment-1001437981


   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. You can also ignore all major, minor, or patch 
releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
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-invoker-plugin] slawekjaranowski closed pull request #86: Bump mavenVersion from 3.2.5 to 3.8.4

[GitBox]

slawekjaranowski closed pull request #86:
URL: https://github.com/apache/maven-invoker-plugin/pull/86


   


-- 
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 #415: [SUREFIRE-1955] Switch project to Java 8

[GitBox]

slawekjaranowski commented on pull request #415:
URL: https://github.com/apache/maven-surefire/pull/415#issuecomment-1001437135


   This PR only change Java version to 1.8 with only necessary changes to make 
project build.
   So it is for 1 only from your list.
   
   Maven Api was changed in #412 


-- 
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 closed pull request #416: Bump plexus-java from 1.0.7 to 1.1.0

[GitBox]

slawekjaranowski closed pull request #416:
URL: https://github.com/apache/maven-surefire/pull/416


   


-- 
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 closed pull request #417: Bump xmlunit-core from 2.6.0 to 2.8.4

[GitBox]

slawekjaranowski closed pull request #417:
URL: https://github.com/apache/maven-surefire/pull/417


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-surefire] dependabot[bot] commented on pull request #417: Bump xmlunit-core from 2.6.0 to 2.8.4

[GitBox]

dependabot[bot] commented on pull request #417:
URL: https://github.com/apache/maven-surefire/pull/417#issuecomment-1001435430


   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
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-parent] slachiewicz merged pull request #43: Bump plexus-component-annotations from 2.1.0 to 2.1.1

[GitBox]

slachiewicz merged pull request #43:
URL: https://github.com/apache/maven-parent/pull/43


   


-- 
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-apache-parent] slachiewicz merged pull request #58: Bump maven-site-plugin from 3.9.1 to 3.10.0

[GitBox]

slachiewicz merged pull request #58:
URL: https://github.com/apache/maven-apache-parent/pull/58


   


-- 
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-doxia-converter] slachiewicz merged pull request #21: Bump doxiaVersion from 1.10 to 1.11.1

[GitBox]

slachiewicz merged pull request #21:
URL: https://github.com/apache/maven-doxia-converter/pull/21


   


-- 
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-doxia-converter] slachiewicz merged pull request #22: Bump plexus-container-default from 2.1.0 to 2.1.1

[GitBox]

slachiewicz merged pull request #22:
URL: https://github.com/apache/maven-doxia-converter/pull/22


   


-- 
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