In this post I’ll quickly show how to get a maven project under Idea running with the GUI builder, and show you the config you need to build an executable jar for it as well.
The problem comes when using the gui builder with Maven, since the builder uses form files that are specific for IDEA. Thankfully there is a maven plugin to help with this issue: The Maven 2 IDEA UI Designer Plugin.
To have a concrete example to work with, we’ll create a simple Swing app for sending JMS Messages to a destination queue. The code will be located at http://github.com/kenglxn/JMSUtility
So lets get started by setting up the project:
Start IDEA and create a new project. Choose to create from scratch.
In the module section choose maven module and give it a name
In the next screen you can set maven artifact properties and if you wish choose an archetype, we’ll be creating from scratch, so skip the archetype and click the finish button
Great, now we have a fresh maven project that we can work with
So now it’s just a matter of adding the dependencies we need, and writing some code. We’ll add some dependencies for tests, string manipulation and JMS.
Here’s a snippet of the dependencies added to the pom.xml so far:
Next step is writing some code and tests.
We’ll start off by making the UI using the built in GUI Builder in IDEA, using the GridLayout. You could of course use JGoodies Forms layout, or even something else you prefer.
create a new package, again I like to use alt+insert hotkey while the target directory is active. I chose net.glxn.jmsutility as the name for my package
Next we create a new GUI Form in the newly added package and give the form a name. Here I chose GridLayoutManager by IntelliJ, this will need to be added to the pom.
IDEA now kindly shows us the fresh GUI builder view, here we add our components from the palette. Take a look at the live demo of the GUI Builder to get started yourself.
We now have enough code to run the application: 4164296182c8efc3f0c97be8f5be1a7a1f2cdeb3
So now IDEA is able to run the GUI, and tests
That’s it for the GUI building.
Our next step is to get this build running equally smooth in maven. Lets see what the output is with the current code (http://github.com/kenglxn/JMSUtility/tree/130462ca99bc7f05980fd129674d41ef975a5e92)
So we see that maven isn’t happy with us. Let’s fix it by adding the following to the pom:
Now we run the test again and get:
Here we see that the build is ok, but the tests fail. This is what I was talking about earlier in regards to the idea forms not being built with maven.
Lets look at the surefire report and see what it says. I’m going to use the “analyze stacktrace” functionality in IDEA to get a pretty view of the content of the surefire report. To do this go to the Analyze menu and at the bottom select “Analyze stacktrace”, and in the dialog paste in your stacktrace and click ok:
This tells us that the helpButton field is null when it tries to attach an ActionListener in the constructor
The way we solve this is to import the Maven 2 IDEA UI Designer Plugin into the pom:
Let’s see what the maven build does now by running clean install
How about that? The sweet taste of build success :)
This means now that the plugin is working. The next and final step is to create an executable jar via maven for this project. For this we will use the maven-jar-plugin to get a jar with the correct manifest and the maven-archive-plugin to get a lib directory with the dependencies in it which the manifest will refer to.
So, just add the following to the pom:
At this point you should have a pom that looks like this: http://github.com/kenglxn/JMSUtility/blob/b217473ab420550ac81f149c2de22497e3bef303/pom.xml
Now let’s run the executable jar by going to the target folder and running ‘java -jar JMSUtil.jar’
And that’s it. You now have a maven build with tests and automatic building of the executable jar.
Feel free to clone the code and do whatever you like with it, just dont blame me :P
The distribution zip with jar and lib can be downloaded directly here
|07 Jun 2015||Deploy an Ember app to gh-pages using npm run-script|
|06 Jun 2015||JSON Contract testing using unit tests to assert full stack integration across REST services|
|03 May 2015||simple http serve a directory from terminal|
|07 Jan 2014||civu, a CLI for cloning git repositories from jenkins views|
|06 Jan 2014||PyramidSort, a Sublime Text plugin for for reformatting text|
|05 Jan 2014||Git commit-message hook for JIRA issue tags|
|31 May 2013||hacking kitchen tiles with coffeescript|
|30 May 2013||Nuke, ps grep kill something|
|24 May 2013||mvnr: recursive mvn command runner|
|23 May 2013||Query By Example for JPA|
|22 May 2013||gitr: recursive git command runner|
|21 May 2013||Keeping gh-pages branch in sync with master|
|19 May 2013||Migrated from wordpress to jekyll and github pages|
|14 Aug 2012||Using Sublime Text 2 as git commit message editor|
|10 Mar 2012||QRGen, a small wrapper on top of ZXING for generating QRCodes in java|
|04 Jan 2012||My Bash PS1 with git branch info|
|17 Aug 2010||Making a swing project using IntelliJ IDEA GUI builder with maven, Including executable jar|
|01 May 2010||Using Arquillian to test against a remote jboss container from within IDEA|
|06 Apr 2010||WELD/CDI lightningtalk from Know IT 2010 annual conference|
|03 Apr 2010||Solving Sudoku using java swing and junit|
|01 Mar 2010||Simple CDI/WELD login example|
|01 Mar 2010||Implementing @RequestParam in CDI/WELD using Qualifier and InjectionPoint as @HttpParam|
|01 Nov 2009||Seam Maven Refimpl|