|
Developing with CRXDE
This section describes how to develop your JCR, Apache Sling or CQ5 application with CRXDE.
Please refer to the Development Tools page for more information on the different development environments that are available.
CRXDE is a pre-packaged stand-alone Eclipse application. CRXDE is custom-built specifically for CQ and CRX and thus enables you to efficiently develop your project. CRXDE gives you a broad set of tools to easily create a project, create and manage files, folders, templates, components, dialogs, nodes, properties, scripts and bundles while logging, debugging and integrating with SVN. CRXDE is built on the Eclipse Rich Client Platform (RCP), leveraging the Eclipse File System (EFS) API.
CRXDE is recommended when you develop complex applications by creating new components and Java bundles.
Getting Started with CRXDE
To get started with CRXDE, proceed as follows:
- Install CQ or CRX.
- Download CRXDE from the CRX Product page
- Extract the package.
- Double-click the executable.
- Enter the location of your CQ or CRX installation. By default it is:
- http://localhost:4502/ for CQ5 Quickstart
- http://localhost:7402/ for CRX Quickstart
- Enter your username and password. By default it is admin and admin.
- Click OK.
Note. If your installation uses non-standard contexts for CRX web applications, e.g., when you deployed CRX to an application server in such a way, you need to do the following:
- In case CRX Launchpad web application is installed under another context (e.g., /launchpad instead of /), you need to login to this URL
- http://<host>:<port>/launchpad
- In case CRX web application is installed under another context (e.g., /daycrx instead of /crx), you need to configure the CRX server endpoint to use this context (/daycrx/server)
The CRXDE User Interface looks as follows:
The screenshot shows CRXDE main window, with content navigator, editor window with a JSP file, outline of the file, and properties of the content node.
You can now use CRXDE to develop your application.
By default, CRXDE does not need to be configured. For advanced use cases, CRXDE offers advanced options to change the CRX server endpoint.
CRXDE supports the following Day products:
- CRX repository
- CQ5 suite of content management products; CQ5 is based on CRX repository
CRXDE release by default supports at least the latest version of CRX, and the CQ5 product which is based on that repository version. Please see CRXDE compatibility for information about compatibility of CRXDE with earlier product releases.
CRXDE seamlessly offers on-the-fly mapping of a JCR 2.0 repository made of nodes and properties to an Eclipse representation as files and folders, and "nodes" and their metadata. The underlying technology is based on FileVault, DavEx remoting and the Eclipse framework.
CRXDE provides the Integrated Development Environment functionalities and features offered by its underlying Eclipse platform. These include editing of source code, code completion and restructuring, searching and browsing, and many others.
Additionally, CRXDE provides extended support for CRX and CQ5 specific development tasks. This functionality is described in the following subsections.
With CRXDE you can create a working project in three clicks. The project wizard creates a new project under /apps, some content under /content and a package wrapping all the project the content under /etc/packages. The project can be used right away to render a sample page displaying Hello World, based on a jsp script that renders a property from the repository and calls a Java class to render some text.
To create a project with CRXDE:
- In CRXDE, in the Navigator tab, right-click a folder, select Build, then Create Project ....
Note: you can right-click any folder in the tree navigation, as the new project nodes are, by design, created below /apps, /content and /etc/packages.
- Define:
- Project Name - the project name is used to create the new nodes and the bundle, e.g. myproject.
- Java Package - the Java package name prefix, e.g. com.mycompany.
- Click OK.
To access the sample page displaying Hello World, point your browser to:
http://localhost:4502/content/<project-name>.html
The Hello World page is based on a content node, that calls a jsp script through the sling:resourceType property. The script reads the jcr:title property from the repository and gets the body content by calling a method of the SampleUtil class, that is available in the project bundle.
The following nodes are created:
- /apps/<project-name>: the application container.
- /apps/<project-name>/components: the components container, containing the sample html.jsp file, used to render a page.
- /apps/<project-name>/src: the bundles container, containing a sample project bundle.
- /apps/<project-name>/install: the compiled bundles container, containing the compiled sample project bundle.
- /content/<project-name>: the content container.
- /etc/packages/<java-suffix>/<project-name>.zip, a package wrapping all the project app and content. You can use it to rebuild the project for further deployment (e.g. to other environments) or for sharing through Package Share.
To create a folder with CRXDE:
- In CRXDE, in the Navigator tab, right-click the folder under which you want to create the new folder, select New, then Folder.
- Enter the Folder name and click Finish.
To create a template with CRXDE:
- In CRXDE, in the Navigator tab, right-click the folder where you want to create the template, select New, then Template.
- Enter the Label, Title, Description, Resource Type and Ranking of the template. Click Finish.
It creates:
- A node of type cq:Template with Template properties
- A child node of type cq:PageContent with Page Content properties
You can drag and drop a thumbnail from your file system into the template folder.
You can add properties to your template: refer to the Creating a Property section.
To create a component with CRXDE:
- In CRXDE, in the Navigator tab, right-click the folder where you want to create the component, select New, then Component.
- Enter the Label, Title, Description, Super Resource Type and Group of the component. Click Next.
- If needed, set values for the optional properties Allowed Parents, Allowed Children and check the box Is Container. Click Finish.
It creates:
- A node of type cq:Component
- Component Properties
- A component .jsp script
To create a dialog with CRXDE:
- In CRXDE, in the Navigator tab, right-click the component where you want to create the dialog, select New, then Dialog.
- Enter the Name and the Title. Click Finish.
It creates a dialog with the following structure:
dialog[cq:Dialog]/items[cq:TabPanel]/items[cq:WidgetCollection]/tab1[cq:Panel]
You can now adapt the dialog to your needs by modifying properties or creating new nodes.
To create a node with CRXDE:
- In CRXDE, in the Navigator tab, right-click the node where you want to contain the new node, select New, then Node.
- Enter the Name and the Type. Click Finish.
You can now adapt the node to your needs by modifying properties or creating new nodes.
To create a property with CRXDE:
- In CRXDE, in the Navigator tab, right-click the node where you want to add the new property, select New, then Property.
- Enter the Name, the Type and the Value. Click Finish.
You can also edit properties and add new ones in the Properties tab.
To create a new script:
- In CRXDE, in the Navigator tab, right-click the component where you want to create the script, select New, then JSP.
- Enter the File name. Click Next.
- Select the JSP Template and click Finish.
The new file opens in the main tab.
You can use the following key combinations for code completion:
- Ctrl + Space on Windows
- Cmd + Space on Mac
Importing Files and Folders into the Repository
To import a file or a folder from your file system into the repository with CRXDE:
- In your file explorer copy the file (or the folder).
- In CRXDE, navigate to the location that will contain the file (or the folder). Right-click and select Paste.
The files are mapped to nodes of type nt:file and the folders to nodes of type nt:folder.
You can also drag and drop the file (or the folder) directly into CRXDE.
Creating and Compiling Java Classes
With CRXDE, you can easily create and compile individual Java classes.
To create a Java class, select a folder where you want to place the new class. Usually, it is a part of an existing Java package (e.g., com/example/mypackage). Right-click the folder, select New, then Class. Fill out the Eclipse dialog providing information about your class, and click Finish. Your class is created, and its skeleton source file displayed in the editor.
Once you add source code to your class, you can easily compile it. Right-click the class source file in Navigator, select Build, then Compile. Your class will be compiled and automatically deployed into CRX OSGi container. In case of compilation problems, you will see the status in the Remote Build view.
With CRXDE, it is straightforward to create an OSGI bundle, add Javaclasses to it, and build it. The bundle is then automatically installed and started in the OSGI container.
This section describes how to create a Test bundle with a HelloWorld Java class that displays Hello World! in your browser when the resource is requested.
To create the Test Bundle with CRXDE:
- In CRXDE create myapp project with the project wizard. Among others the following nodes are created:
- /apps/myapp/src
- /apps/myapp/install
- Right-click the folder /apps/myapp/src that will contain the Test bundle, select Build, then Create Bundle ....
- Enter the following values for the bundle properties:
- Symbolic Bundle Name: com.mycompany.test.TestBundle
- Bundle Name: Test Bundle
- Bundle Description: This is my Test Bundle
- Package: com.mycompany.test
Click Finish.
The wizard creates the following elements:
- The node com.mycompany.test.TestBundle of type nt:folder. It is the bundle container node.
- The file com.mycompany.test.TestBundle.bnd. It acts as deployment descriptor for your bundle and consists of a set of headers.
- The folder structures:
- src/main/java/com/mycompany/test. It will contain the packages and the Java classes.
- src/main/resources. It will contain the resources used within the bundle.
- The Activator.java file. It is the optional listener class to be notified of bundle start and stop events.
The following table lists all the properties of the .bnd file, their values and descriptions:
| Property |
Value |
Description |
| Export-Package: |
* |
The Export-Package header defines exported packages for the bundle (comma-separated list of packages) |
| Import-Package: |
* |
The Import-Package header defines imported packages for the bundle (comma-separated list of packages) |
| Private-Package: |
* |
The Private-Package header defines private packages for the bundle (comma-separated list of packages) |
| Bundle-Name: |
Test Bundle |
Defines a short, human-readable name for the bundle |
| Bundle-Description: |
This is my Test Bundle |
Defines a short, human-readable description for the bundle |
| Bundle-SymbolicName: |
com.mycompany.test.TestBundle |
Specifies a unique, non-localizable name for the bundle |
| Bundle-Version: |
1.0.0-SNAPSHOT |
Specifies the version of the bundle |
| Bundle-Activator: |
com.mycompany.test.Activator |
Specifies the name of the optional listener class to be notified of bundle start and stop events |
For more information on the bnd format, refer to the bnd utility used by CRXDE to create OSGI bundles.
To create the HelloWorld Java class within the Test Bundle:
- In CRXDE, in the Navigator tab, navigate to /apps/myapp/src/com.mycompany.test.TestBundle/src/main/java. Right-click it, select New, then Class.
- Set HelloWorld as Name. Click Finish.
The HelloWorld.java file is created beside Activator.java and displays following code in the main pane:
package com.mycompany.test;
public class HelloWorld {
}
- Add the following lines into the body of the HelloWorld class:
public String getString(){
return "Hello World!";
}
Save the changes.
To build the Test Bundle:
- In CRXDE, in the Navigator tab, right-click the .bnd file and select Build Bundle.
The Build Bundle wizard:
- Compiles the Java classes.
- Creates the .jar file containing the compiled Java classes and the resources and places it into the myapp/install folder.
- Installs and starts the bundle in the OSGI container.
To see the effect of the Test Bundle, create a component that uses the Java method HelloWorld.getString() and a resource that is rendered by this component:
- Create the component mycomp under myapp/components.
- Edit mycomp.jsp and replace the code with the following lines:
<%@ page import="com.mycompany.test.HelloWorld"%><%
%><%@ include file="/libs/foundation/global.jsp"%><%
%><% HelloWorld hello = new HelloWorld();%><%
%>
<html>
<body>
<b><%= hello.getString() %></b><br>
</body>
</html>
- Save the changes.
- Create the resource test_node of type nt:unstructured under /content.
- For test_node, create the following property: Name = sling:resourceType, Type = String, Value = myapp/components/mycomp.
- In your browser, request test_node: http://<hostname>:<port>/content/test_node.html.
- A page is displayed with Hello World! in bold.
In CRXDE you can display the file error.log that is located on the file system at <crx-install-dir>/crx-quickstart/server/logs and filter it with the appropriate log level. Proceed as follows:
- In CRXDE, in the Console tab at the bottom of the window, click the arrow beside the Display Selected Console icon and select CQ.
- In the drop-down menu, set the log level. It can be one of the following values: trace, debug, info, warn or error.
The error.log is filtered according to the log level and displayed in the tab.
To debug with CRXDE:
- Stop the CRX server.
- Start the CRX server in debug mode: on the command line, change to the directory <crx-quickstart> and enter the following command:
java -debug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=30303 -jar <quickstart-name>.jar
Note: you can also enter the following command: server/start -d
- In CRXDE, in the top menu bar, select Debug, then Attach Debugger.
- As port number, enter 30303 (as defined as the address argument of the Xrunjdwp option). Click OK.
- The Debug Perspective is displayed. You can now set breakpoints in the .jsp and .java files.
To switch back to the standard perspective, use cmd + F8 or terminate the debug session by using the Disconnect button in the Debug view.
Note
When Quickstart forks a new process it does not start the JVM
with the debug options. You can prevent forking by specifying the
-nofork command line option.
CRXDE stopped working Remove the .crxde folder from your home folder.
Note: on Windows the .crxde folder is under c:\documents and settings\<YOUR_USER_NAME>.
CRXDE and CRXDE Lite include integration with Apache Subversion (SVN), which allows developers to create a Subversion working copy inside their CRX repository without having to synchronize the file system as an intermediate step.
With SVN integration, you can do the following:
- Check out of an existing CQ5 project from SVN into content subtree.
- Modify a resource like a script and check it back into the SVN repository.
SVN integration has been designed with those use cases in mind where ease of use and simplicity is more important than complex development and processes. Any additional svn functionality is available via the CRX/CQ5 FileVault command-line tool vlt and stand-alone Subversion clients. (For example, use one of these tools to initially import the content into the SVN server.)
With SVN integration, you can perform troubleshooting, performance tuning, quick fixes, and prototyping without external tools, and maintain the source code control at the same time.
In a single-developer project or small, agile teams, where a full project setup is not possible or too costly, but there is a requirement to keep code changes under version control, the CRXDE family of tools provides a simpler alternative to source code control using external tools and intermediate, manually managed working copy in the filesytem.
Typical, intended usage of SVN integration in the CRXDE family of development environments is as follows:
- A developer checks out an existing content application/project from SVN into content in his or her personal development repository; the command line vlt tool and svn client can be used for importing an unversioned content project into SVN. (Unversioned content can also be imported directly from a repository to SVN with the import operation.)
- The developer performs basic development tasks (changes source code in Java bundles or scripts, and so on) then tests the changes locally.
- The developer checks in the changed content back to the SVN repository.
- The developer checks the status of the content working copy and updates the local source code (content) with changes from other developers (changes from SVN), then repeats the cycle.
SVN Integration Features/Design Implications
The focus on simple usage resulted in a few design decisions, which are important to understand before using SVN integration:
Local, single user content repository instance The integration has been designed to work with a local content repository (CRX or CQ5 instance), used by a single developer. Multiple users connecting to the same content repository instance (development instance) and using SVN integration on the same content is not supported.
Implicit SVN operations Certain SVN operations are done implicitly, for example, nodes added to the content tree under source control are automatically added and committed to SVN when checking in (same for deletions).
SVN status on JCR nodes The integration is based on many-to-one mapping between JCR nodes and FileVault representation thereof. This intermediate representation, based on files and folders, is then synchronized one-to-one with Subversion. SVN status is shown for individual repository nodes, and is mapped from "real" SVN status on FileVault files (for example, .content.xml representing potentially many nodes).
Conflict resolution There is very limited support for SVN conflict resolution, so it is recommended to do frequent updates and short update-commit cycles.
Where more explicit control over SVN operations or full support for distributed development in larger teams is required, the integration based on stand-alone FileVault vlt client and Subversion client can be used (such as this project setup based on FileVault, Eclipse, Subversion, and Maven).
With CRXDE you can perform the following operations through the tree context menu (Version Control):
- Import into SVN (initial checkout)
- Check out from SVN
- Export from SVN
- Update from SVN
- Commit to SVN
- View the SVN status
The following image illustrates the Version Control context menu:
Importing the CRX repository into SVN
Importing allows you to put a project under version control that was initially created with CRXDE (rather than in SVN). Use this command to initially check out content to SVN.
To import the CRX repository into SVN:
In CRXDE, in the Navigator tab, right-click the folder that you want to import into SVN, select Version Control, and then Import.
Enter the URL, User Name, Password, Path, and optionally a Message. Click OK. The files are imported into SVN.
Checking out from the SVN server
In CRXDE, in the Navigator tab, right-click the folder that you want to contain the checkout in, and select Version Control, then Checkout.
Enter the URL, User Name, Password, and Path. Click OK. The files are checked out from SVN into the desired location.
Exporting from the SVN server
Exporting from the SVN is similar to checking out except that this action does not create a working copy.
In CRXDE, in the Navigator tab, right-click the folder that you want to export, select Version Control and then Export.
Enter the URL, User Name, Password, and Path. Click OK. The files are exported from SVN into the desired location without version control.
When you create or modify a file or a folder that is under version control, it is automatically added to the version control.
To commit a change:
In CRXDE, in the Navigator tab, right-click the folder that you want to commit, select Version Control, and then Commit.
Enter a message and click OK. Your changes are committed.
To update a file or folder from SVN:
In CRXDE, in the Navigator tab, right-click the file or the folder that you want to update, select Version Control and then Update.
If not already logged in, you are prompted for a user name and password. Click OK. CRXDE updates the file or folder.
You can view the SVN status, either by looking at the icons on the nodes in the Navigator tab or by doing the following:
In CRXDE, in the Navigator tab, right-click the file or the folder under version control, select Version Control and then Status.
View the SVN status in the Console tab.
CRXDE 1.0 supports the following product versions.
CRXDE supports this version out of the box.
CQ 5.3 is based on the CRX 2.0 release (only released as a part of CQ 5.3). To ensure compatibility of CRXDE 1.0 with CQ 5.3, the CRXDE Support module from CRX 2.1 release should be installed into CQ 5.3.
To use CRXDE with this release, you have two options outlined in the following subsections.
CQ 5.3 with CRXDE Support Package Upgraded to Version 2.1
To upgrade the CRXDE Support package in your CQ 5.3 instance to version 2.1 you have to obtain the upgrade package and install it into your CQ 5.3. There are two ways of obtaining the package.
Download from Package Share (recommended). The CRXDE Support package is available on Day Package Share, in the section Public » Day » CQ 5.3.0 » upgrade. The package is called cq53-update-crxdesupport. To install it:
- Go to Packages in your CQ 5.3 instance
- Select Package Share
- Log in to Package Share using your day.com user account
- Navigate to the Public » Day » CQ 5.3.0 » upgrade section
- Click Download for cq53-update-crxdesupport-2.1.0.zip
- After downloading, the button changes to Downloaded; click this and the CQ5 Package Manager will open
- Install the package
Extract the updated components from CRX 2.1 quickstart jar file. If you don't have access to the Package Share from your instance, you can also get all the required components from a CRX 2.1 quickstart jar file. Please follow these steps:
- Extract the CRX support package from the CRX 2.1 quickstart jar file:
- unpack the CRX 2.1 quickstart file in an empty folder:
java -jar crx-2.1.0.20100426-<edition>.jar -unpack
- in the folder where you unpacked CRX 2.1, unzip the initial content file:
crx-quickstart/repository/install/crx-initial-content-2.1.0.zip
- using the CRX Package Manager upload and install the CRX 2.1 crxde-support package from the unpacked zip file:
jcr_root/etc/packages/day/crx210/product/crxde-support.zip
- Then install additional packages:
- navigate to the extracted crx-initial-content-2.1.0
- navigate to jcr_root/libs/sling/install
- upload the following jars to /libs/sling/install (e.g. using WebDAV):
- org.apache.sling.commons.auth-0.9.0-R925144.jar
- crx-auth-token-2.1.0.jar
After upgrading the CRXDE Support package, restart the instance. Start CRXDE and connect to the instance to check, whether the tool works correctly. Pay special attention to checking, if you can execute server-side functionalities (like bundle compilation, product creation, CRXDE operations).
After you have successfully installed the upgrade and tested your instance, your CQ 5.3 is ready for developing with CRXDE.
CQ 5.3 with CRX Repository Upgraded to Version 2.1
Please see Upgrading CQ 5.3 to CRX 2.1 for upgrade instructions.The procedure includes the required update of the CRXDE support package to version 2.1.
After you have successfully upgraded and tested your instance, your CQ 5.3 is ready for developing with CRXDE.
|
|
See note on SVN integration in the Release Notes: http://dev.day.com/docs/en/crx/current/release_notes/overview.html#Important%20Notes
[1] http://sling.apache.org/site/internationalization-support.html
we are aware of some startup performance issues with CRXDE when it is running on windows. We are currently investigating to find out the possible reasons and will post any news here as soon as a solution has been found.
Because our java source code is not in the JCR does that mean that CRXDE cannot be used to edit our java classes?
Thanks,
-james.
I have a CQ project deployed in CQSE. I would like to build package using maven and deploy it in Tomcat environment. Could you pls give me some direction to this. Thanks for the help.
Sumit
day-communique (at) googlegroups (dot) com
http://dev.day.com/discussion-groups/content/lists/cq-google/2010-09/2010-09-21__day_communique_Running_CQ5_IDE_under_Windows_7_Professional_Alan_Yeo.html
So CRXDE and 64bit Java 6 don't mix?
The 64bit Java 6 shouldn't be a problem in itself here. However, as 64b has higher memory overhead than 32b, it might potentially make the Eclipse's RCP in which we're running more resource hungry. It could be the problem you've faced (and we have more challenges on Windows compared to Macs or Linux with CRXDE).
BTW did you manage to have it run?
Any reason?
org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:342)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
What file is it trying to parse that is empty or corrupt?
Intel Core 2 Duo 1.66GHz
Windows XP, 3GB RAM
of the repository (due to eclipse-specific access patterns).
File -> Preferences -> General -> Workspace, uncheck the "Build automatically" pref
2. Can I use fully featured svn plugin, subclipse?
1. CRXDE is a standalone binary, based on Eclipse RCP platform. At the moment you cannot install it as a set of packages into your instance of Eclipse. CRXDE is generally recommended for simpler development environment setups, where you don't have many dependencies on external integrations or need fully-customized Eclipse instances.
For development based on standalone Eclipse with full customization, or for any other IDE, you can use the process based on the "vlt" tool as described in Section "Developing with Eclipse" (http://dev.day.com/docs/en/cq/current/developing/developmenttools/developing_with_eclipse.html)
2. See "Developing with Eclipse" above.
If it is still not working, please post all details (like logs exerpts) to the following mailing-list:
day-communique (at) googlegroups (dot) com
CRXDE version=1.0.0
CQ version = 5.3
CRX version = 2.1
You want me to try with CRXDE 1.0.1?
- preferences and tab positions aren't saved between sessions (very annoying)
- Eclipse plugins: can they be installed, and if so, how? I'd like the Eclipse Color Theme plugin, specifically.
agreed. it's a known (and tracked) issue.
> - Eclipse plugins: can they be installed, and if so, how? I'd like the Eclipse Color Theme plugin, specifically.
that's unfortunately not supported
unsupported value of request parameter 'cmd':import
Can anyone tell me what that means?
-B
If i connect to the CRX-Server by browser (CRXDE Lite) i can see and work with the /content node. Is there a way to get the node visible in the Eclipse based CRXDE?
My environment:
Win7 Prof 64 bit
CRX 2.2.0.20112018
CRXDE 1.0.1
eg:- what cq:- panel mean , what cq: widget means etc. There are large number of such properties there . I need details description for that so that i can choose correct one at correct time.
thank you
what could be the reason
there is one small query.
In crxde lite we have project structure as /etc, /apps. /libs, /content
here /content folder is created by system.But in crxde we have only three folder viz; /apps, /etc, /libs. when i check in my project folder from crxde i could only check in from the above said three folder only. i just request you to please let me know would it create a working apps when i checkout from SVN.
or else plz let me know how to create /content folder in CRXDE also.
Thanks,
CRXDE is not starting, It was not doing anything after entering the cq server URL http://localhost:4503 and the user id and password on Repository login box. I don't see any errors or log files associated with that . Till yesterday it was working fine, all of a sudden it stopped functioning.
Can some one please suggest the solution.
Thanks for your help
If this doesn't solve your issue I suggest to post to the CQ5 dedicated forum:
http://forums.adobe.com/community/adep/ces/web-experience-management
http://forums.adobe.com/community/adep/ces/web-experience-management
1) Reference item find.ext not found for action null
2) Project facet jst.web has not been defined. It is used in plugin org.eclipse.wst.jsdt.web.core.
3) Project facet wst.web has not been defined. It is used in plugin org.eclipse.wst.jsdt.web.core.
4) Project facet wst.web has not been defined. It is used in plugin org.eclipse.jst.common.project.facet.core.
Can you please help....
CRXDE doesn't like imports from com.day.cq and net.sf.ehcache. Where would I go about defining those references in crxde?
Thanks
To try and determine the core issue we suggest that you post all details (what you're trying to achieve, what you've implemented/configured so far, any log output) to our dedicated CQ5 forum:
http://forums.adobe.com/community/digital_marketing_suite/cq5
Hope that helps.
Apparently it has something to do with the following Eclipse bug : https://bugs.eclipse.org/bugs/show_bug.cgi?id=241343
Any solutions?
http://forums.adobe.com/community/adep/ces/web-experience-management. Thank you.
Thank you for your daily review. Typos have been corrected.
Alex
Still unable to locate that version. When will it be released?
This feature is not currently available. If you wish make a feature request, you can create a ticket with our support system at http://www.day.com/daycare.html
Hope that helps. Alex
If you use the standard directory:
- /apps/<project-name>/components
Then it should work (have just confirmed that with a test).
You can also look at this directory, and the sample component to check properties in detail.
Hope that helps.
I right-clicked on the folder /apps/test02/components also and the context menu "Create" doesn't contain "Component", "Dialog", "Template". Please look at the screenshot from CRXDE:
https://www.dropbox.com/s/w75vdw2z423us2y/CRXDE_1.png
CQ is not installed on my computer because in chapter "Getting Started with CRXDE" I read:
"1. Install CQ or CRX"
So I though that CQ isn't required now.
But certain elements (eg templates and components) are CQ specific, so will not be available in the context menu if you are using CRX.
I'll register an issue so that this is made clear in the documentation above.
Will you be using CQ at any point? If so, don't forget that we provide a range of training courses - just ask your support contact. The CQ5 forum also provides a platform for asking questions and swapping experiences about CQ (and CRX):
http://forums.adobe.com/community/digital_marketing_suite/cq5
Hope that helps.
having problem in starting up the crxde?
Can some one please suggest the solution.
java.lang.reflect.InvocationTargetException
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
... 14 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 18 more
Root exception:
org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 18 more
!SESSION 2012-10-12 16:25:33.257 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_32
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.osgi 4 0 2012-10-12 16:39:23.894
!MESSAGE Application error
!STACK 1
java.lang.reflect.InvocationTargetException
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
... 14 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 18 more
Root exception:
org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 18 more
!SESSION 2012-10-19 16:07:18.355 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_32
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.osgi 4 0 2012-10-19 16:07:31.667
!MESSAGE Application error
!STACK 1
java.lang.reflect.InvocationTargetException
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
... 14 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 18 more
Root exception:
org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 18 more
!SESSION 2012-10-19 16:07:51.857 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_32
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.osgi 4 0 2012-10-19 16:08:07.593
!MESSAGE Application error
!STACK 1
java.lang.reflect.InvocationTargetException
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
... 14 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 18 more
Hope that helps.
!SESSION 2012-12-07 15:15:52.959 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.core.resources 2 10035 2012-12-07 15:38:56.513
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!ENTRY org.eclipse.osgi 4 0 2012-12-07 15:39:37.279
!MESSAGE Application error
!STACK 1
java.lang.reflect.InvocationTargetException
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
... 13 more
Caused by: org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 17 more
Root exception:
org.eclipse.core.runtime.CoreException: Error during IDE intialization
at com.day.cq.ide.util.plugin.Policy.throwError(Policy.java:37)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:352)
at com.day.cq.ide.init.SetupWorkspaceOperation.execute(SetupWorkspaceOperation.java:118)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at com.day.cq.ide.CQDEApplication.start(CQDEApplication.java:62)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.day.cq.ide.init.SetupWorkspaceOperation.initIDE(SetupWorkspaceOperation.java:298)
... 17 more
If this doesn't solve your issue I suggest to post to the CQ5 dedicated forum: http://forums.adobe.com/community/digital_marketing_suite/cq5
I appreciate your help/pointer.
Reza
You can use the Package Manager to create a package with a filter definition that contains said jar files. When you then download that package, you can unzip it in order to get to the jar files.
If you are using the 5.6 version, you should use CRXDE Lite. I suggest you have a look at http://dev.day.com/content/docs/en/cq/current/core/developing/development_tools/developing_with_crxde_lite.html#comments. If this doesn't help you, I suggest you bring this to our dedicated forum (http://forums.adobe.com/community/digital_marketing_suite/cq5).
Itis a prime location for exchanging ideas and experiences related to AEM - you can ask for more details there.
Hope that helps,
Guillaume
I want to sink the local environment with the development environment. When i commit the code from cxde, it will move to development environment.
thanks
Sumit
http://dev.day.com/content/docs/en/crx/current/developing/development_tools/developing_with_crxde.html#Integrating%20with%20SVN
and
http://subversion.apache.org/
If you have specific questions related to sync you can ask them on the AEM forum:
- http://forums.adobe.com/community/digital_marketing_suite/cq5
You will reach a wider audience and receive a greater response.
Hope that helps.
Note: Customers with DayCare user accounts need to create a new account for use on day.com.