Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "G-Eclipse"
(→Important Links) |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Important Links == | == Important Links == | ||
| − | * Project Homepage @ Eclipse.org: [http://www.eclipse.org/geclipse] | + | * Project Homepage @ Eclipse.org: [http://www.eclipse.org/geclipse] |
| − | * Project Homepage of the Eclipse Consortium: [http://www.geclipse.eu] | + | * Project Homepage of the g-Eclipse Consortium: [http://www.geclipse.eu] |
* Milestone and Release Planning: [http://www.eclipse.org/geclipse/plan.php g-Eclipse Planning] | * Milestone and Release Planning: [http://www.eclipse.org/geclipse/plan.php g-Eclipse Planning] | ||
| + | * Weekly-Meetings Minutes: [[G-Eclipse/Meeting Minutes|Minutes]] | ||
| − | == g-Eclipse | + | == g-Eclipse FAQ == |
| − | ==== | + | ==== Does g-Eclipse support middleware XYZ? ==== |
| − | + | ||
| − | + | Please look at [[g-Eclipse-Middleware-Extensions]]. If you are interested in implementing your own middleware specific extension above the g-Eclipse framework, please tell us on the g-Eclipse developer mailing list. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | == g-Eclipse Developer FAQ == | |
| − | + | ||
| − | + | ==== How to work with the Subversion repository? ==== | |
| − | + | Follow this link: [http://www.eclipse.org/geclipse/contributing.php] | |
| − | + | ||
==== How can I change my SSH password in Subclipse? ==== | ==== How can I change my SSH password in Subclipse? ==== | ||
| Line 36: | Line 32: | ||
<tt>svn://dev.eclipse.org:/svnroot/technology/eu.geclipse</tt> | <tt>svn://dev.eclipse.org:/svnroot/technology/eu.geclipse</tt> | ||
| − | # 'Synchronize with Repository' and integrate all incoming changes. Look for possible compile problems or conflicting changes and fix | + | # 'Synchronize with Repository' and integrate all incoming changes. Look for possible compile problems or conflicting changes and fix them... |
# Select all projects that contain your outgoing code changes; by right-clicking you will find 'Team' > 'Create Patch'; use the unified diff format, and choose workspace if you changed code in more than one project. | # Select all projects that contain your outgoing code changes; by right-clicking you will find 'Team' > 'Create Patch'; use the unified diff format, and choose workspace if you changed code in more than one project. | ||
# Now this is important: Create a new Bugzilla item (or use an already existing if there is an appropriate one), describe your changes and attach your patch to the Bugzilla item.<br>While the diff/patch works fine with ASCII data, it has its problems with binary files. These files are usually not included in the patch, so please attach all binary files (images, jar's, ...) separately to the Bugzilla item. | # Now this is important: Create a new Bugzilla item (or use an already existing if there is an appropriate one), describe your changes and attach your patch to the Bugzilla item.<br>While the diff/patch works fine with ASCII data, it has its problems with binary files. These files are usually not included in the patch, so please attach all binary files (images, jar's, ...) separately to the Bugzilla item. | ||
# A committer should review the patch and integrate it into the subversion repository. | # A committer should review the patch and integrate it into the subversion repository. | ||
| + | |||
| + | If your solution comes up with a complete new plug-in or a new project, you cannot build a diff against a repository. In that case please export your new project to a .zip or .tar.gz archive and attach it to a bug as described above. For the archive creation please follow these steps: | ||
| + | #open 'File' > 'Export...' > 'General' > 'Archive File' | ||
| + | #select all new plug-ins that you have developed and export them to an archive file (e.g. a ZIP file) | ||
| + | #attach this archive file to the appropriate bug | ||
| + | |||
| + | |||
| + | |||
| + | [[Category:g-Eclipse]] | ||
Latest revision as of 07:10, 30 March 2009
Contents
Important Links
- Project Homepage @ Eclipse.org: [1]
- Project Homepage of the g-Eclipse Consortium: [2]
- Milestone and Release Planning: g-Eclipse Planning
- Weekly-Meetings Minutes: Minutes
g-Eclipse FAQ
Does g-Eclipse support middleware XYZ?
Please look at g-Eclipse-Middleware-Extensions. If you are interested in implementing your own middleware specific extension above the g-Eclipse framework, please tell us on the g-Eclipse developer mailing list.
g-Eclipse Developer FAQ
How to work with the Subversion repository?
Follow this link: [3]
How can I change my SSH password in Subclipse?
When using Subclipse with SVNKit the user password is stored in an encrypted keyring file.
If someone has problems with his/her username/password and the svn+ssh://dev.eclipse.org connection, it is worth to look for a file called '.keyring' in the configuration area ('configuration/org.eclipse.core.runtime/'). If you remove this file, SVNKit will ask for your username/password the next time you try to access the Subversion repository.
BUT: All other passwords that are stored in this file are also lost!
For a dry-run use start Eclipse with the -keyring parameter:
eclipse -keyring c:\my_pw\eclipse.keyring
I am a contributor, not a committer: How do I add my code changes?
If you have checked out the g-Eclipse projects from the following read-only URL and you have done some programming... svn://dev.eclipse.org:/svnroot/technology/eu.geclipse
- 'Synchronize with Repository' and integrate all incoming changes. Look for possible compile problems or conflicting changes and fix them...
- Select all projects that contain your outgoing code changes; by right-clicking you will find 'Team' > 'Create Patch'; use the unified diff format, and choose workspace if you changed code in more than one project.
- Now this is important: Create a new Bugzilla item (or use an already existing if there is an appropriate one), describe your changes and attach your patch to the Bugzilla item.
While the diff/patch works fine with ASCII data, it has its problems with binary files. These files are usually not included in the patch, so please attach all binary files (images, jar's, ...) separately to the Bugzilla item. - A committer should review the patch and integrate it into the subversion repository.
If your solution comes up with a complete new plug-in or a new project, you cannot build a diff against a repository. In that case please export your new project to a .zip or .tar.gz archive and attach it to a bug as described above. For the archive creation please follow these steps:
- open 'File' > 'Export...' > 'General' > 'Archive File'
- select all new plug-ins that you have developed and export them to an archive file (e.g. a ZIP file)
- attach this archive file to the appropriate bug