Jul 9, 2010

Spring Release v3.0.3

Last week, Spring released version 3.0.3 of the Spring Framework. Upgrades are always fun and fraught with hidden troubles. This one has gone smoothly in the handful of web projects I’ve upgraded since getting the update.

If you’re upgrading from an already updated Spring 3.0.X, it’s a mostly simple swap of their JAR files. Find your org.springframework…jar files and replace them with the new ones. I’d say it’s entirely a simple swap, but if I did that, someone would run into a conflict and blame me for it… They didn’t add any dependencies, but there are some updated things in the Spring bits that could break things if they’re currently being used. We’ve been fortunate that none of the changes have impacted our code; simple JAR swap for our stuff.

Be sure to check the change log for conflicts that might impact your projects.

About the Author

Object Partners profile.

One thought on “Spring Release v3.0.3

Leave a Reply

Your email address will not be published.

Related Blog Posts
Android Development for iOS Developers
Android development has greatly improved since the early days. Maybe you tried it out when Android development was done in Eclipse, emulators were slow and buggy, and Java was the required language. Things have changed […]
Add a custom object to your Liquibase diff
Adding a custom object to your liquibase diff is a pretty simple two step process. Create an implementation of DatabaseObject Create an implementation of SnapshotGenerator In my case I wanted to add tracking of Stored […]
Keeping Secrets Out of Terraform State
There are many instances where you will want to create resources via Terraform with secrets that you just don’t want anyone to see. These could be IAM credentials, certificates, RDS DB credentials, etc. One problem […]
Validating Terraform Plans using Open Policy Agent
When developing infrastructure as code using terraform, it can be difficult to test and validate changes without executing the code against a real environment. The feedback loop between writing a line of code and understanding […]