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. Costin > > 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]>
