Hi Konstantin,
Thanks a lot for the reply.
> Hmm, subproject b ejb jar will need also all the
> classes from subproject a - to be packaged together in
> ejb jar.
Yes, that's right - I handle this with a maven plugin stage which
merges the two EJB jar files together at the end.
> That's tricky. And extending olg ( 1.2 ) xdoclet will
> require you to
> dive deep in a lot of code.
Hmm. Thought so. My hope was I could define extra classes which the
valueobject subtask references but doesn't act upon.
I thought I could have something like this, in the properties file:
maven.xdoclet.ejbdoclet.fileset.0=true
maven.xdoclet.ejbdoclet.fileset.0.include=**/*.java
maven.xdoclet.ejbdoclet.valueobject.fileset.0=true
maven.xdoclet.ejbdoclet.valueobject.fileset.0.include=**/*.java
maven.xdoclet.ejbdoclet.valueobject.fileset.0.sourcedir=${path-to-subproject}/src/java
Meaning I need to define a separate XJavaDoc instance for valueobject,
to reference, if these properties are set.
Of course another option altogether is to drop CMP and move to Hibernate
:-)
The funny thing is that all other subtasks are happy having just the
.class files for this CMR - it is only the valueobject subtask which
requires the source code.
Cheers,
Colin
-------------------------------------------------------
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
