Thanks for all this very powerful and interesting work Christian! I think it's really a good way forward and a good opportunity to progressively replace Orbit by a more "build native" approach that will make adoption of Maven artifacts by Eclipse projects much easier and faster than the current process with Orbit.
On Tue, Jan 5, 2021 at 7:57 AM Ed Willink <[email protected]> wrote: > for my (small number of) users the problem is the other way round. How to > make Eclipse standalone project releases easily consumable by Maven. > It's indeed a different problem and requires different solution. My current impression as I deal more and more with things like Language Servers and other stuff that are not purely Eclipse Platfrom artifacts but then gets consumed in an Eclipse IDE is that if your project also targets plain Java and non-Eclipse Platform deployments, then it's better to just make it a plain Java project (ie stop using MANIFEST-first and PDE to develop it; do plain Java, Maven, BND and so on); and then consume those artifacts in your Eclipse Platform integration using the strategies described by Christian in his blog post. Consuming Maven jars in Eclipse Platform is a much better (simpler) handled problem than consuming OSGi artifacts in plain Java. -- Mickael Istria Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________ cross-project-issues-dev mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
