I noticed these jars myself as I was doing some work on the StarTeam tasks this weekend. What version did this start with? Is there some documentation on this change? What are the expected benefits? Right from the start I would guess it makes it easier to debug problems. No longer do you have an optional.jar whose contents are hidden.
However, are there dependencies among the dependencies? So that needs-x.jar might be different depending on whether needs-y.jar is built or not? Or is that not an issue? Would that make it possible to simply drop a needs-*.jar onto the classpath to change the behavior of ant? I'd like to understand the thinking behind this. Sorry I haven't been keeping up on the discussions as much as I should have. -----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED] Sent: Tue 10/22/2002 1:16 AM To: [EMAIL PROTECTED] Cc: Subject: Re: needs-*.jar? On Mon, 21 Oct 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote: > I believe Stefan exploded optional.jar into as many jars as > dependencies!?!? Yes, he did. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
<<winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
