[editor] Any more error badges problems?

[jiri prox]

Hello NetCATers,

  couple of weeks ago you pointed out that new error badges
functionality is not fully reliable. We worked hard to fix all reported
problems [1] but some issues require more complex fixes that could
potentially destabilize 6.0 codebase.

[1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950

  We believe though that these issues have only a minor impact on users.
They are maily connected with changes in project configuration since
NetBeans 5.*:

1) IDE is more sensitive if classes reside in files which do not match
the class names and packages
  - this is a valid bug, but the workaround is easy: just folow the name
conventions

2) source parser ignores project output jar even if it's explicitly
added to project classpath
  - this concers freeform projects and the reasons are described in
issue #116208

3) cyclic dependency
  - IDE doesn't handle cyclic dependency between projects very well

4) error badges are new in 6.0, so any project configuration problems
are more visible now

  Now we would like to know if _YOU_ still face some problems with
incorrect error badges. If _YOU_ do (reported or not), please file an
issue [2] with as much information as you can [3]. Even the minor
configuration detail can be important!

[2]
http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcomponent=source&version=6.0

[3]
* Exact description of wrong behavior
* Project type
* Project configuration - source roots, dependency between projects,
library configuration etc.
* Sample project would be welcome
* Try to clean caches and check whether it helped or not
* Use _RC1 exclusively_ with empty userdir


Thanks for your help, it is highly appreciated!
Jirka Prox

[Jiri Kovalsky]

Wow, 6 hours and no response? That's a very good sign, Jiri!
I for one am gonna sleep tight tonight. :-)

Thank you team,
-Jirka

Jiri Prox wrote:

> Hello NetCATers,
>
>  couple of weeks ago you pointed out that new error badges functionality
> is not fully reliable. We worked hard to fix all reported problems [1]
> but some issues require more complex fixes that could potentially
> destabilize 6.0 codebase.
>
> [1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
>
>  We believe though that these issues have only a minor impact on users.
> They are maily connected with changes in project configuration since
> NetBeans 5.*:
>
> 1) IDE is more sensitive if classes reside in files which do not match
> the class names and packages
>  - this is a valid bug, but the workaround is easy: just folow the name
> conventions
>
> 2) source parser ignores project output jar even if it's explicitly
> added to project classpath
>  - this concers freeform projects and the reasons are described in issue
> #116208
>
> 3) cyclic dependency
>  - IDE doesn't handle cyclic dependency between projects very well
>
> 4) error badges are new in 6.0, so any project configuration problems
> are more visible now
>
>  Now we would like to know if _YOU_ still face some problems with
> incorrect error badges. If _YOU_ do (reported or not), please file an
> issue [2] with as much information as you can [3]. Even the minor
> configuration detail can be important!
>
> [2]
> http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcomponent=source&version=6.0 
>
> [3]
> * Exact description of wrong behavior
> * Project type
> * Project configuration - source roots, dependency between projects,
> library configuration etc.
> * Sample project would be welcome
> * Try to clean caches and check whether it helped or not
> * Use _RC1 exclusively_ with empty userdir
>
> Thanks for your help, it is highly appreciated!
> Jirka Prox

[Bryan Boone]

Not so fast... I'm just waking up;)

-----Original Message-----
From: Jiri.Kovalsky@... [mailto:Jiri.Kovalsky@...]
Sent: Thursday, November 15, 2007 10:31 AM
To: netcat@...
Subject: Re: [60cat] [editor] Any more error badges problems?

Wow, 6 hours and no response? That's a very good sign, Jiri!
I for one am gonna sleep tight tonight. :-)

Thank you team,
-Jirka

Jiri Prox wrote:

