I would say both. include in the jar and stamp the jar name with the version.
Some developers do the following: -get a jar as (1.3.qwerty.jar) and rename to qwerty.jar. This eliminates breaking classpaths.. I'm in this group. Much easier. -get a jar as 1.3.qwerty.jar and keep it that name. PROS: This causes classpath problems... can be a good thing. you know exactly what version of jars you have. CONS: If classpath is not changed. It causes major problems in a production environment. Ie. ClassNotFoundExceptions after a server is started, etc. I'm all for making the version in the name the file.. ie. qwerty.1.2.jar. I'm in the former group. I'll just rename the jar just to prevent classpath issues. My 2 cents... See Ya, Nick > -----Original Message----- > From: James E Weaver [mailto:[EMAIL PROTECTED] > Sent: Friday, June 11, 2004 9:49 AM > To: [EMAIL PROTECTED] > Subject: RE: [Jwebunit-development] 1.2 release date > > > > > > > Nick, > > I've seen version info included before in various ways when > you build, and > I think we probably should stamp the jar in some way. Should > the built > jwebunit jar adhere to the same maven-style standard that our jarred > dependencies do (version is in the name of the file)? > > Jim > > > > > |---------+------------------------------------------------> > | | Nick Neuberger | > | | <[EMAIL PROTECTED]> | > | | Sent by: | > | | [EMAIL PROTECTED]| > | | ceforge.net | > | | | > | | | > | | 06/11/2004 07:41 AM | > | | | > |---------+------------------------------------------------> > > >------------------------------------------------------------- > ---------------------------------------------------------------| > | > | > | To: > "'[EMAIL PROTECTED]'" > <[EMAIL PROTECTED]> | > | cc: > | > | Subject: RE: [Jwebunit-development] 1.2 release > date | > > >------------------------------------------------------------- > ---------------------------------------------------------------| > > > > > > > Martijn > > When shall I rtag the repository to R1_2? > > > > I would say tag everything afer: > -all or the vast majority of the fixes are done, it looks > like most are > fixed. > -everything compiles fine. > -all unittests pass. > -jars fine. > > create the release version. > > Is there a way during the jar / zip to include the "version" > which is R1_2? > I think I have seen an ANT task for something like this. Or > maven task?? > > Sometimes the version is placed in: > -manifest of the jar file. > -*.txt file in the jar / zip. > > Any thoughts. > > It would be much easier to debug problems from users... Although this > could > be added later.. > > See Ya, > > Nick > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the new InstallShield X. > From Windows to Linux, servers to mobile, InstallShield X is the > one installation-authoring solution that does it all. Learn more and > evaluate today! http://www.installshield.com/Dev2Dev/0504 > _______________________________________________ > Jwebunit-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jwebunit-development > - - - - - - This e-mail message is intended only for the use of the individual or entity identified in the alias address of this message and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this e-mail message is strictly prohibited. If you have received this e-mail message in error, please notify the sender immediately by reply e-mail and delete this message from your system. Thank you. ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Jwebunit-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jwebunit-development
