The JFace library (part of the eclipse project) is used for creating user interfaces with the Standard Widget Toolkit (SWT). Reproducible: Always Steps to Reproduce: 1. 2. 3.
I don't have time for this, but if somebody else has the inclination, go ahead;)
I suggest that we pick one of the fresh Java developers to have a look at this some time. Any volunteers, Saleem?;P
Well, I wouldnt mind, just need to finish the work on java-config stuff first :-) But there was a possible volunteer on the mailing lists.
Created attachment 50304 [details] jface-3.0.1.ebuild (New Package) I stored the jface-3.0.1.tar.bz2 source package on my server for the time being. If you have a better spot let me know.
This almost works: It does not find SWT as part of the build process. Can you also provide a patch to the build.xml that ) Turns of verbosity ) Sets javacFailOnError to true ) Adds a <property file="build.properties" /> to the top ) Replaces the <classpath> element in the jface.jar target with a parameter swt.jar that it reads from a build.properties file? Then, the ebuild must be updated to ) Make a build.properties file containg the line swt.jar = <path to swt jar>, for example by echo "swt.jar = `java-config -p swt-3`" > build.properties ) RDEPEND on =dev-java/swt-3* Thanks!
Hmm. To get jface to work, you also need to build the following jars: from osgi: osgi.jar, core.jar, resolver.jar, console.jar, defaultAdaptor.jar, eclipseAdaptor.jar from eclipse.core.runtime: runtime.jar from eclipse.ui.forms: forms.jar from eclipse.jface.text: jfacetext.jar otherwise, you run into all sorts of strange problems. I'll post a updated ebuild later today to build these following packages. And if necessary, I'll also post the 3.1M4 ebuild.
Are these extra jars needed at runtime as well. If so, would it be best to build those all as part of JFace, or as seperate ebuilds?
correction, forms.jar and jfacetext.jar aren't required. Apologies.
Created attachment 50373 [details] Working version of jface-3.0.1.ebuild This is a tested version of the jface ebuild. Things compiles and installs cleanly.
Sorry I forgot to turn verbosity off Please just change the line ant || die "" to ant -q || die "" Sorry.
The latest ebuild from 2005-02-04 worked on my box.
Created attachment 50646 [details] JFace ebuild with runtime and osgi libraries taken away.
Created attachment 50647 [details] Eclipse osgi libraries
Created attachment 50648 [details] Eclipse runtime libraries
Created attachment 50649 [details] JFace ebuild with runtime and osgi libraries as separate ebuilds.
The osgi and runtime libraries are now separate ebuilds on their own.
Do we really want to create a seperate install for each package like this? There is somewhere around 15 different packages that jdtcore relies on for compiling, but it only needs about 2 of them when built. In eclipse there are 30-40 different packages that could be build, and none of them would be usable as Eclipse plugins as far as the architecture of eclipse is concerned. At least that is what I am seeing in the eclipse codebase anyway? What are your thoughts on this?
I am almost sure that osgi and runtime are needed both when compiling and running. Another concern is: If there are other packages requires eclipse runtime or osgi libraries, they could use this ebuild rather than building again. In general, the libraries that are required at compile time, should be present at runtime, that's always the safest bet. What do you think? I've discussed this with Saleem(compnerd) in the irc channel. He was the dev that came up with the idea of splitting them. =P P.S, It'd be great to see you in the irc channel.
Created attachment 50682 [details] Eclipse OSGI libraries ebuild.
Created attachment 50683 [details] Eclipse runtime libraries
Created attachment 50684 [details] JFace ebuild.
Are there alot of changes between 3.0 and 3.1? If so we may want to slot osgi and runtime as 3.0 instead of just 3.
I tried the new osgi and runtime ebuilds. I ran into a problem building these with my sunjdk-1.5 build system. I did not run into these issues when building using the original build.xml and build.properties files. Would it be possible to use the original files for these ebuilds? It seems they set the correct -source flags so 1.5 builds the files in 1.4 compatibility mode.
Can we split out eclipse-runtime and eclipse-osgi as seperate issues?
Created attachment 50751 [details] JFace ebuild. This is the JFace ebuild that with SLOT="3.0". JDK 1.5 compilation is also fixed and checked. The osgi and runtime ebuilds are attached to 71856.
Added an ebuild for now. Please test. It is hardmasked though.
Tested on ~amd64, works fine (as long as I build swt without firefox).
