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/04/07 21:59:17 UTC
[jira] Updated: (MERCURY-75) DependencyBuilder does not check if
the query artifacts exist
[ http://jira.codehaus.org/browse/MERCURY-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov updated MERCURY-75:
--------------------------------
Fix Version/s: (was: 1.0-alpha-6)
1.0-alpha-7
> DependencyBuilder does not check if the query artifacts exist
> -------------------------------------------------------------
>
> Key: MERCURY-75
> URL: http://jira.codehaus.org/browse/MERCURY-75
> Project: Mercury
> Issue Type: Bug
> Affects Versions: 1.0.0-alpha-3
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
> Fix For: 1.0-alpha-7
>
>
> DependencyBuilder always presumes they exist and if DependencyProcessor does not throw an exception (not finding the POM), it will return this as an artifact without dependencies.
> Need to enforce that DependencyProcessor fails for non-existent artifacts. Because Dep.Processor is reading POM from all known repos - if it does not get pom bytes - it means that artifact is not found
--
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