[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [recommenders-dev] Code Formatter, Save Actions ...
|
The JSON is super easy to create.
Just record the preference with the built-in prefs recorder and then
save the epf files to a webserver. Next the the epf files you put the
following JSON:
{
type : 'com.google.eclipse.mechanic.UriTaskProviderModel',
metadata : {
name: 'Workspace Mechanic tasks for code recommenders',
description: 'Workspace Mechanic tasks to get default settings for
Eclipse',
contact: 'recommenders-dev@xxxxxxxxxxx'
},
tasks: [
'java-cleanup.epf',
'java-codestyle.epf',
'java-codetemplates.epf',
'java-compiler.epf',
'java-contentassist.epf',
'java-editor-save.epf',
'java-formatting.epf',
'mylyn.epf',
'project-setup.epf',
'update.epf',
'usage-data-collector.epf',
'maven-download-sources.epf'
]
}
Greetings
-Sascha-
Am 19.04.2013 13:08, schrieb Marcel Bruch:
> Sounds not too bad. Thanks for the update on workspace mechanic
>
> On Apr 19, 2013, at 12:59 PM, Sascha Vogt <FunkyFish@xxxxxxx
> <mailto:FunkyFish@xxxxxxx>> wrote:
>
>> Do all code recommenders project use the same tab width, tab vs. spaces,
>> code templates, etc.? Or is this individual per project?
>
> In general they should all have the same settings. But I know we have
> different settings when it comes to brackets (e.g., simple if statements
> with {} or without them).
>
> If someone on the list would volunteer this look at this and come up
> with a set of JSON files for Workspace Mechanic (based on what we have
> already), this would be great.
>
>
> Best,
> Marcel
>
>
> _______________________________________________
> recommenders-dev mailing list
> recommenders-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/recommenders-dev
>