This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 195148 - Warning on project but no explanation to why
Summary: Warning on project but no explanation to why
Status: VERIFIED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB Project (show other bugs)
Version: 7.0
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-07 22:41 UTC by Chiana
Modified: 2011-02-16 11:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot (13.62 KB, image/x-png)
2011-02-07 22:41 UTC, Chiana
Details
messages.log (67.31 KB, text/plain)
2011-02-16 01:45 UTC, Chiana
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chiana 2011-02-07 22:41:14 UTC
[ BUILD # : beta-2 ]
[ JDK VERSION : 1.6.23 ]

There are warnings on one project, but no explanation as to why or what to do
about it. This oftern occurs when moving a project to an other machine, usually
not when upgrading/downgrading versions.
Comment 1 Chiana 2011-02-07 22:41:48 UTC
Created attachment 105715 [details]
Screenshot
Comment 2 David Konecny 2011-02-08 00:20:20 UTC
If you right click the project node can you see some action like "Resolve Broken ..." there?
Comment 3 Chiana 2011-02-08 01:56:14 UTC
(In reply to comment #2)
> If you right click the project node can you see some action like "Resolve
> Broken ..." there?

Nope, nothing, sometimes this can happen if f.ex. a library file is missing, but I have checked, none is missing and the project compiles and runs fine (with the exception that GF is back down to b40 causing me other trouble...)
Comment 4 Chiana 2011-02-08 02:03:20 UTC
(In reply to comment #2)
> If you right click the project node can you see some action like "Resolve
> Broken ..." there?

Nope, nothing, sometimes this can happen if f.ex. a library file is missing,
but I have checked, none is missing and the project compiles and runs fine
(with the exception that GF is back down to b40 causing me other trouble...)
Comment 5 David Konecny 2011-02-08 22:33:41 UTC
What are values of these properties (nbproject/project.properties):
- javac.source
- javac.target
- platform.active
Comment 6 Chiana 2011-02-08 22:38:12 UTC
(In reply to comment #5)
> What are values of these properties (nbproject/project.properties):
> - javac.source
> - javac.target
> - platform.active

javac.source=1.6
javac.target=1.6
platform.active=default_platform
Comment 7 David Konecny 2011-02-08 23:33:26 UTC
OK, in order to display EJB project node in red color one of five conditions must be true. Unfortunately there is no tooltip hint explaining which condition(s) was hit. The conditions are:

* one of predefined properties (classpaths, platform, etc.) is broken - action "Resolve Broken References" is shown in such case on project's node

* server is missing or not set -> action "Resolve Missing Server" is visible

* a data source does not have connection to database - action "Resolve Broken DataSource" (I cannot remember exact wording) is visible

* javac source and target are not compatible with selected platform 

* broken server library

As we checked all first four conditions and because GlassFish does not have any server libraries I'm not sure what is triggering this problem.

In any case tooltips should be added to help indicate the problem.
Comment 8 David Konecny 2011-02-09 21:39:19 UTC
Again, thanks Kent for your project - one of your data sources is broken, that is it does not exist on the server. The problem was that EJB and AppClient were missing "Broken Datasource" action. I'm fixing that - 656d01762012.
Comment 9 Chiana 2011-02-16 01:44:58 UTC
David, I checked this with 6615on110215, but it is still there, a little tweaked thou, it correctly warns that there is a missing datasource and also there is the "resolve missing datasource" entry in the context menu, however after using that and resolved the problem with "kassaDebug" the marking didn't go away and when when using the "resolve..." item second time the list is empty.
Uploads the messages.log and I'm afraid I cannot verify the fix at this point.
Comment 10 Chiana 2011-02-16 01:45:42 UTC
Created attachment 106047 [details]
messages.log
Comment 11 Chiana 2011-02-16 01:49:45 UTC
After restarting the IDE the marking went away so no need to reopen the case at this time, have to redo the verification however to see if it needs a restart every time or if this was a specific case...
Comment 12 Chiana 2011-02-16 02:27:44 UTC
Apparently there seems to bee a requirement to restart the IDE after fixing the problem or the indication will not go away. Closing and reopening the project also fixes the indication.
I can verify the fix at this point, but it seems to need a few keystrokes more to be a complete fix due to the restart/reopen problem, should I file this as a separate bug and verify this one as fixed? What do you think?
Comment 13 David Konecny 2011-02-16 04:16:39 UTC
Yeah, feel free to file a new issue please. Thanks.
Comment 14 Chiana 2011-02-16 04:38:43 UTC
Verified with notification bug #195540 on 6651on110215
Comment 15 Quality Engineering 2011-02-16 11:45:37 UTC
Integrated into 'main-golden', will be available in build *201102160501* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/656d01762012
User: David Konecny <dkonecny@netbeans.org>
Log: #195148 - Warning on project but no explanation to why