[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781956#action_12781956 ] Thomas Mueller commented on JCR-2389: - You are right, TransientRepository needs it, so let's keep the Derby dependency. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781930#action_12781930 ] Sébastien Launay commented on JCR-2389: --- > I'd very much prefer httpclient 4.0 to be used. I just created JCR-2406 feel free to provide a patch tested against multiple WebDAV clients. > About Derby. I agree that this dependency is needed only at runtime and only if it is used in a PersistenceManager/DataStore. But removing it or rendering it optional implies a non working use of new TransientRepository() with jackrabbit-core (and also by transitivity jackrabbit-webapp/standalone). Maybe the solution is to remove the default repository.xml (only for testing purpose) and force the user to specify one. But this leads to a more difficult first approach of Jackrabbit (first hops). > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781909#action_12781909 ] Thomas Mueller commented on JCR-2389: - No objections for the patch. About Derby: Derby is not required to compile Jackrabbit. It is required when running the tests (that's why I wrote test). And it is used as the default persistence manager, so jackrabbit-standalone (?) should include Derby. However, Derby is not required at runtime if you configure a different persistence manager. In the long term, I believe the Derby dependency within jackrabbit-core should be test and not anything else. Short term, it doesn't really matter. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781903#action_12781903 ] Sébastien Launay commented on JCR-2389: --- After reading the source code, I indeed found that derby is required by the default repository.xml configuration (new TransientRepository()). Therefore this dependency cannot be optional (needed both for test and runtime) and the only solution is to explicitly exclude derby when depending jackrabbit-core. Any objections/concerns with the latest patch? > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781902#action_12781902 ] Lutz Horn commented on JCR-2389: I'd very much prefer httpclient 4.0 to be used. For development of new applications it makes no sense to use 3.x. After all: "Commons HttpClient 3.x codeline is nearing the end of life. All users of Commons HttpClient 3.x are strongly encouraged to upgrade to HttpClient 4.0." > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781413#action_12781413 ] Thomas Mueller commented on JCR-2389: - As far as I understand Maven (and I'm definitely not an expert), "optional dependencies" mean dependencies that are needed to compile the project, but not necessarily needed at runtime. You don't need any JDBC driver to compile Jackrabbit core (not even Derby). You only need Derby (the default persistence manager) when running the tests. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779949#action_12779949 ] Attila Király commented on JCR-2389: These are typical optional dependencies. Maven has support for it [1]. Defining a dependency as optional in jackrabbit would mean that it will not be pulled unless it is explicitely specified by the jackrabbit user project. [1]: http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779495#action_12779495 ] Thomas Mueller commented on JCR-2389: - Derby is the default persistence manager, so it is required when using Jackrabbit out-of-the-box. I'm not completely sure, but I think for Jackrabbit core the Derby dependency could be test. H2 (and MySQL, PostgreSQL,... any database or JDBC driver) are not needed at all (not used for testing and not used as the default database). > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch, > JCR-2389-update-dependencies-2009-11-18_2.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779466#action_12779466 ] Thomas Mueller commented on JCR-2389: - > the H2 version that was tested with H2PersistenceManager You can use any version of H2 :-) The features required by Jackrabbit (by the H2PersistenceManager) are very basic. I'm not aware of a combination that doesn't work. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779423#action_12779423 ] Attila Király commented on JCR-2389: > It is not required to add H2 as a dependency. Specially, the version is not > needed. > If your application uses H2, you can still add it there. Okay. Could you add a note somewhere in the documentation or on the site about the H2 version that was tested with H2PersistenceManager? Currently this information is not available. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779410#action_12779410 ] Thomas Mueller commented on JCR-2389: - > H2 ... needed by the o.a.j.core.persistence.bundle.H2PersistenceManager. It is not required to add H2 as a dependency. Specially, the version is not needed. If your application uses H2, you can still add it there. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779394#action_12779394 ] Jukka Zitting commented on JCR-2389: httpclient: Agreed with Angela, the 3.0 -> 4.0 upgrade is a non-trivial change that should be handled as a separate task. beanutils: AFAIK we only use BeanMap in two places anymore. Instead of the new dependency, I'd rather use a copy of the BeanMap class or refactor the reference away. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779390#action_12779390 ] angela commented on JCR-2389: - > I believe we can also upgrade from commons-httpclient 3.0 to HttpClient 4.0 > on jackrabbit-spi2dav with a few modifications. -1 for changing this dependency. i don't have any time left to run after problems that might be introduced by 'few modifications' or changed behavior or unknown bugs of the httpclient 4.0... and i'm pretty confident that this would cause problems here and there. after all HttpClient 4.0 was just released a couple of month ago (August 17, 2009). > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779386#action_12779386 ] Attila Király commented on JCR-2389: Nice to see this progressing! I would also like to add one that I forgot last time: H2 db. It seems it is not listed as dependency in the poms but it is needed by the o.a.j.core.persistence.bundle.H2PersistenceManager. It would be nice to add it to the dependencies (maybe marked as optional) with the most recent stable version (currently 1.2.23). This also needs some expert checking that the upgrade is safe with the PersistenceManager. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779381#action_12779381 ] Thomas Mueller commented on JCR-2389: - Upgrading Derby should be no problem. Jackrabbit doesn't need any special features. > Update dependency versions for commons-collections, slf4j and derby > --- > > Key: JCR-2389 > URL: https://issues.apache.org/jira/browse/JCR-2389 > Project: Jackrabbit Content Repository > Issue Type: Task >Affects Versions: 2.0-beta1 >Reporter: Attila Király >Priority: Minor > Attachments: JCR-2389-update-dependencies-2009-11-18.patch > > > Some of the dependencies used by the 2.0-beta1 could be upgraded: > commons-collections from 3.1 to 3.2.1 > slf4j from 1.5.3 to 1.5.8 > derby from 10.2.1.6 to 10.5.3.0 > Not sure about derby but the other two seems to be just drop in replacements > for their older verisons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
