adobe / aem-eclipse-developer-tools

The Eclipse plugin that brings you the full connection to the Adobe Experience Manager, with auto-sync and project creation wizard.

AEM Developer Tools for Eclipse

The AEM Developer Tools for Eclipse is a plugin based on the Eclipse plugin for Apache Sling released under the Apache License 2.

For installation instructions and more information, check the online documentation.

Contributing

Contributions are welcomed! Read the Contributing Guide for more information.

Licensing

This project is licensed under the Apache V2 License. See LICENSE for more information.

aem-eclipse-developer-tools's Issues

InstallBundle -> D:\workspace\eclipse\example\core\target\classes : Project P/example.core does not have a META-INF/MANIFEST.MF (yet) - not publishing this time (0 ms)

Hi,
how can i fix this problem?
the archetype version 7 doesnt create this file for default.
Where can i find documentation on this issue?
Thanks.

it.tests not filtered out during first deployment

When creating a new copy of the sample-project-archetype using the wizard, although the code at [0] should filter this out the it.tests bundle is being deployed, which fails due to a missing junit dependency. The it.launcher deploys that junit dependency when the integration tests are explicitly run, but ootb it.tests should not be deployed.

[0] https://github.com/Adobe-Marketing-Cloud/aem-eclipse-developer-tools/blob/master/com.adobe.granite.ide.eclipse-ui/src/main/java/com/adobe/granite/ide/eclipse/ui/wizards/np/NewGraniteProjectWizard.java#L151

Easy conversion of content packages into Maven projects

It should be possible to easily convert or import a content package into a content project.

Unable to save/sync while connected to server in debug mode

When I start my server I can save files locally and they are synced to the server's JCR just fine.

When I put a break point into a JSP and enter debug mode, run a page that uses the component, my debug view in Eclipse works just fine.

When I am connected in debug mode, and make changes to a file, then hit save, it attempts to sync but then fails the operation and gives me this message:

Could not publish to the server.
java.lang.NullPointerException

I am using Luna. If you need any other information let me know.

Provide archive download to eclipse.adobe.com

Finish button broken in server step of new project wizard

If the server already exists and a new project is created, when reaching the last step where the server is to be configured, if the default choices are ok and nothing has to be modified on that screen, then the Finish button is disabled.

Work-around: change something and revert it, the Finish button can then be clicked.

Getting error when including a jsp in another jsp in AEM eclipse

Fragment "/apps/company/global.jsp" was not found at expected path /company.ui.apps/
apps/company/global.jsp.

Pls help me to resolve it..

i am not seeing dialog under my component after using AEM eclipse

pls help..

Add error overlay when the content sync root does not exist

Not sure if it is the wrong way I'm doing it, but how to get existing project up and running with AEM Developer Tools for Eclipse?

My colleague has set up a project using AEM Developer Tools plugin for Eclipse and now I need that project setup in my Eclipse, with deploying it to my local AEM 6 instance.

When I import the project to my workspace as Maven project, it is imported properly, but I cant get the plugin identify the project. It is just a maven project !

Also, options for "Convert to Bundle project" and "Convert to Content project" is disabled.

I'm (whole team) stuck here and can't progress. Is this a bug? If not, what is the correct way of performing this task?

Unclear error when creating a project that already exists on filesystem

When using the AEM Sample Multi-Module Project wizard to create a project that already exists in the workspace folder of the file system, then a cryptic error is displayed: Unable to create project from archetype [com.adobe.granite.archetypes:sample-project-archetype:7].

This can happen frequently in trainings if someone creates a project with wrong parameters and wants to create it again, but when deleting the initial project forgets to check the Delete project contents on disk.

Error when publishing changes in the apps / content project from workspc to the local AEM instance

I repeatedly get the below error when trying to publish the apps or the content projects to the AEM server

