You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by di...@multitask.com.au on 2002/05/09 03:05:57 UTC
RE: Quick comparison between centipede and Maven
Mavelets == Maven Plug-ins.
They are extra functionality added to Maven, beyond the base and are
effectively 'take or leave' functionality - some users will want it, others
wont.
We're currently in the process of documenting how the j2ee plug-in works,
so that others can use it as an example.
As for skinning the site, Maven's direction has been to have it's own
style/content with no 'skinning' ability for consistency and simplicity
purposes. Things like forrest, for example, are planned to be done as a
plug-in.
So that the maven:docs will *always* be maven generated and consistent,
whereas maven:forrest-docs would be totally under forrests control. If you
wish to have your own site look and feel, the recommended way at the moment
is to write a plug-in and bootstrap maven so it is integrated. Longer term
we hope to make the bootstrap process go away, and the plug-ins be
distributed as standalone jars.
At the moment the forrest guys don't feel they're ready to be 'plugged-in'
to Maven - Is this a fair comment? - so we're waiting on them in that
regard.
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
James Taylor
<jtaylor@4lane To: 'Turbine Maven Developers List'
.com> <tu...@jakarta.apache.org>
cc:
05/09/02 10:47 Subject: RE: Quick comparison between centipede and Maven
AM
Please respond
to "Turbine
Maven
Developers
List"
> Do you know what the "mavelets" are meant to address? Would I
> be able to add in my own skin for my own site with them?
dIon or Glenn might be better able to explain it, but I can give you an
illustrative example: currently there is work being done on mavelet
which will allow packaging of web applications.
No it will not allow you to skin your site. That is a different issue:
we have chosen not to allow you to do that, though it could be easily
done with a property.
This is not a choice I agree with, however we have all decided to table
the discussion until Jason returns from vacation since he is the biggest
proponent of the other viewpoint. (To be clear, I agree that allowing
skinning is incongruous with the goals of maven, but considering the
demand it is an area where a compromise may be justified).
Thanks,
James
--
To unsubscribe, e-mail: <
mailto:turbine-maven-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <
mailto:turbine-maven-dev-help@jakarta.apache.org>
Re: Quick comparison between centipede and Maven
Posted by Nicola Ken Barozzi <ni...@apache.org>.
From: <di...@multitask.com.au>
> At the moment the forrest guys don't feel they're ready to be 'plugged-in'
> to Maven - Is this a fair comment? - so we're waiting on them in that
> regard.
Forrest is really in its early stages, and we still don't have a web site.
I am both a Centipede and a Forrest developer, but I am committed to
maintain the projects separate, so that it will be easy to use Centipede as
a plugin for _any_ project, and also with Maven built ones.
On the Jakarta list I have expressed how I fell on Centipede Vs Maven, and
how integration can be possible, so you know I will help Maven use Forrest
when the time will come.
For now, if you are interested, you can use the forrest.cent.jar as a
starting point.
Thank you.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------