On Tue, 04 Sep 2007 14:34:18 -0500, Todd Chambery wrote:
I did a clean unpack of the 0,6M2 build and installed the Europa release
of the WST, but when I started up the Work Items view had thrown an
exception.

Is the WTP known to be incompatible?

I don't know about WTP as a whole but I've installed WST through the
update manager on M2 using the Europa update site without any problems.

Could you provide a stack trace?

Regards,
Rem

Todd Chambery wrote:
Remy Chi Jian Suen wrote:
On Tue, 04 Sep 2007 14:34:18 -0500, Todd Chambery wrote:
I did a clean unpack of the 0,6M2 build and installed the Europa
release of the WST, but when I started up the Work Items view had
thrown an exception.

Is the WTP known to be incompatible?

I don't know about WTP as a whole but I've installed WST through the
update manager on M2 using the Europa update site without any problems.

Could you provide a stack trace?

Regards,
Rem

Hi Rem,

I checked the Web Tools box (I can't remember the exact name),
selecting all four sub-bits and their required packages. When I
clicked the popup to restart, TeamConcert did not come up. Attached
is the stack trace from the workspace log,

I should mention this is different from the error-ed view I got
running the Jazz client in Linux.

Todd


I think in order to get WTP to install/work properly, you need to
download and unzip the whole EMF SDK. TeamConcert ships with a subset of
EMF, not the entire thing, and WTP requires more than our subset provides.

Hope this helps.

james

Hi Todd,

On Tue, 04 Sep 2007 20:06:42 -0500, Todd Chambery wrote:
I should mention this is different from the error-ed view I got running
the Jazz client in Linux.

For this view error, I recommend that you restart Team Concert with the
'-clean' argument...

./TeamConcert -clean

...or whatever the binary is called. I have seen this problem before. It
occurred to after installing WST and then choosing to restart after the UM
directly. This happened to me on Windows XP. If I chose not to restart,
and to restart it manually with the -clean argument, the problem is fixed.

It is rather odd because I have always been under the assumption that
restarts invoked by the UM would be identical to a -clean...but apparently
not.

Root exception:
java.lang.NoClassDefFoundError: org.apache.log4j.Category
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:66)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:127)

Could it be possible that you have two log4j bundles and it is causing
problems? I don't know how smart the UM is with regards to this.

Regards,
Rem