Community
Participate
Working Groups
The MDT/OCL nightly build is failing with the following error (among others): WARNING [0044] : Component request org.eclipse.emf.mwe.ui:osgi.bundle/[1.1.0.v201105030247,2.0.0) is inconflict with request org.eclipse.emf.mwe.ui:osgi.bundle/[1.1.0.v201104201124,1.1.0.v201104201124] ERROR [0044] : No suitable provider for component org.eclipse.emf.mwe.ui:osgi.bundle/[1.1.0.v201105030247,2.0.0) was found in resourceMap file:/opt/users/hudsonbuild/workspace/buckminster-mdt-ocl-core-3.1-nightly/org.eclipse.mdt/org.eclipse.ocl/releng/org.eclipse.ocl.releng.buckminster/releng/ocl-platform.rmap ERROR [0044] : No suitable provider for component org.eclipse.emf.mwe.ui:osgi.bundle/[1.1.0.v201105030247,2.0.0) was found in searchPath mwe ERROR [0044] : Rejecting provider p2({0}/modeling/emft/mwe/updates/nightly[file:/home/data/httpd/download.eclipse.org/modeling/emft/mwe/updates/nightly]): No component match was found Said org.eclipse.emf.mwe.ui plugin has the following version in the following repositories: - org.eclipse.emf.mwe.ui_1.1.0.v201104201124.jar in the mwe nightly repository. - org.eclipse.emf.mwe.ui_1.1.0.v201105030247.jar in the mwe milestones repository. Since our nightly builds, is based on nightly repositories (as long as possible) it would be good if mwe nightly repositories are real nightly repositories. Would you mind running and promoting an N-build to create a proper P2 nightly repository ? Marking the bug as blocker, since our (nightly) builds are currently blocked. Best Regards, Adolfo.
> Since our nightly builds, is based on nightly repositories (as long as > possible) it would be good if mwe nightly repositories are real nightly > repositories. Mwe nightly repository is the most real nightly repository ever! :) The point is that 201104201124 *is* the latest nightly build and there is no reason to produce a new nightly after the latest stable 201105030247. So the real problem is that Xtext and Xpand are build against the last successful mwe hudson build, which is the latest stable mwe and not against the latest nightly. > > Would you mind running and promoting an N-build Sure. Unfortunately I have no permission to trigger the new OCL to verify. Marking bug as normal. TODO: Xtext - we should change pde.match.rule.default to compatible. Investigate possible side effects.
Latest MDT/OCL build is back to normal.
Dennis, Thanks for looking at this... (In reply to comment #1) > > Since our nightly builds, is based on nightly repositories (as long as > > possible) it would be good if mwe nightly repositories are real nightly > > repositories. > Mwe nightly repository is the most real nightly repository ever! :) > The point is that 201104201124 *is* the latest nightly build and there is no > reason to produce a new nightly after the latest stable 201105030247. > So the real problem is that Xtext and Xpand are build against the last > successful mwe hudson build, which is the latest stable mwe and not against the > latest nightly. Ok. I think I understand the problem... Is this situatio expected ? or... are you changing your releng config so that your N-builds use N-repositories instead of the last successful one ? ... If your nightly repository is the most real nightly repository, your milestonre repository (last successful) should be identical. Therefore, It looks like there should not be any problem to make Xtext and Xpand N-builds use mwe nightly repository (instead of the last sucessful one)... > > > > Would you mind running and promoting an N-build > Sure. Unfortunately I have no permission to trigger the new OCL to verify. > Ok, this should make our build work (as Ed has pointed out) > Marking bug as normal. > > TODO: Xtext - we should change pde.match.rule.default to compatible. > Investigate possible side effects. Would you mind providing some information about this ?. motivations, advantages, disadvantages ? I thinks that I still have some bits to learn about releng, p2, features version match, etc :) Cheers, Adolfo.
Seems like this issue was solved.
