goal convert-snapshots(-auto)

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Labels:
    None
  • Environment:
    maven-rc3
    maven-release-plugin-1.3

Description

1) Snapshots should be resolved whenever version specification contains
string SNAPSHOT and not only when the value is exactly SNAPSHOT

2) Errors should not be ignored when getting snapshot-version file
from remote repository. If the file does not exist, no message
is reported

  1. File
    patch.SNAPSHOT
    07/Jun/04 6:55 AM
    1 kB
    Roman Macko
  2. File
    patch2.SNAPSHOT
    14/Jul/04 7:28 AM
    2 kB
    Roman Macko

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Roman Macko added a comment -

patch file to solve the issue

Show
Roman Macko added a comment - patch file to solve the issue
Hide
Permalink
Roman Macko added a comment -

1) patch2.SNAPSHOT replaces patch.SNAPSHOT
2) fixed incorrect replacement of SNAPSHOT in convert-snapshots(-auto)
goals when version does not include only SNAPSHOT string
3) terminate loop throught remote repositories when first
available timestamp file is found

Show
Roman Macko added a comment - 1) patch2.SNAPSHOT replaces patch.SNAPSHOT 2) fixed incorrect replacement of SNAPSHOT in convert-snapshots(-auto) goals when version does not include only SNAPSHOT string 3) terminate loop throught remote repositories when first available timestamp file is found
Hide
Permalink
Trygve Laugstol added a comment -

> 2) Errors should not be ignored when getting snapshot-version file
> from remote repository. If the file does not exist, no message
> is reported

Why should there be a message? Maven can try several repositories and there is nothing wrong if the artifact is missing. But the build shouldn't continue if a jar is missing in the local repository after all artifacts have been tried downloaded.

Show
Trygve Laugstol added a comment - > 2) Errors should not be ignored when getting snapshot-version file > from remote repository. If the file does not exist, no message > is reported Why should there be a message? Maven can try several repositories and there is nothing wrong if the artifact is missing. But the build shouldn't continue if a jar is missing in the local repository after all artifacts have been tried downloaded.

People

  • Assignee:
    Unassigned
    Reporter:
    Roman Macko
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: