I pretty much use maven.xml much like a build.xml and have hadn't any real issues, you don't even need to use the ant tags namespace.
Its not a question of maven, the problem I'm trying to get around is a checkout and build style build with no additional hoops to jump through. I know you guys seem to think that cocoon is in someway a better kettle of fish to struts, but checkout struts out of cvs and build "look no hoops!!!". The "don't let you friends commit to projects" or something to that effect I noticed on this list was frankly laughable. Ant or maven cocoon needs building from source, rather than describe this as a bug with cocoon, you say its nothing to do with you and just define another hoop. Ant or maven the first step would be to have the dependencies for a release builds available on a maven style repository. Then the src of cocoon could be compiled against that, at the very least when the ant/maven file downloads the source it could be just the source and not a bunch of jar files in CVS. I'll investigate further and see if I can get some time to submit each of the dependencies to ibiblio. Basically I want to get the hoop-jumping down to pointing to the cocoon source and build (a project with a standard directory struture). Mark On Mon, 14 Feb 2005 00:46:58 +0000, Paul Russell <[EMAIL PROTECTED]> wrote: > On Sun, 13 Feb 2005 19:26:44 -0500, Stefano Mazzocchi > <[EMAIL PROTECTED]> wrote: > > Ralph Goers wrote: > > > I believe what you are suggesting would require that the Cocoon build be > > > converted to use Maven. While I personally would welcome that, this has > > > been discussed before and for some reason several committers won't > > > support that. Sorry. > > I was the one pushing back for that. Since then I've taken a deep > > review of Maven and I like some of the archiectural concepts. > > So, saying "no way" is a little bit too much. I would welcome if > > somebody tried and did it and it worked. > > I would tend to agree - I've used maven a little recently, despite > initially disliking it, and I have to say, it works. There are > significant chunks of it I still don't like (personally, I think it > needs significant re-design -- I'd prefer to see it built on top of a > proper plug-in architecture like Hivemind), but it does do the job > well, providing you use it for what it's designed for: building one > thing at a time. Try and use it the way you'd use Ant, and you're in > for a bumpy ride. Personally, I've started about 5 projects internally > using Maven in as many months, and none using raw Ant during the same > period. > > > But I have no energy/time/will/itch-to-scratch to do it myself. > > Same problem here :( > > Paul >
