[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-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 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
[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
[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-5) 1.0-alpha-6 Still not sure if it's good or bad 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-6 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
[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.0-alpha-4) 1.0-alpha-5 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-5 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
[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: Summary: DependencyBuilder does not check if the query artifacts exist (was: DependencyBuilder does not check fs the query artifacts exist) 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.0-alpha-4 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 -- 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-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: Description: 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 was: 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 Fix Version/s: 1.0.0-alpha-4 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.0-alpha-4 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
