阅读背景:

cloudfoundry:使用较旧的buildpack版本

来源:互联网 

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?

Cloundfoundry最近将其Java buildpack更新为2.5版(包括java 8和tomcat 8)。我仍然想使用2.4版本,因为我的应用还没有升级到java 8。最简单的方法是什么?

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.

但是如何指定使用版本2.4(https://github.com/cloudfoundry/java-buildpack/releases/tag/v2.4)?显然指定标记URL不起作用。

1 个解决方案

#1


9  

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

要使用“cf push -b”指定分支,请在分支名称前加上“#”。在您的示例中,您将使用

$ 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.

这可能会给你一些关于buildpack克隆处于“detatched HEAD”状态的奇怪消息,但可以忽略。

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?

您应该能够在Java 8 JRE上运行您的应用程序,即使它是使用早期的JDK编译的。在Java 8 JRE上运行应用程序时是否出现错误?

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

直接使用url中的版本号 - 没有“tags /”:java-buildpack#tags / v2.4 - > java-buildpack#v2.4


分享到: