Difference between revisions of "CDT/contributing"

From Eclipsepedia

< CDT
Jump to: navigation, search
Line 10: Line 10:
  
 
One of the fundamental rules that Eclipse follows is the ability to trace back who contributed what code and that the person who contributed it has ownership of the code, or has permission from their employer to contribute the code (since employers tend to own everything you write). To help keep this IP integrity going, please ensure your contributions are "clean".
 
One of the fundamental rules that Eclipse follows is the ability to trace back who contributed what code and that the person who contributed it has ownership of the code, or has permission from their employer to contribute the code (since employers tend to own everything you write). To help keep this IP integrity going, please ensure your contributions are "clean".
 
== Bug reporting ==
 
 
When creating a bugzilla entry on the CDT product you can use the following rules to select a component based on the location of the issue.
 
 
* org.eclipse.cdt.core* => cdt-core
 
* org.eclipse.cdt.debug* => cdt-debug
 
* org.eclipse.cdt.launch => cdt-launch
 
* org.eclipse.cdt.make* => cdt-build
 
* org.eclipse.cdt.managedbuilder* => cdt-build
 
* org.eclipse.cdt.refactoring* => cdt-core
 
* org.eclipse.cdt.ui* =>
 
  
 
== Tips ==
 
== Tips ==
  
 
* If you are behind a firewall, you can use the proxy server at eclipse.org to access the CVS repository using pserver on the proxy.eclipse.org and port 80.
 
* If you are behind a firewall, you can use the proxy server at eclipse.org to access the CVS repository using pserver on the proxy.eclipse.org and port 80.

Revision as of 04:14, 2 March 2007

Sending Patches

To make changes to the CDT, whether it be code, docs, JUnits, etc., you will need to send patches to the source stored on eclipse.org. Here is the process for sending patches.

  1. Create a workspace in Eclipse for your work. Check out the CDT plugins you'd like to work on into it. The plugins are on dev.eclipse.org, /cvsroot/tools. The plugins are under folder org.eclipse.cdt/all. There should be around 40 plugins there that you need to check out.
  2. Edit and test your change. This is all basic Eclipse plugin development. There are a number of resource on the web and in the Eclipse help system on how to do this.
  3. Use the Eclipse Team menu to create a patch. Eclipse 3.2 now lets you do it for your whole workspace. If you are stil on Eclipse 3.1, you will need to create a patch for each plugin you've changed.
  4. Attach the patch or patches to a bugzilla entry. Make sure you check off the patch box to help us find patches.
  5. Send a mail to the cdt-patch list to let the committer's know there is a patch ready.

One of the fundamental rules that Eclipse follows is the ability to trace back who contributed what code and that the person who contributed it has ownership of the code, or has permission from their employer to contribute the code (since employers tend to own everything you write). To help keep this IP integrity going, please ensure your contributions are "clean".

Tips

  • If you are behind a firewall, you can use the proxy server at eclipse.org to access the CVS repository using pserver on the proxy.eclipse.org and port 80.