Issue 745 in moose-technology: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses
Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 745 by usman.bh...@gmail.com: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses http://code.google.com/p/moose-technology/issues/detail?id=745
setUp |importer | importer := MooseSqueakClassPackageImporterTask new. importer importingContext mergeClassAndMetaclass.
can be safely rewritten as
setUp |importer | importer := MooseSqueakClassPackageImporterTask new. importer importingContext mergeClassAndMetaclass.
Updates: Status: Fixed Labels: Component-SmalltalkImporter Milestone-4.6
Comment #1 on issue 745 by tudor.gi...@gmail.com: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses http://code.google.com/p/moose-technology/issues/detail?id=745
This was fixed.
Comment #2 on issue 745 by stephane...@gmail.com: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses http://code.google.com/p/moose-technology/issues/detail?id=745
You fix all the caller of importerClass: ?
Stef
Comment #3 on issue 745 by tudor.gi...@gmail.com: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses http://code.google.com/p/moose-technology/issues/detail?id=745
No. But, as I understood, the issue was that it was not possible to have it without specifying importerClass:.
Comment #4 on issue 745 by stephane...@gmail.com: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses http://code.google.com/p/moose-technology/issues/detail?id=745
No I was stupid in copy and paste, most of the time we can remove importerClass: invocation. I should do a pass and remove them. This was useful when we had famix20 and famix30
-
moose-technology＠googlecode.com