Bind dependency:copy to an execution and just specify all the artifactItems in the execution.
On Monday 30 November 2015, David Hoffer <[email protected]> wrote: > Yeah that is what I ended up doing but would rather have gotten the files > from Maven at build time instead of just adding manually to SVN...just > feels wrong...plus what I really would like is the ability to get later > jars every time the build runs if any new ones exist. I know it might seem > like an odd use case and it is but we have found cases in production where > the version in the classpath won't work due to 3rd party runtime production > issues and at the production site it's not an option to just download a new > jar. > > -Dave > > On Mon, Nov 30, 2015 at 2:13 PM, Ron Wheeler < > [email protected] <javascript:;> > > wrote: > > > So these are not project dependencies since only 1 version is allowed as > a > > dependency and are not on the classpath since only 1 version is used > there > > as well. > > > > As I read your description, you want to include a bunch of jars in a > > resource folder that is not on the classpath of the assembled zip. > > > > Since they are immutable, why would you not just download the stuff that > > you want once and put it in the folder and include the folder in the zip? > > > > Ron > > > > > > > > On 30/11/2015 3:54 PM, David Hoffer wrote: > > > >> I have a use case where I want to include in a subfolder of my assembled > >> zip all of the versions of a particular artifact (or even better all > >> within > >> a range of versions). > >> > >> What's the best way to do this? > >> > >> -Dave > >> > >> > > > > -- > > Ron Wheeler > > President > > Artifact Software Inc > > email: [email protected] <javascript:;> > > skype: ronaldmwheeler > > phone: 866-970-2435, ext 102 > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > <javascript:;> > > For additional commands, e-mail: [email protected] > <javascript:;> > > > > > -- Sent from my phone
