Re: [VOTE] Release Apache NetBeans 11.2 macOS Installer

[reema . taneja]

pkg is signed using Developer ID Installer certificate.

pkgutil --check-signature ~/Downloads/Apache*.pkg
Package "Apache NetBeans 11.2.pkg":
   Status: signed by a certificate trusted by Mac OS X
   Certificate Chain:
    1. Developer ID Installer: The Apache Software Foundation (2GLGAFWEQD)
   SHA1 fingerprint: FE B5 04 54 A5 67 F9 0D 41 7D 43 48 81 9E 0F 
F0 0A F4 E8 9A

-
    2. Developer ID Certification Authority
   SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 
41 E3 88 E1 86

-
    3. Apple Root CA
   SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 
D1 98 DF 6C 60


Thanks,

Reema

On 26/10/19 4:12 AM, Scott Palmer wrote:

I can’t remember, was there a plan to have the .pkg signed?

Delivering unsigned installers is a barrier to the end users that we really 
shouldn’t tolerate.

Scott


On Oct 25, 2019, at 4:55 PM, Geertjan Wielenga  wrote:

+1. Installs fine and did the various checks.

Gj

On Fri, Oct 25, 2019 at 5:56 PM  wrote:


Hi

Artifacts are available here:

https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_netbeans_netbeans_11.2-2Dvc1=DwIFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=FbR0d3Tnh4ma57lgC7izA4G7jWlkx3LNr02UtXj0N4g=qzDrunP-uIwKYAmh-ogeKns7phhL-h813Swm_j1XOY0=

Built locally from release112 branch using JDK 1.8 on macOS 10.13.6:

Primary voting artifact:


https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_netbeans_netbeans_11.2-2Dvc1_Apache-2DNetBeans-2D11.2-2Dbin-2Dmacosx.dmg=DwIFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=FbR0d3Tnh4ma57lgC7izA4G7jWlkx3LNr02UtXj0N4g=etC_uQ93Y1ItGLVGigN7ppD7scJxsaWUk1T-kh_ifpg=

SHA512:

7cde2e5ff1fe2125ff0446b1cd663172eb64db4d852b6cbc265ce33b0eb2ce30b4f4bb632ce8860ce1a16c2127858f45391518b6e8fcfe32ea534d32f24769f8

Apache-NetBeans-11.2-bin-macosx.dmg

KEYS file:

https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_release_netbeans_KEYS=DwIFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=FbR0d3Tnh4ma57lgC7izA4G7jWlkx3LNr02UtXj0N4g=UwVlRgDVXj4WPsYLq8cM7Xy3tlzXGhrDPwMf6i784DA=

Installer build steps:

https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Installer-2BBuild-2BSteps=DwIFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=FbR0d3Tnh4ma57lgC7izA4G7jWlkx3LNr02UtXj0N4g=_xOCa67JgJ61B-4YDN7PV-JR5rsKz9YhcRF4sv9JZYM=

Please check that the artifact functions correctly and has been
correctly signed by a PMC member.

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.

Apache NetBeans 11.2 macOS Installer will be released if and when this
vote passes.


Thanks,

Reema






-
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://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Mailing-2Blists=DwIFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=FbR0d3Tnh4ma57lgC7izA4G7jWlkx3LNr02UtXj0N4g=VTQsNSTZwO6aoE0AgP6zLOLJGGzUjSH1aXXUfzIYr3k=






-
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://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Mailing-2Blists=DwIFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=FbR0d3Tnh4ma57lgC7izA4G7jWlkx3LNr02UtXj0N4g=VTQsNSTZwO6aoE0AgP6zLOLJGGzUjSH1aXXUfzIYr3k=





-
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] Handling release updates

[Laszlo Kishalmi]

On 10/25/19 8:55 AM, Neil C Smith wrote:

On Fri, 25 Oct 2019 at 16:02, Laszlo Kishalmi  wrote:

So anyone can step up coordinate and do a patch release of some modules
if the community approves that. When we are releasing the whole IDE the
RM has one orientation: the whole IDE.

I'm -1 to voting on patch sources vs a whole IDE patch release (even
if +1 to anyone else RM'ing it! ;-) ).  I think the way that the patch
release was done previously would be difficult to achieve with the new
build system.  We need to ensure that even patch releases end up with
consistent build numbers / git hash info.  I also think the patch
voting was more complicated for voters, and "awkward" from an Apache
compatibility point of view.  Hence suggesting we still do a vote on
the full sources built on netbeans-TLP, but only nominate required
binaries.
Well, I'm not pushing for the partial source release/vote. You put 
tremendous effort in the new pipeline to work, I very much believe that 
it is easier, more reliable and safer to vote on the whole source and 
nominate the required binaries.


On Fri, 25 Oct 2019 at 14:01, Laszlo Kishalmi  wrote:

Probably the ugliest part was the actual release of the nbms. In the
future we could create a separate update center for release updates and
ship that configured in the release. I think the new plugin portal
infrastructure probably could help, if that'd support multi tenancy.

Good point on the ugly part!  Although again I'd vote -1 on splitting
the UC for the distribution in two.  Mainly from a downstream
distribution / derivative perspective - enlightened self interest at
play there! :-)

However, we do serve the catalog from the VM, and the catalog can have
absolute rather than relative links, meaning we don't need to serve
the updated artefacts themselves the same way.
Still, the other thing we need to keep in mind is that we may be
starting to ship installers that can install specific clusters.  One
way of upgrading such a release later is to install another cluster
via UC?  Not having them signed / having multiple centres may also be
a problem there.
I'm not sure I get this, but I think that would be explained in more 
detail. Let's listen for other ideas as well...


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 Linux Installer

