I changed the XDoclet config in libraries.ent to default to
thirdparty/xdoclet-xdoclet/lib, which allows other projects to continue
to function. If you want to use the bits from jboss/xdoclet define
xdoclet.xdoclet.lib in your build/local.properties.
I still have not figured out how this ever worked... nothing ever
seemed to get built in my jboss/xdoclet module and it is not hooked up
to the project build anywhere.
I have tested that jboss-head will build with this default
configuration and now so does the buildmagic project.
We really need a better mechanism to handle these dependencies, for
both tools and compile requirements.
I am starting to think that buildmagic should be renamed to
buildheadache... :-(
Also, I removed the nonsense about single-module fluff... the exact
same thing can be done by simply using -Dmodules=some-module (not
-Dmodule mind ya, that won't do what you expect at all).
--jason
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
