开发环境jdk1.5，部署环境jdk1.4 BigDecimal出现问题

最新推荐文章于 2020-03-04 22:47:30 发布

lwowen

最新推荐文章于 2020-03-04 22:47:30 发布

阅读量1.9k

点赞数

分类专栏： Java 文章标签： jdk generics constructor filter google ant

Java 专栏收录该内容

9 篇文章

订阅专栏

本文解决了一个因使用不同版本的JDK导致的BigDecimal构造函数冲突问题。在从JDK 1.5编译并试图在JDK 1.4上运行时出现问题。文中详细解释了问题的原因在于新版本JDK中引入的BigDecimal(int val)构造函数，并提供了通过指定-source和-bootclasspath标志来匹配早期JDK版本的方法。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

开发环境是jdk1.5，部署环境是jdk1.4，用ANT编译程序的时候已经指定了-source 1.4，以前都没问题，最近出问题了。GOOGLE了一下，发现是因为使用了BigDecimal，

以下摘自：http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6226858

As part of jsr 13, a new constructor, BigDecimal(int val), was added to BigDecimal in JDK 5. Therefore, in 1.4 and earlier

new BigDecimal(1)

in the source resolves to BigDecimal(double) while in 1.5 it resolves to BigDecimal(int), which is not present in earlier JDKs. The -source flag of javac only restricts the constructs in the source languge (e.g. assert, generics); it does *not* restrict or filter the contents of the libraries. Therefore, in JDK5 if you compile with "javac -source 1.4" you will still be compiling against the 1.5 version of the libraries. Therefore, in cases like the one in this bug, code compiled at a lower language level might not be able to be used with an ealier release supporting that language level.

To match both the language and libraries of an ealier jdk, use -source and the -bootclasspath flag to specify the earlier rt.jar as well. Of course the ealier jdk could be used too.