On 9 August 2010 12:12, nicolas de loof <[email protected]> wrote: > Hi > My name is Nicolas De loof, I'm a Maven committer and a jMeter user, with > even more usage of this nice tool. I'm french, so please apology for my ugly > english ;) > > As jMeter 2.4 is just released, I think it's a good time to consider > switching the build to use Maven, or maybe just consider Maven as an > alternative build tool. As the ant script allready uses many > properties, that will only require some minor folder changes.
`When I last looked at this a few years ago, it looked like the whole folder hierarchy would need to be changed. However, Maven has improved since then, and I have had more experience of using it on other (simpler) projects. So maybe one can add a Maven build without moving too much around. Although it does a lot of things well, Maven makes some operations really difficult to define. For example, can it automatically invoke the RMIC compiler? It also takes a lot longer to compile and test than Ant, perhaps because of all the dependency checking. That was what really put me off - and still does. But if you just want to create Maven artifacts, then perhaps that can be done without too much pain, and the Ant build used for everything else. Or indeed maybe the Ant build could be extended to create the Maven artifacts. > Building tools around jMeter (maven plugin, Hudson plugin, ...) requires > jMeter artifacts to be available on maven repository. Nowaday users have to > install them manually and can't take advantage of dependency resolution. > There is also no "official" maven plugin to support performance testing > during build (typically, continuous performance testing on nightly builds). > Maybe this could be part of the roadmap. > > WDYT ? > > Best regards, > Nicolas > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
