Re: [Springframework-developer] Example classes needed

[Colin S. <col...@ex...>]

Well in this case, I think the best choice is probably something like 
spring-full.jar for this version, then something like 
spring2-full.jar/spring-full2.jar for the next version which breaks api 
compatibility, etc. This works on the assumption that people are 
manually managing dependencies, and allows people to slip in new jars 
without changing references when the api has not changed. Then for maven 
usage, what would happen is that it would be uploaded to ibiblio (or 
whatever maven repository) with the full version number, for example, 
spring-full-1.0.1.jar. The maven users would specify the exact version 
in the project files.

The alternative, to have the full version in the the name, is almost as 
good, as the manual people can rename it to whatever they like.

But I don't like the in-between variant. It's not exact enough for maven 
handling, and too exact for manual handling.

Again, when the api is no longer upwards compatible and you have 
something like hibernate vs hibernate2, I think that needs to be 
reflected in the name since I basically consider those different 
apis/libs, not just different versions.

Justy my opinion :-)


jürgen höller [werk3AT] wrote:

>We manage our dependencies manually here at werk3AT :-) And as far as I remember, no Hibernate user has complained about hibernate2.jar yet.
>
>Juergen
>
>
>-----Original Message-----
>From: Colin Sampaleanu [mailto:col...@ex...]
>Sent: Thursday, August 28, 2003 3:04 PM
>To: jürgen höller [werk3AT]
>Cc: spr...@li...
>Subject: Re: [Springframework-developer] Example classes needed
>
>
>To throw some water into the fire, :-), I prefer the exact name when 
>using Maven, since I can enforce what I am getting, but when managing 
>dependencies manually, I prefer not to have a version in the name except 
>when it is something like a major version number which indicates a 
>different api; then I can slip a new version in as needed without 
>changing all references.
>
>jürgen höller [werk3AT] wrote:
>
>  
>
>>Hmmm, not much response yet... I still tend to prefer 
>>"spring-full-1.0.jar", for easy drop-in. IMO, a jar file does not need 
>>to reflect the exact detail version. I consider it fine enough if it 
>>indicates the major version. See servlet.jar, hibernate2.jar. Can we 
>>please decide on this until *tomorrow*? :-)
>> 
>>Juergen
>> 
>> 
>>
>>    -----Original Message-----
>>    *From:* jürgen höller [werk3AT]
>>    *Sent:* Monday, August 25, 2003 11:50 PM
>>    *To:* Lars Fischer; spr...@li...
>>    *Cc:* tri...@tr...
>>    *Subject:* Re: [Springframework-developer] Example classes needed
>>
>>    Let's vote on this. I don't mind either naming strategy for jar
>>    files. Anybody else prefering the spring-full-1.0m1 style?
>>     
>>    BTW, Hibernate uses hibernate2.jar for its whole 2.x tree. Log4J
>>    uses log4j-1.2.8.jar for the specific version. 2 examples for
>>    opposite ends, I guess.
>>     
>>    Juergen
>>     
>>     
>>
>>        -----Ursprüngliche Nachricht-----
>>        *Von:* Lars Fischer [mailto:lar...@gm...]
>>        *Gesendet:* Mo 25.08.2003 23:18
>>        *An:* spr...@li...
>>        *Cc:* jürgen höller [werk3AT]; tri...@tr...
>>        *Betreff:* Re: [Springframework-developer] Example classes needed
>>
>>        I agree with Thomas, I once made a mistake because I didn't
>>        realize
>>        that I was using an older version. The jar-files should be
>>        named after
>>        the version.
>>
>>        > Juergen,
>>        >
>>        > The drawback then is that you can't tell from the jar file
>>        if it 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.
>>        > > "spring-framework-0.9.1" but still "spring-full-0.9.jar".
>>        I prefer that
>>        > way
>>        > > to ease drop-in replacement in the literal sense :-) The build
>>        > properties
>>        > > reflect this in "spring-version=1.0" and
>>        "spring-version-detail=1.0m1".
>>        > > 
>>        > > Juergen
>>        > > 
>>        > > 
>>        > >
>>        > >     -----Ursprüngliche Nachricht-----
>>        > >     Von: tri...@tr... [mailto:tri...@tr...]
>>        > >     Gesendet: Mo 25.08.2003 19:21
>>        > >     An: jürgen höller [werk3AT]
>>        > >     Cc: Lars Fischer;
>>        spr...@li...
>>        > >     Betreff: RE: [Springframework-developer] Example
>>        classes needed
>>        > >    
>>        > >    
>>        > >
>>        > >     Juergen,
>>        > >    
>>        > >     > Anyway, ContextLoaderServlet *will* be in 1.0 M1, to
>>        be released at
>>        > the
>>        > > end
>>        > >     > of this week if there aren't any major obstacles.
>>        BTW, can everybody
>>        > > please
>>        > >     > test the current CVS contents against own applications?
>>        > >     >
>>        > >    
>>        > >     I am updating the Step-by-step-MVC document - what
>>        will the exact name
>>        > of
>>        > > the
>>        > >     directory and the jar file be?  I'm assuming
>>        'spring-framework-1.0M1'
>>        > and
>>        > >     'spring-full-1.0M1.jar'.
>>        > >    
>>        > >     Thomas
>>        > >    
>>        > >
>>        > >
>>        >
>>        >
>>        >
>>
>>    
>>
>
>
>  
>