[ http://jira.codehaus.org/browse/CONTINUUM-782?page=comments#action_71184 ] Milos Kleint commented on CONTINUUM-782: ----------------------------------------
actually the suggested workaround with -Dmaven.repo.local doesn't work, at least not on the continnum instance at codehaus. My build fails whenever I try to put a relative path. What I would like to achieve is a "clean" build for my project. 1. have a local repository that gets clean everytime 2. have a local repository that is private to my project (set of projects) and doesn't interfere with other projects running on the same continuum instance 2a. by project I mean something like mevenide which consists of multiple modules but I want it to build all at once I always do a clean build of mevenide prior to commit and commit everything, the major feature of a continuum server for me is to check if my project is buildable with a given set of remote repositories, as cross pollination of my local repository is a common source of problems for me. > Add a feature to allow cleaning the m2 local repo once every N days > ------------------------------------------------------------------- > > Key: CONTINUUM-782 > URL: http://jira.codehaus.org/browse/CONTINUUM-782 > Project: Continuum > Issue Type: New Feature > Components: Core system > Affects Versions: 1.0.3 > Reporter: Vincent Massol > > It's really hard with maven to know if your build is working or not. I've > been hit several times already by buillds working fine locally and on the CIs > but failing for a newcomer trying to build that project. The reason is that > remote repos are not immutable and artifacts can disappear or be modified in > there. > It would be nice if continnuum could help notice when this happen. A way to > implement this would to be to configure Continuum to clean its local repo > every N days. -- 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
