Hm, I probably did something wrong. I had a fair number of random
build path problems after generating and importing the eclipse
projects. Such as most of the inter-project dependencies did not work
and the blueprint-itest also had problems with the library org/apache/
felix/org.osgi.foundation/1.2.0, which overwrote standard JRE classes.
Is that expected?
On 17 Oct 2009, at 15:24, Guillaume Nodet wrote:
Have you tried with running "mvn eclipse:eclipse" and importing the
created project ?
On Sat, Oct 17, 2009 at 13:02, zoe <[email protected]>
wrote:
What are the problems you're seeing? I've got it working in eclipse
3.4, m2eclipse 0.9.8
Downloaded 3.4 and finally have a working environment. I still had
to:
(1) Fix the source paths for most of the projects.
(2) Add a JRE system library to the build path for most projects
With plenty of 'cleaning, closing-opening, restarting' between each
step I
am just down to warnings now.
I can't help feeling there must be a better way than fixing each
project on
it's own.
Zoe
Cheers,
Jeremy
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com