| Summary: | A cspec can only declare a dependency to one version of a component | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | David Samuelsson <david.samuelsson.se> |
| Component: | Buckminster | Assignee: | buckminster.core-inbox <buckminster.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david.samuelsson.se, milesparker, philippn, thomas |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
David Samuelsson
I just fixed this problem in another bugzilla. It's not published yet but I plan to do that during the day today. *** This bug has been marked as a duplicate of bug 319329 *** This doesn't seem to be a duplicate after all. The problem is in the cspec. A dependency can be identified with name and type, but not with version. Consequently, a cspec may only declare _one_ dependency to a component of a specific type. I'm changing the name of this bug to reflect the problem. Fix released to helios-maintenance, rev 11518. (In reply to comment #4) > Fix released to helios-maintenance, rev 11518. Thomas, dumb question but how do we upgrade our headless installation to use this? This bug is a blocker for me. Update from our headless update site: http://download.eclipse.org/tools/buckminster/headless-3.6 I would recommend that you create a new headless installation from scratch using the director. OK, I'll wipe the current version out and start over if things don't work. But what I couldn't figure out is wether there is a simple way to just get an update for an existing buckminster in the same way that we can with eclipse ui. This doesn't seem to be possible with director -- you have to do something like: /Volumes/Resources/Developer/builds/director/director -d /Volumes/Resources/Developer/builds/director/builds/buckminster -p Buckminster -r "http://download.eclipse.org/tools/buckminster/headless-3.6/, http://download.cloudsmith.com/buckminster/external-3.6" -uninstallIU "org.eclipse.equinox.p2.director.feature.feature.group, org.eclipse.buckminster.core.headless.feature.feature.group, org.eclipse.buckminster.subversive.headless.feature.feature.group, org.eclipse.buckminster.pde.headless.feature.feature.group, org.eclipse.buckminster.git.headless.feature.feature.group, org.eclipse.buckminster.cvs.headless.feature.feature.group" -installIU "org.eclipse.equinox.p2.director.feature.feature.group, org.eclipse.buckminster.core.headless.feature.feature.group, org.eclipse.buckminster.subversive.headless.feature.feature.group, org.eclipse.buckminster.pde.headless.feature.feature.group, org.eclipse.buckminster.git.headless.feature.feature.group, org.eclipse.buckminster.cvs.headless.feature.feature.group" Yes, the director lacks a -updateIU. Or even a -updateAll or similar. There is an enhancement request for that, see bug 279659. Thanks Thomas. THis seems to have fixed the issue for me. I could have used the Hudson buckminster auto-installer but unfortunately it's setup to use subeclipse. (?) (In reply to comment #9) > I could have used the Hudson buckminster auto-installer but unfortunately it's > setup to use subeclipse. (?) Why is that a problem? (In reply to comment #10) > (In reply to comment #9) > > I could have used the Hudson buckminster auto-installer but unfortunately it's > > setup to use subeclipse. (?) > > Why is that a problem? Actually, it's not, if anything it seems to work better. :) I thought it was because of an svn issue that was cropping up but that seems to be unrelated. |