Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of tucu@cloudera.com designates
 209.85.160.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2CD1AF50B2764556B00E9DD749C708F9@china.huawei.com>
References: <2CD1AF50B2764556B00E9DD749C708F9@china.huawei.com>
From: Alejandro Abdelnur <tucu@cloudera.com>
Date: Tue, 20 Sep 2011 06:35:22 -0700
Message-ID: 
 <CAJs-t7MtX+yXN12Fc-8iP_J_96EUeKZbesqred2+XEZY2NpvdA@mail.gmail.com>
Subject: Re: Maven eclipse plugin issue
To: common-dev@hadoop.apache.org, lakshman_ch@huawei.com
Content-Type: multipart/alternative; boundary=20cf3079ba50cab91f04ad5f898f

--20cf3079ba50cab91f04ad5f898f
Content-Type: text/plain; charset=ISO-8859-1

Laxman,

This is not an incorrect usage of maven phases, those generated Java classes
are test classes, thus is generation in the 'generate-test-sources' phase.

The problem seem to be that eclipse does not recognize the
target/generated-test-source/java directory as a source directory (for
example, IntelliJ does).

One thing we could try (not 100% correct but it would simplify the life of
eclipse developers) is -as you suggest- to change the phase to
'generate-sources'. But the generated sources and corresponding compiled
classes there must be compiled and used for testing, the classes should end
up in the target/test-classes directory.

If the above is doable it should a nice workaround.

Please open a JIRA to follow up with this. Note that is not only in common
that code is generated, but in mapreduce as well. And there are different
things being generated, avro, protobuf, etc.

Thanks.

Alejandro

On Tue, Sep 20, 2011 at 2:41 AM, Laxman <lakshman_ch@huawei.com> wrote:

> Hi All,
>
>
>
> I can see lot of compilation issues after setting up my development
> environment using "mvn eclipse:eclipse".
>
> All these compilation issues are resolved after adding
> "target/generated-test-sources" as a source folder to the common project.
>
>
>
> When verified the "pom.xml", it's noticed that these are included under
> "generate-test-sources" phase.
>
> This seems to be a problem occurred because of incorrect
> understanding/usage
> of "build-helper-maven-plugin" in Common project.
>
>
>
> All these compilation issues are resolved after changing the phase to
> "generate-sources".
>
>
>
> Please correct me if my understanding is wrong.
>
>
>
> I found similar issue here.
>
> https://issues.sonatype.org/browse/MNGECLIPSE-2387
>
> --
>
> Thanks,
>
> Laxman
>
>

--20cf3079ba50cab91f04ad5f898f--