I think it's fine in the root pom. Again, the important bit is to have one just copy.
Paul Gier wrote:
We could merge it to the as parent pom in the root directory (where
it
was initially). But I wouldn't want to merge it with thirdparty because
the dependency information is used by the module poms. So for
mavenizing the rest of the app server build I want to have one place for
the dependency versions, and the pom has to be parent of the other poms.
They shouldn't get out of sync for version changes. But they do both
have to be updated for new dependencies or moved/renamed dependencies.
Dimitris Andreadis wrote:
> Can we merge the content of component-matrix/pom.xml to
> thirdparty/pom.xml ? What's the benefit of having them separate?
> They'll soon get out of sync.
>
> Paul Gier wrote:
>> I moved the maven component matrix into the app server directory
>> structure based on the discussion on the build forum:
>>
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=132452
>>
>> If it causes problems, please let me know.
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development