[
https://issues.apache.org/jira/browse/SLING-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592129#comment-13592129
]
Lukas Eder edited comment on SLING-2769 at 3/4/13 11:24 AM:
------------------------------------------------------------
Great, thanks for fixing the OSGi import. I'll create a new issue for the
failing trunk build, with more info...
https://issues.apache.org/jira/browse/SLING-2770
was (Author: lukas.eder):
Great, thanks for fixing the OSGi import. I'll create a new issue for the
failing trunk build, with more info...
> Broken sample: post-servlet-extensions
> --------------------------------------
>
> Key: SLING-2769
> URL: https://issues.apache.org/jira/browse/SLING-2769
> Project: Sling
> Issue Type: Bug
> Components: Launchpad, Samples
> Affects Versions: Launchpad Base 2.5.0
> Reporter: Lukas Eder
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> I'm learning about Sling and I'm trying to build and run the Sling samples
> within my Launchpad instance. For instance, I'm trying to run
> "samples/post-servlet-extensions". However, it seems that this sample depends
> on JCR 1.0, transitively, as I'm getting this error in the Sling Console,
> after loading the bundle:
> Imported Packages javax.jcr,version=[1.0,2) -- Cannot be resolved
> The Launchpad (version 6), however includes JCR 2.0. Is this sample outdated?
> How can this be fixed? Note:
> - I've tried upgrading the JCR dependency in ../../../parent/pom.xml before
> building the samples (with mvn clean install) - without success
> - I've tried upgrading the sample's dependencies on
> org.apache.sling.servlets.post from 2.0.4-incubator to 2.2.0 and on
> org.apache.sling.jcr.resource from 2.0.6 to 2.2.4 - without success
> - I've tried building Sling from trunk - without success, as many artefacts
> seem to be missing from the Apache SNAPSHOT repositories.
> I'm not having such issues with the "samples/urlfilter" sample
--
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
