Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spring 3.1.1 #4

Merged
merged 2 commits into from
Jul 7, 2012
Merged

Spring 3.1.1 #4

merged 2 commits into from
Jul 7, 2012

Conversation

hazendaz
Copy link
Member

@hazendaz hazendaz commented Jul 7, 2012

Here is Spring updated to 3.1.1. Both the ANT test and JUNIT tests work as expected which exception of 4 tests I previously mentioned failing on my machine. I did a fresh pull which this time showed from the actual master not my copy of the master. The changes showed only the actual changes I was making prior to committing. After committing, it looks like it changed again on formatting. Based on the fact that I edited some files using notepad and the rest in eclipse, I don't think eclipse is causing the issue but rather the commit process. I'm using the git hub GUI. I closely verified every file prior to hitting commit. They all looked correct. As soon as the commit was completed, they looked different. At the moment, I'm unsure how to get around this other than going to the command prompt method for git hub. It seems to be the GUI is sort of problematic. Anyway, this batch is much smaller in actual code so should be easier to merge than the last.

@dblock
Copy link
Collaborator

dblock commented Jul 7, 2012

Question: if I have Spring Security 3.0, do you think it works after the upgrade? Otherwise I need to branch a spring-security 3.0 first before merging this.

@hazendaz
Copy link
Member Author

hazendaz commented Jul 7, 2012

Since I did this against the master (not spring 2 version), both spring 3.0.3 and spring security 3.0.3 were being used at present. So both of these are bumped up to 3.1.1. I personally don't use spring but all the test cases worked after the change. I even ran a test using the demo for spring to make sure it worked. The only coding change was to switch a deprecated method, add casting in the test cases, and fix the xsd in the demos as another user mentioned . So on the main line I think it would be ok.

-----Original Message-----
From: Daniel Doubrovkine (dB.) [mailto:[email protected]]
Sent: Saturday, July 07, 2012 11:50 AM
To: hazendaz
Subject: Re: [waffle] Spring 3.1.1 (#4)

Question: if I have Spring Security 3.0, do you think it works after the upgrade? Otherwise I need to branch a spring-security 3.0 first before merging this.


Reply to this email directly or view it on GitHub:
#4 (comment)

@hazendaz
Copy link
Member Author

hazendaz commented Jul 7, 2012

Here is some info off the spring website. Looks like version 2 hasn't been updated since August 2011. I'll ask some guys at work that do spring stuff where they are at as far as versioning goes. My team doesn't use spring as we skipped past it onto java ee 6 (glassfish) for the things spring would have gave us.

Getting Spring Security
Spring Security 3.1.1.RELEASE

Spring Security 3.1.1.RELEASE is the latest production release. It requires a minimum of Spring 3.0.6 and Java 5.

Download

Spring Security 3.0.7 is the previous production release. It requires a minimum of Spring 3.0.6 and Java 5.

Download

Spring Security 2.0.7

This is the latest release of the legacy Spring Security 2 version. It is compatible with Spring 2.0 and 2.5 releases and requires a minimum of Java 1.4. New users should use Spring Security 3.1 in preference.

Download

Spring Security Snapshot Releases

If you are using Maven as your build system (or another system which can use Maven repositories), then you can build directly against the latest project snapshots by adding the Spring snapshot repository (http:https://maven.springframework.org/snapshot/) to your build. You can also browse the repository directly.

-----Original Message-----
From: Daniel Doubrovkine (dB.) [mailto:[email protected]]
Sent: Saturday, July 07, 2012 11:50 AM
To: hazendaz
Subject: Re: [waffle] Spring 3.1.1 (#4)

Question: if I have Spring Security 3.0, do you think it works after the upgrade? Otherwise I need to branch a spring-security 3.0 first before merging this.


Reply to this email directly or view it on GitHub:
#4 (comment)

@dblock
Copy link
Collaborator

dblock commented Jul 7, 2012

I am merging this, thank you.

dblock added a commit that referenced this pull request Jul 7, 2012
@dblock dblock merged commit 1d4f5a8 into Waffle:master Jul 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants