You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristoffer Sjogren (JIRA)" <ji...@codehaus.org> on 2009/10/14 17:48:26 UTC
[jira] Created: (MNG-4395) Module dependency
profiles/templates/inheritance for pom projects
Module dependency profiles/templates/inheritance for pom projects
-----------------------------------------------------------------
Key: MNG-4395
URL: http://jira.codehaus.org/browse/MNG-4395
Project: Maven 2
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira