I've managed to get it to compile without errors as a new subproject; 
many thanks! Distributing the jars in a local maven repository is a bit 
more than I want to deal with right now.

Mark Diggory wrote:

> A slight tangent... does OIS consider these jars to be private  
> resources, or do they consider at all sharing them with a larger  
> community at Harvard?  Maybe theres an option for distributing them  in 
> a local maven repository of their own?
> 
>> We have the jars set up in a local repository (Unix directory), with
>> some simple version management. The repository isn't mounted on the
>> machine we're using for DSpace work and isn't available by HTTP, so
>> Maven's proclivity for fetching resources from repositories might be
>> difficult to satisfy.
> 
> 
> I doubt it'd be in the same format anyways. Are you working on  
> deploying just one server, or do you expect this to be What I would  
> recommend
> 
> so, if you wanted to build against these dependencies "right now" yo  
> would do:
> 
> mvn install:install-file -Dfile=location/of/jdbc.jar - 
> DgroupId=edu.harvard.hul.ois -DartifactId=ois-jdbc -Dversion=X.X.X  - 
> Dpackaging=jar
> mvn install:install-file -Dfile=location/of/nrs.jar   - 
> DgroupId=edu.harvard.hul.ois -DartifactId=ois-nrs   -Dversion=X.X.X  - 
> Dpackaging=jar
> 
> where X.X.X is the version you wish to be using (you can make that up  
> if you like or use whatever is already there. then in you pom...  first 
> pass I'd say just do it in dspace-api/pom.xml (later we may  create 
> another maven project if it benefits you).
> 
> <dependency>
>     <artifactId>ois-jdbc</artifactId>
>     <groupId>edu.harvard.hul.ois</groupId>
>     <version>X.X.X</version>
> </dependency>
> 
> <dependency>
>     <artifactId>ois-nrs</artifactId>
>     <groupId>edu.harvard.hul.ois</groupId>
>     <version>X.X.X</version>
> </dependency>
> 
> You'll need to do this again on any server (or user) your running  
> another maven repository in (thus the benefit of deploying instead to  a 
> locally maintained maven repository) which would be added to as a  
> <repository> in the pom and thus the jars could be gotten from on any  
> account/server you were building on.  If you reach this point, it  
> definitely benefits you to consider having a separate maven project  for 
> the nrs HandleManager adapter that preserves this customization  
> independent of the dspace codebase.


-- 
Gary McGath
Digital Library Software Engineer
Harvard University Libraries, Office for Information Systems

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to