Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] [eclipse-ide-wg] Fwd: [cross-project-issues-dev] IMHO serious issues in the Eclipse Java IDE 2021-06 M3

Mickael,

Let me start by rejecting your attempt of framing Orbit benefits by using "hypothetical" as well as denying all the successful, fruitful and helpful collaboration in Orbit which happened in the past and still happens today.

It is ok if you don't want to see those benefits. 

My intend is to raise awareness of side effects of those actions and (hopefully) spark an open discussion in the Eclipse PMC and WG. Needless to say, I would like to see it being reversed and the Eclipse project return to collaborating with the community and other projects in the Simultaneous Release in Orbit. 

-Gunnar

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


> On Jun 2, 2021, at 17:06, Mickael Istria <mistria@xxxxxxxxxx> wrote:
> 
> Hi Gunnar,
> 
> I'm aware of the hypothetical benefits of Orbit, and like some other people, I'm not certain about how profitable they happen to be in real life.
> So my question still stands and is important as it will fundamentally influence the future of the Platform/Orbit relationship IMO: how would using Orbit to publish slf4j 2.0 have prevented this issue in m2e? If there is some compelling positive answer to that, then it will seem more interesting for Platform to reconsider an Orbit first strategy; if there is none, then it will confirm that the current approach of bypassing Orbit was a good one.
> 
> Cheers,
> _______________________________________________
> 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



Back to the top