{"action":"created","issue":{"url":"https://api.github.com/repos/de-jcup/egradle/issues/18","repository_url":"https://api.github.com/repos/de-jcup/egradle","labels_url":"https://api.github.com/repos/de-jcup/egradle/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/de-jcup/egradle/issues/18/comments","events_url":"https://api.github.com/repos/de-jcup/egradle/issues/18/events","html_url":"https://github.com/de-jcup/egradle/issues/18","id":177584671,"number":18,"title":"Hello from Nodeclipse","user":{"login":"paulvi","id":1614482,"avatar_url":"https://avatars.githubusercontent.com/u/1614482?v=3","gravatar_id":"","url":"https://api.github.com/users/paulvi","html_url":"https://github.com/paulvi","followers_url":"https://api.github.com/users/paulvi/followers","following_url":"https://api.github.com/users/paulvi/following{/other_user}","gists_url":"https://api.github.com/users/paulvi/gists{/gist_id}","starred_url":"https://api.github.com/users/paulvi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paulvi/subscriptions","organizations_url":"https://api.github.com/users/paulvi/orgs","repos_url":"https://api.github.com/users/paulvi/repos","events_url":"https://api.github.com/users/paulvi/events{/privacy}","received_events_url":"https://api.github.com/users/paulvi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-17T15:26:42Z","updated_at":"2016-09-19T08:46:36Z","closed_at":null,"body":"Hi, I am Paul Verest from @Nodeclipse \r\n\r\nI have Gradle IDE Pack\r\nhttps://marketplace.eclipse.org/content/gradle-ide-pack\r\nThat became alternative to Eclipse Buildship Gradle Integration\r\n\r\nI just discovered this plugin, and I wonder do you see your solution as possible to complement those 2 solutions?\r\nAny thoughts are welcomed.\r\n"},"comment":{"url":"https://api.github.com/repos/de-jcup/egradle/issues/comments/247939657","html_url":"https://github.com/de-jcup/egradle/issues/18#issuecomment-247939657","issue_url":"https://api.github.com/repos/de-jcup/egradle/issues/18","id":247939657,"user":{"login":"de-jcup","id":11644753,"avatar_url":"https://avatars.githubusercontent.com/u/11644753?v=3","gravatar_id":"","url":"https://api.github.com/users/de-jcup","html_url":"https://github.com/de-jcup","followers_url":"https://api.github.com/users/de-jcup/followers","following_url":"https://api.github.com/users/de-jcup/following{/other_user}","gists_url":"https://api.github.com/users/de-jcup/gists{/gist_id}","starred_url":"https://api.github.com/users/de-jcup/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/de-jcup/subscriptions","organizations_url":"https://api.github.com/users/de-jcup/orgs","repos_url":"https://api.github.com/users/de-jcup/repos","events_url":"https://api.github.com/users/de-jcup/events{/privacy}","received_events_url":"https://api.github.com/users/de-jcup/received_events","type":"User","site_admin":false},"created_at":"2016-09-19T08:46:36Z","updated_at":"2016-09-19T08:46:36Z","body":"Hello Paul,\r\n\r\nthe reason why I decided to create the plugin was my personal feeling of \"overloaded integration\", \"still not smooth working\" and \"two different worlds\" of the current gradle integrations into eclipse.\r\n\r\n**Thoughts about existing integrations**\r\nI tried \"Eclipse Buildship Gradle Integration\" and also the pivotal springsource gradle integrations (Gradle IDE) which is part of the gradle-ide-pack\r\n\r\n- Gradle IDE:\r\nIt has it own gradle nature and also a dedicated class container \"Gradle-Dependencies\" (see https://marketplace.eclipse.org/sites/default/files/Gradle-IDE-pack1.png ) which looks nice and has some advantages, but... This is not the way a standard \"gradle eclipse\" does, so a console call can destroy gradle-ide setups... In my team at work we have often problems with this situation (gradle works in console but not in eclipse.) and it was one of the main reasons why people decided to use intellij instead.\r\n- Buildship: I was a little bit disappointed in this approach (I tried it but it worked not fine for me and my team)\r\n\r\n**What does a developer REALLY need to work with gradle when you strict use KISS pattern?**\r\n- Run /store tasks often used\r\n- Configure environment parts (e.g. JAVA_HOME, debug mode etc.)\r\n- Important Results have to be shown to developers in an easy access way (e.g. for BUILD FAILED, Test failed etc.)\r\n- Use IDE and console world parallel:\r\n Keep as much as possible in default gradle style. Import/Synch mechansim for (existing) gradle task results (e.g. tests, eclipse settings etc.)\r\n- An editor which supports at least syntax highlighting and maybe more powerful features\r\n \r\n**Complementation possibilities**\r\n- I think Gradle-IDE-pack could use EGradle instead of the Gradle-IDE (as an replacement)\r\n- Maybe EGradle could use your \"Minimalist Gradle Editor\" instead of an own implementation (which is still very alpha). But there are some feature I would like to integrate into EGradle (e.g. hyperlinking, code template mechanism, auto completion etc.) which are not supported.\r\n- Buildship: hmm... I think it s a complete different approach and EGradle is only a simple working replacement\r\n\r\n"}}
{"actor":{"display_login":"de-jcup"}}