From: <[EMAIL PROTECTED]>
> On Thu, 2 May 2002, Andrew C. Oliver wrote:
>
> > 1. I'll -1 the attempt to switch any project to maven that I have a vote
> > on unless there is a concerted effort to collaborate on a combined
> > effort with centipede.
>
> Same here, I'll -1 a switch to either maven or centipede on the projects I
> have a vote on until they find a way to work togheter.
>
> DVSL may be a nice language, but XSLT is the standard - regardless of how
> you play with the word. I'm fine with a tool that supports both.
>
> I'll probably be -1 on any tool that uses a project descriptor that is not
> compatible with Gump ( it can add more information - as long as it's
> backward compatible ). If you want changes to the DTD - get it into Gump.
> When centipede and maven will reach the same level with gump ( that allow
> all apache projects to be built without forcing anything but trivial
> changes to the build file ) - we can talk again.
Centipede descriptor is compatible with Gump.
It enhances it as you say, and I will propose it on the gump mailing list as
I promised a while back. It contains the suggestions I kindly recieved from
many users and mailing lists, who I kindly thank. Forrest is now being
gumped using this descriptor directly.
It also doesn't require to change the build files, and doesn't require to
change the directory layout, because layout.xml defines the mapping between
logical and phisical dirs.
It's pure plain Ant.
All of the Centipede features are written with Ant.
Centipede will make it possible to choose Cocoon, Anakia or Maven for
documentation building, because I want users to have a choice, if they want
it.
With Centipede you can call the Centipede targets (which are more granular
than in Maven, usually), define your properties in XML, or have the
"automagic" cent call them for you.
We need documentation, and that is what I'm writing now, it's on the top of
my todo list.
-oOo-
Someone hinted that what I wrote was all blah, blah, blah... read my bottom
line, man.
-oOo-
I keep the possibility of collaborating with Maven always open, but the
recent mails say it all.
This is my second attempt, and won't be the last.
I'm ok with a new project that keeps together build and code comprehension
tools, like Ant, Gump, Alexandria, Maven, and Centipede. We use the same
descriptor data, since we all use basically the same input, so it's ok for
me.
I will continue to work closely with Gump and give back stuff to Alexandria
as previously stated, as we have done with Ant (the new XmlProperty task is
from Centipede).
In contrast, I see Maven doing the opposite, including inside other projects
as Alexandria and putting on them the Maven trademark. I hope they will
give proper credit to Centipede when it will be needed.
Many tools it has, could be cool to be in Commons, (like the importScrubber)
but it seems that you will have to get all Maven to get it to work.
There is also JJAR in Commons which Centipede uses, but it seems that they
don't really like to eat the same Jakarta dogfood they incite others to
have.
"You can bring a horse to water, but you can't make him drink".
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
