Community
Participate
Working Groups
when i upgraded to 4.11 (2019.03) from 4.10 (2018.12) i have a big problem launching our product correctly. this is because we need that that some plugins are autostarted (what is also defined in the product file) Those are all for making logging work (log4j, slf4j, aries plugins) Tested this on 2 systems 1 windows and 1 linux and both have the same problem that the autostart=true are many times reverted, some for X then for Y. Changing plugin X to true and close/save the launch config then reopen it then it could be that Y is reverted if i change that again then X is reverted again I just can't get it correctly again. So we can't launch our product in the right state The best fix for this would be by the way that you dont have to point to an existing config.ini but you just point to the .product file, because that is the leading configuration. I will try to use a generated config.ini (that the product file generates if i make a product).
the only workaround that i could find was really editing the file myself: .metadata\.plugins\org.eclipse.debug.core\.launches And happily if i just change something else like in the arguments tab and save that then it doesn't revert it..
Can you attach a sample reproducible example?
Created attachment 278726 [details] simple plugin project with a target and launch file just make a fresh workspace import the project that is in the zip (or unzip it in the workspace and import existing from workspace) open the eclipse.target file, set that one as the active target then open the Eclipse Application.launch file go to the plugins and search for "log4j" select all 3 or 4 plugins to autostart=true (leave the level to default) then search for "aries" select the 2 plugins to also autostart to true now for example press "apply" and "close" reopen then the debug config again Maybe then tro to search for both of the above again, very likely those are not all in autostart anymore else search for "slf4j" make sure those are in autostart apply/close reopen search for any of the 3 strings in the plugins tab and for me some could still be in autostart but for the most part it is all reverted.
Ok, I am able to reproduce this issue and works well in 4.10. If there is an easy fix will push in 4.12 itself else will have to go in 4.13 as we are at the end stage of 4.12. Workaround - don't search for log4j or aries, scroll down and set it true in on go, then it saves for all.
@Johan: can you please try with 4.12 M3, to know for sure it is not yet fixed? I believe this is PDE specific - moving to PDE. Julian, this sounds related to bug 545614.
(In reply to Andrey Loskutov from comment #5) > Julian, this sounds related to bug 545614. Yes, it's the same issue. *** This bug has been marked as a duplicate of bug 545614 ***
(In reply to Andrey Loskutov from comment #5) > @Johan: can you please try with 4.12 M3, to know for sure it is not yet > fixed? > yes i tested it on M3 and it seems to work fine again in my tests
