[
https://issues.apache.org/jira/browse/SLING-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761123#action_12761123
]
Felix Meschberger commented on SLING-1132:
------------------------------------------
We might want to choose a combined approach for manifest generation: Use the
hand-crafted import/export list from the static file and pom-define settings
for the rest of the manifest headers.
The reason for doing hand-crafted (or semi-automatic generation) of the
import/export list is performance and memory consumption: Calculating the
import/export list for the embedded jackrabbit repository is quite expensive
and might occasionaly break the build. So I decided to have a special profile
for generating the manifest and to use the pre-generated manifest in regular
builds.
> JCR Server Bundle has wrong bundle version
> ------------------------------------------
>
> Key: SLING-1132
> URL: https://issues.apache.org/jira/browse/SLING-1132
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Jackrabbit Server 2.0.4
> Reporter: Carsten Ziegeler
> Fix For: JCR Jackrabbit Server 2.0.5
>
>
> The 2.0.4-incubator release of the server bundle has the hardcoded
> 2.0.3-incubator-SNAPSHOT version as bundle version (and for the exports) This
> is due to the fact that we hard-code the manifest instead of letting it get
> generated by the bundle plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
