Re: [cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

2018-06-12 Thread Scott Lewis 

WRT ECF:

For Photon, the Platform folks chose to stick with the Oxygen versions 
of httpclient/httpcomponents (4.5.2/4.4.6).  One reason was that the new 
Orbit bundles were added fairly late in the release cycle...leaving 
little time...and no milestone releases...for thorough testing of the 
newer versions.


Scott


On 6/12/2018 3:10 PM, Carsten Reckord wrote:

org.eclipse.jgit.http.apache is an optional bundle which is not used by EGit.
It's used in JGit by org.eclipse.jgit.lfs.server (supports implementation of a 
git
lfs server)
and org.eclipse.jgit.pgm (jgit command line client).

Yes, but it's in the simrel repository and it pulls in the second HttpClient 
version.

Since that version has a higher qualifier than the one bundled with ECF, it 
gets pulled in by installing anything that has a dependency on HttpClient with 
a version range. So it also ends up in all the packages (while the other 
version is brought in, because the ECF feature contains the exact version).
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

2018-06-12 Thread Carsten Reckord 
> org.eclipse.jgit.http.apache is an optional bundle which is not used by EGit.
> It's used in JGit by org.eclipse.jgit.lfs.server (supports implementation of 
> a git
> lfs server)
> and org.eclipse.jgit.pgm (jgit command line client).

Yes, but it's in the simrel repository and it pulls in the second HttpClient 
version. 

Since that version has a higher qualifier than the one bundled with ECF, it 
gets pulled in by installing anything that has a dependency on HttpClient with 
a version range. So it also ends up in all the packages (while the other 
version is brought in, because the ECF feature contains the exact version).
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

2018-06-12 Thread Carsten Reckord 
> I'm not sure yet if this is the cause of my bug in MPC, but in the past, these
> kind of version mixups have always been problematic.

I've tested the MPC bug without the duplicate HttpClient versions by installing 
MPC into an Eclipse SDK, and the error is gone. So I guess I can confirm that 
it's caused by wiring issues due to the duplicate version. I'm not sure what 
those wiring issues are yet; "diag" in the OSGi console thinks that everything 
is fine, and I can't see any weird wiring going on...
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

2018-06-12 Thread Matthias Sohn 
On Tue, Jun 12, 2018 at 11:46 PM Carsten Reckord  wrote:

> Hey everybody,
>
>
>
> while diagnosing a problem with reporting install errors in the
> Marketplace Client (https://bugs.eclipse.org/bugs/show_bug.cgi?id=535821),
> I noticed that since RC3 we have two versions of HttpClient 4.5.2 in the
> Simrel repository.
>
>
>
> I’m not sure yet if this is the cause of my bug in MPC, but in the past,
> these kind of version mixups have always been problematic.
>
>
>
> I’ve dug around a bit (for details, see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=535821), and the two
> versions are contributed by the Platform
> (org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925) and by JGit
> (org.apache.httpcomponents.httpclient_4.5.2.v20180410-1551 – this one is
> new in RC3). The newer HttpClient version was introduced in Orbit
> I20180417184143 to make it safely co-exist with commons.logging 1.2 and
> commons.codec 1.10, neither of which are currently found in the Simrel
> repository.
>
>
>
> While the version contributed by JGit is the current one from the Orbit
> Photon repository, I think at this point the easiest and safest thing to do
> would be for JGit to go back to the old version to get a consistent state
> of the Simrel repo again. The alternative would be to update ECF with the
> new version, respin the platform, and get the Mylyn SDK to use the new
> version as well.
>
>
>
> What do you think?
>
>
>
> Kind regards,
>
> Carsten Reckord
>

org.eclipse.jgit.http.apache is an optional bundle which is not used by
EGit.
It's used in JGit by org.eclipse.jgit.lfs.server (supports implementation
of a git lfs server)
and org.eclipse.jgit.pgm (jgit command line client).

-Matthias
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

2018-06-12 Thread Carsten Reckord 
Hey everybody,

