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.
|Summary:||Moving projects breaks future dependency|
|Product:||java||Reporter:||Milan Kubec <mkubec>|
|Component:||Unsupported||Assignee:||David Konecny <dkonecny>|
|Issue Type:||DEFECT||Exception Reporter:|
|Bug Depends on:|
|Attachments:||exc stack traces|
Description Milan Kubec 2004-05-24 14:54:04 UTC
[custom build 20040524, JDK 1.4.2_04] I've created two projects, one depending on the other one. After that I moved those two projects somewhere else and opened the one that depended on the other one - dependency was broken, which is OK. I removed the jar from list of required project jars and added correct project dependency. But I still wasn't able to build the project becasue the script was refering to old jar location. private.properties file is listing: project.JGraph-3.4=/usr/local/space/work/Projects/ForTesting/JGraph-3.4 project.JGraph-3.4-1=/usr/local/space/testing/projects/JGraph-3.4 where the second one is the correct one, but it's not used during build. The error message is: deps-jar: /usr/local/space/testing/projects/JGraph-3.4-examples/nbproject/build-impl.xml:174: Basedir /usr/local/space/work/Projects/ForTesting/JGraph-3.4 does not exist BUILD FAILED (total time: 0 seconds)
Comment 1 Milan Kubec 2004-05-24 16:22:22 UTC
Such project is then unusabe because there is no way how to remove those useless references from UI.
Comment 2 Jesse Glick 2004-05-24 17:08:53 UTC
Looks like a problem either in ReferencesHelper or in the classpath customizer GUI; not sure which. Certainly if you remove the subproject from the classpath it is supposed to remove the entry from private.properties. And even if it doesn't, and a new key is created when you readd the correct version, the new key is supposed to be used at build time - not the old one.
Comment 3 Milan Kubec 2004-05-25 13:26:51 UTC
I forgot one thing - I executed Clean Build action just after opening the project (that failed of course), after that I wanted to remove the jar from CP. Also when opening the project with dependency the other project was opened even if it didn't exist! I'll attach exceptions thrown when opening the non-existing opened project.
Comment 5 David Konecny 2004-05-25 13:55:03 UTC
I will fix the ReferenceHelper problem in this issue. Please file opening of non-existing subproject as separate issue.
Comment 6 David Konecny 2004-06-04 07:38:18 UTC
After looking at this with Milan we realized that it is user's error - he left broken project on classpath and that's why build failed. Removing that project solves it.
Comment 7 Milan Kubec 2005-07-11 14:11:22 UTC
Verified/Closed, moving of projects will be solved by special action soon.