[EMAIL PROTECTED] wrote:
Hi Igor,
here's another suggestion for providing the missing groupId in case of
packageing is eclipse-plugin:
Simply use the POM's groupId for any dependency of type eclipse-plugin with
missing groupId.
Since the dependencies do come from the MANIFEST.MF, they don't have a
groupId
and are implicitly of type eclipse-plugin.
What do you think?
-Max
Import-Package cannot be mapped into maven coordinates. This is why we
have two phase dependency resolution. As I explained in another reply,
tycho first resolves build target platform to determine set of features
and bundles to use by "real" OSGi resolver.
It is theoretically possible to instrument maven repository with
Eclipse/OSGi metadata, effectively turning maven repository into p2
repository. We may add this functionality to our Nexus repository
manager some time in the future, but I can't tell when and in what form
this is going to happen. You may want to create enhancement request in
Nexus JIRA [1] if you are interested in this functionality.
[1] http://issues.sonatype.org/browse/NEXUS
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