[Laszlo Kishalmi]

+1 (binding)

The installer works tested on Ubuntu 18.04 LTS.

There are some strange things (why Java SE requires HTML 5/JavaScript), 
but those can be resolved later.


Thanks for the installer! It brought some old memories back, though I'd 
continue living on Snaps, I know that's not everyone's taste.


On 10/25/19 8:47 AM, reema.tan...@oracle.com wrote:

Hi,

Artifacts are available here:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1

Built using Jenkins job:

https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/

Primary voting artifact:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-linux-x64.sh 



SHA512:

a02206dc569ef00c2e08ecb799604a0cae21d9204894e9432a51ff89981266d097a6f5d0b7c3c90be663cfced5ead7f37f7fe286a2a0e1569c972178a89c3f9e 
Apache-NetBeans-11.2-bin-linux-x64.sh


KEYS file:

https://dist.apache.org/repos/dist/release/netbeans/KEYS

Installer build steps:

https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps 



Please check that the artifact functions correctly and has been 
correctly signed by a PMC member.


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.


Apache NetBeans 11.2 Linux Installer will be released if and when this 
vote passes.



Thanks,

Reema






-
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 Linux Installer

[Kai Uwe Pel]

+1

no issues during the installation procedure.

Cheers,
Kai


On 10/26/2019 2:16 AM, Patrick Musembi wrote:

+1
Installed, activted Java and PHP. Installed nb-javac and all were fine.

On Fri, 25 Oct 2019 at 18:47,  wrote:


Hi,

Artifacts are available here:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1

Built using Jenkins job:

https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/

Primary voting artifact:


https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-linux-x64.sh

SHA512:

a02206dc569ef00c2e08ecb799604a0cae21d9204894e9432a51ff89981266d097a6f5d0b7c3c90be663cfced5ead7f37f7fe286a2a0e1569c972178a89c3f9e

Apache-NetBeans-11.2-bin-linux-x64.sh

KEYS file:

https://dist.apache.org/repos/dist/release/netbeans/KEYS

Installer build steps:

https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps

Please check that the artifact functions correctly and has been
correctly signed by a PMC member.

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.

Apache NetBeans 11.2 Linux Installer will be released if and when this
vote passes.


Thanks,

Reema






-
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 Linux Installer

[Patrick Musembi]

+1
Installed, activted Java and PHP. Installed nb-javac and all were fine.

On Fri, 25 Oct 2019 at 18:47,  wrote:

> Hi,
>
> Artifacts are available here:
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1
>
> Built using Jenkins job:
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/
>
> Primary voting artifact:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-linux-x64.sh
>
> SHA512:
>
> a02206dc569ef00c2e08ecb799604a0cae21d9204894e9432a51ff89981266d097a6f5d0b7c3c90be663cfced5ead7f37f7fe286a2a0e1569c972178a89c3f9e
>
> Apache-NetBeans-11.2-bin-linux-x64.sh
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
> Installer build steps:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps
>
> Please check that the artifact functions correctly and has been
> correctly signed by a PMC member.
>
> 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.
>
> Apache NetBeans 11.2 Linux Installer will be released if and when this
> vote passes.
>
>
> Thanks,
>
> Reema
>
>
>
>
>
>
> -
> 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 macOS Installer

[Scott Palmer]

I can’t remember, was there a plan to have the .pkg signed?

Delivering unsigned installers is a barrier to the end users that we really 
shouldn’t tolerate.

Scott

> On Oct 25, 2019, at 4:55 PM, Geertjan Wielenga  wrote:
> 
> +1. Installs fine and did the various checks.
> 
> Gj
> 
> On Fri, Oct 25, 2019 at 5:56 PM  wrote:
> 
>> Hi
>> 
>> Artifacts are available here:
>> 
>> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1
>> 
>> Built locally from release112 branch using JDK 1.8 on macOS 10.13.6:
>> 
>> Primary voting artifact:
>> 
>> 
>> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-macosx.dmg
>> 
>> SHA512:
>> 
>> 7cde2e5ff1fe2125ff0446b1cd663172eb64db4d852b6cbc265ce33b0eb2ce30b4f4bb632ce8860ce1a16c2127858f45391518b6e8fcfe32ea534d32f24769f8
>> 
>> Apache-NetBeans-11.2-bin-macosx.dmg
>> 
>> KEYS file:
>> 
>> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>> 
>> Installer build steps:
>> 
>> https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps
>> 
>> Please check that the artifact functions correctly and has been
>> correctly signed by a PMC member.
>> 
>> 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.
>> 
>> Apache NetBeans 11.2 macOS Installer will be released if and when this
>> vote passes.
>> 
>> 
>> Thanks,
>> 
>> Reema
>> 
>> 
>> 
>> 
>> 
>> 
>> -
>> 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 macOS Installer

[Geertjan Wielenga]

+1. Installs fine and did the various checks.

Gj

On Fri, Oct 25, 2019 at 5:56 PM  wrote:

> Hi
>
> Artifacts are available here:
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1
>
> Built locally from release112 branch using JDK 1.8 on macOS 10.13.6:
>
> Primary voting artifact:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-macosx.dmg
>
> SHA512:
>
> 7cde2e5ff1fe2125ff0446b1cd663172eb64db4d852b6cbc265ce33b0eb2ce30b4f4bb632ce8860ce1a16c2127858f45391518b6e8fcfe32ea534d32f24769f8
>
> Apache-NetBeans-11.2-bin-macosx.dmg
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
> Installer build steps:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps
>
> Please check that the artifact functions correctly and has been
> correctly signed by a PMC member.
>
> 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.
>
> Apache NetBeans 11.2 macOS Installer will be released if and when this
> vote passes.
>
>
> Thanks,
>
> Reema
>
>
>
>
>
>
> -
> 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: [RESULT][VOTE] Apache NetBeans 11.2 Release

