| Re: [jdt-dev] [platform-dev] Need some more current pointers for getting started on JDT projects |
Hi Richard, Ed, I'm extremely pleased to be able to report that following your suggestions, I've got a working jdt-master eclipse build! Mucho grass!! My next challenge is persuading some veteran jdt committer to serve as a code-buddy as I dive into hacking ejc. While I'm a noob re: eclipse development, I'm pretty seasoned in most development practices, and a veteran of many system, language, and tool wars over many years. I can promise I won't be too much of a pest, and if pointed to docs, will do my best to absorb them in detail before asking for help. What would be fantastic would be links to How Tos covering
Cheers, -rjs On 9/15/2019 10:19 PM, Ed Merks wrote:
It sounds like you selected the SSH URIs for cloning. I.e., not https://git.eclipse.org/r/jdt/eclipse.jdt but rather ssh://${git.user.id|username}@git.eclipse.org:29418/jdt/eclipse.jdt correct? I assume you have an Eclipse account, but have you uploaded your public key to the server as described in the Gerrit wiki that's referenced by the documentation? I.e., specifically from this section: https://wiki.eclipse.org/Gerrit#Git_over_SSH Also, has an entry for "[git.eclipse.org]:29418 ssh-rsa " been added to your ~/.ssh/known_hosts? Note that it would be better to use https://bugs.eclipse.org/bugs/show_bug.cgi?id=536533 as documented in the wiki as the place to ask questions or to provide suggestions for improvements. This way the next person who has such an issue will be more likely find the answers. Regards, On 16.09.2019 07:01, Richard Steiger wrote:
After tying-off previous engagements, I'm back trying to setup the SDK. The Good News: your doc (below) was extremely helpful, and after following it to a T, I was able made significant progress, launching the provisioning and installation process. The Not So Good News: provisioning failed, with the following (partial) trace (after one attempt to restart):
at org.apache.sshd.client.session.ClientUserAuthService.tryNext(ClientUserAuthService.java:322) at org.apache.sshd.client.session.ClientUserAuthService.processUserAuth(ClientUserAuthService.java:258) at org.apache.sshd.client.session.ClientUserAuthService.process(ClientUserAuthService.java:205) at org.apache.sshd.common.session.helpers.AbstractSession.doHandleMessage(AbstractSession.java:400) at org.apache.sshd.common.session.helpers.AbstractSession.handleMessage(AbstractSession.java:333) at org.apache.sshd.common.session.helpers.AbstractSession.decode(AbstractSession.java:1097) at org.apache.sshd.common.session.helpers.AbstractSession.messageReceived(AbstractSession.java:294) at org.eclipse.jgit.internal.transport.sshd.JGitClientSession.messageReceived(JGitClientSession.java:214) at org.apache.sshd.common.session.helpers.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:63) at org.apache.sshd.common.io.nio2.Nio2Session.handleReadCycleCompletion(Nio2Session.java:357) at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:335) at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:332) at org.apache.sshd.common.io.nio2.Nio2CompletionHandler.lambda$completed$0(Nio2CompletionHandler.java:38) at java.security.AccessController.doPrivileged(Native Method) at org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:37) at sun.nio.ch.Invoker.invokeUnchecked(Unknown Source) at sun.nio.ch.Invoker$2.run(Unknown Source) at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source) ... 3 more Took 1 seconds. There are failed tasks. Press Back to choose different settings or Cancel to abort. The "No more authentication methods available" error message seems to suggest that I failed to obtain or supply some essential keys, but am hoping that you (or one of y'all) can pinpoint the root cause and advise how to resume the provisioning. Thanks! -rjs On 8/12/2019 12:58 AM, Ed Merks wrote:
As Paul suggests, if you really want to clone the repos and work with (or see all) the source, better to use the installer. There is a tutorial describing how the create an installation with the complete platform SDK: https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning Likely this is overkill for your purpose, but I find this an extremely useful resource to have around. It can help you find out how other things are already implemented in the platform and provides search capabilities not possible in any other way. For example, if I see a string some where in some dialog or elsewhere in the UI, I can search all the source to find where that is specified, e.g., often in a properties file. Then I can figure out the name of that property and can search for all uses of that property name in the *.java file files. Typically this will be some static final constant, and then I can open a call hierarchy on that constant to find all the places that its used. The advantage of having all the source is that a constant's value (if it's really a static constant with a constant _expression_), gets inlined by the compiler, so you cannot find uses of the static constants in other .class files. But with the source available, you can find the uses of constants in other *.java files in the workspace as well. So probably best not to include all the projects from the tutorial because that takes very long to set up, but following the tutorial you can go back to the previous page of the installer and select the subset of projects likely to be useful, e.g., the JDT projects and the various platform UI projects. Best of luck with your explorations. Cheers, Ed On 12.08.2019 09:38, Paul Pazderski wrote:
Also even if most Platform or JDT projects contain pom.xml files you should import them as existing Eclipse projects. I would recommend you to try Oomph setup (Eclipse Installer). https://www.eclipse.org/downloads/packages/ * In Eclipse Installer select advanced mode * select Eclipse IDE for Eclipse Committers (Latest) * on the next page you can select JDT projects and any other projects you are interested Notes on some of your other points: * If you get a timeout while cloning you can try it again. Those errors are usually temporarily. * The URLs on the Git Workflow page look outdated. In general Eclipse git repos are listed at https://git.eclipse.org/c/ and you can find clone URLs if you select a repo. * Regards the using http: as anonymous. You can clone from https: as anonymous. Anonymous only means you do not provide your username. (as required for ssh clone) Best regards Paul PS: found a wiki page for Eclipse SDK Oomph setup. https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning Maybe that helps too. Am 12.08.2019 um 09:04 schrieb Richard Steiger:
I have a few JDT experiments ("hacks") I want to try-out, and have been trying to follow the instructions in the various dev resources and guides, such as * eclipse.org/jdt/core/dev.php * wiki.eclipse.org/JDT_Core_Committer_FAQ * https://wiki.eclipse.org/JDT_Core_Programmer_Guide * eclipse.org/forums/index.php/f/13/ * and numerous others. The central problem (that's blocking me) is the fact that none of the above appear to be both current and correct, compounded by the fact that none of the docs have overt last-modified dates, nor major release level ranges. I therefore invested a fair amount of time trying to build a JDT dev project going down multiple routes, only to discover that each was effectively an abandoned gopher-hole. In more detail: * I tried to clone the repos listed in https://github.com/eclipse/eclipse.jdt.core; determined that maven can build all modules from the command-line with the -Pbuild-individual-bundles profile, but have yet to successfully import the modules into eclipse as a set of maven projects, since the project can't be compiled without the core eclipse infrastructure jars; attempting to extract them from the parent pom is a total crap-shoot, given its inherent complexity (else I might be on my way to at least prototyping the hacks, but miles from creating even a personal release); * I also tried cloning the repose listed in https://wiki.eclipse.org/Platform-releng/Git_Workflows (using http: as anonymous as instructed); the first 3 clones worked, but the next several crapped-out with timeouts, premature EOFs, or other faults; url #6 (*ssh://userid@xxxxxxxxxxxxxxx:29418/jdt/eclipse.jdt.core.git*) with the magic *29418 <ssh://userid@xxxxxxxxxxxxxxx:29418/jdt/eclipse.jdt.core.git>* segment alludes to this link being release-specific (viewing History doesn't pin-point what release the page presents, but the latest entry is back to '16 * I was initially excited to find eclipse.platform.common-I20190808-1800, then tracked it to https://projects.eclipse.org/projects/eclipse.platform, only to find it's either not indexed there, or might be stale. Any advice or live/good links to Getting Started docs would be most appreciated. Thanks, -rjs _______________________________________________ platform-dev mailing list platform-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev platform-dev mailing list platform-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev _______________________________________________ platform-dev mailing list platform-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev _______________________________________________ platform-dev mailing list platform-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev_______________________________________________ platform-dev mailing list platform-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev |
Richard Steiger ---09/17/2019 08:22:22 AM---Ed, I'm extremely pleased to be able to report that following your