Hi Xuan, > -----Original Message----- > From: Xuan Nguyen [mailto:[EMAIL PROTECTED] > Sent: mardi 5 juillet 2005 07:19 > To: 'Cactus Developers List' > Subject: RE: Cactus Task > > Hi Vincent, > > I've had a look to the Cargo branch, but haven't noticed much update for > the > cargo stuff.
That's strange. I remember that I had done quit a lot of changes there. Hmmm... I'll need to check it again. In any case do what you prefer. I'll create a new branch later on today as I'm not connected right now. > A HEAD branch would be more of help. > The three steps users currently have to carry out are relatively simple > enough for them. I prefer to keep the existing cargo tasks unless you or > other people have some ideas in mind to modify or change them. I'm still > new > to these :) Once again, I'm fine with keeping the <cactus> task but you *MUST* make the usage of Cargo transparent. That is, the user should be able to use a new version of Cargo with possibly new Ant task attributes without having to use a newer version of Cactus. They would just have to drop a new cargo jar in their Ant CP. This is really important. If this cannot be achieved I think it would be best to limit the <cactus> task to JUnit execution (it would still need to set a few cactus system properties though). > I think how Cargo can be integrated into Cactus would depend on how stable > Cargo API is. I don't understand this statement. My view is that it should be 100% transparent for Cactus, i.e. it is the Ant task from Cargo that should be used under the hood (even if they're not directly visible to Cactus users). > I guess if JSR88 is done for Cargo then there will not many > changes expected after that for the deployment API, similarly with JSR77. > Therefore, in my opitions an early plan for the Cargo API would be good, > if > peole in Cargo refactor the API as an anticiapation for compatibility with > these standards. Once more it should be completely transparent so it shouldn't matter at all what the Cargo API state it! :-) This is extremely important. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
