Hi Mickael,
Thanks for the response.
I am actually looking at following wiki and it says that
"
Note: Tycho's interpretation of the target definition file format differs from the PDE in the following aspects:
- The location types "Directory", "Installation", and "Features" are not supported.
"
So I was expecting that its not possible using target files, but I'll give a try now. IMO the page should be updated if its supported.
- Thanks
From: tycho-user-bounces@xxxxxxxxxxx <tycho-user-bounces@xxxxxxxxxxx> on behalf of Mickael Istria <mistria@xxxxxxxxxx>
Sent: Thursday, October 29, 2020 2:31 PM
To: Tycho user list <tycho-user@xxxxxxxxxxx>
Subject: Re: [tycho-user] Building Plugin with Eclipse Installation | Surefire dependency on p2 repo
- Generic Question: Is there a way to build a plugin without using repositories, instead use the locally available eclipse installation to resolve build time dependencies?
- Surefire specific Question: The build system creates a product and lot of other p2 repositories that are not part of product. I am running tests using testRuntime=p2Installed and default work location. If I mention product p2-installable-unit as extra requirement
in target-platform-configuration, it pulls all the plugins related to product in work location.
I want to pull all the plugins from other p2 repositories (created during the same build or already existing) to work location, there are a lot ungrouped p2-installable-units and I don't want to mention everyone as extra requirement in target-platform-configuration.
I tried using target platform and mentioned the repositories in it but surefire doesn't pull them in work. How can I pull all plugins from a p2 repository for running tests with surefire?
There is no solution for this, you'll need to explicitly list the dependencies you need; or the minimal set of dependencies that expands transitively to everything you need (ie you can create a "everything" feature which references everything in the p2
repos and include it).
HTH
--
|