-
Notifications
You must be signed in to change notification settings - Fork 582
#37 Migrate build system away from Ant (WIP) #119
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
Conversation
… plugins for javadoc source and jar with descriptors + add maven versions plugin
properties files in the classpath for ant.
Thank you, I will take a look in the next few days. |
You're welcome. Let me know if there is anything to fix and anything else I can do. |
to run stress tests using maven
By the way you can also run the perf tests like this or with arguments
Basically any class with a main inside package com.rabbitmq.examples without the need to moving any jar around, the classpath is defined by maven. I added a |
I cannot run tests with
In fact, all ant tasks seems to fail the same way. I've merged master into your branch and pushed it as |
Standard Maven tasks ( |
Plus one TLS test consistently errors. There are no failures in master with |
I'll have a look tomorrow. I believe the pb with ant is that it's not using For the TLS problem I don't really know, what is the error ? I'll try to On Sun, Jan 3, 2016 at 5:16 AM, Michael Klishin [email protected]
|
@PatrickSauts thank you. I will dig for details on the TLS test failure in a bit. |
The problem was that I had the generated sources so it didn't try to recreate them. Fixed that part in So running That |
Still don't know about TLS as I'm getting that error on FunctionalTests
|
The tests pass for me when not under umbrella.
|
I pushed another version of the pom.xml that still uses ant but without the need for the build.xml file. |
Thank you @PatrickSauts, will give it another try today. |
I updated
I suspect that those may be using |
Thank you, That should be usefull. I'll have a look tomorrow. |
There was a NPE when initializing Host.java that should fix the java.lang.ExceptionInInitializerError Looking into the other errors if I can reproduce them. Also added cleaning of generated source on |
OK, @PatrickSauts please base all new changes on |
I tried to push the other day to branch On Thu, Jan 7, 2016 at 4:20 PM, Michael Klishin [email protected]
|
@PatrickSauts we'll keep you posted on what might need to be done there. So far things are looking good. You don't have access to our repo. You can, however, create a new branch (with the same name), push it to your repo, and I'll pull it like I do with your master branch right now. Key difference is what branch you base your changes on. What branch you push to in your repo is up to you, we can pull in anything ;) |
Fixed #37 (at least to a large extent).
The tests can be run with
mvn clean test
or with
ant
, I kept it compatible.And also with the right
settings.xml
in your~/.m2
directory likeyou can run
mvn clean deploy
that would compile, run the tests, and deploy to the repository if the tests pass.I also added maven version plugin, so to set a version you can do it that way
mvn versions:set -DnewVersion=<new.version> && mvn versions:commit
That's a better alternative than the release plugin.
So basically to release a new version the maven command would be:
mvn versions:set -DnewVersion=<new.version> && mvn versions:commit && mvn clean deploy