- This topic has 2 replies, 2 voices, and was last updated 20 years, 11 months ago by Riyad Kalla.
-
AuthorPosts
-
Riyad KallaMemberSystem:
JDK 1.4.2_03
Windows XP
Eclipse 2.1.2
ME 2.7rc1, clean installProblem Summary:
Using the deployment tool in ME, I have already setup one deployment target for my project: an exploded webapp in my Tomcat webapps dir. Works great.Now I just tried to hit “Add” to add another target, which would create a WAR file for me, so I could grab it and upload it to the server that this project goes on.
I got an error dialog that popped up saying:
“No enabled and configured servers available. Project XYZ can not be deployed at this time. See MyEclipse preferences to enable a server.”Now Tomcat 5.0 is the ONLY server I have enabled. This dialog message implies to me that I am only allowed 1 deployment target PER server, is this the case?
Why does ME care? Shouldn’t this deployment list just be an arbitrary list of all deployment targets setup by the user?
If it is the case that only 1 target per project is allowed, can this be fixed to allowed arbitrary (Even duplicate) deployment targets to be setup?
Purpose:
So I can setup two deployment targets for the same project. One creates an exploded app that I use while developing, the other creates a WAR that I can quickly upload to the production server when I’m done testing.Best,
Riyad
Scott AndersonParticipantNow Tomcat 5.0 is the ONLY server I have enabled. This dialog message implies to me that I am only allowed 1 deployment target PER server, is this the case?
That is precisely the case as two deployments with the same web root would cause lots of confusion on the server. You may, however, have as many deployments to other servers as you like, but only one active deployment per server.
If it is the case that only 1 target per project is allowed, can this be fixed to allowed arbitrary (Even duplicate) deployment targets to be setup?
If we didn’t prevent duplicate deployments I’d spend all my time debugging problems on why users webapps have problems when they’ve deployed it in multiple configurations with the same web root to the same server.
What you want is the capability to export an archive to an arbitrary location, and this is an active enhancement request. Undeploying your project as exploded, deploying it as an archive and copying it to where you want, and then going back to exploded is the current workaround until the export function is available. Sorry for the inconvenience.
–Scott
MyEclipse Support
Riyad KallaMemberHey no problem, if this is an active request great. Go ahead and close this.
Thanks Scott.
-
AuthorPosts