From 5cfb45c76af67e4ed0a74bbadbe26674b5abe5f1 Mon Sep 17 00:00:00 2001 From: Clebert Suconic Date: Tue, 29 Sep 2015 15:47:29 -0400 Subject: [PATCH] adding note about IBM JDK After I spent a whole afternoon trying to make IBM JDK to work under IDEA, I decided to add a note on the doc so other would have a chance to have it working faster than I did. --- docs/hacking-guide/en/ide.md | 34 +++++++++++++++++++++++----------- 1 file changed, 23 insertions(+), 11 deletions(-) diff --git a/docs/hacking-guide/en/ide.md b/docs/hacking-guide/en/ide.md index 993cb2f9a2..8853780251 100644 --- a/docs/hacking-guide/en/ide.md +++ b/docs/hacking-guide/en/ide.md @@ -20,6 +20,18 @@ Once the project has been imported and IDEA has caught up importing all the rele run JUnit tests from with the IDE. Select any test class in the tests -> integration tests folder. Right click on the class in the project tab and click "Run ". If the "Run " option is present then you're all set to go. +### Note about IBM JDK on Idea + +If you are running IBM JDK it may be a little tricky to get it working. + +After you add the JDK to the IDE, add also the vm.jar specific to your platform under that jdk. + +``` +(e.g: JAVA_HOME/jre/lib/amd64/default/jclSC180/vm.jar +``` + +There's a [SOF Question](http://stackoverflow.com/questions/27906481/can-intellij-14-be-used-to-work-with-ibm-jdk-1-7/32852361#32852361) about this that could be useful in case you are running into this issue. + ### Style Templates for Idea We have shared the style templates that are good for this project. If you want to apply them use these steps: @@ -43,21 +55,21 @@ blue arrow. ## Eclipse -We recommend using Eclipse Kepler (4.3), due to the built-in support for Maven and Git. Note that there are still some +We recommend using Eclipse Kepler (4.3), due to the built-in support for Maven and Git. Note that there are still some Maven plugins used by sub-projects (e.g. documentation) which are not supported even in Eclipse Kepler (4.3). -Eclipse [m2e](http://eclipse.org/m2e/) is already included in "Eclipse IDE for Java Developers", or it can be installed +Eclipse [m2e](http://eclipse.org/m2e/) is already included in "Eclipse IDE for Java Developers", or it can be installed from [Eclipse Kepler release repository](http://download.eclipse.org/releases/kepler). ### Git setup It is strongly recommended to turn off the auto-updating of .gitignore files by the Git Team extension. Otherwise, it -generates new .gitignore files in many directories that are not needed due to the top level .gitignore file. To turn +generates new .gitignore files in many directories that are not needed due to the top level .gitignore file. To turn it off, go to Preferences->Team->Git->Projects and deselect the "Automatically ignore derived resources" checkbox. ### Annotation Pre-Processing -ActiveMQ Artemis uses [JBoss Logging](https://community.jboss.org/wiki/JBossLoggingTooling) and that requires source +ActiveMQ Artemis uses [JBoss Logging](https://community.jboss.org/wiki/JBossLoggingTooling) and that requires source code generation from Java annotations. In order for it to 'just work' in Eclipse you need to install the _Maven Integration for Eclipse JDT Annotation Processor Toolkit_ [m2e-apt](https://github.com/jbosstools/m2e-apt). See this [JBoss blog post](https://community.jboss.org/en/tools/blog/2012/05/20/annotation-processing-support-in-m2e-or-m2e-apt-100-is-out) @@ -69,17 +81,17 @@ Eclipse Indigo (3.7) has out-of-the-box support for it. As of this writing, Eclipse Kepler (4.3) still lacks support for Maven's javacc plugin. The available [m2e connector for javacc-maven-plugin](https://github.com/objectledge/maven-extensions) requires a downgrade of Maven components to be -installed. manual installation instructions (as of this writing you need to use the development update site). See +installed. manual installation instructions (as of this writing you need to use the development update site). See [this post](http://dev.eclipse.org/mhonarc/lists/m2e-users/msg02725.html) for how to do this with Eclipse Juno (4.2). -The current recommended solution for Eclipse Kepler is to mark `javacc-maven-plugin` as ignored by Eclipse, run Maven -from the command line and then modify the project `activemq-core-client` adding the folder +The current recommended solution for Eclipse Kepler is to mark `javacc-maven-plugin` as ignored by Eclipse, run Maven +from the command line and then modify the project `activemq-core-client` adding the folder `target/generated-sources/javacc` to its build path. ### Use _Project Working Sets_ -Importing all ActiveMQ Artemis subprojects will create _too many_ projects in Eclipse, cluttering your _Package Explorer_ -and _Project Explorer_ views. One way to address that is to use -[Eclipse's Working Sets](http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Fcworkset.htm) -feature. A good introduction to it can be found at a +Importing all ActiveMQ Artemis subprojects will create _too many_ projects in Eclipse, cluttering your _Package Explorer_ +and _Project Explorer_ views. One way to address that is to use +[Eclipse's Working Sets](http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Fcworkset.htm) +feature. A good introduction to it can be found at a [Dzone article on Eclipse Working Sets](http://eclipse.dzone.com/articles/categorise-projects-package). \ No newline at end of file