[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] Build a product from features
|
So do you expect that Tycho is automatically able to find A.1 etc? This was implemented once (the so-called "Tycho repositories"), but the implementation did not scale, and there is no solution that could scale (see [1] for details).
So to solve this problem, you need to specify a search scope smaller than "all artifacts in a Maven repository". This can for example be done through POM dependencies, or via p2 repositories.
In your case, the latter is what you probably want: Build p2 repositories in both project A and B, and add them to the target platform of project C. If you have your own Nexus for exchanging binary artifacts, you probably want Tycho's nexus-unzip-plugin [2] to easily reference deployed p2 repositories.
Regards
Tobias
[1] https://issues.sonatype.org/browse/TYCHO-335
[2] http://wiki.eclipse.org/Tycho/Nexus_Unzip_Plugin
> -----Original Message-----
> From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-
> bounces@xxxxxxxxxxx] On Behalf Of Beuck, Torsten
> Sent: Freitag, 18. Januar 2013 12:24
> To: 'tycho-user@xxxxxxxxxxx'
> Subject: [tycho-user] Build a product from features
>
> Hi,
>
> I'm trying to build a product out of three features where two of them
> resulted from different reactor builds. The setup is the following:
>
> Project A
> - plugin A.1
> - plugin A.2
> - feature A consisting of the plugins A.1 and A.2
>
> Project B
> - plugin B.1
> - plugin B.2
> - feature B consisting of the plugins B.1 and B.2
>
> Project C
> - plugin C.1
> - plugin C.2
> - feature C consisting of the plugins C.1 and C.2
> - product consisting of the features A, B and C.
>
> If I'm building A, B and C locally everything works fine. But if I deploy
> the artifact to our internal Nexus repository and another developer tries
> to build only C the build fails because of unsatisfied dependencies to the
> features A and B. If I am defining feature C to contain all Plugins (A.1,
> A.2, B.1, B.2, C.1 and C.2) and modify project C's POM such that pom-
> dependencies to the A and B plugins are added and Tycho "considers" pom-
> dependencies, it works.
> But that is not the desired configuration. Are there other ways to deal
> with not locally available features that are not in a P2 Repository but
> only in a "central" Maven repository?
>
> Regards,
> Torsten
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
