Hello Igor,
On Tue, 11 Nov 2008 14:42:35 -0500, "Igor Fedorenko"
<[EMAIL PROTECTED]> said:
> First, you can use PDE for all your IDE work (i.e. projects do not
> have maven nature and maven dependencies classpath container) and use
> Tycho to build these projects from command line "the maven way". This
> is how we develop m2e and I think it is a good approach if you develop
> eclipse plugins. Test code will have to move to separate projects,
> however.
Sounds like this will result in greater changes in the build process,
but I will have a look at Tycho in the next time.
> Then you can Maven both in IDE and on command line and only use PDE to
> launch OSGi runtime from IDE. I had one test project set up this way
> and it seemed to work. I think this is very close to your current
> project configuration, only you need to remove pde classpath container
> from .classpath (.project files have to have pde nature!). I was using
> Tycho to generate bundle manifest (for obvious reasons ;-) ) but I
> don't see why this would not work with felix/bnd plugin.
I have a manually created manifest: experiments in generating it with
bnd resulted in refresh-clean-marathons inside eclipse.
Now I removed the pde from classpath as you suggested and this seems to
work good. Workspace resolution can be enabled an the unittest
dependencies are resolved. Thank you for this hint!
regards,
Lars
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
