On Wed, 12 Feb 2025 at 22:20, Gary Gregory <garydgreg...@gmail.com> wrote: > > On Wed, Feb 12, 2025, 17:16 Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > > > On Wed, Feb 12, 2025, 09:57 sebb <seb...@gmail.com> wrote: > > > >> On Wed, 12 Feb 2025 at 14:07, Gary Gregory <garydgreg...@gmail.com> > >> wrote: > >> > > >> > Hi All, > >> > > >> > I always use dependency:tree, that always works for me. > >> > >> But have you tried it on weaver? > >> (without previously doing an install) > > > > > I didn't for me, crud. I've got to say that multi-module builds can be > quite a challenge and I often find myself just doing installs just to move > the ball forward.
AFAICT the same problem does not apply to VFS, which is a multi-module project. I would like to establish whether weaver really does need to be installed before the dependency check can work, or whether there is a bug in the setup. Or maybe it's because weaver has a maven module? Maybe I need to ask on a Maven mailing list. > Gary > > > >> > At some point someone set up Jenkins jobs for some of the Commons > >> > components to publish snapshots, but I never look at Jenkins, I find it > >> > unreliable with the regular git errors it seems to throw. I rely on > >> GitHub, > >> > that's rock solid. > >> > >> Jenkins already has the karma to publish snapshots, but I agree it's > >> harder to use. > >> > >> > Otherwise I push snapshots after I make a change I feel is worth > >> pushing. I > >> > just pushed weaver to see if it would help.sure. it blew up the module > >> > samples/pom.xml so there is some modernizing to do. > >> > > >> > It's possible to setup GH to push snapshots but that requires setting up > >> > secrets and makes the workflows more complex. I think infra might need > >> to > >> > get involved for the secrets part, not aure. > >> > >> My point is that it should not be necessary to publish or install > >> snapshots merely to extract dependencies within a project. > >> Further, if publication/installation is needed, then one cannot rely > >> 100% on the output: the poms might have changed since last push. > >> > >> > Gary > >> > > >> > > >> > On Wed, Feb 12, 2025, 08:37 Eric Bresie <ebre...@gmail.com> wrote: > >> > > >> > > Is this saying that not every commons artifact (1) is available in the > >> > > snapshot repo (2)? > >> > > > >> > > Why would some be in the snapshot repo and others not? Are each of > >> the > >> > > given just not setup to publish snapshots? > >> > > > >> > > > >> > > 1. https://repo1.maven.org/maven2/org/apache/commons/ > >> > > 2. https://repository.apache.org/content/groups/snapshots/ > >> > > > >> > > Get Outlook for iOS<https://aka.ms/o0ukef> > >> > > ________________________________ > >> > > From: Elliotte Rusty Harold <elh...@ibiblio.org> > >> > > Sent: Wednesday, February 12, 2025 7:23:16 AM > >> > > To: Commons Developers List <dev@commons.apache.org> > >> > > Subject: Re: [ALL] Maven module expert needed please > >> > > > >> > > On Wed, Feb 12, 2025 at 12:27 AM sebb <seb...@gmail.com> wrote: > >> > > > >> > > > org.apache.commons:commons-weaver-processor:jar:2.1-SNAPSHOT > >> > > > > >> > > > Note that the component is currently at version 2.1-SNAPSHOT. > >> > > > > >> > > > Surely it should not be necessary to build and install the component > >> > > > in order to list its dependencies? > >> > > > Or am I missing something here? > >> > > > >> > > > >> > > Yes, it is necessary to build and install the component you depend on. > >> > > mvn dependency:list is reading dependencies from the maven repository, > >> > > not from the source code. If you haven't installed > >> > > org.apache.commons:commons-weaver-processor:jar:2.1-SNAPSHOT locally > >> > > and it's not available in the central repo (and it probably isn't) > >> > > then Maven can't find it. > >> > > > >> > > The retry resolution can interfere once it's not found, even if you've > >> > > since installed it. There's a flag somewhere whose exact syntax I > >> > > forget to force a retry. > >> > > > >> > > -- > >> > > Elliotte Rusty Harold > >> > > elh...@ibiblio.org > >> > > > >> > > --------------------------------------------------------------------- > >> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> > > For additional commands, e-mail: dev-h...@commons.apache.org > >> > > > >> > > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
