Hey, Lars In fact, we're going through the process of porting our application to the Eclipse 4 framework, but that definitely isn't light work for us. We relied heavily on the presentation packages and our app was torn apart by the changes. I asked for some guidance here before [1].
I know that using the Eclipse 4.x runtime solves the menu problem, but, for now, we have to find a way to make our Eclipse 3.x-based app work properly. As I said, we're building a runnable jar that replicates (as far as we are able to replicate) the behavior of the native launcher. My thought was that maybe it would be easier to make a minor adjustment on the native launcher code and compile it again. [1] https://www.eclipse.org/lists/platform-dev/msg03252.html Thanks for the reply. Mario Marinato ~ Rio de Janeiro/Brazil Em ter., 10 de out. de 2023 às 04:15, Lars Vogel via platform-dev < platform-dev@eclipse.org> escreveu: > Hi Mario, > > I don't know about the Mac native launcher question but you should be > able to run your 3.x application on a 4.x runtime without too many > changes. Most of the Eclipse IDE plug-ins are still based on 3.x API > and they run fine. > > Best regards, Lars > > On Mon, Oct 9, 2023 at 2:03 PM Mário Marinato via platform-dev > <platform-dev@eclipse.org> wrote: > > > > Hello. > > > > I'm part of a team that develops an RCP application that is still based > on the Eclipse 3 framework. > > > > I know we should've migrated years ago, we're porting it now, but the > current version of our system is still alive and needs maintenance, and > that's why I'm here. > > > > The recent release of the new MacOS, Sonoma, broke our menus (see here), > and we discovered that the source of the problem is the native launcher. > If we launch our application using java -jar > plugins/org.eclipse.equinox.launcher.jar, the menus work as expected. > > > > We then started building an executable jar that performs the call and > handles all the other tasks needed (reading the .ini file, handling > restarts, so on). > > > > But then this idea came to me, that recompiling the native launcher > might solve the problem. This way, we would not need to mess around with a > different executable jar. > > > > Do you think this is possible? If so, is there a page with detailed > information on how we could achieve this? > > > > Thanks. > > > > Mario Marinato > > ~ Rio de Janeiro/Brazil > > _______________________________________________ > > platform-dev mailing list > > platform-dev@eclipse.org > > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev > > > > -- > Eclipse Platform project co-lead > CEO vogella GmbH > > Haindaalwisch 17a, 22395 Hamburg > Amtsgericht Hamburg: HRB 127058 > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel > USt-IdNr.: DE284122352 > Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: > http://www.vogella.com > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev >
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