[23 August, 2014 10:11:04 PM IST] AddOrUpdateNodeCommand -> /apps/example/tests : JcrResult[ success:false, exception: org.apache.sling.ide.transport.RepositoryException - javax.jcr.nodetype.ConstraintViolationException: no matching property definition found for {}dependencies](39 ms)
org.apache.sling.ide.transport.RepositoryException: javax.jcr.nodetype.ConstraintViolationException: no matching property definition found for {}dependencies
at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:65)
at org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:43)
at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.execute(SlingLaunchpadBehaviour.java:455)
at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishContentModule(SlingLaunchpadBehaviour.java:428)
at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishModule(SlingLaunchpadBehaviour.java:231)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:137)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:54)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: javax.jcr.nodetype.ConstraintViolationException: no matching property definition found for {}dependencies
at org.apache.jackrabbit.jcr2spi.nodetype.ItemDefinitionProviderImpl.getQPropertyDefinition(ItemDefinitionProviderImpl.java:233)
at org.apache.jackrabbit.jcr2spi.nodetype.ItemDefinitionProviderImpl.getQPropertyDefinition(ItemDefinitionProviderImpl.java:126)
at org.apache.jackrabbit.jcr2spi.NodeImpl.getApplicablePropertyDefinition(NodeImpl.java:1831)
at org.apache.jackrabbit.jcr2spi.NodeImpl.createProperty(NodeImpl.java:1518)
at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:252)
at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:232)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.updateNode(AddOrUpdateNodeCommand.java:299)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:99)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:80)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:57)
... 12 more
[23 August, 2014 10:11:04 PM IST] AddOrUpdateNodeCommand -> /content/example : JcrResult[ success:true](159 ms)
[23 August, 2014 10:11:04 PM IST] AddOrUpdateNodeCommand -> /content/dam/example : JcrResult[ success:true](143 ms)
[23 August, 2014 10:11:04 PM IST] AddOrUpdateNodeCommand -> /content/example : JcrResult[ success:false, exception: org.apache.sling.ide.transport.RepositoryException - javax.jcr.RepositoryException: Unable to retrieve definition for item with id '/content/example/jcr:content'.](70 ms)
org.apache.sling.ide.transport.RepositoryException: javax.jcr.RepositoryException: Unable to retrieve definition for item with id '/content/example/jcr:content'.
at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:65)
at org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:43)
at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.execute(SlingLaunchpadBehaviour.java:455)
at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishContentModule(SlingLaunchpadBehaviour.java:428)
at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishModule(SlingLaunchpadBehaviour.java:231)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:137)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:54)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: javax.jcr.RepositoryException: Unable to retrieve definition for item with id '/content/example/jcr:content'.
at org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.getItemDefinition(RepositoryServiceImpl.java:954)
at org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.getNodeDefinition(RepositoryServiceImpl.java:893)
at org.apache.jackrabbit.jcr2spi.nodetype.ItemDefinitionProviderImpl.getNodeDefinition(ItemDefinitionProviderImpl.java:350)
at org.apache.jackrabbit.jcr2spi.nodetype.ItemDefinitionProviderImpl.getQNodeDefinition(ItemDefinitionProviderImpl.java:81)
at org.apache.jackrabbit.jcr2spi.state.NodeState.retrieveDefinition(NodeState.java:467)
at org.apache.jackrabbit.jcr2spi.state.NodeState.getDefinition(NodeState.java:316)
at org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkProtection(ItemStateValidator.java:504)
at org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkIsWritable(ItemStateValidator.java:214)
at org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkWriteProperty(ItemStateValidator.java:313)
at org.apache.jackrabbit.jcr2spi.state.ItemStateValidator.checkSetProperty(ItemStateValidator.java:253)
at org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.setPropertyStateValue(SessionItemStateManager.java:516)
at org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.visit(SessionItemStateManager.java:381)
at org.apache.jackrabbit.jcr2spi.operation.SetPropertyValue.accept(SetPropertyValue.java:82)
at org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.execute(SessionItemStateManager.java:215)
at org.apache.jackrabbit.jcr2spi.PropertyImpl.setInternalValues(PropertyImpl.java:609)
at org.apache.jackrabbit.jcr2spi.PropertyImpl.setValue(PropertyImpl.java:590)
at org.apache.jackrabbit.jcr2spi.PropertyImpl.setValue(PropertyImpl.java:110)
at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:246)
at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:232)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.updateNode(AddOrUpdateNodeCommand.java:299)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:99)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:103)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:80)
at org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:57)
... 12 more

