as explained in https://issues.sonatype.org/browse/TYCHO-335Tycho can resolve bundle references from MANIFEST.MF etc in local repositories and of course from P2 repos, but not in remote Maven repositories. The mentioned work around on the issue using an “orbit” update sites works only for builds that deploy and use the updatesite consistently. Local builds can produce inconsistent results.

Of course I could use “<pomDependencies>consider</pomDependencies>”, but this requires to repeat all bundle references in the POM, which is ugly and error prone.

What’s about the following proposal:

Tycho could resolve bundle references from Maven repositories, if it could create a GAV. As a BundleSymbolicName and usually also a version is available , the only missing part is a GroupID. For this the POM could contain a list of group IDs that the resolver should search, e.g.

<plugin>

<groupId>${tycho-groupid}</groupId>

<artifactId>target-platform-configuration</artifactId>

<version>${tycho-version}</version>

<configuration>

<resolver>p2</resolver>

<groupIds>

<groupId>com.mycompany.product1</groupId>

<groupId>com.mycompany2.product2</groupId>

</groupIds>

</configuration>

</plugin>

I’m not sure if also a list of versions need to be provided if the bundle references does not contain any version or a range that is not strict enough.

I’m aware that this proposal would not help for package references, but there is a huge benefit for projects that use only bundle references.