HI Stuart, Thanks for the reply! I'm not sure how you imported a maven hierarchical project to Eclipse? I usually do Import-->Maven -->Existing Maven Projects!
Do you see the parent project and the child bundle projects in Eclipse by Generic Import? Can you please let me know the exact steps you followed? Thanks Matt On Mon, Aug 1, 2011 at 6:33 PM, Stuart McCulloch <[email protected]> wrote: > On 1 Aug 2011, at 23:38, Matt Madhavan wrote: > > Hello, > I have posted this issue at least couple of before. > > Anytime when we do a Import maven projects, all the classpath entries are > wiped out and the project becomes a JDK 1.4 (both in eclipse library setting > and eclipse compiler setting). > > Its easy to reproduce. > > *1. Create an OSGi project using :* > *mvn org.ops4j:maven-pax-plugin:create-project > -DgroupId=com.pax.jdkversiontest -DartifactId=com.pax.jdkversiontest > -Dversion=1.0.0* > *cd com.hcsc.ccsp.bd.jdkversiontest* > * > * > *2. update the parent pom.xml to add maven-compiler-plugin* > <build> > <plugins> > * <plugin>* > * <groupId>org.apache.maven.plugins</groupId>* > * <artifactId>maven-compiler-plugin</artifactId>* > * <version>2.3.1</version>* > * <configuration>* > * <source>1.6</source>* > * <target>1.6</target>* > * </configuration>* > * </plugin>* > <plugin> > <groupId>org.ops4j</groupId> > <artifactId>maven-pax-plugin</artifactId> > <version>1.5</version> > </plugin> > </plugins> > </build> > > *3. Create a bundle project:* > *mvn pax:create-bundle -Dpackage=com.pax.jdkversiontest.bundle1 > -Dversion=1.0.0* > * > * > *4.import the projects to eclipse:* > > 5. Check the JDc version of the bundle project - Its 1.4 > > Even if you update the project using mvn pax:eclipse check it into CVS and > re-import in a fresh workspace all the claapath(*.classpth*) entries are > wiped out and the JDK version becomes 1.4. > > Its really excruciating and starting to appear that the whole thing might > be stopped because of this issue becoming a show stopper! > > Any ideas please. Its so easy to reproduce also > > > unfortunately I can't reproduce it here - if I re-generate the Eclipse > project files using: > > mvn pax:clean pax:eclipse > > and import the project using "Import... -> General -> Existing projects > into workspace" then the compiler version is set to 1.6 as expected > > the only thing I can suggest is that you could try moving this line: > > <extensions>true</extensions> > > from the maven-pax-plugin section in "poms/pom.xml" down to > the maven-bundle-plugin, in case the custom lifecycle is affecting the > import > > Thanks in advance! > > Matt > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > >
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
