I think the .classpath files should be removed. They are doomed to be stale. The project is now built with maven2 completely. Maven can create the .classpath files as needed.
Executing "mvn eclipse:eclipse" from the project root will create everything needed. On 9/10/07, Scott Battaglia <[EMAIL PROTECTED]> wrote: > I'm doing some work on some of the JIRA issues assigned to me (finally > getting a chance) and I checked out the project and noticed that the > .classpath was referring to Spring 1.2.9 while the pom refers to 2.0.6. > Anyone have any issues if I update the .classpath file to reflect the > latest Spring version? > > Thanks > -Scott > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Home: http://acegisecurity.org > Acegisecurity-developer mailing list > Acegisecurity-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
