As far as I can remember, the current agreement with "mavenization" is: 1) JMeter is ok with having some pom.xml files in the repository if they would help to load the project with IDE 2) ant must stay the master build system
#2 implies that: implication 1) dependencies are to be managed by ant build.xml implication 2) if a new dependency added, then build.xml must be updated first (to reflect the change), then pom.xml might be required (if anyone uses pom.xml) Frankly speaking, I would love to switch to Maven (I can do mavenization), however I think it is just "not wanted" by the project. Vladimir пт, 7 июл. 2017 г. в 23:34, Antonio Gomes Rodrigues <[email protected]>: > Great > > Antonio > > 2017-07-07 15:29 GMT+02:00 Emilian Bold <[email protected]>: > > > OK, I'll Mavenize the project and keep you posted. > > > > --emi > > > > > > On Fri, Jul 7, 2017 at 4:04 PM, Antonio Gomes Rodrigues > > <[email protected]> wrote: > > > Hi, > > > > > > Using Maven have been considered, unfortunately we don't have enough > time > > > to work on it > > > Feel free to do it > > > > > > Antonio > > > > > > 2017-07-07 12:34 GMT+02:00 Emilian Bold <[email protected]>: > > > > > >> Hello, > > >> > > >> I see that officially only Eclipse is a supported IDE > > >> http://jmeter.apache.org/building.html > > >> > > >> I would like to add at least Apache NetBeans support too. > > >> > > >> I'm able to run the project, but I'm creating a single JAR for all the > > >> src/ submodules instead a multiple JARs. > > >> > > >> It might be a silly question, but have you considered using Maven or > > >> Gradle or some other build system that would be sub-project aware? > > >> > > >> This would more easily allow the project to be loaded from multiple > > IDEs. > > >> > > >> It would also allow a segmentation of dependency JARs per submodule. > > >> > > >> If dev@ is not the proper place for this I can resend the email to > > >> some other mailing list. > > >> > > >> --emi > > >> > > >
