springframework-developer

RE: [Springframework-developer] JARs .. can they be named based on their version ?

[Oliver H. <Oli...@ou...>]

I raised this as an issue in Jira.=20

http://opensource.atlassian.com/projects/spring/secure/ViewIssue.jspa?ke
y=3DSPR-68



-----Original Message-----
From: Cameron Braid [mailto:ca...@da...]=20
Sent: Wednesday, 24 March 2004 2:22 PM
To: spr...@li...
Subject: [Springframework-developer] JARs .. can they be named based on
their version ?


I have run into a problem with supporting multiple applications that use
different spring versions.

We store all of our jars, for every application, in a repository.

In eclipse we link against them, and when deploying we copy them into
the war/ear.

I upgraded an app to spring 1.0 HEAD yesterday, causing the new
aopalliance.jar to be overwritten in our repository.

I now receive an aopalliance exception because an app, using spring rc1,
requres the older aopalliance.jar file.

This issue would be avoided if every jar that spring uses (including the
spring generated jars) are stamped with their version in the filename.

I (and others) managed to convince Hibernate, WebWork2 and Xwork to
follow this pattern as well.=20

I think it is a great idea as it explicitly allows identification of
changes in jars.

Any thoughts ?

Cameron.

Re: [Springframework-developer] JARs .. can they be named based on their version ?

[<jue...@we...>]

Note that the Spring jar files contain the exact version number in the =
manifest file within the jar, just like jars of Apache products do. =
Furthermore, as of the upcoming 1.0 final, our third-party lib directory =
contains a readme.txt that specifies the exact product version and usage =
within Spring for each jar.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Colin Sampaleanu
Sent: Wednesday, March 24, 2004 4:34 AM
To: spr...@li...
Subject: Re: [Springframework-developer] JARs .. can they be named based
on their version ?


Cameron,

What's stopping you from renaming them yourself, and deploying that way? =

This is what I do personally in some projects that use Spring.=20
Everything has a version number, whether it shipped that way or not.

I realize we could do it too in Spring out of the gate, but there's pros =

and cons to both sides though...

Regards,
Colin


Cameron Braid wrote:

> I have run into a problem with supporting multiple applications that=20
> use different spring versions.
> =20
> We store all of our jars, for every application, in a repository.
> =20
> In eclipse we link against them, and when deploying we copy them into=20
> the war/ear.
> =20
> I upgraded an app to spring 1.0 HEAD yesterday, causing the new=20
> aopalliance.jar to be overwritten in our repository.
> =20
> I now receive an aopalliance exception because an app, using spring=20
> rc1, requres the older aopalliance.jar file.
> =20
> This issue would be avoided if every jar that spring uses (including=20
> the spring generated jars) are stamped with their version in the =
filename.
> =20
> I (and others) managed to convince Hibernate, WebWork2 and Xwork to=20
> follow this pattern as well.=20
> =20
> I think it is a great idea as it explicitly allows identification of=20
> changes in jars.
> =20
> Any thoughts ?
> =20
> Cameron.





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] JARs .. can they be named based on their version ?

[Ou, R. <Ro...@sa...>]

+1
=20
We do this for our project...
=20
Rong

-----Original Message-----
From: spr...@li... =
[mailto:spr...@li...]On Behalf =
Of Cameron Braid
Sent: Tuesday, March 23, 2004 9:22 PM
To: spr...@li...
Subject: [Springframework-developer] JARs .. can they be named based on =
their version ?


I have run into a problem with supporting multiple applications that use =
different spring versions.
=20
We store all of our jars, for every application, in a repository.
=20
In eclipse we link against them, and when deploying we copy them into =
the war/ear.
=20
I upgraded an app to spring 1.0 HEAD yesterday, causing the new =
aopalliance.jar to be overwritten in our repository.
=20
I now receive an aopalliance exception because an app, using spring rc1, =
requres the older aopalliance.jar file.
=20
This issue would be avoided if every jar that spring uses (including the =
spring generated jars) are stamped with their version in the filename.
=20
I (and others) managed to convince Hibernate, WebWork2 and Xwork to =
follow this pattern as well.=20
=20
I think it is a great idea as it explicitly allows identification of =
changes in jars.
=20
Any thoughts ?
=20
Cameron.

Re: [Springframework-developer] JARs .. can they be named based on their version ?

[Mike Cannon-B. <mi...@at...>]

Agreed - personally as a Maven shop this would be most appreciated. We =20=

already name all of the Spring JARs as they come out, but it would be =20=

very useful for some of the dependencies (although I know they're in a =20=

.txt file somewhere from memory).

Cheers,
Mike

--
ATLASSIAN - http://www.atlassian.com/

Confluence - the professional J2EE wiki - tried it yet?
http://www.atlassian.com/confluence/

On 24/03/2004, at 2:37 PM, Oliver Hutchison wrote:

> I raised this as an issue in Jira.
>
> http://opensource.atlassian.com/projects/spring/secure/ViewIssue.jspa?=20=

> ke
> y=3DSPR-68
>
>
>
> -----Original Message-----
> From: Cameron Braid [mailto:ca...@da...]
> Sent: Wednesday, 24 March 2004 2:22 PM
> To: spr...@li...
> Subject: [Springframework-developer] JARs .. can they be named based =
on
> their version ?
>
>
> I have run into a problem with supporting multiple applications that =20=

> use
> different spring versions.
>
> We store all of our jars, for every application, in a repository.
>
> In eclipse we link against them, and when deploying we copy them into
> the war/ear.
>
> I upgraded an app to spring 1.0 HEAD yesterday, causing the new
> aopalliance.jar to be overwritten in our repository.
>
> I now receive an aopalliance exception because an app, using spring =20=

> rc1,
> requres the older aopalliance.jar file.
>
> This issue would be avoided if every jar that spring uses (including =20=

> the
> spring generated jars) are stamped with their version in the filename.
>
> I (and others) managed to convince Hibernate, WebWork2 and Xwork to
> follow this pattern as well.
>
> I think it is a great idea as it explicitly allows identification of
> changes in jars.
>
> Any thoughts ?
>
> Cameron.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

Re: [Springframework-developer] JARs .. can they be named based on their version ?

[<ad...@te...>]

On 03-24-2004 16:41 +1100 Mike Cannon-Brookes <mi...@at...> wrote:
> Agreed - personally as a Maven shop this would be most appreciated. We
> already name all of the Spring JARs as they come out, but it would be
> very useful for some of the dependencies (although I know they're in a
> .txt file somewhere from memory).

Having jars contain version information poses a problem for version control 
systems.

The file spring.jar gets updated and keeps it's history.

A.

-- 
Adam Sherman
Technologist
+1 (613) 797-6819
http://www.terravox.com/