Hi Mike,
ok, I have uninstalled WOLips 3.5.5997 (which had been installed over a
previous version, I think 3.5.5990 but I'm not sureof this version) this
morning and updated to the new version and it seems to go fine now, so I
don't know what didn't work but it is now fixed.
Thanks also for the non-null check, I don't have issues anymore.
Maybe with some additional info you will see what it's about, but it
seems that the conversion went well.
The classpath entry for WO was the following:
<classpathentry kind="con"
path="org.objectstyle.wolips.WO_CLASSPATH/DenaliComponents/DenaliCore/DenaliDBUtils/JavaEOAccess/JavaEOControl/JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaWOExtensions/JavaXML"/>
but it has properly updated to the (I guess) new format:
<classpathentry kind="con" path="WOFramework/JavaWOExtensions"/>
<classpathentry kind="con" path="WOFramework/JavaEOAccess"/>
<classpathentry kind="con" path="WOFramework/JavaEOControl"/>
<classpathentry kind="con" path="WOFramework/JavaFoundation"/>
...
while the project contains the following nature:
<nature>org.objectstyle.wolips.incrementalframeworknature</nature>
and include this build command:
<buildCommand>
<name>org.objectstyle.wolips.incrementalbuilder</name>
<arguments>
</arguments>
</buildCommand>
Anyway, it seems to work all fine now.
Thanks,
Guillaume
Le 14/10/2009 15:48, Mike Schrag a écrit :
> for the bottom exception, it looks like you have a messed up install
> of WOLips ... i've never seen anything like this before. I use
> Eclipse 3.5 for all my work, and the only problem is that Eclipse
> performance sucks in 3.5 -- i'm not holding back WOLips 3.5 because of
> a WOLips problem.
>
> for the other one exception, i put in a defensive null check, but I
> don't really know why it's failing. it's upgrading an old .classpath
> file to the new format, but I don't know why it's failing in this
> way. it seems to imply that maybe you don't have a wolips nature on
> your project in the .project file, but it's hard to tell.
>
> On Oct 14, 2009, at 9:16 AM, Guillaume Polet wrote:
>
>> Hi list,
>>
>> It's been a while since I had followed this mailing list, mainly
>> because my company went bankrupt. So anyway, I am now back on some
>> WebObject dev, and of course WOLips is a must.
>> Unfortunately, for some reason, the guy who has set up the
>> CVS/Hudson/Artifactory environment has forced us to use Eclipse 3.5
>> and so I have to use the so-called unstable build.
>>
>> So I was wondering how far was the future stable build for Eclipse
>> 3.5. Would it come any time soon?
>> So far, I have been working with the build 3.5.5997 and it mostly works.
>> However, with some old projects I run into two issues which I have
>> listed below.
>> My environment is:
>> OS: WinXP
>> Java: JDK 1.6
>> Eclipse J2EE Edition 3.5
>> Plugins: WOLips 3.5.5997, M2Eclipse, Jadclipse, Veloceclipse
>>
>> Is there a fix I can do myself in my code or configuration or should
>> I wait for a new release compatible with 3.5.
>>
>> Many thanks in advance,
>>
>>
>> Guillaume Polet
>>
>> First issue:
>> java.lang.NullPointerException
>> at
>> org.objectstyle.wolips.jdt.classpath.WOFrameworkContainerInitializer.convertProjectReferencesToFrameworkReferences(WOFrameworkContainerInitializer.java:241)
>>
>> at
>> org.objectstyle.wolips.jdt.classpath.WOFrameworkContainerInitializer.convertOldClasspathContainer(WOFrameworkContainerInitializer.java:170)
>>
>> at
>> org.objectstyle.wolips.jdt.classpath.WOFrameworkContainerInitializer.initialize(WOFrameworkContainerInitializer.java:130)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2608)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2514)
>>
>> at
>> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2554)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1773)
>>
>> at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3410)
>> at
>> org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35)
>>
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>> which is really anoying because it prevents from seing anything
>> located within a WO project through the package explorer (I have to
>> go with the Navigator)
>> I think the stack below is just another form of the same issue:
>> java.lang.NullPointerException
>> at
>> org.objectstyle.wolips.jdt.classpath.WOFrameworkContainerInitializer.convertProjectReferencesToFrameworkReferences(WOFrameworkContainerInitializer.java:241)
>>
>> at
>> org.objectstyle.wolips.jdt.classpath.WOFrameworkContainerInitializer.convertOldClasspathContainer(WOFrameworkContainerInitializer.java:170)
>>
>> at
>> org.objectstyle.wolips.jdt.classpath.WOFrameworkContainerInitializer.initialize(WOFrameworkContainerInitializer.java:130)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2608)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2514)
>>
>> at
>> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2554)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1773)
>>
>> at
>> org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2652)
>> at
>> org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2578)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2679)
>>
>> at
>> org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1866)
>>
>> at
>> org.eclipse.jdt.internal.core.DeltaProcessingState.getRootInfos(DeltaProcessingState.java:304)
>>
>> at
>> org.eclipse.jdt.internal.core.DeltaProcessingState.initializeRoots(DeltaProcessingState.java:249)
>>
>> at
>> org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1971)
>>
>> at
>> org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470)
>>
>> at
>> org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291)
>>
>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>> at
>> org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
>>
>> at
>> org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
>>
>> at
>> org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:297)
>>
>> at
>> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:136)
>>
>> at
>> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>> The second one happens almost on every project, each time I try to
>> build something (a change in a Java class of WO project, e.g.):
>> java.lang.Exception: The specified class for ResourceManager
>> (org.apache.velocity.runtime.resource.ResourceManagerImpl) does not
>> implement org.apache.velocity.runtime.resource.ResourceManager;
>> Velocity is not initialized correctly.
>> at
>> org.apache.velocity.runtime.RuntimeInstance.initializeResourceManager(RuntimeInstance.java:589)
>>
>> at
>> org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:241)
>>
>> at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java:116)
>> at
>> org.objectstyle.wolips.templateengine.TemplateEngine.init(TemplateEngine.java:126)
>>
>> at
>> org.objectstyle.wolips.templateengine.ProjectTemplate.createProjectContents(ProjectTemplate.java:236)
>>
>> at
>> org.objectstyle.wolips.builder.internal.WOIncrementalBuilder.createInfoPlist(WOIncrementalBuilder.java:231)
>>
>> at
>> org.objectstyle.wolips.builder.internal.WOIncrementalBuilder.invokeOldBuilder(WOIncrementalBuilder.java:181)
>>
>> at
>> org.objectstyle.wolips.core.resources.internal.build.Builder.invokeOldBuilder(Builder.java:205)
>>
>> at
>> org.objectstyle.wolips.core.resources.internal.build.Builder.build(Builder.java:128)
>>
>> at
>> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
>>
>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
>>
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
>>
>> at
>> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
>>
>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
>>
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
>>
>> at
>> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
>>
>> at
>> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
>>
>> at
>> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Thu Oct 15 2009 - 03:56:59 EDT