Fixing module confusion (was Re: All scratchpad code migrated to FOM)

[Geoff Howard <co...@leverageweb.com>]

We discussed this reoccuring problem recently and there was a sort of 
consensus (http://marc.theaimsgroup.com/?t=105623361100002&r=1&w=2) to 
remove the link which currently exists from xml-cocoon2 to the 
"historical" cocoon module and in its place create a real module at 
xml-cocoon2 which contains only one README.txt containing an explanation 
of the real module names.

I don't think I have the karma to do this myself without intervention or 
I would have done it by now.  Does this have to go through 
infrastructure or is there someone here who can do that?

Geoff

Jacob L E Blain Christen wrote:
>>I just compiled a clean checkout with jdk1.4.1_01 on windows 2000 
>>without problems including the scratchpad. What error did you encounter? 
>>If it was with FlowVelocityGenerator, then you need to update from the 
>>latest cvs.
> 
> 
> I was compiling code originally checked out of HEAD when cocoon's
> cvs module name was "xml-cocoon" (I'd been running cvs update
> periodically) and I realized after hitting send on my email that
> perhaps I wasn't checking out the relevant module any longer.
> So, I referred to the installation howto once again: lo and behold
> it seems "cocoon-2.1" is where the "current" version of cocoon lives.
> I am checking that out now (slow connection, heh) and will let you
> know if I run into an problems (I do not forsee any).
> 
> --
> Jacob
> 
> 
> 

Re: Fixing module confusion (was Re: All scratchpad code migrated

[Upayavira <uv...@upaya.co.uk>]

On 9 Jul 2003 at 15:25, Geoff Howard wrote:

> Ok, thanks - will do.  I'll make a README.txt and send it with the
> request.

Or email Pier directly, and he can do it...

[He did offer, and said he won't be reading the list for a few weeks].

Regards, Upayavira

Re: Fixing module confusion (was Re: All scratchpad code migrated to FOM)

[Geoff Howard <co...@leverageweb.com>]

Ok, thanks - will do.  I'll make a README.txt and send it with the request.

Geoff

Vadim Gritsenko wrote:
> Geoff Howard wrote:
> 
>> We discussed this reoccuring problem recently and there was a sort of 
>> consensus (http://marc.theaimsgroup.com/?t=105623361100002&r=1&w=2) to 
>> remove the link which currently exists from xml-cocoon2 to the 
>> "historical" cocoon module and in its place create a real module at 
>> xml-cocoon2 which contains only one README.txt containing an 
>> explanation of the real module names.
>>
>> I don't think I have the karma to do this myself without intervention 
>> or I would have done it by now.  Does this have to go through 
>> infrastructure or is there someone here who can do that?
> 
> 
> 
> Only cvsadmin can do this:
> 
> drwxrwxr-x  189 root      cvsadmin    4608 Jul  2 00:58 ./
> lrwxrwxr-x  1 pier  cvsadmin  19 Feb 26 18:23 xml-cocoon2@ -> 
> cocoon-2-historical
> 
> Please send a request to the infrastructure team.
> 

Re: Fixing module confusion (was Re: All scratchpad code migrated to FOM)

[Vadim Gritsenko <va...@verizon.net>]

Geoff Howard wrote:

> We discussed this reoccuring problem recently and there was a sort of 
> consensus (http://marc.theaimsgroup.com/?t=105623361100002&r=1&w=2) to 
> remove the link which currently exists from xml-cocoon2 to the 
> "historical" cocoon module and in its place create a real module at 
> xml-cocoon2 which contains only one README.txt containing an 
> explanation of the real module names.
>
> I don't think I have the karma to do this myself without intervention 
> or I would have done it by now.  Does this have to go through 
> infrastructure or is there someone here who can do that?


Only cvsadmin can do this:

drwxrwxr-x  189 root      cvsadmin    4608 Jul  2 00:58 ./
lrwxrwxr-x  1 pier  cvsadmin  19 Feb 26 18:23 xml-cocoon2@ -> 
cocoon-2-historical

Please send a request to the infrastructure team.

Vadim