Bug 63062 - Internal: Improve build
Summary: Internal: Improve build
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.0
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2019-01-07 13:26 UTC by Philippe Mouawad
Modified: 2021-01-02 20:56 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2019-01-07 13:26:43 UTC
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:
    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
Comment 1 Philippe Mouawad 2019-03-02 20:22:35 UTC
Would be covered by migration to Gradle:

- https://github.com/apache/jmeter/pull/448
Comment 2 Felix Schumacher 2021-01-02 20:56:31 UTC
I think many of these problems are solved with the migration and continuing work of Vladimir.