Home
This wiki page is here to share project related information and plugin versions.
The current branch is all-action-in-the-backtroudn where I tried to further separate the IntelliJ code from the AEM / Sling code. This was more difficult as the both types of code are intertwined and depend on each other. For now the code is working fine for IntelliJ / AEM-Sling but I did not try the same thing with Eclipse.
The basic idea is that the server connection manager is using an abstract AbstractDeploymentManager which contains the AEM / Sling code. The IDE then must provide the implementation which contains the IDE specific code. For now this is just an idea / prototype and needs adjustments to work with Eclipse but I hope it provides a guideline on how to proceed.
0.6.4.7-SNAPSHOT: All but Dialog Actions were move into the background which is done in the base class so the Actions don't need to do anything special. Added a better way to handle process indicators that also deals with no indicator and handles the nesting easier as it automates the pops.
Release: ZIP File of 0.6.4.6-SNAPSHOT on Dropbox
0.6.4.6-SNAPSHOT: Fixed an issue with the entire Module build which led to deadlocks. Also removed some debug statements that could disable the Plugin. For now the usage of non-Maven based project is discouraged as IntelliJ has no concept of a ZIP file based module.
Release: ZIP File of 0.6.4.6-SNAPSHOT on Dropbox
0.6.4.5-SNAPSHOT: Non-Maven OSGi modules should build now. There is a fix for any OSGi module as the deployment of Maven OSGi modules failed silently to deploy. This is fixed and if the build file is not present an alert is shown. There is also a fix for Maven modules where the Module Name and the Maven Artifact Id did not match as it is now looking at the parent folder to find a match.
Release: ZIP File of 0.6.4.5-SNAPSHOT on Dropbox
0.6.4.4-SNAPSHOT: Added support for non-Maven based project. In order to support these types of projects you need to use two facets. For OSGi modules you need to use the "Osmorc" plugin to setup the OSGi Facet and for Content Modules you need to setup the Sling Content Facet and specify the Content and META-INF root folder. For now only the IntelliJ Plugin Osmorc is supported for non-Maven OSGi bundles.
Release: ZIP File of 0.6.4.4-SNAPSHOT on Dropbox
0.6.4.3-SNAPSHOT: This release makes the deployment wait until the Maven Build for OSGi bundles is over. In addition the toolbar is locked while any action is executed so that background tasks like the Maven Build cannot be intercepted. Finally the build also addresses an issue with AEM DAM Workflows could interfere with deployments of DAM Assets. The plugin will place the push of the /renditions/original nodes to the end.
Release: ZIP File of 0.6.4.3-SNAPSHOT on Dropbox
0.6.4.2-SNAPSHOT: This release contains a fix for the Maven Build execution for OSGi Bundles. Now the build is executed in the background and the action waits until it is finished before installing the OSGi Bundle in AEM.
Release: ZIP File of 0.6.4.2-SNAPSHOT on Dropbox
0.6.4.1-SNAPSHOT: This releases contains the refactored Resource Change Command Factory which is made IDE independent. The UI and handling did not change. This release also contains a fix for mysterious failures to upload Renditions files.
Release: ZIP File of 0.6.4.1-SNAPSHOT on Dropbox
0.6 Beta 3: This releases focuses on the proper handling of Windows paths.
Release: ZIP File of 0.6 Beta 3 on Dropbox
The installation documentation and user manual can be found here:
The markdown file (.md) is the source and the PDF is a rendered, 1-page version of it. The Installation instructions are up to date but the screenshots of the plugin are somewhat outdated.