This page (revision-61) was last changed on 24-Sep-2019 16:53 by Albrecht Striffler

This page was created on 29-Jan-2014 10:44 by Albrecht Striffler

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
61 24-Sep-2019 16:53 11 KB Albrecht Striffler to previous

Page References

Incoming links Outgoing links
IntelliJ FAQ ...nobody
IntelliJ FAQ

Version management

Difference between version and

At line 5 added 18 lines
!!IntelliJ does not start with OSX Yosemite (no Java 1.6 installed)
With version Yosemite, OSX no longer bundles Java 1.6. Because of that, we have to tell IntelliJ to use the Java 1.8 (or newer) runtime instead. The best way to do this is to put a file "idea.properties" into the directory {{~/Library/Preferences/IntelliJXX/}}, specifying the correct runtime. You can also specify other properties like console buffer size and so forth. Your properties file could look like this: [idea.properties]. It's also ok to just use this file.
!!Create a new Plugin-Module
* right click on the respective parent module
* "new" -> "Module"
* select "Maven"
* select no archetype when asked
* Enter the name of your plugin for "Module Name"
* Change the entry of "Content root" using the "..." button, create new subfolder within the parent module named according to your plugin name, select this folder for "Content root" and "Module file location"
* hit next/finish
* (if your intelliJ is not configured to auto-import maven modules:) Import the project as maven module
At line 7 changed one line
Download the attached [code_styles.jar] and import them with File -> Import settings.
Download the attached [code_styles.jar] and import them with File -> Import settings.\\
\\
Also, under Settings, go to "File and Code Templates" (use search bar in Settings) and in the tab "Includes" adapt your File Header. Instead of the "Created by ... on... " use the following:
At line 9 removed 2 lines
!!Add copyright header
Download the attached [copyright.txt] and add it the following way:
At line 12 changed one line
[{Image src='copyright.jpg' height='250'}]
%%prettify
{{{/**
* @author Your Name (optionally your company)
* @created ${DATE}
*/}}}
At line 14 removed one line
The provided copyright.txt is for the denkbares GmbH, but can easily be changed to other firms or e.g. the university.
At line 37 added one line
!! IntelliJ Inspections
At line 39 added 3 lines
Check out the following How-To page: [How-To IntelliJ Inspections]
At line 46 added one line
At line 61 added one line
At line 63 added one line
At line 70 added 12 lines
!!Use Identical Path for JUnit and Maven Testing
Unfortunately JUnit in IntelliJ IDEA has a different path for executing JUnit tests in modules as it will have when testing in maven builds. You can change this unwanted default behaving by setting the default JUnit path in the Run Configuration default settings for JUnit:
Open Menu {{Run->Edit configuration}} and there go to {{Defaults->JUnit->Working directory}} and set the value to {{$MODULE_DIR$}}.
[{Image src='JUnit Default Path Setting.png' height=400px}]
After that IntelliJ IDEA will set the relative path in all JUnits just like Maven.
At line 83 added one line
At line 85 added one line
At line 87 added 2 lines
At line 90 added one line
At line 108 added one line
At line 110 added one line
At line 121 added one line
At line 136 added 6 lines
At line 152 added one line
At line 158 added one line
At line 160 added one line
At line 113 changed one line
# You now see the errors and warnings in the messages view and can go through them. You can hide warnings with a button in the tool bar of the view.
# You now see the errors and warnings in the Messages view and can go through them. You can hide warnings with a button in the tool bar of the view.
At line 173 added one line
%%warning There currently seems to be a problem with the eclipse compiler option using Java 8. If you are getting an error like "Error:java: source level should be comprised in between '1.3' and '1.7' (or '5', '5.0', ..., '7' or '7.0'): 8", switch back to Javac again.
At line 176 added one line
!!Java dock entries on OSX
At line 178 added one line
To remove the dock entries that IntelliJ spawns when compiling or running Tomcat, append {{-Dapple.awt.UIElement=true}} to your Java VM options.
At line 181 added one line
!!Migrating to Java 8 and JSPWiki 2.10
At line 183 added one line
Since the end of July, we migrated KnowWE to now use JSPWiki 2.10, Java 8 and Tomcat 8. Follow this section to migrate your own workspace/project in IntelliJ:
At line 185 added 3 lines
# Install JDK 8 and add and set it as the default in your JDK. In IntelliJ, go to File -> Project Structure... -> SDKs and add the JDK 8. Under Project also in Project Structure..., set it as the default.
# Download the current Tomcat 8 as the zip version. Unzip it analogous to your Tomcat 6 and set it your Tomcat configurations in IntelliJ.
#jspwiki.properties is now jspwiki-custom.properties. Instead of in local/WEB-INF/ it is now in local/WEB-INF/classes/. It has basically the same content as before, but you should nevertheless start again from the .default file and just migrate your individual settings like var.basedir to the new file.
At line 190 added one line
!!Java 8 and JSPWiki 2.10 issues
At line 193 added one line
!Java source level error
At line 195 added 27 lines
If you get an error like:
{{{
"Error:java: source level should be comprised in between '1.3' and '1.7' (or '5', '5.0', ..., '7' or '7.0'): 8"
}}}
you have to switch back to Javac as the compiler again. More info at [IntelliJ FAQ#View all compile errors of the project/workspace]
!SecurityManager/jspwiki.policy issues
If you have an error with content like
{{{
"Failed to start managers: File /IntelliJ%20Workspaces/denkbares/KnowWE-App/target/KnowWE-App-0.2-SNAPSHOT/WEB-INF/jspwiki.policy does not exist, or the SecurityManager prohibited access to it."
}}}
your problem is very likely a whitespace in the path to the jspwiki.policy file. The SecurityManager of JSPWiki 2.10 does not like that.
If the whitespace is in your workspace folder name, you can close IntelliJ, rename the folder, open IntelliJ again and then choose the new folder in the welcome splash screen after clicking "Open Project".
!Error with com.ecyrd.jspwiki....
If you get (class loading) exceptions involving the old pre 2.9. JSPWiki package naming while starting ab KnowWE, you most likely are dealing with one of the following issues:
# You are trying to start KnowWE with an old pre 2.9 JSPWiki plugin like the TablePlugin. Update or remove these plugins in your dependencies.
# There are leftover files in your workspace containing the old JSPWiki code with the wrong package names. Do a "Find in path" with "ecyrd" to quickly find them. Most likely you can delete or update them. In case the files are in one of the "Overlay" folders in KnowWE-Resources or KnowWE-App, you can delete them. Do a maven build afterwards.
This page (revision-61) was last changed on 24-Sep-2019 16:53 by Albrecht Striffler Top