It may be better to use maven:addPath rather than override maven.compile.src.set - not too sure of the implications, but have a look at the plugin.jelly for plugins that generate java source - eg. antlr, castor or xdoclet. They all have something like

   <ant:path id="some.reference.id" location="${some.generated.src.dir}"/>
   <maven:addPath id="maven.compile.src.set" refid="some.reference.id"/>

I've used this notation myself with some success.

cheers,


Matt



Keith Irwin wrote:


On Thu, 2004-01-08 at 18:17, Keith Irwin wrote:


On Thu, 2004-01-08 at 00:43, [EMAIL PROTECTED] wrote:



I gather one can circumvent this by modifying the appropriate property/variable in a preGoal
(like maven.compile.src.set), but that would add to the maintenance workload and really
it'd just be a hack.


For those of us who haven't been on the list long, where is this hack? I just grabbed some WSDL to generate classes and am in the same boat.




Nevermind:


       <preGoal name="java:compile">
               <ant:path id="maven.compile.src.set">
                       <ant:pathelement location="src/java"/>
                       <ant:pathelement location="src/generated"/>
               </ant:path>
       </preGoal>

seems to work.



Changing maven.compile.src.set didn't seem to do anything.

For those interested, a repeat?

Keith



So my question is; will support for multiple source directories in the POM ever be incuded, or
is it absolutely out of the question?


Regard, Jan-Helge


---------------------------------------------------------------------
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]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to