[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-dev] PDE Dev Bootstrap
|
Ok the only remaining errors after moving to ui-basic and closing the ui.tests project are:
Description Resource Path Location Type
Build path specifies execution environment J2SE-1.4. There are no JREs installed in the workspace that are strictly compatible with this environment. org.eclipse.pde.core Build path JRE System Library Problem
Build path specifies execution environment J2SE-1.4. There are no JREs installed in the workspace that are strictly compatible with this environment. org.eclipse.pde.ui Build path JRE System Library Problem
I'm using Sun's 1.6.0.22 JRE/JDK right now..
Thanks,
David
2011/3/29 Curtis Windatt
<Curtis_Windatt@xxxxxxxxxx>
Yes, pde-ui-basic should be enough.
To use the latest code, you need the
bundles from Indigo in your target platform (which can be modifed on a
preference page). By launching with Indigo, your target platform
will be good to go (the default target platform is the install you are
running).
API Tools is different. It compares
your current code in the workspace against a baseline (a previous release)
and warns you if you have broken an api restriction. The baseline
should be the most recent major release (Eclipse Helios 3.6). However,
you don't need to set up API Tools to test some patches, you can just reduce
the severity of missing baseline to ignore. It is a recommended practice
for developers to avoid introducing API issues into the builds.
Curtis
Good suggestions, I'll try pde-ui-basic and see if that
solves it. The Eclipse and baseline I set was Indigo M6a, I haven't
used baseline before (I do general OSGi dev, not Eclipse plug-in specific),
so I just created a default one which I assume was pointing at the Indigo
install. What is the best way to create a Helios baseline from an
Indigo install? Or should I be using Helios to launch and edit the
checked out Indigo version of PDE?
Also is pde-ui-basic sufficient to test the following bugs?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309701
https://bugs.eclipse.org/bugs/show_bug.cgi?id=338182
Thanks!
David
2011/3/29 Curtis Windatt <Curtis_Windatt@xxxxxxxxxx>
A few additional suggestions/questions:
1) Instead of using pde-all.psf, try pde-ui-basic.psf. It has a much
smaller set of projects. The test plug-in is still included, which
requires org.eclipse.test.performance (and o.e.t.p.win32 if on windows).
You could also close or delete the test project if you don't plan
on working on or running our test suite.
2) What did you set at the default baseline? It should be a Eclipse
3.6 (Helios) release. An alternative would be to remove your current
baseline and at the bottom of the preference page, change the missing api
baseline severity to ignore. You would not get the benefits of API
Tooling, but that it probably ok for your case.
3) What kind of errors remain?
Curtis
Hello David,
Thanks for showing interest in contributing to PDE.
When checking out all, you would have also get the tests projects in your
workspace. These projects depend on some test infrastructure projects which
are not part of Eclipse SDK, hence not in your target platform. For this
reason, you must be getting hundreds of compilation errors.
I would recommend to start with smaller set of projects. The PDE projects
are managed currently inside number of folders which you can locate inside
PDE folder in the CVS repository. The names are self-explanatory and shall
lead you do the projects of your interest. If you are unable to locate
the plug-ins you are looking for, do revert back. We will be glad to help.
regards,
Ankur..
---------------------------------------------------------------------------------------------------------
Eclipse PDE co-lead ● IBM India Software Lab, Bangalore
@ankur_sharma ● http://blog.ankursharma.org
---------------------------------------------------------------------------------------------------------
From: David
Erickson <halcyon1981@xxxxxxxxx>
To: pde-dev@xxxxxxxxxxx
Date: 29/03/2011
03:30
Subject: [pde-dev]
PDE Dev Bootstrap
Sent by: pde-dev-bounces@xxxxxxxxxxx
Hi all-
I'm looking for instructions on getting up and running developing for
PDE, I found some instructions here:
http://wiki.eclipse.org/PDE/Contributor_Guide
however I had the
following experience when following them:
I downloaded Indigo M6a, added the CVS repo, I was unable to right
click on the file as no import was available so I downloaded
pde-all.psf then did File->Import and went from there. It
successfully checked everything out. At this point there were many
errors, I went and added a default API baseline, which removed a few
of the errors. At this point Eclipse is telling me I have 529
remaining errors.
Any tips on resolving these would be great, or a pointer to
alternative instructions for getting productive on PDE.
Thanks,
David
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
