cloudfoundry：使用较旧的buildpack版本 [英] cloudfoundry: use an older buildpack version

问题描述

Cloundfoundry最近将其Java buildpack更新到2.5版（包括Java 8和tomcat 8）。我仍然想使用2.4版，因为我的应用尚未升级到Java 8。
这样做最简单的方法是什么？

我可以使用

<$ p $推送应用程序p> cf push app -b https://github.com/cloudfoundry/java-buildpack


，但是如何指定使用版本2.4（ https： //github.com/cloudfoundry/java-buildpack/releases/tag/v2.4 ）？显然，指定标签URL无效。

解决方案

要使用 cf push -b指定分支，请在分支名称前的＃。在您的示例中，您将使用

  $ cf push app -b https://github.com/cloudfoundry/java-buildpack ＃v2.4 
  

这可能会给您一些有关buildpack克隆位于已分发的HEAD中的奇怪消息。状态，但可以忽略。

即使使用早期的JDK进行了编译，您也应该能够在Java 8 JRE上运行您的应用程序。在Java 8 JRE上运行应用程序时遇到错误吗？

直接在url中使用版本号-不带 tags /：java-buildpack＃tags / v2.4-> java-buildpack＃v2.4

Cloundfoundry recently updated its Java buildpack to version 2.5 (including java 8 and tomcat 8). I still would like to use version 2.4 since my app hasn't been upgraded to java 8 yet. What is the easiest way to do so?

I can push the app using

cf push app -b https://github.com/cloudfoundry/java-buildpack

but how can I specify to use release 2.4 (https://github.com/cloudfoundry/java-buildpack/releases/tag/v2.4)? Apparently specifying the tag URL instead doesn't work.

解决方案

To specify a branch with "cf push -b", put a "#" before the branch name. In your example, you would use

$ cf push app -b https://github.com/cloudfoundry/java-buildpack#v2.4

This might give you some strange messages about the buildpack clone being in "detatched HEAD" state, but that can be ignored.

You should be able to run your app on the Java 8 JRE even though it was compiled with an earlier JDK. Are you getting errors when running your app on the Java 8 JRE?

Use directly the version number in the url - without "tags/": java-buildpack#tags/v2.4 -> java-buildpack#v2.4

这篇关于cloudfoundry：使用较旧的buildpack版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！