I would add one bit of emphasis. If your goal is to build it and push the results, use the ant tasks or ivy.
On the other hand, any execution of 'ant' that works outside of maven should work inside of maven using antrun, so long as the dependencies of antrun expand the classpath to include *all of the components* that would be in your ant lib directory outside of maven. If you really have an example in which antrun, pointed at a build.xml, gets different results in this case, please make a SSCE and attach it to a jira for the antrun project. On Thu, Oct 27, 2011 at 8:43 AM, Wayne Fay <[email protected]> wrote: >> I have tried adding the ant jars to the maven project itself, but that >> yielded no results may be because the maven project does not compile any >> java files itself, it delegates the responsibility to Ant via AntRun. > > This is kind of a ridiculous way to build a project with Maven IMO. > >> This is jruby code that I downloaded as a zip and it compiles fine as a >> stand alone. The actual maven project itself doesn't compile any java >> classes, so, no ant dependencies for the maven project. I am trying to > unzip > > You should ask the JRuby folks for help with this since its their code that > you're working with. But don't be surprised when they say that they simply > do not support what you are trying to do since they officially use Ant for > builds: > https://github.com/jruby/jruby/wiki/DownloadAndBuildJRuby > >> missing when the ant build is triggered. So I tried adding the jars to >> plugin hoping that maven will serve these via antrun to ant build. I know >> there is a fallacy in understanding here but I am unable to see it. > > Do the practical thing and just build it with Ant directly. Then if you want > to push the resulting artifacts into a Maven repo etc, use the Maven Ant > Tasks to do so directly from Ant. Why are doing things the hard way? > > Wayne > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
