forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@apache.org>
Subject Re: [jira] Commented: (FOR-1108) Dispatcher, Cocoon 2.1 and Windows
Date Sun, 30 Nov 2008 15:04:00 GMT

On 30 Nov 2008, at 10:35, Gavin wrote:

>
>
>> -----Original Message-----
>> From: Gavin (JIRA) [mailto:jira@apache.org]
>> Sent: Sunday, 30 November 2008 8:22 PM
>> To: dev@forrest.apache.org
>> Subject: [jira] Commented: (FOR-1108) Dispatcher, Cocoon 2.1 and  
>> Windows
>>
>>
>>    [ https://issues.apache.org/jira/browse/FOR-
>> 1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
>> tabpanel&focusedCommentId=12651805#action_12651805 ]
>>
>> Gavin commented on FOR-1108:
>> ----------------------------
>>
>> Well, I got the .Text and .POD plugins working fine on Windows too,  
>> and I
>> expect if I make the same changes throughout the rest will too. I  
>> will
>> test on a couple of whiteboard plugins next.
>>
>> Previously - with a seed-sample and no dispatcher, only the PDF  
>> plugin
>> worked, with the changes below then the above two also work now.
>>
>>  <locator>
>>          <match pattern="text.transform.*.*">
>>                  <select>
>>                          <location src="resources/stylesheets/{1}-to-
>> {2}.xsl" />
>>                          <location
>> src="{forrest:forrest.plugins}/ 
>> org.apache.forrest.plugin.output.Text/resou
>> rces/stylesheets/{1}-to-{2}.xsl"/>
>>                  </select>
>>    </match>
>>  </locator>
>
> So, all I did there then was add in a second match using the more  
> full path
> to the plugins stylesheet(s) and so then it worked fine.
>
> This is a workaround, one that we could extend and test to all  
> plugins and
> if works fine can get Windows devs back to working on trunk.

Getting windows up and running is the primary goal - well done!

> Or, we need to find the real cause and fix it there, may only be a  
> few lines
> of one file rather than altering every single plugin.

We do need to figure out the real cause of the problem though. It used  
to work and now it doesn't - who knows what hidden surprises there are  
because of this.

However, since I wasn't finding the time to fix the windows problem  
myself I'm not about to start demanding you fix this. However, it's  
worth adding a fixme referring to the original issue when adding the  
workaround.

As a windows user, I'll help with what I can, but I doubt 'll be  
actively working on this (my main machines are all Linux).

Ross

Mime
View raw message