I did raise a query on the help forums but didn't really get a resolution,

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.1.html/forum__2svm-did_anyone_haveany.html

not getting JCR properties in Eclipse after adding the AEM Dev tool CQ

Please help me to resolve it..

AEM->Export To Server Generates "Not Direct Child" Error

1. Create project in Eclipse with Maven Archetype 7 & Configure to deploy to local AEM Author (Filesystem mode).
2. Run Maven build once with -P autoInstallPackage to get initial deployment.
3. Make any change in ui.apps.
4. Right-click on ui.apps, choose AEM->Export to Server...
5. Choose local server.
6. Runs for a while and then generates 'not a direct child' error (Resource at path /target/classes/etc/designs/ewcmbiz/jquery/js.txt is not a direct child of /../../../../target/classes/etc/designs/ewcmbiz/jquery)

Publishing error when a project got newly created

After a project is newly created, following error is shown.

[March 6, 2015 2:38:01 PM MST] InstallLocalBundle -> /Users/gwalt/Documents/workspace/lab/it.tests/target/classes : FAILED (23 ms)
org.apache.sling.ide.osgi.OsgiClientException: Unable to install/update bundle from dir /Users/gwalt/Documents/workspace/lab/it.tests/target/classes : Unresolved constraint in bundle org.summit.lab.it.tests [440]: Unable to resolve 440.0: missing requirement [440.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.junit.annotations)(version>=1.0.0)(!(version>=2.0.0)))
    at org.apache.sling.ide.osgi.impl.HttpOsgiClient$LocalBundleInstaller.installBundle(HttpOsgiClient.java:216)
    at org.apache.sling.ide.osgi.impl.HttpOsgiClient.installLocalBundle(HttpOsgiClient.java:172)
    at org.apache.sling.ide.osgi.impl.TracingOsgiClient.logInstallLocalBundle(TracingOsgiClient.java:75)
    at org.apache.sling.ide.osgi.impl.TracingOsgiClient.installLocalBundle(TracingOsgiClient.java:57)
    at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishBundleModule(SlingLaunchpadBehaviour.java:339)
    at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishModule(SlingLaunchpadBehaviour.java:219)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
    at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:137)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
    at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:54)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
    at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Server | Publishing failed

Used the Eclipse AEM plugin(installed from Eclipse marketplace) to create AEM multimodule project (sample-project-archetype-7).
Configured a new server with port, hostname, username same as that of the running AEM instance and
Server Runtime Environment as Adobe Experience Manager.

But, unable to start server and deploy bundles. Gives following error:
Publishing failed
Could not publish to the server.
Service is null

Improve rules for default content paths in project wizard

The AEM Sample Multi-Module Project wizard offers a simplified way to create a project with just 3 fields: Name, Group Id and Artefact Id. But the appsFolderName and the contentFolderName don't get their values from any of them.

It would have been expected that the Artefact Id is taken for their default values.

Set up code signing

The TagExtraInfo class for "cq:defineObjects" (com.day.cq.wcm.tags.DefineObjectsTEI) could not be instantiated

I am facing this issue in global.jsp.. pls help me... "on hovering cq:defineObjects/ and sling:defineObjects/" I am getting this error.
Attached the screenshot.

cq:htmlTag nodes not appearing in eclipse view

Related to my issue around dialog's (and more importantly with cq:dialog's), creating a node of name "cq:htmlTag" doesn't synch to AEM - Errors out: complaining about a double colon (::) in the node name.

When creating a node of type "nt:unstructured" and name of "_cq_htmlTag", this syncs correctly with a node name of "cq:htmlTag" to AEM, however it doesn't appear inside eclipse. Looking in the project workspace on the filesystem, I can see that it was created as a folder created called "_cq_htmlTag" and inside the folder there is a ".content.xml" file.

I can edit the ".content.xml" file on the filesystem (outside of eclipse) to get attributes into AEM, although obviously this is extremely clumsy... is it possible to get this issue addressed?

Creating a project using the AEM project archetype is slow

I timed this today and it takes about 2:30 minutes. Progress reporting is also quite poor, we should be able to improve it.

Support m2e 1.6 or newer

