Re: [incubation] Humongous pre-req deps

["Saggi, Anubhav (GE Digital)" <anubhav.saggi@xxxxxx>]

We’re in a similar boat as Stephane in that the transitive close of our dependency tree weighs in at 230+ artifacts. Filing CQs for all of these is quite a painful process indeed and is eating up more of our time than is necessary. It’s also not scalable esp. if we have to update managed versions of artifacts that, in turn, transitively update the versions of hundreds of other artifacts for which we’ll have to file new CQs.

Is there an automated tool to submit CQs or at least submit them once in batch (including source archives)?

Thanks,
Anubhav

From: <incubation-bounces@xxxxxxxxxxx> on behalf of Stephane Epardaud <stef@xxxxxxxxxxx>
Reply-To: Discussions for new Eclipse projects <incubation@xxxxxxxxxxx>
Date: Tuesday, October 3, 2017 at 8:33 AM
To: "incubation@xxxxxxxxxxx" <incubation@xxxxxxxxxxx>
Subject: EXT: Re: [incubation] Humongous pre-req deps


OK, this sounds fantastic. Play Framework is exactly the same as IJ because it's the kind of framework that the users have to install by themselves, so the same reasoning and solution should apply and point to an "exempt pre-req".

This is really awesome news :)

Thanks!

On 03/10/17 17:25, Wayne Beaton wrote:
It sounds to me like IDEA is what we refer to as a "exempt pre-req" dependency. AFAICT, it's the sort of thing that the kind of user who will use the corresponding Eclipse Ceylon functionality (i.e. the plug-in) will install for themselves (and accept the license).

It's enough to just create a CQ for IDEA itself and, when the system asks you to attach source code, just comment that it's a "exempt pre-req". You don't have to capture the transitive closure of dependencies for an exempt pre-req.

Note that we do have a bug open<https://bugs.eclipse.org/bugs/show_bug.cgi?id=518318> to make the system stop asking for source code on a "works with" that I'll extend to include exempt pre-reqs as well.

There's more information in the Guidelines for the Review of Third Party Dependencies<http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf>. More of this information needs to be moved into the handbook.

Regarding Play Framework, I recommend that you contact emo-ip-team@xxxxxxxxxxx<mailto:emo-ip-team@xxxxxxxxxxx> and ask them how they recommend you proceed. They want to reduce the amount of effort required as much as you do.

HTH,

Wayne

On Tue, Oct 3, 2017 at 5:16 AM, Stephane Epardaud <stef@xxxxxxxxxxx<mailto:stef@xxxxxxxxxxx>> wrote:

Hi,

In the process of migrating Ceylon to Eclipse, I've made several dozens CQs, and I'm already quite fed up, because all of this is manual and repetitive. But I'm seeing the end, and I'm down to two huge deps, that are pre-reqs IMO, but I don't think I can make CQs for them:

- IntelliJ IDEA, because we have an IJ plugin, which quite obviously pre-reqs on IDEA, since it requires it to build and run, and uses several jars from it, which have who knows what runtime deps. I've made a CQ for IJ IDEA sources, which is a 50meg zip file, but I forgot IJ also has jar deps. 610 to be precise. I've no idea which transitive jars my plugin actually requires, but I'll venture that I probably can't know that easily.

- Play Framework 1.2.6, for a web application written for this framework. Again obvious pre-req since it's required to build and run. Same problem about dependencies not being obvious but the jar list is 61.

I am really supposed to make 671 CQs just for those two pre-reqs? I don't think I can, without it being a full-time job for months. And I don't think I want to, because there's no way I'd do that again when we upgrade our dep.

What possible solution do I have here?

Thanks.

_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx<mailto:incubation@xxxxxxxxxxx>
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation



--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation




_______________________________________________

incubation mailing list

incubation@xxxxxxxxxxx<mailto:incubation@xxxxxxxxxxx>

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/incubation