2013/9/20 Adam Murdoch [via Gradle] <
ml-node+s1045684n5711888...@n5.nabble.com>
> Hi,
>
> Can you give a bit more detail about what you're doing here? Are you
> connecting the debugger to the build process or the IDE project? Does it
> work when you use the old API? Are you using embedded mode (ie
> DefaultGradleConnector.embedded(true))?
>
- not embedded mode.
- I'm connecting the debugger to the process started by the "debug" task
(which is a JavaExec of the project).
- Everything works if I'm not using the new API. Actually, if I "attach" to
a process before accessing the new API everything seems to work fine. It
only fails, if I use the new API before debugging.
>
> As an experiment, can you try adding this to FilteringClassLoader's
> constructor:
>
> allowPackage("com.sun.jdi");
>
Sure, I'll give it a try tomorrow.
>
>
> On 18/09/2013, at 7:31 AM, kelemen <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=5711888&i=0>>
> wrote:
>
> Hi Adam,
>
> After using the new API, I have the following issue: If I try to attach to
> a process (JDPA), NetBeans reports a LinkageError. I'm not sure what
> exactly happens but here is the stacktrace:
> https://gist.github.com/kelemen/6600845. This is currently a blocking
> issue for me because I'm yet to find a workaround.
>
> ------------------------------
> View this message in context: Re: Proposal for retrieving multiple types
> of models from a project in a single pass, using the Tooling
> API<http://gradle.1045684.n5.nabble.com/Proposal-for-retrieving-multiple-types-of-models-from-a-project-in-a-single-pass-using-the-Tooling-AI-tp5711516p5711874.html>
> Sent from the gradle-dev mailing list
> archive<http://gradle.1045684.n5.nabble.com/gradle-dev-f1436218.html>at
> Nabble.com.
>
>
>
> --
> Adam Murdoch
> Gradle Co-founder
> http://www.gradle.org
> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
> http://www.gradleware.com
>
> Join us at the Gradle eXchange 2013, Oct 28th in London, UK:
> http://skillsmatter.com/event/java-jee/gradle-exchange-2013
>
>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://gradle.1045684.n5.nabble.com/Proposal-for-retrieving-multiple-types-of-models-from-a-project-in-a-single-pass-using-the-Tooling-AI-tp5711516p5711888.html
> To unsubscribe from Proposal for retrieving multiple types of models from
> a project in a single pass, using the Tooling API, click
> here<http://gradle.1045684.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5711516&code=YXR0aWxhLmtlbGVtZW44NUBnbWFpbC5jb218NTcxMTUxNnwtMTMxMjM2NTcwMA==>
> .
> NAML<http://gradle.1045684.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Proposal-for-retrieving-multiple-types-of-models-from-a-project-in-a-single-pass-using-the-Tooling-AI-tp5711516p5711890.html
Sent from the gradle-dev mailing list archive at Nabble.com.
