You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/02/07 01:11:02 UTC

[jira] Created: (MNG-119) sort out snapshot handling

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-119

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-119
    Summary: sort out snapshot handling
       Type: Bug

     Status: Unassigned
   Priority: Blocker

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-1

   Assignee: 
   Reporter: Brett Porter

    Created: Sun, 6 Feb 2005 7:09 PM
    Updated: Sun, 6 Feb 2005 7:09 PM

Description:
how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31311 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 9 hours
            Time Spent: 50400  (was: 18000)
    Remaining Estimate: 14400  (was: 25200)

1-4 implemented, however there is a bug with resolution that has forced me to comment it out.

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 14 hours
>         Remaining: 4 hours
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=comments#action_30825 ]
     
Brett Porter commented on MNG-119:
----------------------------------

so the plan here is not to introduce RELEASE or CURRENT as we have not been able to find a real use for it where you wouldn't specify the version explicitly.

SNAPSHOT will reference a small DB in the repository that will discover what the latest published version is.

If a <parent> version is not given, it will be assumed to be SNAPSHOT.

We will look at branches again later, but are looking at incorporating that into the USD.

If a POM with SNAPSHOT version is discovered in the reactor, then that project on disk will be used over anything in the repository.

This resolves issues with having to specify the parent version.

Releases will publish the POM with SNAPSHOTs resolved to their final identifiers in the parent and dependencies (though with user intervention to confirm - not automatically)

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Bug
>   Components: design
>     Reporter: Brett Porter
>     Assignee: Jason van Zyl
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31417 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 45 minutes
            Time Spent: 80100  (was: 77400)
    Remaining Estimate: 0  (was: 3600)

done all tasks

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 22 hours, 15 minutes
>         Remaining: 0 minutes
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31266 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 1 hour, 30 minutes
            Time Spent: 5400
    Remaining Estimate: 37800  (was: 43200)

design done - pulled in from all different sources and notes

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 1 hour, 30 minutes
>         Remaining: 10 hours, 30 minutes
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31283 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 1 hour, 30 minutes
            Time Spent: 12600  (was: 7200)
    Remaining Estimate: 30600  (was: 36000)

setup transformations and refactor some artifact code

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 3 hours, 30 minutes
>         Remaining: 8 hours, 30 minutes
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=history ]

Brett Porter reassigned MNG-119:
--------------------------------

    Assign To: Jason van Zyl

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Bug
>   Components: design
>     Reporter: Brett Porter
>     Assignee: Jason van Zyl
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-119) sort out snapshot handling

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Mon, 7 Feb 2005 8:45 PM
    Changes:
             Component changed to design
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MNG-119?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-119

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-119
    Summary: sort out snapshot handling
       Type: Bug

     Status: Unassigned
   Priority: Blocker

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
 Components: 
             design
   Fix Fors:
             1.0-alpha-1

   Assignee: 
   Reporter: Brett Porter

    Created: Sun, 6 Feb 2005 7:09 PM
    Updated: Mon, 7 Feb 2005 8:45 PM

Description:
how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=comments#action_31268 ]
     
Brett Porter commented on MNG-119:
----------------------------------

see also: http://docs.codehaus.org/pages/viewpage.action?pageId=22585

Implementation steps:
1) change deployment mechanism
2) change install mechanism
3) transform every request to check for a newer remote version, if no local deployment (based on build number and also checking for the existence of the legacy file remotely)
4) change to once per session check
5) implement snapshot policies
6) implement -U option

others will be left for later:
- cleaning local snapshots
- universal source directory related changes


> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 2 hours
>         Remaining: 10 hours
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31414 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 2 hours, 30 minutes
            Time Spent: 77400  (was: 68400)
    Remaining Estimate: 3600  (was: 7200)

implemented policies. Now need to make sure the SNAPSHOT fallbacks are in place for local installs, and if there is no timestamp file in the remote repository

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 21 hours, 30 minutes
>         Remaining: 1 hour
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31284 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 1 hour, 30 minutes
            Time Spent: 18000  (was: 12600)
    Remaining Estimate: 25200  (was: 30600)

setup artifact metadata and write the local repository file on install (see 2 above)

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 5 hours
>         Remaining: 7 hours
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31267 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 30 minutes
            Time Spent: 7200  (was: 5400)
    Remaining Estimate: 36000  (was: 37800)

time to write up the design in confluence

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 2 hours
>         Remaining: 10 hours
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=comments#action_31101 ]
     
Brett Porter commented on MNG-119:
----------------------------------

to avoid snapshots over successive runs, we may allow the configuration of a check interval - anywhere from "never" to "every execution", with a likely default of "daily".

This could be overriden using a propery or switch at runtime - eg continuous integration should always check.

This make snapshots more analogous to "cvs update" (and in fact an scm update could trigger a snapshot update), and makes it much more performant.

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Bug
>   Components: design
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work logged: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=worklog#action_31410 ]

Brett Porter logged work on MNG-119:
------------------------------------

           Time Worked: 5 hours
            Time Spent: 68400  (was: 50400)
    Remaining Estimate: 7200  (was: 14400)

1-4 working properly

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 19 hours
>         Remaining: 2 hours
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=history ]

Brett Porter updated MNG-119:
-----------------------------

             Component:     (was: design)
                        maven-core
                        maven-artifact
    Remaining Estimate: 43200
     Original Estimate: 43200
           Environment: 
                  type: Task  (was: Bug)

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>         Remaining: 12 hours
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=history ]

Brett Porter reassigned MNG-119:
--------------------------------

    Assign To: Brett Porter  (was: Jason van Zyl)

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Bug
>   Components: design
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Closed: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=history ]
     
Brett Porter closed MNG-119:
----------------------------

    Resolution: Fixed

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Task
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
> Original Estimate: 12 hours
>        Time Spent: 22 hours, 15 minutes
>         Remaining: 0 minutes
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Work started: (MNG-119) sort out snapshot handling

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-119?page=history ]
     
Work on MNG-119 started by Brett Porter

> sort out snapshot handling
> --------------------------
>
>          Key: MNG-119
>          URL: http://jira.codehaus.org/browse/MNG-119
>      Project: m2
>         Type: Bug
>   Components: maven-core, maven-artifact
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 1.0-alpha-1

>
>
> how snapshots will be downloaded, uploaded and handled is currently uncertain. This needs to be resolved urgently as we have frequent "odd" errors locally because an old snapshot is present, and it shouldn't be necessary to blow away a local repo so often.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira