codenvy-legacy / eclipse-plugin

Codenvy plugin for Eclipse

Eclipse Plugin for Codenvy

Description

This project aims to provide an Eclipse plugin to give the ability to developers to work either on Codenvy or in Eclipse, sharing the same code base without the need of a Git repo.

Update sites

• Nightly Build: https://install.codenvycorp.com/eclipse-plugin/updates-nightly
• Main Update Site: https://install.codenvycorp.com/eclipse-plugin/updates

Build the project with Maven

Prerequisites:

• a Maven installation, minimum version 3.2,
• a JDK, minimum version 7.

Steps:

1. Clone the project:

    git clone https://github.com/codenvy/eclipse-plugin.git
   

2. Execute the following commands:

    cd eclipse-plugin
    mvn clean install
   

Warning: It will launch UI integration tests with SWTBot, be careful not to preempt focus when those tests are running to avoid a test failure.

Get this project working under Eclipse

Prerequisites:

• same as those of the Maven build,
• plus an Eclipse installation with m2e and PDE plug-ins installed,
• having a M2_REPO variable configured in Eclipse:
  1. In Eclipse preferences, go to ‘Run/Debug → String Substitution’.
  2. Create a ‘New String Substitution Variable’ with M2_REPO as name and the path to your Maven local repository as value.

Steps:

1. Import the Git project as a Maven project in Eclipse (be careful to import all its submodules too),
2. Wait for the projects to be configured (some errors should be reported on projects, it's normal as target is not yet configured),
3. For a Luna target, open 4.4.target under com.codenvy.eclipse.target (relative to project root),
4. Click on ‘Set as Target Platform’ in the upper right corner of the editor to set this as the default target platform,
5. Update all the projects (the root one and its submodules) through ‘Maven → Update Project…’.

Run the plugin

Once the project imported in Eclipse, right-click its sub-module com.codenvy.eclipse.ui and chose ‘Run as → Eclipse Application’.

Release the plugin

1. Clone the project:

    git clone https://github.com/codenvy/eclipse-plugin.git
    cd eclipse-plugin
   

2. Prepare release:

    mvn tycho-versions:set-version -DnewVersion=${releaseVersion}
    mvn clean install
    git commit -am "Prepare release ${releaseVersion}"
    git push origin master
   

3. Tag released version:

    git tag -a ${releaseVersion} -m "Tag ${releaseVersion}"
    git push origin ${releaseVersion}
   

4. Prepare for next development iteration:

    mvn tycho-versions:set-version -DnewVersion=${nextDevelopmentVersion}
    mvn clean install
    git commit -am "Prepare for next development iteration"
    git push origin master
   

License

Copyright (c) 2012-2014 Codenvy, S.A.

All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Contributors: Codenvy, S.A. - initial API and implementation

eclipse-plugin's Issues

Add java builder to imported project

Renew token when expired

Token is stored in secure storage. It can expire and must be renewed in this case.

Detect if the tocken is expired.

Add guava to codenvy feature

• Guava is not available in all Eclipse bundles

Project sync: define the sync model

Design how to implement, which format to use globally so Eclipse client can work offline and know what have been modified, new files, deleted files

Projects already imported in Eclipse should be grayed in selection wizard page

Project sync: Deleted resources are not deleted in Eclipse when updating

Add tests in com.codenvy.eclipse.core.test

• Workspace service : test workspace creation
• Project service : test project creation and get workspace projects

Add UI tests for issue #19

Things to test :

• retrieval of already existing URL (repository location) at wizard creation,
• behavior when filling URL field manually (completion if URL is an existing one in secure storage and has one or usernames associated, keep the list with the suggested one either),
• behavior when selecting the URL in the list,
• behavior when filling username field manually,
• behavior when on focus out,
• should enable next when all fields are completed.

Fix SWTBot instability under Jenkins

Get a more stable with reliable SWTBot test results.

Store Codenvy instance urls in eclipse preferences

In the first step of the import wizard the user select or type the codenvy url.

• The suggested urls in the combobox could be retrieved from eclipse preferences.
• The new added url would be added in the preferences automatically

Check in project service methods that workspaceId parameter needed

Ease the first setup of the project after cloning

Enrich the Readme to explain the step to follow to get a working project under Eclipse (SWTBot install, etc.).

Add UI tests for project import

• Working set
• Project available in project explorer view
• Projects already imported
• Test project Nature

Import selected Codenvy projects into Eclipse workspace

Project sync: get modified files from the server

Refactor Eclipse plugins package

Add Codenvy console to update site

See http://docs.codenvy.com/cli/

Use Require-Bundle or Import-Package in MANIFEST.MF

Explain Eclipse plugins installation with update site in readme

For now, installation can only be done with the local update site after the build.

Improve progress bar feedback when importing a project from Codenvy

• We could display the project file downloading
• There is a way to know the number of project files ?

Add core tests

• Test the Codenvy nature
• Test project service methods

Create a Jenkins job

For now,

• lib plugin has to be built before the Eclipse plugins and in another job. #28
• needs failsafe with tycho surefire. see #2
• swtbot on jenkins ? need headless or use xvnc

Rename GitHub repository to eclipse-plugin

Tyler said:

The top level project should be named eclipse-plugin to purposely avoid being too close to the other plugins :). The other plugins go into the sdk and are all the same structure, but this plugin is quite different.

When a project is imported the selected working set should be selected

Provides run on Codenvy options to imported projects

Remote Run in Codenvy

• In a Eclipse project with the Codenvy nature, provide a Eclipise Runner available throught "Run As" menu
• This would run the Remote Codenvy Runner
• The logs output are displayed in the Eclipse console
• Launch Embedded browser if this is a web app

Project sync: delete a file

Project sync: Push new files in the project

Better exception handling in REST api client

• for instance expired token. what to do ?
• if the workspace doesn't exist ? 404 ? to test
• no specs on the rest api

todo: list all the case we need to handle

Add javascript nature for AngularJS projects

Build fails in Linux

The argument '-XstartOnFirstThread' is only defined on Mac OS.

Use credentials in secure storage for project sync

When syncing a local project with its Codenvy remote repository, we should take the credentials stored in the secure storage of Eclipse to authenticate the user. Both user password and Codenvy token are stored.

Provides build on Codenvy options to imported projects

Use secure storage to retrieve identification token when needed

Renew token (if expired #39, when needed) based on the credentials in the secure storage

This task is just about retrieving a new token

Tycho surefire plugins don't stop Codenvy SDK on failure (when running integration test)

• For now, test failures are ignored. If one test fails the tycho-maven-plugin kills the maven build (the post-integration-test maven phase is not executed) and the codenvy sdk (running on tomcat) is not stopped
• Sometimes the build is failing because resources are not filtered

Deploy Codenvy eclipse plugin update sites

• Add update site url to features
• We need the following update sites
  • http://{host}/eclipse-plugin/updates - last release
  • http://{host}/eclipse-plugin/updates-nightly - last build from Jenkins
  • http://{host}/eclipse-plugin/updates-{version} - older versions, version is the version number

Import wizard allow creation of a working set

• Editable combo box
• If working set doesn't exist it is created on finish

No password completion on username selection

Store user credentials in Eclipse securely

• Credentials are stored per-project
• Store credentials in preferences ?
• Maybe the first wizard step can be simplified

First plugin build fails due to inner dependency problem

The parent POM of the plugin has a dependency on a child project com.codenvy.eclipse.lib. It makes the first build failing if you haven't build and installed com.codenvy.eclipse.lib first.

Ability to drag and drop or click on icon from IDE3 to import the project in Eclipse in one step

Idea could be the following :

• Drag and drop an "import into Eclipse" icon to Eclipse and then the project is imported (also if the plugin is missing, it could prompt to install it)
• This feature exist for installing an eclipse plugin
  We also have this kind of feature on GitHub with "clone into desktop"

Create abstract classes to simplify rest service implementation

Project sync: Implement push project changes to Codenvy

We can use the Team Provider feature from Eclipse (synchronize operations will be done by the user).

Update option in team menu must be disabled if selected resource is not tracked

Provides debug on Codenvy options to imported projects

Add Select All and Deselect All buttons to import project wizard page

Update features information and modify their names

Describe the project, site, Liscence etc ...

Add error marker if resources are missing

• '.codenvy' folder must exist
• '.codenvy/project' file must exist
• '.codenvy/team' file must exist

Add a services package in core plugin

Add natures to imported projects

Add logs to Eclipse plugins