- This topic has 11 replies, 2 voices, and was last updated 18 years, 7 months ago by
.
-
Posts
-
The deffault location suggested in the export war file dialog is under the webroot directory. If you take ths location then everything seems to work, however I noticed that the war file grows in size if you don’t delete it and re-export it. It appears that everything you do the export it includes the old version of the file in the new version unless you delete it first.
I suggest that the default file location for war file export be changed up a directory to reside in the main project
directory instead of under webroot.While I’m waiting for the release that fixes this, is there a config file someplace which would allow me to change te default location for war files?
I’m not aware of one at this time, but that’s not to say it’s not hidden somewhere in the bowels of the plugin descriptors or ini files. I’m just not sure where it’s kept.
Did the fix for this get into the 5.1 release? I certainly thought it was a quick fix, but don’t see it in the bugs fixed list.
I do not believe this was changed as management is always hesitent to change defaults because of “expected behavior” that our massive customer base can get use to and in some of our corporate customer settings, minor changes like that can screw up an entire IT departments work flow so even silly little things from time to time cannot be changed in a single release.
I will make a note of it again though to see if they will reevaluate it.
I can understand that, but in this case the default behavior was causing this growth behavior which I’m sure is REALLY not what anybody wanted, and might not have noticed the storage this was eating up.
That is very true, I wouldn’t argue that the current default is better. I’ll see if we can get this changed.
I would point out and alternative and possibly easier mode of operation for you. Is to setup a Custom Location deployment for your project, and set it as packaged, and point it at your project dir. Then you can pop open the Servers view and mangae all your deployments from there, simply refreshing the Custom Location one when you need to update the WAR.
Possibly, I am sending a request for it to make it into 5.1.1
I do have to point out though, that the steps I outlined above are a faster way to manage your custom WAR. It requires One click as opposed to like 5 using the File > Export > WAR menu…
OK thanks. Are you anywhere close to a timeline for a 5.1.1 release? The main reason I’m asking is that there is a lot of administrative overhead in getting things installed where I work and I don’t want to request 5.1 to be installed if 5.1.1 is coming soon behind.
