Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
From: Bill Havanki <bhavanki@clouderagovt.com>
Date: Mon, 5 May 2014 19:53:58 -0400
Message-ID: 
 <CAD-fFUJQRj6RrdqAgo5ovncErDOE0sJh-chnCOe3CNDQe7k6BQ@mail.gmail.com>
Subject: Maven incremental compilation issue
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2ef6e80590f04f8afd974

--001a11c2ef6e80590f04f8afd974
Content-Type: text/plain; charset=UTF-8

I've noticed lately that my builds of at least the core module always
compile all the hundreds of classes in core, even if I didn't make any
edits. I seem to have been encountering this problem:

http://stackoverflow.com/questions/17944108/maven-compiler-plugin-always-detecting-a-set-of-sources-as-stale

The Apache parent POM (version 14) mandates version 3.1 of the compiler
plugin, which is affected. I found when I tried the workaround of setting
useIncrementalCompilation to false that the problem was avoided.

If anyone else sees this, maybe the workaround will help. A good way is
including -Dmaven.compiler.useIncrementalCompilation=false to MAVEN_OPTS.

-- 
// Bill Havanki
// Solutions Architect, Cloudera Govt Solutions
// 443.686.9283

--001a11c2ef6e80590f04f8afd974--