Using v0.5 of the Maven emma plugin. Found that if you specify an include/exclude filter, no classes are instrumented….On digging a little deeper under the covers, it seems that there’s a bug with the Maven emma plugin – I’ve edited the plugin’s jelly script and using it here.
Posted the bug and the fix to Maven’s sourceforge developer forum. You can find it here
The fixed plugin.jelly’s here – Maven emma plugin 0.5 fixed
It has come upon me to build a FC6 server with a Java build environment that is going to serve as the build machine. This is the first time I’m coming to Fedora – always having used Debian in the past.
- OS installation was smooth. I installed with KDE since some folks prefer the GUI.
- During the installation, I chose Java Development – and all the gcj components got installed. Then post installation, I downloaded JDK from Sun and installed it too. The (gcj) tomcat of course didnt work very well in this mess. Fixing it was easy – just fired up yum via Add or Remove Programs and removed gcj – which removed all the other gcj tools and libraries too.
- Setting the host name – unexpectedly, had trouble doing this – finally used system-config-network.
- Environment variables – again a little digging around to figure out how to set environment variables so that they are effective for all users on the system – essentially JAVA_HOME, JRE_HOME, CATALINA_HOME, MAVEN_HOME etc. Finally found that this is best set in /etc/environment where it works for all users.
- Downloaded java tools and libraries – housed tomcat and maven under /usr/lib/java/maven-xxx and /usr/lib/java/apache-tomcat-x.xx and created symlinks. Placed symlinks to tomcat’s startup.sh and shutdown.sh in /usr/bin. Placing a symlink to maven doesnt work – but an alias works as well. To make it work for all users, simply put it in /etc/profile
- Created a group java and added users to the group. Set permissions on the maven installation folder so that java group has write access (this is so that maven plugin:download for additional plugins works properly and can write to the maven plugins folder)
That’s all there is to it. Just make sure that you do everything as the ‘application’ user – dont do it with your account or the root account.