[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ebr-dev] Suspicious warnings on "mvn clean package -f releng/p2"
|
Hi Andreas,
The warning is actually a limitation. The "All Bundles" categories should fetch everything it sees into the repository. The idea is to get rid of the aggregation feature, which currently requires to list bundles manually. Now, there probably could be a switch in Tycho that would prevent including bundles from the local Maven repo but only consider the current reactor and target platform. But that's up to the Tycho team (if they ever are going to implement it).
As a workaround, I suggest using a separate local Maven repository for the recipes build (eg., -Dmaven.repo.local=$HOME/.m2/ebr-repo).
BTW, the aggregation feature currently only lists three bundles. Thus, I doubt the p2 repo is useful for you guys. Would be great to see a pull request once in a while. :)
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
> On 08 Jul 2016, at 08:24, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> wrote:
>
> Hi,
>
> I am building the recipes following the advice in the README [1].
> Building the recipes works fine, but building the p2 repository gives
> rise to some warnings which worry me:
>
>> WARNING] Mirror tool: Problems resolving provisioning plan.: Unable to satisfy dependency from v20150830-1840.all 1.0.0.EG4EgsEMEcLiEQ-Lh-Wb5bf4CV_TBW2U10Q to org.eclipse.recommenders.overrides.rcp [2.4.3.v20160708-1339].; ...
>
> It seems like the All Bundles category tries (not sure if it succeeds)
> all the bundles in my local Maven repository, which contains
> locally-built Code Recommenders bundles, among other things. These
> bundles certainly should not end up on the p2 update site; only the ones
> build by recipes should.
>
> I tried to work around this by explicitly listing all bundles as
> <dependencies> of the p2 project, configuring a
> target-platform-definition with
> <pomDependencies>consider</pomDependencies>, and building with
> -Dtycho.localArtifacts=ignore, in the hope that this would only consider
> those artifacts listed explicitly, but to no avail.
>
> Does anyone know how to get rid of this worrying warning (save nuking
> ~/.m2/repository before every build) or do I worry too much? ;-)
>
> Best wishes,
>
> Andreas
>
> [1] <https://github.com/eclipse/ebr>
>
> --
> Codetrails GmbH
> The knowledge transfer company
>
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-170-811-3791
> http://www.codetrails.com/
>
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940
> _______________________________________________
> ebr-dev mailing list
> ebr-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ebr-dev
