On Tue, Jan 5, 2021 at 1:27 PM Ed Merks <[email protected]> wrote: > I read the article, but what's not clear to me is how the > magically-created-and-repackaged-as-a-bundle Maven artifacts are > republished. I assume they must end up in a p2 repo to be installable > somewhere... Of course in terms of Eclipse Project using this cool > support, the question then is: how will the life cycles will work if such > things are magically created independently by different projects on demand > and also perhaps more significantly, how are they IP reviewed if they've > been pulled straight from some Maven repository somewhere? > Dash-licenses [1] contains maven plugin so IP can be verified on every build you produce if you want. Not easily achievable now due to [2] which shouldn't be too hard to fix.
[1] https://github.com/eclipse/dash-licenses [2] https://github.com/eclipse/dash-licenses/issues/45 > On 05.01.2021 08:48, Mickael Istria wrote: > > > 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/> > > _______________________________________________ > tycho-user mailing [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/tycho-user > > _______________________________________________ > pde-dev mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/pde-dev > -- Alexander Kurtakov Red Hat Eclipse Team
_______________________________________________ cross-project-issues-dev mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
