Eugene, Thanks for the write-up. It should help a lot in getting started looking at the code. I ran into a couple of authentication prompts when importing the team project set (which I had to use http instead of https to fetch, or it too prompts for authentication)...
When prompted for CVS authentication for :pserver:dev.eclipse.org:/cvsroot/tools I used anonymous/anonymous. When prompted for SVN authentication for http://subclipse.tigris.org I used guest/<no password>. After import I needed to run "mvn compile" on org.maven.ide.components.pom to do the xmlbeans stuff. I also had to change the version in the org.maven.ide.eclipse.parent pom.xml back to 0.9.2-SNAPSHOT, since that seems to be what everything else was expecting (or at least without that the org.maven.ide.components.pom project was not resolving dependencies correctly - it seems that some of the other projects have a mix of versions for the parent POM). After that I get 0 errors in eclipse. Thanks, Mark On Tue, Apr 22, 2008 at 7:34 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > > I put some basic documentation on how to setup Eclipse workspace for > working with m2eclipse code. > > http://docs.codehaus.org/display/M2ECLIPSE/Configuring+Development+Environment > > It may see bit lengthy, but things actually quite simple. You can import > the following Eclipse Team Project Sets (PSF) using "File / Import... / Team > / Team Project Set" wizard and it would bring all required projects into > your Eclipse workspace (this PSF is based on Subclipse). > > https://svn.sonatype.org/m2eclipse/trunk/org.maven.ide.eclipse.parent/m2eclipse-all.psf > > Once you get all projects, you should be able to run m2eclipse in > self-hosted mode. Open org.maven.ide.eclipse/plugin.xml with PDE's Plug-in > manifest editor and then click "Launch an Eclipse application" link on the > Overview page. You can also use main menu "Run / Run configurations..." to > create new launch configuration using "Eclipse Application" cofiguration > type. There you can also select JRE used to run Eclipse and what plugins > should be included at runtime (use "all workspace and enabled target > plug-ins, or select them individually and use "Validate Plug-ins" action to > verify if selected configuration is correct). > > Here are few last tips for contributing patches. > http://docs.codehaus.org/display/M2ECLIPSE/Contributing+Patches > > Happy coding > > Eugene > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
