No, I don't think it will work. What you really need is a repository manager to cache things locally for you. That's the recommended solution any time you feel like you're going to be downloading components more than once...which is really in every instance.
On Wed, Sep 27, 2017 at 7:53 AM, Benedikt Ritter <brit...@apache.org> wrote: > Hello Brain, > > > Am 26.09.2017 um 23:10 schrieb Brian Fox <bri...@infinity.nu>: > > > > On Mon, Sep 25, 2017 at 2:10 PM, Benedikt Ritter <brit...@apache.org> > wrote: > > > >> Hello Brian, > >> > >>> Am 20.09.2017 um 23:16 schrieb Brian Fox <bri...@infinity.nu>: > >>> > >>> It's been a really long time, but I recall that there were issues > getting > >>> the dependencies of plugins bound to the lifecycle. This looks to be > the > >>> same problem. I think the documentation talked about a way to do this > >>> effectively. > >> > >> I’ve looked through the documentation of the dependency plugin, but I > can > >> not find anything about this. Do you recall where you found that > >> documentation? > >> > >> > > Ha no, since I wrote that goal 10 years ago I'm scratching the depth of > my > > memory. Maybe I just intended to describe it ;-) > > Thank you for your response. Maybe I’ll just give a little more context > about what I’m trying to achieve. Maybe I’m just doing the wrong thing: > > I have a CI Build in GitLab, where I want to define a job that downloads > all the artifacts which are needed for the different lifecycle phases and > plugin executions as well as all project dependencies. I only want to > download all the stuff once and then copy the artifacts between the build > stages. I thought this would be possible with dependency:go-offline so that > later steps can be run with mvn -o. > Am I missing something or is this simply not possible at the moment? > > Regards, > Benedikt > > > > > > >> Regards, > >> Benedikt > >> > >>> > >>> On Wed, Sep 20, 2017 at 4:48 PM, Benedikt Ritter <brit...@apache.org> > >> wrote: > >>> > >>>> Hi, > >>>> > >>>> as far as I understand it should be possible to call mvn > >>>> dependency:go-offline and from there on work in offline mode (mvn -o). > >>>> I’ve put a minimal example together [1] that demonstrates that this > >>>> currently does not work. Am I missing anything? > >>>> > >>>> Thank you! > >>>> Benedikt > >>>> > >>>> [1] https://github.com/britter/dependency-plugin-bug > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>>> For additional commands, e-mail: dev-h...@maven.apache.org > >>>> > >>>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
