You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Paco Avila (JIRA)" <ji...@apache.org> on 2006/08/02 11:55:13 UTC
[jira] Created: (JCR-529) New versions added after a restore have
bad version name
New versions added after a restore have bad version name
--------------------------------------------------------
Key: JCR-529
URL: http://issues.apache.org/jira/browse/JCR-529
Project: Jackrabbit
Issue Type: Bug
Components: versioning
Environment: Ubuntu Dapper
Reporter: Paco Avila
I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
- 1.0
- 1.1
- 1.2
- 1.3
- 1.4
- 1.3.1
- 1.3.2
- 1.3.3
- 1.3.4
- 1.3.5
New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12459648 ]
Tobias Bocanegra commented on JCR-529:
--------------------------------------
fixed tests.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Affects Versions: 1.0, 1.0.1, 1.1, 0.9, 1.1.1
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Fix For: 1.2
>
> Attachments: AbstractVersionManager.diff, DummyVersion.java, graph.txt
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Paco Avila (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12451123 ]
Paco Avila commented on JCR-529:
--------------------------------
I am the only affected by this issue? :(
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JCR-529) New versions added after a restore have
bad version name
Posted by "Paco Avila (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Paco Avila updated JCR-529:
---------------------------
Attachment: DummyVersion.java
This is a test case.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Attachments: DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Tobias Bocanegra reassigned JCR-529:
------------------------------------
Assignee: Tobias Bocanegra
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Tobias Bocanegra resolved JCR-529.
----------------------------------
Resolution: Fixed
fixed as suggested.
Committed revision 486694.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Paco Avila (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12458580 ]
Paco Avila commented on JCR-529:
--------------------------------
>From my point of view the test should check:
check(v1_3, phase, "1.0.1", 0);
And not:
check(v1_3, phase, "1.1.1", 0);
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Paco Avila (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12458927 ]
Paco Avila commented on JCR-529:
--------------------------------
Yes, I think you are rigth.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java, graph.txt
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12458917 ]
Tobias Bocanegra commented on JCR-529:
--------------------------------------
well, the above ascii art did not really work in jira :-( will attach a file.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java, graph.txt
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Tobias Bocanegra updated JCR-529:
---------------------------------
Attachment: graph.txt
Version Graph
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java, graph.txt
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12425232 ]
Tobias Bocanegra commented on JCR-529:
--------------------------------------
i vaguely remeber a similar bug....what version of jackrabbit are you using? the recent checkout?
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Attachments: DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Paco Avila (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12425266 ]
Paco Avila commented on JCR-529:
--------------------------------
Yes, I updated Jackarbbit source code yesterday. There is a test case attached if you wan't to test it.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Attachments: DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12458913 ]
Tobias Bocanegra commented on JCR-529:
--------------------------------------
imo, this should be the indented behaviour:
1.0
|
1.1
|
1.2
| \ \
1.3 1.2.0 1.2.0.0
| |
1.4 1.2.1
| | \
1.5 1.2.2 1.2.1.0
| |
1.6 1.2.1.1
so if you restored to 1.2 and 1.3 already exists, make a 1.2.0 on checkin since it's the "root version" of the new branch of the 1.2 version.
opinions?
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JCR-529) New versions added after a restore have
bad version name
Posted by "Paco Avila (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Paco Avila updated JCR-529:
---------------------------
Attachment: AbstractVersionManager.diff
This is my patch for this issue. With this modification, the versions are correctly named.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Tobias Bocanegra reopened JCR-529:
----------------------------------
need to validate tests
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JCR-529) New versions added after a restore have
bad version name
Posted by "Przemo Pakulski (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=comments#action_12458415 ]
Przemo Pakulski commented on JCR-529:
-------------------------------------
It seems that after applying patch test org.apache.jackrabbit.core.XATest.#testXAVersionsThoroughly fails.
junit.framework.ComparisonFailure: checkin N1 uncommitted. Version Name expected:<1.1.1> but was:<1.0.1>
at junit.framework.Assert.assertEquals(Assert.java:81)
at org.apache.jackrabbit.core.XATest.check(XATest.java:1140)
at org.apache.jackrabbit.core.XATest.testXAVersionsThoroughly(XATest.java:1080)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at org.apache.jackrabbit.core.XATest.runTest(XATest.java:96)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:393)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:474)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:342)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:194)
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Attachments: AbstractVersionManager.diff, DummyVersion.java
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-529) New versions added after a restore have
bad version name
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Tobias Bocanegra resolved JCR-529.
----------------------------------
Resolution: Fixed
Committed revision 488639.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Affects Versions: 1.0, 1.0.1, 1.1, 0.9, 1.1.1
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Fix For: 1.2
>
> Attachments: AbstractVersionManager.diff, DummyVersion.java, graph.txt
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JCR-529) New versions added after a restore have
bad version name
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-529?page=all ]
Jukka Zitting updated JCR-529:
------------------------------
Fix Version/s: 1.2
Affects Version/s: 1.1.1
1.1
1.0.1
1.0
0.9
Marking this for 1.2. Either the unit test or the code needs to be fixed before the release.
> New versions added after a restore have bad version name
> --------------------------------------------------------
>
> Key: JCR-529
> URL: http://issues.apache.org/jira/browse/JCR-529
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Affects Versions: 1.0, 1.0.1, 1.1, 0.9, 1.1.1
> Environment: Ubuntu Dapper
> Reporter: Paco Avila
> Assigned To: Tobias Bocanegra
> Fix For: 1.2
>
> Attachments: AbstractVersionManager.diff, DummyVersion.java, graph.txt
>
>
> I add several versions to a node (1.0, 1.1, 1.2, 1.3, 1.4). Perform a restore to version 1.2 and add more versions. After that VersionHistory is like this:
> - 1.0
> - 1.1
> - 1.2
> - 1.3
> - 1.4
> - 1.3.1
> - 1.3.2
> - 1.3.3
> - 1.3.4
> - 1.3.5
> New versions should be 1.2.x no 1.3.x, isn't it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira