Hi, Ernesto,
See some replies in-line, below.
Christian
On 24 October, 2016 at 17:33:07, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote: Hi everyone.
according to
A couple of questions:
1) should the actual repo be manually copied to the following?
No. At that location should be a composite repository that aggregates all of the R<stamp> beneath it. I have done that manually, for now, but really the build job ought to generate that. In fact, I’ve composed the releases right up to the https://download.eclipse.org/papyrus-rt/updates/releases/ level, which then includes all of the Mars and Neon releases so far. Having the seemingly superfluous level of R<stamp> under the 0.8.0 actually is, I think, a good idea in case there needs to be a re-spin of the 0.8.0 release. That would just be another R<stamp> in the composite.
2) the build seems to execute some "materialize-product" goal which seems to take a lot of time and install the product. Is this expected?
Yes, this typically takes quite a while. The Tycho materialize-products goal runs the p2 Director application to create a a product installation. This is a subset of what Oomph does, for example.
3) the build fails with what appears to be some sort of UI testing error when executing the .
source/releng/scripts/postbuild-publish.sh script. What's this about and how do we fix it?
--
Ernesto Posse Zeligsoft
_______________________________________________ papyrus-rt-dev mailing list papyrus-rt-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
