In fact tycho is bit strange since it requires a special Maven installation, does not support multiple OSGi repositories to complete target platform. What I need is given a set of OSGI repositories (eclipse installations), during the build, bundles are resolved, dependencies updated, and only by adding this in my POM :
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>fr.fabdouglas.maven</groupId> <artifactId>plugin-pde-adapter-test</artifactId> <version>0.0.1-SNAPSHOT</version> <build> <plugins> <plugin> <groupId>fr.fabdouglas.maven</groupId> <artifactId>plugin-pde-adapter</artifactId> <version>1.0</version> <configuration> <skipm2e>false</skipm2e> <osgiRepositories> <param>C:/java/RSM/SDP70Shared</param> <param>C:/java/RSM/SDP70</param> <param>C:/java/RSM/eclipseSTD/eclipse</param> </osgiRepositories> </configuration> <executions> <execution> <id>update-resources</id> <phase>generate-resources</phase> <goals> <goal>update-resources</goal> </goals> </execution> <execution> <id>update-dependencies</id> <phase>process-resources</phase> <goals> <goal>update-dependencies</goal> </goals> </execution> </executions> </plugin> <plugins> <build> </project> No additional setup, i run : mvn package Right bundles are resolved, no compilation error, and I get a jar bundle exactly same as the one I get from Eclipse/Export. POM is untouched, and I can run this everywhere Hudson/Continuum providing a URL based target platform instead of file system. The way OSGi bundle are build is more than slightly different from the one of Sonatype Tycho. On Thu, Aug 6, 2009 at 7:22 AM, nicolas de loof<[email protected]> wrote: > How does this relate to tycho ? AFAIK this one is allready designed to build > OSGi/PDE projects using Maven. > > 2009/8/5 [email protected] <[email protected]> >> >> Hi, >> I've just developed a plugin able to dynamically update POM dependencies >> according to the OSGi configuration: >> Reads OSGi manifest, resolves dependant bundles (transitive job) and >> update resources reading build.properties. >> >> Why a new Eclipse/Maven plugin? >> >> First, it does not replace M2E/Q4E plugins. They work together. >> OSGi directory structure does not match with the Maven structure, so we >> need an adapter able to resolve maven dependencies for each required OSGi >> bundle. >> The main goal is to be able to run the mvn command with a {Eclipse >> RCP/OSGi bundle/PDE project} POM containing only reference to this plugin >> configured with a/several OSGI runtime locations information. >> >> The plugin is triggered in the generate-resources and process-resources >> phases and is able to prevent interferences with M2E/Q4E plugins. >> It works well in Eclipse+M2E plugin, and also with command line. I need to >> do some to test with Q4E plugin, and to add version range feature. >> >> Questions: >> Are some people interested to ? >> How can I submit this plugin to Codehaus? >> >> Fabrice Daugan >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
