On Tuesday 19 December 2017 12:40:45 Konrad Windszus wrote:
> I think you are running into https://issues.apache.org/jira/browse/MNG-1911
> <https://issues.apache.org/jira/browse/MNG-1911>. You cannot build and use
> the Maven extension in the same Maven reactor build (if it is an
> extension). Please check if building slingstart-maven-plugin separately and
> afterwards triggering the reactor works for you.

Removing slingstart-maven-plugin from reactor does not help.

Regards,
O.

> Thanks,
> Konrad
> 
> > On 19. Dec 2017, at 12:27, Oliver Lietz <[email protected]> wrote:
> > 
> > On Monday 18 December 2017 18:29:50 Konrad Windszus wrote:
> >> Hi Oli,
> > 
> > Hi Konrad,
> > 
> >> Could you do me a favour and start the Maven build with debug options and
> >> set a breakpoint to
> >> https://github.com/apache/sling-slingstart-maven-plugin/blob/c74831bd13e9
> >> 88
> >> e87192eadf75de5dc6daacd61d/src/main/java/org/apache/sling/maven/slingstar
> >> t/P omArtifactVersionResolver.java#L55
> >> <https://github.com/apache/sling-slingstart-maven-plugin/blob/c74831bd13e
> >> 98
> >> 8e87192eadf75de5dc6daacd61d/src/main/java/org/apache/sling/maven/slingsta
> >> rt/ PomArtifactVersionResolver.java#L55>. Basically that condition should
> >> be true and return the proper version. I am wondering why this is not
> >> the case on your computer.
> > 
> > there is an issue with slingstart-maven-plugin running in reactor builds
> > which is further indicated when setting a breakpoint and debugging into
> > code: Source code does not match the bytecode (from IDEA).
> > 
> > So Maven picks up an older version, probably 1.7.2 from Parent 32.
> > Is this a known limitation? Have you tried a reactor build yourself?
> > I get the same issue on two different machines. Also building slingstart-
> > maven-plugin fails on both machines when not skipping tests:
> > 
> > -------------------------------------------------------
> > T E S T S
> > -------------------------------------------------------
> > Running org.apache.sling.maven.slingstart.PomArtifactVersionResolverTest
> > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> > - in org.apache.sling.maven.slingstart.PomArtifactVersionResolverTest
> > Running org.apache.sling.maven.slingstart.PreparePackageMojoTest
> > [debug] Unpacking
> > /Users/olli/.m2/repository/org/apache/sling/org.apache.sling.commons.class
> > loader/1.3.2/org.apache.sling.commons.classloader-1.3.2.jar to
> > 
> >  /var/folders/rd/[...]/T/PreparePackageMojoTest8164747194337206383/slingst
> >  art-> 
> > tmp/standalone
> > [info] Creating subsystem base file: test1.subsystem-base
> > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.267 sec
> > <<< FAILURE! - in
> > org.apache.sling.maven.slingstart.PreparePackageMojoTest
> > testSubsystemBaseGeneration(org.apache.sling.maven.slingstart.PreparePack
> > ageMojoTest) Time elapsed: 0.011 sec  <<< ERROR!
> > org.apache.maven.plugin.MojoExecutionException: Problem creating subsystem
> > .esa file
> > /var/folders/rd/[...]/T/PreparePackageMojoTest7995980118310884160/slingsta
> > rt- tmp/test1.subsystem-base
> > 
> >     at 
> > sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> >     at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> >     at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> >     at
> > 
> > sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.ja
> > va:214)> 
> >     at java.nio.file.Files.newByteChannel(Files.java:361)
> >     at java.nio.file.Files.newByteChannel(Files.java:407)
> >     at
> > 
> > java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.jav
> > a:384)> 
> >     at java.nio.file.Files.newInputStream(Files.java:152)
> >     at java.nio.file.Files.copy(Files.java:3068)
> >     at
> > 
> > org.apache.sling.maven.slingstart.PreparePackageMojo.createSubsystemBaseFi
> > le(PreparePackageMojo.java:382)> 
> >     at
> > 
> > org.apache.sling.maven.slingstart.PreparePackageMojo.buildSubsystemBase(Pr
> > eparePackageMojo.java:255)> 
> >     at
> > 
> > org.apache.sling.maven.slingstart.PreparePackageMojo.buildContentsMap(Prep
> > arePackageMojo.java:235)> 
> >     at
> > 
> > org.apache.sling.maven.slingstart.PreparePackageMojo.prepareGlobal(Prepare
> > PackageMojo.java:141)> 
> >     at
> > 
> > org.apache.sling.maven.slingstart.PreparePackageMojo.execute(PreparePackag
> > eMojo.java:131)> 
> >     at
> > 
> > org.apache.sling.maven.slingstart.PreparePackageMojoTest.testSubsystemBase
> > Generation(PreparePackageMojoTest.java:176)
> > 
> > 
> > Results :
> > 
> > Tests in error:
> >  PreparePackageMojoTest.testSubsystemBaseGeneration:176 ยป MojoExecution
> > 
> > Problem...
> > 
> > Tests run: 5, Failures: 0, Errors: 1, Skipped: 0
> > 
> > Regards,
> > O.
> > 
> >>> On 18. Dec 2017, at 15:14, Oliver Lietz <[email protected]> wrote:
> >>> 
> >>> On Monday 18 December 2017 14:53:50 Konrad Windszus wrote:
> >>>> There is a dependency from Validation Core to SlingStart Maven Plugin
> >>>> 1.7.14 (which is not yet released to Maven Central). An older version
> >>>> of
> >>>> SlingStart Maven Plugin does not allow to leave out the version here
> >>>> from
> >>>> the provisioning model. This is a chicken/egg problem. But switching to
> >>>> the
> >>>> latest SNAPSHOT (i.e. slingstart-maven-plugin 1.7.15-SNAPSHOT)
> >>>> temporarily
> >>>> should allow you to build again.
> >>> 
> >>> That's not the problem as I have built 1.7.14 yesterday around 2 pm
> >>> (it's
> >>> in my local Maven repo) and the error is the same with 1.7.15-SNAPSHOT.
> >>> 
> >>> O.
> >>> 
> >>>>> On 18. Dec 2017, at 14:29, Oliver Lietz <[email protected]> wrote:
> >>>>> 
> >>>>> On Sunday 17 December 2017 13:04:41 Konrad Windszus wrote:
> >>>>>> Hi,
> >>>>>> 
> >>>>>> We solved several issues in these releases:
> >>>>>> 
> >>>>>> SlingStart Maven Plugin:
> >>>>>> https://issues.apache.org/jira/projects/SLING/versions/12342309
> >>>>>> Validation
> >>>>>> Core & Test Services:
> >>>>>> https://issues.apache.org/jira/projects/SLING/versions/12342296
> >>>>> 
> >>>>> The latest changes in Validation Core break my aggregator [1] build:
> >>>>> 
> >>>>> beat:repos olli$ mvn clean install
> >>>>> [INFO] Scanning for projects...
> >>>>> [INFO] Extended Maven classpath (scope 'provided') by the dependencies
> >>>>> extracted from the Sling model.
> >>>>> [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.resolveArtifac
> >>>>> tV
> >>>>> er
> >>>>> sion (ModelResolveUtility.java:94)
> >>>>> 
> >>>>>  at
> >>>>> 
> >>>>> org.apache.sling.provisioning.model.EffectiveModelProcessor.processArt
> >>>>> if
> >>>>> ac
> >>>>> t
> >>>>> (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.after
> >>>>> Pr
> >>>>> oj
> >>>>> ectsRead (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/InternalErrorExceptio
> >>>>> n
> >>>>> 
> >>>>> Adding a version back for Validation Core unbreaks the build.
> >>>>> 
> >>>>> Regards,
> >>>>> O.
> >>>>> 
> >>>>> [1] https://github.com/oliverlietz/apache-sling-aggregator


Reply via email to