[GLASSFISH-13518] asadmin deploy won't come back when mistakenly specifying dir name Created: 17/Sep/10 Updated: 02/May/11
|Fix Version/s:||future release|
|Reporter:||Dies Koper||Assignee:||Hong Zhang|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Operating System: Windows XP
I accidentally passed a directory name instead of a file name to asadmin deploy.
D:\GFv3.1\glassfish-3.1-b21-09_17_2010\glassfishv3>bin\asadmin deploy \
|Comment by Hong Zhang [ 17/Sep/10 ]|
Dies: it's not so much of archive vs directory which makes the disk grinding,
Try to pass a small sub directory with not many files in it, and see how much
|Comment by Dies Koper [ 17/Sep/10 ]|
I've never accidentally packaged the whole root directory and tried deploying it
So I'm not sure what is the root issue here.
If the man pages are wrong, and it is supposed to traverse all subdirectories
In my case I tried to specify an application by using tab completion (and who
|Comment by Hong Zhang [ 20/Sep/10 ]|
If the man page says it can only take a file, it needs to be updated to say
|Comment by Hong Zhang [ 28/Sep/10 ]|
dies: Are you ok for me to close this issue? As I said in my previous comments,
|Comment by Dies Koper [ 28/Sep/10 ]|
Could you close it after addressing the issues I brought up?
1. The man page is wrong. Closing this issue won't fix it.
2. I understand you want to merge 'deploydir' into the 'deploy' command and
|Comment by Hong Zhang [ 04/Oct/10 ]|
|Comment by Hong Zhang [ 07/Dec/10 ]|
I have provided this feedback to the doc team and now the latest 3.1 man page (not published officially yet) has reflected this change.
I am not sure how easy it is to decide what directories and the depth that we should scan by default: libraries could be at random places and referenced through manifest, class files could be located in a deep directory layout. I am going to mark this issue as an enhancement now and see if there is anything we can do in the future release.