Re: [Jalopy-devel] Forte for java 4 and jalopy

[Marco H. <dev...@hu...>]

>> >Ok: I tried a fresh reinstall of the whole IDE (which is rather buggy,
>> >but since I'm in the beta test program I use it anyway): jalopy has
>>
>> It worked? Did all the menu items appear? (As outlined in the manual)

>Uhm... not sure of that: I have always seen two menu items appearing in FFJ
>after installing jalopy: the "jalopy options" one in the "tools" menu, and
>the "reformat" one in the build menu. I was able to modify the options

FYI, I've attached screenshots showing *all* items that should be
available
(depending on the calling context).

>(although not able to load the options file I saved with the previous
>version), and then to start a couple of reformats (on rather large java
>files) which correctly worked.

Ok. At least that works reliable.

>> >correctly worked one or two times. Then, with apparently no reason
>> >(don't remember if I had a lockup of some sort), I began receiving this

The reason are the additional modules you've installed! It worked
directly after the installation and stopped functioning after the
installation of a module with another (older) Log4J library.

>> Did you read the message
>> http://sourceforge.net/forum/message.php?msg_id=1582984? Is Jalopy the
>> only module you have installed (clean setup...)?

>Uhm... didn't read that one: it is true than when I started jalopy it was
>probably right after the reinstall of forte. After Jalopy I installed
>refactorit (a not-so-good refactoring module which I could try turning off),
>AJDE (aspectj development environment) and systinet wasp developer 4 beta (a
>very well done web services development tool). It seems refactorit does use
>antlr, but I see they use versions of the libraries with different package
>names, I think to solve class loading issues (their antlr package is
>"rantlr"). Furthermore I don't know if this is a problem of classes already
>loaded: for log4j there is a 100% chance that the jar has already been
>loaded by the ide in a different version (I have one in
>%FORTE_HOME%/lib/ext, and it is a 1.1.3 version) but the error I have is a

This should be the problem. What module did install something here?
Module depend libs should go into "modules/ext"... Libscontained in
/lib/ext  will go in the global classpath... Or does FFJ ships with
Log4J 1.1.3?

>Wed Jun 05 09:49:12 CEST 2002: java.lang.NoClassDefFoundError:
>java.lang.NoClassDefFoundError: org/apache/log4j/Logger from
>de.hunsicker.jalopy.plugin.netbeans.NbPlugin@c7141c
>I think this can't deal with classes already loaded, can it? It seems more
>of a class in the jalopy jar that can't be loaded. Or is it possible than
>the classloader of netbeans modules is only able to load classes of a
>specific package from a single jar?

My guess here is that this is the NetBeans classloading scheme: Never
load a package twice.

>Should I try removing the 1.1.3 log4j

Either remove it but better would be to install the latest Log4J
release (1.2.3). 

>jar and replacing it with jalopy's one? I'm a little afraid of messing up
>the ide more than it is (every day I dream about starting to use a different

I need to learn more about the NetBeans classloading. Maybe I even have
to use a custom classloader to avoid issues like these.

>ide, such as eclipse or idea but, you know, I use netbeans since when it was
>a wonderful czech all-java ide in the 1.0 version...).

That's the way we work ;-) I don't know NetBeans that much. Actually,
developing the Plug-in was my first encounter with NetBeans. From the
developer perspective quite a satisfying experience...

Cheers,
Marco