Re: Netbeans Plugin-Development and dependent Plugins

Hi,

I can speak for the Gradle plugin since I'm the author: I personally
install a version of NetBeans which already contains the Groovy plugin, so
there is simply no such issue for me. If I run the project in NB, it will
work without any adjustment. In the general case, I'm not sure but you
should look at  Radim's NBM plugin (
https://github.com/radimk/gradle-nbm-plugin). I don't know if it supports
what you want or not because I have never took my time to port my build to
use his plugin. However, even if his plugin does not properly support such
dependencies, my recommendation is to add support there.

As for other build tools: If I remember correctly, the Ant build is able to
recognize such dependencies, if you have the other modul's sources. And for
Maven, you have to depend on the .jar of the modul and I think it will work
but you might check out the Gradle JavaEE support project at
https://github.com/hildo/netbeans-gradle-javaee-project. That said, someone
else is most likely capable of answering how the NB module system should
work.

bye,
Attila Kelemen

2016-10-08 11:08 GMT+02:00 geertjan wielenga <[email protected]>:

> Hi Attila,
>
> Can you help?
>
> Gj
>
> On 7-10-2016 23:22, 38leinaD wrote:
>
>> Hi,
>> I am currently looking into the netbeans gradle plugin
>> https://github.com/kelemen/netbeans-gradle-project and am wondering what
>> is the right way to actually test/run the plugin in my development
>> enviornment when it depends on another plugin? I.e. this plugin depends on
>> Groovy-Grails Plugin.
>> I am not sure if the situation is complicated by the fact that the
>> netbeans-gradle-project actually builds itself by a groovy build.
>> What i habe been doing up to know is:
>>
>> 1. "gradle run" t build and run the IDE with the netbeans-gradle-project
>> installed.
>> 2. Due to the dependency on Groovy-Grails plugin it tells me about the
>> missing dependency on startup so, the plugin is deactivated.
>> 3. I install the Groovy-Grails plugin manually via teh plugin manager
>> 4. I run "gradle run" again.
>>
>> I assume when i will do a clean build i have to install the plugin again.
>> Also, it seems like manual work that should be possible to do in an
>> automated way.
>>
>> Can someone give me a hint how other people go about developing plugins
>> that have dependcies on other plugin? Does no even have to be specifially
>> for gradle-based build. Maybe i can interpolate how others are solving it
>> for ant/maven-based plugin-build...
>>
>> Thanks in advance,
>> Daniel
>>
>>
>>
>>
>>
>