[
https://issues.apache.org/jira/browse/SM-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124280#comment-15124280
]
Krzysztof Sobkowiak commented on SM-2768:
-----------------------------------------
Actually the assembly is built using only the 'assembly' goal of the
karaf-maven-plugin. Instead of the 'archive' goal I have used the custom
assembly definition and the assembly maven plugin. Reasons and potential
solutions to avoid usage of the assembly plugin:
- The 'archive' goal produces 2 distributions - .zip and .tgz. We have decided
over a year ago to provide only one assembly. It's possible to configure the
karaf plugin to generate only one of the distribution - most reasonable would
be a zip file. But the unix scripts (e.g. karaf, client,...) have not set the
executable bit. *TODO*: We need a change in the 'archive' goal to enable the
executable bit for unix scripts in the generated zip file (like in the tgz
file). I'm going to raise an issue for this problem.
- We need the servicemix and servicemix.bat scripts as a copy of karaf and
karaf.bat scripts. It was easy to do with the assembly definition. *TODO*: we
need find another way to copy the renamed scripts into the assembly
- The custom assembly definition is used also to include in the assembly the
samples and Karaf demos. *TODO*: we should do this similar to the Karaf
assembly using the dependency plugin.
- The jar with the ServiceMix branding is copied into the lib directory using
the assembly definition as well. We can solve this using the dependency plugin
or by moving the branding properties from the branding jar into the /etc
directory.
> Upgrade to Apache Karaf 4
> -------------------------
>
> Key: SM-2768
> URL: https://issues.apache.org/jira/browse/SM-2768
> Project: ServiceMix
> Issue Type: Task
> Components: assemblies
> Reporter: Krzysztof Sobkowiak
> Assignee: Krzysztof Sobkowiak
> Fix For: 7.0.0.M1, 7.0.0
>
>
> The purpose of this task is to prepare the new ServiceMix 7 based on Karaf 4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)