[
https://jira.jboss.org/jira/browse/JBIDE-3336?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3336:
--------------------------------------------
Amitev - when you write "that i exclude from deploy ", how did you do that ?
Alexey - by disabling this feature you mean the possibility the user have today to
disable the seam validator via the wtp validator or something else ?
About making it clever then it sounds to me that if one file is changed then to be not
affect/annoy users too much (i.e. be efficient) we should keep track of which
declarations comes from this file and only revalidate the files that would be affected by
this - and not the whole project.
Other optimizations is to only look at .xml within webcontent paths and java source paths
(that might affect pure seam java projects, but then having an default enabled option
saying "only validate files on webcontent and java source path" would be a
solution to that.
That would also stop the original issue of seam validator running because an ant
build.xml file were saved. But again, why are we even running when a build.xml file is
being saved ? Can't we check the content type or something to limit what files we
react to ?
Seam validator is called too often
----------------------------------
Key: JBIDE-3336
URL:
https://jira.jboss.org/jira/browse/JBIDE-3336
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.beta1
Environment: Windows XP, eclipse 3.4.1, wtp 3.0.3, jboss tools nightly build
N200812020037
Reporter: Adrian Mitev
Assignee: Alexey Kazakov
Fix For: 3.0.0.GA
The Seam validator is called even if i save a build.xml file and it scans all pages.
Quite heavy, i have over 50 pages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira