Schaible, J�rg wrote:
Hi Steve,
Good.
Two last remarks:
;-)
To get the previous build behaviour I should now only copy the ant.properties.sample files, but if I have a manual interaction, why do you comment-out all the avalon entries? The users are already used to have to build the other avalon libs before.The reason why is that is they copied the sample file just to do something like modification of compiler directives - then if the local includes were not commented out - then they would be obliged to do a checkout of avalon and excalibur. At the same time I'm trying to make sure that the default build works with Gump (which it does) and is reasonably consistent with my own Maven based build (do you get the impression that I'm juggling a bunch of balls in the air at the same time?).
My firewall and proxy problem also strikes building the docs. Unfortunately the links to the J2SE and J2EE docs are hard coded. It would be good to have two properies here too, that can be overwritten in the ant.properties file, since many may have the docs offline anyway.Have just updated the respective builds so that the links are property based - i.e. you should be able to resolve these locally.
Cheers, Steve.
Thnx for your support,
J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-- Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
