Re: [VOTE] Release Apache NetBeans 11.2-u1 update
+1 - build runs clean, and successful - verified the checksum and the signature Thanks for your had work! Kai On 11/27/2019 4:21 PM, Neil C Smith wrote: Dear all, This is the voting candidate for the 11.2 update 1 release of Apache NetBeans. This release is identical to 11.2 except for backported fixes for - [NETBEANS-3257] Fixed issue on refactoring rename of java method (and potentially other nb-javac issues) [NETBEANS-3335] Enhance robustness of HTML Lexer - enter key doesn't work in certain files [NETBEANS-3290] Fix common.xml causing layer build problems in RCP applications Note you are required to check both sources and convenience binaries before voting! See requirements below, as well as information on a temporary voting update centre for use with 11.2. Build artefacts are available here: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/ They were built by the Jenkins pipeline at: https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/35/ We are primarily voting on: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/netbeans-11.2-u1-source.zip SHA512: 815364dc3e87135e5a1ca20f4765a695cb4a922dc60b0b7da38ed2a34f8a4f0251b1b96b06479969a8e17b65dafeac016506598b2845b942bd0587b3007750c0 ./netbeans-11.2-u1-source.zip KEYS file: https://dist.apache.org/repos/dist/release/netbeans/KEYS Before voting +1 you are required to download the signed source code package, compile it as provided, and test the resulting executable on your own platform, along with also verifying that the package meets the requirements of the ASF policy on releases - see http://www.apache.org/legal/release-policy.html#management In particular, you should (at least) follow these steps. 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files, except for: - platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar which are only jars by their name 3. Verify the cryptographic signatures, the NOTICE and LICENSE file 4. Build it using the README provided by the artefact. 5. Look in nbbuild/netbeans for the NetBeans installation created by the build process and try running it. In addition to checking the sources, you should check the associated convenience binary NBMs at the artefact links above. As well as checking any artefact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source being voted on is sufficient to build the relevant binary. You can test update of the IDE using the provided NBMs by adding a temporary update centre in Tools / Plugins / Settings. You may wish to use a temporary install or userdir for this! https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 The updated NBM files are JAR signed with an ASF certificate, so will show as Third-Party but at least Signed and Valid. A second round of updates will download the actual updated nb-javac libraries - unfortunately, due to the current temporary keystore used in the build process, the nb-javac updates will show as self-signed - I do not believe we have any way to fix that for 11.2. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC member to help with voting admin. If and when this vote passes, the updated source and NBMs will be released on to the mirrors, and the updated catalog (as per above) merged into the existing update centre on the NetBeans VM. Thank you for all the hard work! 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 - 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: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors
Apache rules do not go well with end user applications such as NetBeans IDE. The binary zip could be used as a baseline for building the installers and this fact itself gives it more legitimacy / security. OpenBeans could also distribute 'vanilla' NetBeans installers bundling AdoptOpenJDK. There's a small discussion about trademark here but I think it's allowed per another thread. --emi On Wed, Nov 27, 2019 at 11:51 PM Neil C Smith wrote: > > On Wed, 27 Nov 2019 at 19:41, Laszlo Kishalmi > wrote: > > I do not think that after this discussion we would get the exception > > from the board Geertjan might try to bring it up there as well. > > Well, we'll see. I personally have serious misgivings about ASF's > current position on "platform" dependencies when the world is changing > and moving to bundling that platform. And on the issue of binary > releases not being "official" - I've just signed 5 NBMs with an ASF > code certificate! I think the current position on either of these > things brings the sustainability of Java projects at ASF into > question, and particularly our long-term viability. > > I would really like a more forward thinking approach closer to > https://www.eclipse.org/org/documents/GPL_CE_Policy.php ! > > > As of me option 2 is questionable. > > Maybe! It's doable. I did start looking at doing this in an > InnoSetup based installer recently. > > > Option 3. is a bit hard to say, but if we can't produce proper > > installation packages, it would probably better to not create those > > packages at all, leave that for others. > ... > > 1. From 11.3 we remove the convenience binaries and installers from > > our download page > > If we go down that route, I don't think we should remove the binary > zip. In fact, that could be used as the basis for other people's > installers. eg. an AppImage build script could directly download and > embed that. > > There was some conversation a while back about AdoptOpenJDK making > bundled installers from our sources. That might be a good option to > follow up on again if we go down this route. I'd prefer fostering a > good relationship with a community focused distributor. > > 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 > > > - 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: [VOTE] Release Apache NetBeans 11.2-u1 update
OFF TOPIC I used wget -r -nH --cut-dirs=6 https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/nbms to fetch the individual artifacts. I expected to see only the nbms directory. I was surprised to see $ ls index.html netbeans-11.2-u1-source.zip netbeans-11.2-u1-source.zip.sha512 robots.txt nbms netbeans-11.2-u1-source.zip.asc README.md It fetched all the files on the way down to nbms, overwrote index.html a lot .Did I screw up the command invocation? -ernie On 11/27/2019 4:42 PM, Ernie Rael wrote: On 11/27/2019 3:11 PM, Neil C Smith wrote: On Wed, 27 Nov 2019, 22:56 Ernie Rael, wrote: Is the "nbms/" or "nbms/java" intended? Yes, [snip] Actually, I was wondering about the relative path, but I don't really know how these signatures are supposed to be used. Getting the stuff with "wget ..." and then "cd ...; sha512sum $(find ...)" works fine. -ernie - 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 - 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: [VOTE] Release Apache NetBeans 11.2-u1 update
+1 Using Win7, jdk1.8 Went through the checklist. While testing [NETBEANS-3257] ran into some exceptions (couldn't use Go to Symbol on test project), which also happened on 11.2. Filed [NETBEANS-3475]. -ernie On 11/27/2019 7:21 AM, Neil C Smith wrote: Dear all, This is the voting candidate for the 11.2 update 1 release of Apache NetBeans. This release is identical to 11.2 except for backported fixes for - [NETBEANS-3257] Fixed issue on refactoring rename of java method (and potentially other nb-javac issues) [NETBEANS-3335] Enhance robustness of HTML Lexer - enter key doesn't work in certain files [NETBEANS-3290] Fix common.xml causing layer build problems in RCP applications Note you are required to check both sources and convenience binaries before voting! See requirements below, as well as information on a temporary voting update centre for use with 11.2. Build artefacts are available here: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/ They were built by the Jenkins pipeline at: https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/35/ We are primarily voting on: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/netbeans-11.2-u1-source.zip SHA512: 815364dc3e87135e5a1ca20f4765a695cb4a922dc60b0b7da38ed2a34f8a4f0251b1b96b06479969a8e17b65dafeac016506598b2845b942bd0587b3007750c0 ./netbeans-11.2-u1-source.zip KEYS file: https://dist.apache.org/repos/dist/release/netbeans/KEYS Before voting +1 you are required to download the signed source code package, compile it as provided, and test the resulting executable on your own platform, along with also verifying that the package meets the requirements of the ASF policy on releases - see http://www.apache.org/legal/release-policy.html#management In particular, you should (at least) follow these steps. 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files, except for: - platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar which are only jars by their name 3. Verify the cryptographic signatures, the NOTICE and LICENSE file 4. Build it using the README provided by the artefact. 5. Look in nbbuild/netbeans for the NetBeans installation created by the build process and try running it. In addition to checking the sources, you should check the associated convenience binary NBMs at the artefact links above. As well as checking any artefact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source being voted on is sufficient to build the relevant binary. You can test update of the IDE using the provided NBMs by adding a temporary update centre in Tools / Plugins / Settings. You may wish to use a temporary install or userdir for this! https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 The updated NBM files are JAR signed with an ASF certificate, so will show as Third-Party but at least Signed and Valid. A second round of updates will download the actual updated nb-javac libraries - unfortunately, due to the current temporary keystore used in the build process, the nb-javac updates will show as self-signed - I do not believe we have any way to fix that for 11.2. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC member to help with voting admin. If and when this vote passes, the updated source and NBMs will be released on to the mirrors, and the updated catalog (as per above) merged into the existing update centre on the NetBeans VM. Thank you for all the hard work! 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 - 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: [VOTE] Release Apache NetBeans 11.2-u1 update
+1 (binding) - Checked jar files - Verified the checksum and the signature - BUILD SUCCESSFUL - Verified that [NETBEANS-3335] and [NETBEANS-3290] have been fixed - [NETBEANS-3257] I could rename a java method Thanks a lot for the work, Junichi On Thu, Nov 28, 2019 at 12:21 AM Neil C Smith wrote: > > Dear all, > > This is the voting candidate for the 11.2 update 1 release of Apache > NetBeans. This release is identical to 11.2 except for backported > fixes for - > > [NETBEANS-3257] Fixed issue on refactoring rename of java method (and > potentially other nb-javac issues) > [NETBEANS-3335] Enhance robustness of HTML Lexer - enter key doesn't > work in certain files > [NETBEANS-3290] Fix common.xml causing layer build problems in RCP > applications > > Note you are required to check both sources and convenience binaries > before voting! See requirements below, as well as information on a > temporary voting update centre for use with 11.2. > > > Build artefacts are available here: > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/ > > They were built by the Jenkins pipeline at: > https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/35/ > > We are primarily voting on: > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/netbeans-11.2-u1-source.zip > > SHA512: > 815364dc3e87135e5a1ca20f4765a695cb4a922dc60b0b7da38ed2a34f8a4f0251b1b96b06479969a8e17b65dafeac016506598b2845b942bd0587b3007750c0 > ./netbeans-11.2-u1-source.zip > > KEYS file: > https://dist.apache.org/repos/dist/release/netbeans/KEYS > > > Before voting +1 you are required to download the signed source code > package, compile it as provided, and test the resulting executable on > your own platform, along with also verifying that the package meets > the requirements of the ASF policy on releases - see > http://www.apache.org/legal/release-policy.html#management > > In particular, you should (at least) follow these steps. > > 1. Download the artefact to be voted on and unzip it. > 2. Check that the artefact does not contain any jar files, except for: > - > platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar > - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar > - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar > - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar > - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar > which are only jars by their name > 3. Verify the cryptographic signatures, the NOTICE and LICENSE file > 4. Build it using the README provided by the artefact. > 5. Look in nbbuild/netbeans for the NetBeans installation created by > the build process and try running it. > > > In addition to checking the sources, you should check the associated > convenience binary NBMs at the artefact links above. As well as > checking any artefact functions correctly, you should check that it > has been correctly signed by a PMC member, and that the source being > voted on is sufficient to build the relevant binary. > > You can test update of the IDE using the provided NBMs by adding a > temporary update centre in Tools / Plugins / Settings. You may wish to > use a temporary install or userdir for this! > > https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 > > The updated NBM files are JAR signed with an ASF certificate, so will > show as Third-Party but at least Signed and Valid. A second round of > updates will download the actual updated nb-javac libraries - > unfortunately, due to the current temporary keystore used in the build > process, the nb-javac updates will show as self-signed - I do not > believe we have any way to fix that for 11.2. > > > This vote is going to be open at least 72 hours, vote with +1, 0, and > -1 as usual. Please mark your vote with (binding) if you're an Apache > NetBeans PMC member to help with voting admin. > > If and when this vote passes, the updated source and NBMs will be > released on to the mirrors, and the updated catalog (as per above) > merged into the existing update centre on the NetBeans VM. > > > Thank you for all the hard work! > > 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 > > > - 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: [VOTE] Release Apache NetBeans 11.2-u1 update
On 11/27/2019 3:11 PM, Neil C Smith wrote: On Wed, 27 Nov 2019, 22:56 Ernie Rael, wrote: Is the "nbms/" or "nbms/java" intended? Yes, [snip] Actually, I was wondering about the relative path, but I don't really know how these signatures are supposed to be used. Getting the stuff with "wget ..." and then "cd ...; sha512sum $(find ...)" works fine. -ernie - 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: [VOTE] Release Apache NetBeans 11.2-u1 update
On Wed, 27 Nov 2019, 22:56 Ernie Rael, wrote: > Is the "nbms/" or "nbms/java" intended? > Yes, although it's normally ./nbms/java etc. Don't think lack of ./ causes a problem? I had to do them manually post-signing rather than using the ones from the build. Best wishes, Neil >
Re: [VOTE] Release Apache NetBeans 11.2-u1 update
All the sha512 signatures are of the form ...4d31bc720f637 nbms/updates.xml Is the "nbms/" or "nbms/java" intended? -ernie On 11/27/2019 7:21 AM, Neil C Smith wrote: Dear all, This is the voting candidate for the 11.2 update 1 release of Apache NetBeans. This release is identical to 11.2 except for backported fixes for - [NETBEANS-3257] Fixed issue on refactoring rename of java method (and potentially other nb-javac issues) [NETBEANS-3335] Enhance robustness of HTML Lexer - enter key doesn't work in certain files [NETBEANS-3290] Fix common.xml causing layer build problems in RCP applications Note you are required to check both sources and convenience binaries before voting! See requirements below, as well as information on a temporary voting update centre for use with 11.2. Build artefacts are available here: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/ They were built by the Jenkins pipeline at: https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/35/ We are primarily voting on: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/netbeans-11.2-u1-source.zip SHA512: 815364dc3e87135e5a1ca20f4765a695cb4a922dc60b0b7da38ed2a34f8a4f0251b1b96b06479969a8e17b65dafeac016506598b2845b942bd0587b3007750c0 ./netbeans-11.2-u1-source.zip KEYS file: https://dist.apache.org/repos/dist/release/netbeans/KEYS Before voting +1 you are required to download the signed source code package, compile it as provided, and test the resulting executable on your own platform, along with also verifying that the package meets the requirements of the ASF policy on releases - see http://www.apache.org/legal/release-policy.html#management In particular, you should (at least) follow these steps. 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files, except for: - platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar which are only jars by their name 3. Verify the cryptographic signatures, the NOTICE and LICENSE file 4. Build it using the README provided by the artefact. 5. Look in nbbuild/netbeans for the NetBeans installation created by the build process and try running it. In addition to checking the sources, you should check the associated convenience binary NBMs at the artefact links above. As well as checking any artefact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source being voted on is sufficient to build the relevant binary. You can test update of the IDE using the provided NBMs by adding a temporary update centre in Tools / Plugins / Settings. You may wish to use a temporary install or userdir for this! https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 The updated NBM files are JAR signed with an ASF certificate, so will show as Third-Party but at least Signed and Valid. A second round of updates will download the actual updated nb-javac libraries - unfortunately, due to the current temporary keystore used in the build process, the nb-javac updates will show as self-signed - I do not believe we have any way to fix that for 11.2. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC member to help with voting admin. If and when this vote passes, the updated source and NBMs will be released on to the mirrors, and the updated catalog (as per above) merged into the existing update centre on the NetBeans VM. Thank you for all the hard work! 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 - 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: [DISCUSS] Updating the quarter release for xx.3
If it is helpful, I would be willing to help with this endeavor! -brad w. On Wed, Nov 27, 2019 at 3:08 PM Neil C Smith wrote: > > Would it help in getting C/C++ support in too? Or is that waiting for > 12.1? > >
Re: Figuring out nbjavac in 11.2 is a doozy
On Wed, Nov 27, 2019 at 10:23 PM Neil C Smith wrote: > On Wed, 27 Nov 2019 at 20:13, Emilian Bold wrote: > > An exe installer would be a derivative work imho even if it bundles > > the same bits. > > > > Calling that installer NetBeans based on nominative fair user seems an > > interesting angle. > > I think it's a major stretch to call the installer derivative. It's a > separate piece of software to package the IDE. And if the IDE that it > packages is the same as upstream, then it's not a derivative. > > Now, the installer itself shouldn't be just called Apache NetBeans if > it is not developed here, but note I actually suggested use of "XXX > installer for Apache NetBeans and OpenJDK" (or "OpenBeans installer > for Apache NetBeans and OpenJDK"!) > > That seems perfectly within the scope of the permissions. In fact, > was considering building one myself. > I'd even say the installer *can* be developed here, our source code can contain a script that will build it, and if the installer is built using that script, without custom patches, then the draft policy allows it to be called Apache NetBeans (as, frankly, it would be something we have done.) Jan > > 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: [DISCUSS] Updating the quarter release for xx.3
On Thu, 7 Nov 2019 at 13:47, Neil C Smith wrote: > On Thu, 7 Nov 2019, 13:33 Eric Barboni, wrote: >> >>Can we shift by a month the schedule of xx.3 eventually whiteout messing >> quarterly release ? Allowing maybe more volunteers (me for example :D ) > > > Given problems with 11.2 related to late testing with latest JDK, I think > there's a conversation to be had about shifting the whole schedule back a > month anyway. > > If only 11.3 is a month late, that means no development *at all* before 12.0 > freeze! Bumping this! AFAIK we don't have a release manager for 11.3 yet? Doing updates I realised that there is still some documentation to update, and would be good to talk through some of this with next RM. I'm going to be really busy for most of December, and quite a few things changed during 11.2 (although Eric should be up to speed on most of them! ;-) ) I am also still of the opinion above that we should shift the whole release schedule back a month, for reasons including Eric's above. What are thoughts on that? Would it help in getting C/C++ support in too? Or is that waiting for 12.1? 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: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors
On Wed, 27 Nov 2019 at 19:41, Laszlo Kishalmi wrote: > I do not think that after this discussion we would get the exception > from the board Geertjan might try to bring it up there as well. Well, we'll see. I personally have serious misgivings about ASF's current position on "platform" dependencies when the world is changing and moving to bundling that platform. And on the issue of binary releases not being "official" - I've just signed 5 NBMs with an ASF code certificate! I think the current position on either of these things brings the sustainability of Java projects at ASF into question, and particularly our long-term viability. I would really like a more forward thinking approach closer to https://www.eclipse.org/org/documents/GPL_CE_Policy.php ! > As of me option 2 is questionable. Maybe! It's doable. I did start looking at doing this in an InnoSetup based installer recently. > Option 3. is a bit hard to say, but if we can't produce proper > installation packages, it would probably better to not create those > packages at all, leave that for others. ... > 1. From 11.3 we remove the convenience binaries and installers from > our download page If we go down that route, I don't think we should remove the binary zip. In fact, that could be used as the basis for other people's installers. eg. an AppImage build script could directly download and embed that. There was some conversation a while back about AdoptOpenJDK making bundled installers from our sources. That might be a good option to follow up on again if we go down this route. I'd prefer fostering a good relationship with a community focused distributor. 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: Figuring out nbjavac in 11.2 is a doozy
On Wed, 27 Nov 2019 at 20:13, Emilian Bold wrote: > An exe installer would be a derivative work imho even if it bundles > the same bits. > > Calling that installer NetBeans based on nominative fair user seems an > interesting angle. I think it's a major stretch to call the installer derivative. It's a separate piece of software to package the IDE. And if the IDE that it packages is the same as upstream, then it's not a derivative. Now, the installer itself shouldn't be just called Apache NetBeans if it is not developed here, but note I actually suggested use of "XXX installer for Apache NetBeans and OpenJDK" (or "OpenBeans installer for Apache NetBeans and OpenJDK"!) That seems perfectly within the scope of the permissions. In fact, was considering building one myself. 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: [VOTE] Release Apache NetBeans 11.2-u1 update
+1 Validated: - checksum for source zip is correct - contents of source is identical with repository brach release112 as of commit d54c01082b55 (differences are contrib, git directories and LICENSE file). The differenes are expected - signature of the binaries validates - build runs clean - the differences I see between binaries build locally and the offered artifacts look explainable - NOTICE and LICENSE look sane - Found NETBEANS-3335 to be fixed Thank you for the work. Am Mittwoch, den 27.11.2019, 15:21 + schrieb Neil C Smith: > Dear all, > > This is the voting candidate for the 11.2 update 1 release of Apache > NetBeans. This release is identical to 11.2 except for backported > fixes for - > > [NETBEANS-3257] Fixed issue on refactoring rename of java method (and > potentially other nb-javac issues) > [NETBEANS-3335] Enhance robustness of HTML Lexer - enter key doesn't > work in certain files > [NETBEANS-3290] Fix common.xml causing layer build problems in RCP > applications > > Note you are required to check both sources and convenience binaries > before voting! See requirements below, as well as information on a > temporary voting update centre for use with 11.2. > > > Build artefacts are available here: > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/ > > They were built by the Jenkins pipeline at: > https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/35/ > > We are primarily voting on: > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/netbeans-11.2-u1-source.zip > > SHA512: > 815364dc3e87135e5a1ca20f4765a695cb4a922dc60b0b7da38ed2a34f8a4f0251b1b > 96b06479969a8e17b65dafeac016506598b2845b942bd0587b3007750c0 > ./netbeans-11.2-u1-source.zip > > KEYS file: > https://dist.apache.org/repos/dist/release/netbeans/KEYS > > > Before voting +1 you are required to download the signed source code > package, compile it as provided, and test the resulting executable on > your own platform, along with also verifying that the package meets > the requirements of the ASF policy on releases - see > http://www.apache.org/legal/release-policy.html#management > > In particular, you should (at least) follow these steps. > > 1. Download the artefact to be voted on and unzip it. > 2. Check that the artefact does not contain any jar files, except > for: > - > platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdat > e/data/empty.jar > - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar > - enterprise/glassfish.common/test/unit/data/subdir/nottaDir- > 5.0.jar > - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar > - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar > which are only jars by their name > 3. Verify the cryptographic signatures, the NOTICE and LICENSE file > 4. Build it using the README provided by the artefact. > 5. Look in nbbuild/netbeans for the NetBeans installation created by > the build process and try running it. > > > In addition to checking the sources, you should check the associated > convenience binary NBMs at the artefact links above. As well as > checking any artefact functions correctly, you should check that it > has been correctly signed by a PMC member, and that the source being > voted on is sufficient to build the relevant binary. > > You can test update of the IDE using the provided NBMs by adding a > temporary update centre in Tools / Plugins / Settings. You may wish > to > use a temporary install or userdir for this! > > https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 > > The updated NBM files are JAR signed with an ASF certificate, so will > show as Third-Party but at least Signed and Valid. A second round of > updates will download the actual updated nb-javac libraries - > unfortunately, due to the current temporary keystore used in the > build > process, the nb-javac updates will show as self-signed - I do not > believe we have any way to fix that for 11.2. > > > This vote is going to be open at least 72 hours, vote with +1, 0, and > -1 as usual. Please mark your vote with (binding) if you're an > Apache > NetBeans PMC member to help with voting admin. > > If and when this vote passes, the updated source and NBMs will be > released on to the mirrors, and the updated catalog (as per above) > merged into the existing update centre on the NetBeans VM. > > > Thank you for all the hard work! > > 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 > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For a
Re: Figuring out nbjavac in 11.2 is a doozy
> However, we can certainly have build scripts that have optional flags > that allow anyone building from the source release to include either > of those things for themselves. That's no different to providing the > option for a binary consumer to install at runtime. And means we > don't all have to keep reinventing the wheel. Sure, and I already said I would love something like that. My patch is already done though, has 70 lines, just changes a few files. Re-doing this as a proper build system addition seems like another thing altogether. NetBeans never did have build flags like this. I guess it's not that hard to append to libs.javacapi/manifest.mf (or to have a 2nd manifest.mf for the flag) but this seems a crude solution. > You're looking at the wrong thing - that's about derivatives, not > distributing NetBeans itself. Check out the first example of > nominative fair use here and tell me that doesn't cover what you're > talking about doing! > > http://www.apache.org/foundation/marks/#guidelines An exe installer would be a derivative work imho even if it bundles the same bits. Calling that installer NetBeans based on nominative fair user seems an interesting angle. --emi On Wed, Nov 27, 2019 at 8:12 PM Neil C Smith wrote: > > On Wed, 27 Nov 2019 at 17:30, Emilian Bold wrote: > > I don't see what I'm doing as splitting the effort. If anything it's > > complementary. Can NetBeans bundle a JDK? Can it bundle nbjavac? > > Depends what you mean! Can we bundle either in our binaries - at the > moment, no, although there is still an open legal question on some of > this. > > However, we can certainly have build scripts that have optional flags > that allow anyone building from the source release to include either > of those things for themselves. That's no different to providing the > option for a binary consumer to install at runtime. And means we > don't all have to keep reinventing the wheel. > > > Looking at stuff like > > http://www.apache.org/foundation/marks/faq/#products they are clear > > that I cannot use the Apache marks. > > You're looking at the wrong thing - that's about derivatives, not > distributing NetBeans itself. Check out the first example of > nominative fair use here and tell me that doesn't cover what you're > talking about doing! > > http://www.apache.org/foundation/marks/#guidelines > > 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 > > > - 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: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors
I would be in favor of continuing as we have been doing -- providing an installer that assumes a JDK is available. Not bundling a JDK is not the end of the world though yes inconvenient and I don't think we should throw out the baby with the bathwater. Gj On Wed, Nov 27, 2019 at 8:41 PM Laszlo Kishalmi wrote: > Dear all, > > It is a great burden to us to provide the best out-of-the-box install > experience with NetBeans. That would mean, providing an installer with > JDK, nb-javac probably javafx. > > See the threads: > > > https://lists.apache.org/thread.html/a3e6051130e18aae3f7a81c562a63ac96d3a3a07d4bcbee074392d59@%3Clegal-discuss.apache.org%3E > > > https://lists.apache.org/thread.html/489f17e30d9125ee48e2d78dc36572db6a3f5d6474f492458e0db151@%3Clegal-discuss.apache.org%3E > > On 11/26/19 9:29 PM, Laszlo Kishalmi wrote: > > > > Dear all, > > > > I try to summary the lengthy threads about bundling OpenJDK GPL+CPE > > with Apache NetBeans. > > > > There are mainly two readings of GPL+CPE: > > > > 1. OpenJDK (GPL+CPE) + NetBeans (Apache) = Executable which can be > > distributed under Apache license, due to CPE > > 2. CPE only allows other product built on Java to be distributed > > under their own license. > > > > As I'm not a lawyer, I cannot answer which interpretation is correct > > (maybe none of them). ASF has every right to regard the second > > interpretation, thus GPL+CPE ended up in the Category-X licenses. > > > > The following viable possibilities were brought up: > > > > 1. We may apply for an exception to the board > > 2. Use some download logic in the installer. > > 3. Leave the binary packaging and distribution to third parties. > > > > Regarding that there are interest from third parties to built on > > Apache NetBeans, I'm going to recommend the PMC to select a few > > distributor for creating installer packages and we limit/drop our > > installer bundle creation in the future. > > > > Thank you, > > > > Laszlo Kishalmi > > > > I do not think that after this discussion we would get the exception > from the board Geertjan might try to bring it up there as well. > > As of me option 2 is questionable. > > Option 3. is a bit hard to say, but if we can't produce proper > installation packages, it would probably better to not create those > packages at all, leave that for others. > > How I imagine that: > > 1. From 11.3 we remove the convenience binaries and installers from > our download page > 2. We would still create, sign and host our nbm-s. > 3. On our download page we have the source package and a section for > third party distributors. > > Well of course this thread is just to start a discussion about this > matter. I know it would hurt the brand, but probably it is better than > produce some sub-optimal installers while other parties can come with > all the bells and whistles. > > Thank you, > > Laszlo Kishalmi >
[DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors
Dear all, It is a great burden to us to provide the best out-of-the-box install experience with NetBeans. That would mean, providing an installer with JDK, nb-javac probably javafx. See the threads: https://lists.apache.org/thread.html/a3e6051130e18aae3f7a81c562a63ac96d3a3a07d4bcbee074392d59@%3Clegal-discuss.apache.org%3E https://lists.apache.org/thread.html/489f17e30d9125ee48e2d78dc36572db6a3f5d6474f492458e0db151@%3Clegal-discuss.apache.org%3E On 11/26/19 9:29 PM, Laszlo Kishalmi wrote: Dear all, I try to summary the lengthy threads about bundling OpenJDK GPL+CPE with Apache NetBeans. There are mainly two readings of GPL+CPE: 1. OpenJDK (GPL+CPE) + NetBeans (Apache) = Executable which can be distributed under Apache license, due to CPE 2. CPE only allows other product built on Java to be distributed under their own license. As I'm not a lawyer, I cannot answer which interpretation is correct (maybe none of them). ASF has every right to regard the second interpretation, thus GPL+CPE ended up in the Category-X licenses. The following viable possibilities were brought up: 1. We may apply for an exception to the board 2. Use some download logic in the installer. 3. Leave the binary packaging and distribution to third parties. Regarding that there are interest from third parties to built on Apache NetBeans, I'm going to recommend the PMC to select a few distributor for creating installer packages and we limit/drop our installer bundle creation in the future. Thank you, Laszlo Kishalmi I do not think that after this discussion we would get the exception from the board Geertjan might try to bring it up there as well. As of me option 2 is questionable. Option 3. is a bit hard to say, but if we can't produce proper installation packages, it would probably better to not create those packages at all, leave that for others. How I imagine that: 1. From 11.3 we remove the convenience binaries and installers from our download page 2. We would still create, sign and host our nbm-s. 3. On our download page we have the source package and a section for third party distributors. Well of course this thread is just to start a discussion about this matter. I know it would hurt the brand, but probably it is better than produce some sub-optimal installers while other parties can come with all the bells and whistles. Thank you, Laszlo Kishalmi
Re: [VOTE] Release Apache NetBeans 11.2-u1 update
+1 (binding), did the above listed checks, tried to reproduce some of the related issues before/after including the update 1 release and couldn’t reproduce after including the update. Thanks a lot for this work. Gj On Wed, 27 Nov 2019 at 16:21, Neil C Smith wrote: > Dear all, > > This is the voting candidate for the 11.2 update 1 release of Apache > NetBeans. This release is identical to 11.2 except for backported > fixes for - > > [NETBEANS-3257] Fixed issue on refactoring rename of java method (and > potentially other nb-javac issues) > [NETBEANS-3335] Enhance robustness of HTML Lexer - enter key doesn't > work in certain files > [NETBEANS-3290] Fix common.xml causing layer build problems in RCP > applications > > Note you are required to check both sources and convenience binaries > before voting! See requirements below, as well as information on a > temporary voting update centre for use with 11.2. > > > Build artefacts are available here: > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/ > > They were built by the Jenkins pipeline at: > > https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/35/ > > We are primarily voting on: > > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/netbeans-11.2-u1-source.zip > > SHA512: > > 815364dc3e87135e5a1ca20f4765a695cb4a922dc60b0b7da38ed2a34f8a4f0251b1b96b06479969a8e17b65dafeac016506598b2845b942bd0587b3007750c0 > ./netbeans-11.2-u1-source.zip > > KEYS file: > https://dist.apache.org/repos/dist/release/netbeans/KEYS > > > Before voting +1 you are required to download the signed source code > package, compile it as provided, and test the resulting executable on > your own platform, along with also verifying that the package meets > the requirements of the ASF policy on releases - see > http://www.apache.org/legal/release-policy.html#management > > In particular, you should (at least) follow these steps. > > 1. Download the artefact to be voted on and unzip it. > 2. Check that the artefact does not contain any jar files, except for: > - > platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar > - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar > - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar > - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar > - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar > which are only jars by their name > 3. Verify the cryptographic signatures, the NOTICE and LICENSE file > 4. Build it using the README provided by the artefact. > 5. Look in nbbuild/netbeans for the NetBeans installation created by > the build process and try running it. > > > In addition to checking the sources, you should check the associated > convenience binary NBMs at the artefact links above. As well as > checking any artefact functions correctly, you should check that it > has been correctly signed by a PMC member, and that the source being > voted on is sufficient to build the relevant binary. > > You can test update of the IDE using the provided NBMs by adding a > temporary update centre in Tools / Plugins / Settings. You may wish to > use a temporary install or userdir for this! > > https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 > > The updated NBM files are JAR signed with an ASF certificate, so will > show as Third-Party but at least Signed and Valid. A second round of > updates will download the actual updated nb-javac libraries - > unfortunately, due to the current temporary keystore used in the build > process, the nb-javac updates will show as self-signed - I do not > believe we have any way to fix that for 11.2. > > > This vote is going to be open at least 72 hours, vote with +1, 0, and > -1 as usual. Please mark your vote with (binding) if you're an Apache > NetBeans PMC member to help with voting admin. > > If and when this vote passes, the updated source and NBMs will be > released on to the mirrors, and the updated catalog (as per above) > merged into the existing update centre on the NetBeans VM. > > > Thank you for all the hard work! > > 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: Problems compiling layer.xml for custom module
Awesome! Worked like a champ after the update using that update center link you provided. Thanks! Mark Claassen Senior Software Engineer Donnell Systems, Inc. 130 South Main Street Leighton Plaza Suite 375 South Bend, IN 46601 E-mail: mailto:mclaas...@ocie.net Voice: (574)232-3784 Fax: (574)232-4014 Disclaimer: The opinions provided herein do not necessarily state or reflect those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes no legal liability or responsibility for the posting. -Original Message- From: Neil C Smith Sent: Wednesday, November 27, 2019 11:12 AM To: dev Subject: Re: Problems compiling layer.xml for custom module On Wed, 27 Nov 2019 at 16:06, Mark A. Claassen wrote: > Wow. The Netbeans community is pretty great! I will wait for the updated > daily builds to refresh and give it a try. The daily builds should have been fixed a few days ago, but you could also try adding the temporary update centre in the vote thread to 11.2 under Tools / Plugins / Settings. Feedback on whether applying the update there fixes this issue in all cases would be welcomed. https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 Thanks, 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 - 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: Figuring out nbjavac in 11.2 is a doozy
On Wed, 27 Nov 2019 at 17:30, Emilian Bold wrote: > I don't see what I'm doing as splitting the effort. If anything it's > complementary. Can NetBeans bundle a JDK? Can it bundle nbjavac? Depends what you mean! Can we bundle either in our binaries - at the moment, no, although there is still an open legal question on some of this. However, we can certainly have build scripts that have optional flags that allow anyone building from the source release to include either of those things for themselves. That's no different to providing the option for a binary consumer to install at runtime. And means we don't all have to keep reinventing the wheel. > Looking at stuff like > http://www.apache.org/foundation/marks/faq/#products they are clear > that I cannot use the Apache marks. You're looking at the wrong thing - that's about derivatives, not distributing NetBeans itself. Check out the first example of nominative fair use here and tell me that doesn't cover what you're talking about doing! http://www.apache.org/foundation/marks/#guidelines 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: Figuring out nbjavac in 11.2 is a doozy
> > I didn't mean to involve you too much with this, just curious if my > > patch made sense. I certainly don't want to split the efforts under > > NetBeans. > > I think that was meant that you doing it separately is splitting the > effort! Ideally something to solve here. I don't see what I'm doing as splitting the effort. If anything it's complementary. Can NetBeans bundle a JDK? Can it bundle nbjavac? Some of the other features could also be in NetBeans, but I didn't manage to put them in last time when I was a committer and PMC member. Maybe someday they will be reimplemented by the right person and I can drop my variant. > > It would be great if there was a single flag in the canonical build > > that would include nb-javac but it doesn't seem obvious to me how... > > Especially considering the current nb/updatecenters/extra config. > > I wonder if the old extra cluster mechanism, as JavaFX is (was?) > doing, is easier in this respect? Some of this was discussed in > https://github.com/apache/netbeans/pull/1560 if you haven't read that? I guess? But not by much. The current patch is just fine I think and I have everything in java/libs.javacimpl / ~-api. > > I recently asked if Apache is fine with me producing a NetBeans > > installer that is only the NetBeans release + a bundled JDK. The PMC > > Chair reply was that Apache most certainly does *not* allow such a > > thing and that the project would have to be rebranded. So, for this > > reason alone a distribution is still needed. > > Really?! IMO that's something we've said multiple times we would > allow, including in a recent thread (when Debian, etc. came up). Like many other threads, the most recent one got into many areas but I'm not sure I saw a clear cut conclusion. I expressly asked about the installer then went into CoolBeans and Debian and more and come back head spinning. https://lists.apache.org/thread.html/4075e5bc05d4d5f4eb51ced4e99dfb03847d16b337259bce593a38d4@%3Cdev.netbeans.apache.org%3E The one conclusion was that NetBeans has no specific stance besides what ASF has. Looking at stuff like http://www.apache.org/foundation/marks/faq/#products they are clear that I cannot use the Apache marks. Apache seems to officially not allow their marks being used but in practice allow it (for Linux distros, etc). So, it would be nice to see this black on white. Jan's link http://www.apache.org/foundation/marks/downstream.html with a more recent draft seems a step in the right direction. Hopefully it stops being a draft and actual ASF policy. --emi - 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: Problems compiling layer.xml for custom module
On Wed, 27 Nov 2019 at 16:06, Mark A. Claassen wrote: > Wow. The Netbeans community is pretty great! I will wait for the updated > daily builds to refresh and give it a try. The daily builds should have been fixed a few days ago, but you could also try adding the temporary update centre in the vote thread to 11.2 under Tools / Plugins / Settings. Feedback on whether applying the update there fixes this issue in all cases would be welcomed. https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 Thanks, 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: Problems compiling layer.xml for custom module
Wow. The Netbeans community is pretty great! I will wait for the updated daily builds to refresh and give it a try. Mark Claassen Senior Software Engineer Donnell Systems, Inc. 130 South Main Street Leighton Plaza Suite 375 South Bend, IN 46601 E-mail: mailto:mclaas...@ocie.net Voice: (574)232-3784 Fax: (574)232-4014 Disclaimer: The opinions provided herein do not necessarily state or reflect those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes no legal liability or responsibility for the posting. -Original Message- From: Neil C Smith Sent: Wednesday, November 27, 2019 9:05 AM To: dev Subject: Re: Problems compiling layer.xml for custom module On Wed, 27 Nov 2019 at 14:01, joe foe wrote: > > This is known problem with 11.2 . See NETBEANS-3290 in netbeans JiRA. > > Alternative is to use 11.1 . I am literally as I type pushing the update that should fix this for 11.2 via SVN for update vote. Once that is done, your feedback during the vote on whether this solves that issue will be welcomed! 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 - 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
Where to put a new color scheme? Licensing...
Dear all, I might be caught up a bit with some LaF works recently. I'm working on creating two color schemes (a light and a dark) based on: https://github.com/morhetz/gruvbox/ My question is: where to put it? They are a bunch of xml files and one property file. Options: 1. IDE Defaults module: The current schemes are living in there 2. The new Flatlaf module? 3. In a separate new module. The licensing is also a good question. I do not reuse the code, but the color palette and some guidelines from there. How shall it be handled?
[VOTE] Release Apache NetBeans 11.2-u1 update
Dear all, This is the voting candidate for the 11.2 update 1 release of Apache NetBeans. This release is identical to 11.2 except for backported fixes for - [NETBEANS-3257] Fixed issue on refactoring rename of java method (and potentially other nb-javac issues) [NETBEANS-3335] Enhance robustness of HTML Lexer - enter key doesn't work in certain files [NETBEANS-3290] Fix common.xml causing layer build problems in RCP applications Note you are required to check both sources and convenience binaries before voting! See requirements below, as well as information on a temporary voting update centre for use with 11.2. Build artefacts are available here: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/ They were built by the Jenkins pipeline at: https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/35/ We are primarily voting on: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-u1/netbeans-11.2-u1-source.zip SHA512: 815364dc3e87135e5a1ca20f4765a695cb4a922dc60b0b7da38ed2a34f8a4f0251b1b96b06479969a8e17b65dafeac016506598b2845b942bd0587b3007750c0 ./netbeans-11.2-u1-source.zip KEYS file: https://dist.apache.org/repos/dist/release/netbeans/KEYS Before voting +1 you are required to download the signed source code package, compile it as provided, and test the resulting executable on your own platform, along with also verifying that the package meets the requirements of the ASF policy on releases - see http://www.apache.org/legal/release-policy.html#management In particular, you should (at least) follow these steps. 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files, except for: - platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar which are only jars by their name 3. Verify the cryptographic signatures, the NOTICE and LICENSE file 4. Build it using the README provided by the artefact. 5. Look in nbbuild/netbeans for the NetBeans installation created by the build process and try running it. In addition to checking the sources, you should check the associated convenience binary NBMs at the artefact links above. As well as checking any artefact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source being voted on is sufficient to build the relevant binary. You can test update of the IDE using the provided NBMs by adding a temporary update centre in Tools / Plugins / Settings. You may wish to use a temporary install or userdir for this! https://netbeans.apache.org/nb/updates/11.2/updates.xml.u1 The updated NBM files are JAR signed with an ASF certificate, so will show as Third-Party but at least Signed and Valid. A second round of updates will download the actual updated nb-javac libraries - unfortunately, due to the current temporary keystore used in the build process, the nb-javac updates will show as self-signed - I do not believe we have any way to fix that for 11.2. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC member to help with voting admin. If and when this vote passes, the updated source and NBMs will be released on to the mirrors, and the updated catalog (as per above) merged into the existing update centre on the NetBeans VM. Thank you for all the hard work! 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: Error when building from current git
Actually I've seen that when I added the dark LAF to the build. https://github.com/apache/netbeans/pull/1651/commits/05d9e9fa9e6eaa343c9012bf3745567299c8acaf build.xml was the fix for that, however only the fixed working version were ever merged to the master. But master builds fine for Travis and for me as well. On 11/27/19 12:43 AM, Peter Hull wrote: Hi all, I have started seeing this error after updating to the latest git master and running `ant` or `ant build-basic`: ...\netbeans\nbbuild\build.xml:660: Target "all-o.n.swing.laf.dark" does not exist in the project "nbbuild". It is used from target "nbmerge-build-one-cluster". Has anyone else seen this? I'm using Windows & JDK1.8 to build. Pete - 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: Problems compiling layer.xml for custom module
On Wed, 27 Nov 2019 at 14:01, joe foe wrote: > > This is known problem with 11.2 . See NETBEANS-3290 in netbeans JiRA. > > Alternative is to use 11.1 . I am literally as I type pushing the update that should fix this for 11.2 via SVN for update vote. Once that is done, your feedback during the vote on whether this solves that issue will be welcomed! 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: Problems compiling layer.xml for custom module
This is known problem with 11.2 . See NETBEANS-3290 in netbeans JiRA. Alternative is to use 11.1 . On Wed, 27 Nov 2019, 14:58 Mark A. Claassen, wrote: > I wrote a plugin for a VCS system that we use called AccuRev. I wrote > this for Netbeans version 7. Because I used some internal APIs and was not > a "friend" of some modules, I needed to recompile it for every version. > However, to Netbeans credit, I have always been able to do that without > changing my code! > > I currently have a version that works with Apache Netbeans 11.1. I > downloaded 11.2 this morning and I could not get the compile to work. I am > getting an error when it is examining my layer.xml file. Hopefully this is > just something I can fix in the XML header. > > Any guidance would be appreciated. Thanks. > > Here is a sample of the errors I am getting: > ...\src\org\netbeans\modules\accurev\layer.xml:3:13: Element type > "filesystem" must be declared. > ...\src\org\netbeans\modules\accurev\layer.xml:4:25: Element type > "folder" must be declared. > ...\src\org\netbeans\modules\accurev\layer.xml:5:26: Element type > "folder" must be declared. > ...\src\org\netbeans\modules\accurev\layer.xml:6:74: Element type > "file" must be declared. > ...\src\org\netbeans\modules\accurev\layer.xml:7:95: Element type > "attr" must be declared. > > Here is part of my layer.xml file > > > http://www.netbeans.org/dtds/filesystem-1_2.dtd";> > > > > name="org-netbeans-modules-accurev-actions-StatAction.instance"> > stringvalue="org.netbeans.modules.accurev.actions.StatAction"/> > > > > Mark Claassen > Senior Software Engineer > > Donnell Systems, Inc. > 130 South Main Street > Leighton Plaza Suite 375 > South Bend, IN 46601 > E-mail: mailto:mclaas...@ocie.net > Voice: (574)232-3784 > Fax: (574)232-4014 > > Disclaimer: > The opinions provided herein do not necessarily state or reflect > those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and > assumes no legal liability or responsibility for the posting. > > > - > 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 > > > >
Problems compiling layer.xml for custom module
I wrote a plugin for a VCS system that we use called AccuRev. I wrote this for Netbeans version 7. Because I used some internal APIs and was not a "friend" of some modules, I needed to recompile it for every version. However, to Netbeans credit, I have always been able to do that without changing my code! I currently have a version that works with Apache Netbeans 11.1. I downloaded 11.2 this morning and I could not get the compile to work. I am getting an error when it is examining my layer.xml file. Hopefully this is just something I can fix in the XML header. Any guidance would be appreciated. Thanks. Here is a sample of the errors I am getting: ...\src\org\netbeans\modules\accurev\layer.xml:3:13: Element type "filesystem" must be declared. ...\src\org\netbeans\modules\accurev\layer.xml:4:25: Element type "folder" must be declared. ...\src\org\netbeans\modules\accurev\layer.xml:5:26: Element type "folder" must be declared. ...\src\org\netbeans\modules\accurev\layer.xml:6:74: Element type "file" must be declared. ...\src\org\netbeans\modules\accurev\layer.xml:7:95: Element type "attr" must be declared. Here is part of my layer.xml file http://www.netbeans.org/dtds/filesystem-1_2.dtd";> Mark Claassen Senior Software Engineer Donnell Systems, Inc. 130 South Main Street Leighton Plaza Suite 375 South Bend, IN 46601 E-mail: mailto:mclaas...@ocie.net Voice: (574)232-3784 Fax: (574)232-4014 Disclaimer: The opinions provided herein do not necessarily state or reflect those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes no legal liability or responsibility for the posting. - 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
[VOTE] Release Apache NetBeans nb-repository-plugin version 1.5
Dear members of Apache NetBeans community. I want to call a vote on releasing Apache NetBeans utilities nb-repository-plugin version 1.5 This is an Apache Maven plugin that help populating a maven repository with Apache NetBeans materials. This what we use to populate the maven artefacts to maven central. One change from 1.4 -The plugin his capable on targeting a repository deployId instead of a forced netbeans id (former repository at oracle), helping release in the Apache repository snapshot in more automated way The voting artefacts sources are located here: https://dist.apache.org/repos/dist/dev/netbeans/netbeans-maven-utilities/nb- repository-plugin/nb-repository-plugin-1.5/ In addition to that the Maven artifacts built from https://github.com/apache/netbeans-mavenutils-nb-repository-plugin with the commit id d17bf1073a619bf92c508f700986f0d0502e718e(tag nb-repository-plugin-1.5) are staged in the following repository: https://repository.apache.org/content/repositories/orgapachenetbeans-1053/ Key file is here: https://www.apache.org/dist/netbeans/KEYS The vote is open for at least 72h. Best Regards Eric Barboni (skygo)
Re: Figuring out nbjavac in 11.2 is a doozy
On Wed, 27 Nov 2019 at 08:26, Emilian Bold wrote: > I didn't mean to involve you too much with this, just curious if my > patch made sense. I certainly don't want to split the efforts under > NetBeans. I think that was meant that you doing it separately is splitting the effort! Ideally something to solve here. > It would be great if there was a single flag in the canonical build > that would include nb-javac but it doesn't seem obvious to me how... > Especially considering the current nb/updatecenters/extra config. I wonder if the old extra cluster mechanism, as JavaFX is (was?) doing, is easier in this respect? Some of this was discussed in https://github.com/apache/netbeans/pull/1560 if you haven't read that? > I recently asked if Apache is fine with me producing a NetBeans > installer that is only the NetBeans release + a bundled JDK. The PMC > Chair reply was that Apache most certainly does *not* allow such a > thing and that the project would have to be rebranded. So, for this > reason alone a distribution is still needed. Really?! IMO that's something we've said multiple times we would allow, including in a recent thread (when Debian, etc. came up). Presumably the installer itself would need to be called something like "XXX installer for Apache NetBeans and JDK", but as long as what it installs is our binary release or built from our source release, what's the problem? 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
Error when building from current git
Hi all, I have started seeing this error after updating to the latest git master and running `ant` or `ant build-basic`: > ...\netbeans\nbbuild\build.xml:660: Target "all-o.n.swing.laf.dark" does not exist in the project "nbbuild". It is used from target "nbmerge-build-one-cluster". Has anyone else seen this? I'm using Windows & JDK1.8 to build. Pete
Re: Figuring out nbjavac in 11.2 is a doozy
I didn't mean to involve you too much with this, just curious if my patch made sense. I certainly don't want to split the efforts under NetBeans. It would be great if there was a single flag in the canonical build that would include nb-javac but it doesn't seem obvious to me how... Especially considering the current nb/updatecenters/extra config. But, as you can see, if I can just patch things then the change is quite small. Which seems not a whole lot of work for me in the future to maintain. I recently asked if Apache is fine with me producing a NetBeans installer that is only the NetBeans release + a bundled JDK. The PMC Chair reply was that Apache most certainly does *not* allow such a thing and that the project would have to be rebranded. So, for this reason alone a distribution is still needed. --emi On Tue, Nov 26, 2019 at 11:17 PM Jan Lahoda wrote: > > On Mon, Nov 25, 2019 at 8:18 PM Emilian Bold wrote: > > > Jan, I'm curious if this patch makes sense to you: > > > > https://github.com/OpenBeans/OpenBeans/commit/ec4bfe3db429abd8830d750f8bc5dcc14285db37#diff-03465d6aba3fa54304c800a82884a4b9R31 > > > Technically, yes, this is likely to work. But I wonder if that's the good > direction overall - it feels like splitting the efforts (just the effort to > keep the patch queue apply!), rather than joining the efforts. > > One related note is that when I asked if third-party can still call their > build Apache Netbeans, the answer[1] (which was not disputed) was that > there are draft conditions on that: > http://www.apache.org/foundation/marks/downstream.html > > One of the conditions is: > All source code from which the software it is built must be available in > the Apache Software Foundation source code repository for the project. > > So, custom patches are not allowed, but if there would be a way to > configure the canonical build to include nb-javac and other libraries, > third-parties could produce binaries called "Apache NetBeans" with those > libraries. Advantage is that everything is joint development here, as > opposed to creating separate "distributions". > > (Another condition is "The software must be provided via a channel the end > user would expect to use to obtain packages for their platform.", but I > think a webpage satisfies that for most platforms.) > > Jan > > [1] > http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201911.mbox/%3c86284876-2960-43eb-b3ec-b33538864...@apache.org%3e > > > > > > > > > I'm just including the javacapi/impl JARs in libs.javacimpl, like we > > used to in 8.2. I *think* this should be sufficient but perhaps I'm > > not testing it correctly. > > > > --emi > > > > On Mon, Nov 25, 2019 at 9:33 AM Jan Lahoda wrote: > > > > > > Hello Emilian, > > > > > > While I understand your issue, the problem is that the space for > > solutions > > > if significantly limited: > > > -the ASF does not allow distribution of GPLv2+CPE libraries inside the > > > Apache distribution > > > -there is only a single Plugin Portal for all NetBeans 11.0, 11.1 and > > 11.2; > > > yet, nb-javac based on JDK 13 *cannot* work in NetBeans 11.0, because the > > > old javadoc APIs are stripped from it. So we cannot just upload the new > > > nb-javac to the Plugin Portal, as that would (and did, actually) break > > > NetBeans 11.0. And I don't think this will be a unique situation, > > assuming > > > the records (JEP 359) is merged into JDK 14, nb-javac based on JDK 14 > > will > > > not work with any NetBeans 11.0, 11.1 and 11.2, because of new enum > > > constants added to ElementKind. Overall, as long as we share the Plugin > > > Portals across versions (which makes sense, unless we want to force > > > everyone to upload their plugins to a new portal every 3 months), we > > cannot > > > have nb-javac there, as older versions of NetBeans may not be compatible > > > with the new nb-javac. > > > > > > If you want to add a new constraint that it must be easy to do a build > > > which includes nb-javac, I have nothing against that, but you may need to > > > design that yourself (and preferably contribute that back). > > > > > > Jan > > > > > > > > > On Mon, Nov 25, 2019 at 12:15 AM Emilian Bold > > > wrote: > > > > > > > Hello, > > > > > > > > Before 11.2, nb-javac was just suggested and downloaded as a plain 3rd > > > > party plugin from the UC. Neat and clean. > > > > > > > > In 11.2 there is this rather complicated setup that's getting hard to > > > > untangle. > > > > > > > > So, following the spirit of the JavaFX plugins we use the same '3rd > > > > party' *meta* update center which is just an XML generated at build > > > > time together with the hollow NBMs. > > > > > > > > The magic of these NBMs is that we use .external files for the real > > > > GPL w/ CPE meat of things and these files have an URL pointing to > > > > something like netbeans.osuosl.org . > > > > > > > > Now, I'm trying to just include nb-javac at build time and don't need > > > > all this complicated mecha
