LOGTOOL-159 - Allow jboss-logging-processor to operate as an incremental processor in Gradle builds

[sebersole]

LOGTOOL-159 - Allow jboss-logging-processor to operate as an incremental processor in Gradle builds

[sebersole]

Thanks for applying my PR James!

Any idea which version we can expect the fix in? It causes really painful compile times in Hibernate.

[jamezp]

@sebersole I'll try to get a release out later today or early next week. I know there are some other changes needed/wanted too :)

[sebersole]

@sebersole I'll try to get a release out later today or early next week. I know there are some other changes needed/wanted too :)

Thanks!

[jamezp]

@sebersole Released https://github.com/jboss-logging/jboss-logging-tools/releases/tag/3.0.0.Final

[sebersole]

@jamezp Given that its a major I'm a little worried about the ability to use this in Hibernate considering all the environments it is used in. Any thoughts on that? Is the processor from 3.0.0 usable with older versions of the api/annotations?

[sebersole]

At the moment, Hibernate uses -

• jboss-logging - 3.5.0.Final
• jboss-logging-annotations - 2.2.1.Final
• jboss-logging-processor - 2.2.1.Final

So would it be safe to drop in 3.3.0 for jboss-logging-annotations and jboss-logging-processor and keep using 3.5.0.Final for jboss-logging? I'll tias, but if you know...

[jamezp]

There shouldn't be a problem using 3.0.0.Final of tooling and annotations with older versions of the logging facade. If you find any though, please feel free to let me know :)

There was an issue using the 2.2.1.Final annotations with the 3.0.0.Final processor, but I wouldn't suggest that anyway :)