I use a process which is in between these 2. I checkout the sling source using svn on the command line. I do New -> Java Project -> existing -> Point to the existing source Then I use the m2 plugin for eclispe to enable dependency management (usually already done) and nested modules (usually not done). Then I have the entire source ready to go in project and as long as the poms are valid and the project is building this seems to work every time.
-AZ On Fri, Apr 17, 2009 at 8:18 AM, Carsten Ziegeler <[email protected]> wrote: > Mike Müller wrote: >> Hi Carsten >> >>> Now, just as an additional comment, my Eclipse setup looks >>> different: I >>> don't use the m2 plugins and have one single big project >>> containing all >>> modules - so as always there are different ways to setup the IDE but I >>> think the new wiki page is a great start! >> >> I would like to add your alternative configuration as well. >> Would be good if users can choose a configuration which suits them >> best. Can you give me some hints how your setup looks. I would then >> include it on the new wiki page. > > Ok, sure :) > > I checkout the whole trunk as a single project into Eclipse (using 3.4.2 > and the subclipse plugin). Then I'll manually :) add all src/main/java > and src/test/java folders of the bundles to my project and manually add > all required libraries. Debugging works like in your scenario. > > Carsten >> >> best regards >> Mike >> > > > -- > Carsten Ziegeler > [email protected] > -- Aaron Zeckoski ([email protected]) Senior Research Engineer - CARET - Cambridge University [http://bugs.sakaiproject.org/confluence/display/~aaronz/] Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
