[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-20 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799107#comment-17799107
 ] 

Julian Reschke edited comment on JCR-4979 at 12/20/23 5:16 PM:
---

trunk: (2.21.22) 
[ef12034a7|https://github.com/apache/jackrabbit/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]
2.20: 
[667115099|https://github.com/apache/jackrabbit/commit/667115099df7860ad1f6744bdbdad3f94ffe0a71]



was (Author: reschke):
trunk: (2.21.22) 
[ef12034a7|https://github.com/apache/jackrabbit/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]
2.20: 
[667115099|https://github.com/apache/jackrabbit/commit/667115099df7860ad1f6744bdbdad3f94ffe0a71]


> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.22, 2.20.14, 2.21.22
>
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-20 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798907#comment-17798907
 ] 

Julian Reschke edited comment on JCR-4979 at 12/20/23 11:15 AM:


trunk: (2.21.22) 
[ef12034a7|https://github.com/apache/jackrabbit/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]
2.20: 
[667115099|https://github.com/apache/jackrabbit/commit/667115099df7860ad1f6744bdbdad3f94ffe0a71]



was (Author: reschke):
trunk: (2.21.22) 
[ef12034a7|https://github.com/apache/jackrabbit/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>  Labels: candidate_jackrabbit_2_20
> Fix For: 2.22, 2.21.22
>
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-20 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798916#comment-17798916
 ] 

Julian Reschke edited comment on JCR-4979 at 12/20/23 11:07 AM:


[~kwin] - I'm not completely sure about where the scm tags need to live. Your 
change implies they are not needed in the parent pom. If this is the case, 
should we clean that up in Oak as well?

(FWIW: the Oak 1.22 parent pom still refers to svn, and in both trunk and 1.22, 
tags seem to be incorrect)


was (Author: reschke):
[~kwin] - I'm not completely sure about where the scm tags need to live. Your 
change implies they are not needed in the parent pom. If this is the case, 
should we clean that up in Oak as well?

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>  Labels: candidate_jackrabbit_2_20
> Fix For: 2.22, 2.21.22
>
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-20 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798907#comment-17798907
 ] 

Julian Reschke edited comment on JCR-4979 at 12/20/23 10:55 AM:


trunk: (2.21.22) 
[ef12034a7|https://github.com/apache/jackrabbit/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]


was (Author: reschke):
trunk: 
[ef12034a7|https://github.com/apache/jackrabbit/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>  Labels: candidate_jackrabbit_2_20
> Fix For: 2.22, 2.21.22
>
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-20 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798907#comment-17798907
 ] 

Julian Reschke edited comment on JCR-4979 at 12/20/23 10:53 AM:


trunk: 
[ef12034a7|https://github.com/apache/jackrabbit/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]


was (Author: reschke):
trunk: (2.21.22) 
[ef12034a7|https://github.com/apache/jackrabbit-oak/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>  Labels: candidate_jackrabbit_2_20
> Fix For: 2.22, 2.21.22
>
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-20 Thread Julian Reschke (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798907#comment-17798907
 ] 

Julian Reschke edited comment on JCR-4979 at 12/20/23 10:43 AM:


trunk: (2.21.22) 
[ef12034a7|https://github.com/apache/jackrabbit-oak/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]


was (Author: reschke):
trunk: 
[ef12034a7|https://github.com/apache/jackrabbit-oak/commit/ef12034a7c935a9bf2a61cc5411ac9d2726262ee]

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>  Labels: candidate_jackrabbit_2_20
> Fix For: 2.22, 2.21.22
>
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-12 Thread Konrad Windszus (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795468#comment-17795468
 ] 

Konrad Windszus edited comment on JCR-4979 at 12/12/23 10:30 AM:
-

Steps 1-3. have been done now by ASF INFRA.
Jenkins Jobs adjusted now (Step 6).
Applied slightly adjusted patch for site in 
https://svn.apache.org/viewvc?view=revision=1914542 (Step 4)


was (Author: kwin):
Steps 1-3. have been done now by ASF INFRA.
Jenkins Jobs adjusted now (Step 6).
Applied slightly adjusted patch for site in 
https://svn.apache.org/viewvc?view=revision=1914542 (Step 6)

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-11 Thread Konrad Windszus (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795494#comment-17795494
 ] 

Konrad Windszus edited comment on JCR-4979 at 12/11/23 7:29 PM:


[~reschke] Any idea why  [^JCR4979-v1-check-release.sh.patch] cannot 
successfully check the RC of 2.21.21.  That fails for me with 

{{[ERROR]   NOT OK: Tagged sources are different from those in the archive}}. 

{code}
[INFO]Unzipping jackrabbit-2.21.21-src.zip...
[INFO]Comparing sources...
[INFO] 
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/java/org/apache/jackrabbit/core:
 jmx
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/query:
 pdf
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/stats:
 util
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/resources/org/apache/jackrabbit/core/persistence:
 pool
diff -b -r 
./target/jackrabbit-2.21.21/scm/jackrabbit-2.21.21/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/util/XMLChar.java
 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/util/XMLChar.java
46c46
<  * @version $Id$
---
>  * @version $Id: XMLChar.java 1910276 2023-06-07 11:15:10Z reschke $
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-jcr-commons/src/test:
 resources
diff -b -r 
./target/jackrabbit-2.21.21/scm/jackrabbit-2.21.21/jackrabbit-jcr-tests/src/main/java/org/apache/jackrabbit/test/XMLChar.java
 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-jcr-tests/src/main/java/org/apache/jackrabbit/test/XMLChar.java
46c46
<  * @version $Id$
---
>  * @version $Id: XMLChar.java 1910276 2023-06-07 11:15:10Z reschke $
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit:
 jcr2spi
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-webdav/src/test/java/org/apache/jackrabbit/webdav:
 client
[ERROR]   NOT OK: Tagged sources are different from those in the archive
{code}

Update: Seems to be due to empty directories which do no longer exist with Git. 
Should not be a problem if the upcoming release is triggered from Git.


was (Author: kwin):
[~reschke] Any idea why  [^JCR4979-v1-check-release.sh.patch] cannot 
successfully check the RC of 2.21.21.  That fails for me with 

{{[ERROR]   NOT OK: Tagged sources are different from those in the archive}}. 

{code}
[INFO]Unzipping jackrabbit-2.21.21-src.zip...
[INFO]Comparing sources...
[INFO] 
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/java/org/apache/jackrabbit/core:
 jmx
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/query:
 pdf
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/stats:
 util
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-core/src/main/resources/org/apache/jackrabbit/core/persistence:
 pool
diff -b -r 
./target/jackrabbit-2.21.21/scm/jackrabbit-2.21.21/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/util/XMLChar.java
 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/util/XMLChar.java
46c46
<  * @version $Id$
---
>  * @version $Id: XMLChar.java 1910276 2023-06-07 11:15:10Z reschke $
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-jcr-commons/src/test:
 resources
diff -b -r 
./target/jackrabbit-2.21.21/scm/jackrabbit-2.21.21/jackrabbit-jcr-tests/src/main/java/org/apache/jackrabbit/test/XMLChar.java
 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-jcr-tests/src/main/java/org/apache/jackrabbit/test/XMLChar.java
46c46
<  * @version $Id$
---
>  * @version $Id: XMLChar.java 1910276 2023-06-07 11:15:10Z reschke $
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit:
 jcr2spi
Only in 
./target/jackrabbit-2.21.21/zip/jackrabbit-2.21.21/jackrabbit-webdav/src/test/java/org/apache/jackrabbit/webdav:
 client
[ERROR]   NOT OK: Tagged sources are different from those in the archive
{code}

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Attachments: JCR-4979-site-v1.patch, JCR4979-v1-check-release.sh.patch
>
>
> In order to foster contribution and ease switching between

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-11 Thread Konrad Windszus (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795468#comment-17795468
 ] 

Konrad Windszus edited comment on JCR-4979 at 12/11/23 6:54 PM:


Steps 1-3. have been done now by ASF INFRA.
Jenkins Jobs adjusted now (Step 6).
Applied slightly adjusted patch for site in 
https://svn.apache.org/viewvc?view=revision=1914542 (Step 6)


was (Author: kwin):
Steps 1-3. have been done now by ASF INFRA.
Jenkins Jobs adjusted now (Step 6)

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Attachments: JCR-4979-site-v1.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
>  # adjust pom.xml
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (JCR-4979) Migrate from Subversion to Git

2023-12-11 Thread Konrad Windszus (Jira) 


[ 
https://issues.apache.org/jira/browse/JCR-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795468#comment-17795468
 ] 

Konrad Windszus edited comment on JCR-4979 at 12/11/23 6:03 PM:


Steps 1-3. have been done now by ASF INFRA.
Jenkins Jobs adjusted now (Step 6)


was (Author: kwin):
Steps 1-3. have been done now by ASF INFRA.

> Migrate from Subversion to Git
> --
>
> Key: JCR-4979
> URL: https://issues.apache.org/jira/browse/JCR-4979
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Attachments: JCR-4979-site-v1.patch
>
>
> In order to foster contribution and ease switching between 
> branches/cherrypicking and in general to have a modern development workflow I 
> propose to migrate Jackrabbit (Classic) from SVN to Git similarly to what was 
> done in Oak (https://issues.apache.org/jira/browse/OAK-9440) and Jackrabbit 
> FileVault (https://issues.apache.org/jira/browse/JCRVLT-398).
> It would comprise of the following steps:
>  # migrate the SVN repository at 
> [https://svn.apache.org/repos/asf/jackrabbit/branches], 
> [https://svn.apache.org/repos/asf/jackrabbit/trunk] and 
> [https://svn.apache.org/repos/asf/jackrabbit/tags] to a Git repository named 
> "jackrabbit" (hosted at [https://gitbox.apache.org/repos/asf]) (tracked in 
> INFRA-25150)
>  # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit] to 
> mirror the new native Git repo (at Gitbox) (tracked in INFRA-25150)
>  # make the SVN repository at the folders outlined at 1. read only (tracked 
> in INFRA-25150)
>  # adjust documentation, see attached patch
>  ## 
>  ## 
>  # adjust check script
>  # adjust Jenkins Jobs 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk] and 
> [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/]
> VOTE thread in 
> [https://lists.apache.org/thread/2owqqjhk4wo9gk9jo7o02x73b2kfz7nj]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)