You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/16 14:12:11 UTC

[jira] [Created] (SLING-5296) scripting.sightly.testing build failure due to snapshot dependency on discovery

Stefan Egli created SLING-5296:
----------------------------------

             Summary: scripting.sightly.testing build failure due to snapshot dependency on discovery
                 Key: SLING-5296
                 URL: https://issues.apache.org/jira/browse/SLING-5296
             Project: Sling
          Issue Type: Bug
          Components: Scripting
            Reporter: Stefan Egli
            Assignee: Stefan Egli
            Priority: Minor


On jenkins every other day or so we now get a failure as follows:
{code}
Waiting for Jenkins to finish collecting data
[ERROR] Failed to execute goal on project org.apache.sling.scripting.sightly.testing: Could not resolve dependencies for project org.apache.sling:org.apache.sling.scripting.sightly.testing:slingstart:1.0.5-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.discovery.base:jar:1.0.0-SNAPSHOT, org.apache.sling:org.apache.sling.discovery.oak:jar:1.0.0-SNAPSHOT: Could not find artifact org.apache.sling:org.apache.sling.discovery.base:jar:1.0.0-SNAPSHOT in Nexus (http://repository.apache.org/snapshots) -> [Help 1]
[ERROR] 
{code}
(eg [here|https://builds.apache.org/job/sling-trunk-1.7/2720/console] or [here|https://builds.apache.org/job/sling-trunk-1.7/2716/console]).

This seems to be due to the fact that the SNAPSHOT artifacts get removed (at midnight perhaps) and {{scripting.sightly.testing}} gets built before {{discovery.*}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)