Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[tycho-user] Re: Preferred way to offer zipped, standalone update sites?


> I see .. so every time you push a new eclipse repository from the
> current build, you would like to refresh the composite repository to
> contain all required (not all) dependencies?
> Or should the composite update site only be mirrored once?

our Tycho build builds a couple of eclipse-repository projects (aka
update sites) each time it runs. Different update sites (head,
milestones, stable, ...) are promoted (copied to a webserver) at
different times, but all update sites are assembled during *every*
build. This doesn't slow down the build very much (as the update sites
contents are either cached or produced by the current reactor) and
prevents nasty surprises; we know that all update sites can be assembled
at any time.

Now, in addition to plain old eclipse-repository update sites, I would
also like to build an archive (.zip, .tar.gz, or similar) containing the
contents of one or more eclipse-repositories from the reactor *plus* the
contents of some external update sites. Again, I would like to
reassemble this archive during every build.

Now, these external update sites should of course not be downloaded in
their entirety upon each and every build, but upstream changes should be
picked up automatically; thus, it is fine if every build downloads a
remote content.jar, but it is not if downloads all bundles and features
(sort of like how Tycho deals with the target platform).

Hope that explains things a bit better.


Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

Back to the top