You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Oliver Lietz (JIRA)" <ji...@apache.org> on 2013/04/23 14:17:17 UTC

[jira] [Comment Edited] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

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

Oliver Lietz edited comment on SLING-2789 at 4/23/13 12:16 PM:
---------------------------------------------------------------

version: This is my first shot and far from perfect. There was no feedback on the list [1] nor on this issue and I had to find out what fails/misses myself. I've added comments/TODOs in code to mark points where I have to look again to improve things. Maybe using requirements and capabilities [2] is a better approach. I'm used to mark stuff which is under development with BUILD-SNAPSHOT [3] (however I'm running this code in production and it works).

snapshots: Karaf testing stuff is moving from Apache Karaf to OPS4J Pax Exam [4] and both (Karaf 3.0 and Pax Exam 3.1) should be released in near future.

[1] http://mail-archives.apache.org/mod_mbox/sling-dev/201301.mbox/%3c201301231045.36201.apache@oliverlietz.de%3e
[2] http://blog.osgi.org/2012/03/requirements-and-capabilities.html
[3] http://ebr.springsource.com/repository/app/faq#q12
[4] https://github.com/ops4j/org.ops4j.pax.exam2

                
      was (Author: olli):
    version: This is my first shot and far from perfect. There was no feedback on the list [1] nor on this issue and I had to find out what fails/misses myself. I've added comments/TODOs in code to mark points where I have to look again to improve things. Maybe using requirements and capabilities is a better approach. I'm used to mark stuff which is under development with BUILD-SNAPSHOT [3] (however I'm running this code in production and it works).

snapshots: Karaf testing stuff is moving from Apache Karaf to OPS4J Pax Exam [4] and both (Karaf 3.0 and Pax Exam 3.1) should be released in near future.

[1] http://mail-archives.apache.org/mod_mbox/sling-dev/201301.mbox/%3c201301231045.36201.apache@oliverlietz.de%3e
[2] http://blog.osgi.org/2012/03/requirements-and-capabilities.html
[3] http://ebr.springsource.com/repository/app/faq#q12
[4] https://github.com/ops4j/org.ops4j.pax.exam2

                  
> deploying Sling 7-SNAPSHOT on Karaf fails
> -----------------------------------------
>
>                 Key: SLING-2789
>                 URL: https://issues.apache.org/jira/browse/SLING-2789
>             Project: Sling
>          Issue Type: Bug
>          Components: Launchpad
>    Affects Versions: Launchpad Builder 7
>         Environment: Karaf 3.0.0.*
>            Reporter: Oliver Lietz
>            Assignee: Carsten Ziegeler
>         Attachments: SLING-2789.patch, sling-launchpad-karaf.tar.gz
>
>
> $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start
> $ ssh -p 8101 karaf@localhost
> karaf@root()> feature:install http
> karaf@root()> feature:install webconsole
> karaf@root()> feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features
> karaf@root()> feature:install sling
> no errors on startup but JCR is nearly empty
> to prevent errors:
> - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml
> - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml
> - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml
> setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help

--
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