- This topic has 5 replies, 2 voices, and was last updated 18 years ago by
.
-
Posts
-
Hi all,
It’s more an annoyance than a critical bug actually. Here’s the situation (with Tomcat 5, did not try with other application servers) :
– Hit the “Deploy MyEclipse J2EE Project to Server…” button
– Choose any project, then “Add”
– In “Server”, pick “Externally Launched”, “Custom Location – Suffixed”, “Custom Location”
– Browse the Deploy Location to anything different to default
– Remember you wanted a packaged archive, and not an exploded one
– Switching the radio button makes the deploy location come back to the default value 🙁I think most of the users would expect this deploy location not to change, no?
However, a workaround would be to be able to define a default custom deploy location, but I couldn’t find in the preferences such a possibility.
Cheers,
alexisInstallation details :
*** Date: Thu Nov 09 09:37:39 CET 2006 *** System properties: OS=WindowsXP OS version=5.1 Java version=1.5.0_06 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 5.0 GA Build id: 20060805-5.0-GA *** Eclipse details: Eclipse SDK Version: 3.2.1 Build id: M20060921-0945 Eclipse Platform Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx Build id: M20060629-1905 Eclipse RCP Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq Build id: M20060629-1905 Eclipse Java Development Tools Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC- Build id: M20060921-0945 Eclipse Plug-in Development Environment Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG Build id: M20060921-0945 Eclipse Project SDK Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ Build id: M20060921-0945 Eclipse Graphical Editing Framework Version: 3.2.0.v20060626 Build id: 20060627-0816 Eclipse startup command=-os win32 -ws win32 -arch x86 -launcher C:\Archivos de programa\eclipse\eclipse.exe -name Eclipse -showsplash 600 -exitdata 90c_7c -vm C:\WINDOWS\system32\javaw.exeAlexis,
I agree, this is poor default behavior and can be frustrating. I’ll file the request to change it.Hi Riyad,
Thanks for the quick reply!
Is the release target 5.0.3, or a later one? By the way, any update concerning the release date for 5.0.3?Cheers,
alexisAlexis,
5.0.3 got renamed to 5.1 because of the number of fixes and features that went into it, and unfortunately no this behavior change cannot make that release. We went into a hard freeze Monday (major bug fixes only) and are preparing for a Monday release.Our of curiosity, are you changing between packaged and exploded deployments that often? What you might want to do is just setup multiple deployments for the same project, one exploded and one as packaged (you need to setup them up as External and Custom respectively, because once you use a deployment type/location for a project, you cannot use it again. But using external and custom would allow you to essentially setup two custom locations).
Then you can manage that all from the server view, updating them as you needed… like this:
@support-rkalla wrote:
5.0.3 got renamed to 5.1 because of the number of fixes and features that went into it, and unfortunately no this behavior change cannot make that release. We went into a hard freeze Monday (major bug fixes only) and are preparing for a Monday release.
Great! And no matter the fix doesn’t get integrated in 5.1, it’s just a minor annoyance, not a bug.
@support-rkalla wrote:Our of curiosity, are you changing between packaged and exploded deployments that often? What you might want to do is just setup multiple deployments for the same project, one exploded and one as packaged (you need to setup them up as External and Custom respectively, because once you use a deployment type/location for a project, you cannot use it again. But using external and custom would allow you to essentially setup two custom locations).
Yes, I change from exploded to packaged rather often. The reason why is that I deploy a packaged archive to a dynamically named folder (typically, including today’s date). Since deploying to a custom location is set by default to exploded, it happens to me sometimes to forget to switch to packaged BEFORE setting the deployment path. My workaround is to always deploy to the same custom location (which is basically one level up from the folder named along the date) and then move the archive manually.
@support-rkalla wrote:Then you can manage that all from the server view, updating them as you needed… like this:
I feel a bit stupid now… cos I never noticed this view before! It’s just perfect to manage the many deployments I have (around 15 web apps, all deployed in exploded and packaged forms).
How long has this view been present in ME? I can’t believe I could have done without it so far!…Thanks for you help!
Regards,
alexis
