[jira] [Comment Edited] (SLING-7334) Validation Core breaks aggregator builds

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus edited comment on SLING-7334 at 12/27/17 4:11 PM:
------------------------------------------------------------------

I cannot reproduce with only the Sling validation modules in the aggregator. 
[~olli] Do you have a minimum aggregator project with which to reproduce the behaviour?

Also the stack trace from above hints at a wrong version of {{slingstart-maven-plugin}} being taken, as with the most recent 1.7.14 line 63 doesn't throw (https://github.com/apache/sling-slingstart-maven-plugin/blob/bec3fb21360e34c49329ad54f43336f47f79df36/src/main/java/org/apache/sling/maven/slingstart/PomArtifactVersionResolver.java#L63)


was (Author: kwin):
I cannot reproduce with only the Sling validation modules in the aggregator. 
[~olli] Do you have a minimum aggregator project with which to reproduce the behaviour?

> Validation Core breaks aggregator builds
> ----------------------------------------
>
>                 Key: SLING-7334
>                 URL: https://issues.apache.org/jira/browse/SLING-7334
>             Project: Sling
>          Issue Type: Bug
>          Components: Validation
>    Affects Versions: Validation Core 1.0.4
>            Reporter: Oliver Lietz
>
> Validation Core breaks aggregator builds after switching from {{org.apache.sling.testing.paxexam}} to {{slingstart-maven-plugin}} (SLING-7298) for integration tests. {{slingstart-maven-plugin}} itself is not part of aggregator project (MNG-1911).
> {noformat}
> [ERROR] Internal error: java.lang.IllegalArgumentException: Unable to resolve dependency: mvn:org.apache.sling/org.apache.sling.validation.core/LATEST -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.IllegalArgumentException: Unable to resolve dependency: mvn:org.apache.sling/org.apache.sling.validation.core/LATEST
>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:122)
>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke (Method.java:498)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> Caused by: java.lang.IllegalArgumentException: Unable to resolve dependency: mvn:org.apache.sling/org.apache.sling.validation.core/LATEST
>     at org.apache.sling.maven.slingstart.PomArtifactVersionResolver.resolve (PomArtifactVersionResolver.java:63)
>     at org.apache.sling.provisioning.model.ModelResolveUtility.resolveArtifactVersion (ModelResolveUtility.java:94)
>     at org.apache.sling.provisioning.model.EffectiveModelProcessor.processArtifact (EffectiveModelProcessor.java:51)
>     at org.apache.sling.provisioning.model.ModelProcessor.process (ModelProcessor.java:62)
>     at org.apache.sling.provisioning.model.ModelUtility.getEffectiveModel (ModelUtility.java:155)
>     at org.apache.sling.maven.slingstart.ModelPreprocessor.addDependencies (ModelPreprocessor.java:164)
>     at org.apache.sling.maven.slingstart.ModelPreprocessor.addDependencies (ModelPreprocessor.java:88)
>     at org.apache.sling.maven.slingstart.DependencyLifecycleParticipant.afterProjectsRead (DependencyLifecycleParticipant.java:78)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:267)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke (Method.java:498)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> [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/InternalErrorException
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)