Hi together,
I looked into the problem again and if there is no way of limiting the
dependencies on a more aggregated level, I believe mixins are a really
important feature to look at. In my case, the parent pom with the
dependency management section and configuration already has about 2.5k
lines
It's not a perfect solution but look at placing dependencies in a separated POM
and pulling that POM in as a dependency using scope = import.
This mode is more compositional and mixin-like.
On Apr 1, 2010, at 8:56 AM, Mirko Jahn wrote:
Hi together,
I looked into the problem again and if
Yes, import scope can help with this.
We have a pom that declares the version of any dependency we MIGHT need. That
pom gets imported to control the versions. The actual project poms then
reference the dependencies they need to compile and run. When maven is building
the artifact that is
Well, that sounds promising! I'll give that a try and see how that can
help us managing our dependencies. Thanks a lot for the valuable
feedback!
Cheers,
Mirko
On Thu, Apr 1, 2010 at 3:55 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
Yes, import scope can help with this.
We have a pom
Hey there,
I am currently in the process of defining a pom hierarchy of a hugh
project, which was formally developed using Maven 1. As one of the
benefits we'd like to accomplish a grouping of dependencies / features
and configurations. On a first look profiles seemed promising, but the
lack of
Basing profile activation on a plugins is probably not the best idea. Are these
not based on the platform?
Probably best to state what you require, as people who tend to conflate their
solution with what they think is required tend to go down the wrong path.
Under what conditions exactly do
Hi Jason,
thanks for the fast reply. The requirements are somewhat common I
guess. We provide a development framework for eHealth applications
that depending on your module requirement needs various kinds of
dependencies added to your project pom.
Every user of our framework has to inherit one