Due to https://bugs.eclipse.org/bugs/show_bug.cgi?id=403243 , the org.apache.maven packages are exported with a mandatory provider=m2e attribute.

Plugin execution not covered by lifecycle configuration

Description

When creating a new AEM project, there are multiple (17) Eclipse errors on the various pom.xml, all starting with "Plugin execution not covered by lifecycle configuration".

Environment

• Java 1.8.0_20
• Eclipse Luna 4.4.0
• Maven 3.2.1
• Sling IDE Tools 1.0.2
• AEM IDE Tools: UI-Extensions 1.0.0

Steps to reproduce

• Create a new AEM Sample Multi-Module Project
• Achtetype: com.adobe.granite.archetypes: sample-project-archetype: 7
• Keep default settings (name: Example, group: org.myorg, artefact: example)

Detailed error listing

Description	Resource	Path	Location	Type
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.core	line 18	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.core	line 18	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.core	line 18	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.it.launcher	line 19	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.it.launcher	line 19	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.it.launcher	line 19	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.it.tests	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.ui.apps	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.ui.content	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.it.tests	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.it.tests	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.ui.apps	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.ui.content	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.ui.apps	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.ui.content	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources (execution: copy-metainf-vault-resources, phase: generate-resources)	pom.xml	/example.ui.apps	line 90	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources (execution: copy-metainf-vault-resources, phase: generate-resources)	pom.xml	/example.ui.content	line 90	Maven Project Build Lifecycle Mapping Problem

clientlib.css not refreshed when child .css files are being deployed

(originally reported by @eglistefan)

In the aem-project-archetype we have a sample clientlib. That one causes problems lately, namely the clientlib.css remains empty.

When adding an unrelated property to /etc/designs/myapp/clientlib, the clientlib mechanism (ie HtmlLibraryManagerImpl) seems to be correctly triggered and the clientlib.css is refreshed properly.

What is likely happening is this:

• eclipse starts deploying the ui.apps project (of the archetype)
• it eventually deploys /etc/designs/myapp/clientlib, and clientlib/css.txt
• this seems to trigger the clientlib.css to be generated
• few seconds later only, it deploys the child nodes, eg clientlib/css/main.css
  • that seems to be missed by the HtmlLibraryManagerImpl
  • and thus the originally generated, empty, clientlib.css stays in the cache

Typo in bundle status installed on the server

Description

When the bundle is not installed on a server, the message is:
Installation support bundle is not present our outdated, deployment will not work
It should be instead:
Installation support bundle is not present or outdated, deployment will not work

Issue rendering page in CQ -"Uncaught ReferenceError: CQ is not defined"

I am facing an issue in my CQ Environment. The page breaks with a ERROR in the browser console :"Uncaught ReferenceError: CQ is not defined" in the line below.Can you please give pointers.

The Error in Browser is below:
"Uncaught ReferenceError: CQ is not defined;"

Unable to deploy latest bundle changes to Author

From the main project directory, run cmd = mvn clean install -PautoInstallBundle for the first time. Bundle deploy successfully.

Do some changes like add new classes, new methods in existing class and update the version in package-info.java. Run the same command again and it indicate BUILD SUCCESS from the command prompt.

What's observed:

1. The JAR under /apps/project/install should be the latest one, based on its jcr:content, jcr:lastModified date time value.
2. The bundle installed (found under localhost:4502/system/console/bundles) is not the latest one

