Re: [Ejbca-develop] [PATCH] build.xml

[Tomas G. <to...@pr...>]

Btw. I am against moving in cmd and sh scripts in ant. And this is 
because I don't think ant i a tool for everything, and as such should 
not be used for everything. Ant is not ideal for user-commands. For 
instance the command:
ra.sh adduser foo foo123 "C=SE,O=Foo,CN=Foo" FooCA null null 1 P12
would have to be written as:
ant adduser -Dusername=foo -Dpwd=foo...

Off-course you could prompt for input, but that kills the ability to 
script commands.
Or am I wrong?

We looked at that earlier, but scrapped the idea because it did not 
imporove user experience, rather the other way around. That was 
off-course in earlier days of ant.

Cheers,
Tomas


Stephane Bailliez wrote:

> I did a bit of clean up in the build file, there is still a lot to do 
> but that should be a reasonable first step.
>  
> Triple check that I did not do any harm with the packaging.
>  
> - I eliminated some unecessary expressions mostly in directory copies.
> - splitted the test compilation from main classes (ideally test should 
> be away from the main tree and use a mirror structure)
> - added a test:run target to be able to run tests. (I have a couple of 
> tests failing for some reasons between NPE and IAE)
> - added some jboss checks (valid jboss.home and server up and running 
> before deploy, etc...)
> - use <war>, <ear> and <jar> where appropriate
>  
> It would also be nice to split components in their respective source 
> tree rather than a whole tree of sources that encourage weird 
> dependencies and class by class packaging.
>  
> NB: You need xmlApis in /lib in order for the tests to run.
>  
> Ideally I would like to move all the nasty .cmd and .sh scripts and 
> put them in a specific build file
> My todo list would include as well:
> - migration from command line interaction to Ant tasks but that will 
> take a bit more time.
>  
> Stephane