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 103665

Summary: Project broken when name of JAR from subproject changed
Product: java Reporter: swebb99 <swebb99>
Component: ProjectAssignee: Tomas Zezula <tzezula>
Status: NEW ---    
Severity: blocker CC: jglick, jiriprox
Priority: P3    
Version: 5.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description swebb99 2007-05-10 16:48:30 UTC
If a project is setup to depend on another existing project a problem occurs if
the dist.jar setting for the project that it depends on is changed. The
properties dialog under the compile time settings shows missing project and the
project fails to build due to the class path not being correct.

Shouldn't the ant script in the project be updated to reflect the change in the
project it depends on ?

I'm struggling with this problem becuase the sub project I have use the project
version number as part of the jar naming strategy. When this rename occurs any
projects that depend on it fail to build afterwards. Is there anyway in netbeans
of setting up a project dependancy but not explicitly setting the jar file but
instead the directory the jar can be found in ?
Comment 1 rbalada 2007-05-13 21:42:06 UTC
Re-assigning to 'ide' module.
Comment 2 Jiri Prox 2007-05-14 12:32:43 UTC
What type of project do you use? 
Comment 3 Jesse Glick 2007-05-22 22:40:32 UTC
Sorry, each referring project keeps the actual JAR name. I would perhaps
recommend leaving ${dist.jar} alone and making a separate Ant target to publish
all your JARs with corrected names.
Comment 4 Jesse Glick 2008-07-30 22:55:58 UTC
Probably lower priority in 6.5 since Compile on Save projects should be ignoring dist/*.jar for purposes of
dependencies. Haven't checked though.