On 25/09/15 2:49 PM, Pablo Rodriguez Pina wrote:
Been 3 days going crazy, not even grok, chatgpt or gemini can help me
(and they have tried hard)
Is it possible to use NbMavenProject from a plugin that i make if my
plugin is not a "friend dependency" Nomatter what i try, the plugins
classloader wont make see it at runtime.
On 25/09/16 2:41 AM, Pablo Rodriguez Pina wrote:
Why can it not be public? is there any "reason"?
I mentioned this, yenta, to provide a way for you to move forward today.
I'm not familiar with NbMavenProject and don't know what, if any,
implications there might be to granting unfettered access to that
module. It may be that a public interface should be provided that gives
only partial access. I have no implicit recommendation on whether or not
to make some module globally public and/or whether or not your plugin
should be listed as a "friend". But every method should be checked for
potential problems.
Consider that if yenta is used by your plugin, actually invoking it
could be conditioned on the NB version. This would allow your plugin to
operate on NB today, and have a yenta hack disabled when there's an NB
version available that would run your plugin.
-ernie
How do you ask the developers to make it public, is that on a different
list or on github?
On Tue, Sep 16, 2025 at 3:49 AM Ernie Rael <[email protected]> wrote:
On 25/09/15 2:49 PM, Pablo Rodriguez Pina wrote:
> Been 3 days going crazy, not even grok, chatgpt or gemini can help me
> (and they have tried hard)
>
> Is it possible to use NbMavenProject from a plugin that i make if my
> plugin is not a "friend dependency" Nomatter what i try, the plugins
> classloader wont make see it at runtime.
There's https://github.com/timboudreau/yenta. With caveats and no support.
-ernie
