codenvy-legacy / eclipse-plugin Goto Github PK

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

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

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

Detect if the tocken is expired.

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

• 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

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

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.

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

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.

Get a more stable with reliable SWTBot test results.

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

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

• Guava is not available in all Eclipse bundles

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

• 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

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"

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

Describe the project, site, Liscence etc ...

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

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.

• Test the Codenvy nature
• Test project service methods

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

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

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

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

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

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

This task is just about retrieving a new token

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.

• 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