[Texo] generation IllegalStateException [message #1622438] |
Wed, 18 February 2015 08:54  |
Eclipse User |
|
|
|
I created a single Class in my test ecore and it throws an IllegalStateException when I select the Texo "Generate Model Code". I am using Kepler SR2 on OSX with a 64bit JVM V1.7.0_67. I attach the simple ecore and the stacktrace. The ecore looks fine not sure what the cause is for such a simple ecore model.
Texo version:
EMFT Texo (Incubation) 0.9.0.v201501182340 org.eclipse.emf.texo.feature.group Eclipse Modeling Project
Here is the root cause.
at org.eclipse.emf.texo.generator.SourceMerger.merge(SourceMerger.java:85)
at org.eclipse.emf.texo.generator.MergingOutputHandler.beforeWriteAndClose(MergingOutputHandler.java:63)
at org.eclipse.xpand2.output.Outlet.beforeWriteAndClose(Outlet.java:98)
at org.eclipse.xpand2.output.FileHandleImpl.writeAndClose(FileHandleImpl.java:135)
at org.eclipse.xpand2.output.OutputImpl.closeFile(OutputImpl.java:171)
at org.eclipse.emf.texo.generator.ArtifactGenerator.run(ArtifactGenerator.java:99)
... 9 more
Caused by: java.lang.IllegalArgumentException
at org.eclipse.jdt.core.dom.ASTParser.<init>(ASTParser.java:226)
at org.eclipse.jdt.core.dom.ASTParser.newParser(ASTParser.java:125)
at org.eclipse.emf.texo.generator.ImportResolver.setSource(ImportResolver.java:482)
at org.eclipse.emf.texo.generator.SourceMerger.organizeImports(SourceMerger.java:147)
at org.eclipse.emf.texo.generator.SourceMerger.merge(SourceMerger.java:77)
... 14 more
[Updated on: Wed, 18 February 2015 09:01] by Moderator
|
|
|
|
|
|
Re: [Texo] generation IllegalStateException [message #1623934 is a reply to message #1623848] |
Thu, 19 February 2015 07:32  |
Eclipse User |
|
|
|
Yeah I have the same thing when upgrading, I have a txt document with all the update sites I need to visit to get a new
eclipse up and running...
gr. Martin
On 19-02-15 12:13, David Wynter wrote:
> Thank you Martin,
>
> It work well now.
> I had realised and started the upgrade to Luna, but it takes a long time to source and install all the plugins for a new
> version when you use a lot of plugins. Pity there is not an analysis of your plugins for an Eclipse version and an
> export, which then can trigger an import on the new version of Eclipse installed which works out what version of all of
> those plugins are need to install in the new version of Eclipse.
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxx - mtaal@xxxxxxxx
Web: www.springsite.com - www.elver.org
|
|
|
Powered by
FUDForum. Page generated in 0.18835 seconds