Difference between revisions of "Vex/CommitterResources"

From Eclipsepedia

< Vex
Jump to: navigation, search
(Getting the Source)
(Setup a Workspace)
(39 intermediate revisions by 4 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 ==
 +
* Install the EGit team provider
  
The name of the vex plugin projects are all prefixed with: org.eclipse.wst.xml.vex
+
For committers:
 +
* Configure and clone the Mylyn Docs Vex Git repository including the branch ''master'':
 +
    ssh://<your_username>@git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.vex.git
 +
* Import all projects (prefix ''org.eclipse.vex'') into your workspace
 +
* Checkout the branch ''master'' for the "latest and greatest" code
  
The following is a list of where specific items can be found:
+
For other contributors:
 +
* Import the Team Project Set from
 +
    http://git.eclipse.org/c/mylyn/org.eclipse.mylyn.docs.vex.git/plain/org.eclipse.vex.releng/vex.psf
  
* plugins - the actual ui and core plugins.
+
For all (after cloning the Git repository)
* documentation - eclipse help plugins that contain both user and developer documentation.
+
* Configure the target definition ''vex.target'', which is stored in the releng plug-in.  If no specific editor appears, it means that you need to install the ''Eclipse Releng Tools'' from the eclipse update site.
* tests - unit test plugins.
+
* Use the launch configuration ''Vex'' to start a run-time workbench which includes Vex
* features - features used mainly for update site installation.
+
 
 +
Please bear in mind to configure your name and email address in git before cloning the repository:
 +
    git config --global user.name "Your Name"
 +
    git config --global user.email <your_bugzilla_email_address>
  
 
== Patches and Bug Fixes ==
 
== Patches and Bug Fixes ==
  
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.
+
Please use a local branch for your changes and create a patch as described in the [[EGit/User_Guide #Creating_Patches|EGit User Guide]]. At the moment you have to create one patch for each plug-in that you have changed.
 +
 
 +
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=
+
With [http://eclipse.org/tycho/ Tycho] see [http://live.eclipse.org/node/1003 "Tycho - Building Eclipse Plugins with Maven"]
  
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 both the incubator newsgroup as well as the main webtools newsgroup. Developer questions should be sent to the wtp-incubator 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]]

Revision as of 18:37, 9 March 2012

Contents

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

  • Install the EGit team provider

For committers:

  • Configure and clone the Mylyn Docs Vex Git repository including the branch master:
   ssh://<your_username>@git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.vex.git
  • Import all projects (prefix org.eclipse.vex) into your workspace
  • Checkout the branch master for the "latest and greatest" code

For other contributors:

  • Import the Team Project Set from
   http://git.eclipse.org/c/mylyn/org.eclipse.mylyn.docs.vex.git/plain/org.eclipse.vex.releng/vex.psf

For all (after cloning the Git repository)

  • Configure the target definition vex.target, which is stored in the releng plug-in. If no specific editor appears, it means that you need to install the Eclipse Releng Tools from the eclipse update site.
  • Use the launch configuration Vex to start a run-time workbench which includes Vex

Please bear in mind to configure your name and email address in git before cloning the repository:

   git config --global user.name "Your Name"
   git config --global user.email <your_bugzilla_email_address>

Patches and Bug Fixes

Please use a local branch for your changes and create a patch as described in the EGit User Guide. At the moment you have to create one patch for each plug-in that you have changed.

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

With Tycho see "Tycho - Building Eclipse Plugins with Maven"

Getting Help

Committers watch and hang out on a variety of eclipse resources channels. Include #eclipse irc channel on freenode.net. Also, we monitor both the incubator newsgroup as well as the main webtools newsgroup. Developer questions should be sent to the wtp-incubator mailing list.

Vex Committer Calls