A recent Computerworld article referenced Linux, Mac OS X and Windows Vista. They linked Mac OS X and Windows Vista to their search but they didn't link Linux. Conspiracy? Oversight?
I've just started working on a new grails application, and early in the piece I hit this error: 2008-03-05 18:39:20.715::WARN: Failed startup of context org.mortbay.jetty.webapp.WebAppContext@1fcb845{/jtchat,/home/prule/workspace/jtchat/web-app} org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.codehaus.groovy.grails.plugins.web.taglib.ApplicationTagLib': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'grailsUrlMappingsHolder': Cannot resolve reference to bean 'urlMappingsTargetSource' while setting bean property 'targetSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'urlMappingsTargetSource': Cannot resolve reference to bean 'grailsUrlMappingsHolderBean' while setting constructor argument; nested exception is org.springframework.beans....
I generally prefer Maven2, but I'm currently on a project using a custom ant build script - and I'm over having to type -Dskip.junit=true when I just want to generate a quick jar without running the tests. To easily switch off tests, I modified ant.bat so that it looks for a command line parameter 'st' and if found, it will substitute it with -Dskip.junit=true. In Ant 1.7.0, you just need to change line 68 in block ':setupArgs' from set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% %1 to if ""%1""==""st"" (set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% -Dskip.junit=true) else (set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% %1) So, the whole block reads (from line 65): :setupArgs if ""%1""=="""" goto doneStart if ""%1""==""-noclasspath"" goto clearclasspath if ""%1""==""st"" (set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% -Dskip...
Read the full details here before doing anything: http://support.apple.com/kb/PH18637?viewlocale=en_US Enabling disk encryption on OSX Yosemite turns out to be a straightforward process. Simply enable it through Setting/Security & Privacy/FileVault - if you chose not to let your iCloud account unlock your disk (for when you've forgotten your password) you'll have to keep a safe record of the recovery key (it sounds like you only get one oppourtunity to record this) - this triggers a reboot, and then when you log back in you'll be able to monitor the progress of file encryption from the same settings panel. I have 2 MacBooks: July 2014 Apple MacBook Pro , 2.6GHz Quad-core Intel Core i7, Turbo Boost up to 3.8GHz, 16GB 1600MHz DDR3L SDRAM, 512GB PCIe-based Flash Storage January 2011 Apple MacBook Air , 13 inch display, Core 2 Duo 1.86GHz, 4 Gig RAM 1067 MHz DDR3, 256 Gig SSD Since disk speed is king, I wanted to measure the effect of enabling FileVault so I f...