cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <ru...@apache.org>
Subject Re: Gump on cocoondev.org
Date Wed, 02 Apr 2003 00:00:45 GMT
Stefano Mazzocchi wrote:
> Sam Ruby wrote:
> 
>> Stefano Mazzocchi wrote:
>>
>>> Ah, Sam, Steven, how do I access that cocoon-special gump stuff on 
>>> cocoondev.org? that would likely reduce the try/fail cycle of 24 
>>> hours that is driving me nuts!
>>
>> Please try the instructions I left at the following URL and let me 
>> know how it goes:
>>
>> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104782633424953&w=2
> 
> Ok, I'm running into troubles but I'm not sure I'm doing the right thing.
> 
> here is what I did
> 
> 1) log into cocoondev.org

Check.

> 2) add gump and java to the path (I'm using /usr/j2sdk1.3.1, should I 
> use 1.4.1?

Everything is built with /usr/j2sdk1.4.1_02.  Cocoon may not require it, 
but some software does.  When you say you add gump to your path, are you 
referring to '/usr/serverlocal/gump/bin'?

> 3) 'build gump clean' -> success
> 4) 'build gump verify' -> success
> 5) 'build gump scripts' -> success

Can you run "which build" to see if you you are using 
/usr/serverlocal/gump/bin/build?

> if I do
> 
> 'build cocoon *'

I'm not sure why are you specifying '*'.  What you should specify is the 
Ant target you desire.  For cocoon, the target used by the build is 
"gump", so the proper command would be:

	build cocoon gump

> [as instructed] the cvs modules are not updated and the build fails.

The build command doesn't update cvs modules.  I could go into how all 
that works, but for now the best thing is for me to focus on your 
specific questions.

> So, what I would like to do is:
> 
>  - update all CVS

What do you mean by 'all'?  Do you really mean every project?  This 
process takes approximately 90 minutes.  If that's what you really want, 
the command is 'update all'.  But given that everything is freshly 
updated at midnight every night, I would suspect that what you really 
want to do is update a specific project.  The easiest way to do this 
without disturbing anything else is to cd into that project and do a cvs 
update, thus:

	cd /usr/serverlocal/gump/cocoon-2.1/
	cvs -q update
	build cocoon clean gump

>  - rebuild everything

Again, do you really mean everything?  If so, the command is 'build 
all', but that really takes a long, long time and rarely is required.

> If I try to to into /usr/serverlocal/gump and execute ./update.sh 
> nothing happens. if I do ./build.sh I get a buch of 'permission denied' 
> because I'm not into the cocoondev group.

Those are the right scripts.  Generally the build and update front ends 
found in /usr/serverlocal/gump/bin make this a bit easier to use.

Can you tell me what files you are having trouble getting access to?

> Am i doing something wrong or I simply don't have enough karma?
> 
> Please help.

I don't know if any of the above helps, but give it a try and let me 
know how it goes.  I'll watch for more cries for help.  ;-)

> Stefano.

P.S.  I'm really thrilled that you are giving this a try!



Mime
View raw message