Jump to: navigation, search

Difference between revisions of "Graphical Modeling Framework/Contributors Area"

(New page: == Builds == === GMF Tooling snapshot build === * See it at https://hudson.eclipse.org/hudson/job/tycho-gmp.gmf.tooling/ * Get it at http://download.eclipse.org/modeling/gmp/gmf-tooling/u...)
 
(Build locally)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{GMF}}
 +
 +
== Tracker ==
 +
 +
=== Be notified ===
 +
 +
Go to Bugzilla > Preferences > Mail Preferences > User Watching > and add
 +
* gmp.gmf-tooling-inbox@eclipse.org
 +
* gmp.gmf-runtime-inbox@eclipse.org
 +
* ...
 +
to the list. You'll then receive notifications by mail when an issue is opened or changed.
 +
 +
 +
== Mailing lists ==
 +
 +
* GMF-dev for general development and project organization questions: https://dev.eclipse.org/mailman/listinfo/gmf-dev
 +
* GMF-releng for build reports: https://dev.eclipse.org/mailman/listinfo/gmf-releng
 +
 
== Builds ==
 
== Builds ==
  
=== GMF Tooling snapshot build ===
+
=== GMF Runtime ===
 +
 
 +
* See it at https://hudson.eclipse.org/hudson/job/tycho-gmp.gmf.runtime/
 +
 
 +
==== How to build GMF-Runtime with Tycho (non-principal build)====
 +
 
 +
* checkout source code dev.eclipse.org/cvsroot/modeling/org.eclipse.gmp/org.eclipse.gmf.runtime
 +
* go to releng/org.eclipse.gmf.runtime-parent
 +
* Type mvn clean install
 +
 
 +
GMF-Runtime will be built and tests will be executed.
 +
 
 +
Note: Maven 3 is required
 +
 
 +
=== GMF Tooling ===
 +
 
 +
==== Build locally ====
 +
 
 +
Simply perform a '''mvn verify'''. You can add the following parameters:
 +
* ''clean'' wil remove existing target/ folders and NOT re-use binaries from previous builds (conumes more time, but is more likely to behave well)
 +
* ''-Dtycho.localArtifacts=ignore'' Ignore existing artifacts installed in your repo. It's good to perform a full build. Don't use it if you're using an iterative build (a bundle after the other)
 +
* ''-Dmaven.test.skip=true'' won't run tests
 +
 
 +
==== 3.0 stream ====
 +
* Source on the '''master''' branch
 
* See it at https://hudson.eclipse.org/hudson/job/tycho-gmp.gmf.tooling/
 
* See it at https://hudson.eclipse.org/hudson/job/tycho-gmp.gmf.tooling/
* Get it at http://download.eclipse.org/modeling/gmp/gmf-tooling/updates/dev-snapshots/
+
* Get it at http://download.eclipse.org/modeling/gmp/gmf-tooling/updates/dev-snapshots/3.0
 +
 
 +
==== 2.4.x maintenance Stream ====
 +
* Source on the '''2.4.x-maintenance''' branch
 +
* See it at https://hudson.eclipse.org/hudson/job/tycho-gmp.gmf.tooling.maintenance/
 +
* Get it at http://download.eclipse.org/modeling/gmp/gmf-tooling/updates/dev-snapshots/2.4.x-maintenance
 +
 
 +
== Presentations and Proposals in Conferences ==
 +
 
 +
* [[/EclipseCon Europe 2011| EclipseCon Europe 2011]]
 +
* [http://www.slideshare.net/AurelienPupier/tools-and-methodologies-to-leverage-gmf-power-eclipseday-delft-2012 EclipseDay Delft 2012]
 +
* [http://www.eclipsecon.org/europe2012/sessions/tools-and-methodologies-leverage-gmf-power EclipseCon Europe 2012]

Latest revision as of 11:19, 8 December 2012



GMF
Website
Download
Dev Builds
Update Site releases milestones
Community
Mailing ListNewsgroupIRC
Bugzilla
Open
Help Wanted
Bug Day
Source
GMF Notation: View CVS repo

GMF Runtime: View CVS repo
GMF Tooling: View Git Repo, GitHub


Tracker

Be notified

Go to Bugzilla > Preferences > Mail Preferences > User Watching > and add

  • gmp.gmf-tooling-inbox@eclipse.org
  • gmp.gmf-runtime-inbox@eclipse.org
  • ...

to the list. You'll then receive notifications by mail when an issue is opened or changed.


Mailing lists

Builds

GMF Runtime

How to build GMF-Runtime with Tycho (non-principal build)

  • checkout source code dev.eclipse.org/cvsroot/modeling/org.eclipse.gmp/org.eclipse.gmf.runtime
  • go to releng/org.eclipse.gmf.runtime-parent
  • Type mvn clean install

GMF-Runtime will be built and tests will be executed.

Note: Maven 3 is required

GMF Tooling

Build locally

Simply perform a mvn verify. You can add the following parameters:

  • clean wil remove existing target/ folders and NOT re-use binaries from previous builds (conumes more time, but is more likely to behave well)
  • -Dtycho.localArtifacts=ignore Ignore existing artifacts installed in your repo. It's good to perform a full build. Don't use it if you're using an iterative build (a bundle after the other)
  • -Dmaven.test.skip=true won't run tests

3.0 stream

2.4.x maintenance Stream

Presentations and Proposals in Conferences