Re: [cross-project-issues-dev] aggregation conflict of TM Terminal with PTP
It looks like org.eclipse.ptp.remote.terminal has an includes statement for the Terminal with an old version: cd /home/data/httpd/download.eclipse.org/tools/ptp/builds/kepler/milestones/M5/features unzip -p org.eclipse.ptp.remote.terminal_7.0.0.201301162143.jar feature.xml ?xml version=1.0 encoding=UTF-8? feature id=org.eclipse.ptp.remote.terminal label=%featureName version=7.0.0.201301162143 provider-name=%providerName [...] includes id=org.eclipse.tm.terminal version=3.2.0.201205300905-41-312316411A16/ includes id=org.eclipse.tm.terminal.view version=2.3.0.201205300905-32-312316411A16/ I'm not sure what's the best way resolving this. It might work if PTP simply builds after TM (assuming that it can pull in the TM milestone contribution). There used to be some conversation about includes vs requires of features, and I seem To remember that requires was always considered better... Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David Dykstal Sent: Sunday, February 03, 2013 7:51 PM To: cross-project-issues-dev@eclipse.org Subject: [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 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] aggregation conflict of TM Terminal with PTP
This should be fixed. Rebuilding now. Greg On Feb 4, 2013, at 4:54 AM, Oberhuber, Martin martin.oberhu...@windriver.com wrote: It looks like org.eclipse.ptp.remote.terminal has an “includes” statement for the Terminal with an old version: cd /home/data/httpd/download.eclipse.org/tools/ptp/builds/kepler/milestones/M5/features unzip -p org.eclipse.ptp.remote.terminal_7.0.0.201301162143.jar feature.xml ?xml version=1.0 encoding=UTF-8? feature id=org.eclipse.ptp.remote.terminal label=%featureName version=7.0.0.201301162143 provider-name=%providerName […] includes id=org.eclipse.tm.terminal version=3.2.0.201205300905-41-312316411A16/ includes id=org.eclipse.tm.terminal.view version=2.3.0.201205300905-32-312316411A16/ I’m not sure what’s the best way resolving this. It might work if PTP simply builds after TM (assuming that it can pull in the TM milestone contribution). There used to be some conversation about “includes” vs “requires” of features, and I seem To remember that “requires” was always considered better… Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David Dykstal Sent: Sunday, February 03, 2013 7:51 PM To: cross-project-issues-dev@eclipse.org Subject: [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 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[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___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
