I cannot add web module to IntellIj 9 Ultimate - intellij-idea

I wanted to add a JSP to my project and I think this is most conveniently done by adding a web module. Unfortunately when I do File->New Module the only types available are Java Module and Android Module.
I have tried turning on all likely plug-ins but no Web (or other module type, except Android) Module type appears.
Help About says it's IntelliJ 9.0.2 Ultimate (Personal License). The Register page appears to have a satisfactory license key.
Running on Windows XP.

You need to select the Java Module, and if your JEE integration plugin is enabled, you will be able to select the "web facet" later in your module creation.
You could also install the maven plugin and create a maven module based on the maven-archetype-webapp archetype.

Related

Create GWT project in Intellij IDE

I'm beginner in using IntelliJ IDEA IDE and I want to create a new GWT project. I have added the GWT plugin to IntelliJ IDEA and now and I want to create a project. I googled but I didn't find a helpful tutorials or examples. Did you have guys a helpful tutorials to start. Thanks in advance.
Do not use the GWT project builders from IntelliJ or Eclipse. Both generate projects which use the same class path for client and server. In todays GWT development it is common to use a separate class path for client and server.
Depending on the server you prefer to use, choose:
https://github.com/tbroyer/gwt-maven-archetypes
in case you want to use Jetty or Tomcat on the server side or:
https://github.com/NaluKit/gwt-maven-springboot-archetype
in case you want to use Spring Boot.
How to create a new GWT project in IntelliJ
Create a new project: File → New... → Project...
Select Java EE (Legacy).
Select Java 8.
Do not use Java 9 or above unless you know what you're doing. Yes, GWT 2.8.2+ works with Java 11+, but you'll need to open some internal modules for it to work. If you just want to learn GWT, stay with Java 8.
In Additional Libraries and Frameworks, check ☑ Google Web Toolkit.
In GWT SDK, fill in the path to your GWT installation.
Check ☑ Create sample application and introduce a fully qualified class name for the main class.
Click Next, and fill in the rest of needed info for your new project (this has nothing to do with GWT).
You'll end up with something like this:
If you followed the steps closely, the sample project should be fully functional. IntelliJ should've created a Run configuration for you, too, so you can run the GWT app right away and see it in action:
This is all explained in the official help documentation for IntelliJ 2020.1, which was the last version to include GWT support out of the box.

Plugin Compatibility Issue Eclipse Oxygen (4.7) and Java 9

We upgraded one of our Eclipse 3.x plugins to work with Java 9.
But when we generated the plugin update site content, and used Eclipse Update functionality to install the new version of the plugin, we encountered the following error in Eclipse Oxygen.
Removing part descriptor with the 'pluginxxx.bla.bla' id and the 'bla bla' description. Points to the invalid 'bundleclass://org.eclipse.ui.workbench/org.eclipse.ui.internal.e4.compatibility.CompatibilityView' class.
This error also appears due to some of the bundled plugins of Eclipse Oxygen itself.
After a hard week we had to
Uninstall our plugin
Remove the older versions of the plugin from the Eclipse/plugins folder
Export the plugin as a deployable plugin under the eclipse plugins directory. (Eclipse/plugins/blabla.jar)
Restart Eclipse and it worked.
Right click the eclipse plugin project and Run as "Eclipse Application" works fine, but installing the plugin from an "Update Site" causes the plugin to fail loading.
We could not find a solution yet, but it certainly effects our delivery of the plugin. The plugin is used by almost 500 CS students on their personal computers, and 200 lab computers. So the update should be installed using regular Eclipse Update functionality, not by copying the jar into the plugins directory.
Was there a better way to fix this, or something quicker we could've tried (in case this happens again)?
Update (7 days into the problem)
We have a workaround:
Export the feature project with the following settings in the Export Wizard
Destination/ Directory: Folder of your Plugin Update Site project
Options/ Package as individual JAR archieves (selected)
Options/ Generate p2 repository (selected)
Options/ Allow for binary cycles in target platform (selected)
Options/ Use class files compiled in the workspace (essentially selected)
Install (or update) the plugin from the local (or remote) plugin update site, and the CompatibilityView problem is solved.
In order to have the category listing displayed correctly during install/update new software operations, we added a category.xml file (File/New/Other/Plugin-in Development/Category Definition) in the update site project, defined the categories, and added the feature (versioned as "qualifier").
This is certainly not the way it should be, and we just hope it will be solved in the future Eclipse releases.
By the way current Eclipse Photon integration version has the same problem unfortunately.

How to ensure eclipse plugin has required bundles available?

I'm just starting to develop a new eclipse plugin where I want a web application server running in Eclipse. I found a nice blog, OSGi as a Web Application Server, that describes how to do this. The author suggests creating a target environment for my bundle requirements, and some of those bundles get pulled in from the Equinox Project SDK (now called Equinox Target Components in Juno). I notice that the tutorial project runs fine when my target platform is the platform I created in the tutorial, but fails to start when it is the default platform. So, now for my question...
If I need bundles that are not part of the default, how will my plugin project get access to those bundles? Will I need to deploy them along with my plugin? How would I know if the user's eclipse does or does not already have those required bundles?
You was not much clear about what kind of application you are developing. Running a web server in an Eclipse IDE as a plugin don't make any sense to me. This kind of server application is best just running on top of Equinox.
Anyway, the right path is to create a "Product Configuration" file and add categories that contains the needed bundles (go to File/Plug-in Development/Product Configuration).
With this file you can run an instance of the product (inside the IDE) and can export it (create a zip containing all needed bundles)
And if you want to able your user to install plugin inside his IDE you must create a P2 repository (using a Target Definition File) and expose the exported directory within a Http server. You could research about Tycho to build this kind of components in a maven style.
Well, I'm not sure if re-inventing the wheel again is really sufficient.
You might take a look at Pax-Web for inspiration on how to do it, or take a look Apache Karaf as a OSGi-Container (using Pax-Web). Or even better start contributing to one of the two :-)

