Re: [cf-dev] Release new milestone

[Julien Vermillard <jvermillard@xxxxxxxxx>]

Stumbled on the same problem when trying to locally releasing californium.

My workaround was using good old "sed" file replace.

Anyway I'm testing cali + scandium + leshan master on AirVantage no-regression test suite, it's nearly working (except the problems reported by Simon on Scandium start/stop/resume).

Julien

On Thu, Oct 22, 2015 at 6:49 AM Kovatsch Matthias <kovatsch@xxxxxxxxxxx> wrote:

Yes. I noticed that the normal versions:set does not work anymore when I created RC1. There were also a couple of threads on this problem, but with no good solution.

 

versions:set on the parent POM (without any modules defined) and versions:update-parent in the other repos should fix that.

 

Ciao

Matthias

 

 

From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On Behalf Of Hudalla Kai (INST/ESY)
Sent: Mittwoch, 21. Oktober 2015 09:11

To: Californium (Cf) developer discussions
Subject: Re: [cf-dev] Release new milestone

 

I was not aware of this (yet). Thanks for sharing J

Is this due to the fact that we do not define the version in the POMs anymore but infer it from the referenced parent POM?

 

kai

_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev