Yes, by root I mean platform, JDK, etc.
> But I can comment for the Eclipse top-level project (a.k.a. as SDK and Platform): we never shipped 'org.apache.http.entity.mime'.
Thatâs false. The eclipse top-level project repository for 4.6.2 includes version 4.3.6 of the org.apache.httpcomponents.httpclient bundle that does include the mime package.
From: Daniel Megert
Sent: Friday, February 3, 2017 9:42 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Problem withorg.apache.httpcomponents.httpclient bundle in Oxygen M5
I have no clue what you mean with "root". But I can comment for the Eclipse top-level project (a.k.a. as SDK and Platform): we never shipped 'org.apache.http.entity.mime'.
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 03.02.2017 18:33
Subject: [cross-project-issues-dev] Problem with org.apache.httpcomponents.httpclient bundle in Oxygen M5
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
We are having troubling building our plugin against Oxygen M5. The org.apache.httpcomponents.httpclient bundle in M5 build of root eclipse project is missing org.apache.http.entity.mime package.
In M5 root Eclipse project repo, the version is 4.5.2 (771KB) and is missing the mime package
In M5 Orbit repo, the latest version is 4.3.6 (845KB) and does contain the mime package
On Apache.org, the version 4.5.2is 1226KB and does contain the mime package
So, I have the following questions:
1. Where did version 4.5.2 in root Eclipse project repo come from, as itâs not in Orbit M5 build?
2. Why is this version missing org.apache.http.entity.mime package?
3. Why are we shipping a different bundle then whatâs produced by the original third-party project? Since we are using the same bundle symbolic name, itâs a rather problematic situation.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit