Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] aggregation conflict of TM Terminal with PTP

I get the following problem when validating the TM M5 contribution for Kepler. It appears that PTP has a strict requirement for a particular version of tm.terminal. Can this be corrected?
I haven't yet filed a PTP bug, but will if it is necessary.

Cannot complete the install because of a conflicting dependency.
Only one of the following can be installed at once:
  Target Management Terminal Widget 3.2.1.201209191030 (org.eclipse.tm.terminal 3.2.1.201209191030)
  Target Management Terminal Widget 3.2.2.201301071106 (org.eclipse.tm.terminal 3.2.2.201301071106)
  Target Management Terminal Widget 3.2.0.201205300905 (org.eclipse.tm.terminal 3.2.0.201205300905)

bundle(org.eclipse.tm.terminal 3.2.2.201301071106) is required by:
  ValidationSet(main)
    Contribution(TM)
      MappedRepository(http://download.eclipse.org/tm/updates/3.5milestones)
        Feature(org.eclipse.tm.terminal.local.feature.group 0.2.100)
bundle(org.eclipse.tm.terminal 3.2.0.201205300905) is required by:
  ValidationSet(main)
    Contribution(PTP)
      MappedRepository(http://download.eclipse.org/tools/ptp/builds/kepler/milestones/M5)
        Feature(org.eclipse.ptp.feature.group 6.0.4.201212181107)
          InstallableUnit(org.eclipse.ptp.remote.terminal.feature.group 7.0.0.201301162143)
            InstallableUnit(org.eclipse.tm.terminal.feature.group 3.2.0.201205300905-41-312316411A16)



-- David Dykstal,  Architect - Rational Developer for Power Systems

Back to the top