Hi Justin,
I couldn't find that artifact in a maven repository. However, I rolled
my own, adding in the transaction fragment and eventually got it
working.
I had to add:
org.w3c.dom.ranges;uses:="org.w3c.dom";version="${fragment.xml.version}"
,
org.w3c.dom.traversal;uses:="org.w3c.dom";version="${fragment.xml.versio
n}",
To the list of exported packages before sling would start up without
complaint, though.
While looking at what to do to fix this, I came across this felix bug:
https://issues.apache.org/jira/browse/FELIX-3235 - should sling be doing
something like that (specifying extra packages via the
org.osgi.framework.system.packages.extra property) rather than depending
on extra bundles to specify packages that are bundled with the JVM?
Cheers,
James
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Justin Edelson
Sent: 20 June 2012 20:48
To: [email protected]
Subject: Re: Sling launchpad build reports missing bundle
Hi James,
Can you try adding
<bundle>
<groupId>org.apache.sling</groupId>
<artifactId>org.apache.sling.fragment.xml</artifactId>
<version>0.0.1-SNAPSHOT</version>
</bundle>
to your bundle list at startLevel 0?
Regards,
Justin
On Wed, Jun 20, 2012 at 5:57 PM, Phillpotts, James <
[email protected]> wrote:
> Hi all,
>
> I've used the launchpad maven archetypes to create a build of the
> standalone launchpad, and have added my initial-content bundle to the
> list.xml.
>
> However, when I try running, I get lots of OSGi errors that seem to be
> complaining about missing required package org.xml.sax and
> javax.xml.parsers.
>
> Is there something extra I needed to do after generating my maven
> modules?
>
> Cheers,
> James
>
>
> PS - sorry about the legalese *sigh*
>
>
>
> Information in this e-mail and any attachments is confidential, and
> may not be copied or used by anyone other than the addressee, nor
> disclosed to any third party without our permission. There is no
> intention to create any legally binding contract or other binding
> commitment through the use of this electronic communication unless it
> is issued in accordance with the Experian Limited standard terms and
> conditions of purchase or other express written agreement between
> Experian Limited and the recipient. Although Experian has taken
> reasonable steps to ensure that this communication and any attachments
> are free from computer virus, you are advised to take your own steps
to ensure that they are actually virus free.
>
> Companies Act information: Registered name: Experian Limited.
> Registered
> office: Landmark House, Experian Way, NG2 Business Park, Nottingham,
> NG80 1ZZ, United Kingdom. Place of registration: England and Wales.
> Registered
> number: 653331
>
>