Hi Marco,
I had a similar problem trying to use xdoclet-web via the maven plugin
as well. A solution I found by trawling the archives was a suggestion by
Kebin Hagel
(http://www.mail-archive.com/[EMAIL PROTECTED]/msg08201.html)
While I didn't follow his approach what I found was I needed to include every
xdoclet module in my project.xml dependencies. Now I have it working I suppose
I could go thru and comment out one module at time until it breaks to remove unneeded
modules but at this stage I'm not going to stuff with something that ain't broke :)
[a snippet from my project.xml]
<!-- jar files the project is dependent on -->
<dependencies>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-apache-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-java-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-jdo-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-jboss-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-jmx-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-hibernate-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-web-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xdoclet-xdoclet-module</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>xdoclet</groupId>
<artifactId>xjavadoc</artifactId>
<version>1.0.2</version>
</dependency>
<dependency>
<id>xdoclet+ejb+module</id>
<version>1.2</version>
</dependency>
<dependency>
<id>servletapi</id>
<version>2.3</version>
</dependency>
<dependency>
<id>jakarta-struts</id>
<version>1.1</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
<version>1.6.1</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>commons-collections</groupId>
<artifactId>commons-collections</artifactId>
<version>2.1</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>commons-digester</groupId>
<artifactId>commons-digester</artifactId>
<version>1.5</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>commons-fileupload</groupId>
<artifactId>commons-fileupload</artifactId>
<version>1.0</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>1.0.1</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.0.3</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>commons-validator</groupId>
<artifactId>commons-validator</artifactId>
<version>1.0.2</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
</dependencies>
Hope this helps
Robbe Stewart
> -----Original Message-----
> From: Robert Upshall [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 13 March 2004 2:07 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Xdoclet-user] all cmp/cmr fields must start with a lower
> case letter
>
>
> >On Wed, 2004-01-14 at 05:30, Adam L wrote:
> >> What you're missing is the bean semantics regarding
> property names with
> >> multiple upper case letters in a row.
> >>
> >> basically:
> >> pTblah <-- --> getPTblah
> >> PTblah <-- --> getPTblah
> >>
> >> So, change your property name from PTypeID, either by
> changing the name
> >> entirely, or by adding a lower case letter after the P.
> >>
> >>
> >> You'll find this same issue with every day reflection.
> >>
> >
> >Thanks. I already have managed that.
> >
> >Well, I changed it from PTypeId to PtypeId even semantically the 't'
> >letter should be uppercase.
> >
> >There is no big deal about this, however I think XDoclet should
> >transform always the first letter of the word to lowercase
> independent
> >of the 2nd word letter is uppercase or lowercase.
> >
> >getPTblah --> pTblah
> >getPtblah --> pTblah
> >getPtBlah --> ptBlah
> >
> >It makes more sense... for me.
> >
> >Regards,
> >Pedro Salazar.
> >--
> >-PS
> >
>
> I have also just encountered this prblem with getUId/setUId
> and I have to agree with Pedro, doesn't his approach follow
> the java naming scemantics correctly?
>
> Robert
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> xdoclet-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