while diagnosing a problem with reporting install errors in the Marketplace 
Client (https://bugs.eclipse.org/bugs/show_bug.cgi?id=535821), I noticed that 
since RC3 we have two versions of HttpClient 4.5.2 in the Simrel repository.

I'm not sure yet if this is the cause of my bug in MPC, but in the past, these 
kind of version mixups have always been problematic.

I've dug around a bit (for details, see 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=535821), and the two versions are 
contributed by the Platform 
(org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925) and by JGit 
(org.apache.httpcomponents.httpclient_4.5.2.v20180410-1551 - this one is new in 
RC3). The newer HttpClient version was introduced in Orbit I20180417184143 to 
make it safely co-exist with commons.logging 1.2 and commons.codec 1.10, 
neither of which are currently found in the Simrel repository.

While the version contributed by JGit is the current one from the Orbit Photon 
repository, I think at this point the easiest and safest thing to do would be 
for JGit to go back to the old version to get a consistent state of the Simrel 
repo again. The alternative would be to update ECF with the new version, respin 
the platform, and get the Mylyn SDK to use the new version as well.

What do you think?

Kind regards,
Carsten Reckord

--
+49 (0)69 2475666-33 | 
reck...@yatta.de | 
www.yatta.de
Lead Software Architect & co-founder

Yatta Solutions GmbH c/o WeWork · Neue Rothofstraße 13-19 · 60313 Frankfurt 
a.M. (Germany)
Registered Seat: AG Kassel, HRB 14720 · VAT-ID DE263191529 · Managing Director 
Johannes Jacop

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Disk usage report for HIPP/JIPPs

2018-06-12 Thread genie 
Compiled 2018-06-12-13:30:02

Projects exceeding 80G of disk space on HIPP/JIPPs:
===
819G /jobs/genie.packaging
184G /jobs/genie.capella
162G /jobs/genie.kitalpha
127G /jobs/genie.openj9
86G /jobs/genie.platform
86G /jobs/genie.osee
86G /jobs/genie.app4mc
84G /jobs/genie.cdt
82G /jobs/genie.ice
===

If you find your project's name in the above list, please check
your Hudson/Jenkins configuration and try to lower the disk usage.

You can find more information about CI best practices and disk usage
here: https://wiki.eclipse.org/CI_best_practices#Disk_usage.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Latest TM.RSE and TM.Terminal builds have been published, composited, and contributed to Photon Simrel. (was Re: [cdt-dev] [tm-dev] TM Terminal and RSE releases for Photon (

2018-06-12 Thread Nick Boldt 
Latest TM.RSE and TM.Terminal builds have been published, composited, and
contributed to Photon Simrel.

---

Latest RSE:

* http://download.eclipse.org/tm/updates/3.7.100/repository/?d
* http://download.eclipse.org/tm/updates/3.7.100/rse-repository-3.7.100.zip

Latest Terminal:

* http://download.eclipse.org/tm/terminal/updates/4.4milestones/20180611/?d

*(NEW!) *Composite Site:

http://download.eclipse.org/tm/repository/photon/?d

*(This currently includes 3 Terminal milestones and 1 RSE milestone.
Perhaps it should only include the two RC4/Final builds?)*

*(NEW!) *Releng jobs to orchestrate copying from nightly / snapshot to
stable URLs, then create the composite site:

* https://ci.eclipse.org/tm/job/TM-Publish/
* https://ci.eclipse.org/tm/job/TM-Publish-Repo/

Update to Photon Simrel:

https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=d3065868ee6eac9b7adc8fe42ea6ae5cc10e1cb6

Cheers,

Nick

On Tue, Jun 12, 2018 at 5:18 AM, Jonah Graham 
wrote:

> Answers inline.
>
> On Mon, 11 Jun 2018 at 23:51, Nick Boldt  wrote:
>
>> After more digging it seems that the TM.terminal bits built from master
>> [1], published to the dev/nightly site [2], are built against Eclipse Mars
>> [3], not Photon.
>>
>> I don't think this is wise, but I bet there's a technical reason (like
>> guaranteeing backward compatibility for JDK 7?) so I'm not quite ready to
>> just change this blindly. *WDYT?*
>>
>
>> [1] https://ci.eclipse.org/tm/view/terminal/job/terminal-master/
>> [2] http://download.eclipse.org/tm/terminal/builds/development/nightly/
>> [3] http://git.eclipse.org/c/tm/org.eclipse.tm.terminal.
>> git/tree/admin/pom-config.xml#n73
>>
>> But, if we want to use the Photon-built bits in the TM or CDT
>> contribution to the Simrel, I've added a new deployment step to the
>> 4.8-based job [4], which will push bits here [5].
>>
>> [4] https://ci.eclipse.org/tm/view/terminal/job/terminal-master-4.8/
>> [5] http://download.eclipse.org/tm/terminal/builds/photon/nightly/
>>
>> *Should we use the Photon-stack based build bits instead?*
>>
>
> Martin Oberhuber has recently requested that this remains built with
> Mars/JDK 7 ,
> so no, we should not change at the moment. The terminal-master-4.8 is
> supposed to be a validation only job.
>
>
>>
>> Also worthy of note:
>>
>> tm.terminal depends on CDT. The default master build uses 8.8.1 [6]; the
>> Photon profile uses 9.4 [7].
>>
>> *Is it bad to be shipping something destined to run with 9.x when we're
>> building it against 8.x? Feels bad to me, but again, perhaps there's a
>> reason for this ? *
>>
>
> IIRC while CDT as a whole had a major version change, the individual
> plug-ins in question here, cdt native, did not. The o.e.cdt.native.serial
> bundle was 1.0.0 in CDT 8.8.1, and it is now 1.1.0 in CDT 9.5. So it is ok.
>
>
>>
>> [6] http://git.eclipse.org/c/tm/org.eclipse.tm.terminal.
>> git/tree/admin/pom-config.xml#n81
>> [7] http://git.ec. At leastlipse.org/c/tm/org.
>> eclipse.tm.terminal.git/tree/admin/pom-config.xml#n249
>> 
>>
>> Finally, I discovered that the tm.terminal build also depends on tm.rse
>> [8], whose build in turn also depends on tm.terminal [9]. This circular
>> build-time dependency is worrisome... and should be broken. I honestly
>> don't know which project to build first in order.
>>
>> We could merge the builds, move stuff around, etc. *Again, WDYT?*
>>
>
> Yes, that is a good idea. This is what Doug was considering doing, but
> because you stepped in a few months ago and got the TM builds working
> again, and because of a general lack of contributions, the idea was
> abandoned. Doug can probably comment more.
>
>
>>
>> [8] org.eclipse.tm.terminal.view.ui.rse depends
>> on org.eclipse.rse.core, org.eclipse.rse.subsystems.files.
>> core, org.eclipse.rse.ui
>> [9] org.eclipse.rse.terminals.ui depends on org.eclipse.tm.terminal.
>> control
>>
>>
>>
>> On Mon, Jun 11, 2018 at 11:39 AM, Doug Schaefer > > wrote:
>>
>>> +1. I trust you there. I don’t know the Terminal well enough to know
>>> whether the API changes in the deps would matter.
>>>
>>>
>>>
>>> (BTW, removed cross-project as we’re getting a bit specific to TM).
>>>
>>>
>>>
>>> *From:* cross-project-issues-dev-boun...@eclipse.org [mailto:
>>> cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Nick Boldt
>>> *Sent:* Monday, June 11, 2018 11:13 AM
>>> *To:* TM project developer discussions 
>>> *Cc:* Cross project issues ; CDT
>>> General developers list. 
>>> *Subject:* Re: [cross-project-issues-dev] [tm-dev] [cdt-dev] TM
>>> Terminal and RSE releases for Photon (was: Correct repo for CDT to be
>>> referring to)
>>>
>>>
>>>
>>> Doug,
>>>
>>>
>>>
>>> Do you agree we should respin TM against the latest Orbit and Photon
>>> deps? I'll assume so and try to find time today to get that built and
>>> pushed to the milestone