Over the past couple of months, we've had a number of customers report issues to us regarding ClassNotFoundExceptions and proxies in dm Server. The issue actually has to do with type visibility in OSGi and is explained very well by Peter Kriens over at the OSGi Alliance Blog. Please take a look at his post if you are seeing classloading issues when using proxies in dm Server or any other OSGi runtime.

As Rob's post points out, over the last few months we've learned quite a bit about how people want to manage their own OSGi applications.

We found that some developers want to manage their own bundle manifests, but need a bit of help to automate the details such as specifying package versions across a range of imports. Other developers want to have manifests generated based on the content of their project and the dependencies specified in their build files. In addition, both kinds of developers need to work with existing libraries that do not have the necessary OSGi metadata that enable them…

Dear Spring community,
We are pleased to announce that Spring Batch 1.0.1.RELEASE has been released!

Downloads | Site | Changelog

This release focuses on bug-fixes and improvements in documentation.

Dear Spring community,

I'm pleased to announce that Spring Framework 2.5.3 has been released!  Download | Documentation

This is the third update release in the Spring 2.5 series. It fixes issues reported since 2.5.2 and introduces various enhancements, such as:

• @Autowired and @Required annotations interact more intuitively
• ControllerClassNameHandlerMapping detects @Controller beans by default
• "bean(...)" pointcut designator matches against bean aliases as well
• Spring 2.5 "jee:*" config elements use resource-ref="true" by default
• new CachingConnectionFactory for JMS session and producer pooling
• new DB…

I'm pleased to announce that Spring Batch 1.0.0.rc1 has been released.  You can access this release via the Spring Maven Milestone Repository (browse) or via the Download Page.

This is the first release candidate for the Spring Batch 1.0.0 release with an anticipated final release on 28 March.  The major changes for this release are:

• Improvements in Reference Documentation
• Reorganization of packaging structure in spring-batch-infrastructure and spring-batch-core
• Merging of the spring-batch-core and spring-batch-execution modules

Please see the changelog for details.

Ben Hale
Spring Batch Technical…

We are pleased to announce that the Spring .NET 1.1 final release is now available

Download | Support | Documentation | Changelog

 Feature Summary

•  Inversion of Control Container
• Aspect-Oriented Programming Framework
• Aspect Library
• ASP.NET Framework
• ASP.NET AJAX Integration
• ADO.NET Framework
• Declarative Transaction Management
• Declarative Middleware Services
• NHibernate Integration
• NUnit Integration Testing

This release has been a long time in the making and the team would like to extend our heartfelt thanks to everyone who has contributed to the project.

Happy Holidays and enjoy!

Spring Batch 1.0.0.m3 is now available via the Spring Portfolio Milestone Repository (browse).  See the Spring Batch downloads page for more information.

We have had a lot of good feedback from the community, and from a large number of Accenture projects that are using or evaluating Spring Batch.  So the 1.0.0-m3 release has quite a range of bug fixes and new features.  The main impact to existing users will be class name changes in the input and output abstractions.  New (non-Maven) users will find it much easier to get started with the new .zip assembly including all dependencies.  There is…

By popular demand, the Spring Framework Maven artifacts are now being uploaded to the Spring Snapshot Maven Repository. You can find details about all of the Spring Portfolio Maven repositories in my previous post but I'll reprint the details for the Spring snapshot repository here.

The Spring Snapshot Maven Repository is located at http://s3.amazonaws.com/maven.springframework.org/snapshot. Using this repository requires you to add an entry to the <repositories/> element in your POM. It should look like this:

<repository>
    <id>spring-snapshot</id>
    <name>Spring Portfolio Snapshot…

Up to this point the Spring Portfolio Maven artifacts, especially the snapshots, were inconsitently created and scattered about in various locations. Over the past couple of weeks, we’ve been working to get the projects to be more consistent in the creation and uploading of these artifacts.

Maven Repositories

