[
http://jira.codehaus.org/browse/MNG-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205175#action_205175
]
John Dunlap edited comment on MNG-1755 at 1/5/10 10:36 AM:
-----------------------------------------------------------
I was about to create a feature request for a <developerManagement> tag but
decided to first search for the tag name. The fact that there was already an
open feature request for it suggests, at least to me, that it is an (at least
from a developer's perspective) an intuitive extension to maven.
Having said that, I really like Joerg's idea of <teamManagement> better than my
own idea as it is better thought out a more complete solution to nearly
identical problems. I cast my vote for <teamManagement> instead of
<developerManagement>.
If this is implemented, it would be helpful if maven raised an error, or at
least a warning, when the id of the team member cannot be found. That way we
know that we have to update team memberships in child projects as they move to
newer versions of the parent pom.
was (Author: john.dunlap):
I was about to create a feature request for a <developerManagement> tag but
decided to first search for the tag name. The fact that there was already an
open feature request for it suggests, at least to me, that it is an (at least
from a developer's perspective) an intuitive extension to maven.
Having said that, I really like Joerg's idea of <teamManagement> better than my
own idea as it is better thought out a more complete solution to nearly
identical problems. I cast my vote for <teamManagement> instead of
<developerManagement>. If this is implemented, it would be helpful if maven
raised an error, or at least a warning, when the id of the team member cannot
be found. That way we know that we have to update team memberships in child
projects as they move to newer versions of the parent pom.
> Improve support for <developers> in reactor builds
> --------------------------------------------------
>
> Key: MNG-1755
> URL: http://jira.codehaus.org/browse/MNG-1755
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: POM
> Reporter: Mike Perham
> Fix For: 3.x
>
>
> I would like to see something like <developerManagement> added which acts
> similarly to the other management elements in the POM. This would allow a
> top-level project POM to list all the developers, their orgs, timezones,
> emails, etc and child projects to reference just the ID and the developers
> role in that module. Something like this:
> parent's pom.xml:
> <developerManagement>
> <developer>
> <id>msanchez</id>
> <name>Matt Sanchez</name>
> <email>[email protected]</email>
> <url>http://priori.webify.local:9090/display/~msanchez</url>
> <timezone>-6</timezone>
> </developer>
> <developer>
> <id>mperham</id>
> <name>Mike Perham</name>
> <email>[email protected]</email>
> <url>http://priori:9090/display/~mperham</url>
> <timezone>-6</timezone>
> </developer>
> </developerManagement>
> foo's pom.xml:
> <developers>
> <developer>
> <id>mperham</id>
> <roles>
> <role>Owner</role>
> </roles>
> </developer>
> </developers>
> Our management wants to have one or two clear-cut owners for each module and
> we would like to use maven to document those owners but the current impl is
> terribly redundant since developers are not inherited.
--
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
