Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Vex/CommitterResources"

< Vex
(Vex Committer Calls)
(30 intermediate revisions by 3 users not shown)
Line 5: Line 5:
 
=Getting the Source=
 
=Getting the Source=
  
The source code for Vex resides in the incubator/sourceediting module within the /gitroot/webtools Git repository. For general information about how to use Git see the [[EGit/User Guide|EGit User Guide]].
+
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''.
 
+
The name of the Vex plugin projects are all prefixed with: ''org.eclipse.wst.xml.vex''. The following is a list of where specific items can be found:
+
* development - the configuration of the automated builds
+
* plugins - the actual ui and core plugins.
+
* documentation - eclipse help plugins that contain both user and developer documentation.
+
* tests - unit test plugins.
+
* features - features used mainly for update site installation.
+
  
 
== Setup a Workspace ==
 
== Setup a Workspace ==
* Install the EGit team provider
+
Vex is available through the Eclipse Installer (by Oomph). To setup a workspace, do the following steps:
* Configure and clone the webtools/incubator Git repository including the branch ''vex-dev'':
+
# Get the [[Eclipse Installer]], unzip it and start it.
    git://git.eclipse.org/gitroot/webtools/org.eclipse.webtools.incubator.git
+
# Select "Eclipse Standard/SDK" on the "Product" page and press "Next"
* Import all projects with the prefix ''org.eclipse.wst.xml.vex'' into your workspace
+
# Double-click on "Vex" on the "Projects" page and press "Next"
* Checkout the branch ''vex-dev''
+
# Fill out the "Variables" page as it fits best to your desired environment and press "Next"
* Configure the target definition ''Vex Helios'', which is stored in the releng plug-in
+
# Check the planned bootstrap tasks on the "Confirmation" page and press "Next" to start the actual installation of the IDE
* Use the launch configuration ''Vex'' to start a runtime workbench which includes Vex
+
# 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 ==
 
== Patches and Bug Fixes ==
  
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.
+
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.
 
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.
Line 31: Line 26:
 
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.
  
= Getting Help =
+
== Build ==
  
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 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].
  
 +
= Getting Help =
  
= Release [http://build.eclipse.org/webtools/committers/ Integration Build] (Committers only) =
+
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].
 
+
* Download/install Eclipse '''Releng tools''' plug-in ([http://download.eclipse.org/eclipse/downloads/ it's at the bottom of the download page of a version/release]).
+
# Right-click on '''''releng.incubator.vex project''''' folder and choose '''''Team > Release...'''''
+
# '''Tag name:''' [http://www.worldtimeserver.com/current_time_in_UTC.aspx UTC date/time] in the format '''''vYYYYYMMDDHHMM'''''
+
  
== Vex Committer Calls ==
+
= Vex Committer Calls =
* [[WTP/VisualEditorForXML/VexCommitterCall20100713|2010-07-13]]
+
* [[Vex/VexCommitterCalls|Vex Committer Calls]]
* [[WTP/VisualEditorForXML/VexCommitterCall20100727|2010-07-27]]
+
* [[Vex/VexCommitterCall20110719|2011-07-19]]
* [[WTP/VisualEditorForXML/VexCommitterCall20100817|2010-08-17]]
+
* [[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 02:09, 8 July 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. Select "Eclipse Standard/SDK" on the "Product" page and press "Next"
  3. Double-click on "Vex" on the "Projects" page and press "Next"
  4. Fill out the "Variables" page as it fits best to your desired environment and press "Next"
  5. Check the planned bootstrap tasks on the "Confirmation" page and press "Next" to start the actual installation of the IDE
  6. 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