|[Solved] Compiler level not applied automatically [message #1758544]
||Wed, 29 March 2017 21:04
| erwin de ley
Registered: August 2013
Without deep prior knowledge, and a couple of hours of reading tutorials and browsing the forum etc I've managed to define a project setup and it almost all just works. So thanks for a great tool and extensive online info and examples!|
The setup includes a number of workspace preferences (e.g. customized java code formatter, compiler level etc), dynamic working sets, a workspace JRE 1.7 while using 1.8 for the Neon installation itself etc.
I've updated just before, to the latest Eclipse Installer 1.7.0 build 2932.
Everything works fine form start to finish, except :
1. the compiler level 1.7 is not set, it sticks to 1.8 (on the configured JRE 1.7)
2. in the package explorer the toplevel is not set directly to working sets, I need to do that still manually (will describe that in a separate post)
For the compiler level, I've used the preferences recorder to capture the switch to 1.7. I've tried to store that in 1 project-wide preferences section, and alternatively within the trunk stream (SVN lingo), as we'll probably evolve to having different java levels for different branches in the future. In both cases the level is not applied during the startup tasks, while the other prefs are correctly applied.
The setup model is in attach (just disabled the link to our SVN repo), and in this shot :
When looking at the triggered tasks in the started installation (Help > Perform setup tasks) it shows (I think) that the preferences were indeed not applied. I can then trigger that manually and it goes fine then.
What could cause this, i.e. that they are not set directly during the first installation?
[Updated on: Thu, 30 March 2017 14:51]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01591 seconds