Re: Add additional jars to maven.dependency.classpath?

[Mark McBride]

This is true, there's actually only a handful of jars that are actually 
compiled against. The only concern I have with only entering those handful 
of jars as dependencies is that somehow a developer could change the 
version of the jdbc driver not knowing that it has really already been 
dictated by oc4j's manifest.mf. I'll admit that this is being a little 
picky, but I would like to get our configuration exactly the same as our 
target deployment environment. This will be easier when we can group 
dependencies together so that there's more meaning. But for now I'm reading 
that I should probably just enter those dependencies in the project.xml.

Thank you!

-Mark

At 09:09 AM 10/14/2003 +1000, you wrote:
Surely you don't depend on all 20 jars?
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/
Mark McBride <[EMAIL PROTECTED]> wrote on 14/10/2003 04:23:28 AM:

> Can I add additional jars to the maven.dependency.classpath property
that
> have not been defined as a dependency? I have a project which is using
> OC4J/Orion and the main jar for this server has a manifest which lists
out
> 20+ jars for it's classpath. Instead of declaring all 20+ jars in my
> project.xml I'd like to add to the classpath (in the pregoal for
> java:compile) the jars listed in the manifest.mf.
>
> Thanks in advance!
>
> -Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Mark T. McBride
Computer Scientist
Lawrence Livermore National Laboratory
http://www.llnl.gov
Office: (925) 423-1627
Fax: (925) 423-3140