Thanks for the reply Colin. Very useful information. By using xdoclet directly in maven.xml, are you referring to something like what this user's Xdoclet/Maven experience lead him to do?: http://orinoco.flamefew.net/moatas/archives/000115.html
I have no experience working with the Maven.xml and the property file is already looking painful. Regards, RC -----Original Message----- From: Colin Sampaleanu [mailto:[EMAIL PROTECTED]] Sent: January 31, 2003 3:41 PM To: Turbine Maven Users List Subject: Re: Xdoclet plugin: No goal [xdoclet:ejbdoclet] You need to actually add the xdoclet plugin to your maven home plugin directory. Maven doesn't come with it. You can try the one from the the xdoclet 1.2 beta 2. However, if you are using maven CVS head, I would recommend actually building xdoclet against that. If you do do that, not that the plugin will then have dependencies on 1.3b2, which you will have to satisfy yourself (ie they are not on ibiblio). Having now used the xdoclet plugin and then gone back to just using xdoclet directly (in maven.xml), I would however advise you that as currently implemented the plugin doesn't really buy you almost anything, and I find it more painful to use actually; it takes very simple xml hierarchichal ant tasks and makes you specify them as flat properties in a prop file. Sure, there are a number of defaults, but if you want to change anything, it is actually more work. The other thing to watch out for there is that some of the properties are exposed under the wrong name (I filed a bug in the xdoclet Jira for this), and the only way you can really find out is by doing a compare to the xdoclet plugin's jelly file. In general, this is a problem with the whole property file approach to setting properties. If you have an xml document xdoclet can validate if something is missing, and doesn't care about case on attributes, but if you go the properties in a property file route, a mismatch (wrong name or wrong case) will be silently ignored. All you really need to do is add a pregoal to java:compile, dump in your existing ant built file's ejbdoclet section, and away you go (obviously you'll have to take care of paths). The other thing you do want to do is add the generated source to the compile path, as follows: <path id="ejbdoclet.java.compile.src.set" location="${generated.java.dir}"/> <maven:addPath id="maven.compile.src.set" refid="ejbdoclet.java.compile.src.set"/> Perhaps I will write a genral email on this, to save other people time. Roland Chan wrote: >Hey gang, > >Relatively new to Maven, but have experience with XDoclet.. > >I'm having difficulties getting the XDoclet plugin to work. I keep >receiving a No goal [xdoclet:ejbdoclet] error when trying to run >java:jar. > >My dependencies look like this: > > <dependencies> > <dependency> > <id>xdoclet+xdoclet-module</id> > <version>1.2b2</version> > </dependency> > <dependency> > <id>xdoclet+ejb-module</id> > <version>1.2b2</version> > </dependency> > <dependency> > <id>xdoclet+jboss-module</id> > <version>1.2b2</version> > </dependency> > <dependency> > <id>xdoclet+web-module</id> > <version>1.2b2</version> > </dependency> > <dependency> > <id>ejb</id> > <jar>ejb.jar</jar> > <version>2.0</version> > </dependency> > <dependency> > <id>commons-logging</id> > <version>1.1-dev</version> > </dependency> > <dependency> > <id>log4j</id> > <version>1.2.6</version> > </dependency> > </dependencies> > >And my maven.xml and project.properties came straight off the web site. > >Any ideas why this might be happening?? > >Thanks, >RC > > > > > --------------------------------------------------------------------- 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]
