High Performance REST Applications (3) – Importing the Starter Project

Now you can import the projects required from Git.

First, go to „File > Import…

Import Project

Then select „Projects from Git“

Projects from Git

and „Clone URI“ to clone an existing repository:

Clone existing respository

To get the URI, you have to open https://github.com/hasselbach/ and select the repository „ch.hasselba.concurrent„. Click the „Clone or download„-Button and copy the URI from the opening box:

Get the repository URI

Paste the URI into the location in Eclipse

Add the URI to Eclipse

In the next dialog, you can choose the branch to import. In this case, only „master“ exists

Select the branch to import

Now you have to choose a local destination where the cloned repository will be stored

Select the local destination

Select „Import existing Eclipse projects„…

Import existing projects

… and select all projects of the repository:

Select all projects

With „Finish„, the sources are downloaded. In the „Project Explorer„, you can see the three imported projects. And you can see the original repository name and the current branch you are working on:

Repository & Branch

The JRE used for the project can be seen if you expand one of the projects. „Sometimes“ this changes magically, and the build will fail – that is one of the first things you have to check if you have errors in a OSGi project.

JRE / Target used for this project

Now, do the same for the „domino-rest-servlet“ repository. But instead importing the „master“ branch, select the „highperformance“ branch only.

Import HighPerformance Branch

That’s it. In the next post, we have take a look in what you have downloaded.

Dieser Beitrag wurde unter Java, JEE, OSGi, Performance, REST, Server, Web abgelegt und mit , , , , verschlagwortet. Setze ein Lesezeichen auf den Permalink.

4 Kommentare zu High Performance REST Applications (3) – Importing the Starter Project

  1. Andrew GR sagt:

    Hi Sven,

    thank you so much for providing such a great posts!

    Probably a silly question (maybe I have missed it somehow): is it any other way of some so called „in-place“ deployment of the code in order to simplify debuggin&development rather than going via standard way of plugin deployment into UpdateSite.nsf?

    Thank you so much for your feedback!

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.