Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » GMF (Graphical Modeling Framework) » Generating diagram code in build process
Generating diagram code in build process [message #230926] Thu, 21 May 2009 09:16 Go to next message
chris is currently offline chrisFriend
Messages: 72
Registered: July 2009
Member
Hi,

right now, I'm working on setting up a build process for my (partly
GMF-based) tooling. One step of that process should be to generate the
according diagram plug-ins (which I can do since all customizations are
either in a separate plug-in, implemented through dynamic templates, or
done using the GMFTools stuff (see http://code.google.com/p/gmftools/).

I've found two related threads in this newsgroup ("generating diagram
code from a headless build", "Generating Diagram Code from an Ant
Script") which seem to imply that this is not possible. But it's hard to
believe that nobody out there is doing this :-)

So, if my assumption is correct, can anybody share his/her experiences
with that problem? Preferably incorporating the GMFTools process...

Thanks in advance,
Chris
Re: Generating diagram code in build process [message #231031 is a reply to message #230926] Fri, 22 May 2009 02:35 Go to previous messageGo to next message
Peter Nehrer is currently offline Peter NehrerFriend
Messages: 241
Registered: July 2009
Senior Member
Hi Chris,

I actually put together a small plugin with an Ant task that run GMF's
codegen. E.g.,

<project name="Generate Diagram Code" default="run"
xmlns:gmf="http://ecliptical.ca/gmf/ant">
<target name="run">
<gmf:GenerateDiagramCode
gmfgenPath="org.eclipse.emf.edit/model/Tree.gmfgen"/>
</target>
</project>

Other supported attributes are ignoreLoadErrors and
ignoreValidationErrors (both boolean).

I haven't had the time to publicize it in any way but you can get it
from my update site at
http://www.eclipticalsoftware.com/updates/site.xml (under the GMF
category). Version 0.9.0 is for Europa and version 1.0.0 is for Ganymede
and later. Hope it works for ya.

--Peter

chris wrote:
> Hi,
>
> right now, I'm working on setting up a build process for my (partly
> GMF-based) tooling. One step of that process should be to generate the
> according diagram plug-ins (which I can do since all customizations are
> either in a separate plug-in, implemented through dynamic templates, or
> done using the GMFTools stuff (see http://code.google.com/p/gmftools/).
>
> I've found two related threads in this newsgroup ("generating diagram
> code from a headless build", "Generating Diagram Code from an Ant
> Script") which seem to imply that this is not possible. But it's hard to
> believe that nobody out there is doing this :-)
>
> So, if my assumption is correct, can anybody share his/her experiences
> with that problem? Preferably incorporating the GMFTools process...
>
> Thanks in advance,
> Chris
Re: Generating diagram code in build process [message #235692 is a reply to message #231031] Thu, 09 July 2009 06:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: aurelien.pupier.esial.net

Hi Peter,

I tried your plug-in with

<gmf:GenerateDiagramCode gmfgenPath=" ${buildDirectory}/plugins/org.ow2.jasmine.design.diagram/mod el/jasmine.gmfgen "/>

but it can found the gmfgen file :

org.eclipse.core.runtime.CoreException: Model loaded with errors. uri=platform:/resource/D:/build/plugins/org.ow2.jasmine.desi gn.diagram/model/jasmine.gmfgen
at ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:60)
at ca.ecliptical.gmf.ant.tasks.GenerateDiagramCode.execute(Gene rateDiagramCode.java:53)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
at org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
at org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298 )
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:623)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:495)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)
at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Res ource.java:317)
at org.eclipse.core.internal.resources.Resource.checkAccessible (Resource.java:194)
at org.eclipse.core.internal.resources.File.getContents(File.ja va:296)
at org.eclipse.core.internal.resources.File.getContents(File.ja va:287)
at org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl$WorkbenchHelper.createPlatformResourceInputStream(Pla tformResourceURIHandlerImpl.java:204)
at org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl.createInputStream(PlatformResourceURIHandlerImpl.java :448)
at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterIm pl.createInputStream(ExtensibleURIConverterImpl.java:301)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:1212)
at org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.inte rnalLoad(ModelLoadHelper.java:139)
at org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.<init >(ModelLoadHelper.java:130)
at ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.loadGenMo del(GenerateDiagramCodeOperation.java:110)
at ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:58)
... 62 more
Contains: Resource '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen' does not exist.


