One thing I dont get in AEM. the majority of tutorials and articles only
tell you how to create critical items in the UI of a running local aem
Dev instance, including page template types, page templates, components
and now servlet paths. Adding a new path on my local AEM instance is
rather pointless, as it wont get build and deployed from Git to the
cloud servers. So Ill stick with /bin.
Hi @TB3dock , When you hit the command "mvn clean install", maven will
clean the target folder during the build and place the latest jar after
creating it again. So basically, this will update the jar with the new
codebase. Other than that, if you want to install only the OSGi bundle
in the AEM instance, you can use the below command."mvn clean install
-PautoInstallBundle". Here, "-PautoInstallBundle" will install only the
OSGi bundle in the AEM instance. You need to deploy the OSGI bundle
Right, this is the cloud SDK and development based on AEM as a cloud
service is different thus no manual steps. More information here -
@TB3dock No, "create component" "create template" and "create Dialog"
menu items are NOT removed from crx/de. Although, admin should have all
the required permissions/ACLs on these nodes but could you please check
if the modify action is enabled for admin or administrator group? Is it
happening for all the nodes/folders under /apps?Also could you please
try to create a new user, add this user to the administrator group and
try creating the component/template.
Ok, from the error message, I did a full text search on the contents of
the entire source for "2.0.0", and found that
contains @version("2.0.0") I increased this to 2.1.0. Now it builds
@TB3dock You can refer other components and decide what file/node to
keep under your component.The Create Component option was just creating
the component and was adding the HTL/JSP file. Rest all was added by
individual developer and the same needs to be followed here. Thanks!
Hi @TB3dock Creating a component in IDE is straight forward.Each
component will have some basic fields as shown above:byinline: This is
the folder which will be the component name._cq_dialog: This will be the
folder which will hold the cq:dialog node..content.xml inside
_cq_dialog: This xml file will hold the XML structure of the
dialog..content.xml parallel to _cq_dialog: This is the XML file which
will hold the XML structure for the component such as component group,
sling resource type and al...