Ok, since other people seem against me on using multiple poms, I will spend some
more time trying to get everything working with profiles ;)
Then I will blame all of the maven community if there are bugs with my builds
later on :p
Andrew Williams wrote:
I would have thought that a combination o
I would have thought that a combination of classifiers and profiles
with a decent DependencyManagement should do it.
Make activating a profile at any level will change mydep-1.0 to
mydep-1.0-jdk1.4 thoughout the tree.
Of course you would need to be sure that the depManagement covered
every si
Basically the problem with using profiles is that it really complicates how the
transitive dependencies work. I have to make sure that the correct profiles are
activated throughout the dependency tree.
I added a comment about this to the jira issue:
http://jira.codehaus.org/browse/MNG-3150
Si
On 7 Sep 07, at 9:31 AM 7 Sep 07, Paul Gier wrote:
I submitted a small patch for this issue:
http://jira.codehaus.org/browse/MNG-3150
The basic idea of it is to be able to use alternate pom.xml files
in a multi-module project. Can someone with commit access take a
look at this? It would
I submitted a small patch for this issue:
http://jira.codehaus.org/browse/MNG-3150
The basic idea of it is to be able to use alternate pom.xml files in a
multi-module project. Can someone with commit access take a look at this? It
would really help with some of our projects if this can be add
