Re: [Springframework-developer] Spring 1.2 RC2 and Acegi Security

[Luke T. <ne...@fr...>]

Hi,

I discussed this with Ben the other night and the Acegi Maven build is 
now building against a Spring daily snapshot (generated by the Spring 
Maven build) so any inconsistencies will hopefully be detected right away.

I modified the Acegi code earlier today to use an explicit 
AntPathMatcher to get the build working again. I don't think Ben will 
have any worries about requiring Spring 1.2 for the next release but it 
should be easy to accomodate either way.

Luke.

Juergen Hoeller wrote:
> Yes, there are essentially these two options: either require Spring 1.2 as
> of the next Acegi release (which should probably be called 0.9 then), or
> copy the old PathMatcher over. In the former case, Acegi should follow the
> new Spring pattern there: components that need path-matching functionality
> receive a PathMatcher implementation through dependency injection, using an
> AntPathMatcher as default.
> 
> BTW, it would be good to unify the codebases in the mid term, for example
> moving some of the generic Acegi utility stuff over to the main Spring
> codebase. IMO, we should do this for Acegi Security 1.0 at the latest, with
> Acegi concentrating on the actual security support only. In any case, I
> guess it's inevitable to depend on a specific Spring release level at some
> point.
> 
> Juergen
> 
> 


-- 
  Luke Taylor.                      Monkey Machine Ltd.
  PGP Key ID: 0x57E9523C            http://www.monkeymachine.ltd.uk