Menu
▾
▴
RE: [Springframework-developer] Example classes needed
|
From: <tri...@tr...> - 2003-08-28 17:41:25
|
Juergen, I like the manifest entry and I also like jars without version numbers. Thomas > I've just added a manifest entry "Spring-Version" to our build scripts. This > means that a "spring.jar" for 1.0 M1 will include a "Spring-Version=1.0m1" > entry in its META-INF/manifest.mf file. So if you've got jar files lying > around, you can always check the exact version. With this included, I tend to > drop version numbers even more. Thanks for the idea, Rob - I just guess it's > simpler to make a manifest entry than to include an extra file. > > We all seem to agree we prefer "spring.jar" over "spring-full.jar", but are > about 50:50 regarding version numbers in the name. So let's focus on the > latter: Would anyone *mind* no version number in the name, given that it's > mentioned in the manifest file? Everyone is free to rename the files any way > he wants anyway, it's just about the shipped jars. As for me, I would mind > the full version number "1.0m1" - in the meantime, I even prefer > "spring.jar". > > To keep the fire burning, some examples for no version numbers that I know > of: Servlet, JUnit, JavaMail, Xerces, JSTL, Commons Logging, Commons DBCP, > XAPool, Hibernate, COS, GLUE, Ant, Tomcat, JBoss, Clover. Counterexamples > with version numbers in the jar name: JTA, CGLIB, BCEL, Log4J, Castor, Tyrex, > Velocity, Tapestry, Hessian, iText, MySQL JDBC driver. > > In the end, one can argue for all options. There is no obvious solution. So > we should try to settle on one option and stick with it. > > Juergen > > > -----Original Message----- > From: Rob Butler [mailto:rob...@ve...] > Sent: Thursday, August 28, 2003 6:34 PM > To: jürgen höller [werk3AT]; Lars Fischer > Cc: spr...@li...; tri...@tr...; > rod...@in... > Subject: RE: [Springframework-developer] Example classes needed > > > Hello all, > > Since spring is modular, why not break it down even further into chuncks. > > spring-common.jar ->Basic stuff that is used everywhere in spring > spring-beans.jar -> contains ONLY the Spring Beans stuff. > spring-aop.jar -> contains ONLY the Spring AOP stuff. > spring-jdbc -> contains ONLY the Spring JDBC stuff. > spring-orm.jar -> contains ONLY the Spring ORM stuff. > spring-context.jar -> contains ONLY the Spring context stuff. > spring-mvc.jar -> contains ONLY the spring MVC stuff. > > If spring-orm.jar is dependent upon spring-common.jar then the user will need > to download and include spring-common.jar in the classpath too. In this way > people can pick and choose the exact parts they want, but you don't have to > come up with a million different package combinations... i.e. no packages > that include ORM & JDBC, but not MVC. Another one that has ORM, JDBC, > context, but not MVC. Another one that has ORM, jdbc & MVC. Another one > that has ORM, JDBC, context & MVC. See where I am going with this? > People should be smart enough to take the parts they want, and to get the > dependencies they need. > > Now as far as the file name goes, why not just use a name WITHOUT the version > name in it, and then include a file (or directory) in the root of the jar > called VERSION-1.0.1 or some such thing. That way people will not need to > worry about changing build scripts to use a newer version of the jar that is > API compatible, and they can still easiliy determine what version they are > using by looking in the jar itself. the only time the jar file name should > change is if the API has LARGE changes that renders the new jar completely > incompatible with the old API. Minor changes to the API should probably not > have the jar file names changed. > > Just some ideas and my 2 cents. > > Later > Rob > > > From: jürgen höller [werk3AT] <jue...@we...> > > Date: 2003/08/28 Thu PM 12:07:42 EDT > > To: "Lars Fischer" <lar...@gm...> > > CC: <spr...@li...>, > > <tri...@tr...>, > > <rod...@in...> > > Subject: RE: [Springframework-developer] Example classes needed > > > > Lars, > > > > The problem is that we have multiple jar files: > > - spring-beans.jar > > - spring-aop.jar > > - spring-jdbc.jar > > - spring-orm.jar > > - spring-context.jar > > - spring-full.jar > > > > "full" indicates that it includes all of Spring. We could name it > "spring.jar" of course, I'm quite inclined towards this if others agree. What > does everybody think? > > > > Regarding Colin's argument on in-between numbering: I wouldn't mind > dropping the version number altogether, in Hibernate/Ant/Servlet style. I'm > just not a fan of very specific file names. > > > > So 2 questions: > > 1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file > > 2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c) > "spring-beans.jar" > > > > In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b either, > though. > > > > Juergen > > > > > > -----Original Message----- > > From: Lars Fischer [mailto:lar...@gm...] > > Sent: Thursday, August 28, 2003 5:56 PM > > To: jürgen höller [werk3AT] > > Cc: spr...@li...; tri...@tr...; > > rod...@in... > > Subject: RE: [Springframework-developer] Example classes needed > > > > > > What about spring.jar, spring2.jar ? I don't like this "-full". > > > > > > > Hmmm, not much response yet... I still tend to prefer "sp > > > ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe > > > s not need to reflect the exact detail version. I conside > > > r it fine enough if it indicates the major version. See s > > > ervlet.jar, hibernate2.jar. Can we please decide on this > > > until *tomorrow*? :-) > > > > > > Juergen > > > > > > > > > > > > -----Original > > > Message----- > > > From: jürgen höller [werk3AT] > > > Sent: Mon > > > day, August 25, 2003 11:50 PM > > > To: Lars Fischer; springfr > > > ame...@li... > > > Cc: trisberg@tri > > > db.com > > > Subject: Re: [Springframework-developer] Example > > > classes needed > > > > > > > > > Let's vote on this. I don't mind eith > > > er naming strategy for jar files. Anybody else prefering > > > the spring-full-1.0m1 style? > > > > > > BTW, Hibernate uses hibe > > > rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8 > > > .jar for the specific version. 2 examples for opposite en > > > ds, I guess. > > > > > > Juergen > > > > > > > > > > > > -----Ursprüngliche Nac > > > hricht----- > > > Von: Lars Fischer [mailto:lars.fischer@gmxp > > > ro.net] > > > Gesendet: Mo 25.08.2003 23:18 > > > An: springframe > > > wor...@li... > > > Cc: jürgen hölle > > > r [werk3AT]; tri...@tr... > > > Betreff: Re: [Springfra > > > mework-developer] Example classes needed > > > > > > > > > > > > I agree w > > > ith Thomas, I once made a mistake because I didn't realiz > > > e > > > that I was using an older version. The jar-files shoul > > > d be named after > > > the version. > > > > > > > Juergen, > > > > > > > > The dr > > > awback then is that you can't tell from the jar file if i > > > t is M1, M2 > > > > or > > > > the release jar. > > > > > > > > Thomas > > > > > > > > > > > > It's gonna be "spring-framework-1.0m1" and "spring-full > > > -1.0.jar", if we > > > > stick > > > > > to the current plan. We've > > > used the same naming strategy for 0.9.x, e.g. > > > > > "spri > > > ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr > > > efer that > > > > way > > > > > to ease drop-in replacement in the > > > literal sense :-) The build > > > > properties > > > > > reflect th > > > is in "spring-version=1.0" and "spring-version-detail=1.0 > > > m1". > > > > > > > > > > Juergen > > > > > > > > > > > > > > > > > > > > -----Ur > > > sprÃf¼ngliche Nachricht----- > > > > > Von: trisberg@trid > > > b.com [ mailto:tri...@tr...] > > > > > Gesendet: Mo > > > 25.08.2003 19:21 > > > > > An: jÃf¼rgen hÃf¶ller [werk3A > > > T] > > > > > Cc: Lars Fischer; springframework-developer@l > > > ists.sourceforge.net > > > > > Betreff: RE: [Springframewo > > > rk-developer] Example classes needed > > > > > > > > > > > > > > > > > > > > > > > Juergen, > > > > > > > > > > > Anyway, ContextL > > > oaderServlet *will* be in 1.0 M1, to be released at > > > > th > > > e > > > > > end > > > > > > of this week if there aren't any ma > > > jor obstacles. BTW, can everybody > > > > > please > > > > > > > > > test the current CVS contents against own applications? > > > > > > > > > > > > > > > > I am updating the Step-by-ste > > > p-MVC document - what will the exact name > > > > of > > > > > the > > > > > > > > directory and the jar file be? I'm assuming 'sp > > > ring-framework-1.0M1' > > > > and > > > > > 'spring-full-1.0M1. > > > jar'. > > > > > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
