You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/02 15:45:18 UTC
[jira] (MNG-4395) Module dependency profiles/templates/inheritance
for pom projects
[ https://jira.codehaus.org/browse/MNG-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-4395:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Module dependency profiles/templates/inheritance for pom projects
> -----------------------------------------------------------------
>
> Key: MNG-4395
> URL: https://jira.codehaus.org/browse/MNG-4395
> Project: Maven
> Issue Type: Wish
> Affects Versions: 2.2.1
> Reporter: Kristoffer Sjogren
>
> In our organization we have general definition of what a component means for us.
> For example, a general dependency definition of a component goes like this:
> - EAR (depends on all other projects within this component)
> - IF (no dependencies)
> - EJB (depends on interface project)
> - WAR (depends on interface AND ejb project)
> - RAR (depends on the interface project)
> There is also some other type of projects that are part of this definition but i have left them out here for brevity. This make our pom file very verbose.
> Since we have many components in our system and so we repeat ourselves alot and it's hard to maintain consistency through the system.
> It would be nice to be able to define some kind of template or profile centrally and inherit that for each "component".
> Cheers,
> -Kristoffer
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)