Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NOTICE: Apache JMeter has migrated from Ant build system to Gradle #339

Closed
vlsi opened this issue Aug 2, 2019 · 4 comments
Closed

NOTICE: Apache JMeter has migrated from Ant build system to Gradle #339

vlsi opened this issue Aug 2, 2019 · 4 comments

Comments

@vlsi
Copy link
Contributor

vlsi commented Aug 2, 2019

Apache JMeter has migrated from Ant build system to Gradle, and it might impact jmeter-maven-plugin.

It would be nice if you could test if there are issues with new JMeter builds.

You can publish JMeter jars to local Maven repository via ./gradlew publishToMavenLocal command.

See https://lists.apache.org/thread.html/5bb942cc65f68de1015073b43f25e624528137caea13e9b9858f403b@%3Cdev.jmeter.apache.org%3E

@Ardesco
Copy link
Contributor

Ardesco commented Aug 3, 2019

We don't use any local builds, we just pull pre-built libraries from maven central.

The build system used by JMeter will have no effect on us at all. If the libraries that are generated and put in maven central change, that will affect us (but it will also affect anybody else using the libraries that you upload)

@Ardesco Ardesco closed this as completed Aug 3, 2019
@vlsi
Copy link
Contributor Author

vlsi commented Aug 3, 2019

It seems you are optimistic.

New build system implies that pom.xml and *.jar files are vastly different from what there was previously.
Of course new pom and jar files will be published to Maven Central, and it might easily impact you.

@Ardesco
Copy link
Contributor

Ardesco commented Aug 3, 2019

A build system is a build system. At the end of the day when you decide to perform a new release the code uploaded to maven central/jmeter archives is expected to be usable; if it's not, there isn't much we can do about it.

We download files from maven central and then place them in a JMeter directory structure that matches the structure of the standalone download - http://mirror.vorboss.net/apache//jmeter/binaries/apache-jmeter-5.1.1.zip. As long as all the files are put in the same place and the same command line is used to run JMeter nothing has changed for us.

If this ever changes we need to make changes to the command line we build/directory structure we create, but that's something we need to check with every new release of JMeter anyway (We expect the jar files to change substantially on every new release, there wouldn't be much point in putting out a new release if nothing has changed). I would be surprised if your new build process has fundamentally broken the use of JMeter on the command line without somebody noticing.

tl;dr;

It doesn't look like we need to do anything new that we would not have done anyway despite the build system for JMeter changing.

@vlsi
Copy link
Contributor Author

vlsi commented Aug 3, 2019

is expected to be usable; if it's not, there isn't much we can do about it.

You can try it before the release and report issues early.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants