> 1) The code was removed without any discussion on this list. Spinning off a subproject is a big deal, and I believe it should always be voted on.
My fault, I planned to move the tld processing to a separate module or project since
the beginning. I planned to advertise/discuss this on developer mailing list but I
never did, sorry.
3) The new project does not currently abide by the terms of the Artistic
License. The Artistic requires that, if the elements of the code are
distributed separately from the parent, "prominent notice in each changed
file stating how and when you changed that file".
I think the new project is now abiding by the terms of the AL. The original source of
the files in stated in home page ("The maven/xslt scripts in this plugin were
initially developed in the displaytag project") and the xslt files contains:
<!--
This file was initially developed in the displaytag project -
http://displaytag.sourceforge.net
Original author of this file is Andy TXrXiXpXp Pruitt
-->
> "Andy Tripp" (who???),
:) sorry Andy, my fault again, I will fix it, should read Andy Pruitt (this is the
result of copy and paste when having different projects -JTidy- in the same eclipse
workspace) :)
The copyright notice is only in these files because only these files come directly
from displaytag; there are no changes mentioned since there are no changes after
displaytag.
> 4) If code is going to be spun out, the committers at displaytag should
determine the committers at the new project.
The project is free and open source, anybody who wants to help is free to join. I
created the new sourceforge project and I didn't added any of the other displaytag
developers: I'm absolutely happy to do that, but I don't want to add a lot of unactive
developers like the displaytag project currently has.
If someone thinks to have some free time to contribute I will be happy to include it
in the new project.
Please note the scope of the spin-off is only to make "some parts" of the displaytag
projects also more useful and to give away something other developers can reuse
without reinventing the wheel.
(PS Note that according to actual licence this could be done without any
discussion/communication to the source project)
===
and now: about the maven taglib plugin.
It actually simply contains the same goals you previously saw in displaytag:
- taglib documentation from a tld 1.2
- conversion from 1.2 to 1.1 tld
Source and output files follow the previous displaytag naming but are now configurable
through project properties.
I'm working (mh, planning) to add more useful feature like basic taglib validation and
tests (probably using tagunit, but I'm also evaluating a custom off-line validation)
fabrizio
<<winmail.dat>>
