ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephane Bailliez <>
Subject Ant Compilation problems
Date Sat, 15 Dec 2001 12:43:31 GMT

I'm not able to fully compile Ant due to problems (I still have not managed
to solve due to lack of time or more probably because I put it in my todo
list with a -167 priority ) with the VAJ stuff.

The VAJ stubs that Conor kindly sent me sometime ago to compile Ant are out
of date and w/o having the Javadocs for the API it will be hard to guess
exceptions that can be thrown in a specific method or not, so doing this
could have more chance to result in a verifyerror or such unless I'm wrong,
so that means at this time unless one of us is able to get all APIs, we
cannot do a release.

That demonstrates 3 things.

1) No one is fully compiling Ant for quite some time now since we kindly
avoid to compile it when we do not have the stubs :)

2) of course GUMP does not for the same reason and thus we are not able to
distribute valid optional jar and the core for nightly builds.

3) Unless someone is able to get all APIs we are not able to do a release. 

So my question is: is there a valid solution to solve the particular problem
of commercial APIs and make it available via stubs in CVS or do something so
that we can make sure that Ant always compile ?

I'm not sure this is legal to have stubs in the form of 'com.thecompany' in
CVS (either sources or binaries) or worse the API binaries itself, but I'm
sure Peter can enlighten me here.


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

View raw message