Yes, the Eclipse contrib is skipped unless eclipse.home is set.
See: src/contrib/eclipse-plugin/build.xml lines 47-50
<!-- Skip building if eclipse.home is unset. -->
<target name="check-contrib" unless="eclipse.home">
<property name="skip.contrib" value="yes"/>
<echo message="eclipse.home unset: skipping eclipse plugin"/>
</target>
When this happens you should be able to see the string "skipping eclipse
plugin" in the console output.
However, turning on Eclipse build without any changes will result in a build
failure on branch-0.20-security as well as in release-0.20.203.0-rc0.
We resolved this on a similar internal branch by applying
"alex-HADOOP-3744.patch" as attached in MAPREDUCE-1280.
This leads me to two questions:
1) How would I indicate that this Jira should be applied to this branch? Open a
new jira? Re-open the existing jira and adding affects/fix versions?
2) How does one typically indicate which of the several patches is actually the
one to be applied?
Owen has already applied at least one of these.
I'll try to reconcile the other patches we have applied to our internal branch
and follow the recommended process for these to suggest them for the 203
release.
Thanks,
Joep
-----Original Message-----
From: Nigel Daley [mailto:nda...@mac.com]
Sent: Tuesday, May 03, 2011 2:17 PM
To: common-dev@hadoop.apache.org
Subject: Re: [VOTE] Release candidate 0.20.203.0-rc0
On May 3, 2011, at 1:48 PM, Owen O'Malley wrote:
>
> On May 3, 2011, at 1:33 PM, Nigel Daley wrote:
>
>> Owen, any reason you're not building the eclipse plugin for this release?
>> Instructions are here: http://wiki.apache.org/hadoop/HowToRelease
>
> Of course, I know (and have updated) the HowToRelease page. It looks like
> the eclipse-plugin was dropped off of the list of contrib modules to build by
> default.
I believe it's only built if you have -Declipse.home= defined.
Cheers,
n.
