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 130880 - added project dependency is not visible in the UI
Summary: added project dependency is not visible in the UI
Status: RESOLVED WORKSFORME
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P3 blocker with 1 vote (vote)
Assignee: David Konecny
URL:
Keywords: RANDOM, REGRESSION
: 138014 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-23 22:46 UTC by Lukas Jungmann
Modified: 2008-09-17 04:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
affected project (w/o jar files) (430.43 KB, application/x-compressed)
2008-04-11 15:01 UTC, Lukas Jungmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2008-03-23 22:46:11 UTC
netbeans-hudson-trunk-1247-javaee

-create new javaapplication with some classes
-create new web project
-invoke Add Project action on the libraries node and add javaapplication project

=> added project is not visible under libraries node nor in project properties->libraries

  codecompletion seems to start working after readding the foreign project to libraries
  there's now no way to remove foreign project from libraries
Comment 1 David Konecny 2008-03-25 03:48:04 UTC
I cannot reproduce this on today's build with clean userdir and new java and web project. Just recently I fixed issue
130167 but that was related only to Test Libraries.

Is this always reproducible for you? On all combinations of projects? The fact that CC works (and build therefore too,
right?) sounds like visualization issue? What happens after restart of IDE? Or if you just close and reopen project?
Comment 2 Lukas Jungmann 2008-03-25 15:25:09 UTC
Neither me in current trunk:( so it already somehow got fixed itself. Marking as worksforme for now. I'll reopen this
when I spot it again.
Comment 3 Lukas Jungmann 2008-04-02 20:24:48 UTC
Just reproduced in instrumented build from release61, now with java library, but still don't have a reproducible case :(
Restart of the IDE helped. Till the restart of the IDE there has been no way to add any jar, library, project to the web
project - I had 4 projects opened and only one has been affected by this bug. That's all I can say now :(
Comment 4 David Konecny 2008-04-02 23:13:27 UTC
Re. "no way to add any jar, library, project to the web project" - did you try it via Project Properties?

I will try to look at the code and perhaps add some logging.
Comment 5 Lukas Jungmann 2008-04-02 23:31:13 UTC
grrr, you always know what I've forgotten to try :-)

No, I didn't try that :-( will do next time... Anyway some logging would be great. Thanks.
Comment 6 David Konecny 2008-04-04 03:09:48 UTC
AddProject action on Libraries node seems to be so straightforward that I cannot figure out what could go wrong. If it
happens again I would try to add something via Project Properties and if it works try to remove it via Libraries Node.
And then try to add it again via LibNode. Basically try any possible combination and see if any of them has any impact.
I would also watch project.xml and project.properties whether their content/timestamp has changed or not. 
Comment 7 Jiri Prox 2008-04-11 01:09:28 UTC
moving opened issues from TM <= 6.1 to TM=Dev
Comment 8 Lukas Jungmann 2008-04-11 14:19:17 UTC
reproduced in rc1 (Vista, jdk5.0_15), so:

-I've created a JavaEE5 web project for bundled tomcat and enabled shareability (accepting defaults)
-I've created JAX-WS web service client in this project

=> expected is that the JAX-WS library will be added to the project if it is not already there, current behaviour is
that the library is copied into ./lib folder but that's all - classpath is not altered, library is not visible under
project's libraries

another effect of this issue is that at this point:
-add project action does not work
-add library action does not work (import library works, but not its addition to the project)
-add jar/folder action works
-adding whatever using project properties also works as one would expect

I'll try to attach affected project, just in case
Comment 9 Lukas Jungmann 2008-04-11 15:01:27 UTC
Created attachment 60052 [details]
affected project (w/o jar files)
Comment 10 David Konecny 2008-04-14 00:24:10 UTC
Are you able to reproduce it or did it happen just once? I tried it couple of times on the same setup and it works fine.
Comment 11 Lukas Jungmann 2008-04-15 21:47:29 UTC
only randomly in various builds :(
Comment 12 Lukas Jungmann 2008-06-24 10:43:45 UTC
*** Issue 138014 has been marked as a duplicate of this issue. ***
Comment 13 Jeffrey Rubinoff 2008-07-13 18:02:39 UTC
Myself and at least one user have had similar experiences when creating RESTful services from entity classes and then
building the project. To wit, build fails because key Jersey classes are missing. Solution is to manually add Jersey
libraries to the classpath via Project Properties. Sometimes this problem occurs, sometimes not. I've started adding
notes to the RESTful tutorials but reading this issue, I suppose I should add them to the JAX-WS tutorials as well :( 
Comment 14 David Konecny 2008-07-13 22:16:54 UTC
Re. "I've started adding notes to the RESTful tutorials" - it depends how frequently this happens. If it happens 4 out
of let say 10 tries then I should be able to reproduce it and fix it. So far it was case it happens once in a month and
we do not know how and why.
Comment 15 Jeffrey Rubinoff 2008-07-13 23:31:31 UTC
It seems to happen to me *a lot* when I'm deleting and recreating a project. Yesterday it happened every single time I
recreated the CustomerDB project and created entity classes and RESTful services in it. But it doesn't happen every time
even in those circumstance. 
In the future, I will start keeping proper notes on exactly when this happens. I haven't paid that much attention to it
in the past because adding libraries to the project properties seemed obvious, but in retrospect this was a considerable
oversight on my part.
Comment 16 David Konecny 2008-07-13 23:52:17 UTC
OK, thanks. Just keep in mind that deleting a project and recreating it under *the same name* is known to cause all
sorts of problems so just do not do that - use unique project names.
Comment 17 David Konecny 2008-09-17 04:17:18 UTC
Feel free to reopen if it happens again.