David Garnier <[EMAIL PROTECTED]> wrote on 22/09/2002
04:36:37 PM:
> le dim 22-09-2002 � 01:36, Ben Walding a �crit :
> > As I understand things, if I use the java plugin (java:compile) I can
> > only set the properties that are available to the plugin.
> > eg. maven.compile.debug etc
> >
> > Am I out of luck if I want the plugin to set the source (1.3 / 1.4)
> > parameter for the compile task. (I use assert (rightly or wrongly) and
> > my code won't compile unless I specify source="1.4" to the javac
task).
>
> Same problem here. I just went ahead and created two new properties in
> the javac task from the java:compile goal.
>
> <javac
> destdir="${maven.build.dest}"
> excludes="**/package.html"
> --> source="${dgarnier.java.source}"
> --> target="${dgarnier.java.target}"
> debug="${maven.compile.debug}"
> deprecation="${maven.compile.deprecation}"
> optimize="${maven.compile.optimize}">
> <src>
> <path refid="maven.compile.src.set"/>
> </src>
>
> Then I can set theses properties just like Maven's properties.
How about people start a list of things they'd like as optional parameters
for the java plugin...
source, target, fork, executable more?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
