Oh, thanks for the info. I have added a patch to SLING-555 since I would prefer this is actually fixed in the current trunk. AFAIK it's actually required as long as we deploy stuff to the m2-incubating-repository.
Regards, Alex On Fri, Jul 4, 2008 at 5:54 PM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > Hi Alex, > > See https://issues.apache.org/jira/browse/SLING-555 and > http://incubator.apache.org/sling/site/getting-and-building-sling.html, > as a temporary workaround for this problem. > > -Bertrand > > On Fri, Jul 4, 2008 at 5:36 PM, Alexander Klimetschek <[EMAIL PROTECTED]> > wrote: >> Hi all, >> >> the current trunk fails with a fresh local repository (or at least one >> that does not include all sling builds) to build because >> samples/simple-demo/pom.xml references the maven-jspc-plugin in >> version 2.0.2-incubator which is not available (mvn clean or mvn >> eclipse:eclipse - my original goal - doesn't even work since it's a >> missing plugin dependency... stupid maven). The current trunk version >> of the plugin is already on version 2.0.3-incubator-SNAPSHOT and the >> 2.0.2-incubator version is only deployed on the >> http://people.apache.org/repo/m2-incubating-repository which is not >> configured for the simple-demo project. >> >> To fix it, I had to make these changes: >> >> parent/pom.xml must include the incubating repository as >> pluginRepository (it only references it as normal repository): >> >> <pluginRepository> >> <id>apache.incubating</id> >> <name>Apache Incubating Repository</name> >> <url>http://people.apache.org/repo/m2-incubating-repository</url> >> </pluginRepository> >> >> samples/simple-demo/pom.xml needs to reference the current parent pom: >> >> <parent> >> <groupId>org.apache.sling</groupId> >> <artifactId>sling</artifactId> >> <version>4-incubator-SNAPSHOT</version> >> <relativePath>../../parent/pom.xml</relativePath> >> </parent> >> >> >> Regards, >> Alex >> >> -- >> Alexander Klimetschek >> [EMAIL PROTECTED] >> > -- Alexander Klimetschek [EMAIL PROTECTED]
