I saw the following thread about F7 plans and noticed we don't have any
goals for gcj/eclipse/swt/java-gnome/etc
So here are some ideas, deadlines and dependencies that might be nice to
look at for F7 for the various stacks that make up the fedora-devel-java
world. Please reply if you are working on any of this, if I am saying
something silly/wrong or if there are more stack/application issues that
you think are important for F7.
The "important dates" are:
- January 23 - Test1 Development Freeze
- February 20 - Test2 Development Freeze
- March 15 - Test3 Development Freeze
- Release in April
Test2 is just before Fosdem. And since all features should be in by
then, it would be nice to try and create a liveCD with all "our
features" on it to show off at Fosdem (Feb 24/25, Brussel, Belgium).
- 1.5 language & library support in gcj
This seems to be the biggest and most intrusive upgrade. But starting
this early seems like a very good idea. Upstream is cleaning up some
last issues. And it needs lots of testing. Would be good if something
can be cooked up for Test1. Needs help from gcc-toolchain people.
- Separate libgcj-rpm. Would be really nice so we can update the core
class libraries separate from the core gcc compilers. Should also help
with updates/dependencies since libgcj provides the mozilla plugin now
and the awt libraries depend on gtk+. Would be nice if this can be
done before Test2 so we can test an upgrade. Again needs help from
The biggest issue with this, if the 1.5-stack goes through is that
gjdoc isn't 1.5 safe. If we cannot easily update gjdoc, then maybe
sinjdoc could be investigated as replacement.
(Do we also need updates for javap and javah replacements?)
- eclipse/swt/rcp stack
3.2 seems already good to go, and 3.3 will not come out till the
middle of 2007. Azureus, RSSOwl also already seem updated.
Andrew Overholt already has written down some plans for the future:
Maybe some work can be done to support the JDWP work in libgcj to
get a little debugging going? And it would be nice to make sure that
the ecj from eclipse and that from the gcj 1.5-stack match up.
There are some rumors about a upgrade/rewrite, but nothing concrete as
far as I have seen. If there is a rewrite that might cause some extra
work for applications like Frysk.
- gcj-compiled DocBook toolchain
It seems we have made lots of progress with FOP and Batik since the
last discussion about this:
Does anybody know where we are with that at this time?
Would be nice to coordinate with the fedora-docs-list if we can
- jpackage. Does it make sense to upgrade all packages to jpp 1.7 if the
1.5-stack goes in?
- OpenOffice 2.2
Listed here since it does have some parts written in java. 2.2 comes
out end of February. Probably needs retesting with the gcj-stack. I
don't know if there are new java language/library dependencies.
Some things that would be nice, but that are probably a lot of work,
maybe better left for Fedora *, unless someone volunteers of course! :)
Still lots missing. Hopefully at Fosdem we will learn a bit more about
the encumberments and when which parts of the core libraries will be
liberated fully. But it might be nice to see if javac could be
packaged. Or maybe a brave soul make hotspot work with classpath?
The Micro Edition world seems to really have gotten a boost from the
GPL release of PhoneME. A lot of this is pretty early access. But it
would be nice to have parts of this supported to show that Fedora is
also a nice platform to developer for java-based mobile devices.
- JBoss application server, SEAM stack
Not tried yet. Parts like tomcat are already packaged. If we can get
the 1.5-stack going it makes sense to look at this a bit closer. Maybe
other parts can be lifted from jpackage?
I tried this recently, but it seems still very tight to the Sun java
implementation and I was unable to fully start it up on the free
stack. But some dependencies like JavaHelp have been liberated
(gpl+exception) now (and entered jpackage recently). Also it isn't
clear whether the current license (CDDL) is acceptable (it seems
unacceptable to Debian).
- JOGL and WW2D should work, but I haven't done any testing recently.
- japitools should really be packaged and somehow be tied in with the
build system so developers/packagers can get an easy overview of
whether or not a library upgrade is binary compatible or not.
I am sure there is a lot missing. And as you saw none of the items above
have real deadlines or people responsible, etc. So please feel free to
reply with corrections add those yourself :)
Does anyone on this list have working JacORB packages for FC6 (using the Free
Java stack, i.e. GCJ etc.)? I'm interested in JacORB because a class I'm taking
at the university uses it.
I tried building a package by:
* reconstructing the no longer available jacorb-2.2-3jpp_8fc:
- I started from jacorb-2.2-3.1mdk, which is essentially jacorb-2.2-3jpp_3fc
- I removed the stuff apparently added by Mandriva (changelog entry,
conditionalization of GCJ support)
- I applied all the patches from the fedora-cvs-commits list leading up to 8fc
- I fixed the whitespace in the GCJ 4.1 patch so it actually applies, because
the mailing list software mangled the tabs in the patch to spaces
* bumping the release, ending up with this:
(This is an 8 KB nosrc RPM, I didn't include the source tarball for space
Unfortunately, this _does not build_ under FC6. Judging from the error output,
it tries to use the wrong org.omg.CORBA classes (the libgcj ones), and I can't
seem to fix that. I verified that the gcj41 patch is applied, I tried setting
both classpath and bootclasspath, and also adding this:
None of that works. So help from the experts would be appreciated.
I'm using gcj to compile some java and I'm not getting the results I'd
expect out. Do I file this as usual in BZ or should I check here first
if it's an oddity which doesn't need reporting?
"Mmmmmmmm....Shakira geschmiert mit schokolade" sagt Homer
How does one get the latest Sun j2ee and jpackage to play together? I
can find writeups for the Sun jdk, but don't seem to find any for
I think I want "JDK 5.0 Update 9 with Java EE" on
Charles Curley /"\ ASCII Ribbon Campaign
Looking for fine software \ / Respect for open standards
and/or writing? X No HTML/RTF in email
http://www.charlescurley.com / \ No M$ Word docs in email
Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
* Bhupendra Bhardwaj <bhupendra229(a)gmail.com> [2006-12-14 18:41]:
> Other than the jar files(compilation dependencies), the platform
> specific files for runtime (dll, so etc) will be required. Those
> runtime bundles should also be available to download, if we want to
> package everything together.
The SWT DSOs are *in* the SWT fragment (platform-specific part of the
plugin ... the org.eclipse.swt.gtk.linux.x86_<blah>.jar) and will be
extracted at run-time. If you're going to package this up as an RPM for
your Fedora/RHEL users, you'll want to depend upon eclipse-rcp instead
of bundling the runtime. Look at the RSSOwl or Azureus specfiles in
Fedora Extras CVS  for examples. Those aren't strict RCP apps, but
they're close and will give you something to work from.
On Thu, 2006-12-14 at 18:32 +0000, Bhupendra Bhardwaj wrote:
> The eclipse plugins in maven repository are available for win32 only.
This seems like the root of your current problem. If you are using
maven to build and it pulls its deps from some repo somewhere, then your
dependencies need to be in that repo, right? However, later on you say:
> The downloading of required runtime binary from eclipse is required
> because the platform specific eclipse plugins are not available in
> maven repository, so we can't pachage everything together for all
> platforms using maven.
So what if they *were* in the maven repo? Would it be able to do
per-arch/os/ws builds? SWT -- and by extension RCP -- is
platform-dependent. How does maven handle this situation?
On Thu, 2006-12-14 at 11:22 -0500, Carl Trieloff wrote:
> I have cross posted the lists ... we have a mgnt console that is built
> on RCP and would like
> to get it also working on Linux.
Why is there a hard requirement on the win32 bundle? Whatever is
starting the management console should determine what ws.os.arch triplet
(ex. win32.win32.x86 or gtk.linux.ppc) is needed. It appears that the
launcher may be hard-coding for win32. But perhaps that's just my naive
reading of the situation.
I don't know anything about maven. Sorry.
I've just found out Eclipse hangs on Fedora 6 when triggering the native GTK
file open dialog (when using "open file" or browsing directories). Happens
on GCJ or Sun JDK 1.5 with both Fedora Eclipse and eclipse.org versions.
Anyone familiar with this problem? Suggestions where it should be reported?
Andrew Overholt suggested I ask here for help with this.
One of the really neat things about developing any Java program using
Classpath in Fedora is the integration of Classpath source in the rpm,
and how it integrates with Eclipse. This is great as it allows you to
browse the Classpath code under the api with F3 (or Right Click->Open
Declaration). We'd like to do the same for Java-GNOME and Frysk. Is
there a Wiki page, guide .. or general advice to accomplish this as it
is done via the Classpath rpm?
I just created a wiki page for packaging tasks that need to be done for
the Eclipse Linux Project:
There is a section for Fedora Eclipse and for common tasks. Any help
with with these tasks would be appreciated, just add a note to let
everyone know what task you plan on doing. Also, feel free to add
tasks / ideas as you see fit. To edit the wiki page, just use your
eclipse.org bugzilla account.