You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Martin Klähn <gr...@gmail.com> on 2019/03/10 15:03:40 UTC
Why does deactivation of Gradle Plugin force deactivation of Groovy Plugin?
Hi,
for one reason or another I've attempted to test the gradle plugin from
Attila with Netbeans 11.0-vc2 and came across a disturbing revelation.
Before attempting to install the "new" plugin I wanted to deactivate the
integrated Gradle plugin as I did not want to have two competing plugins
providing the same features. However in the process of deactivating Gradle
I was warned that the Groovy plugin will have to be deactivated too due to
it requiring the Gradle plugin.
This seems wrong.
I can understand that the Gradle plugin will require the Groovy plugin.
However the other way around I can not understand.
Comments?
Regards
- Martin
Re: Why does deactivation of Gradle Plugin force deactivation of
Groovy Plugin?
Posted by Laszlo Kishalmi <la...@gmail.com>.
The issue filter should be pub;ic by now, thanks.
On 3/11/19 6:20 AM, Mike Billman wrote:
> More a curiosity thing...in the changes from vc2, I just see a window that says
>
> Jira project doesn't exist or you don't have permission to view it.
>
> View these issues in Jira
>
> If I click on the link, I see:
>
> A value with ID '12345794' does not exist for the field 'filter'.
>
> Mike
>
> -----Original Message-----
> From: Laszlo Kishalmi <la...@gmail.com>
> Sent: Sunday, March 10, 2019 11:40 AM
> To: dev@netbeans.incubator.apache.org
> Subject: Re: Why does deactivation of Gradle Plugin force deactivation of Groovy Plugin?
>
> https://issues.apache.org/jira/browse/NETBEANS-1976
>
> On 3/10/19 8:03 AM, Martin Klähn wrote:
>> Hi,
>>
>> for one reason or another I've attempted to test the gradle plugin
>> from Attila with Netbeans 11.0-vc2 and came across a disturbing revelation.
>> Before attempting to install the "new" plugin I wanted to deactivate
>> the integrated Gradle plugin as I did not want to have two competing
>> plugins providing the same features. However in the process of
>> deactivating Gradle I was warned that the Groovy plugin will have to
>> be deactivated too due to it requiring the Gradle plugin.
>>
>> This seems wrong.
>>
>> I can understand that the Gradle plugin will require the Groovy plugin.
>> However the other way around I can not understand.
>>
>> Comments?
>>
>> Regards
>> - Martin
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Why does deactivation of Gradle Plugin force deactivation of
Groovy Plugin?
Posted by Mike Billman <mi...@qcsoftware.com>.
More a curiosity thing...in the changes from vc2, I just see a window that says
Jira project doesn't exist or you don't have permission to view it.
View these issues in Jira
If I click on the link, I see:
A value with ID '12345794' does not exist for the field 'filter'.
Mike
-----Original Message-----
From: Laszlo Kishalmi <la...@gmail.com>
Sent: Sunday, March 10, 2019 11:40 AM
To: dev@netbeans.incubator.apache.org
Subject: Re: Why does deactivation of Gradle Plugin force deactivation of Groovy Plugin?
https://issues.apache.org/jira/browse/NETBEANS-1976
On 3/10/19 8:03 AM, Martin Klähn wrote:
> Hi,
>
> for one reason or another I've attempted to test the gradle plugin
> from Attila with Netbeans 11.0-vc2 and came across a disturbing revelation.
> Before attempting to install the "new" plugin I wanted to deactivate
> the integrated Gradle plugin as I did not want to have two competing
> plugins providing the same features. However in the process of
> deactivating Gradle I was warned that the Groovy plugin will have to
> be deactivated too due to it requiring the Gradle plugin.
>
> This seems wrong.
>
> I can understand that the Gradle plugin will require the Groovy plugin.
> However the other way around I can not understand.
>
> Comments?
>
> Regards
> - Martin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Why does deactivation of Gradle Plugin force deactivation of
Groovy Plugin?
Posted by Laszlo Kishalmi <la...@gmail.com>.
https://issues.apache.org/jira/browse/NETBEANS-1976
On 3/10/19 8:03 AM, Martin Klähn wrote:
> Hi,
>
> for one reason or another I've attempted to test the gradle plugin from
> Attila with Netbeans 11.0-vc2 and came across a disturbing revelation.
> Before attempting to install the "new" plugin I wanted to deactivate the
> integrated Gradle plugin as I did not want to have two competing plugins
> providing the same features. However in the process of deactivating Gradle
> I was warned that the Groovy plugin will have to be deactivated too due to
> it requiring the Gradle plugin.
>
> This seems wrong.
>
> I can understand that the Gradle plugin will require the Groovy plugin.
> However the other way around I can not understand.
>
> Comments?
>
> Regards
> - Martin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists