You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2007/06/01 09:44:16 UTC
[jira] Updated: (JCR-955) [PATCH] jackrabbit-webapp pom.xml patch
to create an additional jar artifact
[ https://issues.apache.org/jira/browse/JCR-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated JCR-955:
------------------------------------
Attachment: JCR-955-jackrabbit-webapp.patch
> [PATCH] jackrabbit-webapp pom.xml patch to create an additional jar artifact
> ----------------------------------------------------------------------------
>
> Key: JCR-955
> URL: https://issues.apache.org/jira/browse/JCR-955
> Project: Jackrabbit
> Issue Type: Improvement
> Components: webapp
> Affects Versions: 1.3
> Reporter: Bertrand Delacretaz
> Priority: Trivial
> Attachments: JCR-955-jackrabbit-webapp.patch
>
>
> Modifies the jackrabbit-webapp pom.xml to create a jar artifact in addition to the existing war artifact, to allow the jackrabbit-webapp utility servlets to be reused in other modules.
> The right way would be to create a separate jar module for the servlets (or move them to jackrabbit-jcr-commons?), and reuse that jar as a dependency in the jackrabbit-webapp. So I'm not sure if this patch deserves to be applied to the trunk, but it can be useful as a workaround before a cleaner solution is implemented.
> See also http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/200705.mbox/%3C510143ac0705151453t7a0eb4cam859a40fb106e81f5@mail.gmail.com%3E which discusses possible improvements to these jackrabbit-webapp utility servlets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.