Adrian,
I don't know enough about Spring to be able to answer this question, to
be honest.
If you are interested to invest some time into this, it would be great
if you could help us understand "ideal" spring-eclipse-maven development
environment and workflow. I may be wrong, but my gut feeling is that we
are not too off, especially considering the work we are planning for
next few months. At least we should be able to tell what works and what
is missing and hopefully give some estimates when we plan to implement
the missing parts.
--
Regards,
Igor
PS: your name sounds familiar. did you by any chance work at brightspark
few years ago?
adrians wrote:
Hi,
I've been trying to see (by reading, so far) how close you can come today to
achieving a good command-line build as well as nice Eclipse integration when
working with OSGi and are targetting the Spring DM server. I've installed
the Spring tooling from http://www.springsource.org/dmserver and, things
work very smoothly as far as developing (web) bundles and deploying them to
DM Server from within Eclipse.
Of course I want headless builds as well. Up until now, I've been using
Maven and m2eclipse for the best of both worlds and I'd like to continue
using it in conjunction with Tycho. Can this combination of tools play
nicely with each other when it comes to the various natures/builders
involved and with the new dependency resolution needed for OSGi? What about
deployment to DM Server or some arbitrary OSGi platform? I don't mind
duplicated functionality (although I would hope Sonatype and SpringSource
can avoid this wasted effort) as long as the tools don't step on each
other's toes. I'd be willing to forgo some parts of the Spring tooling
functionality if similar features are available with Tycho.
Thanks in advance for any clarity and cheers for the great tools so far,
Adrian Sampaleanu
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
