Hi, On Mon, 2020-01-06 at 09:13 -0800, Andreas Schaefer wrote: > Hi Robert > > All the IT tests are failing because the ‘core’ artifact is not > installed locally. The invoker goals are set to ‘clean install’ but > for the core that seems not to be applied. When I test it locally the > core artifact (both POM and the JAR file) are installed in the local > maven repo. > > This is the current path: > https://builds.apache.org/job/Sling/job/sling-feature-converter-maven-plugin/job/master/32/execution/node/3/ws/target/it/ > < > https://builds.apache.org/job/Sling/job/sling-feature-converter-maven-plugin/job/master/32/execution/node/3/ws/target/it/ > > to the created target folder of the latest build failure. > > The IT tests are failing because the Maven is not able to find the IT > project’s core artifact and that is not available in a remote repo. > It is working just fine for me locally. As far as I can tell this is > not an issue at all with the plugin but rather with the Invoker / IT > tests. > > Does anyone have a problem with it locally? > > Is there are way to check the layout of the local Maven repo of such > a build?
I can not try at the moment, but try moving away ~/.m2/repository and running the build then. It should fail in the same manner. Robert
