You could make your own "bundle" pom by creating a new pom with
packaging "pom" and specify the dependencies/libraries used by JWSDP
etc.

So you would make your own JWSDP v 1.4, 1.6, 2.0 etc poms with the
proper dependencies declared and then deploy those poms to your
internal corporate repo, and other developers in your company could
depend on those poms to pull in all the proper libraries you need etc.

Wayne

On 2/19/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
bundles are usually a bad idea because conflict with dependencies
needed by other projects

jaxp 1.4 is in
http://repo1.maven.org/maven2/javax/xml/parsers/jaxp-api/1.4/
and Sun's reference implementation in
http://repo1.maven.org/maven2/com/sun/xml/parsers/jaxp-ri/1.4/

On 2/19/07, Erik Ruisma <[EMAIL PROTECTED]> wrote:
> Hello,
>
> what does Maven2 recommend when you have projects that depend on software
> bundles à la JAXP, JWSDP, ... or others?
> In general these software bundles are a collection of other libraries (eg
> JAXP 1.3 contains version X of xercesImpl, version Y of xalan,..). So how do
> you define a dependency to those packages, or how do you add them to your
> internal repository?
>
> I don't seem to find these packages (I'm especially looking for JAXP 1.3 at
> this moment) on the public repositories. I assume there are a lot of people
> out there who have encountered these questions before.
> Our internal repository already contains some of the jaxp dependencies.
> So I was thinking about adding a POM for jaxp version 1.3 that uses that
> links to the correct versions of the other libraries.
> I assume that this should do the job correctly?
>
> Any feedback would be greatly appreciated.
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

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

Reply via email to