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.wiele...@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 <steeleh...@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 >> >
