[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Who decided to override my Java installation with JustJ?
|
@Gunnar, @Ed
thanks for the hints and workarounds, I just found that this example
best reproduces the original issue described here and maybe give some
pointers what might be wrong (or needs adjustments)?
I think whatever causing this its almost always undesirable that justj
is pulled in without explicit user request. New releases always produce
a lot of traffic if we higher this traffic even more by downloading
unnecessary new java version this will frustrate user soon due to long
download times.
And even though it can
Am 17.12.20 um 10:41 schrieb Ed Merks:
You can point at this instead:
https://download.eclipse.org/releases/2020-12/202012161000/
Or at this:
http://download.eclipse.org/eclipse/updates/4.18/R-4.18-202012021800
I.e., don't point at EPP if you don't EPP's IUs.
If the problem is caused by fake p2 a.java.javase IUs missing package
exports that are imported/used by JDT, then I don't think anyone has
tried to fix those (which would be hard because it would need to be a
new IU with a different version number).
On 17.12.2020 10:13, Christoph Läubrich wrote:
Is there any progress on this?
I noticed that even when using for example [1] in a target it
downloads the full java 15 jre (>100mb) what is taking ages (eclipse
servers are currently serving this with 16 to 32kb/s) to resolve
target definition now.
Even worse, if one builds for multiple targets justj is downloaded for
each target platform (e.g. linux, mac, windows) wasting a lot of
bandwith, disk space and time...
<location includeAllPlatforms="false" includeConfigurePhase="false"
includeMode="planner" includeSource="true" type="InstallableUnit">
<repository location="https://download.eclipse.org/releases/2020-12/"/>
<unit id="org.eclipse.sdk.feature.group" version="0.0.0"/>
</location>
Am 22.10.20 um 14:44 schrieb Greg Watson:
Thanks Ed, that helped. Hopefully this will be fixed soon.
Regards,
Greg
On Oct 15, 2020, at 10:17 AM, Ed Merks <ed.merks@xxxxxxxxx> wrote:
Greg,
I don't think anyone has figured out why a JRE is automatically
installed during update:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=567504
You can undo this effect just by removing the -vm argument (to end
up with the default) or by changing the -vm argument to the one you
want it to use, in your eclipse.ini.
It's liable to come back if there is an unexpected updated to the
JRE in the future...
Regards,
Ed
On 15.10.2020 15:11, Greg Watson wrote:
My Eclipse installation recently prompted me to upgrade (something
new), so I accepted the advice. Now I’ve discovered that an unknown
JRE was downloaded onto my machine and is being used to run
Eclipse. This is broken on so many levels, I don’t even know where
to start opening bug reports.
Since when does Eclipse start installing unauthorized versions of
the JRE onto my machine without any notification, and that
overrides my choice of the JRE (or JDK in my case) for running
Eclipse? Not only is there no option to change or uninstall this,
it breaks tools that rely on the JDK (e.g. Spring Boot Live hovers.)
Does anybody else see the problem here? Someone needs to rethink
this kind of behavior.
In the mean time, does anyone know how to undo this mess, or am I
forced to go back to 2020-06?
Regards,
Greg
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