• based on the exported Packages version. It do not reflect the new version number.
• JSP that call to the new classes or methods reporting undefined error (can't find those class or method)

Using JDK 1.7.0_75, with Maven 3.2.5 in OSX Yosemite.

dialog constructs not working

Neither classic or touch UI based dialogs work properly.

Classic:
The dev tools won't allow the creation of a cq:Widget or cq:TabPanel underneath a cq:WidgetCollection.
Importing the dialog created in CRXDE Lite from AEM instead of creating them in eclipse kind of works for classic, so long as you don't try and update it at any stage within Eclipse.

Touch:
Creating a node with name of "cq:dialog" (type=cq:Dialog) gives the following synchronisation error to AEM: "Failed publishing path=/apps/training/components/content/topnav/cq::dialog, result=JcrResult[ success:false, exception: org.apache.sling.ide.transport.RepositoryException - javax.jcr.RepositoryException: Invalid path: /apps/training/components/content/topnav/cq::dialog]" Note the double ":" in error message.
Importing the cq:dialog created in CRXDE Lite from AEM instead of creating them in eclipse doesn't work. Doesn't appear in folder. Not sure if it's relevant or not, however, looking at the project files within the eclipse project folder, you can see the cq:dialog being imported as "_cq_dialog/.content.xml" whereas "_cq_dialog.xml" seems to work better and is more consistent with the dialog node (dialog.xml).

New project should offer option to use already existing folder.

When creating a new project and a corresponding folder already exists, then it fails without any useful help message. Instead, it should offer the option to overwrite that folder.

Improve default values in New Server wizard

The default values of the New Server wizard should be improved:

• The default Port should be 4502 instead of 8080.
• The default Pushing interval should be 0 instead of 15.

Deployed site should not hardcode update site location and artifact

Currently the generated update site HTML page hardcodes the location of the update site and also hardcodes the location of the zipped update site .

If we want to deploy the site in alternate locations, .e.g http://eclipse.adobe.com/aem/dev-tools/nightly , we should make the links dynamic.

Add action for opening node in CRX DE Lite

Not getting the suggestions when i am pressing control+space in AEM eclipse

Error when skipping server creation in wizard

Description

Skipping the server step of the project creation wizard doesn't offer a consistent experience.

Steps to reproduce

Remove all projects, all server configurations and restart Eclipse. This is important otherwise the following instructions will show yet other problems than the ones described.

On a fresh Eclipse, create a project with the AEM Sample Multi-Module Project wizard, and hit the Finish button early on the Configure Archetype Properties step, when no server has been configured yet. The wizard then doesn't close but shows a cryptic error message For input string: "". Trying to hit the Finish button again shows another error message Project already exists with name example, so Cancel must be pressed.

It is very tempting to press enter to go to perform the default action, which should be the best choice. But in this case this behavior leads to a status that is then hard to recover from, especially for those that don't know well Eclipse.

Suggested fix

We shouldn't allow to skip the server setup step of the wizard. But to still allow no server to be setup, we should add a third option to the Select or Create Server step: Don't setup a server.

Support for 5.6.1?

http://docs.adobe.com/docs/en/dev-tools/aem-eclipse.html states that 5.6.1 is supported but the archetype obviously creates AEM 6 projects. Is there any support for 5.6.1 developers? Once the archetype is public I guess I could hack that and fix dependencies, etc but I'm hoping someone has already done that ;)

Even after that's done, can I expect any significant issues trying to use the plugin with 5.6.1?

Thanks!

Component Dialogs Deleted When Publishing Changes to .Java Files

1. Create New Project in Eclipse Dev Tools Using Maven Archetype 7.
2. Connect to Local AEM 6.0 SP1 with Content Project.
3. Run Maven Build once with autoInstallPackage to get whole project deployed.
4. Edit & save a .java file in a component in the ui.apps project with any syntax error ( and sometimes, even with no error).
5. Confirm that dialogs are missing from component on server.

Cannot delete nodes of name cq:dialog or cq:htmlTag as type of nt:unstructured

With the latest eclipse build, we can create touch dialogs now (cq:dialog - nt:unstructured), however once created inside a component, eclipse doesn't allow the option to delete them.

See image:

Currently, the only way to remove these nodes is to go to the filesystem and remove them.

JCR_ROOT Path Breaks Upon Project Import

1. Create AEM project using Developer Tools for Eclipse, Maven Archetype 7.
2. Delete project from Eclipse, but do not delete contents on disk.
3. File->Import->Maven->Existing Maven Projects, select the project you created in step 1.
4. Look at 'problems' tab, and note that jcr_root is not correct.
5. Look at ui.apps project properties, note that path under 'AEM' tab is not correct (only has jcr_root).
6. Uncheck 'Content Project' facet in project properties.
7. Rick click on ui.apps, Configure->Convert To...Content Project.
8. Check Problems & 'AEM' tab, note that path is now set correctly.

Cannot connect to server

When hitting connect to server button I'm getting the following exception:

!SESSION 2014-09-03 02:04:46.728 -----------------------------------------------
eclipse.buildId=4.4.0.I20140606-1215
java.version=1.8.0_20
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product

!ENTRY org.eclipse.wst.server.core 4 0 2014-09-03 02:05:00.410
!MESSAGE Could not publish to the server.
!STACK 0
java.lang.IllegalStateException: Service is null
at org.apache.sling.ide.eclipse.core.ServiceUtil.getNotNull(ServiceUtil.java:26)
at org.apache.sling.ide.eclipse.core.internal.Activator.getSerializationManager(Activator.java:134)
at org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishModule(SlingLaunchpadBehaviour.java:185)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:137)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:54)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Server is configured with defaults with port changed to 4502. I tried it with both Luna and Kepler on java-7-openjdk-amd64 and java-8-oracle on Ubuntu 14.04 64bit. (also tried on windows 7 with Luna - works ok, but my dev env is ubuntu)

