I did develop this solution at work for our internal purpose at www.innoveo.com. Going away from the paradigm “As a developer I run everything locally” isn’t easy to accept but in some rare cases, it make sense. Below I list what I consider to be the main advantages and drawbacks.
Use Windows Remote desktop connection, define a DNS entry to access the server.
Linux has a free remote desktop implementation of Microsoft protocol, if it not installed, run either on Debian
# apt-get install rdesktop
or in OpenSuSE
# zypper install rdesktop
or in RED HAT
# yum install rdesktop
Create a script .sh file to save the connection parameters:
rdesktop -A -C -k de-ch -r PRIMARYCLIPBOARD -u username -p password -xl ipadress
-startup plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.0.200.v20090519 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m -configuration ../Users/cedric.walter/.eclipse/org.eclipse.platform_3.5.0/configuration -Dfile.encoding="UTF-8" -vmargs -Xms2048m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+UseParallelGC
A rollout of new Eclipse version is easy thanks to symbolic link. Download junction.exe, a small tool to create symbolic links
Windows 2000 and higher supports directory symbolic links, where a directory serves as a symbolic link to another directory on the computer.
and run as admin
junction.exe c:\eclipse c:\eclipse-3.5
Now thanks to symbolic links any update to a major new version of eclipse will be plain easy: just delete the symbolic link c:\eclipse and create a new one to the new version!
It is not recommend to share the local Maven repository cache among users as Maven has no locking concept in place. The local maven repository is expected to be located at
If you have enough space there for all your users, you can skip that chapter, Otherwise I will show you how to locate it anywhere on the file system.
Let’s store it at e:\%USERNAME%\repository, here I have choose another drive with more space as Maven local repository can be quite big (700Mb per user today)
The design chosen impose me to one more time play with symbolic links, using junction.exe in c:\users\%USERNAME%\.m2\repository pointing to e:%USERNAME%\repository
When you are logged in as a normal developer account, in a dos windows, run the following
junction.exe c:\users\%USERNAME%\.m2\repository e:\%USERNAME%\repository
I like the idea to maintain only one settings.xml. Apache Maven recommend to have one settings.xml per user (located in c:\users\%USERNAME%\.m2\settings.xml). This is true if you have different responsibilities among all your developers. For example some may not be able to deploy in Artifactory/Nexus while other can. Luckily, this is not the case as for today in our company. That is why I will only have one Settings.xml on server, located at c:\server.xml
I will use a hard link to c:\settings.xml. When you are logged in as a normal developer account, in a dos windows, run the following
fsutil hardlink create c:\users\%USERNAME%\.m2\settings.xml c:\settings.xml
This make Apache Maven think that the settings.xml is in the default location c:\users\%USERNAME%\.m2\
I do use the same trick for having a unique version of maven binary on the server while keeping some flexibility thanks to symbolic links.
Now you can let all your developer reference in M2Eclipse this virtual directory c:\maven. Switching all developers to a new version is done by deleting and pointing to an older/newer version of Maven.
Our shared developer environment setup also virtualizes MYSQL (multiple schema per developer ) and Tomcat (per developer port range) using –D system variables in eclipse.ini
In this scenario, a single install area is shared by many users. The "configuration" directory under the install area is home only to the config.ini as shipped with the product (it is not initialized). Every user has their own local standalone configuration location.
The set up for this scenario requires making the install area read-only for regular users. When users start Eclipse, this causes the configuration area to automatically default to a directory under the user home dir. If this measure is not taken, all users will end up using the same location for their configuration area, which is not supported.
Privacy Statement | Copyright Notice | Licenses
© 1999-2012 Waltercedric.com. Designed by Cédric Walter. Sitemap
Reproduction without explicit permission is prohibited. All Rights Reserved. All photos remain copyright © their rightful owners. No copyright infringement is intended.
Disclaimer: The editor(s) reserve the right to edit any comments that are found to be abusive, offensive, contain profanity, serves as spam, is largely self-promotional, or displaying attempts to harbour irrelevant text links for any purpose.