[ 
https://issues.apache.org/jira/browse/AIRAVATA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262421#comment-13262421
 ] 

Ate Douma commented on AIRAVATA-397:
------------------------------------

This has been asked for and dealt with before, see: JCR-2226 and JCR-3284.
Seems like a artifact sizing problem (too big for repository.apache.org).
And the Jackrabbit standalone jar indeed is big: 35 Mb, accounting for almost 
50% of the size of the airavata binary distribution...
You might want to consider to instead using all the separate jackrabbit jars 
also/already packaged under the airavata standalone-server/lib folder.
After all, the Jackrabbit standalone package is mostly a cli wrapper with an 
embedded Jetty. 
                
> Work with Jackrabbit PMC to get the standalone jar in maven central
> -------------------------------------------------------------------
>
>                 Key: AIRAVATA-397
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-397
>             Project: Airavata
>          Issue Type: Sub-task
>    Affects Versions: 0.4-INCUBATING
>            Reporter: Suresh Marru
>            Assignee: Heshan Suriyaarachchi
>
> Jackrabbit stand alone jar is not available from maven central. Only 
> available from - 
> http://maven.ow2.org/maven2/org/apache/jackrabbit/jackrabbit-standalone/2.2.7/.
>  Have to work with jackrabbit PMC to find out the correct maven repo for 
> these jars and remove the dependency for the following repo:
>         <repository>
>             <id>OW2</id>
>             <name>OW2 Repository</name>
>             <url>http://maven.ow2.org/maven2</url>
>         </repository> 

--
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

        

Reply via email to