Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipselink-dev] Question about external dependencies.

Sometimes, explicit library definitions are neccessary. For example, in directory, I might have multiple versions of Oracle JDBC driver jars, I don't want all of them in the classpath. 


-----Original Message-----
From: Tom Ware 
Sent: November 21, 2008 1:40 PM
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Question about external dependencies.

Hi Eric,

   At the moment, I just define oracle.extensions.depend.dir.  I am not sure 
about the extension.lib.external or directories.

   One thing that is important to keep in mind is that JDBC jar location will 
need to be set both by people using Oracle and by people using other DBs.


Eric Gwin wrote:
> All,
>   Until recently I didn't use the "extension.lib.external" or 
> "" directories. I am curious why we need two.
>   I'd think that the oracle jdbc drivers and all other external 
> dependencies are named differently than each other.
>   Wouldn't a single directory be more efficient?
>   Also wouldn't defining a variable "extensions.depend.dir" make more 
> sense that a plethora of explicit library definitions?
>       jdbc=../extension.lib.external/jdbc.jar
>       junit=../extension.lib.external/junit.jar
>       ....
>   That way the minimum redefinition would be a single value 
> (extensions.depend.dir), unless someone chooses
>   to store them separately thus requiring a redefinition of all the 
> external dependency library values.
> Thanks
> -Eric
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
eclipselink-dev mailing list

Back to the top