Re: [incubation] Humongous pre-req deps

[<werner.keil@xxxxxxx>]

One can only try to imagine, how many CQs EE4J will trigger if Ceylon already caused 671 ;-O

 

From: Wayne Beaton
Sent: Tuesday, October 3, 2017 08:26
To: Discussions for new Eclipse projects
Subject: Re: [incubation] Humongous pre-req deps

 

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 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. More of this information needs to be moved into the handbook.

 

Regarding Play Framework, I recommend that you contact 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> 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
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