You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Jos Backus <jo...@catnook.com> on 2012/04/05 02:20:03 UTC

`make rpms' dies during oozie-docs build

Hi,

My `make rpms' on trunk at '229e9f5 BIGTOP-513-Pig Packaging Cleanup'
is failing, any idea what the problem could be? Does this have
anything to do with the Doxia merge?

[INFO] Reactor Summary:
[INFO]
[INFO] Oozie Main ........................................ SUCCESS [15.654s]
[INFO] Oozie Client ...................................... SUCCESS [1:41.654s]
[INFO] Oozie Share Lib ................................... SUCCESS [56.589s]
[INFO] Oozie Core ........................................ SUCCESS [1:53.648s]
[INFO] Oozie Docs ........................................ FAILURE [19.910s]
[INFO] Oozie WebApp ...................................... SKIPPED
[INFO] Oozie Examples .................................... SKIPPED
[INFO] Oozie Distro ...................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5:16.762s
[INFO] Finished at: Wed Apr 04 16:55:09 PDT 2012
[INFO] Final Memory: 43M/113M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site (default)
on project oozie-docs: Execution default of goal
org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site failed:
Plugin org.apache.maven.plugins:maven-site-plugin:2.0-beta-6 or one of
its dependencies could not be resolved: The following artifacts could
not be resolved:
org.apache.maven.doxia:doxia-module-twiki:jar:1.0-alpha-9.2y,
org.apache.maven.doxia:doxia-core:jar:1.0-alpha-9.2y: Could not find
artifact org.apache.maven.doxia:doxia-module-twiki:jar:1.0-alpha-9.2y
in internal.maven.repo (file:///tmp/internalmavenrepo) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :oozie-docs

Thanks for any suggestions!

Cheers,
Jos
-- 
Jos Backus
jos at catnook.com

Re: Need help with git diff

Posted by Victor Chugunov <vi...@yahoo.com>.
Nice idea, but we need a presenter 
Victor



________________________________
From: Doug Chang <do...@stanfordalumni.org>
To: bigtop-dev@incubator.apache.org
Sent: Mon, April 9, 2012 11:19:26 AM
Subject: Re: Need help with git diff

hey victor why we dont cover this on sat??, others must have questions
also....but are too afraid to ask...

dc

On Mon, Apr 9, 2012 at 8:57 AM, Konstantin Boudnik <co...@apache.org> wrote:

> Victor,
>
> I'd suggest to consider this http://gitready.com/ if you're new to git.
>
> Cos
>
> On Mon, Apr 09, 2012 at 12:44AM, Victor Chugunov wrote:
> > Roman,
> > can you please tell the steps to do a git diff on the new files
> > I tried git add <filename>, git add -N <filename> and after git diff
> <filename>
> > and nothing was working
> > after doing git stash I've lost all my changes
> >
> > Victor
>

Re: Need help with git diff

Posted by Doug Chang <do...@stanfordalumni.org>.
hey victor why we dont cover this on sat??, others must have questions
also....but are too afraid to ask...

dc

On Mon, Apr 9, 2012 at 8:57 AM, Konstantin Boudnik <co...@apache.org> wrote:

> Victor,
>
> I'd suggest to consider this http://gitready.com/ if you're new to git.
>
> Cos
>
> On Mon, Apr 09, 2012 at 12:44AM, Victor Chugunov wrote:
> > Roman,
> > can you please tell the steps to do a git diff on the new files
> > I tried git add <filename>, git add -N <filename> and after git diff
> <filename>
> > and nothing was working
> > after doing git stash I've lost all my changes
> >
> > Victor
>

Re: Need help with git diff

Posted by Konstantin Boudnik <co...@apache.org>.
Victor,

I'd suggest to consider this http://gitready.com/ if you're new to git.

Cos

On Mon, Apr 09, 2012 at 12:44AM, Victor Chugunov wrote:
> Roman,
> can you please tell the steps to do a git diff on the new files
> I tried git add <filename>, git add -N <filename> and after git diff <filename> 
> and nothing was working
> after doing git stash I've lost all my changes
> 
> Victor

Re: Need help with git diff

Posted by Lei Zou <le...@gmail.com>.
Hi Victor,


I think you can do the following steps:

cd ~/bigtop

## let's say you like to add a new file Lei.txt

# do diff, there is no difference
:bigtop lei$ git diff

# create a dummy new file
:bigtop lei$ echo "Lei Zou" > Lei.txt

:bigtop lei$ git diff

# add the file to local repository
:bigtop lei$ git add -N Lei.txt

# do the diff and find out the difference
:bigtop lei$ git diff
diff --git a/Lei.txt b/Lei.txt
index e69de29..53503b0 100644
--- a/Lei.txt
+++ b/Lei.txt
@@ -0,0 +1 @@
+Lei Zou
:bigtop lei$


I hope it helps.

Lei Zou

On Mon, Apr 9, 2012 at 12:44 AM, Victor Chugunov <vi...@yahoo.com> wrote:

> Roman,
> can you please tell the steps to do a git diff on the new files
> I tried git add <filename>, git add -N <filename> and after git diff
> <filename>
> and nothing was working
> after doing git stash I've lost all my changes
>
> Victor

Re: Need help with git diff

Posted by Harsh J <ha...@cloudera.com>.
The best way to diff would be to do so against last known HEAD:

$ git diff HEAD

This will include "git add"-ed files.

If you have done "git stash" then the changes are stashed away. Simply
do "git stash pop", and your stashed changes will get reapplied.

Hope this helps!

On Mon, Apr 9, 2012 at 1:14 PM, Victor Chugunov <vi...@yahoo.com> wrote:
> Roman,
> can you please tell the steps to do a git diff on the new files
> I tried git add <filename>, git add -N <filename> and after git diff <filename>
> and nothing was working
> after doing git stash I've lost all my changes
>
> Victor



-- 
Harsh J

Need help with git diff

Posted by Victor Chugunov <vi...@yahoo.com>.
Roman,
can you please tell the steps to do a git diff on the new files
I tried git add <filename>, git add -N <filename> and after git diff <filename> 
and nothing was working
after doing git stash I've lost all my changes

Victor

Re: `make rpms' dies during oozie-docs build

Posted by Roman Shaposhnik <rv...@apache.org>.
+Oozie dev

On Fri, Apr 6, 2012 at 1:04 PM, Jos Backus <jo...@catnook.com> wrote:
> On Thu, Apr 5, 2012 at 2:50 PM, Roman Shaposhnik <rv...@apache.org> wrote:
>> On Wed, Apr 4, 2012 at 5:20 PM, Jos Backus <jo...@catnook.com> wrote:
>>> Hi,
>>>
>>> My `make rpms' on trunk at '229e9f5 BIGTOP-513-Pig Packaging Cleanup'
>>> is failing, any idea what the problem could be? Does this have
>>> anything to do with the Doxia merge?
>>
>> This is weird. I've just kicked a full Oozie build on our Jenkins:
>>    http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Oozie/19/
>>
>> and it ran without any issues. You're welcome to inspect the logs, but beyond
>> that I'm not sure I can help much.
>
> Mayank, Benoy and I did some digging. The issue is that doc/pom.xml in
> oozie-3.1.3 refers to some Yahoo! artifacts (doxia-core and
> doxia-module-twiki, both version 1.0-alpha-9.2y) but the repository in
> pom.xml (http://yahoo.github.com/maven/repository) no longer exists. I
> have downloaded the jars and installed them on the build machine in
> ~/.m2 which fixed the issue. My guess is your build works because
> ~/.m2 cached the jars or you have them in a local repo.

This seems like a big deal actually.

Oozie dev, do you guys have any plans to fix this in 3.2 ?

Thanks,
Roman.

Re: `make rpms' dies during oozie-docs build

Posted by Doug Chang <do...@stanfordalumni.org>.
this issue also exists in make deb...

On Fri, Apr 6, 2012 at 1:04 PM, Jos Backus <jo...@catnook.com> wrote:

> Hi Roman,
>
> Thanks for responding!
>
> On Thu, Apr 5, 2012 at 2:50 PM, Roman Shaposhnik <rv...@apache.org> wrote:
> > On Wed, Apr 4, 2012 at 5:20 PM, Jos Backus <jo...@catnook.com> wrote:
> >> Hi,
> >>
> >> My `make rpms' on trunk at '229e9f5 BIGTOP-513-Pig Packaging Cleanup'
> >> is failing, any idea what the problem could be? Does this have
> >> anything to do with the Doxia merge?
> >
> > This is weird. I've just kicked a full Oozie build on our Jenkins:
> >
> http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Oozie/19/
> >
> > and it ran without any issues. You're welcome to inspect the logs, but
> beyond
> > that I'm not sure I can help much.
>
> Mayank, Benoy and I did some digging. The issue is that doc/pom.xml in
> oozie-3.1.3 refers to some Yahoo! artifacts (doxia-core and
> doxia-module-twiki, both version 1.0-alpha-9.2y) but the repository in
> pom.xml (http://yahoo.github.com/maven/repository) no longer exists. I
> have downloaded the jars and installed them on the build machine in
> ~/.m2 which fixed the issue. My guess is your build works because
> ~/.m2 cached the jars or you have them in a local repo.
>
> Thanks!
>
> Jos
> --
> Jos Backus
> jos at catnook.com
>

Re: `make rpms' dies during oozie-docs build

Posted by Roman Shaposhnik <rv...@apache.org>.
+Oozie dev

On Fri, Apr 6, 2012 at 1:04 PM, Jos Backus <jo...@catnook.com> wrote:
> On Thu, Apr 5, 2012 at 2:50 PM, Roman Shaposhnik <rv...@apache.org> wrote:
>> On Wed, Apr 4, 2012 at 5:20 PM, Jos Backus <jo...@catnook.com> wrote:
>>> Hi,
>>>
>>> My `make rpms' on trunk at '229e9f5 BIGTOP-513-Pig Packaging Cleanup'
>>> is failing, any idea what the problem could be? Does this have
>>> anything to do with the Doxia merge?
>>
>> This is weird. I've just kicked a full Oozie build on our Jenkins:
>>    http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Oozie/19/
>>
>> and it ran without any issues. You're welcome to inspect the logs, but beyond
>> that I'm not sure I can help much.
>
> Mayank, Benoy and I did some digging. The issue is that doc/pom.xml in
> oozie-3.1.3 refers to some Yahoo! artifacts (doxia-core and
> doxia-module-twiki, both version 1.0-alpha-9.2y) but the repository in
> pom.xml (http://yahoo.github.com/maven/repository) no longer exists. I
> have downloaded the jars and installed them on the build machine in
> ~/.m2 which fixed the issue. My guess is your build works because
> ~/.m2 cached the jars or you have them in a local repo.

This seems like a big deal actually.

Oozie dev, do you guys have any plans to fix this in 3.2 ?

Thanks,
Roman.

Re: `make rpms' dies during oozie-docs build

Posted by Jos Backus <jo...@catnook.com>.
Hi Roman,

Thanks for responding!

On Thu, Apr 5, 2012 at 2:50 PM, Roman Shaposhnik <rv...@apache.org> wrote:
> On Wed, Apr 4, 2012 at 5:20 PM, Jos Backus <jo...@catnook.com> wrote:
>> Hi,
>>
>> My `make rpms' on trunk at '229e9f5 BIGTOP-513-Pig Packaging Cleanup'
>> is failing, any idea what the problem could be? Does this have
>> anything to do with the Doxia merge?
>
> This is weird. I've just kicked a full Oozie build on our Jenkins:
>    http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Oozie/19/
>
> and it ran without any issues. You're welcome to inspect the logs, but beyond
> that I'm not sure I can help much.

Mayank, Benoy and I did some digging. The issue is that doc/pom.xml in
oozie-3.1.3 refers to some Yahoo! artifacts (doxia-core and
doxia-module-twiki, both version 1.0-alpha-9.2y) but the repository in
pom.xml (http://yahoo.github.com/maven/repository) no longer exists. I
have downloaded the jars and installed them on the build machine in
~/.m2 which fixed the issue. My guess is your build works because
~/.m2 cached the jars or you have them in a local repo.

Thanks!

Jos
-- 
Jos Backus
jos at catnook.com

Re: `make rpms' dies during oozie-docs build

Posted by Roman Shaposhnik <rv...@apache.org>.
On Wed, Apr 4, 2012 at 5:20 PM, Jos Backus <jo...@catnook.com> wrote:
> Hi,
>
> My `make rpms' on trunk at '229e9f5 BIGTOP-513-Pig Packaging Cleanup'
> is failing, any idea what the problem could be? Does this have
> anything to do with the Doxia merge?

This is weird. I've just kicked a full Oozie build on our Jenkins:
    http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Oozie/19/

and it ran without any issues. You're welcome to inspect the logs, but beyond
that I'm not sure I can help much.

Thanks,
Roman.