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 2010/01/25 10:25:34 UTC
[jira] Created: (SLING-1313) API should be exported as 2.0.2
API should be exported as 2.0.2
-------------------------------
Key: SLING-1313
URL: https://issues.apache.org/jira/browse/SLING-1313
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR API 2.0.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: JCR API 2.0.6
The first release of the jcr api 2.0.2 was wrongly bundle with the 1.0 version of the JCR API
We fixed this with the 2.0,4 release, but unfortunately the exported package version was increased to 2.0.4 as well. If now some third bundle relies on 2.0.4 it requires the 2.0.4 version of the package to be available and does not work in an 2.0.2 environment anymore.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1313) API should be exported as 2.0.2
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1313.
-----------------------------------
> API should be exported as 2.0.2
> -------------------------------
>
> Key: SLING-1313
> URL: https://issues.apache.org/jira/browse/SLING-1313
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR API 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR API 2.0.6
>
>
> The first release of the jcr api 2.0.2 was wrongly bundle with the 1.0 version of the JCR API
> We fixed this with the 2.0,4 release, but unfortunately the exported package version was increased to 2.0.4 as well. If now some third bundle relies on 2.0.4 it requires the 2.0.4 version of the package to be available and does not work in an 2.0.2 environment anymore.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1313) API should be exported as 2.0.2
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1313.
-------------------------------------
Resolution: Fixed
> API should be exported as 2.0.2
> -------------------------------
>
> Key: SLING-1313
> URL: https://issues.apache.org/jira/browse/SLING-1313
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR API 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR API 2.0.6
>
>
> The first release of the jcr api 2.0.2 was wrongly bundle with the 1.0 version of the JCR API
> We fixed this with the 2.0,4 release, but unfortunately the exported package version was increased to 2.0.4 as well. If now some third bundle relies on 2.0.4 it requires the 2.0.4 version of the package to be available and does not work in an 2.0.2 environment anymore.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1313) API should be exported as 2.0.2
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804460#action_12804460 ]
Carsten Ziegeler commented on SLING-1313:
-----------------------------------------
Fixed with Revision: 902743
> API should be exported as 2.0.2
> -------------------------------
>
> Key: SLING-1313
> URL: https://issues.apache.org/jira/browse/SLING-1313
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR API 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR API 2.0.6
>
>
> The first release of the jcr api 2.0.2 was wrongly bundle with the 1.0 version of the JCR API
> We fixed this with the 2.0,4 release, but unfortunately the exported package version was increased to 2.0.4 as well. If now some third bundle relies on 2.0.4 it requires the 2.0.4 version of the package to be available and does not work in an 2.0.2 environment anymore.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.