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

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