You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "James Phillpotts (JIRA)" <ji...@apache.org> on 2012/06/21 14:35:43 UTC
[jira] [Created] (SLING-2514) API Fragment Bundles not available in
maven repositories
James Phillpotts created SLING-2514:
---------------------------------------
Summary: 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
[jira] [Commented] (SLING-2514) API Fragment Bundles not available
in maven repositories
Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398454#comment-13398454 ]
Justin Edelson commented on SLING-2514:
---------------------------------------
Created SLING-2515 for the missing packages issue
> 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
[jira] [Resolved] (SLING-2514) API Fragment Bundles not available
in maven repositories
Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson resolved SLING-2514.
-----------------------------------
Resolution: Fixed
bundles have been released
> 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: Extensions
> Reporter: James Phillpotts
> Assignee: Justin Edelson
> Fix For: Framework Extension Fragment WS 1.0.0, Framework Extension Fragment XML 1.0.0, Framework Extension Fragment Transaction 1.0.0, Framework Extension Fragment Activation 1.0.0
>
>
> 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
[jira] [Updated] (SLING-2514) API Fragment Bundles not available in
maven repositories
Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson updated SLING-2514:
----------------------------------
Component/s: (was: General)
(was: Maven Plugins and Archetypes)
Extensions
Fix Version/s: Framework Extension Fragment Activation 1.0.0
Framework Extension Fragment Transaction 1.0.0
Framework Extension Fragment XML 1.0.0
Framework Extension Fragment WS 1.0.0
Assignee: Justin Edelson
> 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: Extensions
> Reporter: James Phillpotts
> Assignee: Justin Edelson
> Fix For: Framework Extension Fragment WS 1.0.0, Framework Extension Fragment XML 1.0.0, Framework Extension Fragment Transaction 1.0.0, Framework Extension Fragment Activation 1.0.0
>
>
> 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
[jira] [Comment Edited] (SLING-2514) API Fragment Bundles not
available in maven repositories
Posted by "James Phillpotts (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (SLING-2514) API Fragment Bundles not available
in maven repositories
Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398491#comment-13398491 ]
Justin Edelson commented on SLING-2514:
---------------------------------------
started vote on releases: http://sling.markmail.org/thread/75kbqyizvpxdhemp
> 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: Extensions
> Reporter: James Phillpotts
> Assignee: Justin Edelson
> Fix For: Framework Extension Fragment WS 1.0.0, Framework Extension Fragment XML 1.0.0, Framework Extension Fragment Transaction 1.0.0, Framework Extension Fragment Activation 1.0.0
>
>
> 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
[jira] [Commented] (SLING-2514) API Fragment Bundles not available
in maven repositories
Posted by "James Phillpotts (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398392#comment-13398392 ]
James Phillpotts commented on SLING-2514:
-----------------------------------------
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