Disqus - Latest Comments for Ronnie76er

Re: Getting code coverage in the Play Framework using Jacoco

Ron Alleva — Sun, 20 May 2012 20:40:48 -0000

Excellent. Glad you got it working.

No worries, the wording should have been clearing in the post, and now the next person that comes along will have less trouble.

Re: Getting code coverage in the Play Framework using Jacoco

Ron Alleva — Sun, 20 May 2012 12:15:42 -0000

I am definitely not an sbt expert either, although I'm slowly learning.

A hugely important part of the Build.scala file is the :

lazy val s = Defaults.defaultSettings ++ Seq(jacoco.settings:_*)

Which adds the settings along with the default settings to the variable s.

This line:

val main = PlayProject(appName, appVersion, appDependencies, mainLang = JAVA, settings = s)

adds the settings to the Play project. You'll notice the "settings=s", which I think is the most important part of this line.

I've modified the post a little bit to make it more clear what's going on in the Build.scala file.

Re: JMeter Maven Plugin

Ron Alleva — Mon, 28 Nov 2011 22:30:09 -0000

Hmm, I don't see why it wouldn't be able to run with it. I haven't really looked into the plugins much, and haven't been actively using this plugin lately to maintain it, unfortunately. Technically however, the jmeter used in this plugin is no different than the one used from the command line.

Re: Getting Started with Google Play Music on Ubuntu

Ron Alleva — Sun, 27 Nov 2011 12:59:50 -0000

Try this: http://ronalleva.com/2011/1...

Re: Minor issue with Ubuntu Desktop

Ron Alleva — Thu, 23 Jul 2009 11:34:07 -0000

In Compiz, everything is a texture. On the Intel graphics cards the maximum texture size allowed is 2048x2048. When you go to an extended monitor, the size of the desktop is larger than 2048 across, so Compiz has a built in check to not start when the desktop size is large than the graphics card's supported texture size.

There is two ways you can fix this. First way, make your setup one monitor, switch to using compiz, and then switch to two. Compiz only checks on startup, so when you switch to two monitors, Compiz is already active.

The second choice is to modify the startup script /usr/bin/compiz. If you look for the check_texture_size function, in there you'll see it returns '1' on a failure (line 270 for me). You can switch that to 'return 0;'. Then, you should be able to start compiz.

Also note that since only 2048 is supported, there will be that area of black nothingness that appears on the right-most monitor, where you see all those weird effects of the windows being ghosted. This is a limitation (as far as I know) of the graphics hardware.

Hope that helps.