forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian M Dube <bd...@apache.org>
Subject Re: local-deploy on project-internal plugin
Date Tue, 24 Mar 2009 02:04:13 GMT
On Mon, Mar 23, 2009 at 10:23:13PM +0200, Sjur Moshagen wrote:
> Replying to myself:
>
> Den 23. mar. 2009 kl. 14.59 skrev Sjur Moshagen:
>
>> The action on line 117 in that build file reads:
>>
>>    <copy toDir="${forrest.plugins.localDeploy.dir}/${plugin-name}">
>>      <fileset dir="${forrest.plugins.dir}/${plugin-name}">
>>        <exclude name="lib/**"/>
>>        <exclude name="build/**"/>
>>      </fileset>
>>    </copy>
>
> If I change this to the following:
>
>     <copy toDir="${forrest.plugins.localDeploy.dir}/${plugin-name}">
>       <fileset dir="${forrest.plugins.dir}">
>         <exclude name="lib/**"/>
>         <exclude name="build/**"/>
>       </fileset>
>     </copy>
>
> it works ok (cf the second line, where I removed the ${plugin-name}  
> variable). But this would probably break the regular plugin deployment. 
> This file has not been touched since end of April 2007, and bugs here 
> would certainly have been found much earlier.
>
> Thus it seems to me that there is inconsisten behaviour between local- 
> deploy of regular plugins (and whiteboard ones) and project plugins.
>
> Can anynoe confirm this? Or am I on the wrong track?

The times I have tried to develop plugins out of tree, I've also run
into problems. I don't recall whether it was this same problem or
something else, but this sounds familiar. If I end up with extra
cycles, I'll help look into it.

Brian

Mime
View raw message