In general, if you are debugging, you only need to have the specific modules open in Eclipse whose functionality you are trying to debug. As Sling has a lot of modules, it's just going to slow things down to import everything in Eclipse.
Even if you are developing Sling (not just debugging it), your best bet (as Bertrand said) is to build the whole project on the command line and then open up just the projects you are working on in Eclipse. Personally, I tend to only have 3-5 Sling modules open at a time just to keep Eclipse happy. Justin On Apr 28, 2012, at 2:10 PM, Sabyasachi Mukherjee <[email protected]> wrote: > Hi , > > I am a newbie in Sling and want to work with it and contribute back to the > community . > But stuck in the beginning itself. > > I have run Sling standalone jar file . It worked well . > But to debug the sling project I tried to checkout it in Eclipse. > > I have checked it out from SVN and built it. > Firstly it was showing build error in the Sling Servlet API project . > I removed *<module>maven/archetypes/servlet</module> *from the main > pom.xml. > Then it was built well. > > After that I tried building again and I am getting build error in *Apache > Sling Installer Integration Tests* . > > I opened the org.apache.sling.installer.it. > FragmentInstallTest.txt file and found the issue . > > testInstallFragment > [equinox](org.apache.sling.installer.it.FragmentInstallTest) Time elapsed: > 26.264 sec <<< FAILURE! > java.lang.AssertionError: Test bundle 1.2 must be found after > waitForInstallerAction : Expected events=[ > BundleEvent osgi-installer-testbundle, version=1.2.0, state=1 > BundleEvent osgi-installer-testbundle, version=1.2.0, state=2 > > > > I did not find any documentation through which I can understand the Sling > completely . So I thought of debugging it. > > Can I get any help from you regarding this ? > > > Thanks in advance . > > Sabya
