Quick question. There seems to be at least 3 common ways I see java
being deployed on ubuntu:
1. download jdk binaries from sun, expand to some custom folder (eg
/home/bobj/java) and set path and JAVA_HOME accordingly
2. install 'official' oracle jdk java6 binaries with something like
'sudo apt-get install sun-java6-jdk' and switch between this and
openjdk with update-java-alternatives
3. go with openjdk
I think 1 is probably favoured by developers as it allows maximum
flexibility, working with different versions etc. Its what I tend to
do anyway
For server installs I think it makes much more sense to not fight
against the package system, so 2 is probably most common. I'm curious
about 2 and 3. Does anyone have any concrete (ie not 3rd hand
hearsay) experience of running dhis on openjdk?.
It seems to work okay for me but causes problems with jasper reports due to missing fonts. I couldn’t be bothered to resolve it and followed 2 instead. By far the easiest route i have found.
It seems to work okay for me but causes problems with jasper reports due to
missing fonts. I couldn't be bothered to resolve it and followed 2 instead.
By far the easiest route i have found.
Just chatting to Knut about this.
me: ah. bloody fonts.
me: historically I have found fonts are the biggest hurdle to large
scale gov FOSS migration projects. The hidden little IP landmines
which break everything
It was also the primary difference between staroffice (sun commercial)
and openoffice. The proprietary font packs.
Maybe we need to investigate these jasper fonts a bit more closely.
Getting font liberated is a good thing.
Cheers
Bob
···
On 25 September 2011 07:37, Jason Pickering <jason.p.pickering@gmail.com> wrote:
On Sep 25, 2011 8:06 AM, "Bob Jolliffe" <bobjolliffe@gmail.com> wrote:
Quick question. There seems to be at least 3 common ways I see java
being deployed on ubuntu:
1. download jdk binaries from sun, expand to some custom folder (eg
/home/bobj/java) and set path and JAVA_HOME accordingly
2. install 'official' oracle jdk java6 binaries with something like
'sudo apt-get install sun-java6-jdk' and switch between this and
openjdk with update-java-alternatives
3. go with openjdk
I think 1 is probably favoured by developers as it allows maximum
flexibility, working with different versions etc. Its what I tend to
do anyway
For server installs I think it makes much more sense to not fight
against the package system, so 2 is probably most common. I'm curious
about 2 and 3. Does anyone have any concrete (ie not 3rd hand
hearsay) experience of running dhis on openjdk?.
I have been running DHIS on openJDK 7 locally for a while without any
trouble. One way to dodge font issues is to stay with standard java
"logical" fonts such as serif and sans-serif in jasper reports and
elsewhere.
It seems to work okay for me but causes problems with jasper reports due to
missing fonts. I couldn’t be bothered to resolve it and followed 2 instead.
By far the easiest route i have found.
Just chatting to Knut about this.
me: ah. bloody fonts.
woo…it sounds good…i guess these are some of the official words commonly used in corridore of WHO Headquater, Geneva. Is it some thing new font…i have never heard it before…!
Bod could you let us know what kind of these fonts are…we are keen to know about it…!
me: historically I have found fonts are the biggest hurdle to large
scale gov FOSS migration projects. The hidden little IP landmines
which break everything
It was also the primary difference between staroffice (sun commercial)
and openoffice. The proprietary font packs.
Maybe we need to investigate these jasper fonts a bit more closely.
Getting font liberated is a good thing.
For those who didn't already know, openjdk 7 is not yet part of
official ubuntu repositories, the easiest way to try it out is to add
a repo from one of the ubuntu devs:
I think its better not to contribute any way any thing to the discussion and only listen rather than
using such a low profile words on a standard open source international mailing list like ‘dhis2-dev’ .
its my humble request from India…people should not use freely such a pretty very low profile words like ‘bloody’ etc on this list. We are not expecting such thing here on this standard list. People should follow some kind of discipline while writing anything on this list. Any way, i will glad to contribute soon some thing very good to DHIS2 as a developer that users will like most according to my real experience while working with DHIS2 in their offshore development center, new Delhi as well as in about 4 years of DHIS2 field implementation extraction. Unfortunately, these days little bit busy in development of real expert system for some nuclear power plant project.
Any way thanks for your wonderful suggestion regarding posting which is not so easy to digest…
Regards,
Brajesh.
India
···
On Mon, Sep 26, 2011 at 1:34 PM, Knut Staring knutst@gmail.com wrote:
Brajesh,
I don’t see you contributing in any way to the project or the discussion - please refrain from posting such things to the list.
It seems to work okay for me but causes problems with jasper reports due to
missing fonts. I couldn’t be bothered to resolve it and followed 2 instead.
By far the easiest route i have found.
Just chatting to Knut about this.
me: ah. bloody fonts.
woo…it sounds good…i guess these are some of the official words commonly used in corridore of WHO Headquater, Geneva. Is it some thing new font…i have never heard it before…!
Bod could you let us know what kind of these fonts are…we are keen to know about it…!
me: historically I have found fonts are the biggest hurdle to large
scale gov FOSS migration projects. The hidden little IP landmines
which break everything
It was also the primary difference between staroffice (sun commercial)
and openoffice. The proprietary font packs.
Maybe we need to investigate these jasper fonts a bit more closely.
Getting font liberated is a good thing.
