I've been using Intellij 7's maven support to generate the project files then switching back to Intellij 6 to actually use them (still too many bugs in 7). Don't mind what happens with the eclipse files as I'm barely aware they exist :).
On the commons logging front, we should probably stick with whatever the main Spring dependency is. I doubt if it matters that much though. Personally I'd scrap it and switch to slf4j to reduce the number of <exclude> sections in my pom files :). Does anyone know if you can set global exclusions with maven 2? Scott Battaglia wrote: > Ray Krueger wrote: >> Ooh, here's an idea! >> Have Maven generate a new .classpath file and check that in. >> > The plugin nicely doesn't generate one for the parent POM. Otherwise we > wouldn't still be having this discussion ;-) > The way to handle the flat structure is extremely kludgy: > http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html (its > on the bottom). > > The easiest thing for me to do now is just update the .classpath file > locally and not check it in. I'll let the more core team figure out the > whole Eclipse project issue and then just update to whatever you guys > decide ;-) > > On a completely different side note, in updating the .classpath file, > we're depending on commons-logging 1.0.4. Should we upgrade to 1.1? > > -Scott -- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk ------------------------------------------------------------------------- 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
