Re: [jdt-core-dev] Help checking out jdt-core projects

[David M Williams <david_williams@xxxxxxxxxx>]

Well, first and foremost, you might not
even need it. So hope I've not sent you down a blind alley. It will depend
on what else you have installed and/or loaded in your workspace, I think.
You will know if you need it if you have compile errors that mention missing
bundles in that .target file ... and I've no idea what JDT and its tests
need ... hamcrest? easymock? Sorry, just don't know. Or (more likely) if
you try to "run" the tests, you get similar messages ... could
not load the tests because ... such and such missing. But, honestly, if
you "install" the test framework and/or unit tests as a whole
(in addition to the few you need from the git repo into your workspace)
you may not need them. (You can install the tests and test framework from
our p2 repository, see below for "how to"). 

But, more on the eclipse-sdk-prereqs,
it should be pretty automatic, so not sure what's wrong. I do know it is
not related to maven or Tycho (for use in the the workbench) ... it just
so happens Tycho also makes use of it, if the pom's, etc., have been set
up for it. [Actually, this level of integration is one of the cooler aspects
of Tyhco! :) ] 

But, I suspect it has to do with the
way you clone/import it. It is its own repository, so you need to make
your own clone of of the aggregator (and in your case, you do not want
to "clone submodules ... that'd be too much). Then you need select
it in Git repository view, and say "import projects...", and
then instead of "import existing projects" (the usual choice)
you would want to say "import as a general project". That's because
the aggregator is not actually defined as a project in Eclipse, so when
you import it as a general project, Eclipse will create an untracked file
called .project ... thus making it a "top level project". I believe
it being a top level project is key to PDE being able to "see"
all the *.target files that exist, to populate it's preference list with.
-- but, again, you may not need it at all -- so my advice is to try and
make progress without it, and only worry if you get compile or "run
as.." errors about missing plugins. 

= = Installing test framework from p2
repository == 
As I mentioned, above, another, possibly
even better fix? is that you may need the "test framework installed"?
(Is that mentioned in instructions?) ... and, again, I'm not sure if needed,
or not. But if it is needed, you can 'install' the latest from a p2 repository
such as 

http://download.eclipse.org/eclipse/updates/4.5-I-builds/

(You'll have to add it to your "available
software sites list" in preferences.) 
And this means "install into your
development environment" ... not in a PDE runtime target. 
Assuming you have "categories"
checked (in the install new software dialog) ... you'll see a category
named

  Eclipse Tests, Examples, and
Extras        

And, if you expand that, you will see


    Eclipse SDK Tests  
     
    Eclipse Test Framework
       

among other things. I suspect the "Eclipse
Test Framework" is all you would need (and, it is much smaller than
"all the Eclipse SDK Tests". 

= = == = = = = = = 

So, again, I hope at least one or maybe
two of the above points will help you out -- and, if not you, I bet there
are some committers that don't even know all of these tricks :) 
(And, BTW, it is only my wordy writing
that makes it sound hard and complicated ... once you've done it once or
twice, it will seem like something you've done your whole life as developer
:) 

Keep us posted ... keep good notes!
... and good luck! [The notes are for how you can improve the wiki, and/or
let us know how things could be easier.]






From:      
 "Mohamed M. El-Beltagy"
<melbeltagy@xxxxxxxxx>
To:      
 "Eclipse JDT Core
developers list." <jdt-core-dev@xxxxxxxxxxx>, 
Date:      
 07/28/2014 03:07 PM
Subject:    
   Re: [jdt-core-dev]
Help checking out jdt-core projects
Sent by:    
   jdt-core-dev-bounces@xxxxxxxxxxx

---

Dear David,

Many thanks for your reply.

In response to your points and trying to learn possible options of setting
up the environment, I did the following steps:

1. Switched to Standard edition and it worked fine. Wrong assumption led
me using RCP edition. Many thanks for the correction.

2. When I tried to configure my target platform as explained, I could not
find this option, "eclipse-sdk-prereqs". So, I went on and continued…

3. Although "org.eclipse.releng.aggregator" repository is not
mentioned in the JDT/Core FAQ page, I managed to get it from here: https://wiki.eclipse.org/Platform-releng/Platform_Build#cloning_platform_source_tree
 which when loaded, still could not get the template mentioned "eclipse-sdl-prereqs".
It only displays two options RCP (binaries only) and RCP (with source).

4. Since the workspace was previously opened using RCP edition; I created
a new workspace from scratch using Standard edition, loaded "org.eclipse.releng.aggregator"
repository in an attempt to eliminate any possible workspace's metadata
left overs when I was using RCP edition earlier.
I still cannot get Eclipse to see the "eclipse-sdk-prereqs".

5. I opened the system files in order to get an idea of what's really happening
and noticed that the loaded project into Eclipse is actually not the folder
that contains the file "eclipse-sdk-prereqs.target".
Folder "eclipse.platform.releng.prereqs.sdk" is actually not
an Eclipse project, but contains a Maven project. And since Maven is not
bundled in the Standard edition, I could not go any further for now.

This is my first time trying to contribute to an Eclipse project and since
I have a working environment for development and running JUnit tests, as
described in JDT/Core FAQ, I will not ask for more details on how to get
the steps you mentioned working. This is simply so that I won’t waste
more of your or other members' valuable time.
But of course, and for future references for any new member, if you have
the time to explain, that would be great.

P.s., very sorry for the long email.

Best regards,
Mohamed Elbeltagy



On Monday, July 28, 2014 2:58 PM, David M
Williams <david_williams@xxxxxxxxxx> wrote:


> - My current environment is Eclipse
Luna (RCP edition), running using JDK8.

Not sure what led you to to package (and not sure what's in it, it might
work), but the "standard edition" (which is Eclipse SDK plus
EGit) is probably best "development environment" to use for JDT
related work. 

And to get this to work well, you will probably have to set the Plugin
Development "Preference --> Plugin Development --> Target platform"
and set it to "eclipse-sdk-prereqs" (it already should exist,
list, if you check out "org.eclipse.releng.aggregator" ... and
you just need to set it, hit "reload" and I usually click 'edit'
(not to make changes, but that seems to force all pre-reqs to download,
in case there's problems). [This "pre-reqs" step MIGHT NOT be
needed for what you are doing ... I just make it part of my routine ...
just in case). 

HTH 




From:        "Mohamed
M. El-Beltagy" <melbeltagy@xxxxxxxxx>
To:        "Eclipse
JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx>, 
Date:        07/28/2014
04:39 AM 
Subject:        Re:
[jdt-core-dev] Help checking out jdt-core projects
Sent by:        jdt-core-dev-bounces@xxxxxxxxxxx

---

Dear Jay, 

The first thing I tried was pointing to JDK 1.6 as JDK 1.4 execution environment.
It gave me this error message: 
Build path specifies execution environment J2SE-1.4. There are no JREs
installed in the workspace that are strictly compatible with this environment.

The error did not get resolved no matter what I did until I downloaded
and installed JDK 1.4 and configured Eclipse to use it as JDK 1.4 execution
environment. 

Notes (in case they make a difference):
- My current environment is Eclipse Luna (RCP edition), running using JDK8.
- No modifications were made to either workspace settings (except as mandated
by FAQ and https://wiki.eclipse.org/Platform-releng/Git_Workflows#Configure_the_workspace)
nor to any of the loaded projects. 

Please correct me if I'm mistaken or missing something.
  


On Monday, July 28, 2014 8:51 AM, Jayaprakash Arthanareeswaran <jarthana@xxxxxxxxxx>
wrote: 


Hello Mohamed, 

It's not absolutely required to have 1.4 JRE to get the test projects compiling
and running 
As a work around, you can simply point the 1.4 SE execution environment
to point it to 1.6 JRE and that should get rid of the compiler works. And
as David rightly pointed out, the tests can be run with newer versions
of JRE already. The bug I raised (440503) is not a high priority and I
only raised it to bring the projects consistent and up to date. 

Regards, 
Jay 



From:        "Mohamed
M. El-Beltagy" <melbeltagy@xxxxxxxxx>
To:        "Eclipse
JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx>
Date:        07/28/2014
11:04 AM 
Subject:        Re:
[jdt-core-dev] Help checking out jdt-core projects
Sent by:        jdt-core-dev-bounces@xxxxxxxxxxx

---

Actually without the presence of JDK 1.4 (installed and configured as execution
environment), the project's won't compile due to default settings of Eclipse
IDE (error on missing execution environment).
And to get working on the code without altering any settings (so that environment
would be as expected), I downloaded and installed JDK 1.4 and 1.6 and configured
my workspace to refer to them both in the installed JREs


On Monday, July 28, 2014 8:26 AM, David M Williams <david_williams@xxxxxxxxxx>
wrote: 


> Until then, you have to have both 1.4 and 1.6 EE for your tests and
JDT/Core project respectively. 

And in case it's not obvious, or in case I'm mistaken, this simply means
you need to have the 1.4 and 1.6 (?and 1.5) JDKs installed and defined
in Preferences - Installed JREs, - Execution Environments. And that is
what gives a "good" compile. But to actually run the tests, I'm
guessing, 1.6 is fine. I just wanted to distinguish the difference between
compiling the bundles, and running them. 





From:        Jayaprakash
Arthanareeswaran <jarthana@xxxxxxxxxx>
To:        "Eclipse
JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx>, 
Date:        07/28/2014
01:22 AM 
Subject:        Re:
[jdt-core-dev] Help checking out jdt-core projects
Sent by:        jdt-core-dev-bounces@xxxxxxxxxxx

---

Hello Mohamed, 

We appreciate the interest you have shown in contributing to JDT Core!
Hope my answers help you complete your workspace set up:

A#1:  I have raised bug 440503 to track this. Until then, you have
to have both 1.4 and 1.6 EE for your tests and JDT/Core project respectively.

A#2: You should be using either the latest 4.5 I build or 4.4 official
build. I have updated the wiki page to reflect the correct information.

A#3: If you want to contribute to Eclipse 4.5 (Mars),  you should
be working off master branch. Again, the wiki page has been updated accordingly.

Hope this helps. 

Regards, 
Jay 




From:        "Mohamed
M. El-Beltagy" <melbeltagy@xxxxxxxxx>
To:        "jdt-core-dev@xxxxxxxxxxx"
<jdt-core-dev@xxxxxxxxxxx> 
Date:        07/28/2014
10:16 AM 
Subject:        [jdt-core-dev]
Help checking out jdt-core projects 
Sent by:        jdt-core-dev-bounces@xxxxxxxxxxx

---

On planning to contribute to JDT/Core project and work on a bug that has
been taged as helpwanted; I've checked out the master branch of the JDT/Core
project.

I finally managed to fix all compilation errors I faced during the setup
of the environment to start working.
So, I wanted to update the http://wiki.eclipse.org/JDT_Core_Committer_FAQ
so that new comers wouldn't face the same issues.

My questions are:

Q# 1- This link http://wiki.eclipse.org/JDT_Core_Committer_FAQ
states that the org.eclipse.jdt.core.tests.* projects should be checked
out. 
The problem is that these projects require J2SE-1.4 although the JDT/Core
projects themselves have been updated to use JavaSE-1.6  as indicated
by the FAQ page (updated by Stephan.herrmann.berlin.de on 14th June, 2014)

Will the tests projects be updated as well, or the FAQ document should
be updated to include the JDK1.4 also (note I checked out the master branch
and since the upgrade to JDK1.6 is recent, I'm not sure what to expect)?

Q# 2- I've used Eclipse Luna for development as well as the target API
Baseline. I know the FAQ page says to use 3.8. But since there's no Eclipse
3.8, I don't really know what version of Eclipse I should be using.
Also, just to confirm I must use RCP edition, right?

Q# 3. Which branch should I be checking out to use in my case?

Your reply and time reading this email are highly appreciated._______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
_______________________________________________




jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit 
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev


_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev