Vijay,
Thanks for the explanation. I requested
that this issue be added to the 1.5 hot list as it has a big impact on the team
development scenario.
- Konstantin
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Vijay Bhadriraju
Sent: Sunday, March 19, 2006 8:14
AM
To: wtp-dev@xxxxxxxxxxx
Subject: Re: [wtp-dev] Validator
Settings
Konstantin,
The
project level validation setting are stored under this directroy
..\.metadata\.plugins\org.eclipse.core.resources\.projects\EjbProject\.indexes in
the properties.index file. The project level or the global validation
preferences are per workspace and are not stored at the project level.
Presently the Persistent Property store mechanism is being used hence they are
stored in the .metadata area rather than the project. We have a defect open
https://bugs.eclipse.org/bugs/show_bug.cgi?id=125749 to change this support to
use the Preference store so the preferences can be stored at a project level
and these preferences can participate in the import export of preferences and
shared through project interchanges.
This
defect has been targeted for 1.5 but has been given priority with where we are
for 1.5.
Regards,
Vijay
_____________________________
Vijay Bhadriraju
Rational Tools, J2EE Tooling
Ph: (919) 486-1898, T/L: 526-1898
Internet: vbhadrir@xxxxxxxxxx
_____________________________
David M
Williams/Raleigh/IBM@IBMUS
Sent
by: wtp-dev-bounces@xxxxxxxxxxx
03/19/2006 01:18 AM
Please
respond to "General discussion of project-wide or architectural
issues."
|
|
To
|
"General discussion of project-wide or
architectural issues." <wtp-dev@xxxxxxxxxxx>
|
cc
|
|
bcc
|
|
Subject
|
Re: [wtp-dev] Validator Settings
|
|
Konstantin, I think I see them under
\.metadata\.plugins\org.eclipse.core.resources
a sign that "resource properties" are being used? (And, contrary to
the name, these are not "shared", but are specific to workspace).
So, that sounds kind of old fashioned, left over, and I'm sure the preference
API could be used.
But, my guess is that even then, user-oriented workspace preference is correct.
That these really are envisioned as
user-oriented preferences ... that is, depending on what the user is doing they
may want some on, or others off.
So, not sure what advice to give on your delima, but ... hope you open a bug on
one validator causing problems with
another ... that doesn't sound good.
"Konstantin
Komissarchik" <kosta@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
03/18/2006 08:31 PM
Please
respond to
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
|
To
|
"General discussion of project-wide or
architectural issues." <wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
[wtp-dev] Validator Settings
|
|
When I override validator settings at a project level and turn off a validator,
where are those settings kept? We are having difficulties with WSDL validator conflicting
with BEA-specific functionality, so we turn it off for a project when one of
our facets is installed. However, when the project is imported into a different
workspace (team environment), that change is lost. It doesn’t appear that
this is kept at the project level. Where is this information kept and is there
a reason that’s it is not kept in the project directory?
Thanks,
- Konstantin
_______________________________________________________________________
Notice: This email message, together with
any attachments, may contain
information of BEA Systems,
Inc., its subsidiaries and affiliated
entities, that may be confidential,
proprietary, copyrighted and/or
legally privileged, and is intended solely for the
use of the individual
or entity named in this message. If you are not
the intended recipient,
and have received this message in error, please
immediately return this
by email and then delete it.
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev