Inspired by Felipe Cypriano, I extended his task to sync dependencies from Gradle to IDEA in a multiproject build.

It creates a library file for each subproject and each configuration (if it contains any dependencies). Project dependencies are ignored.

Read more for source

task syncIdeaLibraries << {
  description = 'Add gradle dependecies for each project to IntelliJ project libraries'

  final File librariesDir = new File(".idea${File.separator}libraries")
  librariesDir.mkdirs()

  def createLibrary = { fileName, libraryName, jars ->
    final def gradleLibXml = new File(librariesDir, fileName)
    gradleLibXml.write '''
  <component name=\"libraryTable\">
  <library name=\"''' + String.valueOf(libraryName) + '''\"/>
  </component>'''

    final def xmlRoot = new XmlParser().parse(gradleLibXml)
    final def classesNode = xmlRoot.library[0].appendNode('CLASSES')

    jars.each { jar ->
      classesNode.appendNode('root', [url: "jar://${jar.trim()}!/"])
    }

    def writer = new StringWriter()
    new XmlNodePrinter(new PrintWriter(writer)).print(xmlRoot)
    gradleLibXml.write writer.toString()
    println "File '${gradleLibXml.path}' updated"
  }

  println "Idea library path: ${librariesDir.path}"
  final File userHomeGradle = project.gradle.gradleUserHomeDir
  println "Set the USER_HOME_GRADLE variable to '$userHomeGradle.path'"
  project.subprojects.each { p ->
    p.configurations.each { c ->
      if (!c.dependencies.isEmpty()) {
        def jars = c.files.collect { f ->
          if (f.path.startsWith(userHomeGradle.path)) {
            "\$USER_HOME_GRADLE\$${f.path.substring(userHomeGradle.path.size())}"
          }
        }
        jars.removeAll([null])
        createLibrary "Gradle_${p.name}_${c.name}.xml", "Gradle ${p.name} ${c.name}", jars

      }
    }
  }
}

Basically, it boils down to echo - - - >/sys/class/scsi_host/host$NUMBER/scan where $NUMBER in most cases is 0.

ORA-12519, TNS:no appropriate service handler found

Poking around the Oracle installation, I noticed that the file /oracle/diag/tnslsnr/ora-dev/listener/trace/listener.log contained a lot of:

WARNING: Subscription for node down event still pending

Digging deeper, I found this page. So I added the line:

SUBSCRIBE_FOR_NODE_DOWN_EVENT_Listener=OFF

to the listener.ora and now it seems that our TNS-listener is behaving nicely

Luckily VMware Remote Console (available via VMware server or VMware Workstation) supports connecting to ESXi.

I create a shortcut pointing to:


"C:\Program Files\Common Files\VMware\VMware Remote Console Plug-in\vmware-vmrc.exe" -h esxhost -u user -p password -m "[myDatastore] myDir/myServer.vmx"


And voila! shortcut to a console To obtain the argument to -m, I opened the settings view via Infrastructure Client, clicked “Options” and copied the field “Virtual Machine Configuration File”.

Hope this helps someone else!

However, do notice that hot deployment of JPA and EJB’s is still not possible (as far as I know, do correct me!) and require a complete redeploy of the app.

A rule-of-thumb when comparing dates and calendars (or performing other operations) is to convert it to UTC and then back afterwards.

Recently, I decided to try Foxmarks/Xmarks. Seems to work nicely

(Yes, apparently I’m still alive.)