Hi,
On Wed, Nov 15, 2017 at 10:45 PM, Antonio wrote:
> The "About Dialog" of a NB RCP Application...
...
> b) Shows a text stating that the NetBeans Platform is released under the
> CDDL/GPL+CPE
I don't think it's required to change that before the first release,
I'd say just create a jira t
Hi,
I'm attaching a SVG version of the most voted Apache NetBeans Logo at [1]
I uploaded the SVG image there, but does not render properly (you have
to click on it).
I'll try to add 256/128/64/32/16 pngs in a few days.
Cheers,
Antonio
https://cwiki.apache.org/confluence/display/NETBEANS/NetBea
vieiro commented on issue #152: Case insensitive SHA-1 comparisons for
downloaded binaries.
URL:
https://github.com/apache/incubator-netbeans/pull/152#issuecomment-344741806
Ok. Closing then.
This is an automated message fro
vieiro closed pull request #152: Case insensitive SHA-1 comparisons for
downloaded binaries.
URL: https://github.com/apache/incubator-netbeans/pull/152
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenanc
The "About Dialog" of a NB RCP Application...
a) Shows an image where the CCDL/GPL + CPE is still there.
b) Shows a text stating that the NetBeans Platform is released under the
CDDL/GPL+CPE.
I think the image is also on the splash screen.
Should that be changed before release?
Cheers,
Anton
On Tue, Nov 14, 2017 at 10:44 PM, Jan Lahoda wrote:
> Hi,
>
> I agree there's a need for a short- and long- term solutions. Here, I was
> more aiming for the short-term ones, as we are getting into the stage where
> I think we need a particular plan and action items to fulfil it. The
> simplest t
matthiasblaesing commented on issue #152: Case insensitive SHA-1 comparisons
for downloaded binaries.
URL:
https://github.com/apache/incubator-netbeans/pull/152#issuecomment-344691047
I agree Antonio, feel free to just close this.
--
On Wed, Nov 15, 2017 at 4:50 PM, Jan Lahoda wrote:
> ...the file name will need to
> be changed in the hash file as well/the hash files will need to be
> regenerated, although the hash itself should remain the same...
That's fine - we vote on hashes, not filenames, though having the
right name fr
For the IPMC vote, I'd suppose it might be good to actually stage the
release (signed and with hashes):
http://www.apache.org/legal/release-policy.html#stage
IMO if the only thing we need to change is the filename, it should be
enough to rename before committing to the SVN (the file name will need
That means we need to make a new artifact with that name and start a new
vote thread here for that artifact?
Or do we start a vote thread at the IPMC with the newly named artifact?
Thanks,
Gj
On Wed, Nov 15, 2017 at 2:59 PM, Bertrand Delacretaz wrote:
> On Wed, Nov 15, 2017 at 3:47 PM, Geertj
On Wed, Nov 15, 2017 at 3:47 PM, Geertjan Wielenga
wrote:
> ..."Shouldn't the name of the ZIP start with "incubating" ?
As per http://incubator.apache.org/guides/releasemanagement.html -
"Release artifacts must include incubating in the final file name"
-Bertrand
Would be great if you could do it before we go to the IPMC, or at least to
have had one mentor do it.
Gj
On Wed, Nov 15, 2017 at 2:09 PM, Bertrand Delacretaz wrote:
> On Wed, Nov 15, 2017 at 10:42 AM, Geertjan Wielenga
> wrote:
> > ...Would be great if a mentor would also take a look prior to
Before we go to the IPMC vote, there's another question that needs an
answer by Jaroslav Tulach above: "Shouldn't the name of the ZIP start with
"incubating" ? I think that is a
requirement somewhere in the release documents."
Gj
On Wed, Nov 15, 2017 at 2:44 PM, Geertjan Wielenga <
geertjan.wiele
OK, I think we have all the info we need -- I'm going to put the IPMC vote
thread together.
Gj
On Wed, Nov 15, 2017 at 2:35 PM, Jaroslav Tulach
wrote:
> Isn't the solution to write to the README.md (maybe just next time) that
> one has to:
>
> ./platform/lib/nbexec --userdir /tmp/testuserdir
>
Isn't the solution to write to the README.md (maybe just next time) that
one has to:
./platform/lib/nbexec --userdir /tmp/testuserdir
(if that works on all platforms)?
-jt
2017-11-15 15:23 GMT+01:00 Geertjan Wielenga <
geertjan.wiele...@googlemail.com>:
> On Wed, Nov 15, 2017 at 2:15 PM, Jan L
On Wed, Nov 15, 2017 at 2:15 PM, Jan Lahoda wrote:
> My personal opinion: seems the main issue here is that the nbexec expects
> to get userdir (and cache dir) from the product/application launcher. If
> that's good or bad, that I guess is a question to NetBeans Platform
> architects, but this (a
That is correct, but the build itself tells you to do set nbjdk.home, which is
wrong, so the description or better the message from ant should be updated.
Am 15.11.17, 15:12 schrieb "Geertjan Wielenga"
:
How I do it on mac is:
1. I have JDK 9 installed.
2. In the termina
My personal opinion: seems the main issue here is that the nbexec expects
to get userdir (and cache dir) from the product/application launcher. If
that's good or bad, that I guess is a question to NetBeans Platform
architects, but this (as far as I can tell) is not really anything new in
this relea
How I do it on mac is:
1. I have JDK 9 installed.
2. In the terminal, I do export JAVA_HOME=`/usr/libexec/java_home -v 1.8`
3. Then in the same terminal I run 'ant' to build the NetBeans sources.
Gj
On Wed, Nov 15, 2017 at 2:05 PM, Anton Epple wrote:
> Hi,
>
>
>
> the description on git incu
Excellent. Great -- thanks for letting everyone know.
We should always drop a quick note here when we're speaking somewhere about
NetBeans.
Gj
On Wed, Nov 15, 2017 at 11:37 AM, mark stephens <
marksteph...@idrsolutions.com> wrote:
> My colleague Georgia Ingham and me are reprising our JavaOne N
On Wed, Nov 15, 2017 at 10:42 AM, Geertjan Wielenga
wrote:
> ...Would be great if a mentor would also take a look prior to us moving the
> vote to the IPMC...
I shall be able to do that in the next 24 hours but if not I'll vote
on the IPMC thread later.
-Bertrand
Hi,
the description on git incubator-netbeans suggests to have both JDK 9 and JDK 8
installed when building NB from sources. On mac this can cause problems, so the
description should maybe be updated with instructions to make it work:
When you start the build with JDK 9 installed, you get
BTW, my macOS non-blocking error is caused by nbexec using the root folder (/)
for the cache (Cache directory: /var/cache).
I believe this also explains the Windows error Chris is mentioning where a lock
file is written top-level:
..\Downloads\netbeans\platform\lib\nbexec64.exe
java.io.FileNotF
FWIW, ./platform/lib/nbexec runs just fine on macOS:
Product Version: NetBeans Platform Dev (Build
incubator-netbeans-release-79-on-20171113)
Java: 1.8.0_66; Java HotSpot(TM) 64-Bit Server VM 25.66-b17
Runtime: Java(TM) SE Runtime Environment 1.8.0_66-b17
System: Mac OS X version 10.12.6 running
OK, makes sense.
Still, we need to figure out what the problem is that Chris describes in
this thread.
Gj
On Wed, 15 Nov 2017 at 13:17, Jaroslav Tulach
wrote:
> > On Wednesday, November 15, 2017, Geertjan Wielenga <
> > geertjan.wiele...@googlemail.com> wrote:
> >
> > > Well, the question woul
> On Wednesday, November 15, 2017, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
> > Well, the question would be why it is useful.
> >
> > And what does it prove -- and is it a requirement for release.
>
What does it show if the launcher isn't working? That you cannot start
plat
Hi Gj !
No sorry, I'm not able to reproduce on Windows Server 2012 R2.
- Ralph
D:\netbeans Platform\platform\lib>nbexec --help
Usage: launcher {options} arguments
General options:
--helpshow this help
--jdkhome path to JDK
-Jpass to JVM
--cp:p prepen
+1
On Wed, Nov 15, 2017, 9:23 AM Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> Also, can someone on Windows reproduce the problem Chris describes in this
> thread?
>
> Gj
>
> On Wednesday, November 15, 2017, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
> > Wel
Also, can someone on Windows reproduce the problem Chris describes in this
thread?
Gj
On Wednesday, November 15, 2017, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> Well, the question would be why it is useful.
>
> And what does it prove -- and is it a requirement for release.
>
My colleague Georgia Ingham and me are reprising our JavaOne NetBeans talk at
DevFest Istanbul on 26th November and also running a stand where we will have
NetBeans up and running.
It is one of my favourite events as outside the 'traditional audience', we
generally get 150+ enthusiastic people
Well, the question would be why it is useful.
And what does it prove -- and is it a requirement for release.
Gj
On Wed, Nov 15, 2017 at 9:49 AM, Jaroslav Tulach
wrote:
> 2017-11-14 20:32 GMT+01:00 Geertjan Wielenga <
> geertjan.wiele...@googlemail.com>:
>
> > Calling the exe doesn’t really mak
2017-11-14 20:32 GMT+01:00 Geertjan Wielenga <
geertjan.wiele...@googlemail.com>:
> Calling the exe doesn’t really make sense. Who/why would one do this.
>
Why it doesn't make sense? Calling platform/lib/nbexec.exe shall start the
platform. Calling platform/lib/nbexec does so on Unix.
-jt
Hi all,
The 2nd vote thread looks good, everyone with a +1:
https://lists.apache.org/thread.html/a2ee0c199a4f742b22249d7993233465e18bc8252a665af37f75728e@%3Cdev.netbeans.apache.org%3E
Would be great if a mentor would also take a look prior to us moving the
vote to the IPMC.
Also, should we remo
Hi.
One option that hasn't been discussed yet is to merge work done in the
[jdk-javac branch](
https://github.com/apache/incubator-netbeans/tree/jdk-javac).
When this branch is merged, the Apache-NetBeans.zip download will be able
to work out of the box with the latest JDK9 javac. I believe it is
On Wed, Nov 15, 2017 at 8:55 AM, Lars Bruun-Hansen
wrote:
> Ahh. I see. I'm sure there's solution to the module dependency problem. I
> like best your idea of a dummy. Why do you need checks on entry points?
> Because you want it to fail gracefully in the absence of the real library?
> Isn't that
35 matches
Mail list logo