> Hello NetCATers,
>
>  couple of weeks ago you pointed out that new error badges
> functionality is not fully reliable. We worked hard to fix all
> reported problems [1] but some issues require more complex fixes that
> could potentially destabilize 6.0 codebase.
>
> [1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
>
>  We believe though that these issues have only a minor impact on users.
> They are maily connected with changes in project configuration since
> NetBeans 5.*:
>
> 1) IDE is more sensitive if classes reside in files which do not match
> the class names and packages
>  - this is a valid bug, but the workaround is easy: just folow the
> name conventions
>
> 2) source parser ignores project output jar even if it's explicitly
> added to project classpath
>  - this concers freeform projects and the reasons are described in
> issue
> #116208
>
> 3) cyclic dependency
>  - IDE doesn't handle cyclic dependency between projects very well
>
> 4) error badges are new in 6.0, so any project configuration problems
> are more visible now
>
>  Now we would like to know if _YOU_ still face some problems with
> incorrect error badges. If _YOU_ do (reported or not), please file an
> issue [2] with as much information as you can [3]. Even the minor
> configuration detail can be important!
>
> [2]
> http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcompone
> nt=source&version=6.0
>
> [3]
> * Exact description of wrong behavior
> * Project type
> * Project configuration - source roots, dependency between projects,
> library configuration etc.
> * Sample project would be welcome
> * Try to clean caches and check whether it helped or not
> * Use _RC1 exclusively_ with empty userdir
>
> Thanks for your help, it is highly appreciated!
> Jirka Prox

[Holger Stenzhorn]

Jiri,

I thought you meant "any more NEW" problems, right?
...because "my" error badge problem is still there in the "final" RC1
and the issue posted by me is still open (as you know).

Cheers,
Holger

Jiri Kovalsky wrote:

> Wow, 6 hours and no response? That's a very good sign, Jiri!
> I for one am gonna sleep tight tonight. :-)
>
> Thank you team,
> -Jirka
>
> Jiri Prox wrote:
>
>> Hello NetCATers,
>>
>>  couple of weeks ago you pointed out that new error badges
>> functionality is not fully reliable. We worked hard to fix all
>> reported problems [1] but some issues require more complex fixes that
>> could potentially destabilize 6.0 codebase.
>>
>> [1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
>>
>>  We believe though that these issues have only a minor impact on
>> users. They are maily connected with changes in project configuration
>> since NetBeans 5.*:
>>
>> 1) IDE is more sensitive if classes reside in files which do not
>> match the class names and packages
>>  - this is a valid bug, but the workaround is easy: just folow the
>> name conventions
>>
>> 2) source parser ignores project output jar even if it's explicitly
>> added to project classpath
>>  - this concers freeform projects and the reasons are described in
>> issue #116208
>>
>> 3) cyclic dependency
>>  - IDE doesn't handle cyclic dependency between projects very well
>>
>> 4) error badges are new in 6.0, so any project configuration problems
>> are more visible now
>>
>>  Now we would like to know if _YOU_ still face some problems with
>> incorrect error badges. If _YOU_ do (reported or not), please file an
>> issue [2] with as much information as you can [3]. Even the minor
>> configuration detail can be important!
>>
>> [2]
>> http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcomponent=source&version=6.0 
>>
>> [3]
>> * Exact description of wrong behavior
>> * Project type
>> * Project configuration - source roots, dependency between projects,
>> library configuration etc.
>> * Sample project would be welcome
>> * Try to clean caches and check whether it helped or not
>> * Use _RC1 exclusively_ with empty userdir
>>
>> Thanks for your help, it is highly appreciated!
>> Jirka Prox

[tetsu.soh]

Hi,
I don't know whether this one is new or not. Please check it out.

Steps to reproduce:
1. Create a CDC application project, let's say, name is AAA.
The nb will also create a default main class in a default package.
2. Delete the project clearly.
(btw, you cannot delete the project clearly from Project viewer. After
delete, the project folder is left. So you have to delete that in your OS
file manager.
Is it a another bug?)
3. Re-create the new CDC application project with the same name, AAA.
4. Again, the nb will create the default main class but failed to insert
the default package.

The result is that I get a error badge in Java editor, but no error badge
in Project viewer.

Regards,
Tetsu


Bryan Boone <Bryan.Boone@...> wrote on 2007/11/16 00:33:20:

> Not so fast... I'm just waking up;)

