You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Travis (JIRA)" <ji...@apache.org> on 2019/04/04 21:09:00 UTC

[jira] [Comment Edited] (NETBEANS-1976) Play fair with Attila Kelemen's Gradle plugin

    [ https://issues.apache.org/jira/browse/NETBEANS-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810287#comment-16810287 ] 

Travis edited comment on NETBEANS-1976 at 4/4/19 9:08 PM:
----------------------------------------------------------

I was testing Netbeans 11 vc4 and lost some time due to confusion about this.  Although the new "Gradle" and "Groovy and Gradle" plugins automatically disable themselves, this isn't good enough to avoid various conflicts with the old "Gradle Support" plugin.  I had to uninstall the new "Gradle" and "Groovy and Gradle" plugins in order to get everything working with the old plugin on Netbeans 11.

My understanding from the discussion above is that you can't do much better without more work.  That means everyone who wants to keep using the old Gradle Support plugin will have to learn this new magic dance of uninstallation of built-in plugins.  I've filed a ticket against the old plugin to see if this can be better documented, and if there is any way for the old plugin to issue helpful warnings if the new plugins are also installed alongside it.

[https://github.com/kelemen/netbeans-gradle-project/issues/429]


was (Author: furrer):
I was testing Netbeans 11 vc4 and lost some time due to confusion about this.  Although the new "Gradle" and "Groovy and Gradle" plugins automatically disable themselves, this isn't good enough to avoid various conflicts with the old "Gradle Support" plugin.  I had to uninstall the new "Gradle" and "Groovy and Gradle" plugins in order to get everything working with the old plugin on Netbeans 11.

My understanding from the discussion above is that you can't do much better without more work.  That means everyone who wants to keep using the old Gradle Support plugin will have to learn this new magic dance of uninstallation of built-in plugins.  I'll go file a ticket against the old plugin to see if this can be better documented, and if there is any way for the old plugin to issue helpful warnings if the new plugins are also installed alongside it.

> Play fair with Attila Kelemen's Gradle plugin
> ---------------------------------------------
>
>                 Key: NETBEANS-1976
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-1976
>             Project: NetBeans
>          Issue Type: Improvement
>          Components: projects - Gradle
>            Reporter: Laszlo Kishalmi
>            Assignee: Laszlo Kishalmi
>            Priority: Major
>              Labels: 11.0-vc4, pull-request-available
>             Fix For: 11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If Attila's plugin is installed the default NetBeans plugin shall display an information on this case and shall not initialize.
> The position of the NbGradleProjectFactory shall be much higher than 0 probably 600 or 650



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists