|
|
Re: JET2 merging of model data with existing Java code [message #56534 is a reply to message #56512] |
Tue, 27 January 2009 22:51 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: tmothymarc.freenet.de
Hi Paul,
just a simple question. With JDT tree, you mean the AST created by the
JDT or what else?
Thx
Timothy
Paul Elder schrieb:
> JF:
>
> No, the modelInspectors approach has not been abandoned. JET2 already has
> the following inspectors:
>
> * XML DOM Node objects
> * EMF EObject object (which covers any EMF-based model in existance)
> * Eclipse workspaces IResource objects
>
> I will be adding to this list in the Galileo release:
> * JDT trees
>
> I hope also, to add the ability to navigate (but no promises)
> * java.util.Properties
> * Manifest files
>
> But, that doesn't mean you should leave JMerge behind.
>
> Paul
>
>
|
|
|
|
Re: JET2 merging of model data with existing Java code [message #56749 is a reply to message #56642] |
Sun, 01 February 2009 14:53 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: tmothymarc.freenet.de
Okay, thanks Paul.
i think this enhancement would be quite fantastic.
Paul Elder schrieb:
> Timothy:
>
> I mean the all the descendents of ASTNode:
>
> http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.i sv/reference/api/org/eclipse/jdt/core/dom/ASTNode.html
>
> Paul
>
> "Timothy Marc" <tmothymarc@freenet.de> wrote in message
> news:glo34r$hfi$1@build.eclipse.org...
>> Hi Paul,
>>
>> just a simple question. With JDT tree, you mean the AST created by the JDT
>> or what else?
>>
>> Thx
>> Timothy
>>
>> Paul Elder schrieb:
>>> JF:
>>>
>>> No, the modelInspectors approach has not been abandoned. JET2 already has
>>> the following inspectors:
>>>
>>> * XML DOM Node objects
>>> * EMF EObject object (which covers any EMF-based model in existance)
>>> * Eclipse workspaces IResource objects
>>>
>>> I will be adding to this list in the Galileo release:
>>> * JDT trees
>>>
>>> I hope also, to add the ability to navigate (but no promises)
>>> * java.util.Properties
>>> * Manifest files
>>>
>>> But, that doesn't mean you should leave JMerge behind.
>>>
>>> Paul
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03697 seconds