Update default camunda version to 7.2.0 about camunda-bpm-assert HOT 8 CLOSED

Shouldn't this be a 2.0 release since we have a lot of api changes? At least thats what I am planning to do on *-mockito and *-needle ...

from camunda-bpm-assert.

Well, I would for now just change the default build dependency for camunda-bpm-assert. Assert does not transitively draw in any camunda bpm version... so you provide your own anyway. And at the moment assert still works with 7.0.0-Final upwards. The moment we really add additional assertions for cmmn et al. I'd see a switch to 2.0... agreed?

from camunda-bpm-assert.

The motivation to change the minimal required version from 7.0 to 7.1 was to get rid of teh extra repositories and use maven central only ... I still do not get why you should build against 7.2 in version 1.2 while you will start to actually use 7.2 features with the 2.0 release ... I mean, it will probably not hurt anyone, but why bother?

from camunda-bpm-assert.

Well... you are right. At the same time camunda-bpm-assert 1.2 will be included into the coming archetypes for 7.2. So I have the slight feeling that it's better to show that "compatibility" with 7.2 in the pom just in case somebody looks. And in the comment it's written there, that assert is fully compatible with 7.0.0-Final upwards. The CI will integrate against all versions all the time, anyway.

from camunda-bpm-assert.

Convinced.

from camunda-bpm-assert.

See Issue #39 of why we should go to 7.2

from camunda-bpm-assert.

I think I prefer to implement as much assertions as possible with the minimum version necessary to get the particular job done. Therefore, I propose to use Camunda BPM FormService for #39.

from camunda-bpm-assert.

Implicitely resolved by #56. We compile now always with the current release (currently 7.4.0), but test against all releases.

from camunda-bpm-assert.