[
https://issues.apache.org/jira/browse/SLING-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15551742#comment-15551742
]
Bertrand Delacretaz commented on SLING-6103:
--------------------------------------------
I have removed unnecessary SNAPSHOTs in revision 1763566, but the launcher
module still needs snapshots from the sibling test modules, so you probably
need to configure the addtional Maven Repository using the
org.ops4j.pax.url.mvn.repositories system property as per
https://ops4j1.jira.com/wiki/display/paxurl/Mvn+Protocol as Crankstart uses Pax
URL to get the artifacts.
Note that the tests currently fail with Java 8. For now I have just added an
enforcer rule to fail early with Java 8 (revision 1763567), we could just keep
this build active but failing or disable it until that's fixed.
> crankstart-launcher ITs fail when executed in isolation
> -------------------------------------------------------
>
> Key: SLING-6103
> URL: https://issues.apache.org/jira/browse/SLING-6103
> Project: Sling
> Issue Type: Bug
> Components: Crankstart
> Reporter: Robert Munteanu
> Labels: sling-IT
>
> When building on Jenkins SNAPSHOT dependencies can't be found. I assume that
> this is because they haven't been installed in the local repository and the
> IT does not look in the apache snapshots repository.
> In that case, it should be similar to SLING-6080 and SLING-6074.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
