Hi! I was following the discussion between David and Igor in http://dev.eclipse.org/mhonarc/lists/m2e-users/msg01950.html, as I thought I have a pretty similar situation here.
We have a server- and a client-part of our product. I want to aggregate those projects of the server-part which are ALSO needed on the client-side into ONE bundle, to be able to identify this as THE INTERFACE of our server from the client's perspective, rather than having a bunch of bundles together being 'the interface'. By aggregating I mean to let maven aggregate the packages of different other projects into this 'artificial' bundle and still be able to see them with workspace-resolution from PDE-built projects. This did not work with the currently released versions of eclipse and m2e, but it worked fine with the versions mentioned in http://dev.eclipse.org/mhonarc/lists/m2e-users/msg01950.html. So just to give everybody hope, who is waiting for this to work: It worked with the current milestones of PDE and m2e when the dependencies were declared to be embedded! Now my question: Originally we integrated our interface-project's classes by inlining them into the artificial interface-bundle by simply working with <Export-Package>. But also after upgrading to the mentioned versions, inlined (or i should better say "to be inlined at package-time") classes can not be seen by the eclipse build-system. Only the content of projects, defined to be embedded with <Embed-Dependency> is seen by the eclipse build-system. Is there any known status of the capabilities of the m2e-bundle-plugin-integration concerning inlined dependencies? Regards, Markward PS: This whole m2e/tycho thing is great work and it is a pleasure to see how things constantly improve even more over the time! Thanks to all contributors!
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