> -----Original Message-----
> From: Jiri.Kovalsky@... [mailto:Jiri.Kovalsky@...]
> Sent: Thursday, November 15, 2007 10:31 AM
> To: netcat@...
> Subject: Re: [60cat] [editor] Any more error badges problems?

> Wow, 6 hours and no response? That's a very good sign, Jiri!
> I for one am gonna sleep tight tonight. :-)

> Thank you team,
> -Jirka

> Jiri Prox wrote:

> > Hello NetCATers,
> >
> >  couple of weeks ago you pointed out that new error badges
> > functionality is not fully reliable. We worked hard to fix all
> > reported problems [1] but some issues require more complex fixes that
> > could potentially destabilize 6.0 codebase.
> >
> > [1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
> >
> >  We believe though that these issues have only a minor impact on users.
> > They are maily connected with changes in project configuration since
> > NetBeans 5.*:
> >
> > 1) IDE is more sensitive if classes reside in files which do not match
> > the class names and packages
> >  - this is a valid bug, but the workaround is easy: just folow the
> > name conventions
> >
> > 2) source parser ignores project output jar even if it's explicitly
> > added to project classpath
> >  - this concers freeform projects and the reasons are described in
> > issue
> > #116208
> >
> > 3) cyclic dependency
> >  - IDE doesn't handle cyclic dependency between projects very well
> >
> > 4) error badges are new in 6.0, so any project configuration problems
> > are more visible now
> >
> >  Now we would like to know if _YOU_ still face some problems with
> > incorrect error badges. If _YOU_ do (reported or not), please file an
> > issue [2] with as much information as you can [3]. Even the minor
> > configuration detail can be important!
> >
> > [2]
> > http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcompone
> > nt=source&version=6.0
> >
> > [3]
> > * Exact description of wrong behavior
> > * Project type
> > * Project configuration - source roots, dependency between projects,
> > library configuration etc.
> > * Sample project would be welcome
> > * Try to clean caches and check whether it helped or not
> > * Use _RC1 exclusively_ with empty userdir
> >
> > Thanks for your help, it is highly appreciated!
> > Jirka Prox

[jiri prox]

Hi Tetsu,

is the source broken after step 4? If the source is correct, and only
package statement does not match the file location you're maybe facing
'Wrong package' hint, which is by default set to displayed as error.

Regards
Jirka

tetsu.soh@... wrote:

>Hi,
>I don't know whether this one is new or not. Please check it out.
>
>Steps to reproduce:
>1. Create a CDC application project, let's say, name is AAA.
>The nb will also create a default main class in a default package.
>2. Delete the project clearly.
>(btw, you cannot delete the project clearly from Project viewer. After
>delete, the project folder is left. So you have to delete that in your OS
>file manager.
>Is it a another bug?)
>3. Re-create the new CDC application project with the same name, AAA.
>4. Again, the nb will create the default main class but failed to insert
>the default package.
>
>The result is that I get a error badge in Java editor, but no error badge
>in Project viewer.
>
>Regards,
>Tetsu
>
>
>Bryan Boone <Bryan.Boone@...> wrote on 2007/11/16 00:33:20:
>
>  
>
>>Not so fast... I'm just waking up;)
>>    
>>
>
>  
>
>>-----Original Message-----
>>From: Jiri.Kovalsky@... [mailto:Jiri.Kovalsky@...]
>>Sent: Thursday, November 15, 2007 10:31 AM
>>To: netcat@...
>>Subject: Re: [60cat] [editor] Any more error badges problems?
>>    
>>
>
>  
>
>>Wow, 6 hours and no response? That's a very good sign, Jiri!
>>I for one am gonna sleep tight tonight. :-)
>>    
>>
>
>  
>
>>Thank you team,
>>-Jirka
>>    
>>
>
>  
>
>>Jiri Prox wrote:
>>    
>>
>
>  
>
>>>Hello NetCATers,
>>>
>>> couple of weeks ago you pointed out that new error badges
>>>functionality is not fully reliable. We worked hard to fix all
>>>reported problems [1] but some issues require more complex fixes that
>>>could potentially destabilize 6.0 codebase.
>>>
>>>[1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
>>>
>>> We believe though that these issues have only a minor impact on users.
>>>They are maily connected with changes in project configuration since
>>>NetBeans 5.*:
>>>
>>>1) IDE is more sensitive if classes reside in files which do not match
>>>the class names and packages
>>> - this is a valid bug, but the workaround is easy: just folow the
>>>name conventions
>>>
>>>2) source parser ignores project output jar even if it's explicitly
>>>added to project classpath
>>> - this concers freeform projects and the reasons are described in
>>>issue
>>>#116208
>>>
>>>3) cyclic dependency
>>> - IDE doesn't handle cyclic dependency between projects very well
>>>
>>>4) error badges are new in 6.0, so any project configuration problems
>>>are more visible now
>>>
>>> Now we would like to know if _YOU_ still face some problems with
>>>incorrect error badges. If _YOU_ do (reported or not), please file an
>>>issue [2] with as much information as you can [3]. Even the minor
>>>configuration detail can be important!
>>>
>>>[2]
>>>http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcompone
>>>nt=source&version=6.0
>>>
>>>[3]
>>>* Exact description of wrong behavior
>>>* Project type
>>>* Project configuration - source roots, dependency between projects,
>>>library configuration etc.
>>>* Sample project would be welcome
>>>* Try to clean caches and check whether it helped or not
>>>* Use _RC1 exclusively_ with empty userdir
>>>
>>>Thanks for your help, it is highly appreciated!
>>>Jirka Prox
>>>      
>>>

