|
Notes |
|
|
|
This should probably be ignored. The affected class implement the 'ant export.database' command. This command did accept a -Dmodule parameter to only export a single module. However this single-module export did never work correctly and the official documentation is that the task does always export all modules in development and the export time.
The removed module correspond to the removed -Dmodule parameter and are called indirectly by ant and normally not directly by anyone. As the code using the parameter has been removed it does not make sense to keep the functions around, which would give the impression that the parameter does anything.
A clarification mail regarding the -Dmodule parameter was sent to the -development list to inform/remind people about the implemented behavior. |
|
|
|
|
Yes, I agree with Stefan, this was caused by a change in a dbsourcemanager class. There shouldn't be any modules that use this dbsourcemanager task directly through Java code, so this is really a non-issue.
Note that direct ant calls to the export.database task will continue to work correctly, whether they use the -Dmodule property or not. The only problem could be if somebody tried to instantiate the Task class in a Java class, something that would be really strange. |
|
|
|
|
Exception accepted, but let's not fully ignore this.
Please publish an alert indicating no risk because of the API change. |
|
|
|
(0022052)
|
|
hgbot
|
|
2009-11-20 10:52
|
|
|
|
|
|
|