Open GoogleCodeExporter opened 8 years ago
Some work was done in brach 2009-06-automated-build, but didn't get anywhere.
Essentially, the thread
http://dev.eclipse.org/newslists/news.eclipse.modeling.gmf/msg18284.html covers
an
Ant build target that allows the generation of GMF diagram code; however, this
cannot
be run through a normal Ant build. If run through the Eclipse Ant builder, the
Eclipse instance is run headless.
GMF diagram code generation requires the JDT preferences to be loaded,
otherwise this
error is thrown:
java.lang.NoClassDefFoundError: org/eclipse/jdt/ui/PreferenceConstants
Trying to create a new Eclipse IApplication as an Eclipse application proved
more
successful (specified through the command line, in particular test.bat). The aim
behind this was to generate diagram code through Java in a fully functional
Eclipse
workbench. This is currently throwing invalid thread access errors.
More information may be found by following Eclipse Bugzilla 282331:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=282331.
Original comment by soundasleep
on 3 Jul 2009 at 5:21
Original comment by soundasleep
on 16 Jul 2009 at 2:49
It is possible to automatically build the plugin code.
1. Right click a feature.xml and select "generate build script"
2. This build script can be executed through the command line like so:
java -jar <eclipse path>/plugins/org.eclipse.equinox.launcher_<version>.jar
-application org.eclipse.ant.core.antRunner -buildfile <location of build
file>/build.xml
However, the generated plugins are all placed in their separate projects.
Simply right clicking the update site "site.xml" and selecting "PDE Tools >
Build
Site" seems to work best.
The PDE Help Guide also includes some documentation on automatically building
features, and also some information on automatically exporting source code etc.
Original comment by soundasleep
on 9 Sep 2009 at 11:07
More discussion: http://journals.jevon.org/users/jevon-phd/entry/19749
Original comment by soundasleep
on 9 Sep 2009 at 11:46
Original comment by soundasleep
on 15 Sep 2009 at 8:17
Original comment by soundasleep
on 6 Oct 2009 at 1:16
moving all 0.6 issues to 0.7
Original comment by soundasleep
on 17 Apr 2010 at 6:57
mass tagging old issues to future work
Original comment by soundasleep
on 26 Sep 2011 at 9:53
Original issue reported on code.google.com by
soundasleep
on 25 Mar 2009 at 2:50