Re: [exec] API sketch?

2006-01-24 Thread Niklas Gustavsson
Brett Porter wrote: Niklas Gustavsson wrote: /* * StreamHandlers are used for providing input, * retriving the output. Also used for logging. */ StreamHandler getStreamHandler(); void setStreamHandler(StreamHandler streamHandler); My only comments on these is that I don't see the point of

Re: [exec] API sketch?

2006-01-24 Thread Niklas Gustavsson
Brett Porter wrote: Niklas Gustavsson wrote: /* * StreamHandlers are used for providing input, * retriving the output. Also used for logging. */ StreamHandler getStreamHandler(); void setStreamHandler(StreamHandler streamHandler); My only comments on these is that I don't see the point of

Re: [exec] API sketch?

2006-01-23 Thread Brett Porter
jerome lacoste wrote: There's only one issue: backward compatibility. I have over 1000 lines of code that use the former API. So if the switch could be not too hard to do... Use the IntelliJ Migration assistant :) Seriously - I'd say here we should strive for biut not be constrained by

Re: [exec] API sketch?

2006-01-23 Thread Brett Porter
Niklas Gustavsson wrote: /* * StreamHandlers are used for providing input, * retriving the output. Also used for logging. */ StreamHandler getStreamHandler(); void setStreamHandler(StreamHandler streamHandler); My only comments on these is that I don't see the point of the setters in the

Re: [exec] API sketch?

2006-01-20 Thread jerome lacoste
On 1/13/06, Brett Porter [EMAIL PROTECTED] wrote: Hi, Back in September 05 (wow, is it really 2006 already? :) Jerome sent a comprehensive vision for exec. I found myself agreeing with most everything in there (I'll reply to a couple of specifics shortly). Message ID from then: [EMAIL

Re: [exec] API sketch?

2006-01-18 Thread jerome lacoste
On 1/17/06, Niklas Gustavsson [EMAIL PROTECTED] wrote: Hi jerome lacoste wrote: I had some changes in mind compared to my original design proposal, to make it simpler. So I am willing to help you design test this API/implementation and make sure it works with CruiseControl. Great!

Re: [exec] API sketch?

2006-01-17 Thread jerome lacoste
On 1/13/06, Brett Porter [EMAIL PROTECTED] wrote: Hi, Back in September 05 (wow, is it really 2006 already? :) Jerome sent a comprehensive vision for exec. I found myself agreeing with most everything in there (I'll reply to a couple of specifics shortly). Message ID from then: [EMAIL

Re: [exec] API sketch?

2006-01-17 Thread Niklas Gustavsson
Hi jerome lacoste wrote: I had some changes in mind compared to my original design proposal, to make it simpler. So I am willing to help you design test this API/implementation and make sure it works with CruiseControl. Great! I don't want to duplicate efforts so I would prefer a

Re: [exec] API sketch?

2006-01-17 Thread Niklas Gustavsson
Hi jerome lacoste wrote: I had some changes in mind compared to my original design proposal, to make it simpler. So I am willing to help you design test this API/implementation and make sure it works with CruiseControl. Great! I don't want to duplicate efforts so I would prefer a

Re: [exec] API sketch?

2006-01-14 Thread Niklas Gustavsson
Hi Brett Porter wrote: Hi, Back in September 05 (wow, is it really 2006 already? :) Jerome sent a comprehensive vision for exec. I found myself agreeing with most everything in there (I'll reply to a couple of specifics shortly). Message ID from then: [EMAIL PROTECTED] However, it was long

[exec] API sketch?

2006-01-12 Thread Brett Porter
Hi, Back in September 05 (wow, is it really 2006 already? :) Jerome sent a comprehensive vision for exec. I found myself agreeing with most everything in there (I'll reply to a couple of specifics shortly). Message ID from then: [EMAIL PROTECTED] However, it was long and wordy. I think the key