Now I'm making some progress in getting it to work. It seems like it took some time for it to find the jar, even though the jar was in the right place. It seemed to work when I would open up the project properties, look at the build classpath, and then click ok (without making any changes). That got it to recalculate things.
However, the whole thing is unusable because I'm hitting out of memory (permgen) errors every 15 minutes. I'm running it with ./eclipse -vmargs -Xmx1024M and that is not helping.
I'm going to wipe it out, reboot the computer, reinstall it all, and try again. However, this is not looking like a stable dev environment righ tnow.
It is pretty cool though that it looks at EL and knows what is and is not a Seam component, and shows errors as needed.
tried writing it without code block at first
Thanks for the suggestion. I went ahead and cranked everything up:
eclipse -vmargs -Xms512M -Xmx1024M -XX:PermSize=128M -XX:MaxPermSize=256M
Why not, I have tons of memory. Now it is stable.
Now the one thing left is to figure out how to get JBoss Tools to work nicely with a jar of Seam components that is supplied externally (by some other developer team, using different tools).
This might work!