Hi,
[as I'm not actively working on the 2.4-dev tree, I'm a bit hesitant
to check code in without talking to the active developers].
I did a fair bit of work, some bug fixes and lots of docs for the
plugin on the 2.3-dev tree.
Basically, the plugin is now turbine-release independent. All that
would be necessary to get it working on 2.4-dev is someone sitting
down and creating a few templates for project.xml and all the other
files needed for a 2.4 skeleton (I understand that the web.xml file
has more parameters than on 2.3 and you need at least a pipeline
definition file, which is not needed in 2.3).
In the end, I'd like to see the plugin decoupled from the turbine tree
itself and having it as its own subproject CVS @ jakarta. Mainly
because it _is_ turbine independent, as long as the templates (aka
flavors) are up to date.
Eric: If you want to bring the HEAD code back in sync: This is now a
good time. Except for bug fixes, I feel that the plugin itself and its
documentation is now stable enough to get more testing.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honourable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
