stick's corner » java

Making a delicious coffee cake with openSUSE

Pavol Rusnak — Thu, 11 Nov 2010 14:19:40 +0000

What we need for our delicious openSUSE coffee cake:

300g Eclipse¹
200g IntelliJ Idea²
150g ground NetBeans³
1 baking Maven⁴
1/2 spoon Groovy⁵
1 cup of cold Java⁶
3 eggs
80g drawn butter
100g chocolate icing

¹ flour, ² sugar, ³ walnuts, ⁴ powder, ⁵ cinnamon, ⁶ coffee

Instructions:

Mix powdery ingredients in a bowl.
Add liquid ones as well and stir around well.
Bake in the oven and check regularly.
When ready take out the cake and let it cool down.
Put chocolate icing on the top and add some openSUSE magic.
Enjoy!

Oh no, wait!

There are some ingredients missing in our kitchen, ahem, I meant Factory. Currently we only have NetBeans and today I learned from Michal that it will be probably dropped as well, because some of its parts started to depend on Eclipse.

So my question is: is there anyone from our great openSUSE community who is willing to help with Java packaging? We have various related packages (Eclipse, IntelliJ Idea + their dependencies like Groovy or Maven) spread around various places in the Build Service (e.g. home:lkundrak:IDEA, Java:eclipse:Devel), but we would like to have them fixed and pushed to our devel project for Factory – Java:packages. This is the first and necessary step for including these tools into you beloved distribution. Some of the packages are probably obsolete so it might be better to get inspiration directly at our Fedora friends (you can use this package list and a little helper script to peek how do they do it). If you are interested in this, please do so! We will try to help you on opensuse-java mailing list or #opensuse-java IRC channel on Freenode.

Oh, I almost forgot one thing. The most active Java packager will get an openSUSE coffee cake done by yours truly and the openSUSE Boosters!

Scout: bash-completion, documentation, python indexes and Java demo

Pavol Rusnak — Wed, 25 Jun 2008 11:02:49 +0000

A lot has happened since the public release of scout. Blogpost registered more than 400 hits, Marek Stopka created bash-completion, Thomas Schraitle wrote docbook documentation and Michal Vyskocil prepared module for python and its indexes. Thank you all! I started a wikipage like Thomas suggested and indexed Packman repositories for their binaries.

Michal also prepared small demonstration video about using scout in java wrapper. The wrapper runs java application and greps stderr for exceptions. When NoClassDefFoundError/ClassNotFoundException is detected, the classname is taken to scout, which resolves it to package name, installs the package with zypper and tries to run application again! I like this idea pretty much. Michal is currently working on perl indexes and we will probably index also ruby and pkgconfig files.

Watch mentioned java demonstration video here:

or download it …

Scout released

Pavol Rusnak — Tue, 17 Jun 2008 10:25:02 +0000

Hooray! The first public version of Scout was just released. It is a simple tool which allows user to look for (not yet installed) packages using simple queries (e.g. which autoconf macros does the package contain, which Java classes are present inside or what binaries does the package provide). Scout is available in openSUSE BuildService in home:prusnak:scout project. If you would like to install and test it, follow these three steps:

add the following repositories:

zypper ar http://download.opensuse.org/repositories/home:/prusnak:/scout/openSUSE_11.0 scout
zypper ar http://download.opensuse.org/repositories/home:/prusnak:/scout/data scout-data

(change openSUSE_11.0 to your distribution if necessary)

install scout:
```
zypper in scout
```
add any of the index data you find attractive (only example – see scout wiki page for the whole list)
```
zypper in scout-bin-suse110
zypper in scout-java-suse110
```
Data package names are in format scout-module-repo. Indexes for autoconf macros are in autoconf packages, bin are indexed binaries and java are indexed java classes. Repository names are either distributions (sle10, suse101, suse102, suse103, suse110) or BuildService projects (jpackage17 for Java:jpackage1.7). Simple, isn’t it?

(Warning: Java indexes are pretty large – 5MB RPMs and around 30MB when installed.)

When you are ready, run scout without parameters to see the help. I think that the usage is pretty straightforward (nevertheless, I will try to create demonstration video soon). You can also try running scoutcsv or scoutxml – they are only symlinks, but they produce CSV or XML output, instead of table output.

I hope you will like it!

The next thing to do is to add support for ZYPP repositories (sat-solver files) in module for binaries, so user could query packages (even in the BuildService repositories) without installing any external index data. When this is done, it would be a piece of cake to replace the earlier implementation of command-not-found with the new one using scout as its backend. Unfortunately, this is not going to happen before the ZYPP bindings for Python (python-zypp) are fixed. (API has changed and it seems that only Ruby bindings are maintained.) I tried to fiddle with it (bugzilla), but I’m not a SWIG expert.