Re: Jenkins Jobs of Ivy/IvyDE

> Dropins (or "drops" as they're called in the distributions) is what IvyDE > builds were based on all the time. I am still confounded why it worked > before and stopped working now. Yet, reading the documentation I became > convinced that the dropins must be unpacked in another location. So I

Re: Jenkins Jobs of Ivy/IvyDE

2017-06-26 13:54 GMT+02:00 Nicolas Lalevée : > > > Le 26 juin 2017 à 07:46, Gintautas Grigelionis > a écrit : > > > > If I understand the process correctly, Jenkins executes "ant > > prepare-jenkins" first, which does not work locally any

Re: Jenkins Jobs of Ivy/IvyDE

> Le 26 juin 2017 à 07:46, Gintautas Grigelionis a > écrit : > > If I understand the process correctly, Jenkins executes "ant > prepare-jenkins" first, which does not work locally any more, because the > property used to figure out where to get Ivy jar from is set to

Re: [1/5] ant-ivy git commit: set copyright to 2017

> Le 26 juin 2017 à 08:15, Matèrne, Jan (RZF, Ref 410) > a écrit : > > Would it be better to insert the actual year to the generation process? It can certainly be done. There is some ruby code involved, so I guess this is doable. > If I remember right Stefan had

AW: [1/5] ant-ivy git commit: set copyright to 2017

Would it be better to insert the actual year to the generation process? If I remember right Stefan had changed the site templates regarding the license link (.../ instead of .../LICENSE-2.0.txt). Should we use that link here too? cheers Jan -Ursprüngliche Nachricht- Von: