I was wondering if it was possible to do variable substitution with
Java system properties during the import of the preference file
similar to the way Eclipse Team Etceteras does it?
We have a few preferences that are absolute file paths that may be
different for each developer.
Cheers,
Tom
--
Robert Konigsberg
Is this feature limited to .epf files, or other types, including .kbd?
Does the variable substitution work with preference metadata? Why or Why not?
There might be a legitimate use of ${variable.name} inside a file. Do
those now need to be escaped? How will you deal with this when some
people want variable substitution and some do not?
--
Robert Konigsberg
Here are some questions I have for you.
Is this feature limited to .epf files, or other types, including .kbd?
Does the variable substitution work with preference metadata? Why or Why not?
There might be a legitimate use of ${variable.name} inside a file. Do
those now need to be escaped?
people want variable substitution and some do not?
Here are some questions I have for you.
Is this feature limited to .epf files, or other types, including .kbd?
Does the variable substitution work with preference metadata? Why or Why not?
There might be a legitimate use of ${variable.name} inside a file.
That's fine.
>>
>> Does the variable substitution work with preference metadata? Why or Why
>> not?
>
> Not quite sure what you mean with preference meta data. @title, @description
> and @audit_type?
Yes
>> There might be a legitimate use of ${variable.name} inside a file. Do
>> those now need to be escaped?
>
> Unless variable.name happens to be a system property it would not be
> touched. One could think about adding a prefix such as
> ${mechanic.variable_name}. I could strip off the prefix and check whether
> variable_name is a system property
Speaking of which, why would you use system properties when Eclipse
tends to rely on variable substitution?
> How will you deal with this when some
>>
>> people want variable substitution and some do not?
>
> It's disabled per default and needs to be switched on explicitly
I don't think a preference is the way to go. Instead I think
annotating that the .epf itself uses variable substitution makes more
sense. Then it matters less which characters you use. Trying to choose
a less likely pattern just means it'll happen less likely. We want no
conflicts at all.
What should happen if a variable (or system property) does not exist?
--
Robert Konigsberg
I do not think there is a need to list the variables. Instead just indicate if variable substitution will occur at all. Consider that this needs to be 100% compatible with existing behavior, no questions.
--
Robert Konigsberg
Has this not been implemented? I would like to use ${workspace_loc} since I have different workspace folders for different branches of code.
Has this been implemented by now ?
I'm just annoyed by CDT bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=406783 so I cannot use ${user_home} for my CDT user dictionary... hoping that mechanic could replace this for me ?
--
You received this message because you are subscribed to the Google Groups "Workspace Mechanic for Eclipse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to workspacemecha...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.