[
http://jira.codehaus.org/browse/CONTINUUM-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Catherine Tan updated CONTINUUM-782:
------------------------------------------
Attachment: continuum-purge-07242008.patch
Found some more issues with my patch so I have attached
*continuum-purge-07242008.patch* that fixes those issues.
1. added continuum-configuration.xml in src/test/resources of continuum-purge
module ( for revision 678639 )
2. refactored packages to org.apache.continuum
3. fixed some purging tests
4. added creation of default m2 local repository during continuum
initialization
5. set default project group's local repository to #4
6. fixed repository used when releasing and deploying
7. set project group's local repository to #4 when adding a new maven 2
project whose project group is set to "defined by pom"
8. will not be able to edit/remove the default local repository
9. changed archiva version to 1.1
> 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
> Fix For: 1.2
>
> Attachments: continuum-purge-07242008.patch,
> CONTINUUM-purge-docs.patch, CONTINUUM-purge-newer.patch,
> CONTINUUM-purge.patch, documentation-images.zip, purge-images.zip
>
>
> 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