[Josh Juneau]

Congrats on the release!

Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau

> On Oct 25, 2019, at 3:58 AM, Neil C Smith  wrote:
> 
> On Fri, 25 Oct 2019 at 07:48, Geertjan Wielenga  wrote:
>> we need to do whatever we can to make the following PR for the new
>> nb-javac available, or else refactoring will be broken for everyone with
>> nb-javac installed in 11.2:
> 
> Yes, it's a shame we're releasing knowing that we need to ship an
> update.  I'll start moving release artefacts on to dist now, but will
> leave removal of NB 11.1 for a few days until everything else is
> ready.
> 
> If anyone can input on how we get our processes for shipping updates
> in better shape then please participate in that separate discussion
> thread - it's probably our most urgent problem to solve right now!
> 
> There are some lessons to consider here about our release schedule and
> how strict we are about freezing.  The updated nb-javac was added
> after freeze, and has also been a cause of a few delays - it was not
> until beta3 that it was even testable.  However, without it we'd be
> missing Java 13 support.  Whether we need to make sure these changes
> land before freeze, or push our schedules back a few weeks around JDK
> releases might be something to consider.  A particular concern might
> be how much we can ensure JDK 14 is considered in NetCAT for NB 12.0.
> 
> 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: Blocker Maven issue just opened?

[Peter Hull]

On Sat, 19 Oct 2019 at 11:32, Neil C Smith  wrote:
> Searching that system property surprised to see it's quite old -
> https://blogs.oracle.com/thejavatutorials/jdk-7u25:-solutions-to-issues-caused-by-changes-to-runtimeexec
>
> I've opened a linked issue for 11.3 to track fixing it properly
> https://issues.apache.org/jira/browse/NETBEANS-3254

I have had a bit of a play with this and might have made some
progress. However, in the NB source there are at comments relating to
fixing at least 6 different bugs going back a decade so it's obviously
a bit of a hairy patch of code.

In the linked article above it gives the 'Golden Rule' as creating a
process builder with the first 2 string args being "cmd" and "/c",
then folding the actual thing you want to call into the third
argument, taking care to quote it properly.

But it seems to me that with changes to the JDK's command line
argument validation it is impossible to tiptoe around the tighter
checks with this technique, and furthermore a better approach is to
keep all the parts of the arguments separated out, and let Java take
care of the escaping. More like you'd do on Linux, in fact.

I've had a go at implementing this here:
https://github.com/pedro-w/netbeans/tree/NETBEANS-3254
It works for me with JDK11 on Windows and Linux but I only tested
simple projects. I'm not a Maven expert* and I don't know what kind of
crazy parameters people will use to invoke mvn.cmd with. So, if anyone
could have a go and see where they get to I would be grateful. In my
branch there is also a commit which just cleans up some warnings in
the code, I didn't go all-in on this (e.g. using lambdas where
suggested) but I thought if we were changing the file we might as well
clear up a few things.

Pete
 .* see what I _didn't_ do there!

-
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: NetBeans app with Maven with 3rd party libs

[Matteo Di Giovinazzo]

Thanks, yes but what about the case we have in our RCP app: we use
gitlab4j, batik and awsamazon libraries and they share dependencies on
commons-logging with 3 different versions and other shared dependencies?
Is creating different NBM modules by hand trying to group as much jars as
possible and at the same time minimize the redundancy of including the same
jars multiple times the only solution at the moment?

On Fri, 25 Oct 2019 at 09:19, Eric Barboni  wrote:

> Hi,
>
> You may group more than on artifacts in one wrapper.  And you don't have
> to do  wrapper for every artefacts
> If you wrap batik, it's about 10 maven artefacts, but you may have just
> one wrapper for all of them.
> It depends usage
>
> Regards
> Eric
>
> -Message d'origine-
> De : Matteo Di Giovinazzo 
> Envoyé : vendredi 25 octobre 2019 16:22
> À : dev@netbeans.apache.org
> Objet : Re: NetBeans app with Maven with 3rd party libs
>
> Thanks Timon for the suggestion!
> I am used to follow that way using the Ant-based NetBeans
> module/suite/application projects, but I was hoping with Maven that could
> be avoided given that Maven takes care of dependencies itself. I guess the
> problem is that Maven dependencies are transitive whereas NetBeans ones are
> not. I was in fact reading this
> https://bits.netbeans.org/mavenutilities/nbm-maven-plugin/  hoping
> something clever was going to happen.
>
> Our current problem is that we have 50+ libraries to ship with our RCP
> application and some of them have very log chain of dependencies and
> handling all the dependency graph by hand is a nightmare...
>
> Any other suggestions?
> Thanks!
>
>
>
>
> On Fri, 25 Oct 2019 at 02:31, Timon Veenstra  wrote:
>
> > Hi Matteo,
> >
> > The way to share dependencies between netbeans platform modules is to
> > create library wrapper modules.
> > - Create a new netbeans platform module
> > - add the dependency
> > - declare public packages
> >
> > A little more elaborate description can be found here:
> >
> > https://ljelonek.wordpress.com/2011/04/19/netbeans-maven-library-wrapp
> > er-modules/
> >
> > Cheers,
> > Timon
> >
> > On Thu, Oct 24, 2019 at 7:29 PM Matteo Di Giovinazzo
> > 
> > wrote:
> >
> > > I'm trying to mavenize our NB RCP app, but I do not understand how
> > > to add 3rd party libraries.
> > > I have an app (nbappmaven) with two modules (module1 and module2)
> > > and
> > both
> > > need the same library, say gitlab4j (with all dependencies is about
> > > 7 MB
> > of
> > > jars).
> > >
> > > I tried several approaches but without luck:
> > >
> > >1. I declared the dependency in both modules but I ended up with the
> > >needed jars in both these folders:
> > >   -
> > >
> > >
> > nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> > company.module1
> > >   -
> > >
> > >
> > nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> > company.module2
> > >2. I declared the dependency in the application Maven project,
> > > but it
> > is
> > >not picked up by the two modules...
> > >3. I declared the dependency in the parent Maven project
> > >(nbappmaven-parent), but now I have the jars in 3 folders...
> > >   -
> > >
> > >
> > nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> > company.module1
> > >   -
> > >
> > >
> > nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> > company.module2
> > >   -
> > >
> > >
> > nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> > company.nbappmaven-branding
> > >
> > > Is there a suggested approach in this case? I guess it will be
> > > pretty common to share the same library among different modules, no?
> > >
> > > Thanks for any hint!
> > >
> > > Best,
> > > --
> > > Matteo Di Giovinazzo
> > >
> >
>
>
> --
> Matteo Di Giovinazzo
>
>
> -
> 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
>
>
>
>

