Bug 338741 - Add a quick fix for IU conflict problems
Summary: Add a quick fix for IU conflict problems
Status: RESOLVED FIXED
Alias: None
Product: CBI
Classification: Technology
Component: CBI p2 Repository Aggregator (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P1 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: Debug - Conflicting IUs
Keywords: plan
Depends on: 338738 338739
Blocks:
  Show dependency tree
 
Reported: 2011-03-02 16:45 EST by Kenn Hussey CLA
Modified: 2016-09-16 15:57 EDT (History)
1 user (show)

See Also:
Kenn.Hussey: indigo+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenn Hussey CLA 2011-03-02 16:45:04 EST
Please add a quick fix option for IU conflict markers on features. This action should allow the feature to be moved to a new/existing aggregate in the composite repository.
Comment 1 Thomas Hallgren CLA 2011-04-14 07:52:49 EDT
Excerpt from chat with Michal:

There's only one thing left afaics. That's the "Add quick fix for IU conflicts which allows feature to be moved to new/existing aggregation in the composite". Not completely sure what's entailed in that. Can you brief me?
[1:45:02 PM CEST] Michal Růžička: This should offer some kind of "quick fix" to the user for the problems detected during verification - the problems which now have problem markers created as a result of https://bugs.eclipse.org/bugs/show_bug.cgi?id=338739 (well probably only the conflicting depedency versions problems, as there is not much that can be done automatically about missing dependencies).
The idea is that the "quick fix" should be something similar to for instance java editor offering to "add a cast" in case you are trying to assign a value to a varibale of incompatible type.
What the quick fix should do is: it should create a new Aggregate (or perhaps offer you to choose from existing ones), and move one of the conflicting Contributions there.
[1:47:25 PM CEST] Michal Růžička: Here is a testing model which loads quicky and can produce both the missing dependencies and conflicting problems:
[1:47:27 PM CEST] Michal Růžička: <?xml version="1.0" encoding="UTF-8"?>
<aggregator:Aggregator xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:aggregator="http://www.eclipse.org/b3/2010/aggregator/1.0.0" label="Geppeto Test" buildRoot="build-geppeto">
  <aggregates label="Geppetto 0.1.1"/>
  <configurations/>
  <contributions enabled="false" label="Geppetto 0.1.0">
    <repositories location="http://download.cloudsmith.com/geppetto/updates">
      <features name="org.cloudsmith.geppetto.feature.group" versionRange="[0.1.0.v20110204-1820,0.1.0.v20110204-1820]"/>
    </repositories>
  </contributions>
  <contributions enabled="false" label="Geppetto 0.1.1">
    <repositories location="http://download.cloudsmith.com/geppetto/updates">
      <features name="org.cloudsmith.geppetto.feature.group" versionRange="0.1.1.v20110211-1944"/>
    </repositories>
  </contributions>
  <contributions label="EMF 4 GWT">
    <repositories location="http://download.cloudsmith.com/emf4gwt/sdk">
      <features name="org.eclipse.emf.mapping.feature.group"/>
      <features name="org.eclipse.emf.databinding.feature.group"/>
    </repositories>
  </contributions>
</aggregator:Aggregator>
[1:47:58 PM CEST] Michal Růžička: If you disable both of the "Geppeto" contributions you get a missing dependency.
[1:48:46 PM CEST] Michal Růžička: If you keep the model as it is you get a conflict on the one of dependencies of the geppeto.
[1:49:40 PM CEST] Michal Růžička: If you move one of the "Geppeto" contributions into the "Geppeto" aggregate, the model will verify and build just fine.
Comment 2 Thomas Hallgren CLA 2011-04-29 08:59:54 EDT
Quickfixes added in trunk, rev 1469.
Comment 3 David Williams CLA 2016-09-16 15:57:04 EDT
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.
No change to assignee for resolved and verified bugs.]