Skip to main content
Jump to: navigation, search

Difference between revisions of "Vex/CommitterResources"

< Vex
(Getting the Source)
(Hint to switch to advanced mode)
 
(43 intermediate revisions by 5 users not shown)
Line 1: Line 1:
=VEX Committer and Contributor Resources=
+
= Project Manifesto =
 
+
=Project Manifesto=
+
 
+
 
# All new enhancements will be unit tested.
 
# All new enhancements will be unit tested.
 
# First learn rule number 1.  
 
# First learn rule number 1.  
Line 8: Line 5:
 
=Getting the Source=
 
=Getting the Source=
  
The source code for VEX resides in the incubator/sourceediting module within the /cvsroot/webtools CVS repository.  
+
The source code for Vex resides in the Mylyn Docs Vex Git repository. For general information about how to use Git see the [[EGit/User Guide|EGit User Guide]]. The names of the Vex plug-in projects are all prefixed with: ''org.eclipse.vex''.
  
Information on how to check out the code at eclipse can be found on the [[Development_Resources | Development Resources]] page.
+
== Setup a Workspace ==
 +
Vex is available through the Eclipse Installer (by Oomph). To setup a workspace, do the following steps:
 +
# Get the [[Eclipse Installer]], unzip it and start it.
 +
# Click the menu button and switch to 'Advanced Mode'
 +
# Select "Eclipse IDE for Eclipse Committers" on the "Product" page and press "Next"
 +
# Double-click on "Vex" on the "Projects" page and press "Next"
 +
# Fill out the "Variables" page as it fits best to your desired environment and press "Next"
 +
# Check the planned bootstrap tasks on the "Confirmation" page and press "Next" to start the actual installation of the IDE
 +
# Press "Finish" after the installation is done.
  
The name of the vex plugin projects are all prefixed with: org.eclipse.wst.xml.vex
+
It will take a moment until your new Vex IDE is started, just be patient. Some seconds after the start, again a installation wizard is opened where you have to confirm the configuration tasks for the new IDE.
  
The following is a list of where specific items can be found:
+
== Patches and Bug Fixes ==
  
* plugins - the actual ui and core plugins.
+
Please provide us your contributions through the Gerrit Code Review system of the Eclipse Foundation. For more information about how to use Gerrit, please see [[Development_Resources/Contributing_via_Git]].
* documentation - eclipse help plugins that contain both user and developer documentation.
+
* tests - unit test plugins.
+
* features - features used mainly for update site installation.
+
  
== Patches and Bug Fixes ==
+
Bug fixes that come with unit tests are more likely to be reviewed sooner than those that do not come with unit tests. Patches over 250 lines of code will have to be sent through eclipse IP review.
  
Please use the Team->Create Patch option to submit any patches or bug fixes.  Bug fixes that come with unit tests are more likely to be reviewed sooner than those that do not come with unit tests.  Patches over 250 lines of code will have to be sent through eclipse IP review.
+
With that said, we are actively seeking new enhancements and patches for Vex.
  
With that said, we are actively seeking new enhancements and patches for VEX.
+
== Build ==
  
=Getting Help=
+
Vex is build with [http://eclipse.org/tycho/ Tycho] (see [http://live.eclipse.org/node/1003 "Tycho - Building Eclipse Plugins with Maven"]) on its own [https://hudson.eclipse.org/vex/ Hudson instance].
  
Information on mailing lists, newsgroups, and irc channels.
+
= Getting Help =
  
=Additional Resources=
+
Committers watch and hang out on a variety of eclipse resources channels. Include #eclipse irc channel on freenode.net. Also, we monitor the [https://www.eclipse.org/forums/index.php?t=thread&frm_id=235 Eclipse Community Forum] and the [news://news.eclipse.org/eclipse.vex eclipse.vex] newsgroup. Developer questions should be sent to the [https://dev.eclipse.org/mailman/listinfo/mylyn-vex-dev mylyn-vex-dev mailing list].
  
More useful resources.
+
= Vex Committer Calls =
 +
* [[Vex/VexCommitterCalls|Vex Committer Calls]]
 +
* [[Vex/VexCommitterCall20110719|2011-07-19]]
 +
* [[Vex/VexCommitterCall20110705|2011-07-05]]
 +
* [[Vex/VexCommitterCall20110426|2011-04-26]]
 +
* [[Vex/VexCommitterCall20110412|2011-04-12]]
 +
* [[Vex/VexCommitterCall20110301|2011-03-01]]
 +
* [[Vex/VexCommitterCall20110215|2011-02-15]]
 +
* [[Vex/VexCommitterCall20110201|2011-02-01]]
 +
* [[Vex/VexCommitterCall20101207|2010-12-07]]
 +
* [[Vex/VexCommitterCall20101116|2010-11-16]]
 +
* [[Vex/VexCommitterCall20101109|2010-11-09]]
 +
* [[Vex/VexCommitterCall20101019|2010-10-19]]
 +
* [[Vex/VexCommitterCall20101005|2010-10-05]]
 +
* [[Vex/VexCommitterCall20100921|2010-09-21]]
 +
* [[Vex/VexCommitterCall20100817|2010-08-17]]
 +
* [[Vex/VexCommitterCall20100727|2010-07-27]]
 +
* [[Vex/VexCommitterCall20100713|2010-07-13]]

Latest revision as of 14:57, 14 September 2015

Project Manifesto

  1. All new enhancements will be unit tested.
  2. First learn rule number 1.

Getting the Source

The source code for Vex resides in the Mylyn Docs Vex Git repository. For general information about how to use Git see the EGit User Guide. The names of the Vex plug-in projects are all prefixed with: org.eclipse.vex.

Setup a Workspace

Vex is available through the Eclipse Installer (by Oomph). To setup a workspace, do the following steps:

  1. Get the Eclipse Installer, unzip it and start it.
  2. Click the menu button and switch to 'Advanced Mode'
  3. Select "Eclipse IDE for Eclipse Committers" on the "Product" page and press "Next"
  4. Double-click on "Vex" on the "Projects" page and press "Next"
  5. Fill out the "Variables" page as it fits best to your desired environment and press "Next"
  6. Check the planned bootstrap tasks on the "Confirmation" page and press "Next" to start the actual installation of the IDE
  7. Press "Finish" after the installation is done.

It will take a moment until your new Vex IDE is started, just be patient. Some seconds after the start, again a installation wizard is opened where you have to confirm the configuration tasks for the new IDE.

Patches and Bug Fixes

Please provide us your contributions through the Gerrit Code Review system of the Eclipse Foundation. For more information about how to use Gerrit, please see Development_Resources/Contributing_via_Git.

Bug fixes that come with unit tests are more likely to be reviewed sooner than those that do not come with unit tests. Patches over 250 lines of code will have to be sent through eclipse IP review.

With that said, we are actively seeking new enhancements and patches for Vex.

Build

Vex is build with Tycho (see "Tycho - Building Eclipse Plugins with Maven") on its own Hudson instance.

Getting Help

Committers watch and hang out on a variety of eclipse resources channels. Include #eclipse irc channel on freenode.net. Also, we monitor the Eclipse Community Forum and the eclipse.vex newsgroup. Developer questions should be sent to the mylyn-vex-dev mailing list.

Vex Committer Calls

Back to the top