forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Closed: (FOR-372) publish plugins dist files to svn
Date Fri, 19 Nov 2004 20:06:50 GMT

   The following issue has been closed.

   Resolver: Ross Gardler
       Date: Fri, 19 Nov 2004 2:05 PM

Do "ant deploy" in the plugin directory and the plugins.xml and plugin zip file will be committed
to the site in SVN. This will then be made public by the normal site update scripts within
12 hours.
View the issue:

Here is an overview of the issue:
        Key: FOR-372
    Summary: publish plugins dist files to svn
       Type: Improvement

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Forrest
             Plugins (general issues)
   Fix Fors:

   Assignee: Ross Gardler
   Reporter: Ross Gardler

    Created: Mon, 15 Nov 2004 6:23 PM
    Updated: Fri, 19 Nov 2004 2:05 PM

Dave Brondsema wrote:
> Ross Gardler wrote:
>> Juan Jose Pablos wrote:
>>> Hi,
>>> Why do we need to have:
>>> A  site-author/content/plugins
>>> A  site-author/content/plugins/plugins.xml
>>> A  site-author/content/plugins/
>>> A  site-author/content/plugins/
>>> A  site-author/content/plugins/
>>> A  site-author/content/plugins/
>> These are the distribution files of released plugins that must be 
>> accessible on the website.
> This isn't necessary, it's just an extra step before they go to 
> anyway.

You mean we should publish directly to the website? That makes sense, I agree.


> I think we should have an ant script which builds a plugin, and then 
> publishes it to the appropriate place in svn: ../asf/forrest/site/plugins.
> See forrestbot's deploy.xml for a way to use ant to commit to SVN.

There is the start of an ant script in the plugins directory. At the moment it builds the
distribution and places it in site-author.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message