Re: [eclipse-pmc] IMHO serious issues in the Eclipse Java IDE 2021-06 M3

["Sravan K Lakkimsetti" <sravankumarl@xxxxxxxxxx>]

Hi Gunnar,

There is broader issue here. We need to have a discussion on who is responsible for adding dependencies to Orbit.
In the current scenario slf4j.api v2 came with Jetty. At platform we are consuming Jetty and using it for our help system.

I would like to know what are your thoughts on these

1. Should we validate all the dependencies whether they exist in Orbit for Eclipse projects like Jetty, egit, jgit etc and how should we do it?
2. With https://www.eclipse.org/lists/orbit-dev/msg05359.html what should be the way forward for in maintaining Orbit?
3. With platform team(foundation level project for Simrel) also shrinking what are you thoughts on supporting future releases?
   

In my opinion  these are some of the things we need to have discussion here.

Thanks and Regards,
Sravan 

Sravan Kumar Lakkimsetti
IBM India Pvt Ltd,
Embassy Golf Links Business Park, D Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India

Gunnar Wagenknecht ---02-06-2021 17:17:39---> On Jun 2, 2021, at 11:18, Mickael Istria <mistria@xxxxxxxxxx> wrote: > About Orbit or not, I fail

From:        Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
To:        Discussions on Eclipse IDE Working Group <eclipse-ide-wg@xxxxxxxxxxx>
Cc:        eclipse-pmc@xxxxxxxxxxx
Date:        02-06-2021 17:17
Subject:        [EXTERNAL] Re: [eclipse-ide-wg] [eclipse-pmc] Fwd: [cross-project-issues-dev] IMHO serious issues in the Eclipse Java IDE 2021-06 M3
Sent by:        "eclipse-ide-wg" <eclipse-ide-wg-bounces@xxxxxxxxxxx>

---

> On Jun 2, 2021, at 11:18, Mickael Istria <mistria@xxxxxxxxxx> wrote:
> About Orbit or not, I fail at seeing what would that change: if slf4j 2.0 -which is a requirement- were in Orbit, how would that have prevented this issue in m2e from happening?

You need to look beyond the technical issue at hand. 

The use of Orbit typically serves the community at large by:
1. sharing work that you have already done
2. raising visibility/awareness of upcoming changes
3. improving quality through collaboration

There is a dedicated set logging related bundles in Orbit:
https://git.eclipse.org/c/orbit/orbit-recipes.git/tree/logging

It does provide customized metadata for some bundles, which have been evolved over time through collaboration to avoid potentially issues and improve the quality. Updating those bundles/providing new versions typically happens through collaboration. 

By doing everything in your own you are missing an opportunity for collaboration, avoiding mistakes and benefiting from the experience from others. 

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/ 



_______________________________________________
eclipse-ide-wg mailing list
eclipse-ide-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-ide-wg