jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary D. Gregory (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-2266) Skip deployment of jackrabbit-standalone
Date Fri, 10 Feb 2012 18:52:59 GMT

    [ https://issues.apache.org/jira/browse/JCR-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205627#comment-13205627

Gary D. Gregory commented on JCR-2266:

Hello all,

I would like to use jackrabbit-standalone from Maven for testing our upcoming Apache Commons
VFS 2.1. 

If you have a better idea on how to do the following, please advise.

I want to run our VFS WebDAV unit tests using Jackrabbit as a server embedded in the test.
In previous versions, a developer had to set up a WebDAV server manually and run the one test.

What I started to do is use jackrabbit-standalone 1.6.5 but it does not have the JcrUtils
class which came in with Jackrabbit 2.0.

My current code:

# Create a temp dir
# Create a TransientRepository point to the temp dir
# Use JcrUtils to import a directory its subdirectories full of test files (I cannot do this
# Shutdown the TransientRepository
# Start Jackrabbit with org.apache.jackrabbit.standalone.Main:
org.apache.jackrabbit.standalone.Main.main(new String[] { "--port", Integer.toString(SocketPort),
"--repo", repoDirectory.toString() });
# The tests run
I would like to use the latest jackrabbit but I am stuck without the standalone jar.

> Skip deployment of jackrabbit-standalone
> ----------------------------------------
>                 Key: JCR-2266
>                 URL: https://issues.apache.org/jira/browse/JCR-2266
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-standalone
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Trivial
>             Fix For: 2.0-alpha11
> The jackrabbit-standalone jar currently can't be deployed to the repository.apache.org
server probably because of its size. I'm not sure if there are any good use cases where you'd
want to use the standalone jar as a Maven dependency, so having it on Maven central doesn't
seem that important. I'd like to make this explicit by configuring the deploy plugin to skip
deploying the standalone jar.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message