Hi Chris Thanks for replying. We like to use ant as our main build process, not maven so the maven-antrun wouldnt apply here.
On Wed, May 13, 2015 at 8:14 PM, Christopher <ctubb...@apache.org> wrote: > One maven plugin which might help is the > https://maven.apache.org/plugins/maven-antrun-plugin/ , which allows > you to execute ant tasks within maven. I've seen some projects do this > to "mavenize" an ant project a bit (though, usually they end up > transitioning completely... eventually). > > Another option is to have a small maven project inside your project > which has all your dependencies, and which executes the > copy-dependencies goal of the maven-dependency-plugin to copy all your > dependencies to a specified directory > ( > https://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html > ) > to make them available for ant. > > -- > Christopher L Tubbs II > http://gravatar.com/ctubbsii > > > On Wed, May 13, 2015 at 11:00 PM, Zk W <mpc8...@gmail.com> wrote: > > Hi All > > > > We are new to Maven and we are an ant shop. > > We like to use Maven's dependency management feature, not ivy. > > > > 1- Can we just use Maven's dependency management feature to work with our > > ant build script ? > > > > 2- Since .m2 is the default folder for all the jars, do we use ant copy > > task to copy jars from .m2 folder to different project folders to compile > > properly ? > > > > 3. Are there examples out there that use ant for build purpose in > > conjunction with maven's dependency management ? > > > > Thank you. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
