From: Slava P. <sl...@je...> - 2002-01-02 05:02:34
|
On Wed, 2002-01-02 at 17:40, klmcw yahoo wrote: > But what is the real long-term solution for this? Are we going to have per-JVM > or JVM version customizations in the future? Yes, and they have been part of jEdit for a long time. For example, jEdit 3.2.2 would run under JDK 1.1, but some files only compiled in 1.3. > If so, perhaps we might want to think about a property that can be set > (perhaps in the prepare target using the ant "available" task) and used to > determine which files and perhaps even which plugins to build. I've updated the jEdit build.xml to control building the Java 1.4-specific file using a property. This property is set to default, but I expect JDK 1.4 final to be released before jEdit 4.0final, so this should not be a problem. > I think it would really be great if we could get to a point where anybody > could checkout the source from CVS and build everything! Of course, there are > prerequisites to building some of the plugins (i.e., 3rd party libraries and > jar files). But we are all used to that - right? There are several stumbling blocks to this. For example, some plugins in the CVS are obsolete and should be removed. Another is that not all plugins have build.xml's; some are still built using jmk. -- Slava Pestov |