You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/10/01 08:48:23 UTC
[jira] Created: (SLING-1132) JCR Server Bundle has wrong bundle
version
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.
[jira] Updated: (SLING-1132) JCR Server Bundle has wrong bundle
version
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SLING-1132:
------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
> Fix For: JCR Jackrabbit Server 2.0.6
>
>
> 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.
[jira] Commented: (SLING-1132) JCR Server Bundle has wrong bundle
version
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833033#action_12833033 ]
Ian Boston commented on SLING-1132:
-----------------------------------
Warning: before doing the 2.0.6 release the manifest MUST be edited. Its currently at 2.0.5-SNAPSHOT
> 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.6
>
>
> 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.
[jira] Updated: (SLING-1132) JCR Server Bundle has wrong bundle
version
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SLING-1132:
------------------------------
Fix Version/s: (was: JCR Jackrabbit Server 2.0.6)
JCR Jackrabbit Server 2.0.8
Updated version in manifest in r909472, moving this jira to next release so that the version can be moved on there.
> 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
> Priority: Blocker
> Fix For: JCR Jackrabbit Server 2.0.8
>
>
> 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.
[jira] Updated: (SLING-1132) JCR Server Bundle has wrong bundle
version
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-1132:
-------------------------------------
Assignee: Ian Boston
Fix Version/s: JCR Jackrabbit Server 2.0.6
(was: JCR Jackrabbit Server 2.0.8)
This fix has been applied in time for the 2.0.6 release. In the meantime, this hardcoded MANIFEST.MF and the respective instructions to build it from with a build profile have been removed (Rev. 964875).
> 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
> Assignee: Ian Boston
> Priority: Blocker
> Fix For: JCR Jackrabbit Server 2.0.6
>
>
> 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.
Re: [jira] Commented: (SLING-1132) JCR Server Bundle has wrong bundle version
Posted by Ian Boston <ie...@tfd.co.uk>.
You could use the maven to process the resource and replace maven
properties as part of the build. IIRC the maven resources plugin has
this feature. [1]
Ian
1 http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
On 1 Oct 2009, at 08:56, Felix Meschberger (JIRA) wrote:
>
> [ 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.
>
[jira] Commented: (SLING-1132) JCR Server Bundle has wrong bundle
version
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (SLING-1132) JCR Server Bundle has wrong bundle
version
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-1132.
--------------------------------------
Resolution: Fixed
included in the release
> 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
> Assignee: Ian Boston
> Priority: Blocker
> Fix For: JCR Jackrabbit Server 2.0.6
>
>
> 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.