| Request for direction [message #328840] |
Wed, 04 June 2008 20:56  |
 Ed Zwart
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
I've been using Eclipse for a number of years, both for PHP and Java dev.
Many times I've wanted the feel-good of giving back (picking off a few
bugs, for example). Recently, a bug I encountered has reignited that
desire.
I would like something like the following:
An eclipse installation and workspace that contains my current projects as
well as any eclipse projects I've checked out, and a process for building
a new eclipse and running it (using the same workspace -- I'm not a big
fan of maintaining multiple workspaces; I figure that's what closing
projects is for).
I discovered http://wiki.eclipse.org/index.php/CVS_Howto for instructions
on how to check out modules, but I'm still tripped up on a detail.
I checked out org.eclipse.ant.ui to poke around in
org.eclipse.ant.internal.ui.datatransfer.AntBuildfileExportW izard because
of a minor bug I noticed.
(I also searched bugzilla, and know how to submit a report, but what I'm
more concerned with than the actual bug is the process for tinkering to
build up my skills enough to one day actually contribute -- not to mention
building my skills for selfish reasons!)
Back to org.eclipse.ant.ui... I checked it out just fine, but it won't
build without resolving all the missing dependencies of course. I can
resolve them all manually by checking out a gazillion other projects, but
I'd rather not!
So, that's the question.. what's my best direction?
I'm thinking something like this.. Download (or copy) a new eclipse
installation, point to its source from the checked out project, build that
project, and replace its corresponding jar in the eclipse installation.
That seems wrong, but it's the best I can come up with. Any and all
advice greatly appreciated.
e.
|
|
|
| Re: Request for direction [message #328843 is a reply to message #328840] |
Wed, 04 June 2008 21:10  |
Wayne Beaton
Messages: 554
Registered: December 2017 |
Senior Member |
|
|
When you check straight out of CVS, you always get the latest. I just
checked out org.eclipse.ant.ui into the Ganymede RC1 release (which
contains Eclipse 3.4RC1) and it builds fine with no other projects
loaded. I assume that you're using an earlier version of Eclipse.
You have three choices. Here are two of them (the third takes too long
to explain and is probably not what you want anyway):
You can use the latest version of Eclipse and check out the most recent
version of the plug-in from CVS.
You can, instead of checking out the latest version of the plug-in,
check out an older version. Highlight the plug-in in the CVS
Repositories view and select "Check out as..." On the third page of the
wizard, you can choose an older version of the plug-in. If you scroll
down the list of versions, you'll come to some marked R3_3_1, for
example, corresponding to Eclipse version 3.3.1.
The first option is probably the most useful.
HTH,
Wayne
On Wed, 2008-06-04 at 20:56 +0000, Ed Zwart wrote:
> Back to org.eclipse.ant.ui... I checked it out just fine, but it
> won't
> build without resolving all the missing dependencies of course. I
> can
> resolve them all manually by checking out a gazillion other projects,
> but
> I'd rather not!
|
|
|
|
| Re: Request for direction [message #328864 is a reply to message #328840] |
Thu, 05 June 2008 14:34 |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Ed Zwart wrote:
> Back to org.eclipse.ant.ui... I checked it out just fine, but it won't
> build without resolving all the missing dependencies of course. I can
> resolve them all manually by checking out a gazillion other projects,
> but I'd rather not!
>
> So, that's the question.. what's my best direction?
What package of Eclipse do you use? If you're going to tinker around
with the Eclipse source itself, you usually want to be using the
"Eclipse for RCP/Plug-in Developers" package from
http://www.eclipse.org/downloads/
That one will have the source plugins for all the Eclipse "core"
features, which will make things much easier for tinkering and
exploration. With that version, a checkout of one particular plugin from
CVS should resolve everything correctly. That is, assuming you are
matching up the version you run with the version you check out, as Wayne
already pointed out.
I'll reiterate Wayne's recommendation to go to the latest (3.4 RC2) -
otherwise anything you code will have to be upgraded to fit with the
latest. Especially important if you're going to fix a bug or provide
some other patch that a committer will have to accept.
Hope this helps,
Eric
|
|
|
|
Powered by
FUDForum. Page generated in 0.02832 seconds
] 
Search
Help
Register
Login
Home
