If you're not using Maven 2.0.9, try using that. They appear to have changed some of the ways that they resolve dependencies and therefore the way a pom dependencies are defined appears to freak out older versions.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Fri, Aug 15, 2008 at 11:45 AM, Sandor Nemeth < [EMAIL PROTECTED]> wrote: > Hi again, > > I faced a new problem here. I thought I just simply make a new build with > 3.3 sources, with the same config I built 3.2.1.1, but it looks like some > dependencies are wrong. I took a look at the pom.xml files, but > <spring-version> shows me the correct 2.5.5 version. But M2 downloads > spring-core v2.0.7 and spring-beans v2.0.7. > > So there are some missing classes appearing at deploy: > org.springframework.beans.PropertyAccessorFactory > org.springframework.core.SmartClassLoader > > Did I miss something at the configuration? > > I could download the correct jars from the m2 repository ( I'll give it a > try, and I think it will work with the v2.5.5 jars) but I think you should > be aware of it, if others will experience this problem. > > Regards, > Sandor Nemeth > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
