Just see Rule#7 of David's model - Rule #7: ID's are evil. http://wiki.apache.org/jackrabbit/DavidsModel#Rule_.237:_ID.27s_are_evil

You need to create cq:HtmlTag for this use case. Check this article - http://dev.day.com/cemblog/en/experiencedelivers/2013/04/modify_the_auto-generateddivs.html

You can use vlt rcp command as it is much more faster and better than package installation. You can also try using this utility http://adamcin.net/net.adamcin.recap/ which provides a good web interface for invoking vlt rcp within AEM UI.

If you just want the list of agents then you can fire a GET request to the following URI - http://localhost:4502/bin/querybuilder.json?type=nt:unstructured&sling:resourceType=cq/replication/components/agent&group.1_path=/etc/replication/

I guess you can get this information from the HistoryItem object retrieved from WorkflowHistory object. https://docs.adobe.com/docs/en/cq/5-6-1/javadoc/com/day/cq/workflow/exec/HistoryItem.html##getUserId()You can check this thread for reference - https://forums.adobe.com/thread/1156064

This configuration is meant for indexing OAK repository so all the index configurations defined in crx will be used for indexing the JCR nodes. Even though you can define in crx which node paths to index but if you remove all the indexes and just keep /content/products then your repository will slow...

You should be using a CI tools like Jenkins/GO etc for deploying built artifacts to multiple instances in multiple environments. Maven should only be used for build, unit/integration  tests and deploying on local developer environment.

Instead of options property you should be creating a node named "datasource" and set sling:resourceType property for dynamic options. Check the following example - http://experience-aem.blogspot.com/2015/04/aem-6-sp2-touchui-adding-dynamic-select-options.html. Ref doc - http://docs.adobe.com/docs/en...

Could you please explain the use case you are trying to implement ?

Have you tried this code snippet ? - ${currentStyle.propertyname}