Why not use CRXDE Lite for developing OSGI bundles | Community
Skip to main content
Jai1122
New Participant
October 16, 2015
Solved

Why not use CRXDE Lite for developing OSGI bundles

  • October 16, 2015
  • 2 replies
  • 1270 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Alex Collignon

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

2 replies

Alex CollignonAccepted solution
Employee
October 16, 2015

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

Jai1122
Jai1122Author
New Participant
October 16, 2015

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