[jiri prox]

Hi Tetsu,

is the source broken? If the source code is ok and only package does not
match the current location of the file, you're probably facing 'wrong
package' hint, which is by default set to be shown as error.

Regards
Jirka


tetsu.soh@... wrote:

>Hi,
>I don't know whether this one is new or not. Please check it out.
>
>Steps to reproduce:
>1. Create a CDC application project, let's say, name is AAA.
>The nb will also create a default main class in a default package.
>2. Delete the project clearly.
>(btw, you cannot delete the project clearly from Project viewer. After
>delete, the project folder is left. So you have to delete that in your OS
>file manager.
>Is it a another bug?)
>3. Re-create the new CDC application project with the same name, AAA.
>4. Again, the nb will create the default main class but failed to insert
>the default package.
>
>The result is that I get a error badge in Java editor, but no error badge
>in Project viewer.
>
>Regards,
>Tetsu
>
>
>Bryan Boone <Bryan.Boone@...> wrote on 2007/11/16 00:33:20:
>
>  
>
>>Not so fast... I'm just waking up;)
>>    
>>
>
>  
>
>>-----Original Message-----
>>From: Jiri.Kovalsky@... [mailto:Jiri.Kovalsky@...]
>>Sent: Thursday, November 15, 2007 10:31 AM
>>To: netcat@...
>>Subject: Re: [60cat] [editor] Any more error badges problems?
>>    
>>
>
>  
>
>>Wow, 6 hours and no response? That's a very good sign, Jiri!
>>I for one am gonna sleep tight tonight. :-)
>>    
>>
>
>  
>
>>Thank you team,
>>-Jirka
>>    
>>
>
>  
>
>>Jiri Prox wrote:
>>    
>>
>
>  
>
>>>Hello NetCATers,
>>>
>>> couple of weeks ago you pointed out that new error badges
>>>functionality is not fully reliable. We worked hard to fix all
>>>reported problems [1] but some issues require more complex fixes that
>>>could potentially destabilize 6.0 codebase.
>>>
>>>[1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
>>>
>>> We believe though that these issues have only a minor impact on users.
>>>They are maily connected with changes in project configuration since
>>>NetBeans 5.*:
>>>
>>>1) IDE is more sensitive if classes reside in files which do not match
>>>the class names and packages
>>> - this is a valid bug, but the workaround is easy: just folow the
>>>name conventions
>>>
>>>2) source parser ignores project output jar even if it's explicitly
>>>added to project classpath
>>> - this concers freeform projects and the reasons are described in
>>>issue
>>>#116208
>>>
>>>3) cyclic dependency
>>> - IDE doesn't handle cyclic dependency between projects very well
>>>
>>>4) error badges are new in 6.0, so any project configuration problems
>>>are more visible now
>>>
>>> Now we would like to know if _YOU_ still face some problems with
>>>incorrect error badges. If _YOU_ do (reported or not), please file an
>>>issue [2] with as much information as you can [3]. Even the minor
>>>configuration detail can be important!
>>>
>>>[2]
>>>http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcompone
>>>nt=source&version=6.0
>>>
>>>[3]
>>>* Exact description of wrong behavior
>>>* Project type
>>>* Project configuration - source roots, dependency between projects,
>>>library configuration etc.
>>>* Sample project would be welcome
>>>* Try to clean caches and check whether it helped or not
>>>* Use _RC1 exclusively_ with empty userdir
>>>
>>>Thanks for your help, it is highly appreciated!
>>>Jirka Prox
>>>      
>>>

