Hi,
I have been looking at the existing code base of the Castor plugin for
some days now, and it looks like I will have to break existing contracts
to get it working again (fully, against all Castor releases).
Right now (SVN), the plugin will run against versions of Castor starting
from 1.0.5 to now. But I'd like to get it working against older versions
of Castor as well, but the way it's implemented would not allow that.
There's an arae of code where the plugin tries to outsmart the way
Castor normally works. And the way this has been implemented .. well,
moves a couple of configuration parameters supplied by the means of a
file to the plugin configuration section.
As already said, I'd like to get it working again against all versions
of Castor, and would like to refactor the plugin. For this, I would have
to drop this 'smartness'.
My question: is this actually an option with Mojo plugins. Can we (well,
not) easily drop some configuration parameters even though they have
been supported in the past. Of course we'd make this clear in the plugin
configuration (as much as we don't like this), but I cannot see a way
around.
I'd love to make the code base simpler and more maintainable, so that
new things can be added easily (again).
Looking forward to hear opinions.
Regards
Werner Guttmann
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
