- This topic has 6 replies, 6 voices, and was last updated 16 years, 1 month ago by jhm.
-
AuthorPosts
-
Lee HarringtonMemberIt’d be VERY nice to be able to generate a build.xml that could be run from the root of our project that would create a war file.
Why?
Right now my development is local. Then I have a test server to deploy too. Then a production server.
I have to change my log4j.properties, hibernate.cfg.xml and web.xml files for each build. Build a war file…then change the files again, build the next war, then change them all back to redeploy locally for development.
Ant would do this in a flash.
Lee
Riyad KallaMemberI have to change my log4j.properties, hibernate.cfg.xml and web.xml files for each build. Build a war file…then change the files again, build the next war, then change them all back to redeploy locally for development.
Lee I’m not clear how us providing and Ant script that simply bundles the app into a WAR file (exactly what the deployment tool does for packaged deployments) helps avoid your need for adjusting all your config files… what am I missing?
davhudsonMember@support-rkalla wrote:
I have to change my log4j.properties, hibernate.cfg.xml and web.xml files for each build. Build a war file…then change the files again, build the next war, then change them all back to redeploy locally for development.
Lee I’m not clear how us providing and Ant script that simply bundles the app into a WAR file (exactly what the deployment tool does for packaged deployments) helps avoid your need for adjusting all your config files… what am I missing?
In my case the project will be stored in PVCS Dimensions.
If someone just needs to be able to retreive the source and then regnerate the war/jar/ear file then it is much easier to simply run the ant files rather that have to startup eclipse to do it.It also gives the warm feeling that if Eclipse is unavailable for some reason then the project can still be rebuilt.
Orestis MarkouMemberI think he means auto-generating an ant script that could change parameters of the configuration files automatically and then build it into a war.
I have this issue too: it is always needed to supply our test team with the latest version on the CVS to test for bugs etc., but don’t want to give them the classes I haven’t yet checked in. I used to hand-code an ant script that would do all the necesarry stuff (like replace default values with per-version values) database usernames and connection strings etc etc.
I think that an ant-building tool already exists to facilitate this, but I haven’t looked into it much, and I don’t know how it can operate within MyEclipse…
Milind RaoMemberIs there any support for this now? I have the same need. I’m creating a portlet using MyEclipse and it works well, but I need a ant script that can be used for automated daily builds. I could reverse engineer the packaged war file to see what’s in it, but since that info is already available to MyEclipse, it might be a trivial thing to provide.
Riyad KallaMemberMilind,
No support for this in the IDE yet, I think we are looking at enhancing portlets in the 7.x release train after 7.0 gets out the door.
jhmMemberThe easiest way could be providing Ant tasks which runs the MyE-classes. Having the MyEclipse libraries on the classpath should not be the major problem. But have these in minds:
– a CI build does not have any head (which means: no GUI interaction)
– a CI build does not have any person for asking information
– the CI server could be somewhere else: so maybe having a MyE installation is a license problem -
AuthorPosts