On Fri, Feb 6, 2015 at 10:52 AM, Michael Dürig <[email protected]> wrote: > > > On 4.2.15 10:39 , Robert Munteanu wrote: >> >> On Wed, Feb 4, 2015 at 11:37 PM, Michael Dürig <[email protected]> wrote: >>> >>> >>> >>>>> This is from outside out corporate network so referencing an internal >>>>> release does not work. However I don't have a clue why the bundle >>>>> plugin >>>>> baseline goal thinks it needs 1.1.5-r1654214. >>>> >>>> >>>> >>>> >>>> I think you have some maven metadata locally cached which says that >>>> this is the latest release before 1.1.6 . Try removing the >>>> ~/.m2/repository/..../oak-mk-api directory completely and see if that >>>> helps. >>> >>> >>> >>> Ok this seems to fix it. I wonder though why the baseline feature needs >>> to >>> poke around my local cache and then complain that it can't download >>> something it found there. Maybe worse, might it be that the baseline >>> feature >>> determines a different version to compare against depending on your >>> cache? >>> Something doesn't seem right here. >> >> >> I think that's the way Maven finds the latest version to compare >> against. Once the maven-bundle-plugin version 2.5.4 is released, you >> would at least see the version it's using >> >> https://issues.apache.org/jira/browse/FELIX-4666 >> > > Ok... but doesn't that mean that the baseline feature uses different > versions to compare against depending on the local cache, the network you > are in and probably the phase of the moon ;-) Doesn't seem very useful > then...
We could probably raise an enhancement request which allows restricting the versions considered, such as 'no qualifiers', or a regexp-based validation or ... Robert -- Sent from my (old) computer
