Hi *,
For a while I've been unable to use the built-in ant editor in
eclipse. Trying to open a build.xml file, eclipse reports an error
"Unable to create part: Ant Editor".
The log file contains the attached exception, which I believe is
related to the problem. I also think that maybe the n
hi all.
when packaging sun java 1.4.2 (probably others as well) with mpkg-j2sdk
and installing the resulting j2sdk package, mozilla/galeon stops working,
and reports this error on startup:
INTERNAL ERROR on Browser End: No manager for initializing factory?
System error?:: Success
this apperant
hi all.
when packaging sun java 1.4.2 (probably others as well) with mpkg-j2sdk
and installing the resulting j2sdk package, mozilla/galeon stops working,
and reports this error on startup:
INTERNAL ERROR on Browser End: No manager for initializing factory?
System error?:: Success
this apper
On Fri, 8 Aug 2003 15:44:30 +0200, Egon Willighagen <[EMAIL PROTECTED]>
wrote:
On Friday 08 August 2003 15:31, Matt Zimmerman wrote:
On Fri, Aug 08, 2003 at 03:26:34PM +0200, Egon Willighagen wrote:
> Right... and I understood from Hein's email that the sablevm package
> does this upon upgrade...
Thanks for the replies.
On Fri, 8 Aug 2003 15:44:30 +0200, Egon Willighagen <[EMAIL PROTECTED]>
wrote:
Hein, can you send the output of:
update-alternatives --display java
Here it is:
# update-alternatives --display java
java - status is manual.
link currently points to /usr/lib/j2sdk1.4/bin/ja
Hi
Every time I do an update, and there is a new version of sablevm (I
think), the alternatives system returns to "auto" mode and selects sablevm
as the default JVM, even though I have previously (manually) selected
j2sdk1.4 as the default.
Anyone know why this keeps happening?
Thanks,
Hei
On Fri, 08 Aug 2003 17:24:21 +0200, Hein Meling <[EMAIL PROTECTED]> wrote:
Should I report this as a bug in gij, or is this a problem with update-
alternatives? I mean, why should removing an alternative cause it to
revert to auto mode, unless the alternative being removed is the d
On Fri, 08 Aug 2003 17:24:21 +0200, Hein Meling <[EMAIL PROTECTED]> wrote:
Should I report this as a bug in gij, or is this a problem with update-
alternatives? I mean, why should removing an alternative cause it to
revert to auto mode, unless the alternative being removed is the d
On Fri, 8 Aug 2003 15:44:30 +0200, Egon Willighagen <[EMAIL PROTECTED]>
wrote:
On Friday 08 August 2003 15:31, Matt Zimmerman wrote:
On Fri, Aug 08, 2003 at 03:26:34PM +0200, Egon Willighagen wrote:
> Right... and I understood from Hein's email that the sablevm package
> does this upon upgrade...
Thanks for the replies.
On Fri, 8 Aug 2003 15:44:30 +0200, Egon Willighagen <[EMAIL PROTECTED]>
wrote:
Hein, can you send the output of:
update-alternatives --display java
Here it is:
# update-alternatives --display java
java - status is manual.
link currently points to /usr/lib/j2sdk1.4/bin/java
Hi
Every time I do an update, and there is a new version of sablevm (I
think), the alternatives system returns to "auto" mode and selects sablevm
as the default JVM, even though I have previously (manually) selected
j2sdk1.4 as the default.
Anyone know why this keeps happening?
Thanks,
Hein
other packages
> in unstable require a later version then the testing version. So I
> don't feel happy using the downgraded libc for long.
>
> Dave
>
>
> Hein Meling wrote:
> > Well, since you say that you cannot upgrade to 1.4.1 your only choice
> > seems t
Well, since you say that you cannot upgrade to 1.4.1 your only choice
seems to be to downgrade your libc to version 2.2.5. Alternatively,
maybe you could adhere to the new interface in java.sql.Connection?
- Hein
On Wed, 2002-10-23 at 06:16, Rupa Schomaker wrote:
> -BEGIN PGP SIGNED MESSAGE-
other packages
> in unstable require a later version then the testing version. So I
> don't feel happy using the downgraded libc for long.
>
> Dave
>
>
> Hein Meling wrote:
> > Well, since you say that you cannot upgrade to 1.4.1 your only choice
> > seems t
Well, since you say that you cannot upgrade to 1.4.1 your only choice
seems to be to downgrade your libc to version 2.2.5. Alternatively,
maybe you could adhere to the new interface in java.sql.Connection?
- Hein
On Wed, 2002-10-23 at 06:16, Rupa Schomaker wrote:
> -BEGIN PGP SIGNED MESSAGE-
The problem is the new libc recently made available in unstable. It
breaks a number of Java implementations, so the problem is not with
eclipse. The solution is to upgrade to SDK1.4.1, since also 1.4.0 and
1.3.x has this problem for both Sun and Blackdown distributions. The
alternative is to dow
The problem is the new libc recently made available in unstable. It
breaks a number of Java implementations, so the problem is not with
eclipse. The solution is to upgrade to SDK1.4.1, since also 1.4.0 and
1.3.x has this problem for both Sun and Blackdown distributions. The
alternative is to dow
On Sun, 2002-10-20 at 16:36, Pac wrote:
> I've just upgraded my binaries
>
> and now when I run ANT or Java I've got this error message
>
> Error occurred during initialization of VM
> Unable to load native library: /home/pac/jdk1.3.1_02/jre/lib/i386/libjava.so:
> symbol __libc_wait, version GLI
On Sun, 2002-10-20 at 16:36, Pac wrote:
> I've just upgraded my binaries
>
> and now when I run ANT or Java I've got this error message
>
> Error occurred during initialization of VM
> Unable to load native library: /home/pac/jdk1.3.1_02/jre/lib/i386/libjava.so: symbol
>__libc_wait, version GLIB
Juergen Kreileder wrote:
>
> Robbe <[EMAIL PROTECTED]> writes:
>
> > Hein Meling <[EMAIL PROTECTED]> writes:
> >
> >> # update-alternatives --display javac
> >> javac - status is auto.
> >> link currently points to /usr/lib/j2sdk1.
Juergen Kreileder wrote:
>
> Robbe <[EMAIL PROTECTED]> writes:
>
> > Hein Meling <[EMAIL PROTECTED]> writes:
> >
> >> # update-alternatives --display javac
> >> javac - status is auto.
> >> link currently points to /usr/lib/j2sdk1.
Robert Bihlmeyer wrote:
>
> Hein Meling <[EMAIL PROTECTED]> writes:
>
> > Setting up jikes (1.15-1) ...
> > update-alternatives: unable to make
> > /usr/share/man/ja/man1/javac.1.gz.dpkg-tmp a symlink to
> > /etc/alternatives/javac.ja.1.gz: No such file
Robert Bihlmeyer wrote:
>
> Hein Meling <[EMAIL PROTECTED]> writes:
>
> > Setting up jikes (1.15-1) ...
> > update-alternatives: unable to make
> > /usr/share/man/ja/man1/javac.1.gz.dpkg-tmp a symlink to
> > /etc/alternatives/javac.ja.1.gz: No such file
hi.
every once in a while (when there is some package to upgrade such as
jikes), i run into install problems with creating a symlink to ja man
pages.
below you'll find my most recent problem with this.
Setting up jikes (1.15-1) ...
update-alternatives: unable to make
/usr/share/man/ja/man1/j
hi.
every once in a while (when there is some package to upgrade such as
jikes), i run into install problems with creating a symlink to ja man
pages.
below you'll find my most recent problem with this.
Setting up jikes (1.15-1) ...
update-alternatives: unable to make
/usr/share/man/ja/man1/
Use mmake too, however, the debian package is an old version. Check the
website: http://www.tildeslash.com/mmake/ for the latest version.
Ciao,
Hein
Rob Hazlewood wrote:
I find mmake to be the best.. (available as woody package)
Although I still haven't tried ant
generates a perfectly useful mak
Use mmake too, however, the debian package is an old version. Check the
website: http://www.tildeslash.com/mmake/ for the latest version.
Ciao,
Hein
Rob Hazlewood wrote:
> I find mmake to be the best.. (available as woody package)
> Although I still haven't tried ant
>
> generates a perfectl
Egon Willighagen wrote:
> TODO:
> - make Debian package for dh_java
> - have dh_java output a "control" line
> - have dh_java output a classpath
> - read/comment and implement debian-java comments/wishes etc (hint, hint)
Just like to let you know that I'm looking forward to getting this, as I
thi
28 matches
Mail list logo