-- 
Matteo Di Giovinazzo

[VOTE] Release Apache NetBeans 11.2 macOS Installer

[reema . taneja]

Hi

Artifacts are available here:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1

Built locally from release112 branch using JDK 1.8 on macOS 10.13.6:

Primary voting artifact:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-macosx.dmg

SHA512:

7cde2e5ff1fe2125ff0446b1cd663172eb64db4d852b6cbc265ce33b0eb2ce30b4f4bb632ce8860ce1a16c2127858f45391518b6e8fcfe32ea534d32f24769f8 
Apache-NetBeans-11.2-bin-macosx.dmg


KEYS file:

https://dist.apache.org/repos/dist/release/netbeans/KEYS

Installer build steps:

https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps

Please check that the artifact functions correctly and has been 
correctly signed by a PMC member.


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.


Apache NetBeans 11.2 macOS Installer will be released if and when this 
vote passes.



Thanks,

Reema






-
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] Handling release updates

[Neil C Smith]

On Fri, 25 Oct 2019 at 16:02, Laszlo Kishalmi  wrote:
> So anyone can step up coordinate and do a patch release of some modules
> if the community approves that. When we are releasing the whole IDE the
> RM has one orientation: the whole IDE.

I'm -1 to voting on patch sources vs a whole IDE patch release (even
if +1 to anyone else RM'ing it! ;-) ).  I think the way that the patch
release was done previously would be difficult to achieve with the new
build system.  We need to ensure that even patch releases end up with
consistent build numbers / git hash info.  I also think the patch
voting was more complicated for voters, and "awkward" from an Apache
compatibility point of view.  Hence suggesting we still do a vote on
the full sources built on netbeans-TLP, but only nominate required
binaries.

On Fri, 25 Oct 2019 at 14:01, Laszlo Kishalmi  wrote:
> Probably the ugliest part was the actual release of the nbms. In the
> future we could create a separate update center for release updates and
> ship that configured in the release. I think the new plugin portal
> infrastructure probably could help, if that'd support multi tenancy.

Good point on the ugly part!  Although again I'd vote -1 on splitting
the UC for the distribution in two.  Mainly from a downstream
distribution / derivative perspective - enlightened self interest at
play there! :-)

However, we do serve the catalog from the VM, and the catalog can have
absolute rather than relative links, meaning we don't need to serve
the updated artefacts themselves the same way.

Still, the other thing we need to keep in mind is that we may be
starting to ship installers that can install specific clusters.  One
way of upgrading such a release later is to install another cluster
via UC?  Not having them signed / having multiple centres may also be
a problem there.

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

[VOTE] Release Apache NetBeans 11.2 Windows Installer

[reema . taneja]

Hi,

Artifacts are available here:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1

Built using Jenkins job:

https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/

Primary voting artifact:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-windows-x64.exe

SHA512:

a9a33d19afc439971fc3a3a0d2e5d3404fd1b372c1995067e3fa97bc0f17c7a9471462d592b6b0f46b5b3bd5461a6768625334f7576f4b3ed54f2aebc575cc6b 
Apache-NetBeans-11.2-bin-windows-x64.exe


KEYS file:

https://dist.apache.org/repos/dist/release/netbeans/KEYS

Installer build steps:

https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps

Please check that the artifact functions correctly and has been 
correctly signed by a PMC member.


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.


Apache NetBeans 11.2 Windows Installer will be released if and when this 
vote passes.


Thanks,

Reema






-
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 11.2 Linux Installer

[reema . taneja]

Hi,

Artifacts are available here:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1

Built using Jenkins job:

https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/

Primary voting artifact:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-linux-x64.sh

SHA512:

a02206dc569ef00c2e08ecb799604a0cae21d9204894e9432a51ff89981266d097a6f5d0b7c3c90be663cfced5ead7f37f7fe286a2a0e1569c972178a89c3f9e 
Apache-NetBeans-11.2-bin-linux-x64.sh


KEYS file:

