Here is a proposal<div><br></div><div><br></div><div><br></div><div>MooseTask</div><div>        MooseAbstractImporter (which right now is not used and only contain error handling and importingContext)</div><div>                           this class could hold the plugin mechanism that would be run as a tearDown from now.</div>
<div><br></div><div>              </div><div>                  MooseImportingTask - Renamed SmalltalkImportingTask (add importerClass logic)</div><div>                             MooseCompositeImporterTask </div><div>                                  MooseSqueakClassPackageImporterTask -&gt; MoosePharoClassPackageExtractTask</div>
<div>                                  MooseSqueakClasssCategoriesImporterTask - &gt;MoosePharoClassCategoriesExtractTask</div><div>                             MooseImportClassesTask -&gt; MooseExtractClassesTask</div><div>
<br></div><div>                  FileStructureImporter(/Extractor)</div><div><br></div><div><br></div><div>         MooseOperator</div><div><br></div><div><br></div><div>Since we will not be able to inherit from the same superclass MSEReader and MooseAbstractImporter.</div>
<div>We could define one trait to represent the plugin management and apply to the MSEReader and MooseAbstractImporter.</div><div><br></div><div>So let us know what you think.</div><div><br></div><div>Stef and Usman </div>