Scala New Class Wizard

Hi Tim,

I've been looking into https://lampsvn.epfl.ch/trac/scala/ticket/2685
myself and managed to get past the obstacle you mention; it probably
makes sense for us to join forces, I'll get in touch with you
tomorrow, when I have access to my code changes.

Cheers,
Maciek

On Sat, Dec 5, 2009 at 3:13 AM, Tim Clendenen wrote:
> I am trying to create a new class wizard based on the one provided in the
> groovy eclipse plug-in, however I've run into a problem.  My attempts so far
> have made it as far as the the wizard being shown, but as soon as I enter a
> letter in the wizards Name text box, it results in the stack trace below.
>  I'm pretty new to plug-in development, so I was hoping someone could point
> me in the right direction so that I can hopefully debug it or at least file
> a competent bug report.
>
> Java Model Exception: Java Model Status [D.scala [in hello2 [in src [in
> scala-test]]] does not exist]
> at
> org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
> at
> org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
> at
> org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
> at
> org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
> at
> org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:193)
> at
> scala.tools.eclipse.javaelements.ScalaSourceFile.getCorrespondingElement(ScalaSourceFile.scala:87)
> at
> scala.tools.eclipse.javaelements.ScalaSourceFile.getType(ScalaSourceFile.scala:93)
> at
> org.eclipse.jdt.ui.wizards.NewTypeWizardPage.typeNameChanged(NewTypeWizardPage.java:1596)
> at
> scala.tools.eclipse.wizards.NewScalaClassWizardPage.typeNameChanged(NewScalaClassWizardPage.scala:78)
>
> Thanks for any help or suggestions.
>
> Tim
>
>
>

On Sat, Dec 5, 2009 at 9:51 AM, wrote:
> I've been looking into https://lampsvn.epfl.ch/trac/scala/ticket/2685
> myself and managed to get past the obstacle you mention; it probably
> makes sense for us to join forces, I'll get in touch with you
> tomorrow, when I have access to my code changes.

Yes, please do try and coordinate on this, and let me know how you get on.

Cheers,

Miles