Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 71307 - request for ebuild dev-java/jface
Summary: request for ebuild dev-java/jface
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Java team
Keywords: EBUILD
Depends on: 71856 81561 81562
Blocks: 58596
  Show dependency tree
Reported: 2004-11-15 11:46 UTC by Saleem Abdulrasool (RETIRED)
Modified: 2006-05-02 07:48 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

jface-3.0.1.ebuild (New Package) (jface-3.0.1.ebuild,824 bytes, text/plain)
2005-02-03 21:42 UTC, Scott Carr
Working version of jface-3.0.1.ebuild (jface-3.0.1.ebuild,705 bytes, text/plain)
2005-02-04 11:59 UTC, Qian Qiao
JFace ebuild with runtime and osgi libraries taken away. (jface-3.0.1.ebuild,932 bytes, application/octet-stream)
2005-02-07 12:06 UTC, Qian Qiao
Eclipse osgi libraries (eclipse-osgi-3.0.1.ebuild,631 bytes, text/plain)
2005-02-07 12:07 UTC, Qian Qiao
Eclipse runtime libraries (eclipse-runtime-3.0.1.ebuild,745 bytes, text/plain)
2005-02-07 12:07 UTC, Qian Qiao
JFace ebuild with runtime and osgi libraries as separate ebuilds. (jface-3.0.1.ebuild,932 bytes, text/plain)
2005-02-07 12:08 UTC, Qian Qiao
Eclipse OSGI libraries ebuild. (eclipse-osgi-3.0.1.ebuild,592 bytes, text/plain)
2005-02-07 16:21 UTC, Qian Qiao
Eclipse runtime libraries (eclipse-runtime-3.0.1.ebuild,691 bytes, text/plain)
2005-02-07 16:22 UTC, Qian Qiao
JFace ebuild. (jface-3.0.1.ebuild,803 bytes, text/plain)
2005-02-07 16:22 UTC, Qian Qiao
JFace ebuild. (jface-3.0.1.ebuild,807 bytes, text/plain)
2005-02-08 09:47 UTC, Qian Qiao

Note You need to log in before you can comment on or make changes to this bug.
Description Saleem Abdulrasool (RETIRED) gentoo-dev 2004-11-15 11:46:02 UTC
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:
Comment 1 Karl Trygve Kalleberg (RETIRED) gentoo-dev 2004-11-15 16:18:47 UTC
I don't have time for this, but if somebody else has the inclination, go ahead;)
Comment 2 Karl Trygve Kalleberg (RETIRED) gentoo-dev 2004-12-28 15:41:40 UTC
I suggest that we pick one of the fresh Java developers to have a look at this some time. Any volunteers, Saleem?;P
Comment 3 Saleem Abdulrasool (RETIRED) gentoo-dev 2005-02-03 18:13:39 UTC
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.
Comment 4 Scott Carr 2005-02-03 21:42:10 UTC
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.
Comment 5 Karl Trygve Kalleberg (RETIRED) gentoo-dev 2005-02-04 05:17:42 UTC
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="" /> to the top
) Replaces the <classpath> element in the jface.jar target with
  a parameter swt.jar that it reads from a file?

Then, the ebuild must be updated to
) Make a file containg the line 
swt.jar = <path to swt jar>, for example by 
echo "swt.jar = `java-config -p swt-3`" >
) RDEPEND on =dev-java/swt-3*

Comment 6 Qian Qiao 2005-02-04 05:31:05 UTC
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.
Comment 7 Scott Carr 2005-02-04 07:55:55 UTC
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?
Comment 8 Qian Qiao 2005-02-04 11:12:36 UTC
correction, forms.jar and jfacetext.jar aren't required. Apologies.
Comment 9 Qian Qiao 2005-02-04 11:59:25 UTC
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
Comment 10 Qian Qiao 2005-02-04 12:09:05 UTC
Sorry I forgot to turn verbosity off

Please just change the line ant || die "" to ant -q || die ""
Comment 11 Scott Carr 2005-02-04 14:27:15 UTC
The latest ebuild from 2005-02-04 worked on my box.
Comment 12 Qian Qiao 2005-02-07 12:06:08 UTC
Created attachment 50646 [details]
JFace ebuild with runtime and osgi libraries taken away.
Comment 13 Qian Qiao 2005-02-07 12:07:17 UTC
Created attachment 50647 [details]
Eclipse osgi libraries
Comment 14 Qian Qiao 2005-02-07 12:07:49 UTC
Created attachment 50648 [details]
Eclipse runtime libraries
Comment 15 Qian Qiao 2005-02-07 12:08:44 UTC
Created attachment 50649 [details]
JFace ebuild with runtime and osgi libraries as separate ebuilds.
Comment 16 Qian Qiao 2005-02-07 12:09:34 UTC
The osgi and runtime libraries are now separate ebuilds on their own.
Comment 17 Scott Carr 2005-02-07 12:47:47 UTC
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?
Comment 18 Qian Qiao 2005-02-07 13:03:47 UTC
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.
Comment 19 Qian Qiao 2005-02-07 16:21:09 UTC
Created attachment 50682 [details]
Eclipse OSGI libraries ebuild.
Comment 20 Qian Qiao 2005-02-07 16:22:06 UTC
Created attachment 50683 [details]
Eclipse runtime libraries
Comment 21 Qian Qiao 2005-02-07 16:22:47 UTC
Created attachment 50684 [details]
JFace ebuild.
Comment 22 Scott Carr 2005-02-07 18:22:11 UTC
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.
Comment 23 Scott Carr 2005-02-07 19:04:50 UTC
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 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.
Comment 24 Scott Carr 2005-02-08 08:53:45 UTC
Can we split out eclipse-runtime and eclipse-osgi as seperate issues?
Comment 25 Qian Qiao 2005-02-08 09:47:23 UTC
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.
Comment 26 Saleem Abdulrasool (RETIRED) gentoo-dev 2005-10-01 16:56:16 UTC
Added an ebuild for now.  Please test.  It is hardmasked though.
Comment 27 Christoph Brill (egore) (RESIGNED) 2006-05-02 07:48:51 UTC
Tested on ~amd64, works fine (as long as I build swt without firefox).