Greetings, I'm shifting discussion to here from "Bug 49753 - Please publish jMeter artifacts on Maven central repository" [1].
Considering an outright switch to Maven is a no go [2], what do developers think about delegating dependency management in the JMeter Ant build to the Maven Ant Tasks or Apache Ivy? The primary benefit would be that POMs could be generated to satisfy Bug 49753 that would be based on the same dependencies used by Ant to compile and execute tests. Using Ivy as an example (the Maven Ant Tasks have synonymous functionality), the change would roughly entail the following: - Dependency information in build.properties would move to a corresponding ivy.xml [3] file. - The _process_all_jars Ant target and friends would be implemented with the Ivy resolve [4] and retrieve [5] tasks. - Corresponding classpaths would be generated with the cachepath [6] task. - Equivalent POMs would be generated with the makepom [7] task. - JMeter JARs would be published to Nexus [8] with the publish [9] task. Regards, Ian [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=49753 [2] https://issues.apache.org/bugzilla/show_bug.cgi?id=50324 [3] http://ant.apache.org/ivy/history/2.2.0/ivyfile.html [4] http://ant.apache.org/ivy/history/2.2.0/use/resolve.html [5] http://ant.apache.org/ivy/history/2.2.0/use/retrieve.html [6] http://ant.apache.org/ivy/history/2.2.0/use/cachepath.html [7] http://ant.apache.org/ivy/history/2.2.0/use/makepom.html [8] https://issues.apache.org/jira/browse/INFRA-4332 [9] http://ant.apache.org/ivy/history/2.2.0/use/publish.html
