Re: [Xdoclet-user] beta3 build

[J C. C. <jcc...@jc...>]

>
>
>Checkout module xdoclet-all, copy junit.jar into
>lib directory of ant. build off directory xdoclet
>under xdoclet-all.
>
>Some 20 minutes later you will have xdoclet compiled
>:)
>  
>
That *almost* worked. I got most of the way through by also:

 - copying xalan.jar over to ant's lib. I suppose that is because Java 
1.4 includes an XSLT parser, and I needed Xalan since I'm still on 1.3. 
(Or am I all wet?)

-  doing a simple source change. My compiler didn't buy the getStrings 
method (lines 140-1) of
xdoclet-all/xdoclet/samples/src/java/test/jmx/JBossXMLExample.java

I fixed it by using
      String[] en = {"one", "two", "three"};
      String[] es = {"uno", "dos", "tres"};
      String[][] retval = {en, es};
      return retval;
instead.

- installing Maven. But that wasn't hard.

But, in task 'dist' after is says "Packaging XDoclet" and does all sorts 
of Maven stuff, it says

     [exec] Setting project: XDoclet
     [exec] Received: [301] for 
http://jakarta.apache.org/ant/manual/CoreTypes/fileset.html

Which URL I can plainly see in my browser. So I don't know what's with 
that.  But it does seem to have generated all the necessary jars, in 
target/lib. These are all named xdoclet*-1.2b3-dev.jar.

This is like I could get in the beta builds from SourceForge. However, 
in the 1.1.2 build the only thing in lib/ is a single xdoclet.jar, which 
is what my buildfile looks for (and puts in its xdoclet.path.)

Is there a way to get everything in the one jar like in 1.1.2, or do I 
need to put all those jars in the classpath somehow?

          --jcc