[jira] [Reopened] (FELIX-3778) Create all-in-one WebConsole build again

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger reopened FELIX-3778:
--------------------------------------


The proposed setup with different symbolic names for the three build profiles (regular, all-in-one, and debug) does not work out for localization: Localization can be done by attaching a fragment with translations to the web console bundle. If the bundle has different symbolic names, this fragment approach fails.

Instead of using the symbolic name for the differentiation, we might use the qualifier part of the version: In fact, it is always the same bundle with the same functionality. The only difference is the build setup. So a qualifier is probably the better choice of differentiation any way.

Apart from the bundle version qualifier, the rest remains untouched:
  * A maven classifier for the profiles
  * A "note" in the Bundle-Name header
  * The maven version
                
> Create all-in-one WebConsole build again
> ----------------------------------------
>
>                 Key: FELIX-3778
>                 URL: https://issues.apache.org/jira/browse/FELIX-3778
>             Project: Felix
>          Issue Type: Task
>          Components: Web Console
>    Affects Versions: webconsole-4.0.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: webconsole-4.0.2
>
>
> With FELIX-3279 we dropped the full build of the web console in favor of having a pure-OSGi style web console which imports its dependencies and thus allows for sharing of those dependencies across bundles.
> A discussion on deploying Web Console 4 in a simple manner has started on the users list [1] which shows, that from a pragmatism POV it makes perfect sense to have an all-in-one build of the web console embedding its required dependencies.
> This is to be done:
>   * Create a build profile for an all-in-one Web Console
>   * Embed Commons IO, Commons FileUpload, and JSON libraries
>   * Export embedded libraries
> I think it is save to assume the ServiceTracker API to be provided in the framework and thus need not be embedded.
> [1] http://markmail.org/message/wxqvwumk2c754o2z

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira