-
Notifications
You must be signed in to change notification settings - Fork 11
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
Different Maven versions + Custom configuration #14
Comments
+1 |
1 similar comment
+1 |
That would be good especially for maven plugins matrix build, so +1 also for me. Meanwhile did someone solved that differently? |
+1 |
1 similar comment
+1 |
is this supposed to be available in travis? would be really nice... |
+1 |
Workaround
|
I personnally switched to docker using the following (see it in action in jgitver-maven-plugin for example)
|
@TuomasMatilainen Thanks for the suggestion with before_install!! Note my travis.yml looks like similar (I know it might not be the most compact config but does exactly what I want to test):
feel free to use it for whatever project / license |
Adds Oracle JDK 8 / openJDK 6/7/8 as build JDKs. Oracle JDK7 isn't available. Also adds custom maven version 3.2.5 for Java6 builds. cf. travis-ci/enterprise-installation#14 (comment)
Adds Oracle JDK 8 / openJDK 6/7/8 as build JDKs. Oracle JDK7 isn't available. Also adds custom maven version 3.2.5 for Java6 builds. cf. travis-ci/enterprise-installation#14 (comment)
Adds Oracle JDK 8 / openJDK 6/7/8 as build JDKs. Oracle JDK7 isn't available. Also adds custom maven version 3.2.5 for Java6 builds. cf. travis-ci/enterprise-installation#14 (comment)
Is there any news about this idea? |
Is there any news about this feature? |
Hi!
We would like to be able to choose the Maven version in Java builds for different projects (due to corporate requirements). This might be also great for the public Travis CI offering.
Currently, our developers download and install a custom Maven version on the fly. As we are internal service providers and would like to offer Travis as a tool that takes care of such things, it would be awesome being able to specify the Maven version.
Furthermore, we have a custom
settings.xml
that we currently provide with our machine images. I would be also great to provide a custom settings file for the builds.All this could be done by implementing a
maven
key in the `.travis.yml``:The text was updated successfully, but these errors were encountered: