Getting a spell to work...
David Leangen
dleangen at canada.com
Fri Dec 3 06:07:22 EST 2004
> Creating an antlib will not solve your problem - but it is helpful if
> you planning on automating plugin loading (but we'll cover that another
> day).
k
> When you run with -v ....
> What does the stack trace say (the one originating in your task)?
> My hunch is it may be something to do with the dependencies declared in
> the index (or more specifically a dependency that is not required at
> build time but shows up at runtime).
Here is what's happening at runtime according to ant:
xdoclet.hibernate:
[transit] created impl classloader
[transit] (0) artifact:jar:commons-collections/commons-collections#3.1
[transit] (1) artifact:jar:commons-logging/commons-logging#1.0.4
bla bla bla
[transit] (13) artifact:jar:xdoclet/xdoclet-hibernate-module#1.2.2
bla bla bla
[ant] Exiting K:\pubmed.jp\pubmed\mesh\.\impl\build.xml.
The jar (xdoclet-hibernate-module#1.2.2) does indeed appear to be loaded.
This is the JAR that containes the class that ant claims to be missing.
Regards,
Dave
More information about the support-dpml
mailing list