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)
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
+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
+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:
+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:
>
>
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
+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
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
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
>
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
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:
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
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:
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:
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
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
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
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
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
+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
À :
+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
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.
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
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:
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
25 matches
Mail list logo
