bind an execution of maven-antrun-plugin to the generate-sources phase putting your generated sources in ${project.build.directory}/generated-sources/my-company/
then use buildhelper-maven-plugin (@mojo) to add additional source directory paths (you'll want to add ${project.build.directory}/generated-sources/my-company/) FYI The "Maven Way" is to put generated sources in ${project.build.directory}/generated-sources/____ where ____ is the name of the source code generator... some people cheat and replace the ${project.build.directory} with the hardcoded equivalent "target" but you will have a better more portable build if you use the property -Stephen P.S. Google is your friend if you have issues trying to implement the above On 23 February 2010 15:08, Kiran Kumar M <kirankum...@cybage.com> wrote: > Hi, > > I have requirement where to generate the source code by reading some > velocity files *.vm and *.yml . > > This has been achieved through ant target, since we are moving every > thing to maven, the sam thing need to be achieved through maven plugins > > Could you please help me on this > > > > Regards > > Kiran Kumar M > > > > > > > "Legal Disclaimer: This electronic message and all contents contain > information from Cybage Software Private Limited which may be privileged, > confidential, or otherwise protected from disclosure. The information is > intended to be for the addressee(s) only. If you are not an addressee, any > disclosure, copy, distribution, or use of the contents of this message is > strictly prohibited. If you have received this electronic message in error > please notify the sender by reply e-mail to and destroy the original message > and all copies. Cybage has taken every reasonable precaution to minimize the > risk of malicious content in the mail, but is not liable for any damage you > may sustain as a result of any malicious content in this e-mail. You should > carry out your own malicious content checks before opening the e-mail or > attachment." > www.cybage.com > > >