Hey great answer. Thank you so much.
On 11/26/2012 3:52 PM, Ion Iovu wrote:
You created a NetBeans Module, you specified
com.mycompany.myproduct.mymodule in the 'Code Name Base'.
As a result the com.mycompany.myproduct.mymodule package was
You renamed that package to org.myorg and you expect that the
name of code name base to change respectively.
Those are actually different things. The Code Name base is
the unique identifier of a module in the universe. Having a
package with the same name is convenient resemblance only.
When it comes to packages, you could have any number of
different packages within a module, e.g.
which do not affect how the module is identified in the
This is needed so.
Say you start with org.mymoduleid as the id and a package
with the same name. You release it to the public. For version 2
you need to copy things from a MIT style licence project to
modify and use in your module, say org.very.open. What is
supposed to happen to the way the package is identified now.
If you change the module code name base, you'll surprise your
On Mon, Nov 26, 2012 at 10:32 PM, Ion
could you attach a sample project as an example and
instructions on how to reproduce that?
On Mon, Nov 26, 2012 at
10:00 PM, trhouse <
Refactoring a directory
which is part of a module via:
rt popup->refactor->rename of directory
does not push through the name change to at
least the following files which use the folder
<project name="name is now wrong"
<description = description is now wrong