[tetsu.soh]

Hi Jirka,
Yes, just as you said.

However, IMO, wrong package statement is an error, isn't it?
And this error is only show on editor. Not on Project viewer.

Regards,
Tetsu

Jiri.Prox@... wrote on 2007/11/20 18:20:08:

> Hi Tetsu,

> is the source broken? If the source code is ok and only package does not
> match the current location of the file, you're probably facing 'wrong
> package' hint, which is by default set to be shown as error.

> Regards
> Jirka

>
> tetsu.soh@... wrote:

> >Hi,
> >I don't know whether this one is new or not. Please check it out.
> >
> >Steps to reproduce:
> >1. Create a CDC application project, let's say, name is AAA.
> >The nb will also create a default main class in a default package.
> >2. Delete the project clearly.
> >(btw, you cannot delete the project clearly from Project viewer. After
> >delete, the project folder is left. So you have to delete that in your
OS
> >file manager.
> >Is it a another bug?)
> >3. Re-create the new CDC application project with the same name, AAA.
> >4. Again, the nb will create the default main class but failed to insert
> >the default package.
> >
> >The result is that I get a error badge in Java editor, but no error
badge

> >in Project viewer.
> >
> >Regards,
> >Tetsu
> >
> >
> >Bryan Boone <Bryan.Boone@...> wrote on 2007/11/16 00:33:20:
> >
> >
> >
> >>Not so fast... I'm just waking up;)
> >>
> >>
> >
> >
> >
> >>-----Original Message-----
> >>From: Jiri.Kovalsky@... [mailto:Jiri.Kovalsky@...]
> >>Sent: Thursday, November 15, 2007 10:31 AM
> >>To: netcat@...
> >>Subject: Re: [60cat] [editor] Any more error badges problems?
> >>
> >>
> >
> >
> >
> >>Wow, 6 hours and no response? That's a very good sign, Jiri!
> >>I for one am gonna sleep tight tonight. :-)
> >>
> >>
> >
> >
> >
> >>Thank you team,
> >>-Jirka
> >>
> >>
> >
> >
> >
> >>Jiri Prox wrote:
> >>
> >>
> >
> >
> >
> >>>Hello NetCATers,
> >>>
> >>> couple of weeks ago you pointed out that new error badges
> >>>functionality is not fully reliable. We worked hard to fix all
> >>>reported problems [1] but some issues require more complex fixes that
> >>>could potentially destabilize 6.0 codebase.
> >>>
> >>>[1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
> >>>
> >>> We believe though that these issues have only a minor impact on

users.

> >>>They are maily connected with changes in project configuration since
> >>>NetBeans 5.*:
> >>>
> >>>1) IDE is more sensitive if classes reside in files which do not match
> >>>the class names and packages
> >>> - this is a valid bug, but the workaround is easy: just folow the
> >>>name conventions
> >>>
> >>>2) source parser ignores project output jar even if it's explicitly
> >>>added to project classpath
> >>> - this concers freeform projects and the reasons are described in
> >>>issue
> >>>#116208
> >>>
> >>>3) cyclic dependency
> >>> - IDE doesn't handle cyclic dependency between projects very well
> >>>
> >>>4) error badges are new in 6.0, so any project configuration problems
> >>>are more visible now
> >>>
> >>> Now we would like to know if _YOU_ still face some problems with
> >>>incorrect error badges. If _YOU_ do (reported or not), please file an
> >>>issue [2] with as much information as you can [3]. Even the minor
> >>>configuration detail can be important!
> >>>
> >>>[2]
> >>>http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcompone
> >>>nt=source&version=6.0
> >>>
> >>>[3]
> >>>* Exact description of wrong behavior
> >>>* Project type
> >>>* Project configuration - source roots, dependency between projects,
> >>>library configuration etc.
> >>>* Sample project would be welcome
> >>>* Try to clean caches and check whether it helped or not
> >>>* Use _RC1 exclusively_ with empty userdir
> >>>
> >>>Thanks for your help, it is highly appreciated!
> >>>Jirka Prox
> >>>
> >>>