de.pdark.decentxml.XMLParseException when I input japanese text in xml

I write japanese character in xml node,then occur exception.
Log:
de.pdark.decentxml.XMLParseException: Line 8, column 29: Missing end quote (") of attribute: "\n sling:messa..."
at org.apache.sling.ide.eclipse.ui.nav.model.TolerantXMLTokenizer.parseAttribute(TolerantXMLTokenizer.java:69)
at de.pdark.decentxml.XMLTokenizer.next(XMLTokenizer.java:229)
at de.pdark.decentxml.XMLParser.parseElement(XMLParser.java:769)
at de.pdark.decentxml.XMLParser.parseElementContent(XMLParser.java:876)
at de.pdark.decentxml.XMLParser.parseElement(XMLParser.java:821)
at de.pdark.decentxml.XMLParser.parse(XMLParser.java:159)
at org.apache.sling.ide.eclipse.ui.nav.model.TolerantXMLParser.parse(TolerantXMLParser.java:50)
at org.apache.sling.ide.eclipse.ui.nav.model.TolerantXMLParser.parse(TolerantXMLParser.java:38)
at org.apache.sling.ide.eclipse.ui.nav.model.TolerantXMLParser.parse(TolerantXMLParser.java:34)
at org.apache.sling.ide.eclipse.ui.nav.model.GenericJcrRootFile.(GenericJcrRootFile.java:57)
at org.apache.sling.ide.eclipse.ui.nav.model.JcrNode.initChildren(JcrNode.java:376)
at org.apache.sling.ide.eclipse.ui.nav.model.JcrNode.initChildren(JcrNode.java:411)
at org.apache.sling.ide.eclipse.ui.nav.model.JcrNode.initChildren(JcrNode.java:411)
at org.apache.sling.ide.eclipse.ui.nav.model.JcrNode.initChildren(JcrNode.java:411)
at org.apache.sling.ide.eclipse.ui.nav.model.JcrNode.initChildren(JcrNode.java:411)
at org.apache.sling.ide.eclipse.ui.nav.model.JcrNode.getChildren(JcrNode.java:352)
at org.apache.sling.ide.eclipse.ui.nav.model.SyncDir.getNode(SyncDir.java:93)
at org.apache.sling.ide.eclipse.ui.views.JcrPropertiesView.refreshContent(JcrPropertiesView.java:543)
at org.apache.sling.ide.eclipse.ui.views.JcrPropertiesView$1.syncDirUpdated(JcrPropertiesView.java:148)
at org.apache.sling.ide.eclipse.ui.nav.model.SyncDirManager.syncDirChanged(SyncDirManager.java:54)
at org.apache.sling.ide.eclipse.ui.nav.model.SyncDirManager.registerNewSyncDir(SyncDirManager.java:44)
at org.apache.sling.ide.eclipse.ui.nav.model.SyncDir.(SyncDir.java:38)
at org.apache.sling.ide.eclipse.ui.nav.JcrContentContentProvider.projectGetChildren(JcrContentContentProvider.java:129)
at org.apache.sling.ide.eclipse.ui.nav.JcrContentContentProvider.getPipelinedChildren(JcrContentContentProvider.java:259)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getPipelinedChildren(SafeDelegateTreeContentProvider.java:178)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.pipelineChildren(NavigatorContentServiceContentProvider.java:206)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$1(NavigatorContentServiceContentProvider.java:192)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:161)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:125)
at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1367)
at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917)
at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:620)
at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2643)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1923)
at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1898)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1855)
at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561)
at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533)
at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:555)
at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:350)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$3.run(PackageExplorerContentProvider.java:957)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.runUpdates(PackageExplorerContentProvider.java:195)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.runPendingUpdates(PackageExplorerContentProvider.java:187)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$1.runInUIThread(PackageExplorerContentProvider.java:165)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)

