[
https://issues.apache.org/jira/browse/SLING-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398392#comment-13398392
]
James Phillpotts edited comment on SLING-2514 at 6/21/12 12:44 PM:
-------------------------------------------------------------------
Forgot to mention, I also 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.version}",
was (Author: mrpotes):
Forgot to mention, I also had to add:
{noformat}
org.w3c.dom.ranges;uses:="org.w3c.dom";version="${fragment.xml.version}",
org.w3c.dom.traversal;uses:="org.w3c.dom";version="${fragment.xml.version}",
{noformat}
> API Fragment Bundles not available in maven repositories
> --------------------------------------------------------
>
> Key: SLING-2514
> URL: https://issues.apache.org/jira/browse/SLING-2514
> Project: Sling
> Issue Type: Bug
> Components: General, Maven Plugins and Archetypes
> Reporter: James Phillpotts
>
> After creating a launchpad module using the standalone archetype, on running
> the resultant jar, I got errors for missing dependencies org.xml.sax and
> javax.xml.parsers.
> I was pointed in the direction of the fragment bundles, but as they are not
> in a maven repository, I had to roll my own instead.
> I think these should be released to a maven repository, and should also be
> automatically added to the list.xml by the webapp and standalone launchpad
> archetypes. It would be nice if there was page under the site/bundles.html
> page to explain how this works, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira