I am writing a custom editor for eclipse, it works fine when I run it as an eclipse application, but when I install it through an update site, the editor has no content when opened. How do I fix this?
Source code for plugin, feature, and update-site: https://github.com/programmerjake/peg_parser_generator-eclipse commit 4c01fba773ea2cd60ab0efd08fae1331b18b62bc
update site url: http://programmerjake.tk/peg_parser_generator-eclipse/tk.programmerjake.peg_parser_generator.update_site/ version 0.1.1.5
The reason is that the plugin built didn't contain the actual editor classes, because the jvm version was set to 1.6 but the source code contains version 1.7 features.
Related
Is there a way to configure AEM into an IDE like IntelliJ,Eclipse...
So that the IDE shows the errors on my project before I compile it even if I put it outside the source folder like for example the components created.
If possible both the .java and .jsp
I'm not entirely sure what you mean by outside the source folder, but have you taken a look at adobe's documentation?
They have instructions for IntelliJ + AEM with Maven. It also instruct on jsp support as well. It's for 5.6.1 but it should be valid for 6.x as well.
https://docs.adobe.com/docs/en/cq/5-6-1/developing/developmenttools/howto-develop-aem-projects-with-intellij.html
Here's one for Eclipse
https://helpx.adobe.com/experience-manager/using/creating-aem-project-using-eclipse.html
They also have a more generic set of instruction
https://docs.adobe.com/docs/en/cq/5-6-1/developing/developmenttools/how-to-build-aem-projects-using-apache-maven.html#How-To%20Work%20with%20JSPs
Yes, you can maintain CRX data(AEM folders like /etc, /apps, /content, etc) in an IDE like eclipse. This will help you iron out all the compilation errors using features of IDE. Make use of this eclipse plugin called vaultclipse. You can install it from eclipse marketplace.
There is also another plugin called AEM plugin, details on how to use it here.
I have an Eclipse plugin that was originally written (not by me, and I don't have access to the original developer) that I'm trying to update for Eclipse Luna, because it stopped working when my team updated to Eclipse 4.4.
I downloaded the Luna Plugin development version, cleared a few warnings, updated some broken code, fixed a few bugs, and tested with "Run As -> Eclipse Application
This worked fine: all the views showed up, the preferences pages, etc.
So then I tried to export the plugin so I could test on a fresh installation of vanilla Eclipse Luna. I did that by using the Export Wizard:
And generated a deployable set of jars with said wizard:
I copied the generated folder (which contains all the jars appropriately) into the dropins folder of my fresh vanilla Eclipse Luna and started it up.
Unfortunately, I got the following error:
Which led me to this SO question and this Eclipse bug report, which explains that I have a 2.x style plugin that uses the plugin.xml instead of an OSGi style manifest.mf. Continuing my search, I found this SO question, which was directed at a 3.x version of Eclipse, but I used the 4.x equivalent:
Which I used with the following options checked:
And I accepted all the changes in the previous pane after the (long-running) changeset. However, upon deploying to my vanilla install, I got the same error about the plugin converter. That led me back to this SO question, which recommending installing the Eclipse 2.0 plugin support package. I did so and restarted Eclipse. The error in my error log did stop showing up, however the view/preferences/etc for my plugin are still not showing up. The plugin does show up under Help -> Installation Details -> Plug-ins, but doesn't seem to be interacting at all.
The text of the plugin.xml can be found here at Pastebin. The text of the MANIFEST.MF can by found at this other Pastebin link
Any suggestions for getting my plugin to work through the manual export so the other developers on my team can test my changes before I try releasing the update to the world?
The short question, is when creating dynamic web project (1.6 jdk) I can see all file types to create but there is no option for jsp. To add to that when I check file associations there is no JSP editor to select from.
A slightly longer version is I simply want to edit JSP files, I have Juno EE version installed and it says web tools platform is installed and everything works just fine.
However while everything works, there was no *.jsp in file associations and on adding it there was no JSP editor in the list. This is an out of the box Juno EE.
So I checked installed plugins and it tells me that web tools is installed, there is an icon and a load of plugins. They are all listed under Java EE in the plugin/installation list. I even tried installing just 'java web develop tools' which lists as 'tools for working with jsp' but when I do that I get ""Eclipse Java Web Developer Tools" will be ignored because it is already installed." however I cannot uninstall it because it's part of Java EE eclipse platform. I have no other plugins installed that might have broken this, however it has taken some time to get all the settings good so I'd rather not install it all again.
So I tried to install the full WTP by hand and it said some things were already installed, but it installed others. However, still no JSP editor. Hence why I tried a dynamic web project to see if I could create JSP and it wasn't listed.
So, eclipse base install has absolutely everything (xml, html editor, java editor, all the tools) but just not JSP.
My JDK is fine as dynamic web project is not created unless you have a valid 1.6 or above.
Anyone help?
It seems your missing Eclipse web developer tools and Eclipse java web developer tools.
Help>Install new software>http://download.eclipse.org/releases/juno, select appropriate items under Web,XML,Java EE
Hope this helps
In Eclipse Juno, select File/New/Other, then type in jsp in the wizard field. Select jsp file or jsp tag and there you go. Hope that helps.
Try to install Eclipse with Java EE developer.It should work.
You can go to Eclipse Market place and search for "Java EE Developer tool". On clicking it you should be able to see if your Web developer tool is selected or not. Please select that option and your issue will be resolved.
Check your path. Make sure it is pointing to at least a 1.6 version of Java. Restart Eclipse. That fixed it for me.
If you have installed every thing proper and still it is not showing JSP option while creating new .jsp file then click to the web icon on top right corner of eclipse. If it doesn't work then you need to install updated version of eclipse.
I also faced the same problem; I looked through the "Web,XML,Java EE..." installables available at under Kepler downloads:
and that brought me the New->'JSP File' context menu item.
I checked in eclipse/java plugin project from svn repository.
Eclipse automatically builds the code to show hundreds of errors.
It seems like that eclipse doesn't properly link to the plugin libraries. Googling to find this site that I need dependencies and other tabs in plugin.xml.
What might be wrong? I use Indogo(3.7) on Mac OS X 10.7.4
I used Indigo (3.7) for my Mac, but it happened so that the plugin was built on Helios (3.6). When I run the plugin using Helios, I got the project compiled without errors.
It seems like that some of the plugins are (heavily) version dependent.
Looks like you got the base XML editor instead of the plugin.xml editor.
This is probably caused by your not having the eclipse plugin development environment (PDE) enabled in a new workspace.
Try creating a new plugin project (this will enable the necessary plugin tools), or go to the preferences and enable the "correct" capability. Since the capabilities seem to change from release to release, I always use the first method and then delete the new project.
I have Eclipse PDT 3.0.2 All In Ones installed with Aptana Studio 3.2.0 plug-in. When I create a web project (Project Natures/Web is set to primary) with javascript file and try to use code completion (ctrl + space) this results in "No Default proposals" message. I can right-click on project and select "Configure/Convert to JavaScript Project" though but this is the feature of Eclipse not Aptana.
P.S. CSS and HTML code completion works fine.
That did it. I have changed an editor associated with .js files to JavaScript Source editor instead of JavaScript Editor which was set as default at installation. It would be nice if they added "Aptana" after the name of editor to distinguish it from other editors.