lp me with ... wait!
> > >> Okay, I just read the pom.xml fragment you posted much more carefully.
> > >> Now I think I get it. The destination directory is not arbitrary!
> > >> Instead, you unpack the dependency exactly where maven intends to put
> &
, 29 Jul 2023 at 01:13, wrote:
> Nice catch!
>
> -Original Message-
> From: Nick Stolwijk
> Sent: Friday, July 28, 2023 7:10 PM
> To: Maven Users List
> Subject: Re: enforcing class path order using maven enforcer
>
>
> CAUTION: This email originated
Nice catch!
-Original Message-
From: Nick Stolwijk
Sent: Friday, July 28, 2023 7:10 PM
To: Maven Users List
Subject: Re: enforcing class path order using maven enforcer
CAUTION: This email originated from outside our organisation -
nick.stolw...@gmail.com Do not click on links, open
suggesting doing that as part of every build, instead
> of
> > once, statically?
> >
> > -Original Message-
> > From: Nick Stolwijk
> > Sent: Friday, July 28, 2023 6:40 PM
> > To: Maven Users List
> > Subject: Re: enforcing class path orde
to put
>> compiled class files.
>> Okay, wow. That is hacky. And seriously clever. Is this a standard
>> trick or did you think of this just now?
>>
>> Re: how long to support this: probably pretty long.
>>
>> -Original Message-
>> From: Ni
, wow. That is hacky. And seriously clever. Is this a standard
> trick or did you think of this just now?
>
> Re: how long to support this: probably pretty long.
>
> -Original Message-
> From: Nick Stolwijk
> Sent: Friday, July 28, 2023 6:47 PM
> To: Maven Users List
&
this: probably pretty long.
-Original Message-
From: Nick Stolwijk
Sent: Friday, July 28, 2023 6:47 PM
To: Maven Users List
Subject: Re: enforcing class path order using maven enforcer
CAUTION: This email originated from outside our organisation -
nick.stolw...@gmail.com Do not click on links
t: Friday, July 28, 2023 6:40 PM
> To: Maven Users List
> Subject: Re: enforcing class path order using maven enforcer
>
>
> CAUTION: This email originated from outside our organisation -
> nick.stolw...@gmail.com Do not click on links, open attachments, or
> respond unless yo
Oh, I see, you're suggesting doing that as part of every build, instead of
once, statically?
-Original Message-
From: Nick Stolwijk
Sent: Friday, July 28, 2023 6:40 PM
To: Maven Users List
Subject: Re: enforcing class path order using maven enforcer
CAUTION: This email originated
ell
> >
> >
> > On Fri, 28 Jul 2023 at 23:53,
> > wrote:
> >
> > > I'd like to clarify one point about why I care about order:
> > > I have a class name which clashes on purpose!
> > > That is, I have a third-party dependency from maven
e this issue.
> But they're also not backwards compatible with the version we're on.
>
> -Original Message-
> From: Nick Stolwijk
> Sent: Friday, July 28, 2023 6:10 PM
> To: Maven Users List
> Subject: Re: enforcing class path order using maven enforcer
>
>
>
rsions
> don't have this issue.
> But they're also not backwards compatible with the version we're on.
>
> -Original Message-
> From: Nick Stolwijk
> Sent: Friday, July 28, 2023 6:10 PM
> To: Maven Users List
> Subject: Re: enforcing class path order using maven enforce
sion we're on.
-Original Message-
From: Nick Stolwijk
Sent: Friday, July 28, 2023 6:10 PM
To: Maven Users List
Subject: Re: enforcing class path order using maven enforcer
CAUTION: This email originated from outside our organisation -
nick.stolw...@gmail.com Do not click on links, open a
up!
>
> -Original Message-
> From: Tamás Cservenák
> Sent: Friday, July 28, 2023 5:29 PM
> To: Maven Users List
> Subject: Re: enforcing class path order using maven enforcer
>
>
> CAUTION: This email originated from outside our organisation -
> ta...@cservenak.
As for IDEs, all those that try to "be caliph instead of caliph" (see
https://en.wikipedia.org/wiki/Iznogoud) IMHO are doing wrong.
Maven is Maven, everything else is just trying to be it. Good example of
IDE is Netbeans, an IDE that does not tries to reinvent things, and just
delegate to Maven
make sure that my version gets picked up!
-Original Message-
From: Tamás Cservenák
Sent: Friday, July 28, 2023 5:29 PM
To: Maven Users List
Subject: Re: enforcing class path order using maven enforcer
CAUTION: This email originated from outside our organisation -
ta...@cserve
Yup,
My "coinciding" work was not to fix people depending in cp ordering, but
was more related to my guts telling that "level order" (introduced in
experiment PR) is more correct than "pre order".
Latter may cause that your 3rd or 4th level transitive dep be enlisted on
CP before your 2nd first
Hi Tamás,
Thanks for the corrections! I was still in the belief that it wasn't
explicitly ordered, but it seems that changed in the years. I still think
it is easier to reason about your application if you don't depend on the
order of dependencies. I have always used the Enforcer plugin to at
Nick,
I have to correct you, as what you wrote is not true (anymore). But first,
I think this mail was on hold by moderator, as we had a same/similar
discussion already on this thread:
https://lists.apache.org/thread/16055md5s2d5fqch5t4vkn13j7czfybr
But in short:
- since 2.0.9 dependencies ARE
Hi Mark,
I don't think there is any guarantee for ordering in Maven. The
dependencies are not ordered, the plugins in the build section are not
ordered. I remember that with a Java upgrade the plugins were executed in a
different ordering due to a new implementation of HashMap. (Only the
plugins
20 matches
Mail list logo
