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

Stefan Seifert commented on SLING-8080:
---------------------------------------

the problem affects all recent version of slingstart-maven-plugin

the problem occurs only if other slingfeature/slingstart artifacts in a 
provisioning file are referenced with a version number in POM, it works without 
problems for bundle artifacts.

comparing two runs with versions from POM vs. versions defined in feature model 
for the slingfeature/slingstart references (sling startet and launchpad 
test-bundles in this case) produces the same "final" model in 
{{target/slingstart.txt}}, but differs in this file 
{{slingstart-tmp/standalone/resources/provisioning/model.txt}}. in the first 
case - where the tests fail and the versions are in the POM - the references to 
the slingfeature/slingstart artifacts are *not* removed from the model, 
although they where already resolved - this block is contained in the error 
case, but not contained in the success case:
{noformat}
# Dependencies
[artifacts]
  
org.apache.sling/org.apache.sling.launchpad.test-bundles/12-SNAPSHOT/slingfeature
  org.apache.sling/org.apache.sling.starter/12-SNAPSHOT/slingstart
{noformat}

it looks like the merging of the provisioning files into one effective model 
fails if the version is not defined in the provisioning file itself. perhaps 
the code that removes those after the merging was successful checks only for 
the real version, and ignores the fact that the version might be inherited from 
the POM.

i had a quick look in the merging code of the provisioning model/slingstart 
file but did not find at once the place where this might happening.

> Almost all ITs fail after the Starter 11 release
> ------------------------------------------------
>
>                 Key: SLING-8080
>                 URL: https://issues.apache.org/jira/browse/SLING-8080
>             Project: Sling
>          Issue Type: Bug
>          Components: Starter, Testing
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Critical
>
> Almost all tests fail:
> {noformat}
> [ERROR] Tests run: 575, Failures: 561, Errors: 10, Skipped: 1
> {noformat}
> I noticed that Sling is permanently in the 'Apache Sling is starting up' 
> phase.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to