https://dist.apache.org/repos/dist/release/netbeans/KEYS

Installer build steps:

https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps

Please check that the artifact functions correctly and has been 
correctly signed by a PMC member.


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.


Apache NetBeans 11.2 Linux Installer will be released if and when this 
vote passes.



Thanks,

Reema






-
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: NetBeans app with Maven with 3rd party libs

[Eric Barboni]

Hi,

You may group more than on artifacts in one wrapper.  And you don't have to do  
wrapper for every artefacts
If you wrap batik, it's about 10 maven artefacts, but you may have just one 
wrapper for all of them.
It depends usage 

Regards
Eric

-Message d'origine-
De : Matteo Di Giovinazzo  
Envoyé : vendredi 25 octobre 2019 16:22
À : dev@netbeans.apache.org
Objet : Re: NetBeans app with Maven with 3rd party libs

Thanks Timon for the suggestion!
I am used to follow that way using the Ant-based NetBeans 
module/suite/application projects, but I was hoping with Maven that could be 
avoided given that Maven takes care of dependencies itself. I guess the problem 
is that Maven dependencies are transitive whereas NetBeans ones are not. I was 
in fact reading this https://bits.netbeans.org/mavenutilities/nbm-maven-plugin/ 
 hoping something clever was going to happen.

Our current problem is that we have 50+ libraries to ship with our RCP 
application and some of them have very log chain of dependencies and handling 
all the dependency graph by hand is a nightmare...

Any other suggestions?
Thanks!




On Fri, 25 Oct 2019 at 02:31, Timon Veenstra  wrote:

> Hi Matteo,
>
> The way to share dependencies between netbeans platform modules is to 
> create library wrapper modules.
> - Create a new netbeans platform module
> - add the dependency
> - declare public packages
>
> A little more elaborate description can be found here:
>
> https://ljelonek.wordpress.com/2011/04/19/netbeans-maven-library-wrapp
> er-modules/
>
> Cheers,
> Timon
>
> On Thu, Oct 24, 2019 at 7:29 PM Matteo Di Giovinazzo 
> 
> wrote:
>
> > I'm trying to mavenize our NB RCP app, but I do not understand how 
> > to add 3rd party libraries.
> > I have an app (nbappmaven) with two modules (module1 and module2) 
> > and
> both
> > need the same library, say gitlab4j (with all dependencies is about 
> > 7 MB
> of
> > jars).
> >
> > I tried several approaches but without luck:
> >
> >1. I declared the dependency in both modules but I ended up with the
> >needed jars in both these folders:
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> company.module1
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> company.module2
> >2. I declared the dependency in the application Maven project, 
> > but it
> is
> >not picked up by the two modules...
> >3. I declared the dependency in the parent Maven project
> >(nbappmaven-parent), but now I have the jars in 3 folders...
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> company.module1
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> company.module2
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.my
> company.nbappmaven-branding
> >
> > Is there a suggested approach in this case? I guess it will be 
> > pretty common to share the same library among different modules, no?
> >
> > Thanks for any hint!
> >
> > Best,
> > --
> > Matteo Di Giovinazzo
> >
>


--
Matteo Di Giovinazzo


-
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] Handling release updates

[Laszlo Kishalmi]

On 10/25/19 7:17 AM, Eric Barboni wrote:

Hi,
Needs to be simple and formal enough to be  Apache compatible.

I'm afraid that if it's too complicated, a RM can cancel release vote because 
if it may look simpler to merge some fix and revote. Or let the bug until the 
next X.Y release.
And if a RM is more java oriented he may not see c++ or web issue as important 
to deserve an update. (kind if Laszlo were not RM at the time maybe gradle 
patch would have never been set)


Well that's not entirely true. Each release has it's own RM 11.1 and 
11.2 happens to be Neil. A patch release can have a different RM. What 
for example you are doing with the Maven Archetypes (btw thank you for 
carry on that) are RM. It is the scope of such releases are way smaller 
than releasing the whole IDE.


I would have created the Gradle patch release even if I was not the RM 
for the whole IDE that time, though having two releases behind my back 
certainly helped to have the confidence to walk though the path.


So anyone can step up coordinate and do a patch release of some modules 
if the community approves that. When we are releasing the whole IDE the 
RM has one orientation: the whole IDE.




Regards
Eric

-Message d'origine-
De : Laszlo Kishalmi 
Envoyé : vendredi 25 octobre 2019 14:52
À : dev@netbeans.apache.org
Objet : Re: [DISCUSS] Handling release updates

Well, the Gradle patch has been made in the following way:

1. The result of the release build has been further processed, extracting the 
source files for the changed modules and the necessary files like NOTICE and 
licenses.

2. So the output of the patch build was a small source zip and the 
corresponding nbm-s as binary. The README had the instruction that how you need 
to paths the existing source bundle with the new one to create the binaries.

3. We voted on the source files only

4. The nbms were overwritten in the distribution directory and the 
updates.xml.gz was patched by hand.

Probably the ugliest part was the actual release of the nbms. In the future we 
could create a separate update center for release updates and ship that 
configured in the release. I think the new plugin portal infrastructure 
probably could help, if that'd support multi tenancy.

On 10/23/19 5:51 AM, Neil C Smith wrote:

On Wed, 23 Oct 2019 at 13:47, Geertjan Wielenga  wrote:

Will we really need to go through a vote process for this change?

IMO, yes - it's still a source change.  And that's not quite the only
change required.

But there are other things we might want to make patches for too.
This thread was not meant to be specific to that one particular issue.
We need to work out a process for how we do this in future.

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





