If you feel like fixing all the build warnings due to code not having
generics and the like, sure! :-)
This is one of those "if it ain't broke, don't fix it" things. There is
nothing wrong with source level 1.6 for infrequently modified code that's
stable. If it were undergoing a major rewrite, I
+1 (not binding)
Downloaded and verified sha512 digest
Checked NOTICE and LICENSE
Built basic cluster with Oracle JDK 8 on Ubuntu Linux 18.04
Launched built artefact
Greets,
Alex
Il giorno mar 16 lug 2019 alle ore 17:58 Neil C Smith
ha scritto:
> Dear all,
>
> This is our second voting candid
Verified - sources:
* 11.1-vc2/netbeans-11.1-vc2-source.zip contains same file as the git
tag 11.1-vc2
* sha512sum matched
* netbeans-11.1-vc2-source.zip.asc file verified
* build succeeds and yields a working netbeans 11.1
binary netbeans-11.1-vc2-bin.zip:
* verified detached signature
+1 (binding)
Asc+sh512
Thks Neil
Regards
Eric
-Message d'origine-
De : Neil C Smith
Envoyé : mardi 16 juillet 2019 17:58
À : dev
Objet : [VOTE] Release Apache NetBeans 11.1 [vote candidate 2]
Dear all,
This is our second voting candidate for the 11.1 release of Apache NetBeans,
foll
Hi all,
I just compiled the sources of beta-4 with JAVA 11 on Windows:
JDK: OpenJ9 11.0.3-0.14.3
OS: Windows 10 x64
Ant: 1.10.6
JAVA_HOME: OpenJ9 8u212-0.14.2
Command: ant -Djavac.executable="C:\Program Files\Java\openJ9-11"
-Dpermit.jdk9.builds=true
Build Time: 45 minutes 11 seconds
I will try
Dear all,
This is our second voting candidate for the 11.1 release of Apache
NetBeans, following 11.1-beta4 and a fix to the critical issue that
made us pull the first vote. There have been no changes between beta4
and this voting candidate.
Apache NetBeans 11.1 constitutes all clusters in the A
http://bits.netbeans.org/maven2 is back!
Gj
On Sun, Jul 14, 2019 at 5:24 PM Emilian Bold wrote:
> Well, I expect that people using 8.2 NBMs would need that.
>
> --emi
>
>
> On Sun, Jul 14, 2019 at 2:20 PM Antonio Vieiro wrote:
> >
> > No idea. Where is this being used?
> >
> >
> > En 14 jul. 2
On Tue, 16 Jul 2019 at 13:07, Geertjan Wielenga wrote:
>
> From my point of view, that should be OK, since there's nothing new in vc2
> compared to beta-4, it might be best to rename beta-4 everywhere to vc2,
> assuming everything can be tagged appropriately,
We're OK. Build went through eventua
Toni is not using it, see above.
Gj
On Tue, Jul 16, 2019 at 4:14 PM Zoran Sevarac wrote:
> On Tue, Jul 16, 2019 at 9:18 AM Geertjan Wielenga
> wrote:
>
> > The HTML UI API, that is DukeScript, so you should ask Toni if/how he is
> > using that library.
> >
> > No, we are not simply going to re
On Tue, Jul 16, 2019 at 9:18 AM Geertjan Wielenga
wrote:
> The HTML UI API, that is DukeScript, so you should ask Toni if/how he is
> using that library.
>
> No, we are not simply going to remove this or any other library.
>
It does not work anyway because it has hard coded dependency to jar fro
>From my point of view, that should be OK, since there's nothing new in vc2
compared to beta-4, it might be best to rename beta-4 everywhere to vc2,
assuming everything can be tagged appropriately,
Gj
On Tue, Jul 16, 2019 at 1:51 PM Neil C Smith wrote:
> On Tue, 16 Jul 2019 at 10:38, Neil C Smi
On Tue, 16 Jul 2019 at 10:38, Neil C Smith wrote:
>
> Considered just renaming it, but will
> trigger a separate build / build number in case it affects anything
> else.
Seems to be a massive amount of backlog in Jenkins at the moment,
coupled with first build attempt triggering an Xfvb error (
Ok - having a quick look at github, it looks like my change to
EnterpriseCatalog.java might have been regresessed by 3e7e6fe6,
specifically:
private static final String RESOURCE_PATH =
"nbres:/org/netbeans/modules/j2ee/dd/impl/resources/"; //NO18N
Changed back to:
private static final String RE
Hi All,
So, a slightly pre-emptive thread while the release build for a second
vote candidate is underway.
At some point after release of NB 11.1, we will open the merge window
for NB 11.2. This will be at least a few days after the NB 11.1
release process is completed, and will be notified on h
Yes, agreed -- clearly we need to be very disciplined with this release
structure. But I think we did it the right way, i.e., we should have a very
clear schedule, as we do know, but we should be flexible with it, as we
have been -- and so long as we release by the end of the month, which seems
ver
On Tue, 16 Jul 2019 at 10:48, Geertjan Wielenga wrote:
> I think we should not add any new code to a vc, that's where things went
> wrong with vc1. It would be a cool thing to strive for: no new code in a
> voting candidate.
I'm planning on documenting a few thoughts as we all review the new
rele
Good point, agreed.
Gj
On Tue, Jul 16, 2019 at 11:52 AM Neil C Smith wrote:
> On Tue, 16 Jul 2019 at 10:41, Geertjan Wielenga
> wrote:
> >
> > Sure, it's just that we've been getting questions on Twitter with people
> > pointing to the July 15 date. Either we state that we release on that
> da
On Tue, 16 Jul 2019 at 10:41, Geertjan Wielenga wrote:
>
> Sure, it's just that we've been getting questions on Twitter with people
> pointing to the July 15 date. Either we state that we release on that date
> (as currently stated) or we say something different there. I think it's a
> good sign p
On Tue, Jul 16, 2019 at 11:38 AM Neil C Smith wrote:
> On Sun, 14 Jul 2019 at 11:18, Geertjan Wielenga
> wrote:
> > Looks like we're ready for vc2. :-)
>
> Now I agree with you! :-) Comments here look good and checked through
> JIRA, so going to trigger the release build. I like the fact that
Sure, it's just that we've been getting questions on Twitter with people
pointing to the July 15 date. Either we state that we release on that date
(as currently stated) or we say something different there. I think it's a
good sign people are saying 'hey, where's NetBeans' and I think it's also
fin
On Sun, 14 Jul 2019 at 11:18, Geertjan Wielenga wrote:
> Looks like we're ready for vc2. :-)
Now I agree with you! :-) Comments here look good and checked through
JIRA, so going to trigger the release build. I like the fact that vc2
will be the same as beta4! Considered just renaming it, but w
They have been donated, just not integrated. If you would like to take on
that task, the sources can be provided -- we look forward to someone
integrating them.
Gj
On Tue, Jul 16, 2019 at 10:43 AM Dameron, Yann
wrote:
> Hi,
>
> We upgraded our application to NB11 and I’m also interested by the
On Tue, 16 Jul 2019 at 09:01, Christian Lenz wrote:
> Open your eyes, there is more than only Java .
Maybe open your eyes and realise you're not the only person with a
decade plus of frontend work involved in this discussion, and that
this has nothing to do with whether it's Java or not, and ever
Hi Michal!
Great to have someone else on board working on a solution here -- and on
the infrastructure as a whole.
We always need "someone else" and you should feel very welcome indeed.
Indeed, if we can move to a complete solution that does everything needed,
that is wonderful, let's indeed wor
Hi,
We upgraded our application to NB11 and I’m also interested by the I10N bundles…
I haven’t found them on released artefacts so I guess they have not yet been
donated. Am I right ?
I guess we can safely reuse the ones from NB8.2. Do you see an issue relying on
them waiting more recent ones ?
Pete,
thanks for the suggestion.
The project was indeed "migrated" from NetBeans 8.2 - but it's a Maven project.
So the only (project) configuration file there is, is the pom.xml
There is nbactions.xml but that does not seem to contain any entries relevant
for that.
nb-configuration.xml contai
On Tue, 16 Jul 2019 at 00:36, Michał Dymecki wrote:
> Neil and Antonio commited that not working code into the repository, now
> they want to close the PR that fixes their code, and when Chris wants to
> help with fixing it too, he's being disrespected. Did I miss something?
Maybe stop throwing g
I didn't say anything at all about stability. Only that this is the current
hype.
But the main point is -- do we need more people working on the
infrastructure of the website? Or do we need more people (any people)
working on the content -- that's where the problem is, people (e.g., you?)
are not
Hi Thomas,
I was banned from bringing a laptop on holiday, so this is from memory -
please excuse any mistakes.
I submitted https://github.com/apache/netbeans/pull/1266 to update the
enterprise catalog to look for JavaEE XSDs in org/netbeans/modules/j2ee/dd/
impl/resources
I'm curious why NB is
Gulp and Node next hype and not stable? 😃 Funny. I’m out of the discussion.
Sry, but I think that you don’t know what you are talking about. IMHO.
Open your eyes, there is more than only Java 😉.
Cheers
Chris
Von: Geertjan Wielenga
Gesendet: Dienstag, 16. Juli 2019 09:29
An: dev
Betreff: Re:
Seems scary. :-) Neil and Antonio know how the current system works, and
'someone else' is the person we're going to need to depend on for a
completely new system that has as its only benefit that the latest hyped
technology stack is used instead of a stable one? Would that direction be
acceptable
On Tue, 16 Jul 2019, 07:35 Zoran Sevarac, wrote:
> As far as I know its used by html ui api
> https://github.com/apache/netbeans/tree/master/platform/api.htmlui
Check out the Third Party Libraries thread from the other day too. On JDK
11+ the OpenJFX libraries are downloaded alongside nb-javac,
➢ You're for merging the PR and there is someone else who wants to work on
➢ it, if this changes? If what changes? And who is "someone else"?
Geertjan, look inside he PR, the guy who created it, is someone else 😉.
Cheers
Chris
Von: Geertjan Wielenga
Gesendet: Montag, 15. Juli 2019 23:39
The HTML UI API, that is DukeScript, so you should ask Toni if/how he is
using that library.
No, we are not simply going to remove this or any other library.
Gj
On Tue, 16 Jul 2019 at 08:35, Zoran Sevarac wrote:
> On Mon, Jul 15, 2019 at 11:51 PM Geertjan Wielenga
> wrote:
>
> > Depends, whe
34 matches
Mail list logo
