expressing dependencies of third-party jars in internal repository

[Doug Douglass]

Specifically, I'm in the process of placing all the appropriate jars 
from Suns Web Services Dev Pack into our internal maven repo. But how 
should dependencies for these jars be expressed?

For example, the JWSDP 1.5 contains jaxp-api.jar (1.2.6_01), which 
depends on SAX 2.0, which in turn is available via the ibiblio maven 
repo (sax-2.0.1.jar). Even if I chose to place sax-2.0.jar into our 
internal maven repo, is there a way to "know" that jaxp-api-1.2.6_01.jar 
is dependent upon sax-2.0.jar (or sax-2.0.1.jar)? Should I be creating a 
POM for JAXP, then perhaps use a tool like Deputy (search the archives) 
to discover the dependecies.

Just looking for some advice on best practices...
TIA,
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]