JSR-303 error when upgrade from 0.6.1 to 0.8.1

[zolabh]

I have just upgraded my module to to use 0.8.1 from 0.6.1 and I am now seeing an ERROR message in the build output.

[INFO] jcabi-aspects 0.17.1/8b0e260 started new daemon thread jcabi-cacheable for automated cleaning of expired @Cacheable values Nov 05, 2014 4:31:05 PM org.hibernate.validator.internal.util.Version <clinit> INFO: HV000001: Hibernate Validator 5.1.2.Final
[ERROR] JSR-303 validator failed to initialize: Unable to instantiate Configuration. (see http://www.jcabi.com/jcabi-aspects/jsr-303.html)
[INFO] jcabi-aspects 0.17.1/8b0e260 started new daemon thread jcabi-loggable for watching of @Loggable annotated methods

I have an explicit depenency on a Hibernate validator in the pom but it is not version 5.1.2.Final - I do not know why 5.1.2.Final is trying to be used here, and why it is an ERROR when it was not before.

[yegor256]

the latest version of jcabi-aspects is 0.20.. why 0.8.1? or I mis-understood you?

[zolabh]

Sorry, I mis-typed. I was using jcabi-mysql-maven-plugin 0.6.1, and upgraded to 0.8.1. It is the ERROR and associated messages that are thrown from within jcabi-aspects 0.17.1 when they were not in 0.12.

[yegor256]

Try to use latest versions and let me know if you still see the error:

• jcabi-maven-plugin: 0.9.4
• jcabi-aspects: 0.20

[zolabh]

Hi yegor thanks for the quick response. I am not using the jcabi-maven-plugin, but the jacabi-mysql-maven-plugin. The lastest version of which on Maven Central is 0.8.1.

After cloning the lastest version of the mysql plugin, 0.12.1, and making use version 0.20 of jcabi-aspects, the issue still remains.

[INFO] jcabi-aspects 0.20/9aa4822 started new daemon thread jcabi-cacheable for automated cleaning of expired @Cacheable values
Nov 06, 2014 1:00:34 PM org.hibernate.validator.internal.util.Version <clinit> INFO: HV000001: Hibernate Validator 5.1.2.Final
[ERROR] JSR-303 validator failed to initialize: Unable to instantiate Configuration. (see http://aspects.jcabi.com/jsr-303.html)
[INFO] jcabi-aspects 0.20/9aa4822 started new daemon thread jcabi-loggable for watching of @Loggable annotated methods

Cheers,
Z.

[yegor256]

Well, first of all, this issue should not affect your build. It is just a log message, that notifies you. Second, you can try this solution: yegor256/qulice#330 (similar plugin, similar problem)

[zolabh]

Hi yegor, I did include the dependency within the plugin, but the error still remains.

While you are correct this issue does not break the build, we do have downstream checks on the build log for ERROR messages. If this message is not an indication of something badly broken, perhaps it could be downgraded to a WARN or even INFO.

Quickest solution for me just now is to add a white-list with this ERROR so our build pipeline does not fail.

Thanks again,
Z.

[yegor256]

hm.. that is strange. this is definitely a problem of jcabi-mysql-maven-plugin and should be reported (and managed there). I'll make a ticket there: jcabi/jcabi-mysql-maven-plugin#49

[yegor256]

this ticket can be closed. we'll continue in that new one, if you don't mind.

[zolabh]

OK by me. Cheers.

[gvlasov]

@yegor256 This ticket is still open, shouldn't it be closed by now?

[yegor256]

@Suseika you're right, closing