[infinispan-dev] Issue posted for JBoss Logging and slf4j
Jeff Ramsdale
jeff.ramsdale at gmail.com
Mon Jun 20 18:38:58 EDT 2011
Hi Dan,
I didn't see any failures building with 2.2.1 but the jar seemed to
behave differently. In retrospect it's possible Eclipse was resolving
against a local project without APT running instead of against the
published artifact that contained the class. Wish I had more data, but
ultimately I'd rather use the published jars than my own anyway. Once
the blocking ISPN-1148 was resolved and new jar released I was able to
move back to the published artifacts.
Thanks for the feedback!
-jeff
On Mon, Jun 20, 2011 at 3:07 PM, Dan Berindei <dan.berindei at gmail.com> wrote:
> Hi Jeff
>
> I'm building Infinispan with Maven 2.2.1 on Fedora 14 and it works fine.
> I haven't noticed ISPN-1177 before, but I do get the error from time
> to time when I build from IntelliJ, because the IntelliJ compiler
> doesn't do annotation processing (or at least I haven't been able to
> configure it properly).
> Then when you run 'mvn install' maven sees that the class is up to
> date and doesn't run annotation processing either. Running 'mvn clean
> install' usually sorts everything out.
>
> Dan
>
More information about the infinispan-dev
mailing list