Hi.
There is a plan for a new Hibernate module?
--
*Wilmar A. Giraldo Sanchez*
Hi,
I added my evaluation to the bug and created a related PR.
Greetings
Matthias
Am Donnerstag, den 10.05.2018, 10:15 +0200 schrieb Geertjan Wielenga:
> Hi all,
>
> I'd like to get ahead of a discussion we'll inevitable end up in if
> we
> don't deal with this before we try to do the
This email thread is also a form of brainstorming. I have no problems exploring
ideas even if they never get implemented.
Starting from my plan of increasing the vertical space available for actual
code in the diff top component, several other ideas were explored:
* the fact the even if we
Excellent.
Gj
On Thu, May 10, 2018 at 6:45 PM, Mark Struberg
wrote:
> Yes, last one (305) seems to now also got marked as resolved just a few
> hours ago.
> One more stone out of the way for a next NB release.
>
> txs and LieGrue,
> strub
>
> > Am 10.05.2018 um 09:21
Yes, last one (305) seems to now also got marked as resolved just a few hours
ago.
One more stone out of the way for a next NB release.
txs and LieGrue,
strub
> Am 10.05.2018 um 09:21 schrieb Geertjan Wielenga
> :
>
> On Wed, May 9, 2018 at 7:30 PM, Mark
Hi all,
I remember a discussion with Jan at a Munich event about the possibility of
using jigsaw modules within NetBeans.
With the upcoming new JavaFX SDK (downloadable now) as modules this becomes
an interesting approach for integrating JavaFX and NetBeans..
Any pointers maybe even a working
If there are configurable options to change it why do you care? You can
just keep the settings how you like it and you will be happy. From what I
read in the chain it sounds like this was a suggestion a while back.
On Thu, 10 May 2018, 15:17 Matthias Bläsing,
wrote:
>
Am Donnerstag, den 10.05.2018, 09:25 -0400 schrieb Emilian Bold:
> Not sure why you have to be so adamant about this.
Because you try to force your use-case down my throat. Yes I choose my
hardware to get my work done and this worked good with netbeans. All I
heard till now torpedes this. This is
On Thu, May 10, 2018 at 3:26 PM, Emilian Bold
wrote:
> What's stopping us to delete it: is the .class file used?
>
> Like I've said, it's trivial. If we don't need it, let's delete it.
>
I think it is less about what the class is doing, and more how it was
compiled.
On Thu, 10 May 2018 at 13:10 Sven Reimers wrote:
> +1 for branching.
>
> Concerning the var support PR's.. Do we already have a roadmap for the next
> release? If it takes too long to integrate we could just move those fixes
> to the next (Patch-)Release..?
>
+1 to
It is used here:
https://github.com/apache/incubator-netbeans/blob/master/nbi/engine/src/org/netbeans/installer/utils/applications/JavaUtils.java
...and here:
What's stopping us to delete it: is the .class file used?
Like I've said, it's trivial. If we don't need it, let's delete it.
--emi
‐‐‐ Original Message ‐‐‐
On 10 May 2018 4:23 PM, Geertjan Wielenga
wrote:
> Its not a question of licensing but of
Not sure why you have to be so adamant about this.
I could add some flag per topcomponent that says 'no-individual-tab'. Then, if
I have a floating window holding that single topcomponent it won't have the
title bar.
For people that need or are used to the old style we could have a checkbox in
Its not a question of licensing but of compiled source code not being
allowed to be in the release:
https://lists.apache.org/thread.html/73ce8a13d5c13b56c300e4aad1e9e9bc8351ea6e836f5dc60a55cfaa@%3Cgeneral.incubator.apache.org%3E
Gj
On Thu, May 10, 2018 at 3:04 PM, Emilian Bold
How do we know the license for TestJDK? Was it not owned by Oracle and donated?
Not sure where it's being used but by looking at the bytecode it's an
absolutely trivial class we could rewrite at any time. It prints to System.out
these system properties:
* java.version
* java.vm.version
*
Am Mittwoch, den 09.05.2018, 18:59 -0400 schrieb Emilian Bold:
> > That would be nice--but how would one dock the TopComponent again
> > if there is no tab to right-click or drag?
>
> Closing the frame would dock the contained TopComponent "back".
This breaks current behaviour where closing the
> Closing the frame would dock the contained TopComponent "back".
Ah, not a bad idea! I assume dragging an additional tab into the frame
would make tabs appear again.
On 5/9/18, 6:59 PM, "Emilian Bold" wrote:
>> That would be nice--but how would one dock the
+1 for branching.
Concerning the var support PR's.. Do we already have a roadmap for the next
release? If it takes too long to integrate we could just move those fixes
to the next (Patch-)Release..?
Sven
Geertjan Wielenga schrieb am Do., 10.
Mai 2018, 12:39:
Makes sense.
Note there are several PRs that we need to include in the 9.0 release,
e.g., related to 'var' support, but we can push those to the branch after
merging into main.
Gj
On Thu, May 10, 2018 at 12:32 PM, Jiří Kovalský
wrote:
> Hi folks,
>
>since we only
Hi folks,
since we only have two remaining 9.0 blockers [1] which are
infrastructure related problems I suggest that we create
releases/release90 branch from master. In order to fix #330 we need to
update branding and test new location of the Update Center so I think
the right time has
I've looked around and cannot find the bug in jira, so i'm checking if
it is already known.
When i build a project (target jar) with do.depend=true for a second
time after clean, the following is thrown:
java.lang.ClassFormatError: Invalid Constant Pool entry Type 19
at
Very nice.
Gj
On Thursday, May 10, 2018, John McDonnell wrote:
> Need to tweak some stuff, was in a JUnit 5 chat room last night, found out
> I made a slightly limited assumption around working out if a method is
> testable or not, once that's resolved I'll commit and
Need to tweak some stuff, was in a JUnit 5 chat room last night, found out
I made a slightly limited assumption around working out if a method is
testable or not, once that's resolved I'll commit and push :)
John
On 10 May 2018 at 09:40, Geertjan Wielenga
Hi John,
Great. Indeed, JUnit 5 support is highly desired, if we can get something
in already for the 9.0 release, that would be nice to have -- and once your
starting point is merged and your plans are discussed in a thread here,
more will join in I'm sure.
Gj
On Wed, May 9, 2018 at 5:11 PM,
It's a really cool idea to have a weekly update like this.
Gj
On Thu, May 10, 2018 at 12:03 AM, Emilian Bold
wrote:
> This seems interesting. The mailing list seems like the proper place, I
> would certainly not be reading about it on the wiki right now.
>
> I
Hi all,
Re: https://issues.apache.org/jira/browse/NETBEANS-410
There's still one .class file that we have not solved yet:
nbi/engine/src/org/netbeans/installer/utils/applications/TestJDK.class
It is still present:
Hi all,
I'd like to get ahead of a discussion we'll inevitable end up in if we
don't deal with this before we try to do the release:
https://issues.apache.org/jira/browse/NETBEANS-312
That issue comes from the IPMC review by Justin McLean for the 2nd attempt
at the Beta release:
On Wed, May 9, 2018 at 7:30 PM, Mark Struberg
wrote:
> hi folks!
>
> Had a talk with Jaroslav this morning at GeeCON about tasks we need to
> resolve befor the next release.
>
> I just looked up the old thread. Those are the tickets we still need to
> address.
>
The
28 matches
Mail list logo