Re: [VOTE] Release Apache Jackrabbit Filevault 3.2.8
Here's my > [X] +1 Release this package as Apache Jackrabbit Filevault 3.2.8 With: [INFO] [INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T04:39:06+09:00) [INFO] OS name: "mac os x", version: "10.14.3", arch: "x86_64", family: "mac" [INFO] Java version: 1.8.0_152, vendor: Oracle Corporation [INFO] MAVEN_OPTS: [INFO] [INFO] ALL CHECKS OK [INFO] Regards, Toby
[VOTE] Release Apache Jackrabbit Filevault 3.2.8
A candidate for the Jackrabbit Filevault 3.2.8 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.2.8/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/commons/filevault/tags/jackrabbit-filevault-3.2.8/ The SHA1 checksum of the archive is 7720d7882f5fb51758449a6bd7f3900fc8025e9b. The command for running automated checks against this release candidate is: $ sh check-release.sh filevault 3.2.8 7720d7882f5fb51758449a6bd7f3900fc8025e9b A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachejackrabbit-1409/ Please vote on releasing this package as Apache Jackrabbit Filevault 3.2.8. The vote is open for a minimum of 72 hours during business days and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. The vote fails if not enough votes are cast after 1 week (5 business days). [ ] +1 Release this package as Apache Jackrabbit Filevault 3.2.8 [ ] -1 Do not release this package because... Thanks. Regards, Toby
[jira] [Resolved] (JCR-4401) Split jackrabbit-standalone to jackrabbit-standalone-components and the rest
[ https://issues.apache.org/jira/browse/JCR-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko resolved JCR-4401. - Resolution: Fixed > Split jackrabbit-standalone to jackrabbit-standalone-components and the rest > > > Key: JCR-4401 > URL: https://issues.apache.org/jira/browse/JCR-4401 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-standalone >Affects Versions: 2.19.0 >Reporter: Woonsan Ko >Assignee: Woonsan Ko >Priority: Major > Fix For: 2.20, 2.19.2 > > > I'd like to help fix VFS-686 [1] by upgrading JR dependency from 1.6.5 to the > latest of 2.x for the WebDAV vfs provider. The fix will allow to use WebDAV > DataStore backend again. (Since JR upgraded httpclient to v4.x, WebDAV > backend has been broken.) > One problem is that the test case for WebDAV vfs provider counts on > jackrabbit-standalone dependency--to start an extended JR Main for > testing--which has been unavailable in maven repos for long time. It's > understandable not to deploy the module as it's too big. > At the same time, it would be awkward if VFS should contain all the necessary > JR dependencies as jackrabbit-standalone does. > I think it would be nice if we split the module, by moving all the Java > classes and resources with most dependencies, except of jackrabbit-webapp, to > a new maven module (e.g, "jackrabbit-standalone-components") and having > dependency on this new module and webapp module in jackrabbit-standalone > bundle module. This will let VFS keep the JR dependencies simple and easy. > \[1\] https://issues.apache.org/jira/browse/VFS-686 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4401) Split jackrabbit-standalone to jackrabbit-standalone-components and the rest
[ https://issues.apache.org/jira/browse/JCR-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko updated JCR-4401: Fix Version/s: 2.20 > Split jackrabbit-standalone to jackrabbit-standalone-components and the rest > > > Key: JCR-4401 > URL: https://issues.apache.org/jira/browse/JCR-4401 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-standalone >Affects Versions: 2.19.0 >Reporter: Woonsan Ko >Assignee: Woonsan Ko >Priority: Major > Fix For: 2.20, 2.19.2 > > > I'd like to help fix VFS-686 [1] by upgrading JR dependency from 1.6.5 to the > latest of 2.x for the WebDAV vfs provider. The fix will allow to use WebDAV > DataStore backend again. (Since JR upgraded httpclient to v4.x, WebDAV > backend has been broken.) > One problem is that the test case for WebDAV vfs provider counts on > jackrabbit-standalone dependency--to start an extended JR Main for > testing--which has been unavailable in maven repos for long time. It's > understandable not to deploy the module as it's too big. > At the same time, it would be awkward if VFS should contain all the necessary > JR dependencies as jackrabbit-standalone does. > I think it would be nice if we split the module, by moving all the Java > classes and resources with most dependencies, except of jackrabbit-webapp, to > a new maven module (e.g, "jackrabbit-standalone-components") and having > dependency on this new module and webapp module in jackrabbit-standalone > bundle module. This will let VFS keep the JR dependencies simple and easy. > \[1\] https://issues.apache.org/jira/browse/VFS-686 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4401) Split jackrabbit-standalone to jackrabbit-standalone-components and the rest
[ https://issues.apache.org/jira/browse/JCR-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko updated JCR-4401: Fix Version/s: 2.19.2 > Split jackrabbit-standalone to jackrabbit-standalone-components and the rest > > > Key: JCR-4401 > URL: https://issues.apache.org/jira/browse/JCR-4401 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-standalone >Affects Versions: 2.19.0 >Reporter: Woonsan Ko >Assignee: Woonsan Ko >Priority: Major > Fix For: 2.19.2 > > > I'd like to help fix VFS-686 [1] by upgrading JR dependency from 1.6.5 to the > latest of 2.x for the WebDAV vfs provider. The fix will allow to use WebDAV > DataStore backend again. (Since JR upgraded httpclient to v4.x, WebDAV > backend has been broken.) > One problem is that the test case for WebDAV vfs provider counts on > jackrabbit-standalone dependency--to start an extended JR Main for > testing--which has been unavailable in maven repos for long time. It's > understandable not to deploy the module as it's too big. > At the same time, it would be awkward if VFS should contain all the necessary > JR dependencies as jackrabbit-standalone does. > I think it would be nice if we split the module, by moving all the Java > classes and resources with most dependencies, except of jackrabbit-webapp, to > a new maven module (e.g, "jackrabbit-standalone-components") and having > dependency on this new module and webapp module in jackrabbit-standalone > bundle module. This will let VFS keep the JR dependencies simple and easy. > \[1\] https://issues.apache.org/jira/browse/VFS-686 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (JCR-4401) Split jackrabbit-standalone to jackrabbit-standalone-components and the rest
[
https://issues.apache.org/jira/browse/JCR-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794603#comment-16794603
]
Woonsan Ko edited comment on JCR-4401 at 3/17/19 10:20 PM:
---
Merged PR: https://github.com/apache/jackrabbit/pull/82
-
Added a new submodule, jackrabbit-standalone-components, which contains most of
the dependencies and classes and resource, while jackrabbit-standalone includes
all of those transitively through jackrabbit-standalone-components.
I've used this, jackrabbit-standalone-components in the new webdav4 provider of
Commons VFS. Everything seems working fine now. I made a pull request there for
review purpose for now: https://github.com/apache/commons-vfs/pull/52
By the way, I've made two changes in the standalone Main class for the cases
where unit tests starts a Jackrabbit standalone {{Main}}:
- Make {{#run}} public, so unit tests can easily instantiate and start it.
- Add #shutdown as public, so unit tests can make a graceful shutdown before
JVM shutdown hook takes the place.
was (Author: woon_san):
Merged PR: https://github.com/apache/jackrabbit/pull/82
-
Added a new submodule, jackrabbit-standalone-components, which contains most of
the dependencies and classes and resource, while jackrabbit-standalone includes
all of those transitively through jackrabbit-standalone-components.
I've used this, jackrabbit-standalone-components in the new webdav4 provider of
Commons VFS. Everything seems working fine now. I made a pull request there for
review purpose for now: apache/commons-vfs#52
By the way, I've made two changes in the standalone Main class for the cases
where unit tests starts a Jackrabbit standalone {{Main}}:
- Make {{#run}} public, so unit tests can easily instantiate and start it.
- Add #shutdown as public, so unit tests can make a graceful shutdown before
JVM shutdown hook takes the place.
> Split jackrabbit-standalone to jackrabbit-standalone-components and the rest
>
>
> Key: JCR-4401
> URL: https://issues.apache.org/jira/browse/JCR-4401
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-standalone
>Affects Versions: 2.19.0
>Reporter: Woonsan Ko
>Assignee: Woonsan Ko
>Priority: Major
>
> I'd like to help fix VFS-686 [1] by upgrading JR dependency from 1.6.5 to the
> latest of 2.x for the WebDAV vfs provider. The fix will allow to use WebDAV
> DataStore backend again. (Since JR upgraded httpclient to v4.x, WebDAV
> backend has been broken.)
> One problem is that the test case for WebDAV vfs provider counts on
> jackrabbit-standalone dependency--to start an extended JR Main for
> testing--which has been unavailable in maven repos for long time. It's
> understandable not to deploy the module as it's too big.
> At the same time, it would be awkward if VFS should contain all the necessary
> JR dependencies as jackrabbit-standalone does.
> I think it would be nice if we split the module, by moving all the Java
> classes and resources with most dependencies, except of jackrabbit-webapp, to
> a new maven module (e.g, "jackrabbit-standalone-components") and having
> dependency on this new module and webapp module in jackrabbit-standalone
> bundle module. This will let VFS keep the JR dependencies simple and easy.
> \[1\] https://issues.apache.org/jira/browse/VFS-686
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JCR-4401) Split jackrabbit-standalone to jackrabbit-standalone-components and the rest
[
https://issues.apache.org/jira/browse/JCR-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794603#comment-16794603
]
Woonsan Ko commented on JCR-4401:
-
Merged PR: https://github.com/apache/jackrabbit/pull/82
-
Added a new submodule, jackrabbit-standalone-components, which contains most of
the dependencies and classes and resource, while jackrabbit-standalone includes
all of those transitively through jackrabbit-standalone-components.
I've used this, jackrabbit-standalone-components in the new webdav4 provider of
Commons VFS. Everything seems working fine now. I made a pull request there for
review purpose for now: apache/commons-vfs#52
By the way, I've made two changes in the standalone Main class for the cases
where unit tests starts a Jackrabbit standalone {{Main}}:
- Make {{#run}} public, so unit tests can easily instantiate and start it.
- Add #shutdown as public, so unit tests can make a graceful shutdown before
JVM shutdown hook takes the place.
> Split jackrabbit-standalone to jackrabbit-standalone-components and the rest
>
>
> Key: JCR-4401
> URL: https://issues.apache.org/jira/browse/JCR-4401
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-standalone
>Affects Versions: 2.19.0
>Reporter: Woonsan Ko
>Assignee: Woonsan Ko
>Priority: Major
>
> I'd like to help fix VFS-686 [1] by upgrading JR dependency from 1.6.5 to the
> latest of 2.x for the WebDAV vfs provider. The fix will allow to use WebDAV
> DataStore backend again. (Since JR upgraded httpclient to v4.x, WebDAV
> backend has been broken.)
> One problem is that the test case for WebDAV vfs provider counts on
> jackrabbit-standalone dependency--to start an extended JR Main for
> testing--which has been unavailable in maven repos for long time. It's
> understandable not to deploy the module as it's too big.
> At the same time, it would be awkward if VFS should contain all the necessary
> JR dependencies as jackrabbit-standalone does.
> I think it would be nice if we split the module, by moving all the Java
> classes and resources with most dependencies, except of jackrabbit-webapp, to
> a new maven module (e.g, "jackrabbit-standalone-components") and having
> dependency on this new module and webapp module in jackrabbit-standalone
> bundle module. This will let VFS keep the JR dependencies simple and easy.
> \[1\] https://issues.apache.org/jira/browse/VFS-686
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
