Wow, I had no idea. I do have those errors that Aaron has in my log
file. I haven't yet had to actually use the Jupiter plugin for a code
review (after I got Eclipse 3.1.0) so I have no idea what happens if I
try to use it though. Looks like it has to do with Eclipse 3.1 and not
Java5?
~Julie
Philip Johnson wrote:
I think Julie and Austen are using java 1.4 and Eclipse 3.1.0 and not
getting these errors. Julie/Austen, can you confirm? If so, it's a
Java5 issue.
Cheers,
Philip
--On Wednesday, August 31, 2005 6:40 PM -1000 Aaron Kagawa
<[EMAIL PROTECTED]> wrote:
Hey Guys,
I've found some errors in my eclipse after updating today. I'm using
Eclipse 3.1.0 and Java 1.5.
=======================================
Errors with Jupiter and Hackystat Jupiter Sensor:
I fired up Eclipse today and seen an error in the error log. I then
updated the Hackystat sensors and continued to see the errors. Here
is a
copy of my log file
<http://csdl.ics.hawaii.edu/~kagawaa/eclipse-errorlog.log>. I had to
disable both plugins: Jupiter and the Jupiter Sensor. What would be
good
to know is if Eclipse 3.1.0 and Java 1.4 works with these plugins.
!ENTRY org.eclipse.core.runtime 4 2 2005-08-29 23:02:37.906
!MESSAGE Problems encountered starting up plug-in:
"org.osgi.framework.BundleException: Exception in
org.hackystat.stdext.sensor.eclipse.jupiter.JupiterSensorPlugin.start()
of bundle org.hackystat.jupiter.". !STACK 0
org.osgi.framework.BundleException: Exception in
org.hackystat.stdext.sensor.eclipse.jupiter.JupiterSensorPlugin.start()
of bundle org.hackystat.jupiter. at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator
(BundleContextImpl.java:1013)
!ENTRY org.eclipse.ui 4 0 2005-08-31 18:14:43.812
!MESSAGE java.lang.ExceptionInInitializerError
!STACK 0
java.lang.ExceptionInInitializerError
at
csdl.jupiter.event.ReviewSelectionListener.selectionChanged(ReviewSelecti
onListener.java:50)
=======================================
Minor problem with hackyInstaller eclipse configuration:
the hackyInstaller output folder is "bin" instead of "build/classes"
like
all the other modules.
thanks, aaron
