Hi Mickael,
Since it was to build “fake” modules for testing purposes, I was looking for a way to avoid publishing a target platform.
In the end using a targetplatform already present in Maven central did the trick. [1]
(Not sure if the build is faster than the one defining the target using the url.)
Depending of the configuration I always end up with either a “Project not found” or “Dependency not found”
I will try to setup a small example.
Regards,
Benoit
1:
<!-- Works but is it really faster ?-->
<groupId>org.integratedmodelling</groupId>
<artifactId>org.integratedmodelling.kim.target</artifactId>
<version>0.9.10</version>
De : tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
De la part de Mickael Istria
Envoyé : lundi 6 mars 2017 08:35
À : tycho-user@xxxxxxxxxxx
Objet : Re: [tycho-user] Shared target plaform for many independant module
On 03/02/2017 01:40 PM, MAGGI Benoit wrote:
So my tests modules all have the same parent but their parent isn’t an aggregator.
Whether parent is an aggregator or not shouldn't change anything regarding resolution.
What kind of error messages do you see? That's missing in your initial post.
Do you define the target platform to use as described in
https://wiki.eclipse.org/Tycho/Target_Platform#Target_files ? Are you sure this artifact is available for other modules to resolve it in different reactors: Is it `mvn install`ed in your local repository or available on a remote one modules can consume?
Like parent pom, Target definition artifacts are better being published on a remote Maven repo, so they can be consumed by multiple projects.
HTH
