You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Oleg Gusakov (JIRA)" <ji...@codehaus.org> on 2009/02/19 01:05:19 UTC
[jira] Created: (MERCURY-97) find a way to bypass metadata.xml for
remote repositories
find a way to bypass metadata.xml for remote repositories
---------------------------------------------------------
Key: MERCURY-97
URL: http://jira.codehaus.org/browse/MERCURY-97
Project: Mercury
Issue Type: Improvement
Affects Versions: 1.0-alpha-6
Reporter: Oleg Gusakov
Assignee: Oleg Gusakov
Metadata maybe inaccurate or missing.
Need to find a way to bypass / fix metadata:
* scrape HTTP pages
* ...
--
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
[jira] Updated: (MERCURY-97) find a way to bypass metadata.xml for
remote repositories, if necessary
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov updated MERCURY-97:
--------------------------------
Description:
Original Mercury design was based on the requirement that repository metadata will be always correct.
In real situations metadata maybe inaccurate or missing, and we cannot affect it.
Need to find a way to bypass / fix metadata:
* scrape HTTP pages
* ...
was:
Metadata maybe inaccurate or missing.
Need to find a way to bypass / fix metadata:
* scrape HTTP pages
* ...
> find a way to bypass metadata.xml for remote repositories, if necessary
> ------------------------------------------------------------------------
>
> Key: MERCURY-97
> URL: http://jira.codehaus.org/browse/MERCURY-97
> Project: Mercury
> Issue Type: Improvement
> Affects Versions: 1.0-alpha-6
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> Original Mercury design was based on the requirement that repository metadata will be always correct.
> In real situations metadata maybe inaccurate or missing, and we cannot affect it.
> Need to find a way to bypass / fix metadata:
> * scrape HTTP pages
> * ...
--
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
[jira] Updated: (MERCURY-97) find a way to bypass metadata.xml for
remote repositories, if necessary
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov updated MERCURY-97:
--------------------------------
Summary: find a way to bypass metadata.xml for remote repositories, if necessary (was: find a way to bypass metadata.xml for remote repositories)
> find a way to bypass metadata.xml for remote repositories, if necessary
> ------------------------------------------------------------------------
>
> Key: MERCURY-97
> URL: http://jira.codehaus.org/browse/MERCURY-97
> Project: Mercury
> Issue Type: Improvement
> Affects Versions: 1.0-alpha-6
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> Metadata maybe inaccurate or missing.
> Need to find a way to bypass / fix metadata:
> * scrape HTTP pages
> * ...
--
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
[jira] Updated: (MERCURY-97) find a way to bypass metadata.xml for
remote repositories, if necessary
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov updated MERCURY-97:
--------------------------------
Fix Version/s: 1.0-alpha-6
missing metadata for releases is now processed correctly
> find a way to bypass metadata.xml for remote repositories, if necessary
> ------------------------------------------------------------------------
>
> Key: MERCURY-97
> URL: http://jira.codehaus.org/browse/MERCURY-97
> Project: Mercury
> Issue Type: Improvement
> Affects Versions: 1.0-alpha-6
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
> Fix For: 1.0-alpha-6
>
>
> Original Mercury design was based on the requirement that repository metadata will be always correct.
> In real situations metadata maybe inaccurate or missing, and we cannot affect it.
> Need to find a way to bypass / fix metadata:
> * scrape HTTP pages
> * ...
--
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
[jira] Closed: (MERCURY-97) find a way to bypass metadata.xml for
remote repositories, if necessary
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MERCURY-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov closed MERCURY-97.
-------------------------------
Resolution: Fixed
fixed - added "exclude from verification" flag, used for metadata
> find a way to bypass metadata.xml for remote repositories, if necessary
> ------------------------------------------------------------------------
>
> Key: MERCURY-97
> URL: http://jira.codehaus.org/browse/MERCURY-97
> Project: Mercury
> Issue Type: Improvement
> Affects Versions: 1.0-alpha-6
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
> Fix For: 1.0-alpha-6
>
>
> Original Mercury design was based on the requirement that repository metadata will be always correct.
> In real situations metadata maybe inaccurate or missing, and we cannot affect it.
> Need to find a way to bypass / fix metadata:
> * scrape HTTP pages
> * ...
--
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