You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2005/06/08 23:09:16 UTC

[jira] Created: (FOR-533) Auto Generate plugins.xml entry

Auto Generate plugins.xml entry
-------------------------------

         Key: FOR-533
         URL: http://issues.apache.org/jira/browse/FOR-533
     Project: Forrest
        Type: Improvement
  Components: Plugins (general issues)  
    Reporter: Ross Gardler
    Priority: Minor
     Fix For: 0.8


The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files.

All the necessary values are now in the plugin build.xml file.

This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: [jira] Commented: (FOR-533) Auto Generate plugins.xml entry

Posted by Ross Gardler <rg...@apache.org>.

David Crossley wrote:
> I did a quick comparison between the page generated today and the
> result of the previous method (i.e. the one currently at f.a.org)
> Need to cleanup ASAP so that we can keep publishing the website.

I think all your reported issues are now fixed.

I've added the published="true" property feature, so we need to ensure 
that all plugins we want to publish a this property. I'm almost certain 
I have missed one or two as I'm very tired and not double checking my work.

Can someone please review the list of published plugins.

I am aware that input.pod and output.s5 are missing, this is because the 
source files are not local. As mentioned elsewhere in the thread we need 
to add a external-plugins.xml file. I'll do that soon.

Ross

Re: [jira] Commented: (FOR-533) Auto Generate plugins.xml entry

Posted by Ross Gardler <rg...@apache.org>.

Ross Gardler wrote:
> David Crossley wrote:

...

>> Now missing some entries which were only in the */plugins/plugins.xml
>> descriptors and not present on the local filesystem.
>> input.pod
>> output.s5

Both pod and s5 are missing as we do not host the source code. I will 
therefore create an external-plugins.xml file for such plugins.

Ross

Re: [jira] Commented: (FOR-533) Auto Generate plugins.xml entry

Posted by Ross Gardler <rg...@apache.org>.

David Crossley wrote:
> I did a quick comparison between the page generated today and the
> result of the previous method (i.e. the one currently at f.a.org)
> Need to cleanup ASAP so that we can keep publishing the website.
> 
> Now missing some entries which were only in the */plugins/plugins.xml
> descriptors and not present on the local filesystem.
> input.pod
> output.s5

I now see Cyriaque meant s5 was not appearing in the index page, I 
misunderstood.

> It now lists ones that are being worked on and not yet
> committed. My fault because i was doing plugin development
> directly in the "whiteboard/plugins" directory and not in
> a private space. Committers who are publishing the website
> need to take care.

Hmmmm...

I didn't think about that, I suspect doing local work in whiteboard is 
common. How about I add a property:

published=true|false

This property will not be in the template build.xml so the plugin will 
only be published to the index page if the developer actively creates 
the published property.

> Many extras in the whiteboard section because it is now
> doing a directory listing rather than using the plugins descriptor.
> Some of these were not yet released.

Would be solved by above, but is that a "bad thing". We have deployment 
from local source files and we also have deploy and release targets.

Ross