For those of you that have the m2eclipse plugin installed in eclipse I recommend upgrading to the latest version. Eugene and the folks at Sonatype have really picked up the pace of development on it. And have released 3 versions in the last couple of months. The update site has changed so you'll need to edit your existing one and set it to: http://m2eclipse.sonatype.org/update/
I don't know if it is ready to switch the concord eclipse development enviroment to relying on m2eclipse but it is definitely getting closer. Now would be a good time to try it, and find any issues we still have while trying to use it. This switch would mean the thirdparty-jars project would not be needed. And you wouldn't need to check out all the projects just test or develop a single project. Using it with subclipse also makes checking out projects a bit easier. I'm pretty sure it doesn't handle the working copying style that Stephen prefers, but the m2eclipse developers might be convinced to support it. Stephen's preference is to have his local working copy mirror the directory structure of the svn server. Eclipse likes to have a flat workspace. But is is possible to have your projects stored outside of the workspace folder so this way eclipse can support a nested or multilevel project directory structure. Typical maven projects are nested, so easily checking out the nested working copy would make sense to support. Scott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
