I sure hope you intend to post any changes to the Avalon list if you Modify those classes in any way.
-- The voice of reason There really aren't any issues with version conflicts at this time with excalibur CLI. Even if there were two copies of the jar in your classpath, your classloader would only use the first one. And Chances are that it hasn't changed a lick. > -----Original Message----- > From: Russell Butek [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 18, 2002 5:30 PM > To: [EMAIL PROTECTED] > Subject: RE: clutil.jar vs excalibur-cli.jar - get rid of them! > > > At first I thought this was a good idea. But now that the > idea has fermented in my brain for a few hours, I now think > this is a BAD idea. If we put something into axis that's > really part of something else, then we should rename it. > Otherwise, if some user picks up axis and then picks up that > something-else, then there could be two versions of the same > classes and this could result in name and behaviour conflicts. > > So I'll stick with my vote for 2.b. > > Russell Butek > [EMAIL PROTECTED] > > > Sam Ruby/Raleigh/IBM@IBMUS on 03/18/2002 03:22:56 PM > > Please respond to [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > cc: > Subject: RE: clutil.jar vs excalibur-cli.jar - get rid of them! > > > > Tom Jordahl wrote: > > > > A possibility is to check the excalibur-cli.jar file in to our tree > > and when we build axis.jar, we include all the class files in > excalibur-cli.jar > > in it. > > > > This removes the big problem of having another (really small and > uninteresting) > > jar file from the CLASSPATH but allows us to stay in sync with the > > code. > > > > The problem with this is I don't grok ant well enough to do > it myself. > > Insert the following some place prior to the actual <jar> task. > > <unzip src="${excalibur.jar}" dest="${build.dest}" /> > > - Sam Ruby > > P.S. Do not construe the above as a vote... I'm merely > answering a technical question. > > >
