On Wed, 12 Feb 2025 at 13:26, Elliotte Rusty Harold <elh...@ibiblio.org> wrote: > > 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.
If that is possible: there may be errors that prevent installation. Obviously if one depends on an component from a separate project, it has to be already available, but I would expect Maven to be able to find components in the same project without needing it to be installed. > 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. Does this also affect testing? i.e. if you make a change to a module, and forget to install the updated copy, will testing use the outdated copy? Or does classpath resolution work differently? > 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