-
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: NetBeans app with Maven with 3rd party libs

[Matteo Di Giovinazzo]

Thanks Timon for the suggestion!
I am used to follow that way using the Ant-based NetBeans
module/suite/application projects, but I was hoping with Maven that could
be avoided given that Maven takes care of dependencies itself. I guess the
problem is that Maven dependencies are transitive whereas NetBeans ones are
not. I was in fact reading this
https://bits.netbeans.org/mavenutilities/nbm-maven-plugin/  hoping
something clever was going to happen.

Our current problem is that we have 50+ libraries to ship with our RCP
application and some of them have very log chain of dependencies and
handling all the dependency graph by hand is a nightmare...

Any other suggestions?
Thanks!




On Fri, 25 Oct 2019 at 02:31, Timon Veenstra  wrote:

> Hi Matteo,
>
> The way to share dependencies between netbeans platform modules is to
> create library wrapper modules.
> - Create a new netbeans platform module
> - add the dependency
> - declare public packages
>
> A little more elaborate description can be found here:
>
> https://ljelonek.wordpress.com/2011/04/19/netbeans-maven-library-wrapper-modules/
>
> Cheers,
> Timon
>
> On Thu, Oct 24, 2019 at 7:29 PM Matteo Di Giovinazzo 
> wrote:
>
> > I'm trying to mavenize our NB RCP app, but I do not understand how to add
> > 3rd party libraries.
> > I have an app (nbappmaven) with two modules (module1 and module2) and
> both
> > need the same library, say gitlab4j (with all dependencies is about 7 MB
> of
> > jars).
> >
> > I tried several approaches but without luck:
> >
> >1. I declared the dependency in both modules but I ended up with the
> >needed jars in both these folders:
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module1
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module2
> >2. I declared the dependency in the application Maven project, but it
> is
> >not picked up by the two modules...
> >3. I declared the dependency in the parent Maven project
> >(nbappmaven-parent), but now I have the jars in 3 folders...
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module1
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module2
> >   -
> >
> >
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.nbappmaven-branding
> >
> > Is there a suggested approach in this case? I guess it will be pretty
> > common to share the same library among different modules, no?
> >
> > Thanks for any hint!
> >
> > Best,
> > --
> > Matteo Di Giovinazzo
> >
>


-- 
Matteo Di Giovinazzo

Re: [DISCUSS] Handling release updates

[Laszlo Kishalmi]

Well, the Gradle patch has been made in the following way:

1. The result of the release build has been further processed, 
extracting the source files for the changed modules and the necessary 
files like NOTICE and licenses.


2. So the output of the patch build was a small source zip and the 
corresponding nbm-s as binary. The README had the instruction that how 
you need to paths the existing source bundle with the new one to create 
the binaries.


3. We voted on the source files only

4. The nbms were overwritten in the distribution directory and the 
updates.xml.gz was patched by hand.


Probably the ugliest part was the actual release of the nbms. In the 
future we could create a separate update center for release updates and 
ship that configured in the release. I think the new plugin portal 
infrastructure probably could help, if that'd support multi tenancy.


On 10/23/19 5:51 AM, Neil C Smith wrote:

On Wed, 23 Oct 2019 at 13:47, Geertjan Wielenga  wrote:

Will we really need to go through a vote process for this change?

IMO, yes - it's still a source change.  And that's not quite the only
change required.

But there are other things we might want to make patches for too.
This thread was not meant to be specific to that one particular issue.
We need to work out a process for how we do this in future.

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] Handling release updates

[Neil C Smith]

On Thu, 24 Oct 2019 at 21:17, Jan Lahoda  wrote:
>> Still unsure about how we handle catalog and signing issues though.
>> Am I right in thinking with current situation people will see a
>> warning on update?  Definitely see this already when re-enabling
>> nb-javac.
>
> That is one of the things I'd like to try. The update will be a two phase 
> process - first update the nb/updatecenters module, and then nb-javac. I 
> *think* there should be no warning for the second update (because the NBM is 
> signed using the key that is embedded in the updatecenters module), but I am 
> less sure about how exactly the first update will work.

I'm fairly sure the first update at least will show a warning.
Installing other nbms from the distribution UC does now.

Check the link Reema shared that I posted earlier.  We might be able
to use that, in the short term manually signing the relevant updates
via the web interface?  Except that shows a browser security error for
me.  And also specifies .jar extension.

What other options are there?  Is there any *secure* way that we can
add trust in the IDE for modules built on ASF infrastructure?  If I
understand it correctly, the current way the third-party UC does this
will only work for a single build?

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] Apache NetBeans maven artefacts for version 11.2

[Kai Uwe Pel]

+1 (non binding)

Kai


On 10/25/2019 12:14 PM, Geertjan Wielenga wrote:

+1 (binding)

Gj

On Fri, Oct 25, 2019 at 11:28 AM Eric Barboni  wrote:


We need 2 binding vote

Regards
Eric
-Message d'origine-
De : Kenneth Fogel 
Envoyé : mercredi 23 octobre 2019 17:48
À : dev@netbeans.apache.org
Objet : RE: [VOTE] Apache NetBeans maven artefacts for version 11.2

Responded to wrong thread, my comments were not for maven artifacts. Sorry.
They are for the vote candidate.

Ken

-Original Message-
From: Kenneth Fogel 
Sent: October 23, 2019 11:37 AM
To: dev@netbeans.apache.org
Subject: RE: [VOTE] Apache NetBeans maven artefacts for version 11.2

+1

