-
Notifications
You must be signed in to change notification settings - Fork 40
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
Retiring Docker Maven Plugin #118
Comments
You might want to consider to recommend https://github.com/fabric8io/docker-maven-plugin as an alternative, which seems to be the last actively supported docker-maven-plugin. Thanks for building and supporting this plugin over the last three years, really gives us quite some inspiration, too. |
Thank @rhuss. I agreed, that's a great tool and a perfect alternative. |
As we have a lot of builds running with the plugin I guess @Hubrick will take it over for now. Are you keeping the docker-java-orchestration alive? |
Can you re-release with the updated docker-java/orchestration pieces? |
Should all be released.
… On 3 Jul 2017, at 18:13, Andy Piper ***@***.***> wrote:
Can you re-release with the updated docker-java/orchestration pieces?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
2.11.17 was released a year ago, and it fails when I use it with the latest docker releases? |
Sorry my mistake. 2.11.24 works great! |
2.11.24 is not yet in Maven central repository. Maybe the publishing process had some issue? |
I don't know what's the difference with maven.org but this repository says that it does not have 2.11.24 yet: |
We are currently using this plugin for running integration testing during build. |
Hi gents. I'm really pleased that you've found the plugin useful. It's been sad for me to retire it. If I really thought this was the right way to build containers, I would continue to support it. But really I don't think using Maven to build images is really the right way to build these days. I don't think you should either! I wrote this when there wasn't a great way to do this, but I think these days Docker support is usually first class in many tools. I suggest that you either:
|
I'm currently planning on retiring this plugin. I think the Docker community has moved on, and I no longer believe that you should build or test containers using your build tool.
I'd like to know if anyone would be interested in taking ownership of the plugin. Pleas let me know.
The text was updated successfully, but these errors were encountered: