I've found following link for svn access:
https://svn.java.net/svn/glassfish~svn
Therefor as in my case if I need 3.1.1 version I can obtain it simply via:
svn co https://svn.java.net/svn/glassfish~svn/tags/3.1.1/ glassfish_3.1.1
https://svn.java.net/svn/glassfish~svn
svn co https://svn.java.net/svn/glassfish~svn/tags/3.1.1/ glassfish_3.1.1
export JAVAWS_VM_ARGS="-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=9010,server=y,suspend=n -XX:MaxPermSize=128m"
[#|2013-02-05T08:08:40.769+0100|SEVERE|glassfish3.1.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=90;_ThreadName=Thread-2;|Exception while shutting down application container|#] [#|2013-02-05T08:08:40.938+0100|SEVERE|glassfish3.1.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=90;_ThreadName=Thread-2;|Exception while shutting down application container : java.lang.NullPointerException|#]Well I did, today. And as I've googled, noone could ever get some more meaningfull stacktrace out of it. Sounds like a nightmare. So where the problem could be?
<dependency> <groupId>commons-pool</groupId> <artifactId>commons-pool</artifactId> <version>1.6</version> <scope>runtime</scope> </dependency>As I introduced for client-server communication spring remoting (as a corba alternative) where pooling is used.
mvn <your sfuff>the debug one:
mvnDebug <your sfuff>It should tell you it's waiting for connection, in a way like this:
Preparing to Execute Maven in Debug Mode Listening for transport dt_socket at address: 8000Afterwards use your preffered way to connect to socket 8000 via remote debugger. (For eclipse steps can be found here, or googled)
mvn -Dmaven.surefire.debug testIt would wait for connection, in a way like this:
Listening for transport dt_socket at address: 5005Afterwards use your preffered way to connect to socket 5005 via remote debugger. (For eclipse steps can be found here, or googled)
gksudo nautilusif you can see the mounted filesystem there, you're lucky, just do whatever is required (possibly delete some non-critical stuff).
sudo fdisk -lthis should show you all the partitions. It's important in this step to identify the one you're interested in to see the files of. You can find it based on size. As I assume you can read the output and find the important one.
/dev/sdbXnow as we know the partition, let's mount important one:
sudo mkdir /media/ubuntu sudo mount /dev/sda6 /media/ubuntu sudo cd /media/ubuntunow check how much is your disk occupied using:
df -hafterwards, manipulate the files in a way you need to (possibly delete some non-critical stuff).
rm -rf /media/ubuntu/home/<user_name>/<some_dir>And that should be it.