Sorry to bother. Got fixed after purging M2 cache of hadoop. :)
Thanks
On Mon, Oct 17, 2011 at 11:48 AM, Prashant Sharma
wrote:
> Hey
> I am running into the same issue as Alejandro's . Purged ivy cache and
> recompiled. Can you give more details.
>
> On Sun, Oct 16, 2011 at 9:37 AM, Alejandro A
Hey
I am running into the same issue as Alejandro's . Purged ivy cache and
recompiled. Can you give more details.
On Sun, Oct 16, 2011 at 9:37 AM, Alejandro Abdelnur wrote:
> Arun,Hitesh,
>
> Thanks, that did it. I also had to add the following exclusion to the
> hadoop-mapreduce-project ivy.xml:
Arun,Hitesh,
Thanks, that did it. I also had to add the following exclusion to the
hadoop-mapreduce-project ivy.xml:
I'll open a JIRA for it.
Thanks.
Alejandro
On Sat, Oct 15, 2011 at 2:24 PM, Hitesh Shah wrote:
> The errors (atleast the local framework one) seem to be changes in the p
The errors (atleast the local framework one) seem to be changes in the past few
days so if you haven't tried this already, re-compiling your local source tree
if needed to install the jars locally and purging away your ivy cache before
re-trying should likely fix things.
-- Hitesh
On Oct 15,
Try blowing away your ivy cache?
Sent from my iPhone
On Oct 15, 2011, at 12:29 PM, Alejandro Abdelnur wrote:
> Running 'ant examples -Dresolvers=internal' from trunk fails with.
>
> Any ideas?
>
> Thanks.
>
> Alejandro
>
> --
> compile-mapred-classes:
> [jsp-compile] log4j:WARN No appenders
Running 'ant examples -Dresolvers=internal' from trunk fails with.
Any ideas?
Thanks.
Alejandro
--
compile-mapred-classes:
[jsp-compile] log4j:WARN No appenders could be found for logger
(org.apache.jasper.JspC).
[jsp-compile] log4j:WARN Please initialize the log4j system properly.
[jsp-com
