|
Thanks Igor and Mickael for the
explanation.
I can presume that the composition and url structure are being
maintained by hand or using OS scripts, nothing related to Tycho,
right?
regards.
Cristiano
On 20/08/12 12:32, Mickael Istria wrote:
On 08/20/2012 05:18 PM, Cristiano
Gavião wrote:
I'm
seeing lot of repository using a version in the url, as the one
you have sent me.
Is there any advantage in doing this way instead using a common
one, as the http://download.eclipse.org/releases/juno
?
in that case "juno" is more or less the version. But juno is an
aggregated repo made of several features coming from several
projects, so it's not numeric.
There is a big advantage in putting version in repository URL, it
makes easier to consume and track previous and future release of a
product, and it makes repository URL predictable. But it is often
useful, when using a version in repo URL, to put a symlink or a
copy of the repository to a fixed url for the latest version
(example, having /1.0 /1.1 /1.2 /2.0 ... for each version and
/latest pointing to the latest version of the repo - here /2.0 -
and updating latest on each new release).
There are a lot of places where this has been discussed, without
concluding to a specification/convention:
* http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00261.html
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=377111
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=331385
* probably other mailing-lists...
But this really depends on whether you can force consumers to
update, whether you need to keep previous versions, how often you
ship your repository, whether you have several "qualities"
(snapshot, milestone, release...) for your repositories that do
not target the same users...
There does not seem to be single best solution for all use-cases.
Cheers,
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
|
