Comments on: Scripts to Help with GlassFish Development http://antwerkz.com/scripts-to-help-with-glassfish-development/ Fri, 30 Sep 2011 22:40:59 +0000 hourly 1 http://wordpress.org/?v= By: Jane Young http://antwerkz.com/scripts-to-help-with-glassfish-development/#comment-109 Jane Young Tue, 18 May 2010 13:07:27 +0000 http://www.antwerkz.com/?p=4537#comment-109 <a href="#comment-15703" rel="nofollow">@jlee </a> I'm using Mac OS and on a bash shell. I'll take a look at rebundle.sh. @jlee
I’m using Mac OS and on a bash shell.
I’ll take a look at rebundle.sh.

]]> By: jlee http://antwerkz.com/scripts-to-help-with-glassfish-development/#comment-108 jlee Tue, 18 May 2010 11:57:20 +0000 http://www.antwerkz.com/?p=4537#comment-108 I'll have to check into #1. It seems to be working everywhere else. What OS are you on? for #2, the devtests.sh script uses that variable to find config.properties before running the devtests. If you don't ever run those, then you're probably ok without it. As for #3, there's rebundle.sh that'll work from the top level. It, in fact, calls updateBundle.sh from each changed module root. updateBundle.sh is intended to be a targeted update. I’ll have to check into #1. It seems to be working everywhere else. What OS are you on? for #2, the devtests.sh script uses that variable to find config.properties before running the devtests. If you don’t ever run those, then you’re probably ok without it. As for #3, there’s rebundle.sh that’ll work from the top level. It, in fact, calls updateBundle.sh from each changed module root. updateBundle.sh is intended to be a targeted update.

]]> By: Jane Young http://antwerkz.com/scripts-to-help-with-glassfish-development/#comment-107 Jane Young Tue, 18 May 2010 01:22:01 +0000 http://www.antwerkz.com/?p=4537#comment-107 Hi Justin, Thank you for the helpful scripts. There are couple issues with updateBundle.sh: 1. The script calls "source $0/../dev_base.sh" but $0 returns $PWD/updateBundle.sh so running the script failed with "updateBundle.sh: line 3: updateBundle.sh/../dev_base.sh: Not a directory". The fix is change the line to "source `dirname "$0"`/dev_base.sh" 2. dev_base.sh checks for the environment APS_HOME. Since I don't have v2 workspace checked-out plus this variable is not used in updateBundle.sh, I don't really need this environment so I commented out the lines that check for APS_HOME in dev_base.sh. 3. The script just moves the jar file from target directory to glassfish/modules directory. I'll need to run this script in the module level, not in the top v3 level. It'll be good to enhance the script to run from the top level and instead of a "move" create a symlink from glassfish/modules to the target directories so user just need to run this script once. Jane Hi Justin,

Thank you for the helpful scripts. There are couple issues with updateBundle.sh:

1. The script calls “source $0/../dev_base.sh” but $0 returns $PWD/updateBundle.sh so running the script failed with “updateBundle.sh: line 3: updateBundle.sh/../dev_base.sh: Not a directory”. The fix is change the line to “source `dirname “$0″`/dev_base.sh”
2. dev_base.sh checks for the environment APS_HOME. Since I don’t have v2 workspace checked-out plus this variable is not used in updateBundle.sh, I don’t really need this environment so I commented out the lines that check for APS_HOME in dev_base.sh.
3. The script just moves the jar file from target directory to glassfish/modules directory. I’ll need to run this script in the module level, not in the top v3 level. It’ll be good to enhance the script to run from the top level and instead of a “move” create a symlink from glassfish/modules to the target directories so user just need to run this script once.

Jane

]]>