[jbosstools-dev] How should we deal with components of projects which have not changed since JBT 4.1.0.Final (eg., jbosstools-base/runtime) ?
Max Rydahl Andersen
manderse at redhat.com
Tue Oct 1 10:29:44 EDT 2013
On Tue, Oct 01, 2013 at 03:55:50PM +0200, Mickael Istria wrote:
>On 10/01/2013 02:03 PM, Max Rydahl Andersen wrote:
>>>One day, developers will have to deal with something like this: http://blog.osgi.org/2013/09/baselining-semantic-versioning-made-easy.html
>>>, which is quite strict.
>>This is what we in theory already should be doing - but yes, because
>>we tend to release all together we haven't seen the impact of when
>>it was forgotten.
>I'm more thinking about automating the check so that build fails if a
>bundle is in the same version or older as baseline (last release). And
>later, even fail the build on the criterion of semantic versioning
>(comparing APIs and check whether the right version bump was applied).
Yes, i'm all for enabling that if possible.
>--
>Mickael Istria
>Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
>My blog <http://mickaelistria.wordpress.com> - My Tweets
><http://twitter.com/mickaelistria>
More information about the jbosstools-dev
mailing list