[JBoss JIRA] (SHRINKRES-253) Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-253?page=com.atlassian.jira.plu... ]
Matous Jobanek updated SHRINKRES-253:
-------------------------------------
Git Pull Request: https://github.com/shrinkwrap/resolver/pull/101
> Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
> ---------------------------------------------------------------------------------------
>
> Key: SHRINKRES-253
> URL: https://issues.jboss.org/browse/SHRINKRES-253
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven-plugin
> Reporter: Matous Jobanek
> Assignee: Matous Jobanek
> Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> {code}
> [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce) @ shrinkwrap-resolver-maven-plugin ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
> For artifact {org.codehaus.plexus:plexus-classworlds:null:jar}: The version cannot be empty.
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ShrinkWrap Resolver Bill of Materials ............. SUCCESS [4.832s]
> [INFO] ShrinkWrap Resolver Aggregator .................... SUCCESS [27.086s]
> [INFO] Shrinkwrap Resolver Build Resources ............... SUCCESS [8.974s]
> [INFO] ShrinkWrap Resolver API ........................... SUCCESS [20.971s]
> [INFO] ShrinkWrap Resolver SPI ........................... SUCCESS [4.081s]
> [INFO] ShrinkWrap Resolver Maven API ..................... SUCCESS [12.928s]
> [INFO] ShrinkWrap Resolver Maven SPI ..................... SUCCESS [1.175s]
> [INFO] ShrinkWrap Resolver Maven Archive API ............. SUCCESS [1.969s]
> [INFO] ShrinkWrap Resolver Maven Implementation .......... SUCCESS [4:52.803s]
> [INFO] ShrinkWrap Resolver Maven Archive SPI ............. SUCCESS [1.070s]
> [INFO] ShrinkWrap Resolver Maven Archive Implementation .. SUCCESS [1:22.254s]
> [INFO] ShrinkWrap Resolver Dependency Chain .............. SUCCESS [2.726s]
> [INFO] ShrinkWrap Resolver Maven Plugin .................. FAILURE [1.540s]
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive API ... SKIPPED
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive Implementation SKIPPED
> [INFO] ShrinkWrap Resolver Gradle Dependency Chain ....... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7:48.587s
> [INFO] Finished at: Mon Aug 22 07:35:14 EDT 2016
> [INFO] Final Memory: 28M/236M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (enforce) on project shrinkwrap-resolver-maven-plugin: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :shrinkwrap-resolver-maven-plugin
> Build step 'Invoke top-level Maven targets' marked build as failure
> Recording test results
> Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-253) Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-253?page=com.atlassian.jira.plu... ]
Matous Jobanek commented on SHRINKRES-253:
------------------------------------------
However, the error was already there in the previous builds https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
> ---------------------------------------------------------------------------------------
>
> Key: SHRINKRES-253
> URL: https://issues.jboss.org/browse/SHRINKRES-253
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven-plugin
> Reporter: Matous Jobanek
> Assignee: Matous Jobanek
> Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> {code}
> [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce) @ shrinkwrap-resolver-maven-plugin ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
> For artifact {org.codehaus.plexus:plexus-classworlds:null:jar}: The version cannot be empty.
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ShrinkWrap Resolver Bill of Materials ............. SUCCESS [4.832s]
> [INFO] ShrinkWrap Resolver Aggregator .................... SUCCESS [27.086s]
> [INFO] Shrinkwrap Resolver Build Resources ............... SUCCESS [8.974s]
> [INFO] ShrinkWrap Resolver API ........................... SUCCESS [20.971s]
> [INFO] ShrinkWrap Resolver SPI ........................... SUCCESS [4.081s]
> [INFO] ShrinkWrap Resolver Maven API ..................... SUCCESS [12.928s]
> [INFO] ShrinkWrap Resolver Maven SPI ..................... SUCCESS [1.175s]
> [INFO] ShrinkWrap Resolver Maven Archive API ............. SUCCESS [1.969s]
> [INFO] ShrinkWrap Resolver Maven Implementation .......... SUCCESS [4:52.803s]
> [INFO] ShrinkWrap Resolver Maven Archive SPI ............. SUCCESS [1.070s]
> [INFO] ShrinkWrap Resolver Maven Archive Implementation .. SUCCESS [1:22.254s]
> [INFO] ShrinkWrap Resolver Dependency Chain .............. SUCCESS [2.726s]
> [INFO] ShrinkWrap Resolver Maven Plugin .................. FAILURE [1.540s]
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive API ... SKIPPED
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive Implementation SKIPPED
> [INFO] ShrinkWrap Resolver Gradle Dependency Chain ....... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7:48.587s
> [INFO] Finished at: Mon Aug 22 07:35:14 EDT 2016
> [INFO] Final Memory: 28M/236M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (enforce) on project shrinkwrap-resolver-maven-plugin: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :shrinkwrap-resolver-maven-plugin
> Build step 'Invoke top-level Maven targets' marked build as failure
> Recording test results
> Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-253) Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-253?page=com.atlassian.jira.plu... ]
Matous Jobanek commented on SHRINKRES-253:
------------------------------------------
Well, it seems that the Maven version causes another problems there in the integration tests
> Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
> ---------------------------------------------------------------------------------------
>
> Key: SHRINKRES-253
> URL: https://issues.jboss.org/browse/SHRINKRES-253
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven-plugin
> Reporter: Matous Jobanek
> Assignee: Matous Jobanek
> Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> {code}
> [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce) @ shrinkwrap-resolver-maven-plugin ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
> For artifact {org.codehaus.plexus:plexus-classworlds:null:jar}: The version cannot be empty.
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ShrinkWrap Resolver Bill of Materials ............. SUCCESS [4.832s]
> [INFO] ShrinkWrap Resolver Aggregator .................... SUCCESS [27.086s]
> [INFO] Shrinkwrap Resolver Build Resources ............... SUCCESS [8.974s]
> [INFO] ShrinkWrap Resolver API ........................... SUCCESS [20.971s]
> [INFO] ShrinkWrap Resolver SPI ........................... SUCCESS [4.081s]
> [INFO] ShrinkWrap Resolver Maven API ..................... SUCCESS [12.928s]
> [INFO] ShrinkWrap Resolver Maven SPI ..................... SUCCESS [1.175s]
> [INFO] ShrinkWrap Resolver Maven Archive API ............. SUCCESS [1.969s]
> [INFO] ShrinkWrap Resolver Maven Implementation .......... SUCCESS [4:52.803s]
> [INFO] ShrinkWrap Resolver Maven Archive SPI ............. SUCCESS [1.070s]
> [INFO] ShrinkWrap Resolver Maven Archive Implementation .. SUCCESS [1:22.254s]
> [INFO] ShrinkWrap Resolver Dependency Chain .............. SUCCESS [2.726s]
> [INFO] ShrinkWrap Resolver Maven Plugin .................. FAILURE [1.540s]
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive API ... SKIPPED
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive Implementation SKIPPED
> [INFO] ShrinkWrap Resolver Gradle Dependency Chain ....... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7:48.587s
> [INFO] Finished at: Mon Aug 22 07:35:14 EDT 2016
> [INFO] Final Memory: 28M/236M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (enforce) on project shrinkwrap-resolver-maven-plugin: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :shrinkwrap-resolver-maven-plugin
> Build step 'Invoke top-level Maven targets' marked build as failure
> Recording test results
> Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-253) Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-253?page=com.atlassian.jira.plu... ]
Matous Jobanek edited comment on SHRINKRES-253 at 8/23/16 9:49 AM:
-------------------------------------------------------------------
The problem is with the dependencyManagement part there in the maven/maven-plugin/pom.xml file [here |https://github.com/shrinkwrap/resolver/blob/master/maven/maven-plugin/pom.xml#L22-L37]
it should have been removed.
The reason why it hadn't failed either locally on my pc or on travis is the Maven version - the jenkins job uses 3.1.1, but travis 3.2.5 and I use 3.3.9
was (Author: mjobanek):
The problem is with the dependencyManagement part there in the maven/maven-plugin/pom.xml file [here |https://github.com/shrinkwrap/resolver/blob/master/maven/maven-plugin/pom.xml#L22-L37]
it should have been removed.
The reason why it hadn't failed either locally on my pc or on travis is the Maven version - the jenkins job uses 3.1.1, but travis 3.2.5 and I use 3.9.9
> Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
> ---------------------------------------------------------------------------------------
>
> Key: SHRINKRES-253
> URL: https://issues.jboss.org/browse/SHRINKRES-253
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven-plugin
> Reporter: Matous Jobanek
> Assignee: Matous Jobanek
> Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> {code}
> [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce) @ shrinkwrap-resolver-maven-plugin ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
> For artifact {org.codehaus.plexus:plexus-classworlds:null:jar}: The version cannot be empty.
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ShrinkWrap Resolver Bill of Materials ............. SUCCESS [4.832s]
> [INFO] ShrinkWrap Resolver Aggregator .................... SUCCESS [27.086s]
> [INFO] Shrinkwrap Resolver Build Resources ............... SUCCESS [8.974s]
> [INFO] ShrinkWrap Resolver API ........................... SUCCESS [20.971s]
> [INFO] ShrinkWrap Resolver SPI ........................... SUCCESS [4.081s]
> [INFO] ShrinkWrap Resolver Maven API ..................... SUCCESS [12.928s]
> [INFO] ShrinkWrap Resolver Maven SPI ..................... SUCCESS [1.175s]
> [INFO] ShrinkWrap Resolver Maven Archive API ............. SUCCESS [1.969s]
> [INFO] ShrinkWrap Resolver Maven Implementation .......... SUCCESS [4:52.803s]
> [INFO] ShrinkWrap Resolver Maven Archive SPI ............. SUCCESS [1.070s]
> [INFO] ShrinkWrap Resolver Maven Archive Implementation .. SUCCESS [1:22.254s]
> [INFO] ShrinkWrap Resolver Dependency Chain .............. SUCCESS [2.726s]
> [INFO] ShrinkWrap Resolver Maven Plugin .................. FAILURE [1.540s]
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive API ... SKIPPED
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive Implementation SKIPPED
> [INFO] ShrinkWrap Resolver Gradle Dependency Chain ....... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7:48.587s
> [INFO] Finished at: Mon Aug 22 07:35:14 EDT 2016
> [INFO] Final Memory: 28M/236M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (enforce) on project shrinkwrap-resolver-maven-plugin: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :shrinkwrap-resolver-maven-plugin
> Build step 'Invoke top-level Maven targets' marked build as failure
> Recording test results
> Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-253) Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-253?page=com.atlassian.jira.plu... ]
Matous Jobanek commented on SHRINKRES-253:
------------------------------------------
The problem is with the dependencyManagement part there in the maven/maven-plugin/pom.xml file [here |https://github.com/shrinkwrap/resolver/blob/master/maven/maven-plugin/pom.xml#L22-L37]
it should have been removed.
The reason why it hadn't failed either locally on my pc or on travis is the Maven version - the jenkins job uses 3.1.1, but travis 3.2.5 and I use 3.9.9
> Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
> ---------------------------------------------------------------------------------------
>
> Key: SHRINKRES-253
> URL: https://issues.jboss.org/browse/SHRINKRES-253
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven-plugin
> Reporter: Matous Jobanek
> Assignee: Matous Jobanek
> Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
>
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> {code}
> [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce) @ shrinkwrap-resolver-maven-plugin ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
> For artifact {org.codehaus.plexus:plexus-classworlds:null:jar}: The version cannot be empty.
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ShrinkWrap Resolver Bill of Materials ............. SUCCESS [4.832s]
> [INFO] ShrinkWrap Resolver Aggregator .................... SUCCESS [27.086s]
> [INFO] Shrinkwrap Resolver Build Resources ............... SUCCESS [8.974s]
> [INFO] ShrinkWrap Resolver API ........................... SUCCESS [20.971s]
> [INFO] ShrinkWrap Resolver SPI ........................... SUCCESS [4.081s]
> [INFO] ShrinkWrap Resolver Maven API ..................... SUCCESS [12.928s]
> [INFO] ShrinkWrap Resolver Maven SPI ..................... SUCCESS [1.175s]
> [INFO] ShrinkWrap Resolver Maven Archive API ............. SUCCESS [1.969s]
> [INFO] ShrinkWrap Resolver Maven Implementation .......... SUCCESS [4:52.803s]
> [INFO] ShrinkWrap Resolver Maven Archive SPI ............. SUCCESS [1.070s]
> [INFO] ShrinkWrap Resolver Maven Archive Implementation .. SUCCESS [1:22.254s]
> [INFO] ShrinkWrap Resolver Dependency Chain .............. SUCCESS [2.726s]
> [INFO] ShrinkWrap Resolver Maven Plugin .................. FAILURE [1.540s]
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive API ... SKIPPED
> [INFO] ShrinkWrap Resolver Embedded Gradle Archive Implementation SKIPPED
> [INFO] ShrinkWrap Resolver Gradle Dependency Chain ....... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7:48.587s
> [INFO] Finished at: Mon Aug 22 07:35:14 EDT 2016
> [INFO] Final Memory: 28M/236M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (enforce) on project shrinkwrap-resolver-maven-plugin: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :shrinkwrap-resolver-maven-plugin
> Build step 'Invoke top-level Maven targets' marked build as failure
> Recording test results
> Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-253) Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
by Matous Jobanek (JIRA)
Matous Jobanek created SHRINKRES-253:
----------------------------------------
Summary: Maven-plugin build fails with missing version of org.codehaus.plexus:plexus-classworlds
Key: SHRINKRES-253
URL: https://issues.jboss.org/browse/SHRINKRES-253
Project: ShrinkWrap Resolvers
Issue Type: Bug
Components: maven-plugin
Reporter: Matous Jobanek
Assignee: Matous Jobanek
Priority: Blocker
Fix For: 3.0.0-alpha-1
https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
{code}
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce) @ shrinkwrap-resolver-maven-plugin ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
For artifact {org.codehaus.plexus:plexus-classworlds:null:jar}: The version cannot be empty.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] ShrinkWrap Resolver Bill of Materials ............. SUCCESS [4.832s]
[INFO] ShrinkWrap Resolver Aggregator .................... SUCCESS [27.086s]
[INFO] Shrinkwrap Resolver Build Resources ............... SUCCESS [8.974s]
[INFO] ShrinkWrap Resolver API ........................... SUCCESS [20.971s]
[INFO] ShrinkWrap Resolver SPI ........................... SUCCESS [4.081s]
[INFO] ShrinkWrap Resolver Maven API ..................... SUCCESS [12.928s]
[INFO] ShrinkWrap Resolver Maven SPI ..................... SUCCESS [1.175s]
[INFO] ShrinkWrap Resolver Maven Archive API ............. SUCCESS [1.969s]
[INFO] ShrinkWrap Resolver Maven Implementation .......... SUCCESS [4:52.803s]
[INFO] ShrinkWrap Resolver Maven Archive SPI ............. SUCCESS [1.070s]
[INFO] ShrinkWrap Resolver Maven Archive Implementation .. SUCCESS [1:22.254s]
[INFO] ShrinkWrap Resolver Dependency Chain .............. SUCCESS [2.726s]
[INFO] ShrinkWrap Resolver Maven Plugin .................. FAILURE [1.540s]
[INFO] ShrinkWrap Resolver Embedded Gradle Archive API ... SKIPPED
[INFO] ShrinkWrap Resolver Embedded Gradle Archive Implementation SKIPPED
[INFO] ShrinkWrap Resolver Gradle Dependency Chain ....... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7:48.587s
[INFO] Finished at: Mon Aug 22 07:35:14 EDT 2016
[INFO] Final Memory: 28M/236M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (enforce) on project shrinkwrap-resolver-maven-plugin: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :shrinkwrap-resolver-maven-plugin
Build step 'Invoke top-level Maven targets' marked build as failure
Recording test results
Finished: FAILURE
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-252) Build Failing Locally in AdditionalRemoteRepositoryTestCase
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-252?page=com.atlassian.jira.plu... ]
Matous Jobanek commented on SHRINKRES-252:
------------------------------------------
Hi,
cannot reproduce it either:
{code}
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: /home/mjobanek/maven/apache-maven-3.3.9
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: /home/mjobanek/java/jdk1.8.0_101/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.5.5-300.fc24.x86_64", arch: "amd64", family: "unix"
{code}
> Build Failing Locally in AdditionalRemoteRepositoryTestCase
> -----------------------------------------------------------
>
> Key: SHRINKRES-252
> URL: https://issues.jboss.org/browse/SHRINKRES-252
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven
> Environment: ALR's local machine; does not appear to be an issue on CI server
> Reporter: Andrew Rubinger
> Assignee: Matous Jobanek
>
> {{shouldOverloadRepository(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.611 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> shouldOverloadCentral(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.523 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)}}
> However not present on authoritative CI Server:
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> Anyone else can reproduce?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-252) Build Failing Locally in AdditionalRemoteRepositoryTestCase
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-252?page=com.atlassian.jira.plu... ]
George Gastaldi commented on SHRINKRES-252:
-------------------------------------------
Sure, here it is:
{code}
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T14:41:47-02:00)
Maven home: /opt/maven
Java version: 1.8.0_92, vendor: Oracle Corporation
Java home: /usr/java/jdk1.8.0_92/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.6.6-300.fc24.x86_64", arch: "amd64", family: "unix"
{code}
> Build Failing Locally in AdditionalRemoteRepositoryTestCase
> -----------------------------------------------------------
>
> Key: SHRINKRES-252
> URL: https://issues.jboss.org/browse/SHRINKRES-252
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven
> Environment: ALR's local machine; does not appear to be an issue on CI server
> Reporter: Andrew Rubinger
> Assignee: Matous Jobanek
>
> {{shouldOverloadRepository(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.611 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> shouldOverloadCentral(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.523 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)}}
> However not present on authoritative CI Server:
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> Anyone else can reproduce?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-252) Build Failing Locally in AdditionalRemoteRepositoryTestCase
by Andrew Rubinger (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-252?page=com.atlassian.jira.plu... ]
Andrew Rubinger commented on SHRINKRES-252:
-------------------------------------------
[~gastaldi] Mind pasting in your environment?
$ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00)
Maven home: /home/alr/opt/apache/maven/apache-maven-3.3.9
Java version: 1.8.0_74, vendor: Oracle Corporation
Java home: /home/alr/opt/oracle/java/jdk1.8.0_74/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.6.4-301.fc24.x86_64", arch: "amd64", family: "unix"
> Build Failing Locally in AdditionalRemoteRepositoryTestCase
> -----------------------------------------------------------
>
> Key: SHRINKRES-252
> URL: https://issues.jboss.org/browse/SHRINKRES-252
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven
> Environment: ALR's local machine; does not appear to be an issue on CI server
> Reporter: Andrew Rubinger
> Assignee: Matous Jobanek
>
> {{shouldOverloadRepository(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.611 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> shouldOverloadCentral(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.523 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)}}
> However not present on authoritative CI Server:
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> Anyone else can reproduce?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SHRINKRES-252) Build Failing Locally in AdditionalRemoteRepositoryTestCase
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-252?page=com.atlassian.jira.plu... ]
George Gastaldi commented on SHRINKRES-252:
-------------------------------------------
Cannot reproduce in my machine
> Build Failing Locally in AdditionalRemoteRepositoryTestCase
> -----------------------------------------------------------
>
> Key: SHRINKRES-252
> URL: https://issues.jboss.org/browse/SHRINKRES-252
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven
> Environment: ALR's local machine; does not appear to be an issue on CI server
> Reporter: Andrew Rubinger
> Assignee: Matous Jobanek
>
> {{shouldOverloadRepository(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.611 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> shouldOverloadCentral(org.jboss.shrinkwrap.resolver.impl.maven.integration.AdditionalRemoteRepositoryTestCase) Time elapsed: 0.523 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)}}
> However not present on authoritative CI Server:
> https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_Resolver_upstream-mast...
> Anyone else can reproduce?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month