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 201663 - Implement more reliable versioning policy
Summary: Implement more reliable versioning policy
Status: NEW
Alias: None
Product: qa
Classification: Unclassified
Component: Test Specifications (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-06 07:44 UTC by Peter Nabbefeld
Modified: 2011-09-06 07:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2011-09-06 07:44:29 UTC 
I've got problems several times with bad dependency graphs, sometimes resulting in a completely corrupted IDE. This is caused by upgrading a module which others depend on, so this module gets updated by autoupdate, but not upgrading spec version of the dependend modules, so dependencies are not updated and as such are broken after the update. This hurts especially, if the Editor Libraries are upgraded. Latest issue #201616.

Some NB members just think, upgrades are not necessary for daily build UC, but this makes testing impossible, which will decrease quality on the long run (who wants to test, if tests break too often?).

Please implement processes in a manner so that dependecies are considered when upgrading.