Re: Renaming modules

Tim Lebedkov wrote:

> Hi group,
>
> I plan the following changes on the trunk...
>
> 1. rename the module org.netbeans.tasklistapi to 
> org.netbeans.modules.tasklist.api
> 2. rename tasklist-docscan.jar to 
> org-netbeans-modules-tasklist-docscan.jar
> 3. rename the module org.netbeans.modules.tasklist.suggestions to 
> org.netbeans.modules.tasklist.problems
> 4. move the code from org.netbeans.modules.tasklist.suggestions.ui 
> into the new directory tasklist/problems
> 5. rename the module org.netbeans.modules.suggestions_framework to 
> org.netbeans.modules.tasklist.suggestions
> 6. rename suggestions-framework.jar to 
> org-netbeans-modules-tasklist-suggestions.jar


I agree with the renames that result from projectizing the modules, but 
can you explain your rationale for renaming the suggestions ui module to 
"problems" and the suggestions framework to "suggestions" ?

I didn't do the split into two halves and haven't studied it, but I 
assume what Peter did was to put the suggestions "manager" part (the 
provider registration and notification) into a "framework" module and 
all the ui (window, node creation etc.) into a suggestions ui module. In 
that case, framework and ui seems like good names, whereas "suggestions" 
and "problems" seem like two different concepts. In fact they're pretty 
similar - suggestions are often provided fixes for problems. I don't 
think it will be clear how these two modules differ and what the 
relationships between them are.

-- Tor