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

Bertrand Delacretaz commented on SLING-2770:
--------------------------------------------

We should fix that of course, but in the meantime you might be able to work 
around this by building the corresponding modules manually first.

All the Sling core modules are found in the bundles folder, and you can search 
names like org.apache.sling.resourceresolver in their pom.xml to find where 
which module is.
                
> Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
> -----------------------------------------------------------------------------
>
>                 Key: SLING-2770
>                 URL: https://issues.apache.org/jira/browse/SLING-2770
>             Project: Sling
>          Issue Type: Bug
>          Components: Launchpad
>    Affects Versions: Launchpad Builder 7
>            Reporter: Lukas Eder
>         Attachments: mvn-install-X-e.txt
>
>
> Building Launchpad from trunk fails as there seem to be some SNAPSHOT 
> versions missing from the Apache snapshot repositories.
> Below is the output from a mvn install command (-X -e output attached in a 
> file):
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
> details.
> [INFO] Scanning for projects...
> [INFO]                                                                        
>  
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT
> [INFO] 
> ------------------------------------------------------------------------
> [WARNING] The POM for 
> org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is 
> missing, no dependency information available
> [WARNING] The POM for 
> org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is 
> missing, no dependency information available
> [WARNING] The POM for 
> org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, 
> no dependency information available
> [WARNING] The POM for 
> org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is 
> missing, no dependency information available
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 5.804s
> [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013
> [INFO] Final Memory: 10M/81M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could 
> not resolve dependencies for project 
> org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following 
> artifacts could not be resolved: 
> org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, 
> org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, 
> org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, 
> org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure 
> to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT 
> in http://repository.apache.org/snapshots was cached in the local repository, 
> resolution will not be reattempted until the update interval of 
> apache.snapshots has elapsed or updates are forced -> [Help 1]
> [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/DependencyResolutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to