Le sam. 14 août 2021 à 22:21, Enno Thieleke a
écrit :
> Ok, I feel like we're turning in circles here.
>
> If the feature I'm proposing exists already (without excludes and without
> the need for extra POMs and BOMs, i.e. the common solution), please post a
> link to the docs. If it doesn't exist
Ok, I feel like we're turning in circles here.
If the feature I'm proposing exists already (without excludes and without the
need for extra POMs and BOMs, i.e. the common solution), please post a link to
the docs. If it doesn't exist and people ask for it [1] (and have been for
years), then I d
Le sam. 14 août 2021 à 18:56, Enno Thieleke a
écrit :
> You're right. Currently, if I want to control my dependencies, I must
> resort to excludes and define the dependencies I really want myself. And
> putting something like that in one or two POMs and aggregating them in a
> BOM is very dirty i
You're right. Currently, if I want to control my dependencies, I must resort to
excludes and define the dependencies I really want myself. And putting
something like that in one or two POMs and aggregating them in a BOM is very
dirty in my opinion. Not only is it noisy/verbose when it comes to w
Le sam. 14 août 2021 à 16:52, Enno Thieleke a
écrit :
> You are right, the feature is mainly useful for transitive dependencies.
> That's my main motivation anyway.
>
> Consider the following:
> You have a dependency to something that depends on
> org.hibernate.javax.persistence:hibernate-jpa-2.2
You are right, the feature is mainly useful for transitive dependencies. That's
my main motivation anyway.
Consider the following:
You have a dependency to something that depends on
org.hibernate.javax.persistence:hibernate-jpa-2.2-api. You yourself or another
thing you depend on depends on jak
I don't really see it convenient at all. If you have to change the source
anyway, you can also fix the POM, that's much less confusing than having a
project using technology x but declaring to use technology y.
The only time I see dependency overwrites as somewhat useful if you want to
replace
Could you please elaborate on why a registry would be necessary? What kind of
registry are we talking about (what would its purpose be)?
Profiles should not be an issue since they should be merged into the model at a
very early stage, even before dependency management kicks in, right? Hence
the
Hi Bernd,
hopefully I understand you correctly: I'd expect the artifact (and its source
and javadoc attachment) to change, nothing more. The source would be left
untouched. It is not the responsibility of the dependency resolution
mechanism/engine to do anything else.
Just to make sure that we
Would you expect to only replace artifacts or also change the java source and
class files to actually change the used classes? Your cases are no simple
drop-in replace compatibility. Therefore I doubt a maven feature to do so is
any more useful than just blocking the deprecated artifacts.
Gruss
Le sam. 14 août 2021 à 13:24, Enno Thieleke a
écrit :
> So, you're saying that I can replace artifact coordinates with
> dependencyManagement.dependencies already? I'm not talking about versions,
> scopes and exclusions, I'm talking about groupIds and artifactIds. My idea
> is, simply put, if art
So, you're saying that I can replace artifact coordinates with
dependencyManagement.dependencies already? I'm not talking about versions,
scopes and exclusions, I'm talking about groupIds and artifactIds. My idea is,
simply put, if artifact commons-logging:commons-logging is found,
org.slf4j:jc
michael-o merged pull request #251:
URL: https://github.com/apache/maven-site/pull/251
--
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: dev-unsubsc
The Apache Maven team is pleased to announce the release of the Apache
Maven 3.8.2
Apache Maven is a software project management and comprehension tool.
Based on the concept
of a project object model (POM), Maven can manage a project's build,
reporting and documentation
from a central piece o
14 matches
Mail list logo