[jiri prox]

Hi,

yes, hints are not yet integrated with tasklist/error badges. It is
planned for next release.
The wrong package statement (when package does not match the directory
structure)
is not an error, it's valid java code, but it highly recommended not to
use it. That's why
 this hint is by default enabled and shown as an error.

Thanks for evaluation
Jirka


tetsu.soh@... wrote:

>Hi Jirka,
>Yes, just as you said.
>
>However, IMO, wrong package statement is an error, isn't it?
>And this error is only show on editor. Not on Project viewer.
>
>Regards,
>Tetsu
>
>Jiri.Prox@... wrote on 2007/11/20 18:20:08:
>
>  
>
>>Hi Tetsu,
>>    
>>
>
>  
>
>>is the source broken? If the source code is ok and only package does not
>>match the current location of the file, you're probably facing 'wrong
>>package' hint, which is by default set to be shown as error.
>>    
>>
>
>  
>
>>Regards
>>Jirka
>>    
>>
>
>  
>
>>tetsu.soh@... wrote:
>>    
>>
>
>  
>
>>>Hi,
>>>I don't know whether this one is new or not. Please check it out.
>>>
>>>Steps to reproduce:
>>>1. Create a CDC application project, let's say, name is AAA.
>>>The nb will also create a default main class in a default package.
>>>2. Delete the project clearly.
>>>(btw, you cannot delete the project clearly from Project viewer. After
>>>delete, the project folder is left. So you have to delete that in your
>>>      
>>>
>OS
>  
>
>>>file manager.
>>>Is it a another bug?)
>>>3. Re-create the new CDC application project with the same name, AAA.
>>>4. Again, the nb will create the default main class but failed to insert
>>>the default package.
>>>
>>>The result is that I get a error badge in Java editor, but no error
>>>      
>>>
>badge
>  
>
>>>in Project viewer.
>>>
>>>Regards,
>>>Tetsu
>>>
>>>
>>>Bryan Boone <Bryan.Boone@...> wrote on 2007/11/16 00:33:20:
>>>
>>>
>>>
>>>      
>>>
>>>>Not so fast... I'm just waking up;)
>>>>
>>>>
>>>>        
>>>>
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: Jiri.Kovalsky@... [mailto:Jiri.Kovalsky@...]
>>>>Sent: Thursday, November 15, 2007 10:31 AM
>>>>To: netcat@...
>>>>Subject: Re: [60cat] [editor] Any more error badges problems?
>>>>
>>>>
>>>>        
>>>>
>>>
>>>      
>>>
>>>>Wow, 6 hours and no response? That's a very good sign, Jiri!
>>>>I for one am gonna sleep tight tonight. :-)
>>>>
>>>>
>>>>        
>>>>
>>>
>>>      
>>>
>>>>Thank you team,
>>>>-Jirka
>>>>
>>>>
>>>>        
>>>>
>>>
>>>      
>>>
>>>>Jiri Prox wrote:
>>>>
>>>>
>>>>        
>>>>
>>>
>>>      
>>>
>>>>>Hello NetCATers,
>>>>>
>>>>>couple of weeks ago you pointed out that new error badges
>>>>>functionality is not fully reliable. We worked hard to fix all
>>>>>reported problems [1] but some issues require more complex fixes that
>>>>>could potentially destabilize 6.0 codebase.
>>>>>
>>>>>[1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
>>>>>
>>>>>We believe though that these issues have only a minor impact on
>>>>>          
>>>>>
>users.
>  
>
>>>>>They are maily connected with changes in project configuration since
>>>>>NetBeans 5.*:
>>>>>
>>>>>1) IDE is more sensitive if classes reside in files which do not match
>>>>>the class names and packages
>>>>>- this is a valid bug, but the workaround is easy: just folow the
>>>>>name conventions
>>>>>
>>>>>2) source parser ignores project output jar even if it's explicitly
>>>>>added to project classpath
>>>>>- this concers freeform projects and the reasons are described in
>>>>>issue
>>>>>#116208
>>>>>
>>>>>3) cyclic dependency
>>>>>- IDE doesn't handle cyclic dependency between projects very well
>>>>>
>>>>>4) error badges are new in 6.0, so any project configuration problems
>>>>>are more visible now
>>>>>
>>>>>Now we would like to know if _YOU_ still face some problems with
>>>>>incorrect error badges. If _YOU_ do (reported or not), please file an
>>>>>issue [2] with as much information as you can [3]. Even the minor
>>>>>configuration detail can be important!
>>>>>
>>>>>[2]
>>>>>http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcompone
>>>>>nt=source&version=6.0
>>>>>
>>>>>[3]
>>>>>* Exact description of wrong behavior
>>>>>* Project type
>>>>>* Project configuration - source roots, dependency between projects,
>>>>>library configuration etc.
>>>>>* Sample project would be welcome
>>>>>* Try to clean caches and check whether it helped or not
>>>>>* Use _RC1 exclusively_ with empty userdir
>>>>>
>>>>>Thanks for your help, it is highly appreciated!
>>>>>Jirka Prox
>>>>>
>>>>>
>>>>>          
>>>>>

