Greg,

For example, we recently converted the TrinoDB (
https://github.com/trinodb/trino) build, removed their use of "go offline"
So am just interested in any other patterns out there.

T

On Thu, Mar 21, 2024 at 9:40 PM Greg Chabala <greg.chab...@gmail.com> wrote:

> I do have an example at hand, though I am not sure I would advocate for it:
> https://blog.frankel.ch/faster-maven-builds/2/
>
> There are undoubtedly better ways to achieve the author's goals, but I'm
> not sure that's the fault of dependency:go-offline.
>
> On Thu, Mar 21, 2024 at 3:19 PM Tamás Cservenák <ta...@cservenak.net>
> wrote:
>
> > Greg,
> >
> > would like to see such a project, do you have any examples at hand?
> > Am sure there are much simpler/better/more correct ways to do the same
> > thing.
> >
> > T
> >
> > On Thu, Mar 21, 2024 at 9:15 PM Greg Chabala <greg.chab...@gmail.com>
> > wrote:
> >
> > > My understanding is dependency:go-offline is an effective way to
> > > pre-download plugins and dependencies, for instance if one is making
> some
> > > layer in a docker build container for later reuse.
> > >
> > > On Thu, Mar 21, 2024 at 2:54 PM Tamás Cservenák <ta...@cservenak.net>
> > > wrote:
> > >
> > > > Howdy,
> > > >
> > > > What is the use case of "go offline"?
> > > > That is yet another goal coming from "Maven2 era" and messes up your
> > > local
> > > > repository (wrt back tracing dependencies,
> > > > https://issues.apache.org/jira/browse/MNG-7619)
> > > > I mean, if you do a build (w/o tests, or skipping most time stealing
> > > > steps), like "dry build", why is that not an option?
> > > >
> > > > T
> > > >
> > > >
> > > > On Thu, Mar 21, 2024 at 8:45 PM Scott Kurz <scottk...@gmail.com>
> > wrote:
> > > >
> > > > > +1 to this list from Slawomir:
> > > > >
> > > > > - dependency:analyze /  dependency:analyze-only
> > > > > - dependency:copy
> > > > > - dependency:copy-dependencies
> > > > > - dependency:go-offline
> > > > > - dependency:list
> > > > > - dependency:tree
> > > > > - dependency:unpack
> > > > > - dependency:unpack-dependencies
> > > > >
> > > > > On Thu, Mar 21, 2024 at 2:56 PM Slawomir Jaranowski <
> > > > > s.jaranow...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi
> > > > > > I use:
> > > > > >
> > > > > > - dependency:analyze /  dependency:analyze-only
> > > > > > - dependency:copy
> > > > > > - dependency:copy-dependencies
> > > > > > - dependency:go-offline
> > > > > > - dependency:list
> > > > > > - dependency:tree
> > > > > > - dependency:unpack
> > > > > > - dependency:unpack-dependencies
> > > > > >
> > > > > >
> > > > > >
> > > > > > czw., 21 mar 2024 o 17:06 Tamás Cservenák <ta...@cservenak.net>
> > > > > > napisał(a):
> > > > > >
> > > > > > > Howdy,
> > > > > > >
> > > > > > > I'd would be interested in how users and devs are using
> > > > > > > maven-dependency-plugin:
> > > > > > > https://maven.apache.org/plugins/maven-dependency-plugin/
> > > > > > >
> > > > > > > I collected some basic questions I'd like to have answered (but
> > > feel
> > > > > free
> > > > > > > to add more info!):
> > > > > > > - which goals are "must have" for you
> > > > > > > - which goals are "I never touched" for you (or, "I really
> don't
> > > > need"
> > > > > or
> > > > > > > "never used" or "shrug")
> > > > > > > - what is missing?
> > > > > > >
> > > > > > > Thanks
> > > > > > > T
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sławomir Jaranowski
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to