What are best development practices for multi JRE version support?

Our application needs to support 1.5 and 1.6 JVMs. The 1.5 support needs to stay clear of any 1.6 JRE dependencies, whereas the 1.6 support needs to exploit 1.6-only features. When we change our Eclipse project to use a 1.5 JRE, we get all the dependencies flagged as errors. This is useful to see where our dependencies are, but is not useful for plain development. Committing source with such compile errors also feels wrong. What are the best practices for this kind of multi JRE version support? In C land, we had #ifdef compiler directives to solve such things fairly cleanly. What's the cleanest Java equivalent?
How do you manage to build your 1.5 version at all? Do you carefully exclude 1.6-dependent stuff in your build-file?

以上就是What are best development practices for multi JRE version support?的详细内容,更多请关注web前端其它相关文章!

赞(0) 打赏
未经允许不得转载:web前端首页 » JavaScript 答疑

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

前端开发相关广告投放 更专业 更精准