| Plugin dev [message #328933] |
Fri, 06 June 2008 16:31  |
Eclipse User |
|
|
|
Wayne and Eric, thanks for setting me straight on plugin dev. I'm
convinced, and am spending the rest of the afternoon getting set up with
3.4 RC2.
By the way, I had had in my head that contributing to Eclipse and plugin
dev were two different things. So glad to find out I've only got one
thing to learn!
Question: When I've upgraded Eclipse in the past, it was NOTHING like the
easy Update Manager process I know for managing plugins. I've had a quick
look at Yoxos way back, but didn't love it. Has persisting
installation-specific settings (eclipse.ini, installed plugins, and others
I may be unaware of) been made easier in the last releases?
I'm just reading http://wiki.eclipse.org/Platform_UI/How_to_Contribute
which is helpful (but so buried!), but depends on me having my eclipse
installed. ...I'm still left with the upgrading cycle question.
Is there such a thing as running, do I want to run, the CVS version?
Thanks
e.
|
|
|
| Plugin dev [message #328962 is a reply to message #328933] |
Mon, 09 June 2008 08:58  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Ed Zwart wrote:
> Question: When I've upgraded Eclipse in the past, it was NOTHING like
> the easy Update Manager process I know for managing plugins. I've had a
> quick look at Yoxos way back, but didn't love it. Has persisting
> installation-specific settings (eclipse.ini, installed plugins, and
> others I may be unaware of) been made easier in the last releases?
With the new update infrastructure, called p2 (short for Provisioning
version 2), it is somewhat easier, but still seems to require installing
optional plugins. The UI and underlying infrastructure for doing that is
much better as of 3.4, though.
Other than that, all I can think of that has to be done is to export and
import preferences, and even then only if you move to a new workspace
when upgrading; if you point the new version at an existing workspace,
even that is unnecessary.
> Is there such a thing as running, do I want to run, the CVS version?
To run it as your primary dev environment, you'd have to build it
yourself. Of course, nearly the same thing would be to run a nightly
build. See this page for a description of the different builds that are
produced: http://download.eclipse.org/eclipse/downloads/build_types.ht ml
If I wanted to be REALLY cutting edge, I would run Integration builds;
but I never do that; I run Milestone builds (for some reason, not
described on that page above) or RC builds, as I have been doing with
3.4 since Milestone 4.
However, if you only want to develop targeting the latest and greatest,
you don't actually need to be running the latest and greatest. You can,
for example, run a milestone build but check out the latest HEAD of
various projects from Eclipse CVS. When launching your runtime (to test
whatever plugin coding you've done), any plugin projects you have
checked out in your workspace will override whatever the target
environment contains. For example, I did some patches for JFace late
last year; I was running 3.3 but patches need to be against the latest
in CVS. So I set up a 3.4 target, checked out the 2 or 3 relevant JFace
projects from CVS, and worked on the code (in 3.3) but tested it by
running against a 3.4 target.
This stuff is not obvious unless/until you've learned about plugin
development, so as you're going through the "how to contribute" docs,
please feel free to ask more specific questions.
Hope this helps,
Eric
|
|
|
| Re: Plugin dev [message #328984 is a reply to message #328962] |
Mon, 09 June 2008 16:42 |
| Eclipse User |
|
|
|
Eric Rizzo wrote:
> This stuff is not obvious unless/until you've learned about plugin
> development, so as you're going through the "how to contribute" docs,
> please feel free to ask more specific questions.
Fair enough. I'll be back...
|
|
|
Powered by
FUDForum. Page generated in 0.03571 seconds
Home