Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
On Sat, 17 Dec 2022, 07:08 László Kishalmi, wrote: > I have not planned another build, just with the one with the updated > netbeansrelease.json. > Sure, that was all I actually meant by another build. Certainly not suggesting anything else should go in. I thought initially the build date in the module implementation versions was because of netbeansrelease.json not being updated, but it's not. It's a bug we'll have to live with for 16u1 and try to resolve by 17. Thanks, Neil >
Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Hi Neil! I have not planned another build, just with the one with the updated netbeansrelease.json. I was swamped with work this week, so I need to assess the situation and feedback during the weekend. Both mentioned feature requests are doable for NB17 On Fri, Dec 16, 2022 at 2:03 AM Neil C Smith wrote: > On Fri, 16 Dec 2022 at 07:31, Ernie Rael wrote: > > On 22/12/15 9:34 AM, László Kishalmi wrote: > > > Went ahead and merged the delivery to the release160 branch. The > update can > > > be tested by adding the following update center URL: > > > > > > > https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/artifact/dist/netbeans/nbms/updates.xml.gz > > > > Still running NetBeans on JDK-11 > > Inalled update with plugin manager > > Once it is installed, there doesn't seem to be a way to tell from > > the plugin > > manager that I'm using the new stuff, but > > org.netbeans.modules.gradle/2 [2.29.1 > > Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215] > > org.netbeans.modules.gradle.java [1.20.1.1 > > Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215] > > Will do some testing. Laszlo, I assume you're already planning > another build before vote? > > In case not, the hash and version needs to go into > > https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json > before the build for the vote is triggered. > > Comment initially prompted by seeing the above implementation / build > version with date rather than hash showing up. That actually appears > to be another issue. As far as I can tell we have a bunch of modules > where the implementation version in the update centre is different to > the IDE build?! > > > BTW, it would be nice if the gradle version of the project was display > > somewhere in the project's properties. > > +1. > > +2 if the UI supported updating the Gradle project wrapper next to that! > :-) > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: [RELEASES] NBM module spec versions
On Fri, 16 Dec 2022 at 10:13, Neil C Smith wrote: > Something to put on the radar for NB17 schedule anyway. Haven't had a > chance to look at why yet. Guess we missed something when we > originally looked at using the hash here? Spot the deliberate mistake in the subject line - module *implementation* versions! :-) I think we might want to make sure buildnumber is passed in to the sub-ant property inside build-nbms? It's calculated wrongly in all those invocations according to the log, although haven't looked at why not all modules are affected by that. Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: [RELEASES] NBM module spec versions
Hi Neil, About 90 entry with implementation build and date. I have no idea why. Jar are wrong too they contains date or hash depending on unknow factor. Best Regards Eric -Message d'origine- De : Neil C Smith Envoyé : vendredi 16 décembre 2022 11:14 À : Eric Barboni Cc : dev Objet : [RELEASES] NBM module spec versions Hi Eric, Just noticed while looking at Laszlo's Gradle update post that we have a bunch of modules in the update centre for the IDE where the implementation version in the NBM, catalog and module JAR appear to still be the build and date. Whereas in the IDE itself the same modules are getting the version and git hash as everything else. That includes org.netbeans.modules.gradle/2 and org.netbeans.modules.gradle.java Something to put on the radar for NB17 schedule anyway. Haven't had a chance to look at why yet. Guess we missed something when we originally looked at using the hash here? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[RELEASES] NBM module spec versions
Hi Eric, Just noticed while looking at Laszlo's Gradle update post that we have a bunch of modules in the update centre for the IDE where the implementation version in the NBM, catalog and module JAR appear to still be the build and date. Whereas in the IDE itself the same modules are getting the version and git hash as everything else. That includes org.netbeans.modules.gradle/2 and org.netbeans.modules.gradle.java Something to put on the radar for NB17 schedule anyway. Haven't had a chance to look at why yet. Guess we missed something when we originally looked at using the hash here? Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
On Fri, 16 Dec 2022 at 07:31, Ernie Rael wrote: > On 22/12/15 9:34 AM, László Kishalmi wrote: > > Went ahead and merged the delivery to the release160 branch. The update can > > be tested by adding the following update center URL: > > > > https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/artifact/dist/netbeans/nbms/updates.xml.gz > > Still running NetBeans on JDK-11 > Inalled update with plugin manager > Once it is installed, there doesn't seem to be a way to tell from > the plugin > manager that I'm using the new stuff, but > org.netbeans.modules.gradle/2 [2.29.1 > Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215] > org.netbeans.modules.gradle.java [1.20.1.1 > Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215] Will do some testing. Laszlo, I assume you're already planning another build before vote? In case not, the hash and version needs to go into https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json before the build for the vote is triggered. Comment initially prompted by seeing the above implementation / build version with date rather than hash showing up. That actually appears to be another issue. As far as I can tell we have a bunch of modules where the implementation version in the update centre is different to the IDE build?! > BTW, it would be nice if the gradle version of the project was display > somewhere in the project's properties. +1. +2 if the UI supported updating the Gradle project wrapper next to that! :-) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
