- This topic has 3 replies, 2 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
Dear,
I just migrated our project from Eclipse to MyEclipse.
I had previously everything running fine under ANT-control.
For that I made a directory ./config with all my Apllication Servers specific files… Something like this :| web.xml +---jboss | | oeil-ds.xml | | oeil-xa-ds.xml | +---tomcat | | server-4.10.xml | | server-5.0.24.xml | \---wls | | weblogic.xmlI was wandering what I was better to do to deploy properly under MyEclispe. I mean I DO NOT want to push all AS specific configuration files into the WAR …
Any bright idea ?
Tia,
\T,
tsmets,
You may need to stick with your Ant script for the time being. MyEclipse’s deployment tool will deploy identical copies of your web app to any number of app servers. There is no hook or ability to say “If appServer==BLARG, then deploy XYZ, else deploy ABC” which it sounds like what you want.There are other users on the corums with very complex deployment scripts that have had to stick with Ant because of this, but they are still able to take advantage of the development tools and debugging of MyEclipse; just not the deployment tool.
So the best option might be to have them all copied in the WEB-INF (via an ANT-Task) with the file being flagged as “uncommittable” there (via the .cvsignore). The production WAR would have to be built manually.
Tx,
\T,
The production WAR would have to be built manually.
If you are building the WAR file manually, then I’m not sure why copying the appropriate deployment descriptor into WEB-INF temporarily wouldn’t be part of the same Ant task.
I thought you were trying to use our deployment tool, in which case I would say that your suggestion here:
So the best option might be to have them all copied in the WEB-INF (via an ANT-Task) with the file being flagged as “uncommittable” there (via the .cvsignore)
would probably work. Then the deployment tool would WAR your entire WebRoot recursively (including all the extra deployment descriptors in the WEB-INF dir) and deploy the WAR file to whichever app server you were executing the deploy for via the tool. Then the app server would uncompress the WAR file and deploy the app and only read the deployment descriptors it cared about.
While this sounds sloppy, its probably fine for development. You could use your existing Ant task to build a “clean” WAR file for production deployment that only included the descriptors for the appropriate app server you were deploying too.
Am I understanding your request correctly? If not, please let me know.
