eap64-basic-s2i using Maven version from cretaceous period

jboss-openshift / application-templates

OpenShift application templates supporting JBoss Middleware based applications.

Apache License 2.0

153 stars 303 forks source link

eap64-basic-s2i using Maven version from cretaceous period #146

Open fbricon opened 8 years ago

fbricon commented 8 years ago

When building a new app from eap64-basic-s2i, the log shows: Using Apache Maven 3.0.5 (Red Hat 3.0.5-16)

3.0.5 was released in Feb. 2013 (https://maven.apache.org/docs/history.html) The builder should use the latest version (3.3.9 to this day). Any project depending on bug fixes/features from the past 3 years might not build on openshift when using s2i

rcernich commented 8 years ago

This comes from the base rhel 7 image, so there's not much we can do about it.

willemvd commented 7 years ago

Is there any workaround to use an updated maven version? In our build we depend on a plugin that wants at least maven version 3.1

jmtd commented 7 years ago

The "proper" way would be to get the maven package updated in RHEL. Someone has already requested this, and the bug is marked "CLOSED WONTFIX" https://bugzilla.redhat.com/show_bug.cgi?id=1365671

The comments in that bug indicate that a newer version of Maven is available from Red Hat Software Collections: https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/2/html/2.2_Release_Notes/chap-RHSCL.html#sect-RHSCL-Changes-maven

So the question might be, how does one go about using RHSCL with our images? Is it possible?

willemvd commented 7 years ago

I'm not sure if it is possible, but maybe some extra template variable that can be used to execute additional commands? (something like the post-hook in a DeploymentConfig)