Community
Participate
Working Groups
A solution is required to update the Composite Repo automatically, when adding a new Release or Milestone on the repo. http://download.eclipse.org/papyrus-rt/updates/releases/neon/0.8.0/ http://download.eclipse.org/papyrus-rt/updates/milestones/neon/0.8.0/ Should Compose the Minor version of the repo. The 0.8.0 repository should regroup 0.8.0, 0.8.1, 0.8.2, ...
There is a ANT task existing for updating the composite reposository. An example is available here: http://www.lorenzobettini.it/2015/01/creating-p2-composite-repositories-during-the-build/
Yes, Lorenzo is a great resource for releng and product packaging matters. :-)
Is this something that needs to be in place, at least for the releases repo, already before the 0.8 release? If we need to fall back providing an Oomph end-user setup, I assume that we want to use the releases repo in that setup already for 0.8.
(In reply to Peter Cigehn from comment #3) > Is this something that needs to be in place, at least for the releases repo, > already before the 0.8 release? If we need to fall back providing an Oomph > end-user setup, I assume that we want to use the releases repo in that setup > already for 0.8. The only requirement for 0.8 is that we have the capability for users to download an RCP and for an Oomph-based installation be available for both users and testers. This bug would be needed in 0.8 IFF it makes meeting this requirement easier, or if it _greatly_ complicates handling of future releases, else it can and should be deferred. There have been many things happening with the build in the week preceding a release date (which should have been Oct 14 but will ow most likely be Oct 19) that appears to have caused problems. Let's concentrate on releasing 0.8 before solving all the problems. And by the way, we also have 0.7.x releases, but at this point, I don't really care about those and any adverse effects can be documented in the release notes.
Please indicate effort required.
I'm not assigned on the Papyrus RT project anymore. So I won't have time to do this. The effort should be 3-5 days to put the file ,ANT task in place. - Create ANT Task files: 3 days - Update pom Accordingly: 1 day - Test on the different Repo: 1 or 2 days depending on the repo availablity.
Defered to 1.0.1 - current manual approach will continue for now
Mass changing all 1.0.1 bugs to target milestone 1.0.2, because Bug 520039 depends on Bug 526168 which depends on Bug 526167 which modifies plugin MANIFEST files and therefore requires a new service version number in accordance to the guidelines at https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment. Hence the solution to these bugs must be merged as a new version (1.0.1) and therefore all old 1.0.1 bugs should become 1.0.2.
