Felipe, I have had to provide an exploded implementation of the EarArchive, WarArchive and JarArchive to allow the EarParser to handle an exploded deployment. Currently they implement the Cactus interfaces as this is what is required to allow integration into EarParser.
I have 2 options: 1) Submit as is, in which case when the Cargo integration is completed, they must be enhanced and converted such that they implement the cargo interfaces. 2) Change them to implement the Cargo interfaces now, but this means that EarParser (WarParser should be changed too) would have to rely on the Cargo implementations. I am not sure that this wouldn't break something else. It would also be better to have done this in another changeset than the one I have for 238. Which path would you prefer I follow? Also, I have the doco and a testcase ready to go. So whenever you give me feedback on above I should be able to submit a patch containing the lot. William -----Original Message----- From: Felipe Leme [mailto:[EMAIL PROTECTED] Sent: Monday, 24 April 2006 11:32 AM To: Cactus Developers List Subject: Re: EarArchive, WarArchive, JarArchive William Ferguson wrote: > I notice that the test cases use the above classes from Cargo, but that > there are extremely similar classes in > org.apache.cactus.integration.ant.deployment The Cargo integration is not completed yet... > > Should the ones in cactus be deprecated in favour of the Cargo ones? Yes, please use the new ones wherever possible. -- Felipe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
