You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@excalibur.apache.org by "Robert Burrell Donkin (JIRA)" <de...@excalibur.apache.org> on 2009/07/10 17:51:14 UTC
[jira] Reopened: (EXLBR-38) Split Parent And Aggregation poms
[ https://issues.apache.org/jira/browse/EXLBR-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin reopened EXLBR-38:
----------------------------------------
Turns out components are used more widely by containerkey etc
> Split Parent And Aggregation poms
> ---------------------------------
>
> Key: EXLBR-38
> URL: https://issues.apache.org/jira/browse/EXLBR-38
> Project: Excalibur Components
> Issue Type: Improvement
> Components: Build
> Affects Versions: 2.2
> Reporter: Robert Burrell Donkin
> Fix For: 2.2
>
>
> I find that multi-module projects are easier to manage when the inheritance pom and the aggregation pom are separate. ATM some modules use excalibur (the aggregation pom) and some excalibur-parent. Switching all to use excalibur-parent would consolidate inheritance and split it from the aggregation hierarchy.
> Opinions?
> Objections?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org