Expand my Community achievements bar.

SOLVED

Why not use CRXDE Lite for developing OSGI bundles

Avatar

Level 5

Hi All,

    I have been writing OSGI bundles in CRXDE Lite only. Many say it is supposed to be done by setting up Maven and Eclipse.

I could not find any reasons why it should not be developed in Lite. Can someone please tell that to me?

1 Accepted Solution

Avatar

Correct answer by
Level 2

Hi Jail,

Maven and your favorite IDE - might be Eclipse - offer you many advantages:

  • more efficient code writing workflow with code completion and the other tons of great feature of your IDE
  • well known release process with maven-release plugin
  • simple integration with continuous integration tooling such as Jenkins or Travis
  • simple and powerful integration with AEM thanks to our AEM Developer Tools [1]
    • Seamless integration with AEM instances through Eclipse Server Connector.
    • Synchronization for both content and OSGI bundles.
    • Debugging support with code hot-swaping capabiliby.
    • Simple bootstrap of AEM projects via a specific Project Creation Wizard.
    • Easy JCR properties edition.

One more thing, once your projects are set up you can collaborate with your peers by sharing your code on a version control system such as Git or a non distributed one like Subversion.

Note that we also provide a Brackets extension [2] that might better suit you if you are focusing on front-end development.

[1] http://docs.adobe.com/content/docs/en/dev-tools/aem-eclipse.html

[2] http://docs.adobe.com/docs/en/dev-tools/sightly-brackets.html

View solution in original post

2 Replies

Avatar

Correct answer by
Level 2

Hi Jail,

Maven and your favorite IDE - might be Eclipse - offer you many advantages:

  • more efficient code writing workflow with code completion and the other tons of great feature of your IDE
  • well known release process with maven-release plugin
  • simple integration with continuous integration tooling such as Jenkins or Travis
  • simple and powerful integration with AEM thanks to our AEM Developer Tools [1]
    • Seamless integration with AEM instances through Eclipse Server Connector.
    • Synchronization for both content and OSGI bundles.
    • Debugging support with code hot-swaping capabiliby.
    • Simple bootstrap of AEM projects via a specific Project Creation Wizard.
    • Easy JCR properties edition.

One more thing, once your projects are set up you can collaborate with your peers by sharing your code on a version control system such as Git or a non distributed one like Subversion.

Note that we also provide a Brackets extension [2] that might better suit you if you are focusing on front-end development.

[1] http://docs.adobe.com/content/docs/en/dev-tools/aem-eclipse.html

[2] http://docs.adobe.com/docs/en/dev-tools/sightly-brackets.html

Avatar

Level 5

Thats excellant summary of going for an IDE + Maven. Many thanks alexandre.