|
| Re: caching on site update [message #290726 is a reply to message #290724] |
Tue, 30 August 2005 21:45   |
Eclipse User |
|
|
|
Originally posted by: dorian.birsan.net
This could be related to your versioning scheme:
By default, update is for equivalent versions, ie 1.2.x to 1.2.y.
You can enable for compatible, 1.x.y to 1.z.w from the preference page.
-dorian
"Neil Goldsmith" <neilg@avaya.com> wrote in message
news:df2ij6$198$1@news.eclipse.org...
> Is there any sort of caching going on with site update? I updated some of
> my plugins by first finding a new remote site. In the process of the new
> changes, the new version of the feature.xml embeds the URL to the update
> site. I closed down Eclipse and created a few new plugin/feature
versions,
> built them and ftp'ed back to the site. Then went back and opened up
> Eclipse and looked for changes to an existing feature. It came back with
no
> changes. Looking at the site.xml and feature.xml as well as the plug that
> changes, there are definitely new changes, but the site update doesn't
think
> so. I can't find any mistakes to the site update and my current Eclipse
> doesn't have the new changes, any ideas why Eclipse thinks it is up to
date?
>
>
|
|
|
| Re: caching on site update [message #290727 is a reply to message #290726] |
Tue, 30 August 2005 21:59 |
 Neil Goldsmith
Messages: 68
Registered: July 2009 |
Member |
|
|
No, my feature goes from 3.0.16 -> 3.0.17 The plugins have a similar
numbering.
"dorian birsan" <dorian@birsan.net> wrote in message
news:df2k1l$30p$1@news.eclipse.org...
> This could be related to your versioning scheme:
> By default, update is for equivalent versions, ie 1.2.x to 1.2.y.
> You can enable for compatible, 1.x.y to 1.z.w from the preference page.
>
> -dorian
>
> "Neil Goldsmith" <neilg@avaya.com> wrote in message
> news:df2ij6$198$1@news.eclipse.org...
>> Is there any sort of caching going on with site update? I updated some
>> of
>> my plugins by first finding a new remote site. In the process of the new
>> changes, the new version of the feature.xml embeds the URL to the update
>> site. I closed down Eclipse and created a few new plugin/feature
> versions,
>> built them and ftp'ed back to the site. Then went back and opened up
>> Eclipse and looked for changes to an existing feature. It came back with
> no
>> changes. Looking at the site.xml and feature.xml as well as the plug
>> that
>> changes, there are definitely new changes, but the site update doesn't
> think
>> so. I can't find any mistakes to the site update and my current Eclipse
>> doesn't have the new changes, any ideas why Eclipse thinks it is up to
> date?
>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02931 seconds
] 
Search
Help
Register
Login
Home
