GDK methods documentation in eclipse plugin

[Guillaume Jeudy]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

 

Are there any plans or existing workarounds to get GDK method documentation integrated in the Eclipse IDE plugin? Currently I’m able to pull-up GDK methods with the code assist (ctrl + space) feature but no javadoc or groovydoc come up to describe the GDK methods.

 

I’m using the latest V2 plugin with eclipse 3.5.

 

Thank you,

Regards,

Guillaume Jeudy – Java developer
Java and Open Source Application Development – Montreal Solutions Centre
1801, McGill College Avenue, Suite 1100
Montreal, QC, H3A 2N4

gjeudy@...
W: [phone]           F: [phone]

 

---

This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

 

 

Ce courrier électronique (en incluant n'importe quels attachements) peut contenir des renseignements

qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la divulgation à quelqu'un autre

que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de ce courrier électronique

électronique ou de ses contenus (en incluant n'importe quels attachements) par les personnes autre que

le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce message par erreur, notifiez-nous

s'il vous plaît immédiatement par le courrier électronique de réponse pour que nous puissions corriger nos

dossiers intérieurs. Effacez s'il vous plaît alors le message original (en incluant n'importe quels attachements)

dans son ensemble. Merci.

 

 

douellet@... 

[Ronny Løvtangen-2]

Sounds like you need to tell Eclipse where to find the source jar, or the javadoc jar / javadoc url.

If you use maven then I guess this should be set up automaticly, at least it does in IntelliJ IDEA. But you need trigger a download of the sources/javadoc to your ~/.m2/repos folder, either from mvn command line, or from some Eclipse equivalent to IntelliJ's "download sources" button.

If you aren't using maven then you need to set up this manually in Eclipse. I don't know where since I use IntelliJ, but I'm sure you'll find it close to where you configure your dependent jars.

Ronny

On Nov 2, 2009, at 9:47 PM, Jeudy, Guillaume wrote:

Hi,

 

Are there any plans or existing workarounds to get GDK method documentation integrated in the Eclipse IDE plugin? Currently I’m able to pull-up GDK methods with the code assist (ctrl + space) feature but no javadoc or groovydoc come up to describe the GDK methods.

 

I’m using the latest V2 plugin with eclipse 3.5.

 

Thank you,

Regards,

Guillaume Jeudy – JAVA DEVELOPER
Java and Open Source Application Development – Montreal Solutions Centre
1801, McGill College Avenue, Suite 1100
Montreal, QC, H3A 2N4

gjeudy@... 
W: [phone]           F: [phone]

 

---

This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

 

 

Ce courrier électronique (en incluant n'importe quels attachements) peut contenir des renseignements

qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la divulgation à quelqu'un autre

que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de ce courrier électronique

électronique ou de ses contenus (en incluant n'importe quels attachements) par les personnes autre que

le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce message par erreur, notifiez-nous

s'il vous plaît immédiatement par le courrier électronique de réponse pour que nous puissions corriger nos

dossiers intérieurs. Effacez s'il vous plaît alors le message original (en incluant n'importe quels attachements)

dans son ensemble. Merci.

 

 

douellet@... 

[Guillaume Jeudy]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Ronny,

 

Thanks for replying, the source jar is included by the plugin for the groovy classes, therefore I can see documentation for those classes with no problems.

 

What is lacking is the GDK methods documentation. GDK methods are the ones weaved at runtime on top of existing JDK classes. http://groovy.codehaus.org/groovy-jdk/

 

Guillaume Jeudy – Java developer
Java and Open Source Application Development – Montreal Solutions Centre
1801, McGill College Avenue, Suite 1100
Montreal, QC, H3A 2N4

gjeudy@...
W: [phone]           F: [phone]

 

---

From: Ronny Løvtangen [mailto:lists@...]
Sent: Monday, November 02, 2009 4:07 PM
To: user@...
Subject: Re: [groovy-user] GDK methods documentation in eclipse plugin

 

Sounds like you need to tell Eclipse where to find the source jar, or the javadoc jar / javadoc url.

If you use maven then I guess this should be set up automaticly, at least it does in IntelliJ IDEA. But you need trigger a download of the sources/javadoc to your ~/.m2/repos folder, either from mvn command line, or from some Eclipse equivalent to IntelliJ's "download sources" button.

If you aren't using maven then you need to set up this manually in Eclipse. I don't know where since I use IntelliJ, but I'm sure you'll find it close to where you configure your dependent jars.

 

 

Ronny

 

On Nov 2, 2009, at 9:47 PM, Jeudy, Guillaume wrote:

 

Hi,

 

Are there any plans or existing workarounds to get GDK method documentation integrated in the Eclipse IDE plugin? Currently I’m able to pull-up GDK methods with the code assist (ctrl + space) feature but no javadoc or groovydoc come up to describe the GDK methods.

 

I’m using the latest V2 plugin with eclipse 3.5.

 

Thank you,

Regards,

Guillaume Jeudy – JAVA DEVELOPER
Java and Open Source Application Development – Montreal Solutions Centre
1801, McGill College Avenue, Suite 1100
Montreal, QC, H3A 2N4

gjeudy@... 
W: [phone]           F: [phone]

 

 

 

---

This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

 

 

 

Ce courrier électronique (en incluant n'importe quels attachements) peut contenir des renseignements

qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la divulgation à quelqu'un autre

que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de ce courrier électronique

électronique ou de ses contenus (en incluant n'importe quels attachements) par les personnes autre que

le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce message par erreur, notifiez-nous

s'il vous plaît immédiatement par le courrier électronique de réponse pour que nous puissions corriger nos

dossiers intérieurs. Effacez s'il vous plaît alors le message original (en incluant n'importe quels attachements)

dans son ensemble. Merci.

 

 

douellet@... 

 

---

This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

 

 

Ce courrier électronique (en incluant n'importe quels attachements) peut contenir des renseignements

qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la divulgation à quelqu'un autre

que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de ce courrier électronique

électronique ou de ses contenus (en incluant n'importe quels attachements) par les personnes autre que

le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce message par erreur, notifiez-nous

s'il vous plaît immédiatement par le courrier électronique de réponse pour que nous puissions corriger nos

dossiers intérieurs. Effacez s'il vous plaît alors le message original (en incluant n'importe quels attachements)

dans son ensemble. Merci.

[Andrew Eisenberg]

This is working for me, so I wonder if there is something different
about your set up.

When there are multiple DGM methods with the same name, but different
arguments, hovers can sometimes get confused (since method arguments
are not always explicit in the code).

When I type this:

findAll { }

into an empty script and press F2 (keyboard shortcut to display
hovers), the correct JavaDoc appears.  When I type this:

println ""

I get this for a hover:

* void groovy.lang.Script.println(Object value)
* void org.codehaus.groovy.runtime.DefaultGroovyMethods.println(Object self)
* void groovy.lang.Script.println()

(which means that the information controller does not know which
method it should show JavaDoc for). Are you seeing different behavior?
 If so, this is likely a bug and I'd suggest that you raise a jira for
it and include the code that is failing for you.


ps- in the future, you will get a quicker response if you send
Groovy-Eclipse related questions to the
eclipse-plugin-user@... mailing list.

On Mon, Nov 2, 2009 at 2:29 PM, Jeudy, Guillaume <gjeudy@...> wrote:

> Ronny,
>
>
>
> Thanks for replying, the source jar is included by the plugin for the groovy
> classes, therefore I can see documentation for those classes with no
> problems.
>
>
>
> What is lacking is the GDK methods documentation. GDK methods are the ones
> weaved at runtime on top of existing JDK classes.
> http://groovy.codehaus.org/groovy-jdk/
>
>
>
> Guillaume Jeudy – Java developer
>
> Java and Open Source Application Development – Montreal Solutions Centre
> 1801, McGill College Avenue, Suite 1100
> Montreal, QC, H3A 2N4
>
> gjeudy@...
> W: [phone]           F: [phone]
>
>
>
> ________________________________
>
> From: Ronny Løvtangen [mailto:lists@...]
> Sent: Monday, November 02, 2009 4:07 PM
> To: user@...
> Subject: Re: [groovy-user] GDK methods documentation in eclipse plugin
>
>
>
> Sounds like you need to tell Eclipse where to find the source jar, or the
> javadoc jar / javadoc url.
>
> If you use maven then I guess this should be set up automaticly, at least it
> does in IntelliJ IDEA. But you need trigger a download of the
> sources/javadoc to your ~/.m2/repos folder, either from mvn command line, or
> from some Eclipse equivalent to IntelliJ's "download sources" button.
>
> If you aren't using maven then you need to set up this manually in Eclipse.
> I don't know where since I use IntelliJ, but I'm sure you'll find it close
> to where you configure your dependent jars.
>
>
>
>
>
> Ronny
>
>
>
> On Nov 2, 2009, at 9:47 PM, Jeudy, Guillaume wrote:
>
>
>
> Hi,
>
>
>
> Are there any plans or existing workarounds to get GDK method documentation
> integrated in the Eclipse IDE plugin? Currently I’m able to pull-up GDK
> methods with the code assist (ctrl + space) feature but no javadoc or
> groovydoc come up to describe the GDK methods.
>
>
>
> I’m using the latest V2 plugin with eclipse 3.5.
>
>
>
> Thank you,
>
> Regards,
>
> Guillaume Jeudy – JAVA DEVELOPER
> Java and Open Source Application Development – Montreal Solutions Centre
> 1801, McGill College Avenue, Suite 1100
> Montreal, QC, H3A 2N4
>
> gjeudy@...
> W: [phone]           F: [phone]
>
>
>
>
>
>
>
> ________________________________
>
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>
>
>
>
>
>
>
> Ce courrier électronique (en incluant n'importe quels attachements) peut
> contenir des renseignements
>
> qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la
> divulgation à quelqu'un autre
>
> que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de
> ce courrier électronique
>
> électronique ou de ses contenus (en incluant n'importe quels attachements)
> par les personnes autre que
>
> le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce
> message par erreur, notifiez-nous
>
> s'il vous plaît immédiatement par le courrier électronique de réponse pour
> que nous puissions corriger nos
>
> dossiers intérieurs. Effacez s'il vous plaît alors le message original (en
> incluant n'importe quels attachements)
>
> dans son ensemble. Merci.
>
>
>
>
>
>
>
>
>
> ________________________________
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>
>
>
>
>
> Ce courrier électronique (en incluant n'importe quels attachements) peut
> contenir des renseignements
>
> qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la
> divulgation à quelqu'un autre
>
> que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de
> ce courrier électronique
>
> électronique ou de ses contenus (en incluant n'importe quels attachements)
> par les personnes autre que
>
> le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce
> message par erreur, notifiez-nous
>
> s'il vous plaît immédiatement par le courrier électronique de réponse pour
> que nous puissions corriger nos
>
> dossiers intérieurs. Effacez s'il vous plaît alors le message original (en
> incluant n'importe quels attachements)
>
> dans son ensemble. Merci.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Ronny Løvtangen-2]

Ok, didn't know the plugin included the groovy source. How does that cope with using different groovy version from the one the plugin bundles?

At least in IntelliJ with maven, source for DGM points directly to the groovy-all-1.x.y-sources.jar brought in by maven. 

On Nov 2, 2009, at 10:29 PM, Jeudy, Guillaume wrote:

Ronny,

 

Thanks for replying, the source jar is included by the plugin for the groovy classes, therefore I can see documentation for those classes with no problems.

 

What is lacking is the GDK methods documentation. GDK methods are the ones weaved at runtime on top of existing JDK classes. http://groovy.codehaus.org/groovy-jdk/

 

Guillaume Jeudy – JAVA DEVELOPER
Java and Open Source Application Development – Montreal Solutions Centre
1801, McGill College Avenue, Suite 1100
Montreal, QC, H3A 2N4

gjeudy@... 
W: [phone]           F: [phone]

 

---

From: Ronny Løvtangen [mailto:lists@...] 
Sent: Monday, November 02, 2009 4:07 PM
To: user@...
Subject: Re: [groovy-user] GDK methods documentation in eclipse plugin

 

Sounds like you need to tell Eclipse where to find the source jar, or the javadoc jar / javadoc url.

If you use maven then I guess this should be set up automaticly, at least it does in IntelliJ IDEA. But you need trigger a download of the sources/javadoc to your ~/.m2/repos folder, either from mvn command line, or from some Eclipse equivalent to IntelliJ's "download sources" button.

If you aren't using maven then you need to set up this manually in Eclipse. I don't know where since I use IntelliJ, but I'm sure you'll find it close to where you configure your dependent jars.

 

 

Ronny

 

On Nov 2, 2009, at 9:47 PM, Jeudy, Guillaume wrote:

 

Hi,

 

Are there any plans or existing workarounds to get GDK method documentation integrated in the Eclipse IDE plugin? Currently I’m able to pull-up GDK methods with the code assist (ctrl + space) feature but no javadoc or groovydoc come up to describe the GDK methods.

 

I’m using the latest V2 plugin with eclipse 3.5.

 

Thank you,

Regards,

Guillaume Jeudy – JAVA DEVELOPER
Java and Open Source Application Development – Montreal Solutions Centre
1801, McGill College Avenue, Suite 1100
Montreal, QC, H3A 2N4

gjeudy@... 
W: [phone]           F: [phone]

 

 

 

---

This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

 

 

 

Ce courrier électronique (en incluant n'importe quels attachements) peut contenir des renseignements

qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la divulgation à quelqu'un autre

que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de ce courrier électronique

électronique ou de ses contenus (en incluant n'importe quels attachements) par les personnes autre que

le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce message par erreur, notifiez-nous

s'il vous plaît immédiatement par le courrier électronique de réponse pour que nous puissions corriger nos

dossiers intérieurs. Effacez s'il vous plaît alors le message original (en incluant n'importe quels attachements)

dans son ensemble. Merci.

 

 

douellet@... 

 

---

This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

 

 

Ce courrier électronique (en incluant n'importe quels attachements) peut contenir des renseignements

qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la divulgation à quelqu'un autre

que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de ce courrier électronique

électronique ou de ses contenus (en incluant n'importe quels attachements) par les personnes autre que

le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce message par erreur, notifiez-nous

s'il vous plaît immédiatement par le courrier électronique de réponse pour que nous puissions corriger nos

dossiers intérieurs. Effacez s'il vous plaît alors le message original (en incluant n'importe quels attachements)

dans son ensemble. Merci.

[Andrew Eisenberg]

At this point, we only allow using the groovy versions bundled with
the plugin (1.6.5 or 1.7).  This is something we will be looking at
later.

That being said, the source and the javadoc for DGM are just grabbed
from the source attachment for the groovy jars included in the
project.

On Mon, Nov 2, 2009 at 3:48 PM, Ronny Løvtangen <lists@...> wrote:

> Ok, didn't know the plugin included the groovy source. How does that cope
> with using different groovy version from the one the plugin bundles?
> At least in IntelliJ with maven, source for DGM points directly to the
> groovy-all-1.x.y-sources.jar brought in by maven.
>
> On Nov 2, 2009, at 10:29 PM, Jeudy, Guillaume wrote:
>
> Ronny,
>
> Thanks for replying, the source jar is included by the plugin for the groovy
> classes, therefore I can see documentation for those classes with no
> problems.
>
> What is lacking is the GDK methods documentation. GDK methods are the ones
> weaved at runtime on top of existing JDK
> classes. http://groovy.codehaus.org/groovy-jdk/
>
> Guillaume Jeudy – JAVA DEVELOPER
> Java and Open Source Application Development – Montreal Solutions Centre
> 1801, McGill College Avenue, Suite 1100
> Montreal, QC, H3A 2N4
> gjeudy@...
> W: [phone]           F: [phone]
>
> ________________________________
> From: Ronny Løvtangen [mailto:lists@...]
> Sent: Monday, November 02, 2009 4:07 PM
> To: user@...
> Subject: Re: [groovy-user] GDK methods documentation in eclipse plugin
>
> Sounds like you need to tell Eclipse where to find the source jar, or the
> javadoc jar / javadoc url.
> If you use maven then I guess this should be set up automaticly, at least it
> does in IntelliJ IDEA. But you need trigger a download of the
> sources/javadoc to your ~/.m2/repos folder, either from mvn command line, or
> from some Eclipse equivalent to IntelliJ's "download sources" button.
> If you aren't using maven then you need to set up this manually in Eclipse.
> I don't know where since I use IntelliJ, but I'm sure you'll find it close
> to where you configure your dependent jars.
>
>
> Ronny
>
> On Nov 2, 2009, at 9:47 PM, Jeudy, Guillaume wrote:
>
>
> Hi,
>
> Are there any plans or existing workarounds to get GDK method documentation
> integrated in the Eclipse IDE plugin? Currently I’m able to pull-up GDK
> methods with the code assist (ctrl + space) feature but no javadoc or
> groovydoc come up to describe the GDK methods.
>
> I’m using the latest V2 plugin with eclipse 3.5.
>
> Thank you,
> Regards,
> Guillaume Jeudy – JAVA DEVELOPER
> Java and Open Source Application Development – Montreal Solutions Centre
> 1801, McGill College Avenue, Suite 1100
> Montreal, QC, H3A 2N4
> gjeudy@...
> W: [phone]           F: [phone]
>
>
>
> ________________________________
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>
>
>
>
> Ce courrier électronique (en incluant n'importe quels attachements) peut
> contenir des renseignements
>
> qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la
> divulgation à quelqu'un autre
>
> que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de
> ce courrier électronique
>
> électronique ou de ses contenus (en incluant n'importe quels attachements)
> par les personnes autre que
>
> le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce
> message par erreur, notifiez-nous
>
> s'il vous plaît immédiatement par le courrier électronique de réponse pour
> que nous puissions corriger nos
>
> dossiers intérieurs. Effacez s'il vous plaît alors le message original (en
> incluant n'importe quels attachements)
>
> dans son ensemble. Merci.
>
>
>
>
>
>
>
>
> ________________________________
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>
>
>
> Ce courrier électronique (en incluant n'importe quels attachements) peut
> contenir des renseignements
>
> qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la
> divulgation à quelqu'un autre
>
> que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de
> ce courrier électronique
>
> électronique ou de ses contenus (en incluant n'importe quels attachements)
> par les personnes autre que
>
> le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce
> message par erreur, notifiez-nous
>
> s'il vous plaît immédiatement par le courrier électronique de réponse pour
> que nous puissions corriger nos
>
> dossiers intérieurs. Effacez s'il vous plaît alors le message original (en
> incluant n'importe quels attachements)
>
> dans son ensemble. Merci.
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Guillaume Jeudy]

I tried your examples and it works the same as you. The way I brought up the javadoc originally was for example by typing:

new Object().

Typing the dot brings up the code completion list of possible methods. If you select a GDK method you will not see javadoc brought up to the right of the list (for example findAll). If you select a JDK method you will get the javadoc displayed (for example finalize).

Thanks I will use F2 for the time being.

Regards,
Guillaume Jeudy - Java developer
Java and Open Source Application Development - Montreal Solutions Centre
1801, McGill College Avenue, Suite 1100
Montreal, QC, H3A 2N4
gjeudy@...
W: [phone]           F: [phone]
 
-----Original Message-----
From: andrew.eisenberg@... [mailto:andrew.eisenberg@...] On Behalf Of Andrew Eisenberg
Sent: Monday, November 02, 2009 4:57 PM
To: user@...
Subject: Re: [groovy-user] GDK methods documentation in eclipse plugin

This is working for me, so I wonder if there is something different
about your set up.

When there are multiple DGM methods with the same name, but different
arguments, hovers can sometimes get confused (since method arguments
are not always explicit in the code).

When I type this:

findAll { }

into an empty script and press F2 (keyboard shortcut to display
hovers), the correct JavaDoc appears.  When I type this:

println ""

I get this for a hover:

* void groovy.lang.Script.println(Object value)
* void org.codehaus.groovy.runtime.DefaultGroovyMethods.println(Object self)
* void groovy.lang.Script.println()

(which means that the information controller does not know which
method it should show JavaDoc for). Are you seeing different behavior?
 If so, this is likely a bug and I'd suggest that you raise a jira for
it and include the code that is failing for you.


ps- in the future, you will get a quicker response if you send
Groovy-Eclipse related questions to the
eclipse-plugin-user@... mailing list.

On Mon, Nov 2, 2009 at 2:29 PM, Jeudy, Guillaume <gjeudy@...> wrote:

> Ronny,
>
>
>
> Thanks for replying, the source jar is included by the plugin for the groovy
> classes, therefore I can see documentation for those classes with no
> problems.
>
>
>
> What is lacking is the GDK methods documentation. GDK methods are the ones
> weaved at runtime on top of existing JDK classes.
> http://groovy.codehaus.org/groovy-jdk/
>
>
>
> Guillaume Jeudy - Java developer
>
> Java and Open Source Application Development - Montreal Solutions Centre
> 1801, McGill College Avenue, Suite 1100
> Montreal, QC, H3A 2N4
>
> gjeudy@...
> W: [phone]           F: [phone]
>
>
>
> ________________________________
>
> From: Ronny Løvtangen [mailto:lists@...]
> Sent: Monday, November 02, 2009 4:07 PM
> To: user@...
> Subject: Re: [groovy-user] GDK methods documentation in eclipse plugin
>
>
>
> Sounds like you need to tell Eclipse where to find the source jar, or the
> javadoc jar / javadoc url.
>
> If you use maven then I guess this should be set up automaticly, at least it
> does in IntelliJ IDEA. But you need trigger a download of the
> sources/javadoc to your ~/.m2/repos folder, either from mvn command line, or
> from some Eclipse equivalent to IntelliJ's "download sources" button.
>
> If you aren't using maven then you need to set up this manually in Eclipse.
> I don't know where since I use IntelliJ, but I'm sure you'll find it close
> to where you configure your dependent jars.
>
>
>
>
>
> Ronny
>
>
>
> On Nov 2, 2009, at 9:47 PM, Jeudy, Guillaume wrote:
>
>
>
> Hi,
>
>
>
> Are there any plans or existing workarounds to get GDK method documentation
> integrated in the Eclipse IDE plugin? Currently I'm able to pull-up GDK
> methods with the code assist (ctrl + space) feature but no javadoc or
> groovydoc come up to describe the GDK methods.
>
>
>
> I'm using the latest V2 plugin with eclipse 3.5.
>
>
>
> Thank you,
>
> Regards,
>
> Guillaume Jeudy - JAVA DEVELOPER
> Java and Open Source Application Development - Montreal Solutions Centre
> 1801, McGill College Avenue, Suite 1100
> Montreal, QC, H3A 2N4
>
> gjeudy@...
> W: [phone]           F: [phone]
>
>
>
>
>
>
>
> ________________________________
>
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>
>
>
>
>
>
>
> Ce courrier électronique (en incluant n'importe quels attachements) peut
> contenir des renseignements
>
> qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la
> divulgation à quelqu'un autre
>
> que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de
> ce courrier électronique
>
> électronique ou de ses contenus (en incluant n'importe quels attachements)
> par les personnes autre que
>
> le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce
> message par erreur, notifiez-nous
>
> s'il vous plaît immédiatement par le courrier électronique de réponse pour
> que nous puissions corriger nos
>
> dossiers intérieurs. Effacez s'il vous plaît alors le message original (en
> incluant n'importe quels attachements)
>
> dans son ensemble. Merci.
>
>
>
>
>
>
>
>
>
> ________________________________
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from disclosure
> to anyone other than its intended recipient(s). Any dissemination or use of
> this electronic email or its contents (including any attachments) by persons
> other than the intended recipient(s) is strictly prohibited. If you have
> received this message in error, please notify us immediately by reply email
> so that we may correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>
>
>
>
>
> Ce courrier électronique (en incluant n'importe quels attachements) peut
> contenir des renseignements
>
> qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la
> divulgation à quelqu'un autre
>
> que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de
> ce courrier électronique
>
> électronique ou de ses contenus (en incluant n'importe quels attachements)
> par les personnes autre que
>
> le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce
> message par erreur, notifiez-nous
>
> s'il vous plaît immédiatement par le courrier électronique de réponse pour
> que nous puissions corriger nos
>
> dossiers intérieurs. Effacez s'il vous plaît alors le message original (en
> incluant n'importe quels attachements)
>
> dans son ensemble. Merci.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email





____________________________________________________________________________________________________
This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.

 
 
Ce courrier électronique (en incluant n'importe quels attachements) peut contenir des renseignements
qui sont donnés le privilège, confidentiel, et-ou protégés autrement de la divulgation à quelqu'un autre
que son destinataire (s) voulu. N'importe quelle diffusion ou utilisation de ce courrier électronique
électronique ou de ses contenus (en incluant n'importe quels attachements) par les personnes autre que
le destinataire (s) voulu sont sévèrement interdits. Si vous avez reçu ce message par erreur, notifiez-nous
s'il vous plaît immédiatement par le courrier électronique de réponse pour que nous puissions corriger nos
dossiers intérieurs. Effacez s'il vous plaît alors le message original (en incluant n'importe quels attachements)
dans son ensemble. Merci.
 
 
mailto:douellet@...

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email