Hey gang,

I'm running mvn clean install from the hadoop-mapreduce directory on
an  svn co of trunk (hadoop-common) and get the following:

[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2:exec (generate-sources) on
project hadoop-yarn-api: Command execution failed. Process exited with
an error: 1(Exit value: 1) -> [Help 1]

I'm using mvn version 3.0.3.

Thanks,
Eli

Eli,
 I think its protoc. Do you have protoc installed?

mahadev

On Thu, Aug 18, 2011 at 10:28 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
> Hey gang,
>
> I'm running mvn clean install from the hadoop-mapreduce directory on
> an  svn co of trunk (hadoop-common) and get the following:
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2:exec (generate-sources) on
> project hadoop-yarn-api: Command execution failed. Process exited with
> an error: 1(Exit value: 1) -> [Help 1]
>
> I'm using mvn version 3.0.3.
>
> Thanks,
> Eli
>

Yea, I got same issue - went away when I added protoc 2.4.0a on the path.

(As discussed at the contributor meetup earlier this summer, I think
it would be better to check in the protoc-generated code)

Todd

On Thu, Aug 18, 2011 at 10:29 AM, Mahadev Konar <[EMAIL PROTECTED]> wrote:
> Eli,
>  I think its protoc. Do you have protoc installed?
>
> mahadev
>
> On Thu, Aug 18, 2011 at 10:28 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
>> Hey gang,
>>
>> I'm running mvn clean install from the hadoop-mapreduce directory on
>> an  svn co of trunk (hadoop-common) and get the following:
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2:exec (generate-sources) on
>> project hadoop-yarn-api: Command execution failed. Process exited with
>> an error: 1(Exit value: 1) -> [Help 1]
>>
>> I'm using mvn version 3.0.3.
>>
>> Thanks,
>> Eli
>>
>

--
Todd Lipcon
Software Engineer, Cloudera

>(As discussed at the contributor meetup earlier this summer, I think
>it would be better to check in the protoc-generated code)

+1

- milind

---
Milind Bhandarkar
Greenplum Labs, EMC
(Disclaimer: Opinions expressed in this email are those of the author, and
do not necessarily represent the views of any organization, past or
present, the author might be affiliated with.)

On Thu, Aug 18, 2011 at 10:29 AM, Mahadev Konar <[EMAIL PROTECTED]> wrote:
> Eli,
>  I think its protoc. Do you have protoc installed?
>

Installing protoc (and adding /usr/local/lib to my ld lib path) got it
working.  If we don't check in the generated sources please update the
HowToContribute wiki with this dep (or make the build error nicer),
otherwise we'll get lots of queries on the list.

Thanks,
Eli
> mahadev
>
> On Thu, Aug 18, 2011 at 10:28 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
>> Hey gang,
>>
>> I'm running mvn clean install from the hadoop-mapreduce directory on
>> an  svn co of trunk (hadoop-common) and get the following:
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2:exec (generate-sources) on
>> project hadoop-yarn-api: Command execution failed. Process exited with
>> an error: 1(Exit value: 1) -> [Help 1]
>>
>> I'm using mvn version 3.0.3.
>>
>> Thanks,
>> Eli
>>
>

IMO, committing generated code is not a good idea. I'd rather put the burden
on developers of installing protoc  (they have to do it for Java, Maven,
Forrest, and all the autoconf stuff if compiling native).

I would document protoc as required tool.

Thxs.

Alejandro

On Thu, Aug 18, 2011 at 10:50 AM, Eli Collins <[EMAIL PROTECTED]> wrote:

> On Thu, Aug 18, 2011 at 10:29 AM, Mahadev Konar <[EMAIL PROTECTED]>
> wrote:
> > Eli,
> >  I think its protoc. Do you have protoc installed?
> >
>
> Installing protoc (and adding /usr/local/lib to my ld lib path) got it
> working.  If we don't check in the generated sources please update the
> HowToContribute wiki with this dep (or make the build error nicer),
> otherwise we'll get lots of queries on the list.
>
> Thanks,
> Eli
>
>
> > mahadev
> >
> > On Thu, Aug 18, 2011 at 10:28 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
> >> Hey gang,
> >>
> >> I'm running mvn clean install from the hadoop-mapreduce directory on
> >> an  svn co of trunk (hadoop-common) and get the following:
> >>
> >> [ERROR] Failed to execute goal
> >> org.codehaus.mojo:exec-maven-plugin:1.2:exec (generate-sources) on
> >> project hadoop-yarn-api: Command execution failed. Process exited with
> >> an error: 1(Exit value: 1) -> [Help 1]
> >>
> >> I'm using mvn version 3.0.3.
> >>
> >> Thanks,
> >> Eli
> >>
> >
>

On Thu, Aug 18, 2011 at 11:39 AM, Alejandro Abdelnur <[EMAIL PROTECTED]> wrote:
> IMO, committing generated code is not a good idea. I'd rather put the burden
> on developers of installing protoc  (they have to do it for Java, Maven,
> Forrest, and all the autoconf stuff if compiling native).
>
> I would document protoc as required tool.
>

Alejandro - is there an easy way we can make maven spit out a nicer
error message (eg check for protoc on the path and print a message if
it's not present)?

(Thank you Mahadev btw for pointing out the fix!)

Thanks,
Eli

protoc is invoked from an antrun plugin configuration.

we could check using ant tasks that protoc is avail, and fail with a message
if not.

Thxs.

Alejandro

On Thu, Aug 18, 2011 at 11:44 AM, Eli Collins <[EMAIL PROTECTED]> wrote:

> On Thu, Aug 18, 2011 at 11:39 AM, Alejandro Abdelnur <[EMAIL PROTECTED]>
> wrote:
> > IMO, committing generated code is not a good idea. I'd rather put the
> burden
> > on developers of installing protoc  (they have to do it for Java, Maven,
> > Forrest, and all the autoconf stuff if compiling native).
> >
> > I would document protoc as required tool.
> >
>
> Alejandro - is there an easy way we can make maven spit out a nicer
> error message (eg check for protoc on the path and print a message if
> it's not present)?
>
> (Thank you Mahadev btw for pointing out the fix!)
>
> Thanks,
> Eli
>

Updated http://wiki.apache.org/hadoop/DevelopingOnTrunkAfter279Merge
and filed MAPREDUCE-2901.

+Vinod

On Fri, Aug 19, 2011 at 12:22 AM, Alejandro Abdelnur <[EMAIL PROTECTED]>wrote:

> protoc is invoked from an antrun plugin configuration.
>
> we could check using ant tasks that protoc is avail, and fail with a
> message
> if not.
>
> Thxs.
>
> Alejandro
>
> On Thu, Aug 18, 2011 at 11:44 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Aug 18, 2011 at 11:39 AM, Alejandro Abdelnur <[EMAIL PROTECTED]>
> > wrote:
> > > IMO, committing generated code is not a good idea. I'd rather put the
> > burden
> > > on developers of installing protoc  (they have to do it for Java,
> Maven,
> > > Forrest, and all the autoconf stuff if compiling native).
> > >
> > > I would document protoc as required tool.
> > >
> >
> > Alejandro - is there an easy way we can make maven spit out a nicer
> > error message (eg check for protoc on the path and print a message if
> > it's not present)?
> >
> > (Thank you Mahadev btw for pointing out the fix!)
> >
> > Thanks,
> > Eli
> >
>

Thanks Vinod!

On Aug 29, 2011, at 12:30 AM, Vinod Kumar Vavilapalli wrote:

> Updated http://wiki.apache.org/hadoop/DevelopingOnTrunkAfter279Merge
> and filed MAPREDUCE-2901.
>
> +Vinod
>
> On Fri, Aug 19, 2011 at 12:22 AM, Alejandro Abdelnur <[EMAIL PROTECTED]>wrote:
>
>> protoc is invoked from an antrun plugin configuration.
>>
>> we could check using ant tasks that protoc is avail, and fail with a
>> message
>> if not.
>>
>> Thxs.
>>
>> Alejandro
>>
>> On Thu, Aug 18, 2011 at 11:44 AM, Eli Collins <[EMAIL PROTECTED]> wrote:
>>
>>> On Thu, Aug 18, 2011 at 11:39 AM, Alejandro Abdelnur <[EMAIL PROTECTED]>
>>> wrote:
>>>> IMO, committing generated code is not a good idea. I'd rather put the
>>> burden
>>>> on developers of installing protoc  (they have to do it for Java,
>> Maven,
>>>> Forrest, and all the autoconf stuff if compiling native).
>>>>
>>>> I would document protoc as required tool.
>>>>
>>>
>>> Alejandro - is there an easy way we can make maven spit out a nicer
>>> error message (eg check for protoc on the path and print a message if
>>> it's not present)?
>>>
>>> (Thank you Mahadev btw for pointing out the fix!)
>>>
>>> Thanks,
>>> Eli
>>>
>>