Eclipse provides its own API to access Java source code model. Using this API I can search for classes by name, enum source folders, getting and modifying AST of Java sources, working with Java class files in JARs and looking up their's Javadocs, etc.
In the other words all you see and able to do in Eclipse is exposed via its API. What I did is built my own API around Eclipse API, it's all here: https://github.com/anjlab/eclipse-tapestry5-plugin/tree/master/com.anjlab.eclipse.tapestry5/src/com/anjlab/eclipse/tapestry5 On Mon, Dec 9, 2013 at 2:45 PM, Lance Java <lance.j...@googlemail.com>wrote: > Very cool. How are you getting all this info. Are you able to use tapestry > services? Or are you rolling your own solution? > > I know gradle has a tooling api so that external tools can query the gradle > model. Perhaps Tapestry needs a similar concept? > On 9 Dec 2013 10:36, "Dmitry Gusev" <dmitry.gu...@gmail.com> wrote: > > > Eclipse Tapestry5 Plugin now supports Completion Proposals in WTP > Editors. > > > > This is an experimental feature and lots of enhancements need to be done, > > but you can try basic functionality today. > > > > Version 2.1.0 includes completion proposals for component parameters and > > properties, including original Javadoc tooltip for each proposal. > > > > This feature will be available in XML, JSP, or HTML editors of Eclipse > WTP. > > > > > > -- > > Dmitry Gusev > > > > AnjLab Team > > http://anjlab.com > > > -- Dmitry Gusev AnjLab Team http://anjlab.com