IntelliJ 12 Grails 2.1 Configuration - Grails SDK not configured

I feel like I'm missing something simple at this point. I upgraded to grails 2.1.1 from 1.3.7 while running IntelliJ 10, recently I upgraded to IntelliJ 12 and imported all settings. Somehow in the project in IntelliJ 12, I have no grails SDK.
My Global Library has grails 2.1.1 defined with all the correct .jars included, however, the Tools menu is missing the "Grails" sub-menu, and attempting to run the app gives the error message that Grails SDK is not configured.
If I create a new project for grails, the SDK configures correctly and Grails shows in the Tools menu. What am I missing preventing me from adding the Grails SDK to this project? Thank you, community, for your time and suggestions.
You do not have to create a new project.
Had the same problem, and it took me quite some search to resolve it:
right click your Grails module
click "Add framework support"
select "Groovy"
The dropdown next to "Use library" will allow you to choose a grails library.
If the dropdown is empty press "create" and choose your grails library directory.
Grails SDK is configured then
With Intellij 16 right click on your project in the right hand project pane.
Choose Grails->Configure Grails SDK.
If you're using the grails wrapper I would point to that SDK:
/Users/your user/.grails/wrapper/2.5.2/grails-2.5.2
I have the IntelliJ 12 too, to run app i just click in 'File' -> 'Create Project', select 'Grails Project'
Click Next,
Click em Create, select the folder, who contain the Grails 2, and Voila. :-)
If you has the project before, run in project 'grails integrate-with --intellij' or run import project, and create a Grails SDK
I found a symlink that points to the latest version in:
~/.sdkman/candidates/grails/current
I'm using SDKMAN 4.0.37
Pointing Intellij at that location will allow you to switch versions using sdkman.
Not really an "answer" here, but after seeing similar troubles with IDEA I went ahead and just created a new project and copied my source in and resolved my issues, if not solving the actual problem.
I am working with IntelliJ 12.0.1 ultimate.
I have installed Grails 2.3.1 on my computer, but always got errors when trying to specify it as a Grails SDK-
"failed to create library. Looks like Grails distribution in specified path is broken. Cannot determine version."
I tried with Grails 2.3.0, but got the same error.
Then, I tried my luck with Grails 2.2.4, and I could finally get it work.
Creating a New Project will actually not overwrite any existing code; just point it at your existing project directory, select Grails and open it up.
Your project will now complain that there is no Grails SDK; just point it at your Grails dist and you are good to go.
Recently, I've encountered a similar type of issue. I have the grails SDK folder, but OK Button not enabled when trying to configure from the project. Then we have installed the Grails Plugin in IntelliJ. Then OK Button enabled and grails SDK is configured into project.

Force Eclipse (Helios) to use a newer version of SWT at application runtime

I'm developing an RCP project using Eclipse-Helios.
The version of SWT that is installed (in the plugins directory) is [org.eclipse.swt-win32-3.6.2, & org.eclipse.swt.jar]
I require new API functionality that is only available from swt-3.8. (specifically, I wish to set the custom colours, for an SWT color dialog before opening.)
I have downloaded 3.8.1 from the SWT/Eclipse downloads site [ http://download.eclipse.org/eclipse/downloads/drops/R-3.8-201206081200/#SWT ]
The SWT download is NOT a plugin (couple of jars, src.zip and some readme files), so I am unable to add it to my "Target Platform" (it doesn't appear as an available jar even after adding the containing directory in "locations")
I was unable to find an update site for SWT (or any site where i could get a plugin for the newer version)
If I add the swt.3.8.jar to my classpath (and then increase it's order-priority in the project build-path), I am able to access the newer api functionality from my code (as well as view the source).
When I run the application however, it seems as though the runtime is still using the older SWT jar, as i get an unknown method error, when attempting to access the newer functionality.
Questions:
Is there an SWT repository location that I can use to download a newer version of SWT using the eclipse install manager?
If not, is there a way I can force the runtime to ignore the older version (I assume via plugin.xml)?
Is there a better way to achieve what I am trying to do?
What is the difference between the two SWT jars currently in the helios plugins directory (as the 3.8 download only contains the win-32 version)?
Thanks in advance.
SWT is downloadable as a separate plugin here:
http://download.eclipse.org/eclipse/downloads/drops/R-3.8-201206081200/#SWT
Eclipse 3.8 contains regular plugins including the SWT (the win32 specific as well as the generic "org.eclipse.swt_.jar"). I am currently using the 3.8 version and they appear as plugins.
I also have Eclipse 3.6 (Helios) and I was able to import the swt plugins using the "File->Import->Plug-in Development->Plug-ins and Fragments" wizard. I just specified the eclipse 3.8 directory and could import them in my workspace. Once imported I can of-course use them to be included in the runtime environment. Eclipse should use the latest version automatically.