Issue 1105 in moose-technology: Moose Importing Abstract Classes - Packages Reorganisation - Moose-dev

25 Jan 2015

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1105 by v.blonde...(a)gmail.com: Moose Importing Abstract Classes -  
Packages Reorganisation
https://code.google.com/p/moose-technology/issues/detail?id=1105

The organisation of the Moose importers is a bit messy.

The classe MooseAbstractImporter should be used by MooseImportingTask and  
be a subclass of MooseTask.
MooseImportingTask is only used for smalltalk so it should be in  
Moose-SmalltalkImporter.
And MooseOperator is not only for Smalltalk so it should be in the  
Moose-Core package.

This following my mail from last year:
http://www.iam.unibe.ch/pipermail/moose-dev/2014-April/019420.html
and the discussion from 2011 from Usman and Stef:
http://forum.world.st/Proposal-to-enhance-the-MooseTask-inheritance-and-Moo…

Please fill in the labels with the following information:
* Type-Engineering
* Component-Moose

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings