[
https://issues.apache.org/jira/browse/SLING-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835200#action_12835200
]
Justin Edelson commented on SLING-1202:
---------------------------------------
now that Sling is capable of producing a Karaf features.xml, I wonder if this
can be closed out.
> Artifact jackrabbit-api OSGI unresolved dependency in
> org.apache.sling.jcr.jackrabbit-jcr-server bundle
> -------------------------------------------------------------------------------------------------------
>
> Key: SLING-1202
> URL: https://issues.apache.org/jira/browse/SLING-1202
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Jackrabbit Server 2.0.6
> Environment: JDK15
> Reporter: Rafael Marins
>
> I've created a release.xml for deploying Sling Jackrabbit bundle in the
> Apache Karaf 1.1.0 framework, following the main ideas captured from
> http://cwiki.apache.org/SLING/launching-a-jcr-repository-inside-equinox.html.
> But when deploying I get an unresolved constraint:
> ka...@root> features:install sling-jackrabbit 2.0.5-SNAPSHOT
> Unresolved constraint in bundle org.apache.sling.jcr.base [40]:
> package; (&(package=org.apache.jackrabbit.api)(version>=1.5.0))
> I believe it could be fixed by including that missing artifactId within the
> maven-dependency-plugin configuration, like the following:
> <includeArtifactIds>
> jackrabbit-api,jackrabbit-jcr-rmi, ...
> </includeArtifactIds>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
