deprecation rules for 3.0

[Mike Haberman]

I know that scarab is using the 3.0 source, so I can easily check for
any changes that affect it (none so far).  But can I move stuff around
(mostly between Resolver and ModuleLoader) without following the deprecation
rules?  It doesn't affect other Turbine classes.  Just don't want to
step on any toes.

My goal is to have the Resolver be

 String getTemplate()
 Module getModule()

While it's current public methods are

   getTemplate()
   parseTemplatePath()
   getPossibleModules()
   getPossibleTemplates()

The last two can be private in the DefaultResolver implementation (no
others rely on it).  The parseTemplatePath() may be useful outside
of the Resolver, does anyone have any opinion on where it should reside?


thanks

mike

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>