Hi Bertrand If I get you right, that means, that you do not compile in Eclipse. So you do not get errros and warnings in Eclipse. Does that mean you use Eclipse only as editor, or do I get things wrong? (I must admit, that I do not have deep knowledge of maven...) I do hesitate to use maven as central build tool, but would like to see errors and warnings in Eclipse, and Eclipse should also know the definitions for easy jumping in the code. Have you Bertrand - or someone else - tried another setup where at least compiling to classes is done in Eclipse?
best regards mike > > ...So what are the best pracices to develop an OSGi bundle > for Sling in Eclipse? > > How are you guys developing/testing bigger projects for Sling? > > (including packaging the jar with the correct manifest).... > > The way I do it might not be a best practice but that works for me: > > -Start by copying and adapting an existing Sling pom that > looks like what I need > -Generate the Eclipse project files using mvn eclipse:eclipse > -Disable the Java builder in the Eclipse projects > -Build and test from the command-line, using the Eclipse > remote debugger > -If adding dependencies to my poms, run mvn eclipse:eclipse again and > refresh the project in Eclipse > -Use the subclipse svn client for most things, back to the command > line for the really important stuff > > I know some people want things more integrated with their IDE, but as > I said the above works fine for me, and I'm almost never fighting with > the IDE.
