I disagree. Scan the mailing lists to see how many problems people have getting the maven-xdoclet plugin up and running. In any non-trivial setup, it's much more efficient to use the ant task. the maven-xdoclet plugin is just plain clucky and the documentation is sub par. even trying to modify the plugin is impossible since it contains literally thousands of lines of plugin.jelly code to weed through.
no thanks, I'll stick to my 100+ line maven.xml which is perfectly clear. > -----Original Message----- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 25, 2004 11:17 AM > To: Maven Users List > Subject: Re: Maven XDoclet plug-in examples? > > > Why you don't use the xdoclet plugin? > It simplify the maven.xml > > Emmanuel > > ----- Original Message ----- > From: "Ryan Sonnek" <[EMAIL PROTECTED]> > To: "Maven Users List" <[EMAIL PROTECTED]> > Sent: Tuesday, May 25, 2004 5:57 PM > Subject: RE: Maven XDoclet plug-in examples? > > > I wrote the wiki example for EJB generation using maven > (http://wiki.codehaus.org/maven/CreatingEjbApplications) and > have used the > ant task to execute xdoclet with much success. my example > can be used to > generate as many ejbs as you'd like without creating more > projects. Let me > know if you have questions or comments. I'd be glad to help > out, since i've > been through this integration frustration. > > Ryan > > > -----Original Message----- > > From: Mark Slater [mailto:[EMAIL PROTECTED] > > Sent: Monday, May 24, 2004 6:36 PM > > To: [EMAIL PROTECTED] > > Subject: Maven XDoclet plug-in examples? > > > > > > I'm a little disappointed by the quality of the Maven/XDoclet > > integration > > documentation out there. There seem to be a lot of good > > starts, but nothing in > > the way of a complete solution. I've found the three Wiki > > pages, Maven Magic, > > and a few other pages, and most of them make it look easy > > enough, but when I > > try to duplicate their successes, it doesn't work so well for me. > > > > I'm using Maven 1.0rc2 (moving to rc3, but I'm not sure it's > > going to make a > > difference in this), and XDoclet 1.2.1. While I can get a > > maven.xml script to > > invoke XDoclet like an Ant task, it doesn't seem to do all > > the steps the > > tutorials expect it to (generating the application.xml file, > > for example). So > > I tried to use the maven-xdoclet-plugin, and I get the > > following message: > > > > [echo] Running ejb:install for Testing EJB Module > > Tag library requested that is not present: 'maven' in plugin: > > 'maven-xdoclet- > > plugin-1.2.1' > > > > I found some discussions that suggested this was a namespace > > problem, but > > changing the namespaces in the plugin.jelly didn't help. All > > I know is that > > I'm not getting any generated code. > > > > And finally, the build fails with this message: > > > > xdoclet:ejbdoclet: > > > > [echo] Compiling to {my_path}/root/../TestingEjb/target/classes > > > > BUILD FAILED > > File...... > > {my_home}/.maven/plugins/maven-multiproject-plugin-1.3/plugin.jelly > > Element... maven:reactor > > Line...... 216 > > Column.... 9 > > Unable to obtain goal [multiproject:install-callback] -- > > {my_home}/.maven/ > > plugins/maven-java-plugin-1.4/plugin.jelly:53:48: <ant:javac> srcdir > > "{my_path}/TestingEjb/target/xdoclet/ejbdoclet" does not exist! > > > > Now, I've seen some people suggest that the XDoclet plugin > > is... lacking (in > > terms of documentation, I'd certainly agree). Perhaps I > > shouldn't be using it > > and should stick to the ant task style of running XDoclet? > > Are there any > > projects that I can examine where maven is building a bunch > > of EJBs for > > deployment on JBoss? I got the J2EE sample project off the > > Wiki, but that > > seems to require an EJB client project for each bean, and I > > don't see a good > > reason for it. > > > > Perhaps I'm posting to the wrong group and need to talk on > > the XDoclet user's > > list? > > > > Any help would be appreciated! > > > > Thanks, > > > > Mark > > > > > --------------------------------------------------------------------- > > 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] > > > > --------------------------------------------------------------------- > 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]
