Jump to: navigation, search

Difference between revisions of "G-Eclipse"

(g-Eclipse Project)
(Important Links)
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== g-Eclipse Project ==
+
== 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 Planning ===
+
* Weekly-Meetings Minutes: [[G-Eclipse/Meeting Minutes|Minutes]]
 
+
g-Eclipse project will provide the following releases:  
+
  
* g-Eclipse 0.5.0  (June 2007) <br> including the following features:
+
== g-Eclipse FAQ ==
** Grid authentication management
+
** Grid resource management
+
** Grid job management
+
** Grid data management
+
** including an implementation for the gLite [http://www.glite.org] middleware.
+
  
* g-Eclipse 1.0.0  (June 2008) <br> including the following planed features:
+
==== Does g-Eclipse support middleware XYZ? ====
** including an implementation for a second Grid middleware (not yet defined)
+
** revision of the core features
+
** final definition of API and extension points
+
+
  
=== Obtaining the source code ===
+
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.
  
The source code that is currently in the Subversion repository has some external dependencies which are not yet resolved.
+
== g-Eclipse Developer 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>.
+
==== How to work with the Subversion repository? ====
It contains the usual svn directory structure <tt>TRUNK</tt>, <tt>BRANCHES</tt>, and <tt>TAGS</tt>. The development
+
Follow this link: [http://www.eclipse.org/geclipse/contributing.php]
version of the code can be found in <tt>TRUNK</tt>.
+
  
Within this folder there are several subdirectories:
+
==== How can I change my SSH password in Subclipse? ====
 +
When using Subclipse with SVNKit the user password is stored in an encrypted keyring file.
  
* <tt>doc/</tt> documentation and documentation plug-ins
+
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.
* <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.
+
BUT: All other passwords that are stored in this file are also lost!
Therefore it is not possible to compile it, until we have removed this dependency.
+
  
=== Installing the middleware specific extensions ===
+
For a dry-run use start Eclipse with the -keyring parameter:
  
...waiting for content...
+
<tt>eclipse -keyring c:\my_pw\eclipse.keyring</tt>
  
=== First steps with g-Eclipse ===
+
==== 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>
  
To help new users when trying out g-Eclipse, we have included some documentation in
+
# 'Synchronize with Repository' and integrate all incoming changes. Look for possible compile problems or conflicting changes and fix them...
the Eclipse help system, and as cheat-sheets which will guide you though the
+
# 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.
process of creating your first g-Eclipse Grid 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.
  
* Eclipse Help: Help | Help Content | 'g-Eclipse'
+
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:
* Eclipse Cheat-Sheets: Help | Welcome | Tutorials | 'Set up your g-Eclipse environment'
+
#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
  
  
  
--[[User:Mknauer.innoopract.com|Mknauer.innoopract.com]] 14:32, 4 March 2007 (EST)
+
[[Category:g-Eclipse]]

Latest revision as of 07:10, 30 March 2009

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

  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