On Fri, 2004-09-10 at 01:00, David Smiley wrote:
> On Sep 9, 2004, at 4:07 AM, M.-Leander Reimer wrote:
...
> Thanks... this information led me on the right path.  I went into a 
> sub-folder than where I was running maven commands yesterday.  The 
> sub-folder is a module which uses ejbdoclet and it has the proper 
> dependancies in it's project.xml.  I then tried the goal 
> "xdoclet:ejbdoclet" again.  xdoclet didn't kick in (nothing was 
> generated) though maven says it completed successfully.  I examined 
> maven.xml and it started with:
> 
> <project>
> 
>      <preGoal name="java:compile">
>          <mkdir dir="target/xdoclet/ejbdoclet"/>
>          <echo message="Generating source..."/>
>          <attainGoal name="xdoclet:ejbdoclet"/>
> 
>          <ejbdoclet destdir="${maven.build.dir}/xdoclet/ejbdoclet"
>              excludedtags="@version,@author"
>              ejbspec="2.0"
>              mergeDir="${maven.build.dir}/ejb"
>              >
> ...

I may be mistaken, since I don't actually use Maven myself, but I
thought the <attainGoal name="xdoclet:ejbdoclet"/> was Maven's
equivalent of the <ejbdoclet> Ant task, so why do you have both?

As I understand it, Maven includes support for Ant tasks, so you can
either do things Ant-style with the <ejbdoclet> task & subtasks, or you
do it Maven-style with <attainGoal> and a load of entries in the
project.properties to specify all the parameters.  You only need one of
them, though.

There's an example of both Ant and Maven build setup in the samples
directory.  See samples/maven.xml, samples/project.properties and
samples/project.xml for the Maven configuration.


Andrew.

> 
> I am new to Maven & XDoclet but that logic there seems oddly placed... 
> that is, shouldn't the <ejbdoclet> tag stuff go somewhere in 
> project.xml?  By the way, there is a build.properties which contain 
> lots of xdoclet info for this project.
> 
> I really wish there was better Maven documentation.  They document the 
> properties very well but fall short completely on any sort of tag 
> reference and information on the relationship between maven.xml and 
> project.xml & whatever comes with a plugin.
> 
> I also got the following error:
> 
>       Tag library requested that is not present: 'maven' in plugin: 
> 'maven-xdoclet-plugin-1.2.1'
> 
> I have no clue how to fix that or what it's ramifications were but 
> xdoclet has done it's work anyway.
> 
> Thanks for everyone's help.
> 
> ~ Dave Smiley
-- 



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to