Difference between revisions of "G-Eclipse"

From Eclipsepedia

Jump to: navigation, search
(repository description)
(Important Links)
 
(18 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== g-Eclipse Project ==
+
== Important Links ==
  
=== Obtaining the source code ===
+
* Project Homepage @ Eclipse.org: [http://www.eclipse.org/geclipse]
 +
* 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]
 +
* Weekly-Meetings Minutes: [[G-Eclipse/Meeting Minutes|Minutes]]
  
The source code that is currently in the Subversion repository has some external dependencies which are not yet resolved.
+
== g-Eclipse FAQ ==
We are working on a solution and expect something to download soon.
+
Please check this website for updates or the main website at [http://www.eclipse.org/geclipse].
+
  
The g-Eclipse subversion repository is available at <tt>svn://dev.eclipse.org:/svnroot/technology/eu.geclipse</tt>.
+
==== Does g-Eclipse support middleware XYZ? ====
It contains the usual svn directory structure <tt>TRUNK</tt>, <tt>BRANCHES</tt>, and <tt>TAGS</tt>. The development
+
version of the code can be found in <tt>TRUNK</tt>.
+
  
Within this folder there are several subdirectories:
+
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.
  
* <tt>doc/</tt> documentation and documentation plug-ins
+
== g-Eclipse Developer FAQ ==
* <tt>features/</tt> the core feature
+
* <tt>plugins/</tt> the core plug-ins (middleware independent) including <tt>eu.geclipse.core</tt> and <tt>eu.geclipse.ui</tt>
+
* <tt>releng/</tt> everything that is needed for building the feature; at the moment it contains a simple update-site project
+
* <tt>test/</tt> some JUnit tests
+
  
The plug-in <tt>eu.geclipse.core</tt> has one external dependency to a tar-library.
+
==== How to work with the Subversion repository? ====
Therefore it is not possible to compile it, until we have removed this dependency.
+
Follow this link: [http://www.eclipse.org/geclipse/contributing.php]
  
=== Installing the middleware specific extensions ===
+
==== How can I change my SSH password in Subclipse? ====
 +
When using Subclipse with SVNKit the user password is stored in an encrypted keyring file.
  
...waiting for content...
+
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.
  
=== First steps with g-Eclipse ===
+
BUT: All other passwords that are stored in this file are also lost!
  
To help new users when trying out g-Eclipse, we have included some documentation in
+
For a dry-run use start Eclipse with the -keyring parameter:
the Eclipse help system, and as cheat-sheets which will guide you though the
+
process of creating your first g-Eclipse Grid project.
+
  
* Eclipse Help: Help | Help Content | 'g-Eclipse'
+
<tt>eclipse -keyring c:\my_pw\eclipse.keyring</tt>
* Eclipse Cheat-Sheets: Help | Welcome | Tutorials | 'Set up your g-Eclipse environment'
+
  
 +
==== 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...
 +
<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 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.<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.
  
--[[User:Mknauer.innoopract.com|Mknauer.innoopract.com]] 14:32, 4 March 2007 (EST)
+
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

[edit] 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

[edit] g-Eclipse FAQ

[edit] 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.

[edit] g-Eclipse Developer FAQ

[edit] How to work with the Subversion repository?

Follow this link: [3]

[edit] 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

[edit] 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

  1. 'Synchronize with Repository' and integrate all incoming changes. Look for possible compile problems or conflicting changes and fix them...
  2. 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.
  3. 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.
  4. 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:

  1. open 'File' > 'Export...' > 'General' > 'Archive File'
  2. select all new plug-ins that you have developed and export them to an archive file (e.g. a ZIP file)
  3. attach this archive file to the appropriate bug