Thanks for your reply. I was messing around with the configuration to try and get it to work which is why I specified the alias.
However in the end I realised I was pulling in the com.springframework.security.2.0.4.A jars even though I wasn`t specifying them in my ivy.xml file.
It appears the org.springframework.flex ivy.xml on the SpringSource Enterprise bundle repo is wrong as I was using
to get the spring integration BlazeDS jars from the Spring repo and this was pulling in the spring security 2.0.4.A dependency.
<dependency org="org.springframework.flex" name="org.springframework.flex" rev="1.0.3.RELEASE"/>
I`ve added the following to include only the 3.0.2 spring security and exclude the 2.0.4.A jar
so this is no longer a issue and I get no exceptions when starting tomcat.
<dependency org="org.springframework.security" name="org.springframework.security.core" rev="3.0.2.RELEASE" />
<dependency org="org.springframework.security" name="org.springframework.security.web" rev="3.0.2.RELEASE" />
<dependency org="org.springframework.security" name="org.springframework.security.config" rev="3.0.2.RELEASE" />
<exclude org="org.springframework.security" module="org.springframework.security" />
But I guess the ivy.xml on spring repo needs to be fixed to not pull in the 2.0.4.A dependency