The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Sun, 9 Nov 2003 9:02 AM
Changes:
Fix Version changed to 1.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-944&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-944
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-944
Summary: Display status of inclusion in remote Maven repository on generated
dependency page
Type: Improvement
Status: Unassigned
Priority: Trivial
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-site
Fix Fors:
1.1
Versions:
1.0-beta-10
Assignee:
Reporter: Charlie Dobbie
Created: Fri, 17 Oct 2003 9:29 AM
Updated: Sun, 9 Nov 2003 9:02 AM
Description:
My project contains several dependencies that are not yet (or never will be) available
from ibiblio. It would be useful to have an indication on the dependency page to
distinguish these entries.
As each environment has its own opinion of where dependencies come from, and thus what
is and isn't "custom", this would require a property named something like
"maven.repo.remote.official" to store the project's opinion of standard repository
locations.
I can see this being implemented in one of two different ways:
1) At time of page generation, check whether each dependency exists in one of the
official/standard repository locations. If in off-line mode, don't check and don't
render any indication.
2) At time of dependency download, store extra information in the local repository
detailing where the file came from. At page generation time, check these values
instead.
The first option is quick and easy, but requires network access which will slow a
build down. The second option is more "correct", but requires a (minor) change to a
core Maven process. The second option may become out-of-sync with reality if a
"custom" library is added - the local repository wouldn't be aware of this.
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
