<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Spring Framework 3.0 RC2 released</title>
	<atom:link href="http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/</link>
	<description>The voice of SpringSource</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:31:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: viking</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-193429</link>
		<dc:creator>viking</dc:creator>
		<pubDate>Fri, 06 May 2011 13:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-193429</guid>
		<description>Example using @Inject corse :)</description>
		<content:encoded><![CDATA[<p>Example using @Inject corse <img src='http://blog.springsource.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: viking</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-193428</link>
		<dc:creator>viking</dc:creator>
		<pubDate>Fri, 06 May 2011 13:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-193428</guid>
		<description>Great work! 
Could you get some example or indicate some svn url :), too?

Thanx a lot.</description>
		<content:encoded><![CDATA[<p>Great work!<br />
Could you get some example or indicate some svn url <img src='http://blog.springsource.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> , too?</p>
<p>Thanx a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitch Gitman</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169788</link>
		<dc:creator>Mitch Gitman</dc:creator>
		<pubDate>Wed, 02 Dec 2009 16:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169788</guid>
		<description>Following up the earlier comments about not being able to find 3.0.0.RC2 in any Maven repositories, I’m wondering if there are any Ivy repositories out there where I might be able to find 3.0.0.RC2. If so, what are the Ivy settings to use?

I ran into trouble trying to consume 3.0.0.RC2 at its expected Ivy repository locations according to Spring’s own build. Here’s what I tried. 

I used projects/spring-build/common/ivysettings.xml in the distribution to configure Ivy. I made sure all the stuff in projects/spring-build/lib/ivy/ was in the classpath that created Ivy. Then I tried doing an ivy:resolve on an arbitrary Spring module against the spring-portfolio-lookup resolver. All I got was messages like the following:
[ivy:resolve]   ==== bundle-release-repository: tried
[ivy:resolve]     s3://repository.springsource.com/ivy/bundles/release/org.springframework/org.springframework.context/3.0.0.RC2/ivy-3.0.0.RC2.xml
[ivy:resolve]   ==== bundle-milestone-repository: tried
[ivy:resolve]     s3://repository.springsource.com/ivy/bundles/milestone/org.springframework/org.springframework.context/3.0.0.RC2/ivy-3.0.0.RC2.xml
...
...
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           :: org.springframework#org.springframework.context;3.0.0.RC2: not found
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::

Then I figured, even if the Spring modules themselves aren’t at the expected Ivy repositories, surely their third-party dependencies are. Otherwise I wouldn’t have been able to build 3.0.0.RC2 by hand. (See previous message.) So I tried doing an ivy:resolve on an arbitrary third-party module against the external-lookup resolver. What I get is a variation on the same problem:

[ivy:resolve]   ==== bundle-external-repository: tried
[ivy:resolve]     s3://repository.springsource.com/ivy/bundles/external/org.apache.commons/com.springsource.org.apache.commons.logging/1.1.1/ivy-1.1.1
.xml
[ivy:resolve]   ==== library-external-repository: tried
[ivy:resolve]     s3://repository.springsource.com/ivy/libraries/external/org.apache.commons/com.springsource.org.apache.commons.logging/1.1.1/ivy-1.1
.1.xml
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           :: org.apache.commons#com.springsource.org.apache.commons.logging;1.1.1: not found
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::

Now, what’s odd to me about this failure is that the same resolve had to be succeeding against the same repositories since I managed to get the Spring build working, and it had to find those modules somewhere.

Thankfully, I&#039;m able to do some hacks, based on what the Spring build outputs, to be able to consume a reconstituted 3.0.0.RC2 via Ivy. Just, it would be nice if there were a right, recommended way to do this.</description>
		<content:encoded><![CDATA[<p>Following up the earlier comments about not being able to find 3.0.0.RC2 in any Maven repositories, I’m wondering if there are any Ivy repositories out there where I might be able to find 3.0.0.RC2. If so, what are the Ivy settings to use?</p>
<p>I ran into trouble trying to consume 3.0.0.RC2 at its expected Ivy repository locations according to Spring’s own build. Here’s what I tried. </p>
<p>I used projects/spring-build/common/ivysettings.xml in the distribution to configure Ivy. I made sure all the stuff in projects/spring-build/lib/ivy/ was in the classpath that created Ivy. Then I tried doing an ivy:resolve on an arbitrary Spring module against the spring-portfolio-lookup resolver. All I got was messages like the following:<br />
[ivy:resolve]   ==== bundle-release-repository: tried<br />
[ivy:resolve]     s3://repository.springsource.com/ivy/bundles/release/org.springframework/org.springframework.context/3.0.0.RC2/ivy-3.0.0.RC2.xml<br />
[ivy:resolve]   ==== bundle-milestone-repository: tried<br />
[ivy:resolve]     s3://repository.springsource.com/ivy/bundles/milestone/org.springframework/org.springframework.context/3.0.0.RC2/ivy-3.0.0.RC2.xml<br />
&#8230;<br />
&#8230;<br />
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::<br />
[ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::<br />
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::<br />
[ivy:resolve]           :: org.springframework#org.springframework.context;3.0.0.RC2: not found<br />
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::</p>
<p>Then I figured, even if the Spring modules themselves aren’t at the expected Ivy repositories, surely their third-party dependencies are. Otherwise I wouldn’t have been able to build 3.0.0.RC2 by hand. (See previous message.) So I tried doing an ivy:resolve on an arbitrary third-party module against the external-lookup resolver. What I get is a variation on the same problem:</p>
<p>[ivy:resolve]   ==== bundle-external-repository: tried<br />
[ivy:resolve]     s3://repository.springsource.com/ivy/bundles/external/org.apache.commons/com.springsource.org.apache.commons.logging/1.1.1/ivy-1.1.1<br />
.xml<br />
[ivy:resolve]   ==== library-external-repository: tried<br />
[ivy:resolve]     s3://repository.springsource.com/ivy/libraries/external/org.apache.commons/com.springsource.org.apache.commons.logging/1.1.1/ivy-1.1<br />
.1.xml<br />
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::<br />
[ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::<br />
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::<br />
[ivy:resolve]           :: org.apache.commons#com.springsource.org.apache.commons.logging;1.1.1: not found<br />
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::</p>
<p>Now, what’s odd to me about this failure is that the same resolve had to be succeeding against the same repositories since I managed to get the Spring build working, and it had to find those modules somewhere.</p>
<p>Thankfully, I&#039;m able to do some hacks, based on what the Spring build outputs, to be able to consume a reconstituted 3.0.0.RC2 via Ivy. Just, it would be nice if there were a right, recommended way to do this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitch Gitman</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169785</link>
		<dc:creator>Mitch Gitman</dc:creator>
		<pubDate>Wed, 02 Dec 2009 15:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169785</guid>
		<description>I&#039;m experimenting with building 3.0.0.RC2 from scratch. Running &quot;ant&quot; and &quot;ant jar package&quot; from projects/build-spring-framework/ works without a hitch. 

I noticed, though, that everything that got built came out with a version of 3.0.0.BUILD-timestamp (where timestamp is in yyyyMMdd... form). This verbose, snapshot-like version would show up in both the JAR names and as the revision in the ivy.xml files that get generated. Instead of this, I wanted to see if I could generate the actual version, 3.0.0.RC2, as the version.

I tried going to projects/build.properties and changing the version property from 3.0.0 to 3.0.0.RC2, but there&#039;s a bundlor Ant task invocation that would complain there was something invalid about that. Also, there&#039;s a build.stamp property commented out in build.properties; I tried setting that to an empty string, but a BUILD-timestamp suffix would still get added to the version.

Can anyone say how to configure the Spring build to produce 3.0.0.RC2 as the actual version?</description>
		<content:encoded><![CDATA[<p>I&#039;m experimenting with building 3.0.0.RC2 from scratch. Running &#034;ant&#034; and &#034;ant jar package&#034; from projects/build-spring-framework/ works without a hitch. </p>
<p>I noticed, though, that everything that got built came out with a version of 3.0.0.BUILD-timestamp (where timestamp is in yyyyMMdd&#8230; form). This verbose, snapshot-like version would show up in both the JAR names and as the revision in the ivy.xml files that get generated. Instead of this, I wanted to see if I could generate the actual version, 3.0.0.RC2, as the version.</p>
<p>I tried going to projects/build.properties and changing the version property from 3.0.0 to 3.0.0.RC2, but there&#039;s a bundlor Ant task invocation that would complain there was something invalid about that. Also, there&#039;s a build.stamp property commented out in build.properties; I tried setting that to an empty string, but a BUILD-timestamp suffix would still get added to the version.</p>
<p>Can anyone say how to configure the Spring build to produce 3.0.0.RC2 as the actual version?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Obtaining Spring 3 Artifacts with Maven &#124; SpringSource Team Blog</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169760</link>
		<dc:creator>Obtaining Spring 3 Artifacts with Maven &#124; SpringSource Team Blog</dc:creator>
		<pubDate>Wed, 02 Dec 2009 06:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169760</guid>
		<description>[...] on December 2nd, 2009 by Keith Donald in Spring.  A recent commentor here ragged, &quot;It&#039;s only half of the world that&#039;s using Maven&quot;, when pointing [...]</description>
		<content:encoded><![CDATA[<p>[...] on December 2nd, 2009 by Keith Donald in Spring.  A recent commentor here ragged, &quot;It&#39;s only half of the world that&#39;s using Maven&quot;, when pointing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Baruch Sadogursky</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169718</link>
		<dc:creator>Baruch Sadogursky</dc:creator>
		<pubDate>Mon, 30 Nov 2009 15:25:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169718</guid>
		<description>The current implementation in Spring3 RC2 is only a subset of the standalone Java-config capabilities (which is stale since 1.0.0M4 in favor of integration with Spring3) . A lot of features, existing in 1.0.0M4 simply do not exist in Spring3 RC2 AnnotationConfigApplicationContext. E.g. - @AspectJAutoProxy, @AnnotationDrivenTx, etc.

If I am not in error, Release Candidate implies feature-freeze. Does it mean final version of Spring3 AnnotationConfigApplicationContext won&#039;t have those critical features?</description>
		<content:encoded><![CDATA[<p>The current implementation in Spring3 RC2 is only a subset of the standalone Java-config capabilities (which is stale since 1.0.0M4 in favor of integration with Spring3) . A lot of features, existing in 1.0.0M4 simply do not exist in Spring3 RC2 AnnotationConfigApplicationContext. E.g. &#8211; @AspectJAutoProxy, @AnnotationDrivenTx, etc.</p>
<p>If I am not in error, Release Candidate implies feature-freeze. Does it mean final version of Spring3 AnnotationConfigApplicationContext won&#039;t have those critical features?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wim</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169659</link>
		<dc:creator>Wim</dc:creator>
		<pubDate>Thu, 26 Nov 2009 12:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169659</guid>
		<description>Released? As previous posters said: it&#039;s not much of a &quot;release&quot; if it isn&#039;t in your milestone repo yet and thus not easily available for inclusion in (test) applications.</description>
		<content:encoded><![CDATA[<p>Released? As previous posters said: it&#039;s not much of a &#034;release&#034; if it isn&#039;t in your milestone repo yet and thus not easily available for inclusion in (test) applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Medieval Programming &#187; devoxx is over</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169642</link>
		<dc:creator>Medieval Programming &#187; devoxx is over</dc:creator>
		<pubDate>Wed, 25 Nov 2009 13:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169642</guid>
		<description>[...] lot (as always), but interestingly it was mainly on three topics * New Features of JDK 7, EE 6 and Spring 3 * New programming models like the famous map&amp;reduce, big tables etc * New JVM based languages: [...]</description>
		<content:encoded><![CDATA[<p>[...] lot (as always), but interestingly it was mainly on three topics * New Features of JDK 7, EE 6 and Spring 3 * New programming models like the famous map&amp;reduce, big tables etc * New JVM based languages: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdboer</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169626</link>
		<dc:creator>jdboer</dc:creator>
		<pubDate>Mon, 23 Nov 2009 23:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169626</guid>
		<description>Can you please public the Spring 3 RC2 modules in a Maven repository? It&#039;s only half of the world that&#039;s using Maven.
I found these S3 repositories but they do not contain all modules (I want to use the spring-web module) and I also think not all dependencies are correct because when I include spring-beans in my project, I do not get the spring-core and spring-context dependencies with it.

Milestone Repository: http://s3browse.com/explore/maven.springframework.org/milestone
Snapshot Repository: http://s3browse.com/explore/maven.springframework.org/snapshot

Tnkx!!</description>
		<content:encoded><![CDATA[<p>Can you please public the Spring 3 RC2 modules in a Maven repository? It&#039;s only half of the world that&#039;s using Maven.<br />
I found these S3 repositories but they do not contain all modules (I want to use the spring-web module) and I also think not all dependencies are correct because when I include spring-beans in my project, I do not get the spring-core and spring-context dependencies with it.</p>
<p>Milestone Repository: <a href="http://s3browse.com/explore/maven.springframework.org/milestone" rel="nofollow">http://s3browse.com/explore/maven.springframework.org/milestone</a><br />
Snapshot Repository: <a href="http://s3browse.com/explore/maven.springframework.org/snapshot" rel="nofollow">http://s3browse.com/explore/maven.springframework.org/snapshot</a></p>
<p>Tnkx!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bencmai</title>
		<link>http://blog.springsource.org/2009/11/13/spring-framework-3-0-rc2-released/comment-page-1/#comment-169573</link>
		<dc:creator>bencmai</dc:creator>
		<pubDate>Fri, 20 Nov 2009 07:24:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=3117#comment-169573</guid>
		<description>where is spring3 rc2 maven repository url
it seem that http://repository.springsource.com/maven/bundles/milestone  no longer get it

thx!!!</description>
		<content:encoded><![CDATA[<p>where is spring3 rc2 maven repository url<br />
it seem that <a href="http://repository.springsource.com/maven/bundles/milestone" rel="nofollow">http://repository.springsource.com/maven/bundles/milestone</a>  no longer get it</p>
<p>thx!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

