I followed your advice and 1: Used svn checkout http://svn.apache.org/repos/asf/sling/trunk sling3 --revision 1145965 2: In that directory maven clean install
Pretty much identical results: the Launchpad installer tests failed, and the reason is java.lang.RuntimeException: URL [mvn:org.apache.sling/org.apache.sling.installer.factory.configuration/0.9.0-SNAPSHOT] could not be resolved. If I manually inspect that repository, there is no 0.9.0-SNAPSHOT, although there is a 1.0.0. It is clear I think that one of the bundles has advanced in version number, and this is causing me a problem because I don't have the old bundle in my local maven repository. (I am not a Maven guru so my interpretation could easily be wrong) I have tried changing the pom.xml, but it looks as though some of the files used are generated by code. For example: launchpad/testing/src/main/bundles/list.xml has a time data stamp that indicates it changes, and it has content including 9.0.0-SNAPSHOT Basically I am stuck. I don't have the knowledge of the Sling project structure to know how these files are generated. Is there any chance someone can give me a series of commands that actually works? Or fix the build so that the above two commands work On Thu, Jul 14, 2011 at 6:46 PM, Phil Rice <[email protected]> wrote: > Upon further investigation: > The file: \sling\contrib\launchpad\testing\src\main\bundles\list.xml > holds references to 4 projects all using 0.9.0-SNAPSHOT > <bundle> > <groupId>org.apache.sling</groupId> > > <artifactId>org.apache.sling.scripting.scala.hello-world</artifactId> > <version>0.9.0-SNAPSHOT</version> > </bundle> > There are also 0.9.0-SNAPSHOT references for > <artifactId>org.apache.sling.scripting.scala.script</artifactId> > <artifactId>org.apache.sling.scripting.scala.forum</artifactId> > <artifactId>org.apache.sling.scripting.scala.config</artifactId> > > This bundle isn't actually in the maven repository (the repository is > 1.0.0). This explains why the tests run, and yet it doesn't work for > me: Maven is both your friend and your enemy at times like this. Your > test system probably has 1.0.0 in its local repository, while I cannot > get them. > > Thanks for the specific svn number. I will use it, although I suspect > it will have the same issues. As long as their is no material change > between 0.9.0-SNAPSHOT and 1.0.0, I should be past this hurdle. > > Phil > > > > On Thu, Jul 14, 2011 at 1:48 PM, Bertrand Delacretaz > <[email protected]> wrote: >> Hi Phil, >> >> On Thu, Jul 14, 2011 at 2:37 PM, Phil Rice >> <[email protected]> wrote: >>> ...1: Roughly why would the "Apache Sling Installer Integration Tests" >>> fail. Do I need to be running something, is it an environment problem?... >> >> Our tests run every time there's an SVN change, with both Java 1.5 and >> 1.6, see the sling-trunk-1.* jobs at >> https://builds.apache.org/view/S-Z/view/Sling/ >> >> Right now those builds have no errors, so all tests pass with the svn >> revision that they used, which according to >> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.5/changes >> is revision 1145965. >> >> If the tests fail for you, try with that revision and please provide >> the output of java -version and mvn -v so that we can try and >> reproduce your problem. >> >>> ...2: What Subversive plug in do you recommend, are there any extra >>> plugins that I need as well?... >> >> I use subclipse, but only for read-only subversion operations - I >> don't trust it for writing. Didn't try subversive. >> >> -Bertrand >> >
