Skip to main content
Jump to: navigation, search

Difference between revisions of "Recommenders/Infrastructure"

m (Compiling Sources in Eclipse)
(Compiling Sources in Eclipse)
Line 49: Line 49:
 
After you cloned the repository, import all required plug-ins, features, and update-sites from ${git-repository.basedir}. It's recommended to use a fresh Eclipse Workspace since we work with ''target platforms'' to build Code Recommenders in Eclipse. If you are new to target platforms please check out [http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.pde.doc.user/concepts/target.htm this Eclipse Help page] for details.
 
After you cloned the repository, import all required plug-ins, features, and update-sites from ${git-repository.basedir}. It's recommended to use a fresh Eclipse Workspace since we work with ''target platforms'' to build Code Recommenders in Eclipse. If you are new to target platforms please check out [http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.pde.doc.user/concepts/target.htm this Eclipse Help page] for details.
  
After import you will see quite a lot compile errors due to missing plug-ins not available in your current Eclipse installation. To fix that you need to set the target platform of the workspace. This is done by simply  
+
After import you will see quite a lot compile errors due to missing plug-ins not available in your current Eclipse installation. To fix that you need to set the target platform of the workspace. This is done by simply:
  
 
# Opening the target platform definition file under ''/org.eclipse.recommenders.releng/rcp-3.6.target''.
 
# Opening the target platform definition file under ''/org.eclipse.recommenders.releng/rcp-3.6.target''.
Line 57: Line 57:
 
# If not, refresh the complete workspace and trigger a second full rebuild manually.
 
# If not, refresh the complete workspace and trigger a second full rebuild manually.
 
# If still errors show up, report this incident to the developer mailing list :)
 
# If still errors show up, report this incident to the developer mailing list :)
# '''''Finally (and most important) you need to run Maven from command-line at least once! The recommender models are not hosted inside GIT but kept on a separate website. When running a full maven build, maven will recognize that the model zip files are missing and will download the automatically. If you skip this step, you will experience strange errors whenever you trigger Code Completion in Eclipse...'''''
 
  
 
Now you are ready to start a new Eclipse Runtime with Code Recommenders.
 
Now you are ready to start a new Eclipse Runtime with Code Recommenders.

Revision as of 04:58, 15 September 2011

Calendar

Backlog

https://spreadsheets.google.com/ccc?key=0ApWmyB4n3MejdHpvcGl2aENFV0hGa2Joc2ZYSkFxVVE&hl=en&authkey=COTbxbYO

GIT Repository

Committer: 
  git clone ssh://committer_id@git.eclipse.org/gitroot/recommenders/org.eclipse.recommenders.git

Anonymous:
  git clone git://git.eclipse.org/gitroot/recommenders/org.eclipse.recommenders.git


Committers, PLEASE NOTE: Eclipse.org will REFUSE pushed changes if the Committer entry is not YOU. Please ensure you configure your git environment correctly, by specifying your Eclipse Committer email address before committing.


Therefore, do one of the following:

EITHER via command line:

$ pwd
/Users/Marcel/Repositories/org.eclipse.recommenders
$ git config --local user.name "Marcel Bruch"
$ git config --local user.email "bruch@st.informatik.tu-darmstadt.de"

OR edit $REPO_HOME/.git/config and add the user section to the config file:

[user]
       name = Marcel Bruch
       email = bruch@st.informatik.tu-darmstadt.de


For more information about Git, please see the Git wiki page and migration guide:

AND see this pretty good screencast tutorial by Ralf Ebert:


Using Public Keys

See Git#Setting_up_ssh_keys, but not working for committers without shell access. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=312378


Compiling Sources in Eclipse

After you cloned the repository, import all required plug-ins, features, and update-sites from ${git-repository.basedir}. It's recommended to use a fresh Eclipse Workspace since we work with target platforms to build Code Recommenders in Eclipse. If you are new to target platforms please check out this Eclipse Help page for details.

After import you will see quite a lot compile errors due to missing plug-ins not available in your current Eclipse installation. To fix that you need to set the target platform of the workspace. This is done by simply:

  1. Opening the target platform definition file under /org.eclipse.recommenders.releng/rcp-3.6.target.
  2. Waiting until Eclipse resolved and downloaded all plug-ins (check the progress monitor). This may take a while for the first time.
  3. After resolving successfully finished, click on Set as Target Platform on the upper right corner of the editor.
  4. A workspace full build is now started by Eclipse. Wait until the build is finished. Hopefully all compile errors are gone now - except for org.eclipse.recommenders.*fixture* projects. They don't compile per construction :)
  5. If not, refresh the complete workspace and trigger a second full rebuild manually.
  6. If still errors show up, report this incident to the developer mailing list :)

Now you are ready to start a new Eclipse Runtime with Code Recommenders.

Project Website

Your project website is up and ready to be authored. Simply set up a new repository location:

host: dev.eclipse.org
repository: /cvsroot/org.eclipse
method: extssh

You have access to the www component, and specifically, the recommenders/ directory. Anything you commit to the recommenders/ directory will be automatically published to http://www.eclipse.org/recommenders/ within one minute.



Mailing lists

The recommenders-dev@eclipse.org list has been created. You can subscribe to the list here: https://dev.eclipse.org/mailman/listinfo/recommenders-dev . Subscription is required to post messages to the list.

Your mailing list will be added to the page (http://www.eclipse.org/mail/) after you have entered the required information into your ProjectInfo, via the Portal tools.

Newsgroups

The eclipse.recommenders list has been created on the news.eclipse.org server.

Your newsgroup will be added to the page (http://www.eclipse.org/newsgroups/) after you have entered the required information into your ProjectInfo, via the Portal tools.:

If you need additional mailing lists or newsgroups, please contact webmaster@eclipse.org

Downloads

You have a downloads area with 2GB of space. To access this area, simply use an SFTP or SCP client (such as CoreFTP or WinSCP) in SSH mode to transfer your files. Refer to the File Paths section in the Committer Tools for the downloads area to see where you should be publishing downloadable files. Please be diligent when transferring files: the downloads area is mirrored to over 70 mirror sites worldwide.

To link to a downloadable file, use the following path:

 <a href="http://www.eclipse.org/downloads/download.php?file=/recommenders/recommenders-1.0.0.zip">you name it</a>

This will ask users to pick a mirror site for the file, and it will add technology.recommenders downloads to our download statistics (also in the Committer Tools, Live Download Stats).

Bugzilla

Your bugzilla project, components, versions (if specified) and milestones (if specified) have been created.

If your committers had a bugzilla account that matches the e-mail address supplied to the Foundation, their account was granted standard committer rights to edit and confirm bugs. If the committers didn't have a bugzilla account, they should create one using the same e-mail address as supplied to the Foundation and contact webmaster@eclipse.org to have their account upgraded with committer rights.

Back to the top