Hi, I tried the following steps:
1. mvn clean install 2. mvn eclipse:eclipse 3. import all projects as existing projects 4 set a new build classpath variable M2_REPO to my local maven 2 repo, e.g. /Users/linsun/.m2/repository I think I am down to 5 errors in my eclipse 3.5 which is essentially one (not really important) error that complains about aries-blueprint-core is missing required source folder - /Users/linsun/aries/blueprint/blueprint-api/src/main/resources/org/osgi/service/blueprint, because the only file in this folder is a xsd file. If I comment out this line in my .classpath file of aries-blueprint-core, all my 5 errors gone - <!-- <classpathentry kind="src" path="/Users/linsun/aries/blueprint/blueprint-api/src/main/resources/org/osgi/service/blueprint" including="blueprint.xsd" excluding="**/*.java"/> --> HTH Lin On Sun, Oct 18, 2009 at 4:28 PM, zoe <[email protected]> wrote: > Valentin Mahrwald wrote: >> >> 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? > > Hi Valentin > > It sounds very similar to the problems I saw and eventually managed to fix. > > The interproject dependencies don't work because the source paths are > screwed up. If you look at the projects they are called: > > src.java.org.something.or.other > > They should be: > > org.something.or.other > > To fix this you need to delete the source path for each project and replace > it with the right source path. Right click of the project, take build path, > configure build path. Select the source tab and delete the incorrect source > path. Then click add source path, this screenshot shows selecting the right > source path: http://imagebin.ca/view/Tr_DKr.html > > After you have done this for all the projects that are wrong (it's not all > of them) you will need to add the right JRE library for all of them as well. > Some of mine had no JRE library and some had picked up a JRE 1.4 library. > > I hope this makes sense, it's hard to describe Eclipse screens :-S >> >> 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 >> >> > >
