Howdy, Maven (3 or 4) by default does "nothing" if dependency with type=zip is declared (as it has no dedicated "artifact handler", a component describing "what" should happen with dependency). Hence, as stated in the issue, the "default" artifact handler kicks in, and it will not be added to classpath.
I understand both parties (pro and con), but also Joerg asks "how to stop it happening (once it is made to happen)". As this use case was many times asked for, I went to create Zippy: https://github.com/maveniverse/zippy/releases/tag/release-0.1.0 You can add this extension to your project and achieve the behaviour you want. Read carefully the release notes, as extensions (unlike dependencies) are NOT transitive ;) HTH T On Fri, Apr 18, 2025 at 9:36 AM Olivier Cailloux <olivier.caill...@gmail.com> wrote: > > Dear list, > > I have read https://issues.apache.org/jira/browse/MNG-5567 but did not > manage to understand whether the issue has supposedly been solved or > even whether it is consensual that it should be solved. One person (who > seems to be, or was at the time, a Maven developer?) seems to argue > that it should, but other voices seem to be opposed to it. > > I just lost hours trying to understand why my (zip) dependency was not > reachable from my code, then thought that my IDE was at fault, and > finally realized that Maven itself does not seem to include zip types > in the classpath. > > I want to raise my support for fixing this: there is clearly a natural > expectation for this to work, considering that java accepts zip files > as dependencies. > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
