Thorsten Scherler wrote:
On Mon, 2008-09-01 at 13:40 +0300, Sjur Moshagen wrote:
...
I agree with Ross that the easiest solution would be to just move the
code to core.
Yeah, it is just one generator. It is fine with me to move this class
directly to the core, best solution IMO is to leave it in the plugin
structure but build it by default with the core. Meaning we can drop the
dependency in the required plugin section.
However ATM I cannot look into the needed changes for that. I am fine
with either move the class directly to the core or generate the jar once
and add it to the lib dir. In both cases we need the one match that the
plugin offers in the main sitemap.
Looks like we have a solution then.
I don't understand the motivation for leaving the code in a plugin but
building it with core, I'm -0 on that.
Easiest solution is certainly just to take the code into core and lose
the plugin, I'm +0 for that.
Ross
