Since this is a Java method, you can try opening the Java console
(should be in the tools menu) before doing the publish. This should show
you the stack from the exception. The only thing I can think of as a
likely culprit is if you have changed your classpath or put classes into
your custom directory that are in conflict with some of the classes that
we use in the Editor. I once saw something like this from someone that
had some classes from an old install in their custom directory and we
crashed because of the mix of old and new classes.
But if it is not something obvious like that, you should probably report
this to TPS pretty soon.
John Dreystadt
Software Development Director
Arbortext - PTC
734-352-2835
-
