On Tue, 2003-02-11 at 04:53, David Jencks wrote:
> On 2003.02.10 11:57 Darren Hartford wrote:
> > Hi All,
> > Been using Ant and Xdoclet, great tools, makes my life a LOT easier than
> > good-ol' writing interfaces on my own :-)
> > 
> > I have started migrating to the Maven build system, to support more
> > project management features, auto javadoc creation and deployment,
> > changelog, blah blah blah.  I know you can do all these things with Ant
> > (I used to do that).  Looking to the Jboss community to see where
> > everyone else is going, experiences, etc.  Maven/xDoclet integration
> > requires community support and dev, and would like opinions/feedback if
> > anyone else is going this route? 
> 
> I haven't been able to figure out why Maven is better than plain ant.  Can
> you explain?  Would it be appropriate to use Maven to build jboss?

Maven is a great tool, if you project fits the holes it drills for you.
If you have a square peg then you are in a world of hurt, last I checked
you couldn't have two java source directories, the reactor managed
project interdependencies very well, but didn't aggregate the results in
any way.

Centipede removes the biggest advantage/disadvantage of maven, that it's
not in ant. Centipede is based on ant 1.6 (which has an import feature).
It supports use of the maven repository for downloading modules (and the
leaders are the people behind the jakarta repository proposal). It
supports automatic download of build components (which is nice). It
suffers from teh their holes problem in the same way maven does.

I was a user of maven who switched to centipede for ant compatibility.

Maven is new (and promising), jelly is really nice, I'm using it and the
werken goal system in experimental projects now. My major projects are
still built with ant. I have a jboss style build with lots of modules. I
know that the new jira is built using maven with lots of modules, it'll
be interesting to watch. 

> > 
> > p.s. Is the Jboss-Xdoclet going to be a seperate module controlled by
> > JBoss and available through a JBoss controlled location, or still
> > retrieved through xDoclet?
> 
> That's the plan, but there are 2 problems atm:
> 
> 1. I haven't been able to get xdoclet to build reliably as part of the
> jboss build process.  I think but can't prove that this has to do with the
> buildmagic tasks not keeping up with changes in ant.
> 
> 2. No one (AFAIK) has stepped forward to say "I will maintain the jboss
> xdoclet stuff in jboss"
> 
> Right now it is sort of possible to build xdoclet as part of jb4 but the
> normal version is checked into cvs.
> 
> david jencks
> > 
> > thanks, just looking for some discussion
> > -D
> > 
> > 
> > -------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld
> > http://www.vasoftware.com
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > 
> > 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
-- 
If you don't test then your code is only a collection of bugs which 
apparently behave like a working program. 

Website: http://www.rocketred.com.au/blogs/kevin/



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to