Hi Janandith, I use Eclipse only for editing and mostly for SVN commits and updates.
For SVN checkouts and Maven builds I revert to the command line. It is suffiently easy to use and allows for better control : (1) checkout in the terminal $ svn checkout (2) create Eclipse project descriptors $ mvn eclipse:clean eclipse:m2eclipse (3) Import the existing projects into the Eclipse workspace (4) Inside Eclipse I also use subclibse for per-project checkouts and updates (5) For maven integration, namely keeping the project descriptors in-sync with the maven project files, I use the m2eclipse plugin from http://m2eclipse.codehaus.org/ (note the latest revisions are found in the sonatype.org update site). To be able to checkout projects from SVN and create Eclipse project descriptors from the checked out pom.xml files you need an additional plugin which - if I remember correctly - is also available from the sonatype.org update site. Hope this helps. Regards Felix Am Sonntag, den 25.05.2008, 22:50 +0530 schrieb janandith jayawardena: > Hi all, > > So far I have been working with vim-editor and the terminal to go through > the source and do maven builds for sling. > > Instead of building manually I like to use the eclipse IDE. I would like to > use it to checkout latest source code and build the project. > > In trying to do so during the past few days I experienced the following > difficulties. > > 1 ) I've tried to use the subclipse pluggin for eclipse to checkout the code > from sling repository but it doesn't checkout the source. > > 2 ) To build using maven I installed the "mevenide.update-0.3.1" but I > cannot build using "Project -> Build project". > > I suspect that my configuration is wrong. > > could you please guide me on setting up eclipse to work with sling including > checking out and maven building. > > > I use "jdk-1.6" and "eclipse 3.3.2" is there a conflict between these two. > > > janandith.
