<div dir="ltr">Is this the sort of thing that geard will address going forward?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 23, 2014 at 8:46 AM, Farah Juma <span dir="ltr"><<a href="mailto:fjuma@redhat.com" target="_blank">fjuma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> From: "Jim McGuinness" <<a href="mailto:dador92@gmail.com">dador92@gmail.com</a>><br>
> To: "Farah Juma" <<a href="mailto:fjuma@redhat.com">fjuma@redhat.com</a>>, <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> Sent: Wednesday, April 23, 2014 9:10:02 AM<br>
<div class="">> Subject: Re: [wildfly-dev] WildFly 8.1.0.CR1 on OpenShift<br>
><br>
</div><div><div class="h5">> Farah,<br>
><br>
> I've been looking at this some more, and the marker for Java just toggles<br>
> back and forth between Java 6 and Java 7. If the Java 7 marker is not<br>
> present, then a cartridge just defaults back to Java 6.<br>
><br>
> But you still have to have the version of Java installed on the gear in<br>
> order to toggle back and forth.<br>
><br>
> Here are the contents of the /usr/lib/jvm directory on the gear where<br>
> OpenShift online installed my Wildfly 8.1<br>
> cartridge ...<br>
><br>
> lrwxrwxrwx. 1 root root 26 Apr 22 13:19 java -><br>
> /etc/alternatives/java_sdk<br>
> drwxr-xr-x. 3 root root 4.0K Feb 18 2013 java-1.5.0-gcj-1.5.0.0<br>
> lrwxrwxrwx. 1 root root 32 Apr 22 13:19 java-1.6.0 -><br>
> /etc/alternatives/java_sdk_1.6.0<br>
> lrwxrwxrwx. 1 root root 26 Apr 22 13:19 java-1.6.0-openjdk -><br>
> java-1.6.0-openjdk-1.6.0.0<br>
> drwxr-xr-x. 7 root root 4.0K Apr 11 06:57 java-1.6.0-openjdk-1.6.0.0<br>
> lrwxrwxrwx. 1 root root 32 Apr 22 13:18 java-1.7.0 -><br>
> /etc/alternatives/java_sdk_1.7.0<br>
> lrwxrwxrwx. 1 root root 27 Apr 22 13:18 java-1.7.0-openjdk -><br>
> java-1.7.0-openjdk-1.7.0.55<br>
> drwxr-xr-x. 3 root root 4.0K Feb 3 17:06 java-1.7.0-openjdk-1.7.0.45<br>
> drwxr-xr-x. 3 root root 4.0K Apr 22 13:19 java-1.7.0-openjdk-1.7.0.51<br>
> drwxr-xr-x. 7 root root 4.0K Apr 22 13:18 java-1.7.0-openjdk-1.7.0.55<br>
> drwxr-xr-x. 3 root root 4.0K May 1 2013 java-1.7.0-openjdk-1.7.0.9<br>
> lrwxrwxrwx. 1 root root 34 Apr 22 13:19 java-openjdk -><br>
> /etc/alternatives/java_sdk_openjdk<br>
> lrwxrwxrwx. 1 root root 21 Apr 22 13:19 jre -> /etc/alternatives/jre<br>
> lrwxrwxrwx. 1 root root 27 Feb 18 2013 jre-1.5.0 -><br>
> /etc/alternatives/jre_1.5.0<br>
> lrwxrwxrwx. 1 root root 26 Feb 18 2013 jre-1.5.0-gcj -><br>
> java-1.5.0-gcj-1.5.0.0/jre<br>
> lrwxrwxrwx. 1 root root 27 Apr 22 13:19 jre-1.6.0 -><br>
> /etc/alternatives/jre_1.6.0<br>
> lrwxrwxrwx. 1 root root 30 Apr 22 13:19 jre-1.6.0-openjdk -><br>
> java-1.6.0-openjdk-1.6.0.0/jre<br>
> lrwxrwxrwx. 1 root root 27 Apr 22 13:18 jre-1.7.0 -><br>
> /etc/alternatives/jre_1.7.0<br>
> lrwxrwxrwx. 1 root root 31 Apr 22 13:18 jre-1.7.0-openjdk -><br>
> java-1.7.0-openjdk-1.7.0.55/jre<br>
> lrwxrwxrwx. 1 root root 25 Feb 18 2013 jre-gcj -><br>
> /etc/alternatives/jre_gcj<br>
> lrwxrwxrwx. 1 root root 29 Apr 22 13:19 jre-openjdk -><br>
> /etc/alternatives/jre_openjdk<br>
><br>
> I truly think the answer is that the gear needs to add Java 8 SE in order<br>
> for the Wildfly cartridge to be able to use it. And the Wildfly cartridge<br>
> will then need to be updated to respond to a Java 8 marker..<br>
<br>
</div></div>That's correct. Since OpenShift hasn't yet made JDK 8 available though, the idea is to update the WildFly cartridge so that it installs JDK 8 on the gear.<br>
<span class="HOEnZb"><font color="#888888"><br>
Farah<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
><br>
> On Tue, Apr 22, 2014 at 6:57 PM, Jim McGuinness <<a href="mailto:dador92@gmail.com">dador92@gmail.com</a>> wrote:<br>
><br>
> > Doesn't the marker just indicate the JDK version(s) used/usable by the app<br>
> > (in this case wildfly)? The gear still has to have a JDK 8 installed<br>
> > doesn't it?<br>
> ><br>
> ><br>
> > On Tue, Apr 22, 2014 at 6:00 PM, Farah Juma <<a href="mailto:fjuma@redhat.com">fjuma@redhat.com</a>> wrote:<br>
> ><br>
> >><br>
> >> > From: "Jim McGuinness" <<a href="mailto:dador92@gmail.com">dador92@gmail.com</a>><br>
> >> > To: "Farah Juma" <<a href="mailto:fjuma@redhat.com">fjuma@redhat.com</a>><br>
> >> > Sent: Tuesday, April 22, 2014 5:57:07 PM<br>
> >> > Subject: Re: [wildfly-dev] WildFly 8.1.0.CR1 on OpenShift<br>
> >> ><br>
> >> > Would it be better to create a JDK 8 cartridge which could be deployed<br>
> >> in<br>
> >> > the same gear as the Wildfly 8.1 cartridge? Ideally you'll want to use<br>
> >> the<br>
> >> > JDK 8 for more than just Wildfly.<br>
> >><br>
> >> Support for different JDK versions is added using marker files (e.g.,<br>
> >> this post describes how JDK7 support was added:<br>
> >> <a href="https://www.openshift.com/blogs/new-openshift-release-aug-8-2012-java-7-cakephp-origin-updates-and-more" target="_blank">https://www.openshift.com/blogs/new-openshift-release-aug-8-2012-java-7-cakephp-origin-updates-and-more</a><br>
> >> ).<br>
> >><br>
> >> > Is the gear's lack of a JDK 8 caused by the requirements of SELinux?<br>
> >><br>
> >> It just hasn't been added by OpenShift yet.<br>
> >><br>
> >> ><br>
> >> > On Tue, Apr 22, 2014 at 2:35 PM, Farah Juma <<a href="mailto:fjuma@redhat.com">fjuma@redhat.com</a>> wrote:<br>
> >> ><br>
> >> > > OpenShift hasn't added support for JDK8 yet but it should be possible<br>
> >> for<br>
> >> > > us to add it into the WildFly cartridge. I'll look into this.<br>
> >> > ><br>
> >> > > Farah<br>
> >> > ><br>
> >> > > ----- Original Message -----<br>
> >> > > > From: "Tomaž Cerar" <<a href="mailto:tomaz.cerar@gmail.com">tomaz.cerar@gmail.com</a>><br>
> >> > > > To: "Farah Juma" <<a href="mailto:fjuma@redhat.com">fjuma@redhat.com</a>><br>
> >> > > > Cc: "WildFly Dev" <<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>><br>
> >> > > > Sent: Tuesday, April 22, 2014 3:22:45 PM<br>
> >> > > > Subject: Re: [wildfly-dev] WildFly 8.1.0.CR1 on OpenShift<br>
> >> > > ><br>
> >> > > > Great news!<br>
> >> > > ><br>
> >> > > > Btw, did you manage to add support for JDK8 yet?<br>
> >> > > > Not sure how far is openshift in this area but it would be great if<br>
> >> we<br>
> >> > > > would have JDK8 with WildFly on OpenShift.<br>
> >> > > ><br>
> >> > > > --<br>
> >> > > > tomaz<br>
> >> > > ><br>
> >> > > ><br>
> >> > > > On Tue, Apr 22, 2014 at 9:17 PM, Farah Juma <<a href="mailto:fjuma@redhat.com">fjuma@redhat.com</a>><br>
> >> wrote:<br>
> >> > > ><br>
> >> > > > > Since WildFly 8.1.0.CR1 was released last week, the OpenShift<br>
> >> WildFly<br>
> >> > > > > cartridge has been updated as well.<br>
> >> > > > ><br>
> >> > > > > See<br>
> >> > > > ><br>
> >> > ><br>
> >> <a href="https://community.jboss.org/people/fjuma/blog/2014/04/22/wildfly-810cr1-on-openshiftfor" target="_blank">https://community.jboss.org/people/fjuma/blog/2014/04/22/wildfly-810cr1-on-openshiftfor</a><br>
> >> > > > > more details on how to get started. Please try it out and provide<br>
> >> > > > > feedback.<br>
> >> > > > ><br>
> >> > > > > _______________________________________________<br>
> >> > > > > wildfly-dev mailing list<br>
> >> > > > > <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> >> > > > > <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
> >> > > > ><br>
> >> > > ><br>
> >> > ><br>
> >> > > _______________________________________________<br>
> >> > > wildfly-dev mailing list<br>
> >> > > <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> >> > > <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
> >> > ><br>
> >> ><br>
> >><br>
> ><br>
> ><br>
><br>
</div></div></blockquote></div><br></div>