Well technically it is not valid according to the javac spec, which was
David's point (which I assume who you are referring to). And in fact
we get a slew of errors from running `javac -proc:only`. We just
happen to eat/ignore them.
For example, take hibernate-core as it is the more "complex"
On 2 Jan 2013, at 16:07, Steve Ebersole wrote:
> So I am also working on reverting the change to use -proc:both with a
> single compile phase. However, what we will end up with is still a
> single -proc:only phase no matter how many processors are run. They
> will output to a unified direc
I decided to hold off on this for now until GRADLE-2966[1] is resolved,
which would allow us to fold hibernate-testing into hibernate-core from
a source/project perspective but still allow us to publish
hibernate-testing as a artifact.
So I am also working on reverting the change to use -proc:b
