Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 90118 invoked from network); 8 Nov 2006 13:21:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Nov 2006 13:21:14 -0000 Received: (qmail 41864 invoked by uid 500); 8 Nov 2006 13:21:25 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 41693 invoked by uid 500); 8 Nov 2006 13:21:25 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 41682 invoked by uid 99); 8 Nov 2006 13:21:25 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2006 05:21:25 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2006 05:21:13 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 322877142FC for ; Wed, 8 Nov 2006 05:20:52 -0800 (PST) Message-ID: <12282958.1162992052189.JavaMail.jira@brutus> Date: Wed, 8 Nov 2006 05:20:52 -0800 (PST) From: "Gavin (JIRA)" To: dev@forrest.apache.org Subject: [jira] Commented: (FOR-901) Review the note on the home page about first forrest run and retrieving plugins from network In-Reply-To: <15666351.1151134709957.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/FOR-901?page=comments#action_12448133 ] Gavin commented on FOR-901: --------------------------- Tim I guess will hopefully clarify, but from what I remember the comments on the main page are still correct. I'll repeat them in the Issue so we don't have to keep going off and reminding ourselves :- "...The first time you run Forrest it will attempt to retrieve some plugins from the Internet. This will happen whenever a new plugin is specified. For more information see the plugins documentation...." Forrest will attempt to retrieve any required plugins from the internet. 1. Check if plugin already exists in build dir 2. Check descriptor file & see if local version needs updating and update it if it does. 3. Get it locally from forrest/plugins. This happens every time any build is initiated, and will obviously do so from a fresh install of forrest. Now, when forrest is first downloaded - do all the plugins come with it in the package or not, only having worked on trunk I don't know, I remember this being a question for for the new release package but the question is relevent here too I guess, if there is no internet connection when a user first goes to use a plugin then if a version exists locally from the intial download of forrest there is no problem - aside from it maybe having gone out of date. If no local version exists and no internet connection exists then a failure needs to happen with a warning message as to possible reasons why. Summary then, if the above is correct then only slight modification to the note will be neccessary. > Review the note on the home page about first forrest run and retrieving plugins from network > -------------------------------------------------------------------------------------------- > > Key: FOR-901 > URL: http://issues.apache.org/jira/browse/FOR-901 > Project: Forrest > Issue Type: Bug > Components: Documentation and website, Plugins (general issues) > Affects Versions: 0.8-dev > Reporter: David Crossley > Fix For: 0.8-dev > > > Review the note on the home page about first forrest run and retrieving plugins from network > http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&r2=365494&pathrev=365495 -- 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