Hi Jörg,
Am 21.12.18 um 18:51 schrieb Jörg Schaible:
Actually you may be faced in future with stripped POMs in the repositories,
because Maven will separate
between build time information and runtime information. Only the latter is
required in the repo. And profiles
are meant to be build time.
There are a couple of things happening here.
1. dependencies are checked even though they are downloaded
This ensures that the build doesn't rely on *your* *local* repository. At
any time anybody should be able to build the project, it even should be
possible that you remove your own local re
On Fri, 21 Dec 2018 17:50:42 +0100 Tibor Digana wrote:
> I had a discussion with Robert about inheritable profiles.
Actually, they are inherited, but just the declaration. The activation is based
on the conditions of the current
(sub)project.
> As Robert said, this would introduce new issues a
I had a discussion with Robert about inheritable profiles.
As Robert said, this would introduce new issues and bugs. Altering
dependencies is a bad sing in project my company really need it at least in
POM with packaging WAR and runtime scope.
Profiles are not inheritable. This is user unfriendly
Hi Mavenistas,
I was recently quite puzzled on why Maven is trying to download a
dependency already present in the local repository and I tracked it
down to this comment in EnhancedLocalRepositoryManager[1]:
"artifact downloaded from remote repository is accepted only
downloaded from request repos
Hi Mavenistas,
I was recently quite puzzled on why Maven is trying to download a
dependency already present in the local repository and I tracked it
down to this comment in EnhancedLocalRepositoryManager[1]:
"artifact downloaded from remote repository is accepted only
downloaded from request repos
