Re: Keeping dependency out of all classpaths

ot;ALL zip MUST be on the classpath", it just says "THOSE zips that you WANT to consume by the compiler must be on the classpath". This is a huge difference! -Markus -Ursprüngliche Nachricht- Von: Tamás Cservenák Gesendet: Freitag, 10. Juni 2022 13:53 An: Maven Users List Bet

AW: Keeping dependency out of all classpaths

Gesendet: Freitag, 10. Juni 2022 13:53 An: Maven Users List Betreff: Re: Keeping dependency out of all classpaths So let's enumerate what we have so far: - the ZIP is built in same multi module build, and is "intentionally incompatible" - the ZIP should be a dependency of WAR module,

Re: Keeping dependency out of all classpaths

ervenák > Gesendet: Freitag, 10. Juni 2022 13:15 > An: Maven Users List > Betreff: Re: Keeping dependency out of all classpaths > > Well, shoot in the dark: why is this ZIP a _dependency_ in the first place? > As you say "they solely serve as an input to third party

AW: Keeping dependency out of all classpaths

, 10. Juni 2022 13:15 An: Maven Users List Betreff: Re: Keeping dependency out of all classpaths Well, shoot in the dark: why is this ZIP a _dependency_ in the first place? As you say "they solely serve as an input to third party plugins (not dealing with Java at all)". If so, ma

Re: Keeping dependency out of all classpaths

he > classpath, but how to keep a specific one one still? > > -Ursprüngliche Nachricht- > Von: Tamás Cservenák > Gesendet: Freitag, 10. Juni 2022 12:13 > An: Maven Users List > Betreff: Re: Keeping dependency out of all classpaths > > If you can use Maven4, try out

Re: Keeping dependency out of all classpaths

ld go with runtime scope), but what I want to reach is that >>> we find a consensus how a clean and generic solution should look like -- >>> and propose that solution to the Maven team.  >>> >>> Thanks! >>> -Markus >>> >>> >>>

AW: Keeping dependency out of all classpaths

classpath, but how to keep a specific one one still? -Ursprüngliche Nachricht- Von: Tamás Cservenák Gesendet: Freitag, 10. Juni 2022 12:13 An: Maven Users List Betreff: Re: Keeping dependency out of all classpaths If you can use Maven4, try out this one: https://github.com/apache/maven/pull

Re: Keeping dependency out of all classpaths

to reach is that >> we find a consensus how a clean and generic solution should look like -- >> and propose that solution to the Maven team.  >> >> Thanks! >> -Markus >> >> >> -Ursprüngliche Nachricht- >> Von: Tamás Cservenák >>

AW: Keeping dependency out of all classpaths

Nachricht- Von: Tamás Cservenák Gesendet: Freitag, 10. Juni 2022 12:01 An: Maven Users List Betreff: Re: Keeping dependency out of all classpaths I see. Well, as long as oracle Java doco says this: Class paths to the JAR, zip or class files. Each class path should end with a file name

Re: Keeping dependency out of all classpaths

0. Juni 2022 11:13 > An: Maven Users List > Betreff: Re: Keeping dependency out of all classpaths > > Howdy, > > just a quick idea: introduce your own packaging "quipsy-zip"? (yes, you'd > need your extension to be added to build, but it's worth it, trust me). &

AW: Keeping dependency out of all classpaths

2022 11:13 An: Maven Users List Betreff: Re: Keeping dependency out of all classpaths Howdy, just a quick idea: introduce your own packaging "quipsy-zip"? (yes, you'd need your extension to be added to build, but it's worth it, trust me). Look here: https://github.com/apache/maven/b

Re: Keeping dependency out of all classpaths

Howdy, just a quick idea: introduce your own packaging "quipsy-zip"? (yes, you'd need your extension to be added to build, but it's worth it, trust me). Look here: https://github.com/apache/maven/blob/master/maven-artifact/src/main/java/org/apache/maven/artifact/handler/ArtifactHandler.java#L58

Keeping dependency out of all classpaths

How can I keep a dependency out of all classpaths? I do have a dependency in my project that produces a ZIP full of resources. None of those resources is actually of any use for the Java compiler; they solely serve as an input to third party plugins (not dealing with Java at all).