forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] Updated: (FOR-172) Finish off copyless behaviour
Date Thu, 01 Jan 1970 00:00:00 GMT
The following issue has been updated:

    Updater: David Crossley (mailto:crossley@apache.org)
       Date: Thu, 10 Jun 2004 8:19 AM
    Comment:
http://marc.theaimsgroup.com/?l=forrest-dev&m=108684756211324

Nicola Ken Barozzi wrote:
> Juan Jose Pablos wrote:
>
>> If we want for each project:
>> logs
>
> We should simply point to the project build dir.
>
>> upgrade skinconf
>
> This is to be done in the sitemap.
>
>> search index
>
> It should be done only when we do the static site inside the project;
> for forrest run it should be in th eproject build dir.
>
>> custom xmaps
>
> Hmmm, this is harder to tackle, it can be done but we won't be doing it
> now :-/  (*)
>
>> .... other custom stuff that I do not remember
>>
>> The quick way is to copy for each project.
>
> Quick, but not what we want :-)
>
>> With the copyless brach,
>> building forrest means to create a forrest.jar. But for each project
>> thereis stuff (like copying status.xml) that needs review.
...
>> Doing some trial and error test. It seems that as a minimum the
>> WEB-INF has to be copied (24 Files).
>>
>> But then:
>>
>> The catalog path within cocoon.xconf is relative, so it needs to point
>> to forrest.home . Same would apply to skins and resources/stylesheets.
>
> That's another point (**)
>
...
>
> I think that because of (*) and (**) we must in fact keep it for now as
> you have reverted it to.
>
> For the next version we should tackle this fully.

    Changes:
[Description] changed from [Nicola Ken Barozzi wrote:
> Juan Jose Pablos wrote:
> 
>> If we want for each project:
>> logs
> 
> We should simply point to the project build dir.
> 
>> upgrade skinconf
> 
> This is to be done in the sitemap.
> 
>> search index
> 
> It should be done only when we do the static site inside the project; 
> for forrest run it should be in th eproject build dir.
> 
>> custom xmaps
> 
> Hmmm, this is harder to tackle, it can be done but we won't be doing it 
> now :-/  (*)
> 
>> .... other custom stuff that I do not remember
>>
>> The quick way is to copy for each project. 
> 
> Quick, but not what we want :-)
> 
> With the copyless brach,
> 
>> building forrest means to create a forrest.jar. But for each project 
>> thereis stuff (like copying status.xml) that needs review.
...
>> Doing some trial and error test. It seems that as a minimum the 
>> WEB-INF has to be copied (24 Files).
>>
>> But then:
>>
>> The catalog path within cocoon.xconf is relative, so it needs to point 
>> to forrest.home . Same would apply to skins and resources/stylesheets.
> 
> That's another point (**)
> 
...
> 
> I think that because of (*) and (**) we must in fact keep it for now as 
> you have reverted it to.
> 
> For the next version we should tackle this fully.] to [The "true" copyless behaviour
is not quite fully implemented.]

---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-172&page=history

---------------------------------------------------------------------
View the issue:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-172


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-172
    Summary: Finish off copyless behaviour
       Type: Improvement

     Status: Unassigned
   Priority: Critical

    Project: Forrest
  Component: Core operations
    Fix For: 0.7
   Versions:
             0.6

   Assignee: 
   Reporter: Nicola Ken Barozzi

    Created: Thu, 10 Jun 2004 8:11 AM
    Updated: Thu, 10 Jun 2004 8:19 AM

Description:
The "true" copyless behaviour is not quite fully implemented.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org/jira//Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message