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.
This issue came from this bug: http://www.netbeans.org/issues/show_bug.cgi?id=142733 The summary is that, if you have a Netbeans Module that exports a package, and then you do a refactor->rename on the package name, the module's exported packages will not reflect the change. An example: * Start with a Netbeans module with a package com.some.pkg. Set the package to be public (properties->API Versioning->Public Packages). * Refactor->Rename the package com.some.otherpkg com.some.pkg will not appear in the public packages widget (it shouldnt be). com.some.otherpkg will but it will not be labeled public. Expected behavior is that it would be. * Refactor->Rename the package com.some.pkg (ie put it back the way it was) The package now appears and is once again declared public. It remembered the old name.
*** This issue has been marked as a duplicate of 72275 ***
Not a dupe, that is something else.
*** Bug 199716 has been marked as a duplicate of this bug. ***
https://hg.netbeans.org/core-main/rev/a8c23a859a37
Integrated into 'main-golden', will be available in build *201306212301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/a8c23a859a37 User: Martin Kozeny <mkozeny@netbeans.org> Log: #144150: Refactor->Rename package updates module package exports.