You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@netbeans.apache.org by Peter Steele <st...@gmail.com> on 2019/02/09 06:33:21 UTC
Help on setting up licenses for new builds
Hi
I am testing the new gradle build, which is going well. But I have noticed
the license template functionality has changed.
Previously there used to be a box to enter the organization, this has now
dissapeared? Where is the replacement box located? Why was it removed?
Previously I created a profile and just applied that profile to projects,
now I need to select either a global license or use a gradle defined
license.which is set using a netbeans.license property. The options for
values here are to use absolute paths or short codes for the license I want
to use. The question is what are these short codes? I tried some obvious
examples for the license I want but it didn't work. Is there a list
somewhere?
Thanks
Peter
Re: Help on setting up licenses for new builds
Posted by Peter Steele <st...@gmail.com>.
Apologies but I have been ill recently so didn;t get a chance to create s
JIRA. I have now created https://issues.apache.org/jira/browse/NETBEANS-2138
On Mon, Feb 11, 2019 at 3:03 PM Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Just "gradle" should be fine.
>
> Gj
>
> On Mon, Feb 11, 2019 at 4:00 PM Peter Steele <st...@gmail.com> wrote:
>
>> Yes sure, I'll try and consolidate all my feedback in to one jira issue.
>> Are there any specific tags required in the Jira to flag it as a new
>> gradle issue?
>>
>> On Mon, 11 Feb 2019, 14:38 Geertjan Wielenga <
>> geertjan.wielenga@googlemail.com wrote:
>>
>>> Yes, these are completely different supports for Gradle in Apache
>>> NetBeans.
>>>
>>> Can you explain in detail what is missing, ideally via an issue, so that
>>> it can be added?
>>>
>>> Yes, feedback is great, an issue with full description will help Laszlo
>>> and others working on this support to understand what is needed, what is
>>> missing.
>>>
>>> Can you help?
>>>
>>> Gj
>>>
>>>
>>> On Mon, Feb 11, 2019 at 3:35 PM Peter Steele <st...@gmail.com>
>>> wrote:
>>>
>>>> New build equals the new builds with the new gradle functionality built
>>>> in rather than the gradle plugin. You sent another email previously asking
>>>> for testers and I have been testing and providing feedback.
>>>>
>>>> To avoid making the other email trail too large I started a separate
>>>> email trail with some specific feedback here.
>>>>
>>>> The summary is that the licencing for a gradle project is different in
>>>> the new build compared to Apache 10 build with the plugin. It's not really
>>>> useable in my mind.
>>>>
>>>> I'm not a developer of netbeans, I'm just reporting feedback.
>>>>
>>>> On Mon, 11 Feb 2019, 14:07 Geertjan Wielenga <
>>>> geertjan.wielenga@googlemail.com wrote:
>>>>
>>>>> I don't really understand the context -- what is "the new gradle
>>>>> build", for example? Do note that the Gradle support that is in the Apache
>>>>> NetBeans GitHub is different to the Gradle plugin -- i.e., this is a long
>>>>> story, but the point is that if you've been using the external Gradle
>>>>> plugin by Attila, then you need to be aware that the Gradle support
>>>>> integrated into Apache NetBeans GitHub by Laszlo is completely different.
>>>>> Missing a feature? Great -- file an issue and, ideally, provide a pull
>>>>> request.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Gj
>>>>>
>>>>>
>>>>> On Sat, Feb 9, 2019 at 7:33 AM Peter Steele <st...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> I am testing the new gradle build, which is going well. But I have
>>>>>> noticed the license template functionality has changed.
>>>>>>
>>>>>> Previously there used to be a box to enter the organization, this has
>>>>>> now dissapeared? Where is the replacement box located? Why was it removed?
>>>>>>
>>>>>> Previously I created a profile and just applied that profile to
>>>>>> projects, now I need to select either a global license or use a gradle
>>>>>> defined license.which is set using a netbeans.license property. The options
>>>>>> for values here are to use absolute paths or short codes for the license I
>>>>>> want to use. The question is what are these short codes? I tried some
>>>>>> obvious examples for the license I want but it didn't work. Is there a list
>>>>>> somewhere?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Peter
>>>>>>
>>>>>
Re: Help on setting up licenses for new builds
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Just "gradle" should be fine.
Gj
On Mon, Feb 11, 2019 at 4:00 PM Peter Steele <st...@gmail.com> wrote:
> Yes sure, I'll try and consolidate all my feedback in to one jira issue.
> Are there any specific tags required in the Jira to flag it as a new
> gradle issue?
>
> On Mon, 11 Feb 2019, 14:38 Geertjan Wielenga <
> geertjan.wielenga@googlemail.com wrote:
>
>> Yes, these are completely different supports for Gradle in Apache
>> NetBeans.
>>
>> Can you explain in detail what is missing, ideally via an issue, so that
>> it can be added?
>>
>> Yes, feedback is great, an issue with full description will help Laszlo
>> and others working on this support to understand what is needed, what is
>> missing.
>>
>> Can you help?
>>
>> Gj
>>
>>
>> On Mon, Feb 11, 2019 at 3:35 PM Peter Steele <st...@gmail.com>
>> wrote:
>>
>>> New build equals the new builds with the new gradle functionality built
>>> in rather than the gradle plugin. You sent another email previously asking
>>> for testers and I have been testing and providing feedback.
>>>
>>> To avoid making the other email trail too large I started a separate
>>> email trail with some specific feedback here.
>>>
>>> The summary is that the licencing for a gradle project is different in
>>> the new build compared to Apache 10 build with the plugin. It's not really
>>> useable in my mind.
>>>
>>> I'm not a developer of netbeans, I'm just reporting feedback.
>>>
>>> On Mon, 11 Feb 2019, 14:07 Geertjan Wielenga <
>>> geertjan.wielenga@googlemail.com wrote:
>>>
>>>> I don't really understand the context -- what is "the new gradle
>>>> build", for example? Do note that the Gradle support that is in the Apache
>>>> NetBeans GitHub is different to the Gradle plugin -- i.e., this is a long
>>>> story, but the point is that if you've been using the external Gradle
>>>> plugin by Attila, then you need to be aware that the Gradle support
>>>> integrated into Apache NetBeans GitHub by Laszlo is completely different.
>>>> Missing a feature? Great -- file an issue and, ideally, provide a pull
>>>> request.
>>>>
>>>> Thanks,
>>>>
>>>> Gj
>>>>
>>>>
>>>> On Sat, Feb 9, 2019 at 7:33 AM Peter Steele <st...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> I am testing the new gradle build, which is going well. But I have
>>>>> noticed the license template functionality has changed.
>>>>>
>>>>> Previously there used to be a box to enter the organization, this has
>>>>> now dissapeared? Where is the replacement box located? Why was it removed?
>>>>>
>>>>> Previously I created a profile and just applied that profile to
>>>>> projects, now I need to select either a global license or use a gradle
>>>>> defined license.which is set using a netbeans.license property. The options
>>>>> for values here are to use absolute paths or short codes for the license I
>>>>> want to use. The question is what are these short codes? I tried some
>>>>> obvious examples for the license I want but it didn't work. Is there a list
>>>>> somewhere?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Peter
>>>>>
>>>>
Re: Help on setting up licenses for new builds
Posted by Peter Steele <st...@gmail.com>.
Yes sure, I'll try and consolidate all my feedback in to one jira issue.
Are there any specific tags required in the Jira to flag it as a new
gradle issue?
On Mon, 11 Feb 2019, 14:38 Geertjan Wielenga <
geertjan.wielenga@googlemail.com wrote:
> Yes, these are completely different supports for Gradle in Apache NetBeans.
>
> Can you explain in detail what is missing, ideally via an issue, so that
> it can be added?
>
> Yes, feedback is great, an issue with full description will help Laszlo
> and others working on this support to understand what is needed, what is
> missing.
>
> Can you help?
>
> Gj
>
>
> On Mon, Feb 11, 2019 at 3:35 PM Peter Steele <st...@gmail.com> wrote:
>
>> New build equals the new builds with the new gradle functionality built
>> in rather than the gradle plugin. You sent another email previously asking
>> for testers and I have been testing and providing feedback.
>>
>> To avoid making the other email trail too large I started a separate
>> email trail with some specific feedback here.
>>
>> The summary is that the licencing for a gradle project is different in
>> the new build compared to Apache 10 build with the plugin. It's not really
>> useable in my mind.
>>
>> I'm not a developer of netbeans, I'm just reporting feedback.
>>
>> On Mon, 11 Feb 2019, 14:07 Geertjan Wielenga <
>> geertjan.wielenga@googlemail.com wrote:
>>
>>> I don't really understand the context -- what is "the new gradle build",
>>> for example? Do note that the Gradle support that is in the Apache NetBeans
>>> GitHub is different to the Gradle plugin -- i.e., this is a long story, but
>>> the point is that if you've been using the external Gradle plugin by
>>> Attila, then you need to be aware that the Gradle support integrated into
>>> Apache NetBeans GitHub by Laszlo is completely different. Missing a
>>> feature? Great -- file an issue and, ideally, provide a pull request.
>>>
>>> Thanks,
>>>
>>> Gj
>>>
>>>
>>> On Sat, Feb 9, 2019 at 7:33 AM Peter Steele <st...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> I am testing the new gradle build, which is going well. But I have
>>>> noticed the license template functionality has changed.
>>>>
>>>> Previously there used to be a box to enter the organization, this has
>>>> now dissapeared? Where is the replacement box located? Why was it removed?
>>>>
>>>> Previously I created a profile and just applied that profile to
>>>> projects, now I need to select either a global license or use a gradle
>>>> defined license.which is set using a netbeans.license property. The options
>>>> for values here are to use absolute paths or short codes for the license I
>>>> want to use. The question is what are these short codes? I tried some
>>>> obvious examples for the license I want but it didn't work. Is there a list
>>>> somewhere?
>>>>
>>>> Thanks
>>>>
>>>> Peter
>>>>
>>>
Re: Help on setting up licenses for new builds
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Yes, these are completely different supports for Gradle in Apache NetBeans.
Can you explain in detail what is missing, ideally via an issue, so that it
can be added?
Yes, feedback is great, an issue with full description will help Laszlo and
others working on this support to understand what is needed, what is
missing.
Can you help?
Gj
On Mon, Feb 11, 2019 at 3:35 PM Peter Steele <st...@gmail.com> wrote:
> New build equals the new builds with the new gradle functionality built in
> rather than the gradle plugin. You sent another email previously asking for
> testers and I have been testing and providing feedback.
>
> To avoid making the other email trail too large I started a separate email
> trail with some specific feedback here.
>
> The summary is that the licencing for a gradle project is different in the
> new build compared to Apache 10 build with the plugin. It's not really
> useable in my mind.
>
> I'm not a developer of netbeans, I'm just reporting feedback.
>
> On Mon, 11 Feb 2019, 14:07 Geertjan Wielenga <
> geertjan.wielenga@googlemail.com wrote:
>
>> I don't really understand the context -- what is "the new gradle build",
>> for example? Do note that the Gradle support that is in the Apache NetBeans
>> GitHub is different to the Gradle plugin -- i.e., this is a long story, but
>> the point is that if you've been using the external Gradle plugin by
>> Attila, then you need to be aware that the Gradle support integrated into
>> Apache NetBeans GitHub by Laszlo is completely different. Missing a
>> feature? Great -- file an issue and, ideally, provide a pull request.
>>
>> Thanks,
>>
>> Gj
>>
>>
>> On Sat, Feb 9, 2019 at 7:33 AM Peter Steele <st...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> I am testing the new gradle build, which is going well. But I have
>>> noticed the license template functionality has changed.
>>>
>>> Previously there used to be a box to enter the organization, this has
>>> now dissapeared? Where is the replacement box located? Why was it removed?
>>>
>>> Previously I created a profile and just applied that profile to
>>> projects, now I need to select either a global license or use a gradle
>>> defined license.which is set using a netbeans.license property. The options
>>> for values here are to use absolute paths or short codes for the license I
>>> want to use. The question is what are these short codes? I tried some
>>> obvious examples for the license I want but it didn't work. Is there a list
>>> somewhere?
>>>
>>> Thanks
>>>
>>> Peter
>>>
>>
Re: Help on setting up licenses for new builds
Posted by Peter Steele <st...@gmail.com>.
New build equals the new builds with the new gradle functionality built in
rather than the gradle plugin. You sent another email previously asking for
testers and I have been testing and providing feedback.
To avoid making the other email trail too large I started a separate email
trail with some specific feedback here.
The summary is that the licencing for a gradle project is different in the
new build compared to Apache 10 build with the plugin. It's not really
useable in my mind.
I'm not a developer of netbeans, I'm just reporting feedback.
On Mon, 11 Feb 2019, 14:07 Geertjan Wielenga <
geertjan.wielenga@googlemail.com wrote:
> I don't really understand the context -- what is "the new gradle build",
> for example? Do note that the Gradle support that is in the Apache NetBeans
> GitHub is different to the Gradle plugin -- i.e., this is a long story, but
> the point is that if you've been using the external Gradle plugin by
> Attila, then you need to be aware that the Gradle support integrated into
> Apache NetBeans GitHub by Laszlo is completely different. Missing a
> feature? Great -- file an issue and, ideally, provide a pull request.
>
> Thanks,
>
> Gj
>
>
> On Sat, Feb 9, 2019 at 7:33 AM Peter Steele <st...@gmail.com> wrote:
>
>> Hi
>>
>> I am testing the new gradle build, which is going well. But I have
>> noticed the license template functionality has changed.
>>
>> Previously there used to be a box to enter the organization, this has now
>> dissapeared? Where is the replacement box located? Why was it removed?
>>
>> Previously I created a profile and just applied that profile to projects,
>> now I need to select either a global license or use a gradle defined
>> license.which is set using a netbeans.license property. The options for
>> values here are to use absolute paths or short codes for the license I want
>> to use. The question is what are these short codes? I tried some obvious
>> examples for the license I want but it didn't work. Is there a list
>> somewhere?
>>
>> Thanks
>>
>> Peter
>>
>
Re: Help on setting up licenses for new builds
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
I don't really understand the context -- what is "the new gradle build",
for example? Do note that the Gradle support that is in the Apache NetBeans
GitHub is different to the Gradle plugin -- i.e., this is a long story, but
the point is that if you've been using the external Gradle plugin by
Attila, then you need to be aware that the Gradle support integrated into
Apache NetBeans GitHub by Laszlo is completely different. Missing a
feature? Great -- file an issue and, ideally, provide a pull request.
Thanks,
Gj
On Sat, Feb 9, 2019 at 7:33 AM Peter Steele <st...@gmail.com> wrote:
> Hi
>
> I am testing the new gradle build, which is going well. But I have noticed
> the license template functionality has changed.
>
> Previously there used to be a box to enter the organization, this has now
> dissapeared? Where is the replacement box located? Why was it removed?
>
> Previously I created a profile and just applied that profile to projects,
> now I need to select either a global license or use a gradle defined
> license.which is set using a netbeans.license property. The options for
> values here are to use absolute paths or short codes for the license I want
> to use. The question is what are these short codes? I tried some obvious
> examples for the license I want but it didn't work. Is there a list
> somewhere?
>
> Thanks
>
> Peter
>