That's been my question about: I do not know if some module needs OSGi,
JEE was just an idea for what could *probably* need OSGi. Probably my
question wasn't exact.
Kind regards
Peter
Am 09.11.18 um 18:47 schrieb Emilian Bold:
PS: I what way is the broken OSGi break our JEE support? I would
16 GB. Its a developer laptop.
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing
How do you come to the conclusion that his java heap is swapped to disk?
OP, how much RAM is on your machine?
On 2018/11/09 10:22:40, Tim Boudreau wrote:
> >
> > But may be that's not enough, I've raised it to 4092m. May be that'll
> > perform better.
> >
>
> Turn it DOWN not up. Your
Telling the truth, bug priorities are used very subjective right now.
Though AFAIK we have a good guideline somewhere on the old wiki which
helps to categorize the issue priorities, there are a number of people
not following that guide (I do not really blame them.)
We have simply no resource
On Fri, 9 Nov 2018 at 15:57, Christian Lenz wrote:
> it would be nice, if we can have a look into the list of all criticals that
> are open, after release of NetBeans 10.0:
...
> Could be a Milestone for the next NetBeans Version.
Maybe some rethinking of how we use bug priorities? Shouldn't
The critical list is quite reasonable, at least half of them even
resolvable with a little effort.
To get a picture what is going on the project regarding the issues,
bookmark this link:
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12332552
On 11/9/18 9:28 AM, Geertjan
PS: I what way is the broken OSGi break our JEE support? I would like
to see an issue explaining this.
--emi
On Fri, Nov 9, 2018 at 2:23 PM Peter Nabbefeld wrote:
>
>
> Hello,
>
> OSGi support is obviously broken since NB 9, see
> https://github.com/mojohaus/nbm-maven-plugin/issues/52 for
Thanks Johannes! Do you want to make a GitHub PR for this or should we make one?
--emi
On Fri, Nov 9, 2018 at 6:08 PM Johannes Boesl wrote:
>
> Hey there,
>
> here are the changes I applied to NB 9 to have osgi bundles working
> again with java 9.
>
> With kind regards,
> Johannes Boesl
>
>
> Am
I can't check right now but does NetBeans *ship* OSGi modules running
in the OSGi container as such?
--emi
On Fri, Nov 9, 2018 at 2:23 PM Peter Nabbefeld wrote:
>
>
> Hello,
>
> OSGi support is obviously broken since NB 9, see
> https://github.com/mojohaus/nbm-maven-plugin/issues/52 for details.
Great, fully agree. Aside from focusing on Java/Jakarta EE for the next
release, it would be excellent to have a bug-fix oriented release of
all/most critical bugs.
Gj
On Fri, Nov 9, 2018 at 4:57 PM Christian Lenz
wrote:
> Hey Guys,
>
> it would be nice, if we can have a look into the list of
Thanks Tim. That turned what little I know about garbage collection on its
head. Need to do some more reading.
Thanks Geertjan, I knew that button was there for a reason :).
-
To unsubscribe, e-mail:
Hey there,
here are the changes I applied to NB 9 to have osgi bundles working
again with java 9.
With kind regards,
Johannes Boesl
Am 09.11.18 um 16:56 schrieb Chuck Davis:
> My understanding is that OSGi was developed as a client side technology for
> small form factor devices. It's easy to
Hey Guys,
it would be nice, if we can have a look into the list of all criticals that are
open, after release of NetBeans 10.0:
Advanced search: project = NETBEANS AND issuetype = Bug AND status in (Open,
"In Progress", Reopened) AND priority = Critical
Could be a Milestone for the next
My understanding is that OSGi was developed as a client side technology for
small form factor devices. It's easy to think of it as a server technology
since all the current app servers are based on OSGi.
Since NB is only for Swing I have started looking at the possibility of
creating a JFX
I exported my Keymap profile from NetBeans 8.2 (Only the KeyBindings), after I
imported them into NB 10.0 VC3, I got a message that not all bindings could be
found, see the log.
I didn’t have a look into the log but I wanted to test it so I hit Ctrl + Alt +
R, Ctrl + Alt + M for Revert
https://github.com/apache/incubator-netbeans/tree/master/profiler
Possibly this specifically:
https://github.com/apache/incubator-netbeans/tree/master/profiler/lib.profiler/native
Gk
On Fri, Nov 9, 2018 at 11:33 AM Peter Hull wrote:
> On Fri, Nov 9, 2018 at 9:52 AM Geertjan Wielenga
>
Provide a patch, or jboesl, in the issue you reference:
AFAIK the felix version currently intgerated with netbeans doesn't work
> with Java9 or later. I did update it in my appilcation to 5.6.10 and now it
> works.
>
Apache NetBeans 10 does not support Java EE, that's the focus of the
release
Hello,
OSGi support is obviously broken since NB 9, see
https://github.com/mojohaus/nbm-maven-plugin/issues/52 for details. I've
created NETBEANS-1638 as a critical bug.
The question here is, how important is OSGi for functionality of
NetBeans itself (e.g. JEE support), i.e. does it
On Fri, Nov 9, 2018 at 9:52 AM Geertjan Wielenga
wrote:
>
> Does the problem occur with Apache NetBeans 9 as well?
Just tested it now, the same error occurs for Apache NetBeans 9 (NB is
running under JDK1.8, the profiled app running under JDK 11)
I've updated the JIRA.
Could someone point me to
Hello Tim,
the question is about the wiki article - it just should be turned into a
good description instead of redirecting to an outdated issue.
So it's not the point to argue here for the best practice - it seems
that has been done in the issues' comments.
If nobody else will update the
>
> But may be that's not enough, I've raised it to 4092m. May be that'll
> perform better.
>
Turn it DOWN not up. Your Java heap is in your swap file, and has to be
swapped back in to memory for the garbage collector to scan it. So your
machine is furiously thrashing bytes off disk and into
Maven's 'system' scope looks like it is good for something, but it rarely
(possibly never) is.
The few times I thought that was what I wanted, what I actually wound up
using was a entry where the URL file: protocol with a relative
path to some folder where the needed JAR files were pre-copied
Thank You, found only a bug history on nabble, but without the zip
files. Could the explanations be turned into a wiki article, or are
there any copyright issues?
Kind regards
Peter
Am 09.11.18 um 00:38 schrieb Emilian Bold:
Since codehaus is gone, we could use
>
> But now that I did, let me making thread useful by asking how does one
> profile netbeans.
>
There's blue buttons for self-profiling NetBeans in the main toolbar.
Gj
On Fri, Nov 9, 2018 at 3:35 AM venkatram.akkin...@gmail.com <
venkatram.akkin...@gmail.com> wrote:
> Hi
>
> Thanks for the
Does the problem occur with Apache NetBeans 9 as well?
Gj
On Fri, Nov 9, 2018 at 10:14 AM Peter Hull wrote:
> As mentioned elsewhere, during netcat I found that attempting to
> profile Java applications under Windows crashes the JVM. This is
> reported as
As mentioned elsewhere, during netcat I found that attempting to
profile Java applications under Windows crashes the JVM. This is
reported as https://issues.apache.org/jira/browse/NETBEANS-1428 and
thanks to work by Eduardo Quintanilla, it appears that Java 9 and
later are all affected.
I'd like
26 matches
Mail list logo
