Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Product dependency resolution does not match expected result in PDE
  • From: "Shannon, Joe (DLSLtd,RAL,LSCI)" <joe.shannon@xxxxxxxxxxxxx>
  • Date: Thu, 17 Dec 2020 23:06:07 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lRSPH6PaHMVcazWPMhKn/16aZnkUqkYOMDrHFKHtVvQ=; b=oMqfyWvhBLaqlebkKeaTAfK8/1iJeSfTVS6KwdelSIwTbRqUTIKDI7FU3tDsWJek4rkQSb6DsvhbrZM+WjSOLpicDboiFJ/ng5/kk3dap+OZpOMAaZgk/FumyUHgrgdT6067rcGDTBF5EaBpjAdSNowWcJaPC5LCOT3eBGueKet4z1naq62qjNYArV9Bytmu5ND/u0OLh3XU4D/ETfsrT/b97viioxRiHBHzFeXf1tA46Ptjj2IkBW95v/MgZYAF8KQeK51axatpdBf+AYymaiCwRIVu1E4dHCF+GAl29H528q3Rrekxr5FIdNyt/WGlnL8r0+Njly0fcuI6Fsl4Gw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=KN5bkLuqgDjV1zsrfqzHcy0kG/ei5/E+lllSHoMzwcBip2L6nJmnV3oiQyW3KmYFeLbTiBZClvZJqd2LahHHoyO+Rbb26eQJ67UbqGmw/Z7Gigo2vdIEi9suwCRF3aDvlHwCkn5OqmsrnCIclwIkAl1p9RLt9c0PsFQbzocbdK4gd/SNxLsUP5+BkHzli811htQG5NPmuFjEe0ebR2bnO4CQQ3B7NGKcpFV7L0Ay5M03sa/TymKQ1REwQ0rjY5Eu7KZPm8dTLKvGAnNk/Rygo0COp5xjkDsblRkkLD7XZL+Oj3FGycwvDWnVqIZqJj6VSaWFiRN+mDmWmrp1YXJLzA==
  • Delivered-to: tycho-user@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AQHW1GtQfqmUVVigxUyAwrspFky40Kn7hfyX
  • Thread-topic: [tycho-user] Product dependency resolution does not match expected result in PDE

Thank you all for your discussion.

To go along with my example, I have produced a minimal example:
This hopefully shows the type of simple use case where the option to validate the product on the Tycho side would be very helpful in order to maintain consistency with the experience in the IDE.

I understand there are workarounds in the IDE by manually modifying the launch configuration but for a simple product such as the example the better solution (as I understand it) is to fix the product contents or the requirements of an included feature.

I'm learning from Christoph's points and the bugs linked by Rolf that this part of PDE is even more complex and subtle than I was originally aware!

Let me know if this sounds reasonable.



This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

Back to the top