Make Icenium deploy to Nexus 10

To make Icenium see your Nexus 10 you first need to install the appropriate USB driver for Windows. For Nexus devices you need the Google USB Driver.

To install the Google USB Driver:

  1. Download and unzip the archive.
  2. Right-click on Control Panel -> Device Manager -> Portable Devices -> Nexus 10 and choose ‘Update Driver Software’.
  3. Choose ‘Browse my computer for driver software’.
  4. Enter the path to the folder you’ve extracted the archive (see point 1) in and finish the wizard.

Next you just need to enable USB debugging on your Nexus device. The developer Options are a little bit hidden. You first need to “become a developer”, that’s how Google calls it.. Go to Settings -> About tablet -> and click several times on the Build number to become a developer.

Then you will have Developer options in the Settings. Turn USB debugging on and you are done.

You should be able to see your Nexus in the Devices pane.

Posted in Icenium | Leave a comment

Running Protege on Windows 8 x64

I managed to run Protege 4.2 Beta using the distributable ZIP protege-4.2-beta.284.zip and latest Java (Java 7 Update 13 (x64)). There is a bat file run.bat that does the job of launching the ProtegeLauncher.jar.

Both 4.1 and 4.2 windows installers failed for me with the same error

ZeroGu2: Windows DLL failed to load
at ZeroGa2.b(DashoA10*..)
at ZeroGa2.b(DashoA10*..)
at com.zerog.ia.installer.LifeCycleManager.b(DashoA10*..)
at com.zerog.ia.installer.LifeCycleManager.a(DashoA10*..)
at com.zerog.ia.installer.Main.main(DashoA10*..)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.zerog.lax.LAX.launch(DashoA10*..)
at com.zerog.lax.LAX.main(DashoA10*..)

While the 4.2 version runs fine from the zip, the 4.1 version failed with

C:\Program Files\Protege_4.1>java -Dlog4j.configuration=file:log4j.xml -DentityE
xpansionLimit=100000000 -Dfile.encoding=utf-8 -Dorg.protege.plugin.dir=plugins -
classpath bin/felix.jar;bin/ProtegeLauncher.jar org.protege.osgi.framework.Launc
her
Core Bundle 1 failed to start.
Exception in thread “main” org.osgi.framework.BundleException: Unresolved constr
aint in bundle org.protege.common [1]: package; (&(package=javax.swing.text)(ver
sion>=0.0.0))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3295)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1653)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892)
at org.protege.osgi.framework.Launcher.startBundles(Launcher.java:111)
at org.protege.osgi.framework.Launcher.start(Launcher.java:80)
at org.protege.osgi.framework.Launcher.main(Launcher.java:143)

Maybe I will just download the source and try to debug my first Java project…

Posted in Uncategorized | Leave a comment

Make Powershell script fail a Jenkins build

Recently I made our Jenkins builds execute only one powershell script. Executing several build steps for specific tasks makes it hard to share state between steps. I decided to have only 1 script that does everything.  If you want to control the build status from a script you need 2 things.

1. Return proper exit code from your script (0 success, else failure)
2. The plugin you are using must use that exit code to control the status.

Unfortunately the Jenkins PowerShell plugin doesn’t care about the exit code of your script (source code). So no matter what had happened with your script, your build would always be green (success). The fix is fairly simple – just don’t use it. Use the built-in Execute windows batch command instead

powershell "&.<path_to_your_script>"

Now you only need proper exit code from your script. If you want to fail your build you can use exit 1 or throw “Error” 

NOTE:

Termination errors will break your script and exit with 1, effectively failing your build.   Some cmdlets generate error simply by writing to the error stream. Powershell considers these as “non-terminating errors” and will continue executing your script. If you want to stop the execution and raise the error set the ErrorActionPreference variable.

$ErrorActionPreference = "Stop"

If you run executables from your script like msbuild or mstest you need to manually check the $LASTEXITCODE and exit if necessary.

Posted in Jenkins, Powershell | Leave a comment

My first shot with a tripod

Taken from a window

Posted in Uncategorized | Leave a comment

WordPress postname permalinks on Windows hosting

If you just upload the content of WordPress.zip to your windows web server (like I did) you will notice that the postname permalinks are not working.

WordPress postname permalinks require URL rewriting. In order to fix this you will need IIS URL Rewrite enabled and the following web.config in your wordpress folder.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
 <system.webServer>
  <rewrite>
   <rules>
    <rule name="Main Rule" stopProcessing="true">
     <match url=".*" />
     <conditions logicalGrouping="MatchAll">
      <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
      <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
     </conditions>
     <action type="Rewrite" url="index.php/{R:0}" />
    </rule>
   </rules>
  </rewrite>
  <security>
   <requestFiltering allowDoubleEscaping="true" />
  </security>
 </system.webServer>
</configuration>
Posted in Uncategorized | Leave a comment