http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#BIKESHED-PAIN TING
The language you use for transformation is, in the case of a Maven/Centipete-type tool, largely internal to the project. Gather some developers, call a vote, and use what the majority decides. Later on, if you have an itch to switch, convert the files, put them in a staging area, and call another vote. Both will do the job. Personally I like XSLT. I find it feature rich and I don't find it difficult to use. But I'll use DVSL if that's what the project requires. I think the quantity of developers who are literally incapable of using one or the other is negligable. If they are ideologically incapable, that's their problem. Actually it may not even be necessary to pick one or the other exclusively. For example Latka maintains its documentation in docbook, but Dion added a transform to Anakia so it works with the site build. Similarly you may be able to provide DVSL and XSL alternatives. This is not a slam on Oliver or anybody else. This just happened to be the most recent post on this topic. - Morgan ----- Original Message ----- From: "Andrew C. Oliver" <[EMAIL PROTECTED]> To: "Jakarta General List" <[EMAIL PROTECTED]> Sent: Thursday, May 02, 2002 8:51 AM Subject: Re: [PROPOSAL] Centaven and Friends (was Re: You make the decision (was Re: Quick! convert all your projects to maven!)) > Guys, > > Bottom line (you could probably guess these but it needs to be said): > > 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. > > 2. I'll -1 anything that REQUIRES me to use DVSL if I don't want to. > > So what decides (in the minds of the maven community) whether it is > successful... If its that a large set or all of the projects on > jakarta/xml/etc use it well then collaboration is the easiest way (it > removes my and several others objections). If its to force us all to > use your pet projects, well good luck. Its certainly not turning out to > be a springboard for collaboration. > > You want the hearts and minds, then we've outlined it. Work towards > collaboration. Work towards standards support. Then you'll reach a > consensus. If not, *shrug* then I'm sure some projects will use it, but > it will imo kind of be a flop of the goals I assume it wants to achieve. > > -Andy > > > > Berin Loritsch wrote: > > > Jon Scott Stevens wrote: > > > >> on 5/2/02 2:54 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > >> wrote: > >> > >> > >>> Centaven Reasoning: I don't see how we can easily do this. The > >>> approaches > >>> are wildly different at basic levels, e.g. dvsl vs xsl, entities vs > >>> external build files for ant, extending GUMPs descriptor vs > >>> generating one > >>> etc. Any 'coming together' is going to be a very difficult decision > >>> to get > >>> past the maven developer community, because they have a tool that > >>> works and > >>> is going in a consistent direction from a design perspective, and that > >>> coming together will result in much slowing of progress. I don't think, > >>> IMHO, either tool is mature enough at this point to merge. > >> > >> > >> > >> I can agree with that. Hell, the dvsl vs. xsl is a showstopper for me. > >> > >> I can't stand XSL... > > > > > > > > And I can't be bothered with non-standard transformation languages... > > > > Centipede uses Cocoon, which allows you to use Velocity, or whatever you > > want to transform your documents. You aren't locked into XSL if you > > don't want. THat's the beauty of it. WIth Maven, you are locked into > > DVSL, and there is no other way of doing things. :/ > > > > But again, Reality Check: how often do you mess with the look and feel > > of a site? If the theme exists--use it. It's that simple. > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
