rmannibucau commented on PR #12745:
URL: https://github.com/apache/maven/pull/12745#issuecomment-6753833589
@gnodet means api=compile, implementation=runtime for consumer but compile
for producer? So only goal is to avoid to have another pom?
The common (and good) practise is to have an API module and an
implementation module so downstream consumers can have the api in scope
provided and impl in scope runtime, is this a bypass of this rule?
Technically I think there is no point having api scope -> worse case just
rename implementation to something meaningful (`local-compile`).
Also a better solution sounds like enabling to explicit the consumer pom
scope in a new tag and drop these new aggregates? Sounds like a better solution
to that need to me.
```xml
<dependency>
<groupId>foo</>
<artifactId>bar</>
<scope consumer.override="runtime">compile</> <!-- or whatever syntax,
another tag etc -->
</dependency>
```
another ambiguity is the scope: the module, the full project, every
subreactors? I assume only the module is usable but makes a multimodule
project needing to redefine the same deps again and again so using a pivot
module? (it also avoids the conflict specific handling in the multimodule
project)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]