Christian, Out of curiosity, what cool things does PDE give you that you'd not want to switch? Is it to do with your osgi container? Karaf has excellent integration with mvn (via pax). With it you can pull bundles straight from your mvn repo straight into the running container. Couple this with 'features', its mechanism for defining groups of bundles and you have a really compelling platform.
There is no reason you couldn't get pax working with whatever container you are using, but you get it for free with karaf and it makes building and deploying bundles a snap. You've no doubt checked, but in case you've missed seeing them, there are a bunch of samples in the camel examples (and the features project under platform) that show how to build osgi bundles with maven. You can then run your eclipse plugin to attach the sources. Just a suggestion of course, but do check it out you might be pleasantly suprised. rgds, ste On Tue, May 18, 2010 at 11:46 AM, Christian Schneider <[email protected]> wrote: > Hi Stephen, > > for non osgi projects I also use maven and have no problem getting the > sources. Currently I do not use maven for my osgi projects as the ide > support is better when using the pde mode in eclipse. > The only problem is that the source code is not attached this way. > > Greetings > > Christian > > > Am 18.05.2010 18:19, schrieb Stephen Gargan: >> >> if you run the eclipse plugin with the following flag it will download >> the sources and attach them in the classpath. >> >> mvn eclipse:eclipse -DdownloadSources=true >> >> if you're in linux or use cygwin, add quick alias to 'me' and you >> never need worry about it again. >> >> alias me='mvn eclipse:eclipse -DdownloadSources=true' >> >> If you're so inclined you can download the javadoc too, but usually >> having the source is enough! >> >> Here are a few more mvn aliases that I regularly use, you might get >> some use out of them too. >> >> mci='mvn clean install' >> mcist='mvn clean install -Dmaven.test.skip=true' >> mdt='mvn dependency:tree' >> me='mvn eclipse:eclipse -DdownloadSources=true' >> mep='mvn help:effective-pom' >> mes='mvn help:effective-settings' >> mag='mvn archetype:generate >> >> -DarchetypeCatalog="internal,file:///opt/mf/repo/archetype-catalog.xml,http://cocoon.apache.org,http://download.java.net/maven/2,http://myfaces.apache.org,http://tapestry.formos.com/maven-repository,http://scala-tools.org,http://www.terracotta.org/download/reflector/maven2/"; >> ' >> >> ste >> >> >> On Tue, May 18, 2010 at 12:17 AM, Christian Schneider >> <[email protected]> wrote: >> >>> >>> Hi all, >>> >>> while trying to get camel running in osgi I would like to be able to >>> debug >>> through the source code in eclipse. When I am not using osgi I usually >>> leave >>> the task of attaching the source to maven which does a great job here. >>> For osgi I have set up a target platform where I copied the camel jars >>> and >>> also the source jars from the maven repo. The problem is though that the >>> source is not resolved and there is no setting to tell eclipse how to do >>> it. >>> The source for the eclipse bundles is resolved so I guess it has to do >>> with >>> the fact how the source is bundled. >>> >>> Is there any way to use the sources from maven in eclipse plugin >>> dependencies? If not then I think it would be great to setup the camel >>> build >>> in such a way that the source is bundled in a way that works in eclipse >>> plugin dependencies. Is this possible? >>> >>> Gereetings >>> >>> Christian >>> >>> -- >>> ---- >>> http://www.liquid-reality.de >>> >>> >>> >> >> > > -- > ---- > http://www.liquid-reality.de > >
