My standard procedure is to go into .netbeans and rename the directory for
my current version (I've been using the dev build, so it is called dev) so
that I have a backup and can revert.
I have found always starting with a clean directory is .netbeans is key.
On Mon, Dec 1, 2008 at 8:09 PM, David
I'd suggest removing the ~/.netbeans directory (and anything that looks like
it).
On Mon, Dec 1, 2008 at 5:00 PM, Charles F. Munat <[EMAIL PROTECTED]> wrote:
>
> I thought I had updated to that, but maybe I broke it before the
> update... Will install all the latest this time and will see what
>
I thought I had updated to that, but maybe I broke it before the
update... Will install all the latest this time and will see what
happens. But I had the same experience a couple of months ago when I
tried it for the first time. I'd really like it to work, though. That
would be great, and it w
There was a defect in the plugin. Cauyuon posted a fix to this list last
week.
On Mon, Dec 1, 2008 at 3:07 PM, Charles F. Munat <[EMAIL PROTECTED]> wrote:
>
> I've tried twice to get NetBeans up and running on my MacBook Pro with 2
> gigs of RAM. Both times I made the mistake of loading in the e
Cool. I hope I get time to read this really soon.
Thanks!
Chas.
Derek Chen-Becker wrote:
> I've done it in Eclipse and I'm assuming it would be similarly easy in
> NetBeans. There's a good article on setting up Maven remote debugging
> with Jetty here:
>
> http://www.mojavelinux.com/blog/arc
I've tried twice to get NetBeans up and running on my MacBook Pro with 2
gigs of RAM. Both times I made the mistake of loading in the entire
liftweb library. After that -- and even after I closed the liftweb
master project -- NetBeans will lock up for long periods of time (e.g.
ten minutes or
I've done it in Eclipse and I'm assuming it would be similarly easy in
NetBeans. There's a good article on setting up Maven remote debugging with
Jetty here:
http://www.mojavelinux.com/blog/archives/2007/03/remote_debugging_with_jetty/
Derek
On Mon, Dec 1, 2008 at 2:43 PM, David Pollak
<[EMAIL P
Charles,
I use NetBeans and a whole lot of printlns. In general, if you've got a
case class or Scala collections, the toString methods are pretty descriptive
of what's going on.
I have heard tell that it's possible to hook the NetBeans debugger up to a
running Jetty instance and do breakpoints i
