You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2007/10/18 08:09:50 UTC
[jira] Created: (SLING-66) Create a microsling jar artifact in
addition the the war file
Create a microsling jar artifact in addition the the war file
-------------------------------------------------------------
Key: SLING-66
URL: https://issues.apache.org/jira/browse/SLING-66
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Bertrand Delacretaz
Priority: Minor
It'd be useful for the microsling build to generate a jar artifact in addition to the war, to make it easier for people to use microsling with other JCR repositories besides jackrabbit.
microsling expects to find a Repository as a ServletContext attribute named "javax.jcr.Repository", so as long as another Servlet initializes this attribute it should run with any JCR compliant repository.
JCR-955 does the same thing for the jackrabbit-webapp module
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-66) Create a microsling jar artifact in
addition to the war file
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-66.
--------------------------------------
Resolution: Fixed
Fixed in revision 585881
> Create a microsling jar artifact in addition to the war file
> ------------------------------------------------------------
>
> Key: SLING-66
> URL: https://issues.apache.org/jira/browse/SLING-66
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> It'd be useful for the microsling build to generate a jar artifact in addition to the war, to make it easier for people to use microsling with other JCR repositories besides jackrabbit.
> microsling expects to find a Repository as a ServletContext attribute named "javax.jcr.Repository", so as long as another Servlet initializes this attribute it should run with any JCR compliant repository.
> JCR-955 does the same thing for the jackrabbit-webapp module
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-66) Create a microsling jar artifact in
addition to the war file
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated SLING-66:
-------------------------------------
Summary: Create a microsling jar artifact in addition to the war file (was: Create a microsling jar artifact in addition the the war file)
> Create a microsling jar artifact in addition to the war file
> ------------------------------------------------------------
>
> Key: SLING-66
> URL: https://issues.apache.org/jira/browse/SLING-66
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> It'd be useful for the microsling build to generate a jar artifact in addition to the war, to make it easier for people to use microsling with other JCR repositories besides jackrabbit.
> microsling expects to find a Repository as a ServletContext attribute named "javax.jcr.Repository", so as long as another Servlet initializes this attribute it should run with any JCR compliant repository.
> JCR-955 does the same thing for the jackrabbit-webapp module
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.