Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] shipping directly a jre with an eclipse product on OSX

If i rememmber right from last time digging into Equinox source "restart" does not really restarts the process but exit the application with a special statuscode and the instantly start up the OSGi-Framework again (switch workspace works in a similar way).

So I think updating a JRE/JDK of a running product won't work as expected without additional support for this specific use-case because the JVM never exit but required files are already deleted.

The only reliable way for such upgrade-path I see is using the director application and modifying a (non-running) install.

It might also work to install the new feature, then SHUTDOWN and then uninstall the old one.

Am 24.09.19 um 10:05 schrieb Johan Compagner:
hi

no it is not just window
also linux and osx don't work
So it is not about deletion of files.. it's a generic multi os problem.

and I have a feeling if I make simple example with just a feature that it then will work (I think)
its that a full product is updated with that feature that it maybe fails.
But i am first now also going to test how it works when i use a 4.12 to a 4.12 with an updated feature
current test is 4.11 to a 4.12 with those new feature versions.

I already created the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=551378

On Mon, 23 Sep 2019 at 17:02, Mickael Istria <mistria@xxxxxxxxxx <mailto:mistria@xxxxxxxxxx>> wrote:

    Hi Johan,

    I suggest to ensure it's a p2 bug and to facilitate its remediation,
    you build some dummy test p2 units (such as empty bundle) with a
    p2.inf file using a simple

    instructions.install =
    org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:-consoleLog);
    instructions.uninstall =
    org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:-consoleLog);

    and put it into some p2 repo.
    Check metadata, try installing then uninstalling it (really
    uninstall, no update).
    If after uninstall the `-consoleLog` persists on some OS, then you
    can report to p2 with more details; if it does not persist, then you
    may need to investigate a bit more, but it could be caused by
    Windows not being able to delete open files, and probably altering
    the uninstallation process.
    _______________________________________________
    tycho-user mailing list
    tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
    To change your delivery options, retrieve your password, or
    unsubscribe from this list, visit
    https://www.eclipse.org/mailman/listinfo/tycho-user



--
Johan Compagner
Servoy

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tycho-user



Back to the top