As a Windows user I can say that I see a noticeable improvement in
performance over 11.1. I do have Windows Defender turned off for my .m2
folder, my NB folder, and my project folder. One change I made compared to
NB 11.1 was to place the userdir and cachedir into a folder adjacent to NB
and also tuned off Defender for them. Nice to see more up to date pom
files.

Ken

-Original Message-
From: Eric Barboni 
Sent: October 21, 2019 8:32 AM
To: dev@netbeans.apache.org
Subject: [VOTE] Apache NetBeans maven artefacts for version 11.2

Dear member of the Apache NetBeans community.

The Maven artefacts for Apache NetBeans 11.2 are ready ( with correct build
numbers + javadoc  where Javadoc is generated) to be published based on the
respective state of source that is used for main vote [1].

Build from this commit:

https://github.com/apache/incubator-netbeans/commit/d04fb24027334c4b6fd8397b
5d0cdd33187a8f54


Artefacts taken from the same build as main voting thread [1] build number
the same.


https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
ns/job/release112/29/


staged at
https://repository.apache.org/content/repositories/orgapachenetbeans-1045

Artefacts are signed using my key (Eric Barboni) and verified by the
repository.apache.org closing phase.

Artefacts are composed of jars,nbm,sources,javadocs,pom.

This vote is going to be open at least 72  hours, vote with +1, 0, and -1
as
usual
--- Important rules
If main vote[1] is cancelled this vote will be cancelled too.


Best Regards
Eric
[1]

https://lists.apache.org/thread.html/a562f51f614364f931a35f8dfd310cfd15ebf44
b150e40277e94ff40@%3Cdev.netbeans.apache.org%3E


-
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




-
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







-
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] Apache NetBeans maven artefacts for version 11.2

[Geertjan Wielenga]

+1 (binding)

Gj

On Fri, Oct 25, 2019 at 11:28 AM Eric Barboni  wrote:

> We need 2 binding vote
>
> Regards
> Eric
> -Message d'origine-
> De : Kenneth Fogel 
> Envoyé : mercredi 23 octobre 2019 17:48
> À : dev@netbeans.apache.org
> Objet : RE: [VOTE] Apache NetBeans maven artefacts for version 11.2
>
> Responded to wrong thread, my comments were not for maven artifacts. Sorry.
> They are for the vote candidate.
>
> Ken
>
> -Original Message-
> From: Kenneth Fogel 
> Sent: October 23, 2019 11:37 AM
> To: dev@netbeans.apache.org
> Subject: RE: [VOTE] Apache NetBeans maven artefacts for version 11.2
>
> +1
>
> As a Windows user I can say that I see a noticeable improvement in
> performance over 11.1. I do have Windows Defender turned off for my .m2
> folder, my NB folder, and my project folder. One change I made compared to
> NB 11.1 was to place the userdir and cachedir into a folder adjacent to NB
> and also tuned off Defender for them. Nice to see more up to date pom
> files.
>
> Ken
>
> -Original Message-
> From: Eric Barboni 
> Sent: October 21, 2019 8:32 AM
> To: dev@netbeans.apache.org
> Subject: [VOTE] Apache NetBeans maven artefacts for version 11.2
>
> Dear member of the Apache NetBeans community.
>
> The Maven artefacts for Apache NetBeans 11.2 are ready ( with correct build
> numbers + javadoc  where Javadoc is generated) to be published based on the
> respective state of source that is used for main vote [1].
>
> Build from this commit:
>
> https://github.com/apache/incubator-netbeans/commit/d04fb24027334c4b6fd8397b
> 5d0cdd33187a8f54
> 
>
> Artefacts taken from the same build as main voting thread [1] build number
> the same.
>
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
> ns/job/release112/29/
> 
>
> staged at
> https://repository.apache.org/content/repositories/orgapachenetbeans-1045
>
> Artefacts are signed using my key (Eric Barboni) and verified by the
> repository.apache.org closing phase.
>
> Artefacts are composed of jars,nbm,sources,javadocs,pom.
>
> This vote is going to be open at least 72  hours, vote with +1, 0, and -1
> as
> usual
> --- Important rules
> If main vote[1] is cancelled this vote will be cancelled too.
>
>
> Best Regards
> Eric
> [1]
>
> https://lists.apache.org/thread.html/a562f51f614364f931a35f8dfd310cfd15ebf44
> b150e40277e94ff40@%3Cdev.netbeans.apache.org%3E
>
>
> -
> 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
>
>
>
>
> -
> 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] Apache NetBeans maven artefacts for version 11.2

[Eric Barboni]

We need 2 binding vote 

Regards
Eric
-Message d'origine-
De : Kenneth Fogel  
Envoyé : mercredi 23 octobre 2019 17:48
À : dev@netbeans.apache.org
Objet : RE: [VOTE] Apache NetBeans maven artefacts for version 11.2

Responded to wrong thread, my comments were not for maven artifacts. Sorry.
They are for the vote candidate.

Ken

-Original Message-
From: Kenneth Fogel  
Sent: October 23, 2019 11:37 AM
To: dev@netbeans.apache.org
Subject: RE: [VOTE] Apache NetBeans maven artefacts for version 11.2

+1

As a Windows user I can say that I see a noticeable improvement in
performance over 11.1. I do have Windows Defender turned off for my .m2
folder, my NB folder, and my project folder. One change I made compared to
NB 11.1 was to place the userdir and cachedir into a folder adjacent to NB
and also tuned off Defender for them. Nice to see more up to date pom files.

Ken