[tetsu.soh]

oh, I got it.

Thanks for the information.

Tetsu.

Jiri.Prox@... wrote on 2007/11/20 19:31:08:

> Hi,

> yes, hints are not yet integrated with tasklist/error badges. It is
> planned for next release.
> The wrong package statement (when package does not match the directory
> structure)
> is not an error, it's valid java code, but it highly recommended not to
> use it. That's why
> this hint is by default enabled and shown as an error.

> Thanks for evaluation
> Jirka

>
> tetsu.soh@... wrote:

> >Hi Jirka,
> >Yes, just as you said.
> >
> >However, IMO, wrong package statement is an error, isn't it?
> >And this error is only show on editor. Not on Project viewer.
> >
> >Regards,
> >Tetsu
> >
> >Jiri.Prox@... wrote on 2007/11/20 18:20:08:
> >
> >
> >
> >>Hi Tetsu,
> >>
> >>
> >
> >
> >
> >>is the source broken? If the source code is ok and only package does

not

> >>match the current location of the file, you're probably facing 'wrong
> >>package' hint, which is by default set to be shown as error.
> >>
> >>
> >
> >
> >
> >>Regards
> >>Jirka
> >>
> >>
> >
> >
> >
> >>tetsu.soh@... wrote:
> >>
> >>
> >
> >
> >
> >>>Hi,
> >>>I don't know whether this one is new or not. Please check it out.
> >>>
> >>>Steps to reproduce:
> >>>1. Create a CDC application project, let's say, name is AAA.
> >>>The nb will also create a default main class in a default package.
> >>>2. Delete the project clearly.
> >>>(btw, you cannot delete the project clearly from Project viewer. After
> >>>delete, the project folder is left. So you have to delete that in your
> >>>
> >>>
> >OS
> >
> >
> >>>file manager.
> >>>Is it a another bug?)
> >>>3. Re-create the new CDC application project with the same name, AAA.
> >>>4. Again, the nb will create the default main class but failed to

