[
https://issues.apache.org/jira/browse/SLING-7334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309430#comment-16309430
]
ASF GitHub Bot commented on SLING-7334:
---------------------------------------
kwin closed pull request #3: SLING-7334 only consider Maven modules leveraging
the same version of
URL: https://github.com/apache/sling-slingstart-maven-plugin/pull/3
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> slingstart-maven-plugin: DependencyLifecycleParticipant must only consider
> Maven modules leveraging the same version of slingstart-m-p
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-7334
> URL: https://issues.apache.org/jira/browse/SLING-7334
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Affects Versions: Slingstart Maven Plugin 1.7.14
> Reporter: Oliver Lietz
> Assignee: Konrad Windszus
> Fix For: Slingstart Maven Plugin 1.7.16
>
>
> The {{DependencyLifecycleParticipant}} is always being active for all module
> leveraging the plugin (in any version). That might lead to problems, when
> certain modules rely on a newer version of that extension. This is e.g. the
> case for Validation Core which breaks aggregator builds after switching from
> {{org.apache.sling.testing.paxexam}} to {{slingstart-maven-plugin}}
> (SLING-7298) for integration tests. This module relies on version 1.7.14 of
> the {{slingstart-maven-plugin}} and breaks with older versions.
> The {{slingstart-maven-plugin}} itself is not part of aggregator project
> (MNG-1911) though.
> {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)
