> Proposal
>
>
> to me commons-exec is slightly over-engineered. As is, clients will
> have to resort to strange things and rewrite somewhat complex helper
> classes to do simple things.
>
> I propose to change the API.
>
> Vision: Make commons-exec a reusable Library that is available to
> I am also voluntary to produce documentation for the package (as said
> to Brett and Trygve yesterday), help redesign things if these small
> redesigns are allowed, making sure if will be used fully in
> CruiseControl and why not help ant migration when it comes.
Some notes below on that regard:
Hi,
I did the first step at integrating commons-exec into CruiseControl.
It's not in the trunk yet [1]. I am not using all the functionality
(Exec) and we still have some duplicated code that could be fixed if
commons-exec was a little bit more flexible (i.e. add some interfaces
where appropriate)