The file exists I'm sure.
I'm on Win XP.

Any idea?


Peter Nehrer a écrit :
> Hi Chris,
>
> I actually put together a small plugin with an Ant task that run GMF's
> codegen. E.g.,
>
> <project name="Generate Diagram Code" default="run"
> xmlns:gmf="http://ecliptical.ca/gmf/ant">
> <target name="run">
> <gmf:GenerateDiagramCode
> gmfgenPath="org.eclipse.emf.edit/model/Tree.gmfgen"/>
> </target>
> </project>
>
> Other supported attributes are ignoreLoadErrors and
> ignoreValidationErrors (both boolean).
>
> I haven't had the time to publicize it in any way but you can get it
> from my update site at
> http://www.eclipticalsoftware.com/updates/site.xml (under the GMF
> category). Version 0.9.0 is for Europa and version 1.0.0 is for Ganymede
> and later. Hope it works for ya.
>
> --Peter
>
> chris wrote:
>> Hi,
>>
>> right now, I'm working on setting up a build process for my (partly
>> GMF-based) tooling. One step of that process should be to generate the
>> according diagram plug-ins (which I can do since all customizations are
>> either in a separate plug-in, implemented through dynamic templates, or
>> done using the GMFTools stuff (see http://code.google.com/p/gmftools/).
>>
>> I've found two related threads in this newsgroup ("generating diagram
>> code from a headless build", "Generating Diagram Code from an Ant
>> Script") which seem to imply that this is not possible. But it's hard to
>> believe that nobody out there is doing this :-)
>>
>> So, if my assumption is correct, can anybody share his/her experiences
>> with that problem? Preferably incorporating the GMFTools process...
>>
>> Thanks in advance,
>> Chris
Re: Generating diagram code in build process [message #236196 is a reply to message #231031] Wed, 15 July 2009 10:33 Go to previous messageGo to next message
Miguel Angel Garcia de Dios is currently offline Miguel Angel Garcia de DiosFriend
Messages: 22
Registered: July 2009
Junior Member
Hi Peter,
I want to use your plugin but, in the nwe Eclipse release 'Galileo' when
I try to get it using Update Site Manager I obtain the next error message:

"Cannot complete the install because one or more required items could
not be found.
Software being installed: Ant Support for GMF 1.0.0.20090407141548
(ca.ecliptical.gmf.ant.feature.group 1.0.0.20090407141548)
Missing requirement: Ant Support for GMF 1.0.0.20090407141548
(ca.ecliptical.gmf.ant.feature.group 1.0.0.20090407141548) requires
'org.eclipse.gmf.codegen [2.1.1,2.2.0)' but it could not be found"

But I have already intalled the "org.eclipse.gmf.codegen
2.2.0.v20090529-1238" sice it is de defualt version when you download
Galileo.

Is there any incompatibility between your plugin and Galileo? Why
Galileo cannot resolve the dependency correctly?
I am very concerned about using your plging because I think that it is a
really useful plugin.

On the other hand, your plugin takes a .gmfgen file and generates the
diagram code and, as I said before, that's a very interesting job but
also, do you now if there is an Ant task to cover the step of having
..ecore, .gmfgrah, .gmftool, .gmfmap models, generate the .gmfgen file in
order to use it like the input of your plugin?

Thanks!

Peter Nehrer wrote:
> Hi Chris,
>
> I actually put together a small plugin with an Ant task that run GMF's
> codegen. E.g.,
>
> <project name="Generate Diagram Code" default="run"
> xmlns:gmf="http://ecliptical.ca/gmf/ant">
> <target name="run">
> <gmf:GenerateDiagramCode
> gmfgenPath="org.eclipse.emf.edit/model/Tree.gmfgen"/>
> </target>
> </project>
>
> Other supported attributes are ignoreLoadErrors and
> ignoreValidationErrors (both boolean).
>
> I haven't had the time to publicize it in any way but you can get it
> from my update site at
> http://www.eclipticalsoftware.com/updates/site.xml (under the GMF
> category). Version 0.9.0 is for Europa and version 1.0.0 is for Ganymede
> and later. Hope it works for ya.
>
> --Peter
>
> chris wrote:
>> Hi,
>>
>> right now, I'm working on setting up a build process for my (partly
>> GMF-based) tooling. One step of that process should be to generate the
>> according diagram plug-ins (which I can do since all customizations are
>> either in a separate plug-in, implemented through dynamic templates, or
>> done using the GMFTools stuff (see http://code.google.com/p/gmftools/).
>>
>> I've found two related threads in this newsgroup ("generating diagram
>> code from a headless build", "Generating Diagram Code from an Ant
>> Script") which seem to imply that this is not possible. But it's hard to
>> believe that nobody out there is doing this :-)
>>
>> So, if my assumption is correct, can anybody share his/her experiences
>> with that problem? Preferably incorporating the GMFTools process...
>>
>> Thanks in advance,
>> Chris
Re: Generating diagram code in build process [message #236313 is a reply to message #235692] Thu, 16 July 2009 15:42 Go to previous messageGo to next message
Peter Nehrer is currently offline Peter NehrerFriend
Messages: 241
Registered: July 2009
Senior Member
Aurelien,

unfortunately GMF codegen doesn't work outside of the workspace. The
gmfgenPath argument must be workspace-relative.

To get around this in an automated build, set your
${buildDirectory}/plugins as the workspace root (using -data argument in
your build launcher).

--Peter

Aurelien Pupier wrote:
> Hi Peter,
>
> I tried your plug-in with
>
> <gmf:GenerateDiagramCode
> gmfgenPath=" ${buildDirectory}/plugins/org.ow2.jasmine.design.diagram/mod el/jasmine.gmfgen "/>
>
>
> but it can found the gmfgen file :
>
> org.eclipse.core.runtime.CoreException: Model loaded with errors.
> uri=platform:/resource/D:/build/plugins/org.ow2.jasmine.desi gn.diagram/model/jasmine.gmfgen
>
> at
> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:60)
>
> at
> ca.ecliptical.gmf.ant.tasks.GenerateDiagramCode.execute(Gene rateDiagramCode.java:53)
>
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
> at
> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1298 )
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:623)
>
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:495)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)
> at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
> Caused by: org.eclipse.core.internal.resources.ResourceException:
> Resource
> '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen'
> does not exist.
> at
> org.eclipse.core.internal.resources.Resource.checkExists(Res ource.java:317)
> at
> org.eclipse.core.internal.resources.Resource.checkAccessible (Resource.java:194)
>
> at org.eclipse.core.internal.resources.File.getContents(File.ja va:296)
> at org.eclipse.core.internal.resources.File.getContents(File.ja va:287)
> at
> org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl$WorkbenchHelper.createPlatformResourceInputStream(Pla tformResourceURIHandlerImpl.java:204)
>
> at
> org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl.createInputStream(PlatformResourceURIHandlerImpl.java :448)
>
> at
> org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterIm pl.createInputStream(ExtensibleURIConverterImpl.java:301)
>
> at
> org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:1212)
>
> at
> org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.inte rnalLoad(ModelLoadHelper.java:139)
>
> at
> org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.<init >(ModelLoadHelper.java:130)
>
> at
> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.loadGenMo del(GenerateDiagramCodeOperation.java:110)
>
> at
> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:58)
>
> ... 62 more
> Contains: Resource
> '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen'
> does not exist.
>
>
> The file exists I'm sure.
> I'm on Win XP.
>
> Any idea?
Re: Generating diagram code in build process [message #236320 is a reply to message #236196] Fri, 17 July 2009 03:50 Go to previous messageGo to next message
Peter Nehrer is currently offline Peter NehrerFriend
Messages: 241
Registered: July 2009
Senior Member
Miguel,

I uploaded an updated version of the plugin that will work with Galileo.
You'll find it at the same update site url as before.

--Peter

Miguel Angel Garcia de Dios wrote:
> Hi Peter,
> I want to use your plugin but, in the nwe Eclipse release 'Galileo' when
> I try to get it using Update Site Manager I obtain the next error message:
>
> "Cannot complete the install because one or more required items could
> not be found.
> Software being installed: Ant Support for GMF 1.0.0.20090407141548
> (ca.ecliptical.gmf.ant.feature.group 1.0.0.20090407141548)
> Missing requirement: Ant Support for GMF 1.0.0.20090407141548
> (ca.ecliptical.gmf.ant.feature.group 1.0.0.20090407141548) requires
> 'org.eclipse.gmf.codegen [2.1.1,2.2.0)' but it could not be found"
>
> But I have already intalled the "org.eclipse.gmf.codegen
> 2.2.0.v20090529-1238" sice it is de defualt version when you download
> Galileo.
>
> Is there any incompatibility between your plugin and Galileo? Why
> Galileo cannot resolve the dependency correctly?
> I am very concerned about using your plging because I think that it is a
> really useful plugin.
>
> On the other hand, your plugin takes a .gmfgen file and generates the
> diagram code and, as I said before, that's a very interesting job but
> also, do you now if there is an Ant task to cover the step of having
> .ecore, .gmfgrah, .gmftool, .gmfmap models, generate the .gmfgen file in
> order to use it like the input of your plugin?
>
> Thanks!
>
> Peter Nehrer wrote:
>> Hi Chris,
>>
>> I actually put together a small plugin with an Ant task that run GMF's
>> codegen. E.g.,
>>
>> <project name="Generate Diagram Code" default="run"
>> xmlns:gmf="http://ecliptical.ca/gmf/ant">
>> <target name="run">
>> <gmf:GenerateDiagramCode
>> gmfgenPath="org.eclipse.emf.edit/model/Tree.gmfgen"/>
>> </target>
>> </project>
>>
>> Other supported attributes are ignoreLoadErrors and
>> ignoreValidationErrors (both boolean).
>>
>> I haven't had the time to publicize it in any way but you can get it
>> from my update site at
>> http://www.eclipticalsoftware.com/updates/site.xml (under the GMF
>> category). Version 0.9.0 is for Europa and version 1.0.0 is for
>> Ganymede and later. Hope it works for ya.
>>
>> --Peter
>>
>> chris wrote:
>>> Hi,
>>>
>>> right now, I'm working on setting up a build process for my (partly
>>> GMF-based) tooling. One step of that process should be to generate the
>>> according diagram plug-ins (which I can do since all customizations are
>>> either in a separate plug-in, implemented through dynamic templates, or
>>> done using the GMFTools stuff (see http://code.google.com/p/gmftools/).
>>>
>>> I've found two related threads in this newsgroup ("generating diagram
>>> code from a headless build", "Generating Diagram Code from an Ant
>>> Script") which seem to imply that this is not possible. But it's hard to
>>> believe that nobody out there is doing this :-)
>>>
>>> So, if my assumption is correct, can anybody share his/her experiences
>>> with that problem? Preferably incorporating the GMFTools process...
>>>
>>> Thanks in advance,
>>> Chris
Re: Generating diagram code in build process [message #236363 is a reply to message #236313] Fri, 17 July 2009 12:27 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: aurelien.pupier.esial.net

Hi Peter,

I set the workspace root to ${buildDirectory}/plugins but I'm still having the same error but I've got another error before :

!ENTRY org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
!MESSAGE Bundle org.eclipse.jdt.apt.pluggable.core_1.0.200.v20090526-2130 [347] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.dispatch_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.model_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.util_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
!MESSAGE Bundle org.eclipse.jdt.compiler.apt_1.0.200.v20090528-1135 [349] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2009-07-17 13:56:31.614
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
!MESSAGE Bundle org.eclipse.jdt.compiler.tool_1.0.100.v_963 [350] was not resolved.


Will this can interfere?
and if you know how to avoid it.

Nota : I use the new version with Galileo

Aurelien


Peter Nehrer a écrit :
> Aurelien,
>
> unfortunately GMF codegen doesn't work outside of the workspace. The
> gmfgenPath argument must be workspace-relative.
>
> To get around this in an automated build, set your
> ${buildDirectory}/plugins as the workspace root (using -data argument in
> your build launcher).
>
> --Peter
>
> Aurelien Pupier wrote:
>> Hi Peter,
>>
>> I tried your plug-in with
>>
>> <gmf:GenerateDiagramCode
>> gmfgenPath=" ${buildDirectory}/plugins/org.ow2.jasmine.design.diagram/mod el/jasmine.gmfgen "/>
>>
>>
>> but it can found the gmfgen file :
>>
>> org.eclipse.core.runtime.CoreException: Model loaded with errors.
>> uri=platform:/resource/D:/build/plugins/org.ow2.jasmine.desi gn.diagram/model/jasmine.gmfgen
>>
>> at
>> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:60)
>>
>> at
>> ca.ecliptical.gmf.ant.tasks.GenerateDiagramCode.execute(Gene rateDiagramCode.java:53)
>>
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
>>
>> at org.apache.tools.ant.Task.perform(Task.java:348)
>> at org.apache.tools.ant.Target.execute(Target.java:357)
>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
>>
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>
>> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
>>
>> at org.apache.tools.ant.Task.perform(Task.java:348)
>> at org.apache.tools.ant.Target.execute(Target.java:357)
>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
>>
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>
>> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
>> at
>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:105)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
>>
>> at org.apache.tools.ant.Task.perform(Task.java:348)
>> at org.apache.tools.ant.Target.execute(Target.java:357)
>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1298 )
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>>
>> at
>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>
>> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:623)
>>
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:495)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)
>> at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)
>> at
>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>>
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
>>
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
>> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>> Caused by: org.eclipse.core.internal.resources.ResourceException:
>> Resource
>> '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen'
>> does not exist.
>> at
>> org.eclipse.core.internal.resources.Resource.checkExists(Res ource.java:317)
>>
>> at
>> org.eclipse.core.internal.resources.Resource.checkAccessible (Resource.java:194)
>>
>> at
>> org.eclipse.core.internal.resources.File.getContents(File.ja va:296)
>> at
>> org.eclipse.core.internal.resources.File.getContents(File.ja va:287)
>> at
>> org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl$WorkbenchHelper.createPlatformResourceInputStream(Pla tformResourceURIHandlerImpl.java:204)
>>
>> at
>> org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl.createInputStream(PlatformResourceURIHandlerImpl.java :448)
>>
>> at
>> org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterIm pl.createInputStream(ExtensibleURIConverterImpl.java:301)
>>
>> at
>> org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:1212)
>>
>> at
>> org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.inte rnalLoad(ModelLoadHelper.java:139)
>>
>> at
>> org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.<init >(ModelLoadHelper.java:130)
>>
>> at
>> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.loadGenMo del(GenerateDiagramCodeOperation.java:110)
>>
>> at
>> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:58)
>>
>> ... 62 more
>> Contains: Resource
>> '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen'
>> does not exist.
>>
>>
>> The file exists I'm sure.
>> I'm on Win XP.
>>
>> Any idea?
Re: Generating diagram code in build process [message #236386 is a reply to message #236363] Fri, 17 July 2009 14:45 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: aurelien.pupier.esial.net

Ok : In fact, my project is in the folder but not really the workspace.
When I open the eclipse with the workspace I don't see the project.

Now, maybe I "only" to add the project to the workspace via ant task or by modifying your ant task.

Aurelien Pupier a écrit :
> Hi Peter,
>
> I set the workspace root to ${buildDirectory}/plugins but I'm still
> having the same error but I've got another error before :
>
> !ENTRY org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
> !MESSAGE The following is a complete list of bundles which are not
> resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
> !MESSAGE Bundle
> org.eclipse.jdt.apt.pluggable.core_1.0.200.v20090526-2130 [347] was not
> resolved.
> !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
> !MESSAGE Missing imported package
> org.eclipse.jdt.internal.compiler.tool_0.0.0.
> !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
> !MESSAGE Missing imported package
> org.eclipse.jdt.internal.compiler.apt.dispatch_0.0.0.
> !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
> !MESSAGE Missing imported package
> org.eclipse.jdt.internal.compiler.apt.model_0.0.0.
> !SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2009-07-17 13:56:31.614
> !MESSAGE Missing imported package
> org.eclipse.jdt.internal.compiler.apt.util_0.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
> !MESSAGE Bundle org.eclipse.jdt.compiler.apt_1.0.200.v20090528-1135
> [349] was not resolved.
> !SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2009-07-17 13:56:31.614
> !MESSAGE Missing imported package
> org.eclipse.jdt.internal.compiler.tool_0.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2009-07-17 13:56:31.614
> !MESSAGE Bundle org.eclipse.jdt.compiler.tool_1.0.100.v_963 [350] was
> not resolved.
>
>
> Will this can interfere?
> and if you know how to avoid it.
>
> Nota : I use the new version with Galileo
>
> Aurelien
>
>
> Peter Nehrer a écrit :
>> Aurelien,
>>
>> unfortunately GMF codegen doesn't work outside of the workspace. The
>> gmfgenPath argument must be workspace-relative.
>>
>> To get around this in an automated build, set your
>> ${buildDirectory}/plugins as the workspace root (using -data argument
>> in your build launcher).
>>
>> --Peter
>>
>> Aurelien Pupier wrote:
>>> Hi Peter,
>>>
>>> I tried your plug-in with
>>>
>>> <gmf:GenerateDiagramCode
>>> gmfgenPath=" ${buildDirectory}/plugins/org.ow2.jasmine.design.diagram/mod el/jasmine.gmfgen "/>
>>>
>>>
>>> but it can found the gmfgen file :
>>>
>>> org.eclipse.core.runtime.CoreException: Model loaded with errors.
>>> uri=platform:/resource/D:/build/plugins/org.ow2.jasmine.desi gn.diagram/model/jasmine.gmfgen
>>>
>>> at
>>> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:60)
>>>
>>> at
>>> ca.ecliptical.gmf.ant.tasks.GenerateDiagramCode.execute(Gene rateDiagramCode.java:53)
>>>
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>>> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at
>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
>>>
>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>> at org.apache.tools.ant.Target.execute(Target.java:357)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
>>>
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>>> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at
>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
>>>
>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>> at org.apache.tools.ant.Target.execute(Target.java:357)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:38)
>>>
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
>>> at
>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:105)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>>> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at
>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
>>>
>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>> at org.apache.tools.ant.Target.execute(Target.java:357)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1298 )
>>> at
>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>>>
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>>
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:623)
>>>
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:495)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:513)
>>> at org.eclipse.ant.core.AntRunner.start(AntRunner.java:600)
>>> at
>>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>>>
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>>
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>>
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
>>>
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
>>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
>>> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
>>> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>>> Caused by: org.eclipse.core.internal.resources.ResourceException:
>>> Resource
>>> '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen'
>>> does not exist.
>>> at
>>> org.eclipse.core.internal.resources.Resource.checkExists(Res ource.java:317)
>>>
>>> at
>>> org.eclipse.core.internal.resources.Resource.checkAccessible (Resource.java:194)
>>>
>>> at
>>> org.eclipse.core.internal.resources.File.getContents(File.ja va:296)
>>> at
>>> org.eclipse.core.internal.resources.File.getContents(File.ja va:287)
>>> at
>>> org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl$WorkbenchHelper.createPlatformResourceInputStream(Pla tformResourceURIHandlerImpl.java:204)
>>>
>>> at
>>> org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandl erImpl.createInputStream(PlatformResourceURIHandlerImpl.java :448)
>>>
>>> at
>>> org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterIm pl.createInputStream(ExtensibleURIConverterImpl.java:301)
>>>
>>> at
>>> org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:1212)
>>>
>>> at
>>> org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.inte rnalLoad(ModelLoadHelper.java:139)
>>>
>>> at
>>> org.eclipse.gmf.internal.common.migrate.ModelLoadHelper.<init >(ModelLoadHelper.java:130)
>>>
>>> at
>>> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.loadGenMo del(GenerateDiagramCodeOperation.java:110)
>>>
>>> at
>>> ca.ecliptical.gmf.ant.GenerateDiagramCodeOperation.run(Gener ateDiagramCodeOperation.java:58)
>>>
>>> ... 62 more
>>> Contains: Resource
>>> '/build/plugins/org.ow2.jasmine.design.diagram/model/jasmine .gmfgen'
>>> does not exist.
>>>
>>>
>>> The file exists I'm sure.
>>> I'm on Win XP.
>>>
>>> Any idea?
Re: Generating diagram code in build process [message #236444 is a reply to message #236386] Mon, 20 July 2009 09:08 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: aurelien.pupier.esial.net

Aurelien Pupier a écrit :
>
> Ok : In fact, my project is in the folder but not really the workspace.
> When I open the eclipse with the workspace I don't see the project.
>
> Now, maybe I "only" to add the project to the workspace via ant task or
> by modifying your ant task.
>


After added the project to the workspace it works fine if I execute only the diagram generation.
But I generate model java code (emf.Ecore2Java) before I've got Java Heap Space error.
And in all cases, the generation is really slow.

I argument the JVM memory args but doesn't work and BTW it works great with less memory when using classic generation via UI...

I also tried System.gc() at the beginning of the run function.(In order to have a clean VM before the generation of diagram code).

Did you encounter this kind of issue? How to solve it?
Is it an Ant issue?
Re: Generating diagram code in build process [message #236869 is a reply to message #236444] Mon, 20 July 2009 13:34 Go to previous messageGo to next message
Peter Nehrer is currently offline Peter NehrerFriend
Messages: 241
Registered: July 2009
Senior Member
Aurelien,

do you specify "--launcher.XXMaxPermSize <size>" in your launcher
command line? I'm not sure what else could be the problem. I have not
run into it even when generating several medium-size models in one build.

--Peter

Aurelien Pupier wrote:
> Aurelien Pupier a écrit :
>>
>> Ok : In fact, my project is in the folder but not really the workspace.
>> When I open the eclipse with the workspace I don't see the project.
>>
>> Now, maybe I "only" to add the project to the workspace via ant task
>> or by modifying your ant task.
>>
>
>
> After added the project to the workspace it works fine if I execute only
> the diagram generation.
> But I generate model java code (emf.Ecore2Java) before I've got Java
> Heap Space error.
> And in all cases, the generation is really slow.
>
> I argument the JVM memory args but doesn't work and BTW it works great
> with less memory when using classic generation via UI...
>
> I also tried System.gc() at the beginning of the run function.(In order
> to have a clean VM before the generation of diagram code).
>
> Did you encounter this kind of issue? How to solve it?
> Is it an Ant issue?
Re: Generating diagram code in build process [message #236925 is a reply to message #236869] Mon, 20 July 2009 14:14 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: aurelien.pupier.esial.net

I run Ant from Eclipse, so in launch configuration, I choose run in a separate JVM and for VM argument :
-Xms1024m -Xmx1280m

in the eclipse.ini of the launched eclipse, there are :
-Xms512m
-Xmx768m

and I also tried to set <arg value="--launcher.XXMaxPermSize 512m" /> in my build.xml in <java classname="org.eclipse.equinox.launcher.Main" fork="true"
failonerror="true" errorproperty="build.stderr">

Peter Nehrer a écrit :
> Aurelien,
>
> do you specify "--launcher.XXMaxPermSize <size>" in your launcher
> command line? I'm not sure what else could be the problem. I have not
> run into it even when generating several medium-size models in one build.
>
> --Peter
>
> Aurelien Pupier wrote:
>> Aurelien Pupier a écrit :
>>>
>>> Ok : In fact, my project is in the folder but not really the workspace.
>>> When I open the eclipse with the workspace I don't see the project.
>>>
>>> Now, maybe I "only" to add the project to the workspace via ant task
>>> or by modifying your ant task.
>>>
>>
>>
>> After added the project to the workspace it works fine if I execute
>> only the diagram generation.
>> But I generate model java code (emf.Ecore2Java) before I've got Java
>> Heap Space error.
>> And in all cases, the generation is really slow.
>>
>> I argument the JVM memory args but doesn't work and BTW it works great
>> with less memory when using classic generation via UI...
>>
>> I also tried System.gc() at the beginning of the run function.(In
>> order to have a clean VM before the generation of diagram code).
>>
>> Did you encounter this kind of issue? How to solve it?
>> Is it an Ant issue?
Re: Generating diagram code in build process [message #236960 is a reply to message #236925] Mon, 20 July 2009 18:15 Go to previous messageGo to next message
Peter Nehrer is currently offline Peter NehrerFriend
Messages: 241
Registered: July 2009
Senior Member
> and I also tried to set <arg value="--launcher.XXMaxPermSize 512m" /> in
> my build.xml in <java classname="org.eclipse.equinox.launcher.Main"
> fork="true"
> failonerror="true" errorproperty="build.stderr">


This has to be a jvmarg, not an arg.
Re: Generating diagram code in build process [message #237020 is a reply to message #236960] Tue, 21 July 2009 06:49 Go to previous message
Eclipse UserFriend
Originally posted by: aurelien.pupier.esial.net

Peter Nehrer a écrit :
>> and I also tried to set <arg value="--launcher.XXMaxPermSize 512m" />
>> in my build.xml in <java classname="org.eclipse.equinox.launcher.Main"
>> fork="true"
>> failonerror="true" errorproperty="build.stderr">
>
>
> This has to be a jvmarg, not an arg.

Oh gosh!! thanks

I was thinking that it will used the values set in eclipse.ini but it seems not...

Thanks again a lot
Previous Topic:Removing a diagram from the New wizard
Next Topic:Accessing the GenModel nsUri
Goto Forum:
  


Current Time: Mon Apr 06 22:37:04 GMT 2020

Powered by FUDForum. Page generated in 0.11429 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top