Hi Thomas,
Apparently, I failed a couple of times to make myself clear and did not run
my tests thoroughly enough.
1. Yes, you're right, from the command line, only javac 1.8 displays the
error message. Javac 1.7 does not display anything (being OpenJDK's or
Oracle's).
2. No, I have never seen a
On Mon Feb 23 2015 at 09:53:24 Sébastien Lesaint <
sebastien.lesa...@gmail.com> wrote:
> Hello,
>
> Thanks Thomas for your extensive answer. But you seemed to focus only on
> the first problem (which I had identified as potentially _not_ a bug).
>
> What about the fact that m-compiler-p ignores th
Hello,
Thanks Thomas for your extensive answer. But you seemed to focus only on
the first problem (which I had identified as potentially _not_ a bug).
What about the fact that m-compiler-p ignores the error returned by Javac
and allows the build to continue ?
Right now, I have a successful build
On Fri Feb 20 2015 at 21:11:14 Sébastien Lesaint <
sebastien.lesa...@gmail.com> wrote:
> Hello,
>
> I have been into annotation processing a lot for the past year and a half
> and I am now going back to the basics so that I can share knowledge I
> gathered.
>
> Doing so, I stumbled upon, again, a
On Sat Feb 21 2015 at 10:12:23 Jeff MAURY wrote:
> Sure this is not a Javac problem ?
>
No it's not.
target/classes contains the
META-INF/services/javax.annotation.processing.Processor and it's put in the
classpath, and because there's no support for processorpath [1], javac
looks up annotation
Sure this is not a Javac problem ?
Jeff
On Fri, Feb 20, 2015 at 9:09 PM, Sébastien Lesaint <
sebastien.lesa...@gmail.com> wrote:
> Hello,
>
> I have been into annotation processing a lot for the past year and a half
> and I am now going back to the basics so that I can share knowledge I
> gather
