Re: [pde-build-dev] Eclipse bundles on the Maven repository

["Wendell Beckwith" <wbeckwith@xxxxxxxxx>]

For repository resolving I'm thinking of something like

<plugin>
    <groupId>org.eclipse.pde.maven.plugins</groupId>
    <artifactId>maven-eclipsecompiler-plugin</artifactId>
    <configuration>
        <!-- ... other config parameters here ... -->
          ...
        <!-- The repository group to compile against. -->
        <eclipseTarget>org.eclipse.platform:org.eclipse.platform:3.2
</eclipseTarget>
    </configuration>
</plugin>

The <eclipseTarget> element in the format of "<groupId>:<artifactId>:<version>" would map to the url 
http://www.mycompany.com/maven2/org/eclipse/platform/org.eclipse.platform/3.2/org.eclipse.platform-3.2.repo-group.  The contents of the group file would list the members of the group which can be found elsewhere in the repository.  Maven already supports loading from multiple repos so if a dependency isn't met in one repo it will try the others until met or an exception is thrown.

<repositoryGroup>
    <dependency>
        <groupId>org.eclipse.core.runtime</groupId>
        <artifactId>org.eclipse.core.runtime</artifactId>
        <version>
3.2</version>
    </dependency>
    ...
    <dependency>
        <groupId>org.eclipse.core.resources</groupId>
        <artifactId>org.eclipse.core.resources</artifactId>
        <version>3.2.1</version>
    </dependency>
</repositoryGroup>

Additional information such as the exports from an artifact could be added to each dependency in a repositoryGroup or to their respective poms.  This would allow the compiler to know who provides what packages without taking the time to open the jars.

Wb