could also add it to the compiler plugin's source root directly by declaring the maven-compiler-plugin in the pom and setting compileSourceRoots in the pluign's configuration.
but that is potentially messy since you'll be overriding any others that might be set in that project...and not as clean as wrapping that generated java in a mojo, so bretts approach is definitely the better one...but in a pinch you might be able to get away with putting an entry in that compileSourceRoots list. jesse On 11/16/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > I'd recommend writing the plugin in Java and calling the Ant task > using the Java API, then add the source root. This would help to > encapsulate the functionality. > > - Brett > > On 11/17/05, Lee Meador <[EMAIL PROTECTED]> wrote: > > I've scanned the last couple of weeks' messages and I think I see what > > is happening. > > > > I have an ant task that generates java from a wsdl using Websphere 6.0's > > ant tasks to do so. It's similar to the Axis ones. > > > > I have it generate the java into target/generated-sources/java. > > > > The generated code doesn't get compiled when I do a > > > > mvn compile > > > > I think the problem is that generated-sources doesn't get added to the > > compileSourceRoots since they are being generated in ant. > > > > So ... can I run some useless plugin with no input and get the > > generated-sources added to the list of roots? Is there some other way to > > get it to look there? > > > > Thanks. > > > > -- Lee Meador > > > > > > --------------------------------------------------------------------- > > 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] > > -- jesse mcconnell
