A step-by-step guide to set up a p2 repository for your GitHub projects the right way
There are different options to make an Eclipse plugin available to the end user. The bundle in question can be packed in an archive file to be downloaded and installed manually or can be distributed via a proper repository and installed using the Eclipse install/update software manager.
The latter is preferred for a number of reasons. Now, the problem of creating such a repository, or update site, can be addressed in several, more or less complex, ways which rely on a different set of tools. To read further on the topic see the post Build a cross-platform JOGL Eclipse plugin using Tycho.
Once an Eclipse update site has been generated and is available locally on your machine it still needs to be published such that can be accessed via a simple URL. Assuming the source code of your plugin is hosted on GitHub wouldn’t be great to have the repository there as well?
The distribution of a binary package, thus the plugin archive mentioned before, on GitHub is achieved defining a Releases. But how can we set up our Eclipse update site instead?
To publish the update site you still have to create teh update site project, fill in the details of the site content in the site.xml file
then you add the pom.xml, for MAven/tycho to take care of the packaging of the site to be uploaded and accessed at a given URL
use tycho eclipse-repository target… put it by hand
The next step is how to set up your environment to exploit GitHub Pages functionality.
CREATE GOOGLE PAGE
find and ADD GOOGLE ANALYTICS CODE