From: Dale A. <da...@gr...> - 2006-07-07 04:19:28
|
This is the build file for the plugins? Or for jEdit? I agree with keeping jEdit core java 1.4 compatible, but I don't see any problem with letting plugins go with java 1.5. Dale On Thu, 6 Jul 2006, Marcelo Vanzin wrote: > Alan and Steve already said what I was going to say about default > properties/build.properties, so I'll just add my two bits on this matter: > > Vampire wrote: >> If a user wants to change the target java version, why shouldn't he? If >> he tries to set it to a value before 1.4 he will see that the compiler >> complains. And if he sets it to something higher, why not? It will still >> compile fine. > > I think that since we want to keep jEdit compatible with 1.4 for the > time being, we should discourage anyone from even trying to use 1.5 > features at all. By making it harder to change that value, the person > compiling won't think "hey, look at this property, I'm using Java 5 so > I'll set it to 1.5" and the submitting some bug fix/feature/enhancement > that has 1.5 code in it. > > I'd go as far as say that everybody compiling jEdit, and most of all the > packagers, shouldn't even use the javac from a 1.5 JDK to do it, so that > no references to classes that don't exist in 1.4 make it into the code. > > -- > Marcelo Vanzin > va...@us... > "Life is too short to drink cheap beer" > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-devel > |