Archetypes displayed in wizard not always consistent

Initially, in the AEM Sample Multi-Module Project wizard there is only the com.adobe.granite.archetypes : sample-project-archetype : 7 archetype listed.

But when a second project is created, it also displays a com.adobe.granite.archetypes : sample-project-archetype : slingclipse-embedded archetype.

I don't know wether only one or both should be listed, but it should at be consistent.

Change icon of the extension to an AEM icon

Also update the icon to the latest rebrand (on dark background).

Reference Sling IDE Tooling through p2 update site

We should not rely on locally installed artifacts for the Sling IDE Tooling. Although it can be convenient, Tycho flags it as a warning and we should make reuse the officially deployed artifacts.

how to unpublish without republishing

Hi,
i am trying to remove all published content from the JCR, but there is just a button to clean and republish.
isnt there one for clean only the once published from JCR?
Thanks.

Classic view issue while editing/displaying parsys

I am using aem eclipse developer tool . I have followed the steps listed here and created my project called training.
http://docs.adobe.com/content/docs/en/dev-tools/aem-eclipse.html.Issue is when I view the below page in classic mode I get javascript error :
http://localhost:8080/cf#/content/training/en.html
Uncaught ReferenceError: CQ is not defined en.html:29(anonymous function)

<script type="text/javascript"> CQ.WCM.edit({"path":"/content/training/en/jcr:content/logo","type":"foundation/components/logo","csp":"page-home|page/logo"}); </script>

I am not getting sidekick as well. Can you please give pointers.

Syncing favicons seems to corrupt them

Steps to reproduce:

• Create a new project using the archetype
• Sync it to an AEM instance
• The favicon is now corrupted:
  /etc/designs/${appsFolderName}/favicon.ico

Ensure that installing the AEM Developer Tools brings in a recent enough version of the Sling IDE Tooling

As seen in #13 , it's possible for a new version of the AEM Dev Tools to coexist with an old version of the Sling IDE Tooling. We should make sure that when installing/updating the AEM Dev Tools we pull in a 'recent enough' version of the Sling IDE Tooling.

Content navigator does not display renditions for a dam asset

Setup Travis build

@gabrielwalt - can you please enable the Travis build for this repo and for the aem-project-archetype? See http://docs.travis-ci.com/user/getting-started/ for details. Once the webhook is activated, I can take care of the rest.

Thanks!

Improve server creation in new project wizard

Currently, the AEM Sample Multi-Module Project wizard asks for many details concerning the server as opposed to the New Server wizard.

We should pre-fill the values in the project creation wizard with following default values:

• Server name: Adobe Experience Manager at localhost
• Host name: localhost
• Port: 4502
• Username: admin
• Password: admin
• Debug Port: 30303

Wrong namespace in the XML file for cq:EditConfig node

Steps to reproduce this issue.

1. From within AEM Eclipse Developer Tools, create a node with node type = cq:EditConfig under a cq:Component node. Let's call it Component-A
2. Double click the cq:EditConfig node to open up as XML.
3. Notice that there's a namespace = xmlns:sling="http://sling.apache.org/jcr/sling/1.0"
4. Repeat step ONE on another component (Component-B) but using CRXDE Lite.
5. From within AEM Eclipse Developer Tools, click on Component-B, right click > Import From Server.
6. Double click the cq:EditConfig node to open up as XML.
7. Notice that you can find the namespace discovered in step 3. Instead, you'll see this namespace = xmlns:cq="http://www.day.com/jcr/cq/1.0"

The one created in AEM Eclipse Developer Tools will have issue after I added an attribute say for e.g.: cq:layout = editbar and trying to export into server.