... | ... | @@ -19,12 +19,12 @@ So far, it has been handled as one big piece of software: |
|
|
Few of the main problems with this approach are:
|
|
|
|
|
|
* Many unused plugins becomes obsolete and pollute the SVN repository. +
|
|
|
When compatibility-breaking modfifications
|
|
|
When compatibility-breaking modifications
|
|
|
are performed on other used plugins, we either need to update such plugins
|
|
|
(tedious, time consuming) to be able to build the project or exclude
|
|
|
them from the build, which essentially turns them into zombies.
|
|
|
* The build/test process is long and tedious.
|
|
|
* Plugins Versionning is virtually impossible.
|
|
|
* Plugins versioning is virtually impossible.
|
|
|
* Branch/Merge operations are very tedious which
|
|
|
|
|
|
To help solving these problems, most active {gecos} plugins from the SVN repository
|
... | ... | @@ -277,22 +277,36 @@ It contains the following entries: |
|
|
** *latest/*: link to the latest testing version
|
|
|
|
|
|
The individual project update sites are mainly used to ensure
|
|
|
dependencies between {gecos} projects.
|
|
|
|
|
|
|
|
|
Composite update site
|
|
|
~~~~~~~~~~~~~~~~~~~~~
|
|
|
In order to provide an overall {gecos} update site, a composite repository
|
|
|
is also provided at:
|
|
|
http://gecos.gforge.inria.fr/updatesite/releases/
|
|
|
|
|
|
It contains one entry per {gecos} release version and is also kept for
|
|
|
a very long time.
|
|
|
New releases (updates) will be automatically visible.
|
|
|
|
|
|
dependencies between {gecos} projects. +
|
|
|
Although, they can be used to install individual project features,
|
|
|
it is not recommended to use them for this purpose. Since Eclipse
|
|
|
may not be able to find dependencies to other {gecos} projects
|
|
|
unless their update site are also added! +
|
|
|
Use one of the <<section-compo-update-site, Composite update sites>> instead.
|
|
|
|
|
|
|
|
|
|
|
|
[[section-compo-update-site, Composite update sites]]
|
|
|
Composite update sites
|
|
|
~~~~~~~~~~~~~~~~~~~~~~
|
|
|
In order to provide an overall {gecos} update site, two composite repositories
|
|
|
are also provided.
|
|
|
|
|
|
Releases update site:
|
|
|
^^^^^^^^^^^^^^^^^^^^^
|
|
|
* http://gecos.gforge.inria.fr/updatesite/releases/
|
|
|
* provide access to all the released version of {gecos}.
|
|
|
* Individual releases can be accesses at http://gecos.gforge.inria.fr/updatesite/releases/<version>
|
|
|
* stable and kept for a very long time.
|
|
|
* new releases will be automatically visible.
|
|
|
|
|
|
Snapshot (updates) update site:
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
* http://gecos.gforge.inria.fr/updatesite/updates
|
|
|
* provide access to the *latest snapshots* on top of the released versions.
|
|
|
* new releases and latest snapshots (only!) will be automatically visible.
|
|
|
* developers should rather use this update site.
|
|
|
|
|
|
IMPORTANT: Users should rather use this update site to install {gecos}.
|
|
|
Updates will be automatically detected by eclipse.
|
|
|
|
|
|
|
|
|
Access to {gecos} Projects
|
... | ... | |