"Ara Abrahamian" <[EMAIL PROTECTED]> wrote on 10/09/2002 08:27:20 AM:
> OK, it's working for me, but my workaround is quite ugly. A copy of my > previous message is attached. > > I fork a new instance of Ant in a separate jvm and let a pure Ant build > file do the xdoclet stuff for me. Here's my maven.xml: So the problem appears to be that xdoclet requires all ant properties to be serializable, is this correct? And a fork of the VM simply removes the 'bad' maven properties... [snip] > You may ask why don't you use <ant/> from the maven.xml file? Well, > because it doesn't work: > > java:compile: > ejbdoclet: > > [ERROR] BUILD FAILED > [ERROR] File...... D:\Projects\Petsoar\maven.xml > [ERROR] Element... ant > [ERROR] Line...... 13 > [ERROR] Column.... 81 > [ERROR] java.lang.NullPointerException > Total time: 25 seconds This needs fixing.... > But I can run run-xdoclet.xml from command line easily. Folks, Maven > seems to have some classloader problems, or maybe some trouble with path > refs. Can you post something small to the maven-user list that shows <ant/> failing from maven.xml in general, or is it only when used in conjunction with xdoclet? I'd love to have maven supporting xdoclet ASAP, and from what I can tell there are the following issues: a) xdoclet seems to create ant tasks under the covers, and hence from Maven's perspective, it needs to be in the root classloader as a dependency b) Maven puts non-serializable objects as 'Ant' properties. XDoclet serializes them and fails. c) Maven's <ant/> tag fails with an NPE Is this close? > Ara. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
