You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2007/02/06 16:51:05 UTC
[jira] Commented: (JCR-735) Add seperate maven module / packaging
for j2ee servlets.
[ https://issues.apache.org/jira/browse/JCR-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470618 ]
angela commented on JCR-735:
----------------------------
wouldn't it be better to move the webdav-related servlets to 'jackrabbit-server' then?
they can't be used without their webdav-implementation (simple/jcr-server) anyway, can they?
for the remaining servlets, you may still move them to a separate project.....
angela
> Add seperate maven module / packaging for j2ee servlets.
> --------------------------------------------------------
>
> Key: JCR-735
> URL: https://issues.apache.org/jira/browse/JCR-735
> Project: Jackrabbit
> Issue Type: Task
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1
> Reporter: Tobias Bocanegra
> Assigned To: Tobias Bocanegra
> Priority: Minor
>
> currently we have a a 'jackrabbit-webapp' project that provides some useful servlets for running a repository within an appserver (without JCA). they are bundled as classes in the jackrabbit-webapp.war and are not available separately in a jar file. this makes it almost impossible the use them as dependency in another project, since you would have to rip the war apart yourself and repackage them yourself.
> i suggest to divide the webapp project into 2 parts:
> jackrabbit-webapp (dummy parent project)
> |-- servlets --> jackrabbit-servlets.jar
> `-- webapp --> jackrabbit.war
> suggestions?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.