rombert commented on PR #66:
URL: 
https://github.com/apache/sling-org-apache-sling-starter/pull/66#issuecomment-1117320272

   @kwin - it seems that the bnd-indexer-maven-plugin is unable to resolve the 
new SNAPSHOT dependencies we have for tests
   
   ```
   [ERROR] Failed to determine the artifact URI for artifact 
org.apache.sling:org.apache.sling.launchpad.test-fragment:jar:13-20220429.031819-11
   
   java.io.FileNotFoundException: Unable to index artifact 
org.apache.sling:org.apache.sling.launchpad.test-fragment:jar:13-20220429.031819-11.
 The repository Nexus is not known to this resolver
   
       at 
aQute.bnd.maven.indexer.plugin.IndexerMojo$RepositoryURLResolver.resolver 
(IndexerMojo.java:343)
   
       at aQute.bnd.maven.indexer.plugin.IndexerMojo.execute 
(IndexerMojo.java:177)
   
       at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
   
       at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:301)
   
       at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:211)
   
       at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:165)
   
       at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:157)
   
       at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:121)
   
       at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
   
       at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
   
       at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:127)
   
       at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
   
       at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
   
       at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
   
       at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
   
       at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
   
       at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
   
       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:282)
   
       at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:225)
   
       at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:406)
   
       at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:347)
   ```
   
   This is probably because of the references to the test content from 
https://github.com/apache/sling-org-apache-sling-starter/pull/66/files#diff-809481c400c1abb16967b7e08ab0865fbc81c685c9a6b21c40f770529cc48492
 .  I can (and probably should) make the test-fragment bundle a standalone 
module not tied to the starter, but there is nothing I can do about the 
test-services.
   
   Do you have an idea about how to fix this?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to