Re: [DISCUSS] New goal for install/deploy plugin?

Then I guess the new deploy logic is wrong since it does not enable to use the mojo as a mojo (outside a predefined lifecycle which is against mojo design) so should be relaxed (reverted?). Romain Manni-Bucau @rmannibucau | Blog

Re: Test problem at head: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:unpack (unpack-classes) on project plexus-utils: Artifact has not been packaged yet.

Just curious, why is such an old version of maven-dependency-plugin used in that build? - Eric L On Sat, Feb 25, 2023 at 2:46 PM Elliotte Rusty Harold wrote: > On Sat, Feb 25, 2023 at 11:46 AM Guillaume Nodet > wrote: > > > > Which goal are you running ? > > I think you need to run the

Re: [HEADS UP] Maven Release 3.9.1 coming soon

Howdy, I may be late, sorry about that, but few days ago pulled this page from archive org (was hosted and lost on codehaus confluence): https://cwiki.apache.org/confluence/display/MAVEN/Versioning As based on this page was Maven3 versioning implemented, at least according to this page:

Re: [HEADS UP] Maven Release 3.9.1 coming soon

After further investigation I'm willing to state that MNG-7701 is invalid, and I closed it. MNG-7700 is mostly invalid. There's a bit of a glitch around the "canonical representation" of version strings of the form 0.x that does not affect comparisons. However, nowhere do we define or promise

Re: Test problem at head: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:unpack (unpack-classes) on project plexus-utils: Artifact has not been packaged yet.

On Sat, Feb 25, 2023 at 11:46 AM Guillaume Nodet wrote: > > Which goal are you running ? > I think you need to run the package phase as hinted by the error. > mvn test also mvn compile; mvn test mvn clean test mvn package; mvn test All end with the same failure. This seems to be a regression

Re: [DISCUSS] New goal for install/deploy plugin?

I dislike the idea to "toggle logic". This way, we would have 3 mojos with 3 different logic. Is simpler to understand, that invoke same mojo to do this or that, based on toggle. T On Sat, Feb 25, 2023, 13:18 Romain Manni-Bucau wrote: > Hi, > > Maybe I missed some details but n unsafe toggle

Re: [DISCUSS] New goal for install/deploy plugin?

Hi, Maybe I missed some details but n unsafe toggle (parameter) to deploy sounds like a good compromise to me. Too much overlapping goals sounds weird and hard to understand. Le sam. 25 févr. 2023 à 12:39, Tamás Cservenák a écrit : > Howdy, > > Here is this thread: >

Re: Test problem at head: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:unpack (unpack-classes) on project plexus-utils: Artifact has not been packaged yet.

Which goal are you running ? I think you need to run the package phase as hinted by the error. Le sam. 25 févr. 2023 à 07:58, Elliotte Rusty Harold a écrit : > FYI, maven core tests fail for me (Java 1.8. Maven 3.8.7) when > building at head like so. I'm not sure what to do about this: > >

[DISCUSS] New goal for install/deploy plugin?

Howdy, Here is this thread: https://lists.apache.org/thread/lbbd5n92xjksyf53mlf12togxrvdbvhl In short, user is _partially_ building a module, and invokes deploy:deploy, that now fails, as since 3.x version of install/deploy, there is a "safety check" in these mojos, to not deploy partially (here