NetBeans 6.0.1 Patch1 Now Available

[Vaughn]

The NetBeans open source project is proud to announce that NetBeans 6.0.1 Patch1 is now available on the Update Center. The patch includes fixes in modules for Mercurial SCM Plugin, GlassFish Integration, IDE Platform, Java, Java EE, Java Persistence, Java Profiler, JSF, Mobility, Ruby and Rails, Struts, UML, Visual JSF, and Web Applications.

For more information, see http://wiki.netbeans.org/wiki/view/NetBeans6.0PatchesInfo.

The update is easy to install when NetBeans 6.0 is running. Just click on the globe in the status bar or go to Tools -> Plugins -> Updates tab. Then click the "Reload Catalog" button and follow the installation instructions.

[Chuck Davis-3]

WOW!!  That's all I can say about the significant improvement in
responsiveness on my development machine!

Thanks to all the developers who did this trick!

Chuck

On 2/20/08, Vaughn <vaughn.spurlin@...> wrote:

>
> The NetBeans open source project is proud to announce that NetBeans 6.0.1
> Patch1 is now available on the Update Center. The patch includes fixes in
> modules for Mercurial SCM Plugin, GlassFish Integration, IDE Platform, Java,
> Java EE, Java Persistence, Java Profiler, JSF, Mobility, Ruby and Rails,
> Struts, UML, Visual JSF, and Web Applications.
>
> For more information, see
> http://wiki.netbeans.org/wiki/view/NetBeans6.0PatchesInfo.
>
> The update is easy to install when NetBeans 6.0 is running. Just click on
> the globe in the status bar or go to Tools -> Plugins -> Updates tab. Then
> click the "Reload Catalog" button and follow the installation instructions.
> --
> View this message in context:
> http://www.nabble.com/NetBeans-6.0.1-Patch1-Now-Available-tp15596184p15596184.html
> Sent from the Netbeans - J2EE mailing list archive at Nabble.com.
>
>

[avbravo]

Van , i could write in my blog,

http://avbravo.blogspot.com/2008/02/netbeans-601-patch1.html

 

On 2/20/08, Chuck Davis <cjgunzel@...> wrote:

WOW!!  That's all I can say about the significant improvement in
responsiveness on my development machine!

Thanks to all the developers who did this trick!

Chuck

On 2/20/08, Vaughn <vaughn.spurlin@...> wrote:
>
> The NetBeans open source project is proud to announce that NetBeans 6.0.1
> Patch1 is now available on the Update Center. The patch includes fixes in
> modules for Mercurial SCM Plugin, GlassFish Integration, IDE Platform, Java,
> Java EE, Java Persistence, Java Profiler, JSF, Mobility, Ruby and Rails,
> Struts, UML, Visual JSF, and Web Applications.
>
> For more information, see
> http://wiki.netbeans.org/wiki/view/NetBeans6.0PatchesInfo.
>
> The update is easy to install when NetBeans 6.0 is running. Just click on
> the globe in the status bar or go to Tools -> Plugins -> Updates tab. Then
> click the "Reload Catalog" button and follow the installation instructions.
> --
> View this message in context:
> http://www.nabble.com/NetBeans-6.0.1-Patch1-Now-Available-tp15596184p15596184.html
> Sent from the Netbeans - J2EE mailing list archive at Nabble.com.
>
>

--
Member of NetBeans Dream Team
http://www.netbeans.org/community/contribute/dreamteam.html
http://qa.netbeans.org/processes/cat/60/participants.html
http://avbravo.blogspot.com
http://www.panamajug.org
http://translatedfiles.netbeans.org/
http://wiki.netbeans.org/wiki/view/SpanishTranslation

Well strange problem may be it is an ant script thing but I'm not really an
ant expert...

Our project is going well on NB 6.0
But can't  debugged in 6.1 release I just downloaded.

