maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marilyn E. Sander (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MNG-2684) local repository can only be specified per user, not per build, which impacts scalability
Date Sat, 03 Feb 2007 06:01:44 GMT

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

Marilyn E. Sander updated MNG-2684:
-----------------------------------

    Attachment: repotest.gz

There are five test cases.  driver.sh is a bash script that  will run one testcase at a time.
 Each is a different method of specifying a local repository.   Each local repository is put
on /tmp.  (They are small).

> local repository can only be specified per user, not per build, which impacts scalability
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-2684
>                 URL: http://jira.codehaus.org/browse/MNG-2684
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Ant tasks
>    Affects Versions: 2.0.4
>         Environment: Linux
>            Reporter: Marilyn E. Sander
>         Attachments: repotest.gz
>
>
> Because the local repository can only be specified in the ~/.m2/settings.xml or ~/.m2/ant/settings.xml
file, there can be only one local repository per user per executing build.  Worst case, the
repository is on a mounted filesystem and thus the user can run only one build at a time.
 Best case, the repository is on the local machine, and the user can run one build per machine.
 This does not scale to an installation with large-capacity build servers, where one user
might run several builds of different products or releases simultaneously, with each build
using its own local repository.  This can be done with Maven alone, but not with Maven ant
tasks.
> I would like a mechanism for the ant tasks to pick up the local repository from a property,
an environment variable, or a file in the base directory for the build.  Even $M2_HOME/conf/settings.xml
would be acceptable, as we could jigger $M2_HOME so as to have a unique one for each build.
 Any mechanism would be suitable, as long as it would allow a unique local repostory for each
build.
> Feel free to lower this from major to minor if you do not agree with the impact. For
our shop it is a major inconvenience, and we are considering a major rewrite to our build
in order to avoid the ant tasks.  We really need to make good use of our build servers.

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

        

Mime
View raw message