Jörg, I do appreciate that you are trying to help me. But in order to do so, it would be good to pay more attention before replying. Otherwise, you are wasting your energy and limited time, both of which I also highly appreciate.
Again: There is no inheritance. That should have been clear from my very first message, and I explained it again and again. I said *nothing* about parent and child anywhere in this thread and even made it clear again in my last message. That I need to repeat myself, trying to be more and more assertive about what I already said or need to correct you about things I never said, is simply a matter of trying to make you understand that what you think is my question is really not. That then you do not like my tone, because we are both wasting cycles, you trying to help me and me trying to help you stop chasing your tail, is regrettable, but how can I help you if you just do not listen? Again: There is a *single* project/module using a plugin. And I, as a plugin author am asking literally here, quoting the very subject of the thread: "Can a *plugin* permit a dependency override by the user setting a simple option?" No parent/child, just a plugin and its user. The user wants to override a default dependency version provided by a plugin, not by a parent. The term "override" does not imply parent and child POMs, even if you insist it does. The module using a plugin is not its child, it is just its user and wants to override the plugin's default. Sorry to the whole audience to repeat and paraphrase the same thing so many times. I just want to make sure it sticks this time, so nobody in this community wastes time trying to solve a problem I do not have. -- Alexander Kriegisch https://scrum-master.de Jörg Schaible schrieb am 08.02.2024 05:28 (GMT +07:00): > On Wednesday, 7. February 2024, 01:00:50 CET Alexander Kriegisch wrote: >> 3rd party parent? Are you maybe mixing up my questions about different >> topics? There is not parent POM involved here, it is about a plugin and an >> application using it. > > You talk about "override by the user" which implies some kind of inheritance, > at least > for me. > >> Very simple and straightforward. I even gave an >> example of what does not work for me but you say should. > > So strait forward: > > <plugin> > <groupId>org.acme</groupId> > <artifactId>xy-compiler-plugin</artifactId> > <version>1.2.3</version> > <dependencies> > <dependency> > <groupId>org.xy</groupId> > <artifactId>xy-compiler</artifactId> > <version>${xy.compilerVersion}</version> > </dependency> > </dependencies> > </plugin> > > ... somewhere in a child ... > > <properties> > <xy.compilerVersion>4.5</xy.compilerVersion> > </properties> > >> So does it? > > It does. If this is not, what you want, you will have to ask in a different > way, since Lasse > also understood your question the way I answered. > >> If you do not know, it is OK. But if you want to help, the ball >> is in your court now. A counter-example showing me how to do what you >> suggested right would be most welcome. > > Actually I don't like your tone and I get the impression that we waist each > other's time. > > So I'll shut up, > Jörg > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
