Re: jQAssistant

Running the build from any submodule => switch to gradle. However switching to gradle on a project hosted @ ASF yields another problem: the inability to host the gradle wrapper because it requires a binary (the wrapper jar). So yes, we're stuck with maven and everything it entails ;-) --

Re: jQAssistant

Hi Oliver yes, I wanted to discuss that with you, but did not have the time so far ;). Reason behind was that, once more, the build was breaking because of some bug in the tooling (not even a rule but simply some error message). I never had to spend so much useless and unproductive time with tools

Re: jQAssistant

+1 to get checkstyle by default (or to not use it at all). +1 for findbugs and jqassitant on demand (or on sonar build) Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn

Re: jQAssistant

I will reintegrate it, but it will be activate only on request. I suggest the same for checkstyle and finbugs. WDYT? Von meinem iPhone gesendet > Am 22.05.2015 um 19:17 schrieb Oliver B. Fischer : > > Anatole, you removed simply some parts of my work on the quality of the code > base by not o

jQAssistant

Anatole, you removed simply some parts of my work on the quality of the code base by not only disabling the tool but removing it at all. To be honest, I don't like such things because it does not respect the work of others. Oliver -- N Oliver B. Fischer A Schönhauser Allee 64, 10437 Berlin, D

Re: Release Preparation

I will create a dashboard in JIRA for all open issues for 0.1. Hope to be able it to do until tomorrow. Have to prepare a talk currently... Am 22.05.15 um 16:47 schrieb Tresch, Anatole : Would certainly help, then we can distribute the tasks to be done on whoever has time to help ;) -Or

Re: Release Preparation

+1, think we have done a pretty good writeup in BVal back then http://bval.apache.org/release-management.html LieGrue, strub > Am 22.05.2015 um 16:33 schrieb Oliver B. Fischer : > > Should I create a release document with all need preparations? > > WDYT? > > Von meinem iPhone gesendet > >>

RE: Release Preparation

Would certainly help, then we can distribute the tasks to be done on whoever has time to help ;) -Original Message- From: Oliver B. Fischer [mailto:o.b.fisc...@swe-blog.net] Sent: Freitag, 22. Mai 2015 16:34 To: dev@tamaya.incubator.apache.org Subject: Re: Release Preparation Should I c

Re: Release Preparation

Should I create a release document with all need preparations? WDYT? Von meinem iPhone gesendet > Am 22.05.2015 um 16:26 schrieb Tresch, Anatole > : > > Hi all, > > does anyone have more hints (some kind of checklist ?), what must be in place > to do a first release... > In the mean time we

Release Preparation

Hi all, does anyone have more hints (some kind of checklist ?), what must be in place to do a first release... In the mean time we have 80% plus test coverage on all modules I think, so I would say documentation, dist package are the most next steps. Beside we can still discuss on further aspec

RE: TAMAYA-79 : Updated ObservedConfigTest

Thanks Daniel I have integrated it in both the main events module as well as the example. Best, Anatole -Original Message- From: linead [mailto:lin...@gmail.com] Sent: Dienstag, 19. Mai 2015 08:17 To: dev@tamaya.incubator.apache.org Subject: Re: TAMAYA-79 : Updated ObservedConfigTest S