...
The Sandbox incorporates a number of steps that a new developer would have to discover by trial and error. Does your Java have the unlimited cryptography files and does it have the Yale Certificate Authority files installed? Do you have both a current Maven and the old Maven 2.2.1 that Jenkins runs? There are a few changes required to the standalone.xml configuration file in JBoss, and you need the database drivers installed. Have all of the servers, drivers, JREs, and versions of Maven been configured to Eclipse?Its not that you cannot solve each of these problems in a new environment. It just takes days or weeks. The Sandbox makes it all just workDo you have Oracle and SQL Server database drivers installed? How do you get JBoss logs to go to /var/log/jbossas/standalone instead of the log directory inside JBoss itself?
You can duplicate the Server environment of the DEV VM, but that configuration is not designed for edit, compile, and debug. Before you get to DEV, you need something more friendly to developers.The solutions are not hard, but there are enough problems that crop up that you could spend days or weeks recreating the Sandbox environment, and that is just a waste of time.
That's not how WE do it!
...
The Sandbox system allows to to edit, compile, and debug the program. After debugging, the Sandbox commits source changes back to Subversion. To move those changes even into DEV requires a Jenkins Build job that checks the source out of Subversion, reruns the compile, and stores the JAR or WAR on the Artifactory server. So the only external consequences of the Sandbox development are the source changes in Subversion. Except for that, everything that happens in the Sandbox is private and doesn't matter.
Installation
VirtualBox is free, open source, quite easy to use, and available for all the host operating systems we use. Normally you install whatever is First you download and install the current version of Virtualbox from virtualbox.org. VirtualBox is an open source project, but Oracle also provides some proprietary extensions that you are prompted to install immediately after you install the base software.You can decide later on You only require a version that is reasonably stable. You will not be running production servers under it 24x7, and you will not be using the more exotic personal desktop features like 3D video acceleration or USB passthrough.
Because the Sandbox has no special requirements for the virtual machine host, this is one place where you are free to prefer VMWare Player or Hyper-V if you already have them installed.
Later on you can decide to mount the SandboxData files natively on your Windows or Linux laptop. This should not be an your initial choice because you may have to change some configuration parameters, and it is better to get used to the VM before you attempt an advanced configuration process.The user named "casdev" is defined to each VM image. OK, so the Sandbox was originally created to develop CAS, but there is no reason to change the userid if you are working on IIQ insteadnative OS configuration parameters, and it is better to get used to the VM before you attempt an advanced configuration process on your normal machine.
There is an admin user named "casdev" defined in every Sandbox. There is a single universal password defined for this user (get it from another developer). Because this user is so well known, it is a bad practice to expose the VM to other machines (by giving it "bridged" access to the network). The casdev user is typically the owner of all the directories used by the development tools or the running application. The Sandbox is not a place to test file security.
Yes, the Sandbox was originally created for CAS development, but it works with other projects and there was no need to rename the user.
If you launch the VirtualBox application you will see a management console. It displays the Virtual Machines (VMs) that you already have and provides a Wizard for creating new VMs, typically by running the OS installer CD image for Windows or a Linux distribution. If you ask it to start an existing VM, VirtualBox creates a simulation of a full personal computer and even runs a power up BIOS. It then boots from the virtual hard disk image or from the virtual CD image.
...