As devel­op­ers we are used to hav­ing bet­ter and faster devel­op­ment tools. If you’re a devel­op­ing with Sling, the clas­sic ‘my code is com­pil­ing’ excuse won’t give you time for a lit­tle sword­fight, since the the build time is mea­sured in sec­onds, rather than min­utes. How­ever, you might spend a lit­tle time deploy­ing a JAR file con­tain­ing your bun­dle or ini­tial con­tent from the com­mand line.  Our goal is to remove the time you spend fid­dling with com­mand line tool­ing and let you work in an incre­men­tal fash­ion in your IDE.

In my Sling IDE tool­ing talk I will show­case the work done in the Sling com­mu­nity to build Eclipse tool­ing for Sling appli­ca­tions. Cur­rently we sup­port deploy­ing both OSGi bun­dles and con­tent — via Apache Jackrab­bit Fil­e­Vault, as well as con­nect­ing to Sling Launch­pad instances in debug mode. I will also dis­cuss the tech­ni­cal foun­da­tions of the tool­ing and future devel­op­ment directions.

The IDE tool­ing is in its early devel­op­ment stage, but it’s sta­ble and the cur­rent fea­ture set is enough for pro­duc­tive use. We lever­age estab­lished Open Source tools such as Apache Maven and Apache Jackrab­bit Fil­e­Vault to deploy con­tent and code to a run­ning Sling instance.

I’m look­ing for­ward to meet­ing you at adaptTo() 2013, Sept. 23–25 in Berlin, and dis­cussing the cur­rent state and the future direc­tions of the Sling IDE tool­ing. You can learn more about the event, read up on all of the ses­sions, and reg­is­ter to attend here.