[jbehave-dev] [jira] Updated: (JBEHAVE-139) Convert ant build to use ivy for dependencies
[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-139: - Bumping out of 2.2 release until some Ant-driven soul is motivated to implement Ivy-based dependency lookup. Convert ant build to use ivy for dependencies - Key: JBEHAVE-139 URL: http://jira.codehaus.org/browse/JBEHAVE-139 Project: JBehave Issue Type: Improvement Components: Build system Affects Versions: 2.0 Environment: Any Reporter: Dan North Assignee: Dan North Fix For: 2.2 We currently have a lib directory with various subdirectories containing a number of dependent jars. As we add more adapters (spring, pico, test-ng) this is going to get more complex. Ivy (http://ant.apache.org/ivy) has a similar dependency resolution model to maven. By migrating to ivy we can simplify the build and remove the dependent third-party jars from the repository. -- 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 - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-139) Convert ant build to use ivy for dependencies
[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-139: - Comment: was deleted (was: Bumping out of 2.2 release until some Ant-driven soul is motivated to implement Ivy-based dependency lookup. ) Convert ant build to use ivy for dependencies - Key: JBEHAVE-139 URL: http://jira.codehaus.org/browse/JBEHAVE-139 Project: JBehave Issue Type: Improvement Components: Build system Affects Versions: 2.0 Environment: Any Reporter: Dan North Assignee: Dan North We currently have a lib directory with various subdirectories containing a number of dependent jars. As we add more adapters (spring, pico, test-ng) this is going to get more complex. Ivy (http://ant.apache.org/ivy) has a similar dependency resolution model to maven. By migrating to ivy we can simplify the build and remove the dependent third-party jars from the repository. -- 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 - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-139) Convert ant build to use ivy for dependencies
[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-139: - Fix Version/s: (was: 2.2) Bumping out of 2.2 release until some Ant-driven soul is motivated to implement Ivy-based dependency lookup. Convert ant build to use ivy for dependencies - Key: JBEHAVE-139 URL: http://jira.codehaus.org/browse/JBEHAVE-139 Project: JBehave Issue Type: Improvement Components: Build system Affects Versions: 2.0 Environment: Any Reporter: Dan North Assignee: Dan North We currently have a lib directory with various subdirectories containing a number of dependent jars. As we add more adapters (spring, pico, test-ng) this is going to get more complex. Ivy (http://ant.apache.org/ivy) has a similar dependency resolution model to maven. By migrating to ivy we can simplify the build and remove the dependent third-party jars from the repository. -- 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 - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email