On 28/08/05, Brett Porter <[EMAIL PROTECTED]> wrote: > You can use --check-plugin-latest (I thought this was the default...)
This doesn't seem to make any difference. I'm not sure how the bootstrap process of installing the plugins differs from a manual m2 install within a plugin dir, but the latter never creates the RELEASE.version.txt file. You can easily replicate the problem by deleting a plugin from your local repo and manually installing it again. Subsequent uses of the plugin will then not use the locally installed version, but will attempt to be auto-discovered (e.g. deleting and reinstalling the site 2.0-beta-1-SNAPSHOT plugin will then download and use site 2.0-alpha-3 plugin when invoked). This doesn't seem to be the intended behaviour? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
