When you say xjc do you mean:
http://www.ibiblio.org/maven2/javax/xml/jaxb-xjc/1.0.5/jaxb-
xjc-1.0.5.pom
because if so there are no dependencies declared there. What you see
in my
dependency list is home made in my own repository by trial and error.
I think I've just temporarily been experiencing what it must have
been like
to devlop in maven 1.
On 4 Oct 2005, at 15:03, Brett Porter wrote:
I'm pretty sure xjc depends on all of these. If that were in the xjc
pom, you'd only need to depend on xjc.
Basically, you should only need to depend on what you use if the
libraries have a properly constructed pom.
Likewise, if you construct a pom with all these deps, you can depend
on that to get them all.
- Brett
On 10/4/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
I'm currently trying to knock up a plugin that invokes xjc but I'm
concerned my approach to handling dependencies isn't the best one. To
illustrate my dependency section looks like this so far:
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxb-api</artifactId>
<version>1.0.5</version>
</dependency>
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxb-impl</artifactId>
<version>1.0.5</version>
</dependency>
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxb-libs</artifactId>
<version>1.0.5</version>
</dependency>
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxb-xjc</artifactId>
<version>1.0.5</version>
</dependency>
<dependency>
<groupId>javax.xml</groupId>
<artifactId>namespace</artifactId>
<version>1.0.5</version>
</dependency>
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jax-qname</artifactId>
<version>1.0.5</version>
</dependency>
and it's still growing every time I bump into a NoClassDefFoundError!
Basically because all these little jar files have licensing issues,
I'm having to install them locally by calling m2 install:install-file
multiple times. But even if this weren't the case I feel there should
be some way of dealing with all the java web service files as one
entity.
Actually to answer my own question maybe the answer is to provide a
parent pom that has references to all the little critter poms and
just depend on that. Perhaps somebody could verify this approach or
suggest an alternative.
Thanks
- AW
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
