Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 527795

Summary:	Drop 32-bits EPP package
Product:	[Technology] EPP	Reporter:	Mickael Istria <mistria>
Component:	Packager	Assignee:	Project Inbox <epp.packager-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	akurtakov, hubert+eclipseorg, mknauer
Version:	4.7.0
Target Milestone:	later
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	526620
Bug Blocks:

Description Mickael Istria

2017-11-27 09:32:58 EST

See bug 526620.
If 32 bits Java doesn't exist anymore, we should drop 32-bits EPP to save build time and disk space.

Comment 1 Markus Knauer

2017-11-27 10:11:34 EST

+1

- First, and probably most important, is the communication. It shouldn't be a surprise to anyone on the release day that 32-bit support is not available any more.
- Are there any real reasons, or even blockers for some people, to keep 32-bit support? 3-4 percent are still using this flavour. What are the reasons for these users to stick to 32-bit? Is there something that we missed, or could they easily migrate?
- What's the timeframe? Photon next year?
- Would it make sense to only support 64-bit, but still create the 32-bit metadata? I.e. include 32-bit in the p2 repositories, but do not publish archive files on the download page, and hide 32-bit installations from Oomph in the default settings?

Comment 2 Alexander Kurtakov

2018-07-11 09:48:01 EDT

(In reply to Markus Knauer from comment #1)
> +1
> 
> - First, and probably most important, is the communication. It shouldn't be
> a surprise to anyone on the release day that 32-bit support is not available
> any more.
> - Are there any real reasons, or even blockers for some people, to keep
> 32-bit support? 3-4 percent are still using this flavour. What are the
> reasons for these users to stick to 32-bit? Is there something that we
> missed, or could they easily migrate?
> - What's the timeframe? Photon next year?
> - Would it make sense to only support 64-bit, but still create the 32-bit
> metadata? I.e. include 32-bit in the p2 repositories, but do not publish
> archive files on the download page, and hide 32-bit installations from Oomph
> in the default settings?

You can see bug 536766 listing some real world issues with 32 bit flavors.

Comment 3 Alexander Kurtakov

2018-12-04 05:38:52 EST

2018-12 no longer contains 32 bit builds - https://www.eclipse.org/downloads/packages/release/2018-12/m3