Closed GoogleCodeExporter closed 9 years ago
The Workspace Mechanic does not read that file, Eclipse does.
Original comment by konigsb...@gmail.com
on 18 Feb 2013 at 7:36
Then is the wiki page on it still accurate?
As following it after reading the links I am still unable to get it to add a
new location.
Original comment by robin.m...@logica.com
on 19 Feb 2013 at 12:43
I have done the following:
Created a plugin_customization.ini with the contents (Based on the preference
recorder results) being
/instance/com.google.eclipse.mechanic/mechanicSourceDirectories=["D\:\\\\Users\\
\\mossro\\\\.eclipse\\\\mechanic","D\:\\\\eclipse\\\\configuration\\\\com.google
.eclipse.mechanic\\\\mechanic", "http:\\\\localhost\\"]
I have tried this file in the following directories
plugins\com.google.eclipse.mechanic_0.3.4
plugins\com.google.eclipse.mechanic
plugins\com.google.eclipse.mechanic_0.3.4.jar (inside the jar)
This has has no affect. Could you verify that the ini file contents is correct
and that where im placing the file is correct.
Original comment by robin.m...@logica.com
on 19 Feb 2013 at 3:56
The wiki page says there are TODOs given the change of format so I'm not
terribly surprised by your comment. Does the Eclipse error log have anything to
say?
Original comment by konigsb...@gmail.com
on 19 Feb 2013 at 8:27
There's nothing in the eclipse error log.
I got the above json format by using the preference recorder to record my
Workspace Mechanics preferences.
I'm not convinced Eclipse is picking up the plugin ini file.
Original comment by robin.m...@logica.com
on 19 Feb 2013 at 8:43
Original issue reported on code.google.com by
robin.m...@logica.com
on 18 Feb 2013 at 3:40