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 2008/12/03 09:31:44 UTC

[jira] Commented: (SLING-753) Create new launchpad package project

    [ https://issues.apache.org/jira/browse/SLING-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652715#action_12652715 ] 

Bertrand Delacretaz commented on SLING-753:
-------------------------------------------

Sounds good, the current way of building the webapps (launchpad/webapp, launchpad/testing and the recently added extensions/jcrinstall/testing) is complicated and causes duplication between modules.

Anything that allows these projects to inherit from a common base is welcome.

> Create new launchpad package project
> ------------------------------------
>
>                 Key: SLING-753
>                 URL: https://issues.apache.org/jira/browse/SLING-753
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad Launcher
>            Reporter: Felix Meschberger
>
> Currently the launchpad/app project prepares a runnable jar package from the launchpad/base project (providing the launcher) and all the bundles required for inclusion. The launchpad/webapp project takes the launchpad/app package and modifies it by adding servlet container integration and removing the embedded servlet container.
> This construct creates a complicated dependency in the webapp project on app internals.
> It would probably be better to have a launchpad/package project, which just packages everything which web app and app have in common and have the app and webapp projects extend the package by adding additional stuff required for the specific environment (standalone vs. servlet container).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.