ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Devienne" <>
Subject Re: Building from a list...
Date Tue, 25 Apr 2006 19:26:11 GMT
> [...] While Depot is not final, it does provide:
>  1. transitive dependency management
>  2. plugin build system deployment
>  3. automated path management (build, test and runtime)
>  4. source normalization
>  5. automated filtering, compilation, jar production, testing, etc.
>  6. build automation support via custom processors
>  7. build customization via ant

Sounds too good to be true Steve ;-)

Would I still be doing Java CM with Ant, I'd definitely check it out,
to replace all the custom stuff I used to do. But one aspect of what I
was doing I don't see in Maven or other dependency management tools is
the fact that the build artifacts I was depending upon were only
partly cross-platform. Half of it was native code with the JNI layer
on top. I was jumping thru a lot of hoops because of this. Each
component had to be continuously built on several platforms. When
downloading a dependency, getting all 4 platforms' binaries was too
big (Solaris .so are huge), so only the current platforms binaries had
to be downloaded. Solaris builds slower than Linux or Windows, so
platforms were not synced. This kind of complications...

How would depot deal with such a mixed native+Java code situation?
Just wondering. Maybe it's too specific a case, although I'm sure
there must be other people doing mixed Java / C/C++/Fortran
development out there.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message