You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/10/05 16:23:50 UTC

[jira] Closed: (SLING-43) Extend the sling-app project by support to build a complete jar file

     [ https://issues.apache.org/jira/browse/SLING-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-43.
----------------------------------

    Resolution: Fixed

Commited the extend pom with a new build profile "full", which builds said JAR file using the "full" classifier on the file created.

In addition, I modified the dependency plugin configuration to not strip the version names off the jar files copied such that it is easier to see, what is actually contained in the package (this is of course only convenience as the running framework has the final knowledge of what is installed at what version).

> Extend the sling-app project by support to build a complete jar file
> --------------------------------------------------------------------
>
>                 Key: SLING-43
>                 URL: https://issues.apache.org/jira/browse/SLING-43
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launcher
>    Affects Versions: 2.0.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> When building the sling-app project a JAR file is created which contains the launcher, the Felix framework, the OSGi core and compendium interfaces as well as core bundles installed and started on first start. This package contains enough bundles to launch Sling and present the Sling Management Console so as to install more bundles to complete the Sling environment.
> It would be practical to have a bundling of all bundles needed for a complete Sling environment in one JAR file. This could be implemented in the pom with a separate build profile, which just lists the additional dependencies and includes them the same way as in the default build.

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