You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Gary D. Gregory (Created) (JIRA)" <ji...@apache.org> on 2012/04/01 16:24:28 UTC
[jira] [Created] (JCR-3284) Provide jackrabbit standalone jar
Provide jackrabbit standalone jar
---------------------------------
Key: JCR-3284
URL: https://issues.apache.org/jira/browse/JCR-3284
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-standalone
Reporter: Gary D. Gregory
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
[jira] [Commented] (JCR-3284) Provide jackrabbit standalone jar
Posted by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243786#comment-13243786 ]
Jukka Zitting commented on JCR-3284:
------------------------------------
It's fairly straightforward to start an embedded Jackrabbit repository and expose it over WebDAV using an embedded Jetty or Tomcat instance. Starting the full standalone jar is IMHO a bit overkill for a test case like that.
See http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-jcr-server/src/test/java/org/apache/jackrabbit/webdav/simple/LitmusTest.java for some example code on how to do this.
> Provide jackrabbit standalone jar
> ---------------------------------
>
> Key: JCR-3284
> URL: https://issues.apache.org/jira/browse/JCR-3284
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-standalone
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary D. Gregory
> Assignee: Jukka Zitting
> Fix For: 2.0-alpha11
>
>
> 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 ATM.)
> # Shutdown the TransientRepository
> # Start Jackrabbit with org.apache.jackrabbit.standalone.Main:
> {noformat}
> org.apache.jackrabbit.standalone.Main.main(new String[] { "--port", Integer.toString(SocketPort), "--repo", repoDirectory.toString() });
> {noformat}
> # The tests run
> I would like to use the latest jackrabbit but I am stuck without the standalone jar.
> Thoughts?
--
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
[jira] [Updated] (JCR-3284) Provide jackrabbit standalone jar
Posted by "Gary D. Gregory (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory updated JCR-3284:
---------------------------------
Priority: Major (was: Trivial)
Description:
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 ATM.)
# Shutdown the TransientRepository
# Start Jackrabbit with org.apache.jackrabbit.standalone.Main:
{noformat}
org.apache.jackrabbit.standalone.Main.main(new String[] { "--port", Integer.toString(SocketPort), "--repo", repoDirectory.toString() });
{noformat}
# The tests run
I would like to use the latest jackrabbit but I am stuck without the standalone jar.
Thoughts?
was: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.
Environment:
Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Maven home: C:\Java\apache-maven-3.0.4\bin\..
Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_31\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Provide jackrabbit standalone jar
> ---------------------------------
>
> Key: JCR-3284
> URL: https://issues.apache.org/jira/browse/JCR-3284
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-standalone
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary D. Gregory
> Assignee: Jukka Zitting
> Fix For: 2.0-alpha11
>
>
> 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 ATM.)
> # Shutdown the TransientRepository
> # Start Jackrabbit with org.apache.jackrabbit.standalone.Main:
> {noformat}
> org.apache.jackrabbit.standalone.Main.main(new String[] { "--port", Integer.toString(SocketPort), "--repo", repoDirectory.toString() });
> {noformat}
> # The tests run
> I would like to use the latest jackrabbit but I am stuck without the standalone jar.
> Thoughts?
--
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