Home » Language IDEs » PHP Development Tools (PDT) » How to keep an all-in-one up to date?
|
| Re: How to keep an all-in-one up to date? [message #90459 is a reply to message #90427] |
Thu, 15 January 2009 11:07   |
Eclipse User |
|
|
|
Originally posted by: spam.networks.fi
Dennis Verspuij wrote:
> What is the recommended procedure to keep an all-in-one PDT installation
> up to date? Should I check the downloads provided on
> http://www.eclipse.org/pdt/downloads/page periodically and extract some
> new *-Update.zip packages somewhere?
> Or can "Automatic updates" do this for me? I do have it enabled but it
> does for instance not come up with a 2.0.1 update for my 2.0.0GA
> all-in-one. Must I setup additional sites or modify the "available
> software sites"?
>
>
This is absolutely valid question and i'd like good and deep answer on
that also.
|
|
| | | |
| Re: How to keep an all-in-one up to date? [message #90630 is a reply to message #90459] |
Thu, 15 January 2009 18:22 |
| Eclipse User |
|
|
|
Originally posted by: nickboldt+eclipse+newsgroup.gmail.com
You have a few options.
a) Each time a new, updated all-in-one is made available, download it,
unpack it, and point it at your existing workspace. Simple,
self-contained, and no updating required. (Note that anything else
you've installed into your Eclipse, like for debugging or other
scripting support, will need to be reinstalled.)
b) From an existing installed all-in-one, load up the update site you
like best (interim, milestones, or releases -- see
http://www.eclipse.org/pdt/updates/ for the list) and install updates
into your existing Eclipse. Restart when prompted.
c) Download a new, updated Update site zip. Unpack it. From an existing
installed all-in-one, use the Install Manager to install the new plugins
from the unpacked local update site. Restart when prompted.
d) Download a new, updated SDK or runtime zip. Unpack it into your
existing Eclipse's dropins folder, eg., ~/eclipse/dropins/. Restart
eclipse with the -clean flag, and be prepared to wait a bit as it finds
the new dropins and loads them. (The purists might say that you should
remove the old stuff in dropins/eclipse/plugins/*pdt* and
dropins/eclipse/features/*pdt*, but you don't strictly have to.)
Bear in mind that you cannot update from 2.0.0 to 2.1.0, but you can
move from 2.0.0 to 2.0.x. This is because 2.1.0 requires Eclipse 3.5,
whereas 2.0.x require Eclipse 3.4. If you're simply replacing one
all-in-one with another (option (a)) then you can move from 2.0 to 2.1
because the all-in-ones also include the correct version of Eclipse.
HTH,
Nick
Jasmo Hiltula wrote:
> Dennis Verspuij wrote:
>> What is the recommended procedure to keep an all-in-one PDT installation
>> up to date? Should I check the downloads provided on
>> http://www.eclipse.org/pdt/downloads/page periodically and extract some
>> new *-Update.zip packages somewhere?
>> Or can "Automatic updates" do this for me? I do have it enabled but it
>> does for instance not come up with a 2.0.1 update for my 2.0.0GA
>> all-in-one. Must I setup additional sites or modify the "available
>> software sites"?
>>
>>
> This is absolutely valid question and i'd like good and deep answer on
> that also.
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
|
|
|
| Re: How to keep an all-in-one up to date? [message #90645 is a reply to message #90630] |
Thu, 15 January 2009 18:31 |
 sNop
Messages: 281
Registered: July 2009 |
Senior Member |
|
|
Nick Boldt napsal(a):
> You have a few options.
>
> a) Each time a new, updated all-in-one is made available, download it,
> unpack it, and point it at your existing workspace. Simple,
> self-contained, and no updating required. (Note that anything else
> you've installed into your Eclipse, like for debugging or other
> scripting support, will need to be reinstalled.)
>
> b) From an existing installed all-in-one, load up the update site you
> like best (interim, milestones, or releases -- see
> http://www.eclipse.org/pdt/updates/ for the list) and install updates
> into your existing Eclipse. Restart when prompted.
>
> c) Download a new, updated Update site zip. Unpack it. From an existing
> installed all-in-one, use the Install Manager to install the new plugins
> from the unpacked local update site. Restart when prompted.
>
> d) Download a new, updated SDK or runtime zip. Unpack it into your
> existing Eclipse's dropins folder, eg., ~/eclipse/dropins/. Restart
> eclipse with the -clean flag, and be prepared to wait a bit as it finds
> the new dropins and loads them. (The purists might say that you should
> remove the old stuff in dropins/eclipse/plugins/*pdt* and
> dropins/eclipse/features/*pdt*, but you don't strictly have to.)
>
> Bear in mind that you cannot update from 2.0.0 to 2.1.0, but you can
> move from 2.0.0 to 2.0.x. This is because 2.1.0 requires Eclipse 3.5,
> whereas 2.0.x require Eclipse 3.4. If you're simply replacing one
> all-in-one with another (option (a)) then you can move from 2.0 to 2.1
> because the all-in-ones also include the correct version of Eclipse.
>
> HTH,
>
> Nick
>
You wrote it very good, could you copy&paste to the PDT's wiki ? I think that is good
source of the informations how to update PDT and what is most important is that you
described all possibilies how to update ;)
thank you
|
|
| |
| Re: How to keep an all-in-one up to date? [message #90797 is a reply to message #90645] |
Fri, 16 January 2009 16:41 |
| Eclipse User |
|
|
|
Originally posted by: nickboldt+eclipse+newsgroup.gmail.com
Wikified.
http://wiki.eclipse.org/PDT/FAQ#How_do_I_update_PDT.3F
BTW, the wiki is editable by anyone with a Bugzilla account, and for
that all you need is an email address. We encourage anyone and everyone
to edit the wiki to provide more information, updated information, or
just better information, should you find something missing, incorrect,
or misleading.
Don't be a stranger! Editing the wiki is a great way to give back to the
community and the committers who make Eclipse, and PDT, a possibility.
Cheers,
Nick
sNop wrote:
> Nick Boldt napsal(a):
>> You have a few options.
>>
>> a) Each time a new, updated all-in-one is made available, download it,
>> unpack it, and point it at your existing workspace. Simple,
>> self-contained, and no updating required. (Note that anything else
>> you've installed into your Eclipse, like for debugging or other
>> scripting support, will need to be reinstalled.)
>>
>> b) From an existing installed all-in-one, load up the update site you
>> like best (interim, milestones, or releases -- see
>> http://www.eclipse.org/pdt/updates/ for the list) and install updates
>> into your existing Eclipse. Restart when prompted.
>>
>> c) Download a new, updated Update site zip. Unpack it. From an existing
>> installed all-in-one, use the Install Manager to install the new plugins
>> from the unpacked local update site. Restart when prompted.
>>
>> d) Download a new, updated SDK or runtime zip. Unpack it into your
>> existing Eclipse's dropins folder, eg., ~/eclipse/dropins/. Restart
>> eclipse with the -clean flag, and be prepared to wait a bit as it finds
>> the new dropins and loads them. (The purists might say that you should
>> remove the old stuff in dropins/eclipse/plugins/*pdt* and
>> dropins/eclipse/features/*pdt*, but you don't strictly have to.)
>>
>> Bear in mind that you cannot update from 2.0.0 to 2.1.0, but you can
>> move from 2.0.0 to 2.0.x. This is because 2.1.0 requires Eclipse 3.5,
>> whereas 2.0.x require Eclipse 3.4. If you're simply replacing one
>> all-in-one with another (option (a)) then you can move from 2.0 to 2.1
>> because the all-in-ones also include the correct version of Eclipse.
>>
>> HTH,
>>
>> Nick
>>
>
> You wrote it very good, could you copy&paste to the PDT's wiki ? I think that is good
> source of the informations how to update PDT and what is most important is that you
> described all possibilies how to update ;)
>
> thank you
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
|
|
|
| Re: How to keep an all-in-one up to date? [message #90812 is a reply to message #90797] |
Fri, 16 January 2009 17:26 |
sNop
Messages: 281
Registered: July 2009 |
Senior Member |
|
|
Nick Boldt napsal(a):
> Wikified.
>
> http://wiki.eclipse.org/PDT/FAQ#How_do_I_update_PDT.3F
>
> BTW, the wiki is editable by anyone with a Bugzilla account, and for
> that all you need is an email address. We encourage anyone and everyone
> to edit the wiki to provide more information, updated information, or
> just better information, should you find something missing, incorrect,
> or misleading.
>
> Don't be a stranger! Editing the wiki is a great way to give back to the
> community and the committers who make Eclipse, and PDT, a possibility.
>
> Cheers,
>
> Nick
>
Hi Nick,
I have created http://wiki.eclipse.org/PDT/how-to-keep-an-all-in-one-up-to- date from your
newsgroup message
But I have problem when i want to update M2.0.1 throught update manager(from local or
remote update site), because M have the same id number, simply eclipse tells me that pdt
is still installed.
Do you know about this bug, i don't know if there is tha same problem with I or N builds
thank you for wiki text
|
|
|
| Re: How to keep an all-in-one up to date? [message #90827 is a reply to message #90812] |
Fri, 16 January 2009 17:44 |
| Eclipse User |
|
|
|
Originally posted by: nickboldt+eclipse+newsgroup.gmail.com
> But I have problem when i want to update M2.0.1 throught update manager(from local or
> remote update site), because M have the same id number, simply eclipse tells me that pdt
> is still installed.
If the build ID is the same, so are the bits. You'll need a newer build.
> Do you know about this bug, i don't know if there is tha same problem with I or N builds
I and N builds are for PDT 2.1.
M builds are for PDT 2.0.1.
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
|
|
| |
| Re: How to keep an all-in-one up to date? [message #90873 is a reply to message #90858] |
Fri, 16 January 2009 21:56 |
| Eclipse User |
|
|
|
Originally posted by: nickboldt+eclipse+newsgroup.gmail.com
/me looks at screnshot
Ah, I see. The issue here is that the *feature* is not new, but (maybe)
some of the underlying plugins are.
I suspect the best workaround here (for you) is to uninstall the older
PDT feature, restart, then install the newer one.
For the PDT devs, the solution is to commit a change to their features
(even a no-op one) more often so that the change will be tagged, the map
file will be updated and thus the version on the feature will be
incremented so early adopters can update more regularly.
Nick
sNop wrote:
> Nick Boldt napsal(a):
>>> But I have problem when i want to update M2.0.1 throught update
>>> manager(from local or
>>> remote update site), because M have the same id number, simply eclipse
>>> tells me that pdt
>>> is still installed.
>> If the build ID is the same, so are the bits. You'll need a newer build.
>>
>
> But how can i update PDT 2.0.0.v20081229-1135 (which is in stable all-in-one packege) to
> the latest PDT 2.0.1 M200901150831(which have the same id of package so PDT
> 2.0.0.v20081229-1135) throught Ganymede update manager ?
>
> I have attached picture, which everythink describe:
> http://img231.imageshack.us/img231/5880/updateproblemqb0.jpg
>
>>> Do you know about this bug, i don't know if there is tha same problem
>>> with I or N builds
>> I and N builds are for PDT 2.1.
>> M builds are for PDT 2.0.1.
>>
>
> aha
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
|
|
| |
Goto Forum:
Current Time: Sat Nov 09 01:58:58 GMT 2024
Powered by FUDForum. Page generated in 0.03834 seconds |
] 
Search
Help
Register
Login
Home
