573

mvn clean install -Dmaven.surefire.debug=-Xdebug -Xnoagent -Djava.compiler=NONE  -Xrunjdwp:transport=dt_shmem,server=y,address=Maven,suspend=n

# In Netbeans Debug/attachDebugger with 
#   connector : SharedMemory
#   Name : Maven
#   Timeout : 10 000 

573

get_db() {
  if [ -z "$CABAL_SANDBOX_CONFIG" ]
  then
    db=""
  else
    db=$(sed -nr -e 's/^package-db: (.*)/\1/p' "$CABAL_SANDBOX_CONFIG")
    if [ $? -ne 0 ]; then exit 1; fi
  fi
}
db_cmd() (

573

import com.google.inject.AbstractModule;
import com.google.inject.Guice;
import com.google.inject.Inject;
import com.google.inject.name.Named;
import com.google.inject.name.Names;

import java.io.FileInputStream;
import java.io.IOException;
import java.util.Properties;

573

Reused that box description for proof-of-concept jenkins-in-a-box for M$-bound developers.

The ssh-call to ssh into the once enrolled box was (information per vagrant ssh-config):

$ ssh [email protected] -p 2200 -i /d/tools/vagrant-aweijnitz/.vagrant/machines/default/virtualbox/private_key -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PasswordAuthentication=no -o IdentitiesOnly=yes -o LogLevel=FATAL

Have to look more deeply on the set of commands vagrant understands, not to forget one of them vagrant reload on changes in the configuration.

On some occasions ssh-add ~/.vagrant.d/insecure_private_key can be useful.

573

# -------------- In my case it was this location, change accordingly -----------
#                I only show here the part of that file I changed
## [ v3_req ]
##
### Extensions to add to a certificate request
##
##basicConstraints = CA:FALSE
##keyUsage = nonRepudiation, digitalSignature, keyEncipherment

[ v3_req ]