[jira] Moved: (MNGSITE-117) Creating a company-wide POM

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNGSITE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann moved MNG-4743 to MNGSITE-117:
------------------------------------------------

           Complexity:   (was: Intermediate)
          Component/s:     (was: Documentation:  General)
    Affects Version/s:     (was: 2.2.1)
                  Key: MNGSITE-117  (was: MNG-4743)
              Project: Maven 2 Project Web Site  (was: Maven 2 & 3)

> Creating a company-wide POM
> ---------------------------
>
>                 Key: MNGSITE-117
>                 URL: http://jira.codehaus.org/browse/MNGSITE-117
>             Project: Maven 2 Project Web Site
>          Issue Type: Improvement
>            Reporter: Larry Singer
>            Priority: Minor
>
> http://maven.apache.org/guides/mini/guide-configuring-maven.html refers to "a company-wide parent pom.xml" but gives no guidance on creating one. There should at least be some documentation or example of this. The documentation needs to be linked from to the above URL.
> One of the big issues with a company wide POM is that it needs to contain a reference to a company-wide repository, but it needs to be in that repository. Therefore it is not possible to retrieve it until it is retrieved. A solution to this can be found at http://knol.google.com/k/emerson-farrugia/declaring-repositories-in-snapshot/2u2m6rp0ot3oc/1#
> An alternate solution would be a setting for a company repository in settings.xml.

-- 
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