Hi Aslak
I have one more remark regarding compilation path in Maven.
In my opinion it would be even better if an update of compilation path is
separated from xdoclet target(s).
Simply if I want to start XDoclet from time to time and perform java
compilation more often.
In this case it is still required to make update of compilation path
manually.
I would like to have possibility of invoking a target like:
"xdoclet:updateCompilationPath" which will do the job for me wherever I
need.
It can look like:
(I am not proffcient in jelly so I beg your pardon about syntax)
<goal name="xdoclet:udateCompilationPath">
<j:if test="$maven.xdoclet.ejbdoclet.updateCompilationPath=true"> //this
is false by default
<path id="ejbdoclet.java.compile.src.set"
location="${maven.build.dir}/xdoclet/ejbdoclet"/>
<maven:addPath id="maven.compile.src.set"
refid="ejbdoclet.java.compile.src.set"/>
</j:if>
<j:if test="$maven.xdoclet.webdoclet.updateCompilationPath=true">
<path id="webdoclet.java.compile.src.set"
location="${maven.build.dir}/xdoclet/webdoclet"/>
<maven:addPath id="maven.compile.src.set"
refid="webdoclet.java.compile.src.set"/>
</j:if>
... and so on
<goal>
This separation can give user a choice if he needs to have compilation path
updated or not
E.g I could have targets like those then:
<goal name="component"
prereqs="clean,xdoclet:ejbdoclet,xdoclet:updateCompliationPath,ejb:install">
and
<goal name="fast_component"
prereqs="xdoclet:updateCompilationPath,ejb:install">
Michal
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 17, 2002 4:46 PM
> To: Michal Maczka
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Xdoclet-devel] Maven issue compilation path issue
>
>
> That's noted. Thanks for the tip.
>
> Aslak
>
> ----- Original Message -----
> From: Michal Maczka <[EMAIL PROTECTED]>
> Date: Tuesday, December 17, 2002 3:57 pm
> Subject: [Xdoclet-devel] Maven issue compilation path issue
>
> > In new maven plugin there is a strategy to update compilation path
> > automatically.
> >
> > E.g.:
> >
> > <!--
> > In order to make it easier for the user of the XDoclet
> > plugin, we
> > automatically add the
> > destination folder to the compile path. This way, people
> > don't have
> > to deal with maven:addPath in their own
> > maven.xml scripts. This has been tested with Maven from
> > CVS HEAD on
> > 2002.12.15. (AH)
> > -->
> > <path id="ejbdoclet.java.compile.src.set"
> > location="${maven.build.dir}/xdoclet/ejbdoclet"/>
> > <maven:addPath id="maven.compile.src.set"
> > refid="ejbdoclet.java.compile.src.set"/>
> >
> >
> > I like this approach. Only remark : I propose to use
> properties like:
> >
> > maven.xdoclet.ejbdoclet.destDir instead of
> > ${maven.build.dir}/xdoclet/ejbdoclet"
> >
> > Michal
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:
> > With Great Power, Comes Great Responsibility
> > Learn to use your power at OSDN's High Performance Computing Channel
> > http://hpc.devchannel.org/
> > _______________________________________________
> > Xdoclet-devel mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Xdoclet-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
>
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