In fact as of my tests, even an out-of-the-box dummy project created via the
"new project" wizard
fails.
(In case you ask : tested on 2 different windows XP stations ; I'm on the
latest jdk and jre (6_06); I tried deleting jdk 6 and getting back to an
1.5's jdk but same trouble.)




only NB 6.0 is Ok for debugging a project.

All Netbeans 6.1 versions claims

    ..
    ..
    All operations completed successfully
    connect-debugger:
    Non-existing path "C:\TestEAR\${javac.classpath}" provided.
    Non-existing path "C:\ TestEAR\${run.classpath}" provided.
    Attached JPDA debugger to localhost:9009
    debug-display-browser:
    ..
    ..
    ... [show rest of quote]

Please
Can someone please kind enough to give it a check and tell me if for him it
is working ?, or even if you are not working with ear projects
(JEE5+EJB3+VWP)

it really simple and quick just to confirm me if it is a bug to be listed or
if I'm loosing something or if it is just some changes to make to the build
files (which will be clearly called "a bug" anyway)
?


It's only 5 mn straight :
-take the new project wizard
- say you want an enterprise app;
- create a persistent unit
-add an entity (don't matter what) on the ejb side
-add an Visual Web JSF page on the war side

and it's done.

Add a breakpoint in the code (or on a method) of the web page:
breakpoint in the code : you won't get nothing at all;
breakpoint on a method you will be stopped on the method entrance but can't
go step by step etc...



Please I'm really in a mess.
 I don't know where to look at ? I tried to change the ant build but didn't
succeeded (again I'm not an ant expert)
I can't go on, on my project if I can't debug it !
 and NB6.0 is far too slow dealing with the VWP(Visual Web Pack)

Any help or hint
or at least just telling me what is your platform, if it works  with you,
will be appreciated.

Sincerely,

[Arne Knorr]

Im using NB6.1 and your example works fine for me. I can debug that web page.

Regards
Arne

On Tue, Apr 29, 2008 at 5:50 PM, Henoc <henoc@...> wrote:

Well strange problem may be it is an ant script thing but I'm not really an
ant expert...

Our project is going well on NB 6.0
But can't  debugged in 6.1 release I just downloaded.

In fact as of my tests, even an out-of-the-box dummy project created via the
"new project" wizard
fails.
(In case you ask : tested on 2 different windows XP stations ; I'm on the
latest jdk and jre (6_06); I tried deleting jdk 6 and getting back to an
1.5's jdk but same trouble.)




only NB 6.0 is Ok for debugging a project.

All Netbeans 6.1 versions claims

   ..
   ..
   All operations completed successfully
   connect-debugger:
   Non-existing path "C:\TestEAR\${javac.classpath}" provided.
   Non-existing path "C:\ TestEAR\${run.classpath}" provided.
   Attached JPDA debugger to localhost:9009
   debug-display-browser:
   ..
   ..
   ... [show rest of quote]

Please
Can someone please kind enough to give it a check and tell me if for him it
is working ?, or even if you are not working with ear projects
(JEE5+EJB3+VWP)

it really simple and quick just to confirm me if it is a bug to be listed or
if I'm loosing something or if it is just some changes to make to the build
files (which will be clearly called "a bug" anyway)
?


It's only 5 mn straight :
-take the new project wizard
- say you want an enterprise app;
- create a persistent unit
-add an entity (don't matter what) on the ejb side
-add an Visual Web JSF page on the war side

and it's done.

Add a breakpoint in the code (or on a method) of the web page:
breakpoint in the code : you won't get nothing at all;
breakpoint on a method you will be stopped on the method entrance but can't
go step by step etc...



Please I'm really in a mess.
 I don't know where to look at ? I tried to change the ant build but didn't
succeeded (again I'm not an ant expert)
I can't go on, on my project if I can't debug it !
 and NB6.0 is far too slow dealing with the VWP(Visual Web Pack)

Any help or hint
or at least just telling me what is your platform, if it works  with you,
will be appreciated.

Sincerely,

[vince kraemer]

I think I have been able to reproduce the issue.  I filed
http://www.netbeans.org/issues/show_bug.cgi?id=134276

I have included a possible work-around at the bottom of the description.

vbk

Henoc wrote:

> Well strange problem may be it is an ant script thing but I'm not really an
> ant expert...
>
> Our project is going well on NB 6.0
> But can't  debugged in 6.1 release I just downloaded.
>
> In fact as of my tests, even an out-of-the-box dummy project created via the
> "new project" wizard
> fails.
> (In case you ask : tested on 2 different windows XP stations ; I'm on the
> latest jdk and jre (6_06); I tried deleting jdk 6 and getting back to an
> 1.5's jdk but same trouble.)
>
>
>
>
> only NB 6.0 is Ok for debugging a project.
>
> All Netbeans 6.1 versions claims
>
>     ..
>     ..
>     All operations completed successfully
>     connect-debugger:
>     Non-existing path "C:\TestEAR\${javac.classpath}" provided.
>     Non-existing path "C:\ TestEAR\${run.classpath}" provided.
>     Attached JPDA debugger to localhost:9009
>     debug-display-browser:
>     ..
>     ..
>     ... [show rest of quote]
>
> Please
> Can someone please kind enough to give it a check and tell me if for him it
> is working ?, or even if you are not working with ear projects
> (JEE5+EJB3+VWP)
>
> it really simple and quick just to confirm me if it is a bug to be listed or
> if I'm loosing something or if it is just some changes to make to the build
> files (which will be clearly called "a bug" anyway)
> ?
>
>
> It's only 5 mn straight :
> -take the new project wizard
> - say you want an enterprise app;
> - create a persistent unit
> -add an entity (don't matter what) on the ejb side
> -add an Visual Web JSF page on the war side
>
> and it's done.
>
> Add a breakpoint in the code (or on a method) of the web page:
> breakpoint in the code : you won't get nothing at all;
> breakpoint on a method you will be stopped on the method entrance but can't
> go step by step etc...
>
>
>
> Please I'm really in a mess.
>  I don't know where to look at ? I tried to change the ant build but didn't
> succeeded (again I'm not an ant expert)
> I can't go on, on my project if I can't debug it !
>  and NB6.0 is far too slow dealing with the VWP(Visual Web Pack)
>
> Any help or hint
> or at least just telling me what is your platform, if it works  with you,
> will be appreciated.
>
> Sincerely,
>
>  

Thanks for the time you take to help but
(excuse my ignorance )  how is explained that just 2 people reproduce
this ?  I don't have to make extra steps like you to reproduce it;
it is simply direct on my computer just ask a new project and add a
persistent.xml; an entity and a web page.
It's all you need to fail !

If one got an explanation it will be cool

But first of all thanks Vince !!  Your workaround work fine !
Really , your help is so much appreciated ; I was in a clear dead-end

Cheers




Vince Kraemer a écrit :
> I think I have been able to reproduce the issue.  I filed
> http://www.netbeans.org/issues/show_bug.cgi?id=134276
>
> I have included a possible work-around at the bottom of the description.
> vbk
>