Hi Marcel,

Reading between the lines I think you are asking if you need to have an ant installation on your machine - the answer is no, since the plugin brings in
ant as one of its dependencies.

Some background: everybody has their own theory but mine is that maven intends to replace all of the functionality of the ant tasks out there - and as a long term goal I see no problem with that. However in the short term I see the following problems:

1. I need stuff that works well right now and can't wait for months and years. Even when we do get maven replacements they won't have had the advantage of being
extensively user tested for quite some time.

2. Everybody knows ant syntax so familiarity is a big plus for somebody coming to maven for the first time. I do wish that even when pure maven replacements come along they would
retain syntax compatibility with a reasonable subset of ant.

3. With the other ant integration stuff we already have in maven we don't have the ability to easily map maven properties to ant attributes (correct me if I'm wrong). For me this seemingly small point ends up being a real killer as I personally find it very troublesome to supply values such as destDir="{project.output}/generated-sources/ main/java" (see I've probably got that wrong and I'd have to look it up!!!) by hand and keep them all synchronized.

4. I create a temporary build file because I really can't get to grips with the slippery ant api. Many methods are be private so I'd have to use reflection, also seeing problems such as running tasks individually would work but run them as part of the same build
would fail. Glad to abandon that approach.

---

On balance I do look forward to the ant-maven integration plugins being retired
but can't see it happening any time soon.

- Ashley

On 25 Nov 2005, at 08:11, Marcel Dullaart wrote:

Hi Ashley,

sounds good, I'll try-out the webdoclet ASAP.
Since you create an ant script on the fly, does that mean that using your
xdoclet plugin requires ant?
Is that a good idea?

Cheers,
Marcel
Ashley Williams <[EMAIL PROTECTED]> wrote on 25-11-2005 01:08:04:

I have placed new ejbdoclet and webdoclet plugins in the sandbox here
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/

And to see their use in a sample ear project try the following link:
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/sample-ear- proj/

---

Briefly they provide the following features:

1. Familiar ant xdoclet syntax can be used in configuration

2. Maven properties are automatically applied to the ant task - for
example
you don't have to specify attributes such as destDir="target/
generated-sources",
because the plugin applies a list of known mappings!

3. Can execute plugins in the same mvn session - eg a pom.xml that
kicks off
an ejb and then web build won't bomb out.

4. Works by creating an actual build.xml file on the fly.

- Ashley

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to