insert

> >>>the default package.
> >>>
> >>>The result is that I get a error badge in Java editor, but no error
> >>>
> >>>
> >badge
> >
> >
> >>>in Project viewer.
> >>>
> >>>Regards,
> >>>Tetsu
> >>>
> >>>
> >>>Bryan Boone <Bryan.Boone@...> wrote on 2007/11/16 00:33:20:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>Not so fast... I'm just waking up;)
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Jiri.Kovalsky@... [mailto:Jiri.Kovalsky@...]
> >>>>Sent: Thursday, November 15, 2007 10:31 AM
> >>>>To: netcat@...
> >>>>Subject: Re: [60cat] [editor] Any more error badges problems?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>>Wow, 6 hours and no response? That's a very good sign, Jiri!
> >>>>I for one am gonna sleep tight tonight. :-)
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>>Thank you team,
> >>>>-Jirka
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>>Jiri Prox wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>>>Hello NetCATers,
> >>>>>
> >>>>>couple of weeks ago you pointed out that new error badges
> >>>>>functionality is not fully reliable. We worked hard to fix all
> >>>>>reported problems [1] but some issues require more complex fixes

that

> >>>>>could potentially destabilize 6.0 codebase.
> >>>>>
> >>>>>[1] http://www.netbeans.org/issues/showdependencytree.cgi?id=121950
> >>>>>
> >>>>>We believe though that these issues have only a minor impact on
> >>>>>
> >>>>>
> >users.
> >
> >
> >>>>>They are maily connected with changes in project configuration since
> >>>>>NetBeans 5.*:
> >>>>>
> >>>>>1) IDE is more sensitive if classes reside in files which do not

match

> >>>>>the class names and packages
> >>>>>- this is a valid bug, but the workaround is easy: just folow the
> >>>>>name conventions
> >>>>>
> >>>>>2) source parser ignores project output jar even if it's explicitly
> >>>>>added to project classpath
> >>>>>- this concers freeform projects and the reasons are described in
> >>>>>issue
> >>>>>#116208
> >>>>>
> >>>>>3) cyclic dependency
> >>>>>- IDE doesn't handle cyclic dependency between projects very well
> >>>>>
> >>>>>4) error badges are new in 6.0, so any project configuration

problems
> >>>>>are more visible now
> >>>>>
> >>>>>Now we would like to know if _YOU_ still face some problems with
> >>>>>incorrect error badges. If _YOU_ do (reported or not), please file
an

> >>>>>issue [2] with as much information as you can [3]. Even the minor
> >>>>>configuration detail can be important!
> >>>>>
> >>>>>[2]
>
>>>>>http://www.netbeans.org/issues/enter_bug.cgi?component=java&subcompone
> >>>>>nt=source&version=6.0
> >>>>>
> >>>>>[3]
> >>>>>* Exact description of wrong behavior
> >>>>>* Project type
> >>>>>* Project configuration - source roots, dependency between projects,
> >>>>>library configuration etc.
> >>>>>* Sample project would be welcome
> >>>>>* Try to clean caches and check whether it helped or not
> >>>>>* Use _RC1 exclusively_ with empty userdir
> >>>>>
> >>>>>Thanks for your help, it is highly appreciated!
> >>>>>Jirka Prox
> >>>>>
> >>>>>
> >>>>>
> >>>>>

[Belbin, Peter]

In general, my experience so far with rc1 is that the error badges are much improved.

I did have one case where the error badge was wrong, even after closing and reopening netbeans.

After opening the source file, and seeing that nothing was complained about, at that point, the error badge got corrected, it seems.

So, as I said, error badges are much better, in my experience.

Good job.

NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named.  Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.

[Ulf Zibis]

Not on badges, but on red underlining, see:
http://www.netbeans.org/issues/show_bug.cgi?id=122663

-Ulf