{"id":34626,"date":"2025-11-19T23:41:01","date_gmt":"2025-11-19T20:41:01","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=34626"},"modified":"2025-11-19T23:41:01","modified_gmt":"2025-11-19T20:41:01","slug":"gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/","title":{"rendered":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber"},"content":{"rendered":"

<\/p>\n

Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber<\/h2>\n

Giri\u015f<\/h3>\n

Modern yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde, projelerin derlenmesi, test edilmesi, ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131n y\u00f6netilmesi ve da\u011f\u0131t\u0131lmas\u0131 gibi tekrarlayan g\u00f6revler otomasyon ara\u00e7lar\u0131 ile b\u00fcy\u00fck \u00f6l\u00e7\u00fcde kolayla\u015ft\u0131r\u0131lm\u0131\u015ft\u0131r. Bu ara\u00e7lar aras\u0131nda Gradle, esnekli\u011fi, performans odakl\u0131 yap\u0131s\u0131 ve geni\u015fletilebilirli\u011fi ile \u00f6ne \u00e7\u0131kmaktad\u0131r. \u00d6te yandan, Eclipse IDE (Integrated Development Environment), uzun y\u0131llard\u0131r Java geli\u015ftiricileri aras\u0131nda pop\u00fclerli\u011fini koruyan, zengin \u00f6zelliklere sahip ve g\u00fc\u00e7l\u00fc bir geli\u015ftirme ortam\u0131d\u0131r. Bir\u00e7ok geli\u015ftirici, projelerini y\u00f6netmek i\u00e7in Gradle’\u0131n g\u00fcc\u00fcn\u00fc kullan\u0131rken, kod yazma, hata ay\u0131klama ve genel proje y\u00f6netimi i\u00e7in Eclipse’in sundu\u011fu konfor ve verimlilikten vazge\u00e7mek istemez. Bu iki g\u00fc\u00e7l\u00fc arac\u0131n birle\u015fimi, geli\u015ftirme s\u00fcrecini \u00f6nemli \u00f6l\u00e7\u00fcde h\u0131zland\u0131rabilir ve basitle\u015ftirebilir.<\/p>\n

Bu makale, Gradle’\u0131n temel prensiplerinden ba\u015flayarak, Eclipse IDE ile entegrasyonunu ad\u0131m ad\u0131m ele alacakt\u0131r. \u00d6zellikle, Eclipse i\u00e7in resmi Gradle entegrasyon eklentisi olan Buildship’in kurulumu, mevcut Gradle projelerinin Eclipse’e aktar\u0131lmas\u0131, yeni Gradle projelerinin olu\u015fturulmas\u0131 ve Eclipse i\u00e7inde Gradle g\u00f6revleriyle verimli bir \u015fekilde \u00e7al\u0131\u015fma konular\u0131na odaklan\u0131lacakt\u0131r. Ayr\u0131ca, s\u0131k kar\u015f\u0131la\u015f\u0131lan sorunlara \u00e7\u00f6z\u00fcmler ve ileri seviye kullan\u0131m ipu\u00e7lar\u0131 da sunularak, geli\u015ftiricilerin Gradle ve Eclipse ikilisinden en iyi \u015fekilde faydalanmalar\u0131 hedeflenmektedir. Bu rehberin sonunda, okuyucular\u0131n Gradle tabanl\u0131 projeleri Eclipse ortam\u0131nda sorunsuz bir \u015fekilde y\u00f6netebilecek ve geli\u015ftirebilecek bilgiye sahip olmalar\u0131 ama\u00e7lanmaktad\u0131r.<\/p>\n

Gradle Temelleri<\/h3>\n

Yaz\u0131l\u0131m projeleri b\u00fcy\u00fcd\u00fck\u00e7e, derleme, test etme, paketleme ve da\u011f\u0131t\u0131m gibi s\u00fcre\u00e7ler karma\u015f\u0131k hale gelir. Bu s\u00fcre\u00e7leri manuel olarak y\u00f6netmek zaman al\u0131c\u0131, hataya a\u00e7\u0131k ve verimsizdir. \u0130\u015fte bu noktada “build otomasyon ara\u00e7lar\u0131” devreye girer. Build otomasyonu, bu tekrarlayan g\u00f6revleri otomatikle\u015ftirerek geli\u015ftiricilerin temel i\u015flerine, yani kod yazmaya odaklanmas\u0131n\u0131 sa\u011flar.<\/p>\n

Build Otomasyonu Neden Gerekli?<\/h4>\n

Bir projenin derlenmesi, kaynak kodlar\u0131n makine diline \u00e7evrilmesini, ba\u011f\u0131ml\u0131l\u0131klar\u0131n (di\u011fer k\u00fct\u00fcphaneler) \u00e7\u00f6z\u00fclmesini ve projenin \u00e7al\u0131\u015ft\u0131r\u0131labilir bir formata getirilmesini i\u00e7erir. Test otomasyonu, kodun beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in testleri otomatik olarak \u00e7al\u0131\u015ft\u0131rmay\u0131 sa\u011flar. Bu s\u00fcre\u00e7lerin otomatize edilmesi, insan hatalar\u0131n\u0131 azalt\u0131r, tutarl\u0131l\u0131\u011f\u0131 art\u0131r\u0131r ve \u00f6zellikle b\u00fcy\u00fck ekiplerde i\u015fbirli\u011fini kolayla\u015ft\u0131r\u0131r.<\/p>\n

Gradle’\u0131n Di\u011fer Build Ara\u00e7lar\u0131ndan Fark\u0131<\/h4>\n

Piyasada Ant ve Maven gibi k\u00f6kl\u00fc build ara\u00e7lar\u0131 bulunurken, Gradle kendine \u00f6zg\u00fc avantajlar\u0131yla \u00f6ne \u00e7\u0131kar.
\n* Ant:<\/strong> XML tabanl\u0131d\u0131r ve olduk\u00e7a esnektir, ancak her \u015feyi s\u0131f\u0131rdan tan\u0131mlaman\u0131z gerekti\u011fi i\u00e7in b\u00fcy\u00fck projelerde y\u00f6netimi zorla\u015fabilir. “Prosed\u00fcrel” bir yakla\u015f\u0131ma sahiptir.
\n* Maven:<\/strong> Konvansiyon odakl\u0131 (Convention over Configuration) bir yakla\u015f\u0131ma sahiptir. Standart bir proje yap\u0131s\u0131 ve ya\u015fam d\u00f6ng\u00fcs\u00fc sunar, bu da projelerin h\u0131zl\u0131ca ba\u015flat\u0131lmas\u0131n\u0131 sa\u011flar. Ancak, bu kat\u0131 yap\u0131 bazen esnekli\u011fi k\u0131s\u0131tlayabilir. XML tabanl\u0131d\u0131r.
\n* Gradle:<\/strong> Maven’\u0131n konvansiyonel yakla\u015f\u0131m\u0131n\u0131 ve Ant’\u0131n esnekli\u011fini birle\u015ftirir. Groovy veya Kotlin tabanl\u0131 bir DSL (Domain Specific Language) kullanarak build scriptleri yazar, bu da XML’e k\u0131yasla daha okunabilir, daha k\u0131sa ve daha g\u00fc\u00e7l\u00fc scriptler olu\u015fturulmas\u0131n\u0131 sa\u011flar. Performans odakl\u0131d\u0131r (inkremental buildler, paralel g\u00f6rev \u00e7al\u0131\u015ft\u0131rma). Geni\u015fletilebilir bir eklenti ekosistemine sahiptir.<\/p>\n

Groovy ve Kotlin DSL<\/h4>\n

Gradle’\u0131n en belirgin \u00f6zelliklerinden biri, build scriptlerini yazmak i\u00e7in Groovy veya Kotlin programlama dillerini kullanmas\u0131d\u0131r.
\n* Groovy DSL:<\/strong> Java sanal makinesi (JVM) \u00fczerinde \u00e7al\u0131\u015fan dinamik bir dildir. Java ile uyumludur ve daha az kodla daha fazlas\u0131n\u0131 yapman\u0131za olanak tan\u0131r. Gradle, uzun s\u00fcredir Groovy DSL’i desteklemektedir.
\n* Kotlin DSL:<\/strong> Kotlin, JetBrains taraf\u0131ndan geli\u015ftirilen statik tipli bir dildir. Daha iyi IDE deste\u011fi, derleme zaman\u0131 hata denetimi ve daha okunabilir kod sunar. Son y\u0131llarda Gradle projelerinde Kotlin DSL kullan\u0131m\u0131 pop\u00fclerlik kazanm\u0131\u015ft\u0131r. Her iki DSL de g\u00fc\u00e7l\u00fcd\u00fcr ve se\u00e7im genellikle geli\u015ftiricinin tercihine ba\u011fl\u0131d\u0131r.<\/p>\n

build.gradle<\/code> Dosyas\u0131 Yap\u0131s\u0131<\/h4>\n

Bir Gradle projesinin kalbi build.gradle<\/code> (veya Kotlin DSL kullan\u0131l\u0131yorsa build.gradle.kts<\/code>) dosyas\u0131d\u0131r. Bu dosya, projenin nas\u0131l derlenece\u011fini, hangi ba\u011f\u0131ml\u0131l\u0131klara sahip oldu\u011funu ve hangi g\u00f6revlerin \u00e7al\u0131\u015ft\u0131r\u0131labilece\u011fini tan\u0131mlar. Temel bile\u015fenleri \u015funlard\u0131r:
\n* plugins<\/code>:<\/strong> Projeye belirli yetenekler kazand\u0131ran eklentileri tan\u0131mlar. \u00d6rne\u011fin, java<\/code> eklentisi bir Java projesinin derlenmesi, test edilmesi ve paketlenmesi i\u00e7in gerekli g\u00f6revleri ekler.
\n* group<\/code>, version<\/code>, sourceCompatibility<\/code>:<\/strong> Proje meta verilerini ve Java s\u00fcr\u00fcm uyumlulu\u011funu belirtir.
\n* repositories<\/code>:<\/strong> Ba\u011f\u0131ml\u0131l\u0131klar\u0131n nereden indirilece\u011fini belirtir. Genellikle Maven Central veya JCenter gibi depolar kullan\u0131l\u0131r.
\n* dependencies<\/code>:<\/strong> Projenin ihtiya\u00e7 duydu\u011fu harici k\u00fct\u00fcphaneleri ve mod\u00fclleri tan\u0131mlar. implementation<\/code>, testImplementation<\/code> gibi farkl\u0131 ba\u011f\u0131ml\u0131l\u0131k konfig\u00fcrasyonlar\u0131 bulunur.
\n* tasks<\/code>:<\/strong> \u00d6zel build g\u00f6revlerini tan\u0131mlar. \u00d6rne\u011fin, bir uygulamay\u0131 \u00e7al\u0131\u015ft\u0131rmak veya \u00f6zel bir rapor olu\u015fturmak i\u00e7in g\u00f6revler yaz\u0131labilir.<\/p>\n

Temel Gradle Komutlar\u0131<\/h4>\n

Gradle CLI (Command Line Interface) \u00fczerinden bir\u00e7ok i\u015flem yap\u0131labilir:
\n* gradle build<\/code>: Projeyi derler, testleri \u00e7al\u0131\u015ft\u0131r\u0131r ve paketler.
\n* gradle clean<\/code>: Build \u00e7\u0131kt\u0131s\u0131 dizinini temizler.
\n* gradle tasks<\/code>: Projede tan\u0131ml\u0131 t\u00fcm g\u00f6revleri listeler.
\n* gradle run<\/code>: E\u011fer application<\/code> eklentisi kullan\u0131l\u0131yorsa uygulamay\u0131 \u00e7al\u0131\u015ft\u0131r\u0131r.
\n* gradle wrapper<\/code>: Projenin kendi Gradle wrapper’\u0131n\u0131 olu\u015fturur veya g\u00fcnceller. Bu, projenin belirli bir Gradle s\u00fcr\u00fcm\u00fcyle \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar ve geli\u015ftiricilerin yerel Gradle kurulumuna ihtiya\u00e7 duymadan projeyi derlemesine olanak tan\u0131r.<\/p>\n

Eclipse Temelleri<\/h3>\n

Eclipse, Java geli\u015ftirme i\u00e7in en pop\u00fcler IDE’lerden biridir. A\u00e7\u0131k kaynak kodlu olmas\u0131, geni\u015f eklenti ekosistemi ve g\u00fc\u00e7l\u00fc hata ay\u0131klama yetenekleri sayesinde milyonlarca geli\u015ftirici taraf\u0131ndan tercih edilmektedir.<\/p>\n

Eclipse IDE’ye Genel Bak\u0131\u015f<\/h4>\n

Eclipse, kod d\u00fczenleyici, derleyici, hata ay\u0131klay\u0131c\u0131 ve proje y\u00f6netim ara\u00e7lar\u0131n\u0131 tek bir \u00e7at\u0131 alt\u0131nda sunar. Workspace (\u00e7al\u0131\u015fma alan\u0131) kavram\u0131, projelerinizi d\u00fczenlemenizi ve farkl\u0131 ayarlar alt\u0131nda \u00e7al\u0131\u015fman\u0131z\u0131 sa\u011flar. Perspektifler (Perspectives), belirli bir g\u00f6rev (\u00f6rne\u011fin Java geli\u015ftirme, hata ay\u0131klama) i\u00e7in IDE’nin aray\u00fcz\u00fcn\u00fc optimize eder. G\u00f6r\u00fcn\u00fcmler (Views), projenin yap\u0131s\u0131, g\u00f6rev listesi, konsol \u00e7\u0131kt\u0131s\u0131 gibi farkl\u0131 bilgileri g\u00f6sterir.<\/p>\n

Workspace Kavram\u0131<\/h4>\n

Eclipse’te bir “workspace”, projelerinizi, ayarlar\u0131n\u0131z\u0131 ve meta verilerinizi depolad\u0131\u011f\u0131n\u0131z bir dizindir. Birden fazla workspace olu\u015fturabilir ve farkl\u0131 projeler veya farkl\u0131 m\u00fc\u015fteri projeleri i\u00e7in ayr\u0131 workspace’ler kullanabilirsiniz. Bu, ortamlar\u0131n\u0131z\u0131 izole etmenizi ve \u00e7ak\u0131\u015fmalar\u0131 \u00f6nlemenizi sa\u011flar.<\/p>\n

Java Projesi Olu\u015fturma<\/h4>\n

Eclipse’te yeni bir Java projesi olu\u015fturmak olduk\u00e7a basittir:
\n1. File -> New -> Java Project<\/code> yolunu izleyin.
\n2. Proje ad\u0131n\u0131 girin ve uygun bir JRE (Java Runtime Environment) se\u00e7in.
\n3. Finish<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\nBu i\u015flem, temel bir Java projesi yap\u0131s\u0131 (src klas\u00f6r\u00fc, JRE sistem k\u00fct\u00fcphaneleri) olu\u015fturur.<\/p>\n

Plugin Ekleme\/Y\u00f6netme<\/h4>\n

Eclipse’in g\u00fcc\u00fcn\u00fcn \u00f6nemli bir k\u0131sm\u0131, geni\u015f eklenti ekosisteminden gelir. Eklentiler, IDE’ye yeni \u00f6zellikler ve yetenekler kazand\u0131r\u0131r. Eklentileri y\u00f6netmek i\u00e7in:
\n* Eclipse Marketplace:<\/strong> Help -> Eclipse Marketplace...<\/code> yolunu izleyerek binlerce eklentiye g\u00f6z atabilir, arayabilir ve do\u011frudan kurabilirsiniz.
\n* Install New Software:<\/strong> Help -> Install New Software...<\/code> yolunu izleyerek belirli bir g\u00fcncelleme sitesinden (URL) eklenti kurabilirsiniz. Bu y\u00f6ntem, genellikle resmi eklentileri veya belirli versiyonlar\u0131 kurmak i\u00e7in kullan\u0131l\u0131r.<\/p>\n

Gradle Buildship Eklentisi Nedir?<\/h3>\n

Eclipse’in Gradle projeleriyle sorunsuz bir \u015fekilde \u00e7al\u0131\u015fabilmesi i\u00e7in \u00f6zel bir entegrasyona ihtiyac\u0131 vard\u0131r. \u0130\u015fte bu noktada Buildship devreye girer.<\/p>\n

Buildship’in Amac\u0131 ve \u00d6nemi<\/h4>\n

Buildship, Eclipse i\u00e7in resmi Gradle entegrasyon eklentisidir. Amac\u0131, geli\u015ftiricilerin Eclipse IDE i\u00e7inde Gradle projelerini rahat\u00e7a i\u00e7e aktarmas\u0131na, y\u00f6netmesine ve Gradle g\u00f6revlerini \u00e7al\u0131\u015ft\u0131rmas\u0131na olanak tan\u0131makt\u0131r. Buildship olmadan, bir Gradle projesini Eclipse’te y\u00f6netmek, manuel olarak proje yap\u0131land\u0131rmas\u0131 yapmak, classpath’leri ayarlamak ve Gradle komutlar\u0131n\u0131 harici bir terminalden \u00e7al\u0131\u015ft\u0131rmak anlam\u0131na gelirdi ki bu da olduk\u00e7a zahmetli bir s\u00fcre\u00e7tir.<\/p>\n

Eclipse i\u00e7in Resmi Gradle Entegrasyonu<\/h4>\n

Buildship, Gradle ekibi taraf\u0131ndan geli\u015ftirilir ve s\u00fcrd\u00fcr\u00fcl\u00fcr, bu da en g\u00fcncel Gradle \u00f6zellikleriyle uyumlu olmas\u0131n\u0131 sa\u011flar. Bu resmi entegrasyon, Gradle’\u0131n kendi API’lerini kullanarak Eclipse’in proje modeliyle etkile\u015fime girer ve IDE’nin Gradle projelerini “anlamas\u0131n\u0131” sa\u011flar.<\/p>\n

Sa\u011flad\u0131\u011f\u0131 Faydalar<\/h4>\n

Buildship’in sundu\u011fu temel faydalar \u015funlard\u0131r:
\n* Kolay Proje \u0130\u00e7e Aktarma:<\/strong> Mevcut Gradle projelerini birka\u00e7 t\u0131klamayla Eclipse workspace’ine aktar\u0131r.
\n* Otomatik Proje Yap\u0131land\u0131rmas\u0131:<\/strong> Gradle’\u0131n build.gradle<\/code> dosyas\u0131n\u0131 okuyarak, Eclipse projesinin kaynak klas\u00f6rlerini, \u00e7\u0131kt\u0131 dizinlerini, ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 ve di\u011fer ayarlar\u0131n\u0131 otomatik olarak yap\u0131land\u0131r\u0131r.
\n* Gradle G\u00f6revlerini \u00c7al\u0131\u015ft\u0131rma:<\/strong> Eclipse i\u00e7indeki \u00f6zel bir “Gradle Tasks” g\u00f6r\u00fcn\u00fcm\u00fc arac\u0131l\u0131\u011f\u0131yla t\u00fcm Gradle g\u00f6revlerini listeleyebilir ve \u00e7al\u0131\u015ft\u0131rabilirsiniz.
\n* Ba\u011f\u0131ml\u0131l\u0131k Y\u00f6netimi:<\/strong> Projenin ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 (JAR dosyalar\u0131) otomatik olarak indirir ve Eclipse’in build path’ine ekler. build.gradle<\/code> dosyas\u0131nda yap\u0131lan de\u011fi\u015fiklikler otomatik olarak alg\u0131lan\u0131r ve senkronize edilir.
\n* Hata Ay\u0131klama Deste\u011fi:<\/strong> Gradle g\u00f6revlerini Eclipse’in hata ay\u0131klay\u0131c\u0131s\u0131yla birlikte \u00e7al\u0131\u015ft\u0131rma yetene\u011fi sunar.
\n* \u00c7oklu Mod\u00fcll\u00fc Proje Deste\u011fi:<\/strong> Karma\u015f\u0131k, \u00e7oklu mod\u00fcll\u00fc Gradle projelerini tek bir Eclipse workspace’inde do\u011fru bir \u015fekilde y\u00f6netir.<\/p>\n

Buildship Kurulumu<\/h3>\n

Buildship eklentisini Eclipse’e kurmak olduk\u00e7a basittir ve iki ana y\u00f6ntemle yap\u0131labilir.<\/p>\n

Eclipse Marketplace \u00dczerinden Kurulum Ad\u0131mlar\u0131<\/h4>\n

Bu, Buildship’i kurman\u0131n en kolay ve \u00f6nerilen yoludur.
\n1. Eclipse’i Ba\u015flat\u0131n:<\/strong> Eclipse IDE’nizi a\u00e7\u0131n.
\n2. Marketplace’i A\u00e7\u0131n:<\/strong> \u00dcst men\u00fcden Help -> Eclipse Marketplace...<\/code> yolunu izleyin.
\n3. Arama Yap\u0131n:<\/strong> A\u00e7\u0131lan pencerede arama \u00e7ubu\u011funa “Buildship” yaz\u0131n ve arat\u0131n.
\n4. Kurulumu Ba\u015flat\u0131n:<\/strong> “Buildship Gradle Integration” eklentisini buldu\u011funuzda, yan\u0131ndaki Install<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n5. Lisans Anla\u015fmas\u0131n\u0131 Kabul Edin:<\/strong> Kurulum sihirbaz\u0131, kurmak istedi\u011finiz bile\u015fenleri ve lisans anla\u015fmas\u0131n\u0131 g\u00f6sterecektir. Confirm<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n ve ard\u0131ndan lisans anla\u015fmas\u0131n\u0131 kabul edip Finish<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n6. Eclipse’i Yeniden Ba\u015flat\u0131n:<\/strong> Kurulum tamamland\u0131ktan sonra Eclipse, de\u011fi\u015fikliklerin etkili olmas\u0131 i\u00e7in IDE’yi yeniden ba\u015flatman\u0131z\u0131 isteyecektir. Restart Now<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.<\/p>\n

Help -> Install New Software<\/code> ile Kurulum Ad\u0131mlar\u0131<\/h4>\n

E\u011fer Eclipse Marketplace’e eri\u015fimde sorun ya\u015f\u0131yorsan\u0131z veya belirli bir Buildship s\u00fcr\u00fcm\u00fcn\u00fc kurman\u0131z gerekiyorsa bu y\u00f6ntemi kullanabilirsiniz.
\n1. Eclipse’i Ba\u015flat\u0131n:<\/strong> Eclipse IDE’nizi a\u00e7\u0131n.
\n2. Kurulum Penceresini A\u00e7\u0131n:<\/strong> \u00dcst men\u00fcden Help -> Install New Software...<\/code> yolunu izleyin.
\n3. G\u00fcncelleme Sitesini Ekleyin:<\/strong> Work with:<\/code> alan\u0131n\u0131n yan\u0131ndaki Add...<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n * Name:<\/code> alan\u0131na “Buildship” veya istedi\u011finiz bir ad\u0131 girin.
\n * Location:<\/code> alan\u0131na Buildship’in g\u00fcncelleme sitesi URL’sini girin. Genellikle bu URL, Eclipse s\u00fcr\u00fcm\u00fcn\u00fcze ve Buildship s\u00fcr\u00fcm\u00fcne g\u00f6re de\u011fi\u015febilir. En g\u00fcncel Buildship i\u00e7in genellikle https:\/\/download.eclipse.org\/buildship\/update\/e429<\/code> (Eclipse 2023-09 i\u00e7in \u00f6rnek) gibi bir URL kullan\u0131l\u0131r. En do\u011fru URL’yi Buildship’in resmi GitHub sayfas\u0131ndan veya Eclipse web sitesinden kontrol edebilirsiniz.
\n * Add<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n4. Bile\u015fenleri Se\u00e7in:<\/strong> URL eklendikten sonra, Eclipse ilgili yaz\u0131l\u0131m\u0131 y\u00fckleyecektir. “Buildship Gradle Integration” alt\u0131ndaki t\u00fcm bile\u015fenleri se\u00e7in.
\n5. Kurulumu Tamamlay\u0131n:<\/strong> Next<\/code>, Next<\/code> d\u00fc\u011fmelerine t\u0131klay\u0131n, lisans anla\u015fmas\u0131n\u0131 kabul edin ve Finish<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n6. Eclipse’i Yeniden Ba\u015flat\u0131n:<\/strong> Kurulum tamamland\u0131ktan sonra Eclipse’i yeniden ba\u015flat\u0131n.<\/p>\n

Kurulumun Do\u011frulanmas\u0131<\/h4>\n

Buildship’in ba\u015far\u0131yla kurulup kurulmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in:
\n1. Eclipse’i yeniden ba\u015flatt\u0131ktan sonra, File -> Import...<\/code> yolunu izleyin.
\n2. A\u00e7\u0131lan pencerede Gradle<\/code> kategorisini g\u00f6rmelisiniz. E\u011fer Gradle<\/code> kategorisi mevcutsa, Buildship ba\u015far\u0131yla kurulmu\u015ftur.<\/p>\n

Mevcut Bir Gradle Projesini Eclipse’e Aktarma<\/h3>\n

Buildship eklentisi kurulduktan sonra, mevcut bir Gradle projesini Eclipse workspace’inize aktarmak olduk\u00e7a kolayd\u0131r. Bu, genellikle ba\u015fka bir kaynaktan (\u00f6rne\u011fin Git deposundan) klonlad\u0131\u011f\u0131n\u0131z veya daha \u00f6nce olu\u015fturdu\u011funuz bir projeyi Eclipse’te geli\u015ftirmeye devam etmek istedi\u011finizde yap\u0131l\u0131r.<\/p>\n

Ad\u0131m Ad\u0131m Rehber<\/h4>\n

A\u015fa\u011f\u0131daki ad\u0131mlar\u0131 takip ederek bir Gradle projesini Eclipse’e aktarabilirsiniz:
\n1. Eclipse’i Ba\u015flat\u0131n:<\/strong> Eclipse IDE’nizi a\u00e7\u0131n ve \u00e7al\u0131\u015ft\u0131rmak istedi\u011finiz workspace’i se\u00e7in.
\n2. \u0130\u00e7e Aktarma Sihirbaz\u0131n\u0131 A\u00e7\u0131n:<\/strong> \u00dcst men\u00fcden File -> Import...<\/code> yolunu izleyin.
\n3. Gradle Projesini Se\u00e7in:<\/strong> A\u00e7\u0131lan “Import” penceresinde, sol taraftaki listeden Gradle<\/code> kategorisini geni\u015fletin ve Existing Gradle Project<\/code> se\u00e7ene\u011fini i\u015faretleyin. Ard\u0131ndan Next<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n4. Proje K\u00f6k Dizinini Belirleyin:<\/strong> “Import Gradle Project” penceresinde:
\n * Project root directory:<\/code> alan\u0131n\u0131n yan\u0131ndaki Browse...<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n * Bilgisayar\u0131n\u0131zdaki Gradle projenizin ana dizinini (genellikle build.gradle<\/code> dosyas\u0131n\u0131n bulundu\u011fu dizin) se\u00e7in. Select Folder<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n * Se\u00e7ti\u011finiz dizin do\u011fruysa, Next<\/code> d\u00fc\u011fmesi etkinle\u015fecektir. Next<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n5. Gradle Ayarlar\u0131n\u0131 Yap\u0131land\u0131r\u0131n:<\/strong> “Import Gradle Project” penceresinin ikinci ad\u0131m\u0131nda Gradle ayarlar\u0131n\u0131 yap\u0131land\u0131rabilirsiniz:
\n * Gradle distribution:<\/strong> Genellikle Gradle wrapper<\/code> se\u00e7ene\u011fi i\u015faretli gelir. Bu, projenin kendi tan\u0131mlad\u0131\u011f\u0131 Gradle s\u00fcr\u00fcm\u00fcn\u00fc kullanmas\u0131n\u0131 sa\u011flar ve en iyi uygulamad\u0131r. E\u011fer projenizde wrapper yoksa veya belirli bir yerel Gradle kurulumunu kullanmak istiyorsan\u0131z, di\u011fer se\u00e7enekleri (Local installation<\/code> veya Specific Gradle version<\/code>) se\u00e7ebilirsiniz.
\n * JVM arguments:<\/strong> Gradle’a \u00f6zel JVM arg\u00fcmanlar\u0131 ge\u00e7irmek isterseniz buraya yazabilirsiniz.
\n * Gradle user home:<\/strong> Gradle’\u0131n \u00f6nbellek ve konfig\u00fcrasyon dosyalar\u0131n\u0131 depolad\u0131\u011f\u0131 dizini belirtir. Varsay\u0131lan de\u011fer genellikle yeterlidir.
\n * Offline mode:<\/strong> E\u011fer internet ba\u011flant\u0131n\u0131z yoksa veya ba\u011f\u0131ml\u0131l\u0131klar\u0131 \u00f6nbellekten \u00e7\u00f6zmek istiyorsan\u0131z bu se\u00e7ene\u011fi i\u015faretleyebilirsiniz.
\n * Ayarlar\u0131 g\u00f6zden ge\u00e7irdikten sonra Finish<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n6. Projenin \u0130\u00e7e Aktar\u0131lmas\u0131n\u0131 Bekleyin:<\/strong> Eclipse, Gradle projesini i\u00e7e aktarmaya ba\u015flayacakt\u0131r. Bu s\u00fcre\u00e7, projenin b\u00fcy\u00fckl\u00fc\u011f\u00fcne, ba\u011f\u0131ml\u0131l\u0131k say\u0131s\u0131na ve internet h\u0131z\u0131n\u0131za ba\u011fl\u0131 olarak biraz zaman alabilir. Eclipse, Gradle’\u0131 \u00e7al\u0131\u015ft\u0131rarak ba\u011f\u0131ml\u0131l\u0131klar\u0131 \u00e7\u00f6zecek ve projenin Eclipse projesi (.project<\/code>, .classpath<\/code> dosyalar\u0131) yap\u0131s\u0131n\u0131 olu\u015fturacakt\u0131r. \u0130\u015flem tamamland\u0131\u011f\u0131nda, projeniz “Project Explorer” g\u00f6r\u00fcn\u00fcm\u00fcnde g\u00f6r\u00fcnecektir.<\/p>\n

Proje Ayarlar\u0131n\u0131n Yap\u0131land\u0131r\u0131lmas\u0131 (JVM, Gradle S\u00fcr\u00fcm\u00fc)<\/h4>\n

\u0130\u00e7e aktarma s\u0131ras\u0131nda Buildship, projenizin build.gradle<\/code> dosyas\u0131ndaki gereksinimlere g\u00f6re otomatik olarak \u00e7o\u011fu ayar\u0131 yapar. Ancak, baz\u0131 durumlar i\u00e7in manuel kontrol gerekebilir:
\n* Java S\u00fcr\u00fcm\u00fc:<\/strong> Projeniz belirli bir Java s\u00fcr\u00fcm\u00fcn\u00fc (\u00f6rne\u011fin Java 17) gerektiriyorsa ve Eclipse’inizde birden fazla JRE\/JDK kuruluysa, projenin \u00f6zelliklerinden (sa\u011f t\u0131klama -> Properties -> Java Build Path -> Libraries -> JRE System Library<\/code>) do\u011fru JRE’yi se\u00e7ti\u011finizden emin olun. Ayr\u0131ca, build.gradle<\/code> dosyan\u0131zda sourceCompatibility<\/code> ve targetCompatibility<\/code> de\u011ferlerinin do\u011fru ayarland\u0131\u011f\u0131ndan emin olun.
\n* Gradle S\u00fcr\u00fcm\u00fc:<\/strong> gradle\/wrapper\/gradle-wrapper.properties<\/code> dosyas\u0131ndaki distributionUrl<\/code> projenizin kullanaca\u011f\u0131 Gradle s\u00fcr\u00fcm\u00fcn\u00fc belirler. Buildship genellikle bu s\u00fcr\u00fcm\u00fc otomatik olarak alg\u0131lar. E\u011fer farkl\u0131 bir s\u00fcr\u00fcmle \u00e7al\u0131\u015fmak isterseniz, bu dosyay\u0131 g\u00fcncelleyebilir veya i\u00e7e aktarma sihirbaz\u0131nda Specific Gradle version<\/code> se\u00e7ene\u011fini kullanabilirsiniz.<\/p>\n

Workspace’e Aktar\u0131m ve Proje Yap\u0131s\u0131<\/h4>\n

\u0130\u00e7e aktar\u0131lan Gradle projesi, Eclipse’in Project Explorer g\u00f6r\u00fcn\u00fcm\u00fcnde standart bir Eclipse projesi gibi g\u00f6r\u00fcnecektir. Ancak, arka planda Buildship, Gradle’\u0131n yap\u0131s\u0131n\u0131 Eclipse’in beklentilerine uygun hale getirir:
\n* Kaynak klas\u00f6rleri (src\/main\/java<\/code>, src\/main\/resources<\/code>, src\/test\/java<\/code> vb.) Eclipse’in build path’ine do\u011fru \u015fekilde eklenir.
\n* Gradle taraf\u0131ndan indirilen t\u00fcm ba\u011f\u0131ml\u0131l\u0131klar (JAR dosyalar\u0131), Eclipse’in Referenced Libraries<\/code> veya Gradle Dependencies<\/code> alt\u0131nda g\u00f6r\u00fcn\u00fcr hale gelir.
\n* Proje klas\u00f6r\u00fcnde .project<\/code>, .classpath<\/code> ve .settings<\/code> gibi Eclipse’e \u00f6zg\u00fc dosyalar olu\u015fturulur. Bu dosyalar Eclipse’in projeyi tan\u0131mas\u0131n\u0131 sa\u011flar.<\/p>\n

\u00d6rnek build.gradle<\/code> Dosyas\u0131 ile Basit Bir Java Projesi<\/h4>\n

Diyelim ki a\u015fa\u011f\u0131daki gibi basit bir build.gradle<\/code> dosyan\u0131z var:<\/p>\n

plugins {\n    id 'java'\n    id 'application' \/\/ Uygulamay\u0131 \u00e7al\u0131\u015ft\u0131rmak i\u00e7in\n}\n\ngroup 'com.example'\nversion '1.0-SNAPSHOT'\n\nrepositories {\n    mavenCentral()\n}\n\ndependencies {\n    implementation 'com.google.guava:guava:31.1-jre'\n    testImplementation 'org.junit.jupiter:junit-jupiter-api:5.10.0'\n    testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.10.0'\n}\n\napplication {\n    mainClass = 'com.example.App'\n}\n\ntest {\n    useJUnitPlatform()\n}<\/code><\/pre>\n
Ve src\/main\/java\/com\/example\/App.java<\/code> i\u00e7inde basit bir main<\/code> metodu:<\/p>\n
package com.example;\n\nimport com.google.common.collect.Lists;\nimport java.util.List;\n\npublic class App {\n    public static void main(String[] args) {\n        List names = Lists.newArrayList(\"Alice\", \"Bob\", \"Charlie\");\n        System.out.println(\"Hello Gradle World with Guava!\");\n        names.forEach(System.out::println);\n    }\n}<\/code><\/pre>\n
Bu projeyi yukar\u0131daki ad\u0131mlar\u0131 izleyerek Eclipse’e aktard\u0131\u011f\u0131n\u0131zda, Buildship guava<\/code> ve JUnit ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 otomatik olarak indirecek ve Eclipse’in build path’ine ekleyecektir. App.java<\/code> dosyas\u0131ndaki kod tamamlama (code completion) \u00f6zelli\u011fi, Guava k\u00fct\u00fcphanesini tan\u0131yacak ve hatas\u0131z bir \u015fekilde \u00e7al\u0131\u015facakt\u0131r.<\/p>\n
Yeni Bir Gradle Projesi Olu\u015fturma ve Eclipse’e Aktarma<\/h3>\n
Bazen mevcut bir projeyi i\u00e7e aktarmak yerine, s\u0131f\u0131rdan yeni bir Gradle projesi olu\u015fturup hemen Eclipse’te \u00e7al\u0131\u015fmaya ba\u015flamak isteyebilirsiniz. Buildship bu senaryoyu da destekler.<\/p>\n
Gradle Komut Sat\u0131r\u0131 ile Yeni Proje Olu\u015fturma (gradle init<\/code>)<\/h4>\n
Yeni bir Gradle projesi olu\u015fturman\u0131n en yayg\u0131n yolu, Gradle CLI kullanmakt\u0131r.
\n1.  Terminali A\u00e7\u0131n:<\/strong> Komut istemcisini veya terminali a\u00e7\u0131n.
\n2.  Proje Dizinine Gidin:<\/strong> Yeni projenizi olu\u015fturmak istedi\u011finiz \u00fcst dizine gidin (\u00f6rne\u011fin, cd \/Users\/kullanici\/projeler<\/code>).
\n3.  Gradle Init Komutunu \u00c7al\u0131\u015ft\u0131r\u0131n:<\/strong> A\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n
gradle init<\/code><\/pre>\n
    Bu komut, size birka\u00e7 soru soracakt\u0131r:
\n    *   Select type of project to generate:<\/strong> Genellikle application<\/code> (uygulama) veya library<\/code> (k\u00fct\u00fcphane) se\u00e7ilir. \u00d6rne\u011fin, 2: application<\/code> se\u00e7ene\u011fini se\u00e7in.
\n    *   Select implementation language:<\/strong> Projenizin ana dilini se\u00e7in. \u00d6rne\u011fin, 2: Java<\/code> se\u00e7ene\u011fini se\u00e7in.
\n    *   Select build script DSL:<\/strong> 1: Groovy<\/code> veya 2: Kotlin<\/code> se\u00e7ene\u011fini se\u00e7in. Bu rehberde Groovy ile devam edelim, 1: Groovy<\/code> se\u00e7in.
\n    *   Select test framework:<\/strong> 3: JUnit Jupiter<\/code> se\u00e7ene\u011fini se\u00e7in.
\n    *   Project name:<\/strong> Proje ad\u0131n\u0131 girin (\u00f6rn. MyNewGradleApp<\/code>).
\n    *   Source package:<\/strong> Ana paketinizi girin (\u00f6rn. com.example.app<\/code>).
\n    Bu sorular\u0131 yan\u0131tlad\u0131ktan sonra Gradle, projenizin temel iskeletini olu\u015fturacakt\u0131r.<\/p>\n
Olu\u015fan Projenin Yap\u0131s\u0131<\/h4>\n
gradle init<\/code> komutu \u00e7al\u0131\u015ft\u0131ktan sonra, belirtilen proje ad\u0131yla yeni bir dizin olu\u015facakt\u0131r (\u00f6rn. MyNewGradleApp<\/code>). Bu dizinin i\u00e7inde standart bir Gradle projesi yap\u0131s\u0131 bulacaks\u0131n\u0131z:
\n*   build.gradle<\/code>: Projenin build script dosyas\u0131.
\n*   settings.gradle<\/code>: \u00c7oklu projelerde mod\u00fclleri tan\u0131mlamak i\u00e7in kullan\u0131l\u0131r. Basit projelerde sadece proje ad\u0131n\u0131 i\u00e7erir.
\n*   gradlew<\/code>, gradlew.bat<\/code>: Gradle wrapper scriptleri.
\n*   gradle\/wrapper<\/code>: Gradle wrapper’\u0131n kendisi.
\n*   src\/main\/java<\/code>: Ana Java kaynak kodlar\u0131.
\n*   src\/test\/java<\/code>: Test Java kaynak kodlar\u0131.
\n*   src\/main\/resources<\/code>: Ana kaynak dosyalar\u0131 (properties, XML vb.).
\n*   src\/test\/resources<\/code>: Test kaynak dosyalar\u0131.<\/p>\n
Bu Projeyi Buildship Kullanarak Eclipse’e Aktarma<\/h4>\n
Yeni olu\u015fturdu\u011funuz bu Gradle projesini Eclipse’e aktarmak, mevcut bir projeyi aktarmakla neredeyse ayn\u0131d\u0131r:
\n1.  Eclipse’i Ba\u015flat\u0131n.<\/strong>
\n2.  \u0130\u00e7e Aktarma Sihirbaz\u0131n\u0131 A\u00e7\u0131n:<\/strong> File -> Import...<\/code> yolunu izleyin.
\n3.  Gradle Projesini Se\u00e7in:<\/strong> Gradle -> Existing Gradle Project<\/code> se\u00e7ene\u011fini i\u015faretleyin ve Next<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n4.  Proje K\u00f6k Dizinini Belirleyin:<\/strong> Project root directory:<\/code> alan\u0131nda, az \u00f6nce gradle init<\/code> ile olu\u015fturdu\u011funuz projenin ana dizinini se\u00e7in (\u00f6rn. MyNewGradleApp<\/code>). Next<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n5.  Gradle Ayarlar\u0131n\u0131 Yap\u0131land\u0131r\u0131n:<\/strong> Ayarlar\u0131 g\u00f6zden ge\u00e7irin ve Finish<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\nEclipse, yeni olu\u015fturdu\u011funuz Gradle projesini i\u00e7e aktaracak ve Project Explorer’da g\u00f6sterecektir. Art\u0131k Eclipse i\u00e7inde kod yazmaya, derlemeye ve hata ay\u0131klamaya ba\u015flayabilirsiniz.<\/p>\n
Eclipse \u0130\u00e7inde Gradle Projeleriyle \u00c7al\u0131\u015fma<\/h3>\n
Buildship eklentisi sayesinde Eclipse, Gradle projeleriyle do\u011fal bir entegrasyon sunar. Bu entegrasyon, geli\u015ftirme s\u00fcrecini \u00f6nemli \u00f6l\u00e7\u00fcde kolayla\u015ft\u0131r\u0131r.<\/p>\n
Gradle Tasks View<\/h4>\n
Buildship’in en kullan\u0131\u015fl\u0131 \u00f6zelliklerinden biri “Gradle Tasks” g\u00f6r\u00fcn\u00fcm\u00fcd\u00fcr. Bu g\u00f6r\u00fcn\u00fcm, projenizde tan\u0131ml\u0131 t\u00fcm Gradle g\u00f6revlerini (task’lar\u0131) listeler ve bunlar\u0131 do\u011frudan Eclipse i\u00e7inden \u00e7al\u0131\u015ft\u0131rman\u0131za olanak tan\u0131r.
\n1.  G\u00f6r\u00fcn\u00fcm\u00fc A\u00e7\u0131n:<\/strong> Window -> Show View -> Other...<\/code> yolunu izleyin. A\u00e7\u0131lan pencerede Gradle<\/code> kategorisini geni\u015fletin ve Gradle Tasks<\/code> se\u00e7ene\u011fini se\u00e7ip Open<\/code> d\u00fc\u011fmesine t\u0131klay\u0131n.
\n2.  G\u00f6revleri G\u00f6r\u00fcnt\u00fcleyin:<\/strong> Gradle Tasks g\u00f6r\u00fcn\u00fcm\u00fc, workspace’inizdeki t\u00fcm Gradle projelerini listeler. Her projenin alt\u0131nda, build<\/code>, clean<\/code>, test<\/code>, run<\/code> gibi standart g\u00f6revler ve build.gradle<\/code> dosyan\u0131zda tan\u0131mlad\u0131\u011f\u0131n\u0131z \u00f6zel g\u00f6revler kategoriler halinde listelenir.
\n3.  G\u00f6revleri \u00c7al\u0131\u015ft\u0131r\u0131n:<\/strong> Bir g\u00f6revi \u00e7al\u0131\u015ft\u0131rmak i\u00e7in, listeden g\u00f6revi bulun ve \u00e7ift t\u0131klay\u0131n veya sa\u011f t\u0131klay\u0131p Run Gradle Task<\/code> se\u00e7ene\u011fini se\u00e7in. G\u00f6revin \u00e7\u0131kt\u0131s\u0131 Eclipse’in “Console” g\u00f6r\u00fcn\u00fcm\u00fcnde g\u00f6r\u00fcnt\u00fclenecektir.
\n4.  G\u00f6revleri Hata Ay\u0131klay\u0131n:<\/strong> Bir g\u00f6revi hata ay\u0131klama modunda \u00e7al\u0131\u015ft\u0131rmak i\u00e7in g\u00f6reve sa\u011f t\u0131klay\u0131n ve Debug Gradle Task<\/code> se\u00e7ene\u011fini se\u00e7in. Bu, Eclipse’in hata ay\u0131klay\u0131c\u0131s\u0131n\u0131 Gradle g\u00f6reviyle birlikte ba\u015flat\u0131r.<\/p>\n
Gradle Dependencies<\/h4>\n
Buildship, projenizin build.gradle<\/code> dosyas\u0131nda tan\u0131mlanan t\u00fcm ba\u011f\u0131ml\u0131l\u0131klar\u0131 otomatik olarak y\u00f6netir.
\n*   G\u00f6r\u00fcnt\u00fcleme:<\/strong> Project Explorer’da projenizi geni\u015fletti\u011finizde, Gradle Dependencies<\/code> adl\u0131 bir giri\u015f g\u00f6receksiniz. Bu giri\u015fi geni\u015fleterek projenizin t\u00fcm harici ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 (JAR dosyalar\u0131) ve bunlar\u0131n versiyonlar\u0131n\u0131 g\u00f6rebilirsiniz.
\n*   Otomatik Y\u00f6netim:<\/strong> build.gradle<\/code> dosyan\u0131zda bir ba\u011f\u0131ml\u0131l\u0131k ekledi\u011finizde, de\u011fi\u015ftirdi\u011finizde veya kald\u0131rd\u0131\u011f\u0131n\u0131zda, Buildship bu de\u011fi\u015fikli\u011fi otomatik olarak alg\u0131lar. Proje \u00fczerinde sa\u011f t\u0131klay\u0131p Gradle -> Refresh Gradle Project<\/code> se\u00e7ene\u011fini se\u00e7erek de manuel olarak senkronizasyonu tetikleyebilirsiniz. Bu i\u015flem, gerekli JAR dosyalar\u0131n\u0131 indirir ve Eclipse’in build path’ini g\u00fcnceller.<\/p>\n
Otomatik Senkronizasyon<\/h4>\n
Buildship’in en b\u00fcy\u00fck kolayl\u0131klar\u0131ndan biri, build.gradle<\/code> dosyas\u0131nda yap\u0131lan de\u011fi\u015fikliklerin otomatik olarak alg\u0131lanmas\u0131 ve Eclipse projesinin buna g\u00f6re g\u00fcncellenmesidir.
\n*   build.gradle<\/code> dosyas\u0131n\u0131 kaydetti\u011finizde, Buildship genellikle arka planda Gradle’\u0131 \u00e7al\u0131\u015ft\u0131r\u0131r ve projenin ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131, kaynak klas\u00f6rlerini vb. otomatik olarak senkronize eder.
\n*   E\u011fer otomatik senkronizasyon \u00e7al\u0131\u015fmazsa veya de\u011fi\u015fikliklerin hemen yans\u0131mas\u0131n\u0131 istiyorsan\u0131z, Project Explorer’da projenize sa\u011f t\u0131klay\u0131p Gradle -> Refresh Gradle Project<\/code> se\u00e7ene\u011fini kullanabilirsiniz. Bu, Gradle’\u0131 yeniden \u00e7al\u0131\u015ft\u0131r\u0131r ve Eclipse projesini g\u00fcncel build tan\u0131m\u0131na g\u00f6re yeniden yap\u0131land\u0131r\u0131r.<\/p>\n
Run\/Debug Konfig\u00fcrasyonlar\u0131<\/h4>\n
Gradle g\u00f6revlerini do\u011frudan Eclipse i\u00e7inden \u00e7al\u0131\u015ft\u0131rmak veya hata ay\u0131klamak i\u00e7in \u00f6zel “Run Configurations” veya “Debug Configurations” olu\u015fturabilirsiniz.
\n1.  Konfig\u00fcrasyon Olu\u015fturma:<\/strong> Run -> Run Configurations...<\/code> veya Run -> Debug Configurations...<\/code> yolunu izleyin.
\n2.  Gradle Task’\u0131 Se\u00e7in:<\/strong> Sol taraftaki listeden Gradle Task<\/code> se\u00e7ene\u011fine \u00e7ift t\u0131klay\u0131n.
\n3.  Ayarlar\u0131 Yap\u0131land\u0131r\u0131n:<\/strong>
\n    *   Name:<\/code> Konfig\u00fcrasyonunuza bir ad verin.
\n    *   Gradle Project:<\/code> \u00c7al\u0131\u015ft\u0131rmak istedi\u011finiz Gradle projesini se\u00e7in.
\n    *   Gradle Tasks:<\/code> \u00c7al\u0131\u015ft\u0131rmak istedi\u011finiz Gradle g\u00f6revlerini buraya yaz\u0131n (\u00f6rn. clean build<\/code>). Birden fazla g\u00f6rev virg\u00fclle ayr\u0131labilir.
\n    *   Arguments:<\/code> G\u00f6revlere ge\u00e7irmek istedi\u011finiz ek arg\u00fcmanlar\u0131 yaz\u0131n.
\n    *   JRE:<\/code> G\u00f6revin \u00e7al\u0131\u015faca\u011f\u0131 JRE’yi se\u00e7in.
\n4.  \u00c7al\u0131\u015ft\u0131r\u0131n\/Hata Ay\u0131klay\u0131n:<\/strong> Konfig\u00fcrasyonu kaydettikten sonra, Run<\/code> veya Debug<\/code> d\u00fc\u011fmesine t\u0131klayarak g\u00f6revi \u00e7al\u0131\u015ft\u0131rabilirsiniz.<\/p>\n
Code Completion ve Navigasyon<\/h4>\n
Buildship, Gradle projeleri i\u00e7in Eclipse’in zengin IDE \u00f6zelliklerinden tam olarak faydalanman\u0131z\u0131 sa\u011flar:
\n*   Code Completion:<\/strong> build.gradle<\/code> dosyas\u0131nda (\u00f6zellikle Kotlin DSL kullan\u0131rken) veya Java\/Kotlin kaynak dosyalar\u0131nda ba\u011f\u0131ml\u0131l\u0131klar ve Gradle API’leri i\u00e7in ak\u0131ll\u0131 kod tamamlama \u00f6zelli\u011fi sunar.
\n*   Navigasyon:<\/strong> Projenizdeki s\u0131n\u0131flar, metodlar ve ba\u011f\u0131ml\u0131l\u0131klar aras\u0131nda h\u0131zl\u0131ca gezinmenizi sa\u011flar (Ctrl + Click<\/code> veya F3<\/code>).
\n*   Refactoring:<\/strong> Yeniden d\u00fczenleme (refactoring) i\u015flemleri, Gradle projenizin yap\u0131s\u0131n\u0131 bozmadan sorunsuz bir \u015fekilde \u00e7al\u0131\u015f\u0131r.<\/p>\n
S\u0131k Kar\u015f\u0131la\u015f\u0131lan Sorunlar ve \u00c7\u00f6z\u00fcmleri<\/h3>\n
Gradle ve Eclipse entegrasyonu genellikle sorunsuz \u00e7al\u0131\u015fsa da, bazen beklenmedik durumlarla kar\u015f\u0131la\u015f\u0131labilir. \u0130\u015fte baz\u0131 yayg\u0131n sorunlar ve \u00e7\u00f6z\u00fcm \u00f6nerileri:<\/p>\n
Gradle S\u00fcr\u00fcm\u00fc Uyumsuzluklar\u0131<\/h4>\n
*   Sorun:<\/strong> Eclipse’in kulland\u0131\u011f\u0131 Buildship s\u00fcr\u00fcm\u00fc ile projenizin gradle-wrapper.properties<\/code> dosyas\u0131nda belirtilen Gradle s\u00fcr\u00fcm\u00fc aras\u0131nda uyumsuzluklar olabilir. Bu, derleme hatalar\u0131na veya projenin i\u00e7e aktar\u0131lamamas\u0131na neden olabilir.
\n*   \u00c7\u00f6z\u00fcm:<\/strong>
\n    *   Eclipse’teki Buildship eklentisinin en g\u00fcncel s\u00fcr\u00fcm\u00fcn\u00fc kulland\u0131\u011f\u0131n\u0131zdan emin olun (Help -> Check for Updates<\/code>).
\n    *   Projenizin gradle\/wrapper\/gradle-wrapper.properties<\/code> dosyas\u0131ndaki distributionUrl<\/code> de\u011ferini kontrol edin ve desteklenen bir Gradle s\u00fcr\u00fcm\u00fcn\u00fc kulland\u0131\u011f\u0131ndan emin olun. Gerekirse bu URL’yi g\u00fcncelleyerek daha yeni veya daha kararl\u0131 bir Gradle s\u00fcr\u00fcm\u00fcne ge\u00e7in.
\n    *   Project -> Clean...<\/code> ve ard\u0131ndan Gradle -> Refresh Gradle Project<\/code> ad\u0131mlar\u0131n\u0131 uygulay\u0131n.<\/p>\n
Proxy Ayarlar\u0131<\/h4>\n
*   Sorun:<\/strong> Kurumsal bir a\u011fda veya proxy sunucusu arkas\u0131nda \u00e7al\u0131\u015f\u0131rken Gradle, ba\u011f\u0131ml\u0131l\u0131klar\u0131 indiremeyebilir.
\n*   \u00c7\u00f6z\u00fcm:<\/strong>
\n    *   Eclipse’in proxy ayarlar\u0131n\u0131 yap\u0131land\u0131r\u0131n: Window -> Preferences -> General -> Network Connections<\/code>. Active Provider<\/code> olarak Manual<\/code> se\u00e7ene\u011fini se\u00e7in ve HTTP\/HTTPS proxy ayarlar\u0131n\u0131z\u0131 girin.
\n    *   Gradle’\u0131n kendi proxy ayarlar\u0131n\u0131 yap\u0131land\u0131r\u0131n. GRADLE_USER_HOME<\/code> dizininizde (~\/.gradle\/<\/code> veya C:\\Users\\Kullan\u0131c\u0131\\.gradle\\<\/code>) gradle.properties<\/code> adl\u0131 bir dosya olu\u015fturun veya mevcutsa d\u00fczenleyin ve a\u015fa\u011f\u0131daki sat\u0131rlar\u0131 ekleyin (kendi proxy bilgilerinizle):<\/p>\n
systemProp.http.proxyHost=proxy.example.com\n        systemProp.http.proxyPort=8080\n        systemProp.http.proxyUser=your_username\n        systemProp.http.proxyPassword=your_password\n        systemProp.http.nonProxyHosts=localhost|127.0.0.1\n        systemProp.https.proxyHost=proxy.example.com\n        systemProp.https.proxyPort=8080\n        systemProp.https.proxyUser=your_username\n        systemProp.https.proxyPassword=your_password\n        systemProp.https.nonProxyHosts=localhost|127.0.0.1<\/code><\/pre>\n
    *   Eclipse’i yeniden ba\u015flat\u0131n ve projeyi yenileyin (Gradle -> Refresh Gradle Project<\/code>).<\/p>\n
Workspace Sorunlar\u0131<\/h4>\n
*   Sorun:<\/strong> Workspace’in bozulmas\u0131 veya eski meta verilerin \u00e7ak\u0131\u015fmas\u0131, projenin i\u00e7e aktar\u0131lmas\u0131n\u0131 veya do\u011fru \u00e7al\u0131\u015fmas\u0131n\u0131 engelleyebilir.
\n*   \u00c7\u00f6z\u00fcm:<\/strong>
\n    *   \u00d6ncelikle Project -> Clean...<\/code> ile projeyi temizleyin.
\n    *   Gradle -> Refresh Gradle Project<\/code> ile Gradle entegrasyonunu yenileyin.
\n    *   E\u011fer sorun devam ederse, Eclipse’i kapat\u0131n, workspace dizininizdeki .metadata<\/code> klas\u00f6r\u00fcn\u00fc yedekleyip silin ve Eclipse’i yeni bir workspace ile ba\u015flatmay\u0131 deneyin. Bu, t\u00fcm ayarlar\u0131n\u0131z\u0131 s\u0131f\u0131rlayacakt\u0131r, bu nedenle dikkatli olun.<\/p>\n
Buildpath Hatalar\u0131<\/h4>\n
*   Sorun:<\/strong> Referenced Libraries<\/code> veya Gradle Dependencies<\/code> alt\u0131nda ba\u011f\u0131ml\u0131l\u0131klar eksik g\u00f6r\u00fcn\u00fcyor veya “Unresolved compilation problem” hatalar\u0131 al\u0131yorsunuz.
\n*   \u00c7\u00f6z\u00fcm:<\/strong>
\n    *   build.gradle<\/code> dosyan\u0131zdaki ba\u011f\u0131ml\u0131l\u0131k tan\u0131mlar\u0131n\u0131n do\u011fru oldu\u011fundan emin olun (do\u011fru grup, artefakt, versiyon).
\n    *   Projenize sa\u011f t\u0131klay\u0131n ve Gradle -> Refresh Gradle Project<\/code> se\u00e7ene\u011fini se\u00e7in. Bu, Gradle’\u0131n ba\u011f\u0131ml\u0131l\u0131klar\u0131 yeniden indirmesini ve Eclipse’in build path’ini g\u00fcncellemesini sa\u011flar.
\n    *   E\u011fer sorun hala devam ediyorsa, Gradle \u00f6nbelle\u011fini temizlemeyi deneyebilirsiniz. Terminalde projenizin k\u00f6k dizininde gradle clean<\/code> ve ard\u0131ndan gradle build<\/code> komutlar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n. Sonra Eclipse’te projeyi tekrar yenileyin.
\n    *   Bazen Eclipse’in dahili \u00f6nbelle\u011fi bozulabilir. Project -> Clean...<\/code> se\u00e7ene\u011fini kullan\u0131n ve ard\u0131ndan Eclipse’i yeniden ba\u015flat\u0131n.<\/p>\n
\u00c7\u00f6z\u00fcm \u00d6nerileri (Genel Yakla\u015f\u0131m)<\/h4>\n
Bir sorunla kar\u015f\u0131la\u015ft\u0131\u011f\u0131n\u0131zda izleyebilece\u011finiz genel ad\u0131mlar \u015funlard\u0131r:
\n1.  Konsolu Kontrol Edin:<\/strong> Eclipse’in “Console” g\u00f6r\u00fcn\u00fcm\u00fcnde veya terminalde Gradle \u00e7\u0131kt\u0131s\u0131n\u0131 dikkatlice inceleyin. Hata mesajlar\u0131 genellikle sorunun k\u00f6k nedenini a\u00e7\u0131klar.
\n2.  Gradle Projesini Yenileyin:<\/strong> Projenize sa\u011f t\u0131klay\u0131n ve Gradle -> Refresh Gradle Project<\/code> se\u00e7ene\u011fini se\u00e7in. Bu, Buildship’in Gradle ile senkronize olmas\u0131n\u0131 sa\u011flar.
\n3.  Projeyi Temizleyin:<\/strong> Project -> Clean...<\/code> yolunu izleyerek projenin derlenmi\u015f \u00e7\u0131kt\u0131lar\u0131n\u0131 temizleyin.
\n4.  Eclipse’i Yeniden Ba\u015flat\u0131n:<\/strong> Bazen basit bir IDE yeniden ba\u015flatmas\u0131, ge\u00e7ici sorunlar\u0131 \u00e7\u00f6zebilir.
\n5.  Gradle \u00d6nbelle\u011fini Temizleyin:<\/strong> Terminalde gradle cleanBuildCache<\/code> veya rm -rf ~\/.gradle\/caches\/<\/code> komutlar\u0131n\u0131 kullanarak Gradle’\u0131n \u00f6nbelle\u011fini temizlemeyi deneyin (dikkatli olun, bu t\u00fcm Gradle \u00f6nbelle\u011fini siler). Ard\u0131ndan projeyi Eclipse’te yenileyin.
\n6.  Buildship S\u00fcr\u00fcm\u00fcn\u00fc Kontrol Edin:<\/strong> En g\u00fcncel Buildship s\u00fcr\u00fcm\u00fcn\u00fc kulland\u0131\u011f\u0131n\u0131zdan emin olun.
\n7.  Gradle Wrapper S\u00fcr\u00fcm\u00fcn\u00fc Kontrol Edin:<\/strong> gradle\/wrapper\/gradle-wrapper.properties<\/code> dosyas\u0131ndaki Gradle s\u00fcr\u00fcm\u00fcn\u00fcn g\u00fcncel ve desteklenen bir s\u00fcr\u00fcm oldu\u011fundan emin olun.<\/p>\n
\u0130leri Seviye Konular<\/h3>\n
Gradle ve Eclipse entegrasyonu, temel proje y\u00f6netiminin \u00f6tesinde daha karma\u015f\u0131k senaryolar i\u00e7in de g\u00fc\u00e7l\u00fc yetenekler sunar.<\/p>\n
\u00c7oklu Mod\u00fcll\u00fc Gradle Projeleri ve Eclipse’e Aktar\u0131m\u0131<\/h4>\n
B\u00fcy\u00fck uygulamalar genellikle birden fazla mod\u00fcle ayr\u0131l\u0131r (\u00f6rne\u011fin, core<\/code>, web<\/code>, api<\/code>). Gradle, bu t\u00fcr \u00e7oklu mod\u00fcll\u00fc (multi-module) projeleri settings.gradle<\/code> dosyas\u0131 arac\u0131l\u0131\u011f\u0131yla y\u00f6netir.
\n*   settings.gradle<\/code>:<\/strong> Bu dosya, ana projenin hangi alt mod\u00fclleri i\u00e7erdi\u011fini tan\u0131mlar. \u00d6rne\u011fin:<\/p>\n
rootProject.name = 'my-multi-module-app'\n    include 'core', 'web', 'api'<\/code><\/pre>\n
*   Eclipse’e Aktar\u0131m:<\/strong> \u00c7oklu mod\u00fcll\u00fc bir Gradle projesini Eclipse’e aktar\u0131rken, ana projenin k\u00f6k dizinini se\u00e7meniz yeterlidir. Buildship, settings.gradle<\/code> dosyas\u0131n\u0131 otomatik olarak okuyacak ve her bir alt mod\u00fcl\u00fc Eclipse’te ayr\u0131 bir proje olarak i\u00e7e aktaracakt\u0131r. Bu, her mod\u00fcl i\u00e7in ayr\u0131 bir Eclipse projesi olu\u015fturulmas\u0131n\u0131 sa\u011flar, ancak hepsi ayn\u0131 workspace’te ve ana projenin alt\u0131nda grupland\u0131r\u0131lm\u0131\u015f olarak g\u00f6r\u00fcn\u00fcr. Mod\u00fcller aras\u0131 ba\u011f\u0131ml\u0131l\u0131klar (\u00f6rne\u011fin web<\/code> mod\u00fcl\u00fcn\u00fcn core<\/code> mod\u00fcl\u00fcne ba\u011f\u0131ml\u0131l\u0131\u011f\u0131) Eclipse’in build path’inde otomatik olarak yap\u0131land\u0131r\u0131l\u0131r.<\/p>\n
Eclipse WTP (Web Tools Platform) ile Web Projeleri Entegrasyonu<\/h4>\n
E\u011fer Gradle ile bir web uygulamas\u0131 (\u00f6rne\u011fin Spring Boot, Vaadin) geli\u015ftiriyorsan\u0131z, Eclipse WTP (Web Tools Platform) eklentileriyle Buildship entegrasyonu \u00f6nemlidir.
\n*   WTP Kurulumu:<\/strong> Eclipse’in genellikle “Eclipse IDE for Enterprise Java and Web Developers” paketi WTP’yi i\u00e7erir. E\u011fer manuel kurman\u0131z gerekirse, Help -> Install New Software<\/code> \u00fczerinden WTP eklentilerini kurabilirsiniz.
\n*   Gradle WTP Eklentisi:<\/strong> Gradle projelerinizde genellikle war<\/code> veya org.gretty<\/code> gibi web eklentileri kullan\u0131l\u0131r. Buildship, bu eklentileri alg\u0131layarak Eclipse projenizi otomatik olarak bir “Web Project” olarak yap\u0131land\u0131r\u0131r. Bu sayede, sunucu adapt\u00f6rleri (Tomcat, Jetty vb.) ile entegrasyon, web kayna\u011f\u0131 klas\u00f6rlerinin do\u011fru tan\u0131mlanmas\u0131 ve web da\u011f\u0131t\u0131m descriptor’lar\u0131n\u0131n y\u00f6netimi kolayla\u015f\u0131r.
\n*   Sunucuya Da\u011f\u0131t\u0131m:<\/strong> Buildship ile i\u00e7e aktar\u0131lan bir web projesini, Eclipse’in “Servers” g\u00f6r\u00fcn\u00fcm\u00fc arac\u0131l\u0131\u011f\u0131yla bir uygulama sunucusuna (\u00f6rne\u011fin Tomcat) kolayca da\u011f\u0131tabilir ve \u00e7al\u0131\u015ft\u0131rabilirsiniz.<\/p>\n
\u00d6zel Gradle G\u00f6revleri ve Eclipse Entegrasyonu<\/h4>\n
Gradle’\u0131n en g\u00fc\u00e7l\u00fc yanlar\u0131ndan biri, \u00f6zel g\u00f6revler (custom tasks) tan\u0131mlayabilme yetene\u011fidir. Bu g\u00f6revler, projenize \u00f6zg\u00fc otomasyon ihtiya\u00e7lar\u0131n\u0131 kar\u015f\u0131lamak i\u00e7in yaz\u0131labilir (\u00f6rne\u011fin, veritaban\u0131 \u015femas\u0131n\u0131 g\u00fcncellemek, \u00f6zel bir rapor olu\u015fturmak, bir deploy script’i \u00e7al\u0131\u015ft\u0131rmak).
\n*   \u00d6zel G\u00f6rev Tan\u0131mlama:<\/strong> build.gradle<\/code> dosyan\u0131zda basit bir g\u00f6rev tan\u0131mlayabilirsiniz:<\/p>\n
task hello {\n        doLast {\n            println 'Hello from a custom Gradle task!'\n        }\n    }<\/code><\/pre>\n
*   Eclipse’te \u00c7al\u0131\u015ft\u0131rma:<\/strong> Bu g\u00f6revi tan\u0131mlad\u0131ktan sonra, Eclipse’in Gradle Tasks<\/code> g\u00f6r\u00fcn\u00fcm\u00fcn\u00fc yeniledi\u011finizde (sa\u011f t\u0131klama -> Refresh<\/code>), hello<\/code> g\u00f6revi listede g\u00f6r\u00fcnecektir. T\u0131pk\u0131 di\u011fer Gradle g\u00f6revleri gibi, bu \u00f6zel g\u00f6revi de \u00e7ift t\u0131klayarak veya sa\u011f t\u0131klay\u0131p Run Gradle Task<\/code> se\u00e7ene\u011fini se\u00e7erek do\u011frudan Eclipse i\u00e7inden \u00e7al\u0131\u015ft\u0131rabilirsiniz. Bu, geli\u015ftiricilerin IDE’den ayr\u0131lmadan t\u00fcm proje otomasyonunu y\u00f6netmesini sa\u011flar.<\/p>\n
Sonu\u00e7<\/h3>\n
Gradle ve Eclipse entegrasyonu, modern Java geli\u015ftirme s\u00fcre\u00e7leri i\u00e7in vazge\u00e7ilmez bir ara\u00e7 kombinasyonudur. Bu makale boyunca, Gradle’\u0131n esnek ve g\u00fc\u00e7l\u00fc build otomasyon yeteneklerini, Eclipse’in zengin IDE \u00f6zellikleriyle birle\u015ftirmenin ne kadar kolay ve verimli oldu\u011funu detayl\u0131 bir \u015fekilde inceledik.<\/p>\n
Buildship eklentisi sayesinde, geli\u015ftiriciler mevcut Gradle projelerini sorunsuz bir \u015fekilde Eclipse’e aktarabilir, yeni projeler olu\u015fturabilir ve Gradle’\u0131n t\u00fcm g\u00fcc\u00fcn\u00fc IDE’nin konforunda kullanabilirler. Otomatik proje yap\u0131land\u0131rmas\u0131, ba\u011f\u0131ml\u0131l\u0131k y\u00f6netimi, Gradle g\u00f6revlerini do\u011frudan Eclipse i\u00e7inden \u00e7al\u0131\u015ft\u0131rma ve hata ay\u0131klama gibi \u00f6zellikler, geli\u015ftiricilerin zaman kazanmas\u0131n\u0131, hatalar\u0131 azaltmas\u0131n\u0131 ve genel \u00fcretkenli\u011fi art\u0131rmas\u0131n\u0131 sa\u011flar.<\/p>\n
Kar\u015f\u0131la\u015f\u0131labilecek olas\u0131 sorunlara y\u00f6nelik \u00e7\u00f6z\u00fcmler ve ileri seviye kullan\u0131m senaryolar\u0131 (\u00e7oklu mod\u00fcll\u00fc projeler, web entegrasyonu, \u00f6zel g\u00f6revler) da bu rehberin kapsam\u0131na al\u0131narak, geli\u015ftiricilerin her t\u00fcrl\u00fc Gradle tabanl\u0131 projeyi Eclipse ortam\u0131nda ba\u015far\u0131yla y\u00f6netebilmeleri i\u00e7in gerekli bilgi birikimi sunulmu\u015ftur.<\/p>\n
\u00d6zetle, Gradle’\u0131n modern build sistemi yakla\u015f\u0131m\u0131 ile Eclipse’in kapsaml\u0131 geli\u015ftirme ortam\u0131n\u0131n birle\u015fimi, geli\u015ftirme s\u00fcrecini daha h\u0131zl\u0131, daha g\u00fcvenilir ve daha keyifli hale getirir. Bu entegrasyonu benimseyen ekipler ve bireysel geli\u015ftiriciler, projelerini daha etkin bir \u015fekilde y\u00f6netebilir ve kaliteli yaz\u0131l\u0131mlar\u0131 daha h\u0131zl\u0131 bir \u015fekilde piyasaya s\u00fcrebilirler. Gelecekte de Gradle ve Eclipse entegrasyonunun, s\u00fcrekli geli\u015fen yaz\u0131l\u0131m ekosisteminde \u00f6nemli bir rol oynamaya devam edece\u011fi a\u00e7\u0131kt\u0131r.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber\nGiri\u015f\nModern yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde, projelerin derlenmesi, test edilmesi, ba\u011f\u0131","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-34626","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nGradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber\" \/>\n<meta property=\"og:description\" content=\"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber Giri\u015f Modern yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde, projelerin derlenmesi, test edilmesi, ba\u011f\u0131\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-19T20:41:01+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"28 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber\",\"datePublished\":\"2025-11-19T20:41:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/\"},\"wordCount\":5180,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/\",\"name\":\"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-11-19T20:41:01+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/","og_locale":"tr_TR","og_type":"article","og_title":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber","og_description":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber Giri\u015f Modern yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde, projelerin derlenmesi, test edilmesi, ba\u011f\u0131","og_url":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-11-19T20:41:01+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"28 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber","datePublished":"2025-11-19T20:41:01+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/"},"wordCount":5180,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/","url":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/","name":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-11-19T20:41:01+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/gradle-ve-eclipse-entegrasyonu-kapsamli-bir-rehber\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Gradle ve Eclipse Entegrasyonu: Kapsaml\u0131 Bir Rehber"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34626","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=34626"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34626\/revisions"}],"predecessor-version":[{"id":34627,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34626\/revisions\/34627"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=34626"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=34626"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=34626"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}