One of the most useful improvements to the Maven support in the Spring Portfolio is the use of consistent repository locations. There are three different repositories depending on your level of comfort with the code.

Release Repository

For any final release (Spring 2.5, Spring Web Flow 2.0, etc.) the Maven artifacts for that release will be uploaded to the Maven Central repository (http://repo1.maven.org/maven2). Using this repository requires no effort on your part as Maven will automatically look for artifacts there.

The artifacts in this repository do follow expected repository behaviors and will not (and cannot) not be removed.

Milestone Repository

For any milestone release (Spring 2.5-RC1, Spring Web Flow 2.0-M2, etc.) the Maven artifacts for that release will be uploaded to the the Spring Milestone repository (http://s3.amazonaws.com/maven.springframework.org/milestone). Using this repository requires you to add an entry to the <repositories/> element in your POM. It should look like this:

<repository>
    <id>spring-milestone</id>
    <name>Spring Portfolio Milestone Repository</name>
    <url>http://s3.amazonaws.com/maven.springframework.org/milestone</url>
</repository>

The artifacts in this repository do not follow expected repository behaviors and will be removed regularly. Upon the release of a final version (Spring 2.6, Spring Web Flow 2.1, etc.) all milestone versions from the previous release of an artifact will be removed. For example, when Spring 2.6 is released, Spring 2.5 milestones will be removed while Spring 2.6 milestones will be retained.

Snapshot Repository

For any snapshot build (Spring 2.5-SNAPSHOT, Spring Web Flow 2.0-SNAPSHOT, etc.) the Maven artifacts for that build will be uploaded to the Spring Snapshot repository (http://s3.amazonaws.com/maven.springframework.org/snapshot). Using this repository requires you to add an entry to the <repositories/> element in your POM. It should look like this:

<repository>
    <id>spring-snapshot</id>
    <name>Spring Portfolio Snapshot Repository</name>
    <url>http://s3.amazonaws.com/maven.springframework.org/snapshot</url>
</repository>

The artifacts in this repository do not follow expected repository behaviors and will be removed regularly. At least the last 10 snapshot builds for a given artifact will be retained. If an artifact is removed from a distribution its snapshot builds will be removed immediately. On the release of a milestone or a final release, all snapshots for an artifact will be removed and a new snapshot for the next release created.

Repository Browsing

The milestone and snapshot repositories are both hosted on Amazon’s S3 service and as such the directory structure is not human-readable. To view the repositories in a human-readable format, use the S3Browse utility.

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

Only use these URLs for human-readable viewing. If you use them as the URLs for your POMs you will encounter errors.

Artifact Sources

Another important improvement is the addition of source artifacts for all releases. You will notice in the milestone repository all artifacts have sources deployed with them. This will also be true as we go forward for all final releases as well. Specifically, starting with the Spring 2.5 release, in addition to the combined Spring sources, each module will also have a source artifact.

Spring Snapshots

The final improvement is one that isn’t yet complete; a nightly snapshot of Spring. I’m pleased to say that this is close to being completed. I’m still working out the final kinks with respect to the Maven Ant Tasks but this will eventually start showing up and I’ll announce it again when it does. As well, you can expect this functionality to eventually make its way out to all of the other ANT-based Spring Portfolio projects so that all projects will create Maven snapshots as well as milestones.

With the release of Spring 2.1-m2, some significant changes have been made to the infrastructure of the Spring distribution. Please see the announcement and changelog for the complete list of changes.

Distribution

• spring-context.jar includes JMX support and core remoting support (no spring-jmx and spring-remoting jars anymore)
• spring-orm.jar combines all ORM support packages (replaces spring-hibernate, spring-ibatis, spring-jdo, spring-jpa, and spring-toplink jars)
• spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures)
• renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now
• renamed spring-support.jar to spring-context-support.jar
• renamed spring-portlet.jar to spring-webmvc-portlet.jar
• module jar files contain module-specific "spring.handlers" and "spring.schemas" files now

Maven Artifacts