I looked at SEC-96
http://opensource.atlassian.com/projects/spring/browse/SEC-96 and
thought it would be an easy thing to jump on.
The refactoring is actually very beneficial, as the Md5 and Sha
PasswordEncoder classes were basically duplicates with one word
changed (yuck).
I've refactored that
Really, just scratch the thought. The BaseDigestPasswordEncoder is
simple enough in it's purpose that I can leave it alone and put all my
MessageDigest stuff in it's own subclass.
On 5/30/06, Ray Krueger [EMAIL PROTECTED] wrote:
I looked at SEC-96
I took the freedom also to tag the source tree and bump the pom
versions to 1.1.0-SNAPSHOT
On 5/30/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
I'll take care of that
On 5/30/06, Ray Krueger [EMAIL PROTECTED] wrote:
Can we get the maven repos updated?
Right now mvn compile fails because
Hi,
We upgraded to the 1.0 final jar the other day and things worked fine on our
dev build,
which uses an InMemoryDao implementation. However, last night we tried to push
out a build
to the client and the context will no longer start due to a NoClassDefFound in
the Acegi
code.
That should read: I saw that, should it have been 1.0.1 though?
mashed the send button mid-correction hehe.
On 5/31/06, Ray Krueger [EMAIL PROTECTED] wrote:
I saw that, my should it have been 1.0.1 though?
On 5/30/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
I took the freedom also to tag the
I'm afraid it's true. It no longer compiles under Spring 1.2.7.
Something to log in JIRA for a 1.0.1.
On 5/31/06, Ben Munat [EMAIL PROTECTED] wrote:
Hi,
We upgraded to the 1.0 final jar the other day and things worked fine on our
dev build,
which uses an InMemoryDao implementation. However,
Usually it's bumped to the main next release that will have new
features. Not too important though.
On 5/31/06, Ray Krueger [EMAIL PROTECTED] wrote:
That should read: I saw that, should it have been 1.0.1 though?
mashed the send button mid-correction hehe.
On 5/31/06, Ray Krueger [EMAIL
http://opensource.atlassian.com/projects/spring/browse/SEC-288
I made it a blocker for 1.0.1
This means that the 1078 people that have downloaded 1.0.0 to this
point cannot use Ldap correct?
On 5/31/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
I'm afraid it's true. It no longer compiles under
I pulled an update from Subversion, and executed the following...
cd core
maven test
The tests run and then build failed, test failures.
One thing I've always wanted to know, and I know Carlos is going to
have the quick answer on this...
Where is one supposed to go to see what tests failed?
Thanks for entering the jira issue for me! I pulled from svn and built my own
jar with only two changes and I think it's
working now (the client hasn't called to complain yet :-) ).
All I did was change two places that use EmptyResultDataAccessException to use
the next superclass up, which is
That's pretty much the fix that I put in earlier today - the same issue
was raised in the forums yesterday
http://forum.springframework.org/showthread.php?t=25430
and in Jira as SEC-281.
Sorry it wasn't spotted earlier. Perhaps we should change the Spring
maven dependency back to 1.2.8 to
Sorry it wasn't spotted earlier. Perhaps we should change the Spring
maven dependency back to 1.2.8 to detect this kind of thing?
That's what i suggested some time ago. In fact for now only 1.2.7 is in ibiblio.
___
Home: http://acegisecurity.org
Carlos Sanchez wrote:
Sorry it wasn't spotted earlier. Perhaps we should change the Spring
maven dependency back to 1.2.8 to detect this kind of thing?
That's what i suggested some time ago. In fact for now only 1.2.7 is in
ibiblio.
Wouldn't that subsequently mean that Spring 2.x
In theory Spring is guaranteeing that 2.0 is backwards compatible, so
if it works on 1.2.x it'll work on 2.0.
In practice we could create a maven 2 profile setting the 2.0
dependencies and setting up continuous integration to build the
default (1.2.x) and the profile too (2.x)
On 5/31/06, Scott
Remeber that there's a Maven 2 repository now at
http://acegisecurity.sourceforge.net/repository/releases/
I just deployed the 1.0.0, with sources and javadocs. I changed maven
deployed jars for the ones in the distribution because they are signed
by Ben.
It'll be synced to the main maven
15 matches
Mail list logo
