Re: NetBeans garbage output problem report
On 12/07/15 20:49, Rafael Sadowski wrote: [...] > Hi Scott, > > thank you for your feedback. Could you check out the new updated version > from github and play with -J-Dawt.useSystemAAFontSettings=XXX in > bin/netbeans. For me lcd works fine without garbage output. > > Here are all options for useSystemAAFontSettings: > http://wiki.netbeans.org/FaqFontRendering > > Once again, thank you very much! I hope useSystemAAFontSettings will the > output problem. > this doesn't work for me as well, what is the output of `pkg_info | grep font` ? Cheers Giovanni
Re: NetBeans garbage output problem report
On Wed Dec 02, 2015 at 10:57:19PM -0700, Scott Walters wrote: > On 11/24/15, Rafael Sadowskiwrote: > > On Sat Nov 14, 2015 at 03:36:36PM -0700, Scott Walters wrote: > >> Hopefully this is going to the correct place. > > > > Hi Scott, > > > > could you or maybe other netbeans user test/run the current state of: > > > > https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans > > Hi Rafael, > > Thanks for your work on this, and sorry for the slow response. > I'm not normally a NetBeans user (or IDE user), so this has been educational. > > I set up OpenBSD Ports and checked out that github repo into it, and > made the /etc/mk.conf config change suggested by the README.md for > openbsd-wip. Java took a good while to build, chewing on a source > file someone mentioned in this thread. I uninstalled the other > NetBeans then pkg_add'd > /usr/ports/packages/amd64/all/netbeans-8.1.tgz. > > I'm now unable to create a project in NetBeans. Picking New Project > -> Java -> Next, I get this screen ("Finding Feature" with the Next > button greyed out), and it sits for at least hours for me. > > I'm sure that has a lot more to do with my system and NetBeans 8.1 > than it does with the patch for the garbage output issue, but my first > attempt at testing that patch has been frustrated. > > Blowing away the NetBeans directories in my homedir didn't help. > > I'll try to Google this problem and fix it and get further and report. > > Thanks again, > -scott Hi Scott, thank you for your feedback. Could you check out the new updated version from github and play with -J-Dawt.useSystemAAFontSettings=XXX in bin/netbeans. For me lcd works fine without garbage output. Here are all options for useSystemAAFontSettings: http://wiki.netbeans.org/FaqFontRendering Once again, thank you very much! I hope useSystemAAFontSettings will the output problem. Cheers, Rafael
Re: NetBeans garbage output problem report
Scott Walters wrote: I'm now unable to create a project in NetBeans. Picking New Project -> Java -> Next, I get this screen ("Finding Feature" with the Next button greyed out) Oh, and Scott, try changing /usr/local/netbeans/etc/netbeans.conf #netbeans_default_options="-J-client -J-Xss2m -J-Xms32m -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true -J-Dsun.java2d.dpiaware=true -J-Dsun.zip.disableMemoryMapping=true -J-Dplugin.manager.check.updates=false -J-Dplugin.manager.check.interval=NEVER" # Needs more memory than default -- jax 20151115 netbeans_default_options="-J-client -J-Xss8m -J-Xms256m -J-Xmx512m -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true -J-Dsun.java2d.dpiaware=true -J-Dsun.zip.disableMemoryMapping=true -J-Dplugin.manager.check.updates=false -J-Dplugin.manager.check.interval=NEVER" -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
On 11/24/15, Rafael Sadowskiwrote: > On Sat Nov 14, 2015 at 03:36:36PM -0700, Scott Walters wrote: >> Hopefully this is going to the correct place. >> http://www.openbsd.org/faq/faq15.html#Problems says to mail the >> maintain, and http://openports.se/devel/netbeans gives >> http://openports.se/bbmaint.php?maint=ports|a|openbsd.org as the >> maintainer. > > Hi Scott, > > could you or maybe other netbeans user test/run the current state of: > > https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans > > I think, I fixed the output problem. I would be happy to read from you. Hi Rafael, No go. Still getting boxes in the "Output" window. I removed the apache-ant, jre, and jdk already installed and installed the ones built into /usr/ports/packages/amd64/all: -rw-r--r-- 3 root wheel 39138268 Dec 2 18:47 jre-1.8.0.45p0v0.tgz -rw-r--r-- 3 root wheel 77591429 Dec 2 18:47 jdk-1.8.0.45p0v0.tgz -rw-r--r-- 3 root wheel4585757 Dec 2 17:49 groff-1.22.3p2.tgz -rw-r--r-- 3 root wheel5674843 Dec 2 17:47 apache-ant-1.9.6.tgz -rw-r--r-- 3 root wheel 324154749 Dec 2 17:43 netbeans-8.1.tgz Neither "UTF" nor "ASCII" appear in my environment. I blew away /usr/local/netbeans entirely before re-installing, and blew away ~/NetBeansProjects and ~/.netbeans before launching it. I'm not finding anything of any capitalization in /etc/ matching "netbeans". I'm not sure why my system differs at this point. Ideas on other things to blow away? Thanks, -scott
Re: NetBeans garbage output problem report
On 12/3/15, Jack J. Woehrwrote: > Scott Walters wrote: >> I'm now unable to create a project in NetBeans. Picking New Project -> >> Java -> Next, I get this screen ("Finding >> Feature" with the Next button greyed out) > Oh, and Scott, try changing /usr/local/netbeans/etc/netbeans.conf > > netbeans_default_options="-J-client -J-Xss8m -J-Xms256m -J-Xmx512m > -J-Dapple.laf.useScreenMenuBar=true > -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true > -J-Dsun.java2d.dpiaware=true > -J-Dsun.zip.disableMemoryMapping=true -J-Dplugin.manager.check.updates=false > -J-Dplugin.manager.check.interval=NEVER" It looks like this is another one of those NetBeans problems that has been around for a long time: https://netbeans.org/bugzilla/show_bug.cgi?id=127248 2007 seems to have been a bad year for NetBeans. My original issue was from then as well. bash-4.3# pkg_info | grep -i jdk jdk-1.7.0.80p0v0Java2(TM) SE Dev Kit v1.7.0.80 Switching it to use 1.8.x instead worked around the problem, and it goes on to show a bouncy progress meter then change to present other options. Looking at the ticket, it seems like it's a thread implementation timing bug, so the fundamental problem is very much not fixed. For the sake of the OpenBSD port, it seems like it would be a good idea to require 1.8.x if other people can verify that this don't work with jdk-1.7. I'm imagining other platforms than amd64 would likely have problems as well. More diagnostic goo follow (solution moved to the top): Changing netbeans_default_options to the above and restarting it, it still gets stuck on that same dialog box in the same way. I have this in my /etc/login.conf: default:\ :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/local/sbin:\ :umask=022:\ :datasize-max=infinity:\ :datasize-cur=infinity:\ :maxproc-max=infinity:\ :maxproc-cur=infinity:\ :openfiles-cur=4096:\ :stacksize-cur=32M:\ :localcipher=blowfish,8:\ :ypcipher=old:\ :tc=auth-defaults:\ :tc=auth-ftp-defaults: staff:\ :datasize-cur=infinity:\ :datasize-max=infinity:\ :maxproc-max=infinity:\ :maxproc-cur=infinity:\ :ignorenologin:\ :requirehome@:\ :tc=default: The end of /home/scott/.netbeans/8.1/var/log/messages.log reads: State Data Manager java.lang.Thread.sleep:-2 org.eclipse.osgi.internal.baseadaptor.StateManager.run:297 java.lang.Thread.run:745 Inactive RequestProcessor thread [Was:OpenIDE-request-processor-1/org.netbeans.core.startup.preferences.NbPreferences$1] java.lang.Object.wait:-2 org.openide.util.RequestProcessor$Processor.run:2002 Thread-2 java.lang.Object.wait:-2 java.lang.Object.wait:503 java.util.prefs.AbstractPreferences$EventDispatchThread.run:1476 Active Reference Queue Daemon java.lang.Object.wait:-2 java.lang.Object.wait:503 org.openide.util.lookup.implspi.ActiveQueue.removeBetter:225 org.openide.util.lookup.implspi.ActiveQueue.access$400:57 org.openide.util.lookup.implspi.ActiveQueue$Daemon.run:180 process reaper sun.misc.Unsafe.park:-2 java.util.concurrent.locks.LockSupport.parkNanos:226 java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill:460 java.util.concurrent.SynchronousQueue$TransferStack.transfer:359 java.util.concurrent.SynchronousQueue.poll:942 java.util.concurrent.ThreadPoolExecutor.getTask:1068 java.util.concurrent.ThreadPoolExecutor.runWorker:1130 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:745 Inactive RequestProcessor thread [Was:Find Modules/org.netbeans.modules.ide.ergonomics.fod.FindComponentModules$2] java.lang.Object.wait:-2 org.openide.util.RequestProcessor$Processor.run:2002 Framework Active Thread java.lang.Object.wait:-2 org.eclipse.osgi.framework.internal.core.Framework.run:1862 java.lang.Thread.run:745 Inactive RequestProcessor thread [Was:WinSysModuleChangeHandler/org.netbeans.core.windows.persistence.ModuleChangeHandler$1] java.lang.Object.wait:-2 org.openide.util.RequestProcessor$Processor.run:2002 AWT-Shutdown java.lang.Object.wait:-2 java.lang.Object.wait:503 sun.awt.AWTAutoShutdown.run:296 java.lang.Thread.run:745 Reference Handler java.lang.Object.wait:-2 java.lang.Object.wait:503 java.lang.ref.Reference$ReferenceHandler.run:133 WARNING [org.netbeans.core.TimableEventQueue]: too much time in AWT thread org.netbeans.modules.sampler.InternalSampler@a14f9d8 WARNING [org.netbeans.core.TimableEventQueue]: no snapshot taken Cheers, -scott
Re: NetBeans garbage output problem report
Scott Walters wrote: I'm now unable to create a project in NetBeans. Picking New Project -> Java -> Next, I get this screen ("Finding Feature" with the Next button greyed out), and it sits for at least hours for me From my experience this is probably NB throwing memory allocation errors. Did you check the NetBeans log (in your home dir)? -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
On 11/24/15, Rafael Sadowskiwrote: > On Sat Nov 14, 2015 at 03:36:36PM -0700, Scott Walters wrote: >> Hopefully this is going to the correct place. > > Hi Scott, > > could you or maybe other netbeans user test/run the current state of: > > https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans Hi Rafael, Thanks for your work on this, and sorry for the slow response. I'm not normally a NetBeans user (or IDE user), so this has been educational. I set up OpenBSD Ports and checked out that github repo into it, and made the /etc/mk.conf config change suggested by the README.md for openbsd-wip. Java took a good while to build, chewing on a source file someone mentioned in this thread. I uninstalled the other NetBeans then pkg_add'd /usr/ports/packages/amd64/all/netbeans-8.1.tgz. I'm now unable to create a project in NetBeans. Picking New Project -> Java -> Next, I get this screen ("Finding Feature" with the Next button greyed out), and it sits for at least hours for me. I'm sure that has a lot more to do with my system and NetBeans 8.1 than it does with the patch for the garbage output issue, but my first attempt at testing that patch has been frustrated. Blowing away the NetBeans directories in my homedir didn't help. I'll try to Google this problem and fix it and get further and report. Thanks again, -scott
Re: NetBeans garbage output problem report
Stuart Henderson wrote: You could try raising the datasize limit (login.conf and/or ulimit -d). Ah yes. Forgot about that. Never came before :) Thank you. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
On 2015/11/28 18:06, Jack J. Woehr wrote: > Jack J. Woehr wrote: > > #netbeans_default_options="-J-client -J-Xss2m -J-Xms32m ... > --- > netbeans_default_options="-J-client -J-Xss8m -J-Xms256m -J-Xmx512m ... > > This I had to do with both ports. Not sure the -Xss is necessary, but the > heap definitely is. > > If I up -Xmx to 768m or 1g Netbeans crashes with a can't allocate sorta > message (on my underloaded 8g machine), specific text on request. You could try raising the datasize limit (login.conf and/or ulimit -d).
Re: NetBeans garbage output problem report
Rafael Sadowski wrote: could you or maybe other netbeans user test/run the current state of: https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans I think, I fixed the output problem. I would be happy to read from you. I am trying to build this. It starts with the JDK 1.8.0.45 port. Seems to hang and spin on ad_x86_64_gen.cpp... Compiling /usr/ports/pobj/jdk-1.8.0.45/openjdk-8u45b14-bsd-port-20150618/hotspot/src/share/vm/compiler/abstractCompiler.cpp Compiling /usr/ports/pobj/jdk-1.8.0.45/openjdk-8u45b14-bsd-port-20150618/hotspot/src/share/vm/utilities/accessFlags.cpp Compiling ../generated/adfiles/ad_x86_64.cpp Compiling ../generated/adfiles/ad_x86_64_clone.cpp Compiling ../generated/adfiles/ad_x86_64_expand.cpp Compiling ../generated/adfiles/ad_x86_64_format.cpp Compiling ../generated/adfiles/ad_x86_64_gen.cpp forever, Here is 'top' load averages: 1.17, 1.18, 1.04 73 processes: 71 idle, 2 on processor CPU0 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU1 states: 99.6% user, 0.0% nice, 0.4% system, 0.0% interrupt, 0.0% idle CPU2 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU3 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU4 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU5 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU6 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU7 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Memory: Real: 1129M/1933M act/tot Free: 5981M Cache: 661M Swap: 0K/0K PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 31198 root 640 1077M 1081M onproc- 13:19 99.02% cc1plus -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
On 2015/11/28 10:21, Jack J. Woehr wrote: > Rafael Sadowski wrote: > >could you or maybe other netbeans user test/run the current state of: > >https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans > >I think, I fixed the output problem. I would be happy to read from you. > > I am trying to build this. It starts with the JDK 1.8.0.45 port. Seems to > hang and spin on ad_x86_64_gen.cpp... It takes a while to build, you could just pkg_add it to save time though. > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND > 31198 root 640 1077M 1081M onproc- 13:19 99.02% cc1plus No need to use root for building packages..
Re: NetBeans garbage output problem report
Il 28 novembre 2015 17:21:53 GMT+00:00, "Jack J. Woehr"ha scritto: >Rafael Sadowski wrote: >> could you or maybe other netbeans user test/run the current state of: > >> https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans >> I think, I fixed the output problem. I would be happy to read from >you. > >I am trying to build this. It starts with the JDK 1.8.0.45 port. Seems >to hang and spin on ad_x86_64_gen.cpp... > >Compiling >/usr/ports/pobj/jdk-1.8.0.45/openjdk-8u45b14-bsd-port-20150618/hotspot/src/share/vm/compiler/abstractCompiler.cpp >Compiling >/usr/ports/pobj/jdk-1.8.0.45/openjdk-8u45b14-bsd-port-20150618/hotspot/src/share/vm/utilities/accessFlags.cpp >Compiling ../generated/adfiles/ad_x86_64.cpp >Compiling ../generated/adfiles/ad_x86_64_clone.cpp >Compiling ../generated/adfiles/ad_x86_64_expand.cpp >Compiling ../generated/adfiles/ad_x86_64_format.cpp >Compiling ../generated/adfiles/ad_x86_64_gen.cpp > > forever, Here is 'top' > >load averages: 1.17, 1.18, 1.04 >73 processes: 71 idle, 2 on processor >CPU0 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, >100% idle >CPU1 states: 99.6% user, 0.0% nice, 0.4% system, 0.0% interrupt, >0.0% idle >CPU2 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, >100% idle >CPU3 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, >100% idle >CPU4 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, >100% idle >CPU5 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, >100% idle >CPU6 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, >100% idle >CPU7 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, >100% idle >Memory: Real: 1129M/1933M act/tot Free: 5981M Cache: 661M Swap: 0K/0K > > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND >31198 root 640 1077M 1081M onproc- 13:19 99.02% cc1plus > >-- >Jack J. Woehr # Science is more than a body of knowledge. It's a >way of >www.well.com/~jax # thinking, a way of skeptically interrogating the >universe >www.softwoehr.com # with a fine understanding of human fallibility. - >Carl Sagan It's easier to install jdk from packages, than return to build the Netbeans package. Cheers Giovanni -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità .
Re: NetBeans garbage output problem report
Jack J. Woehr wrote: #netbeans_default_options="-J-client -J-Xss2m -J-Xms32m ... --- netbeans_default_options="-J-client -J-Xss8m -J-Xms256m -J-Xmx512m ... This I had to do with both ports. Not sure the -Xss is necessary, but the heap definitely is. If I up -Xmx to 768m or 1g Netbeans crashes with a can't allocate sorta message (on my underloaded 8g machine), specific text on request. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
Jack J. Woehr wrote: Jack J. Woehr wrote: peculiarities in Git behavior. Eh, and doesn't run worth a darn. Bombs with out of memory errors at every turn. Back to the earlier port. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
Stuart Henderson wrote: It takes a while to build, you could just pkg_add it to save time though. Okay, installed JDK8 and made the jasperla-openbsd-wip Netbeans 8.1 port. It works a bit flakier than the earlier Daniel Dickman port I installed, peculiarities in Git behavior. (Team->Show Changes and then Commit only comes up with one file in the changed list. Have to click in the tree view to get the Commit dialog to come up with the whole set of files. Maybe Java 8?) The box-character problem in the output window is still there. Thanks for this team effort. I'm ready to work with you if you're going to proceed on this. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
Jack J. Woehr wrote: peculiarities in Git behavior. BTW, CVS support didn't work in either port. It's there but bombs, "stream closed", hanging, etc. I've been doing checkins manually, but Git support had been working okay and is more or less working now, with some flakiness as noted. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
Jack J. Woehr wrote: Eh, and doesn't run worth a darn. Bombs with out of memory errors at every turn. Back to the earlier port. And the earlier port did the same, until I switched back to JAVA_HOME=/usr/local/jdk-1.7.0 So apparently it's JDK 1.8 that's messing things up. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
Rafael Sadowski wrote: could you or maybe other netbeans user test/run the current state of: https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans I think, I fixed the output problem. I would be happy to read from you. Best regards, Rafael I'm running Daniel Dickman's version of the 8.1 port right now daily, hourly and earnestly. If Daniel approves the state of https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans I will install it and get back to work :) -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Re: NetBeans garbage output problem report
On Sat Nov 14, 2015 at 03:36:36PM -0700, Scott Walters wrote: > Hopefully this is going to the correct place. > http://www.openbsd.org/faq/faq15.html#Problems says to mail the > maintain, and http://openports.se/devel/netbeans gives > http://openports.se/bbmaint.php?maint=ports|a|openbsd.org as the > maintainer. Hi Scott, could you or maybe other netbeans user test/run the current state of: https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans I think, I fixed the output problem. I would be happy to read from you. Best regards, Rafael
Re: NetBeans garbage output problem report
On Sat Nov 14, 2015 at 03:36:36PM -0700, Scott Walters wrote: > Hopefully this is going to the correct place. > http://www.openbsd.org/faq/faq15.html#Problems says to mail the > maintain, and http://openports.se/devel/netbeans gives > http://openports.se/bbmaint.php?maint=ports|a|openbsd.org as the > maintainer. > > The "Output" window in NetBeans shows garbled characters (boxes) when > the green "play arrow"/Run button is pressed. This is reproducible > for me by starting NetBeans, picking "New Project", taking the default > of "Java", naming it "Hello World", then immediately pressing the > green arrow to run the default skeleton project. > NetBeans 8.1 is much better it shows empty output. Only whitespaces or non visible characters :-/ > NetBeans on OpenBSD (5.8, amd64, package current as of the other day) > continues to exhibit this problem first reported in 2008 to the > NetBeans bug tracker: > https://netbeans.org/bugzilla/show_bug.cgi?id=145696 > > No small number of OpenBSD people have chimed in there. > https://netbeans.org/bugzilla/show_bug.cgi?id=224526 seems to be > continuation of that bug. Other platforms are affected by the same > basic failure mode. > > The problem seems to be that NetBeans does not detect the encoding of > output from Maven, nor does it attempt to interrogate Maven's > configuration to learn the encoding it will likely use. For example, > Maven emits UTF-16 and NetBeans interprets it as UTF-8 (or as ASCII, > how the OpenBSD port has its configured). > > scott@fluffy:~$ /usr/local/netbeans/java/maven/bin/mvn --version > Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; > 2013-02-19 06:51:28-0700) > Maven home: /usr/local/netbeans/java/maven > Java version: 1.7.0_80, vendor: Oracle Corporation > Java home: /usr/local/jdk-1.7.0/jre > Default locale: en_US, platform encoding: US-ASCII > OS name: "openbsd", version: "5.8", arch: "amd64", family: "unix" > > I don't know why (stopped investigating at this point), but mvn says > the "Default locale" is "en_US" and platform encoding is "US-ASCII", > but this piece of configuration change (also documented in more detail > on the NetBeans ticket) fixes the garbled output: > > In ~/NetBeansProjects/*/build.xml, at the top level (under ), > where "*" is your project (or repeated for each project), at this: > > > > > org.apache.maven.plugins > maven-resources-plugin > 3.0.5 > > US-ASCII > > > > > > ... needs to match Maven's version. That file is > created for a project after the project is created. Start NetBeans, > create the project, quit, edit the file, restart, then press "play", > and output should be non-garbled (or this worked for me at least). > > I wasn't able to successfully apply this fix to > /usr/local/netbeans/java/maven/conf/settings.xml (perhaps it has a > different structure or needs to be installed somewhere to be used; I > didn't investigate). > > I was able to reproduce this problem in the latest daily developer > release of NetBeans, dated yesterday, in addition to the 6.9.1 in > OpenBSD packages. > > tl;dr It may be possible to fix the garbage from running a project > that shows up in the "Output" window with a config change to Maven or > NetBeans. > Nice hint and thank you, I'll try to apply this advice in netbeans 8.1 port on https://github.com/jasperla/openbsd-wip/tree/master/devel/netbeans Here is 8.1rc2 but I'll commit my finale 8.1 as soon as possible. NetBeans 8.1 comes whiteout netbeans.desktop and a lot of windows/linux/solaris binary crap. Best regards, Rafael
NetBeans garbage output problem report
Hopefully this is going to the correct place. http://www.openbsd.org/faq/faq15.html#Problems says to mail the maintain, and http://openports.se/devel/netbeans gives http://openports.se/bbmaint.php?maint=ports|a|openbsd.org as the maintainer. The "Output" window in NetBeans shows garbled characters (boxes) when the green "play arrow"/Run button is pressed. This is reproducible for me by starting NetBeans, picking "New Project", taking the default of "Java", naming it "Hello World", then immediately pressing the green arrow to run the default skeleton project. NetBeans on OpenBSD (5.8, amd64, package current as of the other day) continues to exhibit this problem first reported in 2008 to the NetBeans bug tracker: https://netbeans.org/bugzilla/show_bug.cgi?id=145696 No small number of OpenBSD people have chimed in there. https://netbeans.org/bugzilla/show_bug.cgi?id=224526 seems to be continuation of that bug. Other platforms are affected by the same basic failure mode. The problem seems to be that NetBeans does not detect the encoding of output from Maven, nor does it attempt to interrogate Maven's configuration to learn the encoding it will likely use. For example, Maven emits UTF-16 and NetBeans interprets it as UTF-8 (or as ASCII, how the OpenBSD port has its configured). scott@fluffy:~$ /usr/local/netbeans/java/maven/bin/mvn --version Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 06:51:28-0700) Maven home: /usr/local/netbeans/java/maven Java version: 1.7.0_80, vendor: Oracle Corporation Java home: /usr/local/jdk-1.7.0/jre Default locale: en_US, platform encoding: US-ASCII OS name: "openbsd", version: "5.8", arch: "amd64", family: "unix" I don't know why (stopped investigating at this point), but mvn says the "Default locale" is "en_US" and platform encoding is "US-ASCII", but this piece of configuration change (also documented in more detail on the NetBeans ticket) fixes the garbled output: In ~/NetBeansProjects/*/build.xml, at the top level (under ), where "*" is your project (or repeated for each project), at this: org.apache.maven.plugins maven-resources-plugin 3.0.5 US-ASCII ... needs to match Maven's version. That file is created for a project after the project is created. Start NetBeans, create the project, quit, edit the file, restart, then press "play", and output should be non-garbled (or this worked for me at least). I wasn't able to successfully apply this fix to /usr/local/netbeans/java/maven/conf/settings.xml (perhaps it has a different structure or needs to be installed somewhere to be used; I didn't investigate). I was able to reproduce this problem in the latest daily developer release of NetBeans, dated yesterday, in addition to the 6.9.1 in OpenBSD packages. tl;dr It may be possible to fix the garbage from running a project that shows up in the "Output" window with a config change to Maven or NetBeans. Thank you everyone for your work. I send this in the hope that it is helpful. -scott P.S.: The NetBeans project manager blocked me when I pressed him for instructions on exactly how to change the config to work around this when I refused to disclose my platform. I am now persona non-gratis there. That happened after he contacted me offering to help resolve my issue. OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP