[
http://jira.jboss.com/jira/browse/JBIDE-1180?page=comments#action_12406713 ]
Alexey Kazakov commented on JBIDE-1180:
---------------------------------------
Yes, I recall it... So the first thing that we met was the comment of
CompilationParticipant:
/**
...
* Code that participates in the build should in general be implemented with a separate
Builder,
* rather than a CompilationParticipant. It is only necessary to use a
CompilationParticipant if
* the build step needs to interact with the Java build, for instance by creating
additional
* Java source files that must themselves in turn be compiled.
..
*/
As us far as we understand it's not a common way to use it for things like validation.
But maybe we just got it wrong. So anyway let's look at it leter.
Consider using ICompilationParticipant when validating java
-----------------------------------------------------------
Key: JBIDE-1180
URL:
http://jira.jboss.com/jira/browse/JBIDE-1180
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Max Andersen
Fix For: LATER
I noticed that our seamvalidator reads each .java file into memory before validating; it
must be much more efficient to use ICompliationParticipant to validate these things since
then we will just use the already existing representation inside eclipse and we can also
limit the checks to be in only relevant strings etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira