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:38:15 UTC
[jira] Created: (JCR-955) [PATCH] jackrabbit-webapp pom.xml patch
to create an additional jar artifact
[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
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.
[jira] Updated: (JCR-955) [PATCH] jackrabbit-webapp pom.xml patch
to create an additional jar artifact
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-955:
------------------------------
Affects Version/s: (was: 1.3)
Fix Version/s: 1.4
Contrary to my comment above, this change did go to 1.4, so I'm correcting the version tagging.
There are cases where having the jar artifact available is useful even now that we have jackrabbit-jcr-servlet, so let's keep this.
> [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: jackrabbit-webapp
> Reporter: Bertrand Delacretaz
> Assignee: Jukka Zitting
> Priority: Trivial
> Fix For: 1.4
>
> 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.
[jira] Updated: (JCR-955) [PATCH] jackrabbit-webapp pom.xml patch
to create an additional jar artifact
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (JCR-955) [PATCH] jackrabbit-webapp pom.xml patch
to create an additional jar artifact
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting reassigned JCR-955:
---------------------------------
Assignee: Jukka Zitting
> [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
> Assignee: Jukka Zitting
> 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.
[jira] Resolved: (JCR-955) [PATCH] jackrabbit-webapp pom.xml patch
to create an additional jar artifact
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-955.
-------------------------------
Resolution: Fixed
Thanks! Patch applied in revision 543651.
I won' t tag this for any future release, as I'd like to create a more reusable set of servlet components for this need. See JCR-956 for the more general issue. Once we have something like that I think we can revert this change.
> [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
> Assignee: Jukka Zitting
> 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.