JSF Tools is starting to look at the JEM proxy tooling (bean introspection). This will likely a become a key dependency for us in 3.0. I don't think this is part of the UI, but just in case...
--Cam -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David M Williams Sent: Friday, October 19, 2007 9:36 PM To: Discussions people developing code for the Visual Editor project; [email protected] Subject: [wtp-dev] Does VE use org.eclipse.jem.ui? I suspect so. But, funny thing is, we in WTP don't. I guess during in the component transfer that happened last year, since it had 'jem' in the name, we assumed they all went together, but, I think, we only use JEM as a model ... no JEM UI per se. So ... I was wondering ... does VE need it? If so, would you like it "back"? As far as I can tell, we in WTP don't need it, and as far as I know, no adopter needs it, except in the context of VE. Hence, we in WTP have no real reason to "ship" it, except for the fact that VE might need it, so if VE project does need it, then it would be better to live in VE. Thoughts? It is at jst/components/jem/org.eclipse.jem.ui in the /cvsroot/webtools repository
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
