This could be potentially solved by a migration to Maven but some annoying things about current process: - Dependency addition / update is cumbersome (6 files to update) , partly because we are very/too verbose in terms of what we do: 1/jmeter/trunk/LICENSE 2/ jmeter/trunk/build.properties => Not needed if we move to Maven 3/ jmeter/trunk/eclipse.classpath => Not needed if we move to Maven 4/ jmeter/trunk/lib/ (props changed) => Not needed if we move to Maven 5/ jmeter/trunk/lib/aareadme.txt => Probably better in xdocs as a documentation of development 6/ jmeter/trunk/res/maven/ApacheJMeter_parent.pom => Still needed, but without the need to have 1 version property for every different artifact of the same library (jodd, jackson....) 7/ jmeter/trunk/xdocs/changes.xml => Still needed 8/ License files if not ASF license => Do we really need to be that verbose ? 9/ Hacks in JMeterVersionTest => Would be dropped
Would be covered by migration to Gradle: - https://github.com/apache/jmeter/pull/448
I think many of these problems are solved with the migration and continuing work of Vladimir.
@Philippe, I think we can close this, right?
Hi Felix, Thanks for reviewing. Yes it can be closed. Regards
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4971