-Original Message-
From: Eric Barboni  
Sent: October 21, 2019 8:32 AM
To: dev@netbeans.apache.org
Subject: [VOTE] Apache NetBeans maven artefacts for version 11.2

Dear member of the Apache NetBeans community.

The Maven artefacts for Apache NetBeans 11.2 are ready ( with correct build
numbers + javadoc  where Javadoc is generated) to be published based on the
respective state of source that is used for main vote [1].

Build from this commit:
https://github.com/apache/incubator-netbeans/commit/d04fb24027334c4b6fd8397b
5d0cdd33187a8f54 

Artefacts taken from the same build as main voting thread [1] build number
the same.
 
https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
ns/job/release112/29/

staged at
https://repository.apache.org/content/repositories/orgapachenetbeans-1045

Artefacts are signed using my key (Eric Barboni) and verified by the
repository.apache.org closing phase.

Artefacts are composed of jars,nbm,sources,javadocs,pom.

This vote is going to be open at least 72  hours, vote with +1, 0, and -1 as
usual
--- Important rules
If main vote[1] is cancelled this vote will be cancelled too.


Best Regards
Eric
[1]
https://lists.apache.org/thread.html/a562f51f614364f931a35f8dfd310cfd15ebf44
b150e40277e94ff40@%3Cdev.netbeans.apache.org%3E


-
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




-
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: [RESULT][VOTE] Apache NetBeans 11.2 Release

[Neil C Smith]

On Fri, 25 Oct 2019 at 07:48, Geertjan Wielenga  wrote:
>  we need to do whatever we can to make the following PR for the new
> nb-javac available, or else refactoring will be broken for everyone with
> nb-javac installed in 11.2:

Yes, it's a shame we're releasing knowing that we need to ship an
update.  I'll start moving release artefacts on to dist now, but will
leave removal of NB 11.1 for a few days until everything else is
ready.

If anyone can input on how we get our processes for shipping updates
in better shape then please participate in that separate discussion
thread - it's probably our most urgent problem to solve right now!

There are some lessons to consider here about our release schedule and
how strict we are about freezing.  The updated nb-javac was added
after freeze, and has also been a cause of a few delays - it was not
until beta3 that it was even testable.  However, without it we'd be
missing Java 13 support.  Whether we need to make sure these changes
land before freeze, or push our schedules back a few weeks around JDK
releases might be something to consider.  A particular concern might
be how much we can ensure JDK 14 is considered in NetCAT for NB 12.0.

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: NetBeans app with Maven with 3rd party libs

[Timon Veenstra]

Hi Matteo,

The way to share dependencies between netbeans platform modules is to
create library wrapper modules.
- Create a new netbeans platform module
- add the dependency
- declare public packages

A little more elaborate description can be found here:
https://ljelonek.wordpress.com/2011/04/19/netbeans-maven-library-wrapper-modules/

Cheers,
Timon

On Thu, Oct 24, 2019 at 7:29 PM Matteo Di Giovinazzo 
wrote:

> I'm trying to mavenize our NB RCP app, but I do not understand how to add
> 3rd party libraries.
> I have an app (nbappmaven) with two modules (module1 and module2) and both
> need the same library, say gitlab4j (with all dependencies is about 7 MB of
> jars).
>
> I tried several approaches but without luck:
>
>1. I declared the dependency in both modules but I ended up with the
>needed jars in both these folders:
>   -
>
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module1
>   -
>
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module2
>2. I declared the dependency in the application Maven project, but it is
>not picked up by the two modules...
>3. I declared the dependency in the parent Maven project
>(nbappmaven-parent), but now I have the jars in 3 folders...
>   -
>
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module1
>   -
>
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.module2
>   -
>
> nbappmaven\application\target\nbappmaven\nbappmaven\modules\ext\com.mycompany.nbappmaven-branding
>
> Is there a suggested approach in this case? I guess it will be pretty
> common to share the same library among different modules, no?
>
> Thanks for any hint!
>
> Best,
> --
> Matteo Di Giovinazzo
>

Re: [RESULT][VOTE] Apache NetBeans 11.2 Release

[Geertjan Wielenga]

Congratulations! And many thanks to Neil.

Before we announce this too much, i.e., I think we should do that only once
we have the installers from Reema and the site updated (I'm working on
that), we need to do whatever we can to make the following PR for the new
nb-javac available, or else refactoring will be broken for everyone with
nb-javac installed in 11.2:

https://github.com/apache/netbeans/pull/1589

Gj

On Fri, Oct 25, 2019 at 3:16 AM Patrick Musembi 
wrote:

> Congratulations Neil and everyone involved.
>
> On Fri, 25 Oct 2019 at 00:11, Neil C Smith  wrote:
>
> > On Thu, 24 Oct 2019, 21:34 Laszlo Kishalmi, 
> > wrote:
> >
> > > Shall Neil handle all the votes on those or different binaries shall
> > > have their owner and then shall sync with/by Neil?
> > >
> >
> > Zip binary is done. The Maven artefacts vote is already active. I think
> > Reema will be kicking off the 3 installer votes in the next day or so.
> > Better, I think, that the person who signs handles the vote.
> >
> >
> > > Yes, the most obvious reason I'm asking that, as the Snap version is
> > > already out on Snapcraft (in the edge channel) and used by some 29
> > > people according to the stats. If it has been voted to be released We
> > > just need to promote the build to the stable channel
> > >
> >
> > I think so. The thing people were pushing for with binary votes was PMC
> > oversight over what was distributed via Apache infrastructure. Not sure
> the
> > Snap needs anything more?
> >
> > Best wishes,
> >
> > Neil
> >
> > >
> >
>