On Wed, Jun 12, 2019 at 1:04 AM Anders Hammar <and...@hammar.net> wrote:
> Having a dependency to some other scm repo is not a good approach. If that > changes your build could fail all of a sudden and you want consistency. > This is not true. The "big 3" VCSes each allow you to checkout a specific tag or revision if you like. If both projects (the dependent and the dependency) use the same VCS, then, at least in the cases of Git and SVN, you have a VCS-specific feature, e.g. Git subrepos or SVN externals, to work with the dependency's repo pretty seamlessly (though admittedly their use is controversial, but let's not go on a tangent about it :) ). > Your Maven project should typically be self contained. Any dependency > should be a Maven artifact (that is immutable). > It is certainly preferable to make one Maven project depend on another when possible, but keep in mind there are by necessity other kinds of dependencies too: The JDK, system-level libraries not provided by some JVMs, a SQL database, etc. You _can_ mavenize a lot of dependencies (like a SQL database project) and gain Maven's dependency management, but that is not invariably worth the cost of implementing and maintaining that mavenization. /Anders > > On Wed, Jun 12, 2019 at 7:50 AM Rajesh Deshpande < > rajesh.deshpa...@gmail.com> > wrote: > > > Hello, > > I have a maven project that builds Java jar files. I wan to run a python > > script as one of the goals in the verify phase. I am planning to use the > > ant run plugin for running the python script. The python script is stored > > in a separate repository that I would like to copy to my project root > > folder using maven. Is this possible? What's the best way to approach > this? > > > > Thanks! > > >
