|WTP Best Practices? [message #178836]
||Sat, 09 September 2006 20:18
Originally posted by: aeg.eclipse.somnia.com|
Is there any document that describe the "best practices" for using WTP in
a multi-developer environment?
I've been an Eclipse user for years, and have followed the various
iterations of the WTP. However, I've always been hesitant to adopt a new
methodology when I've been productive with others.
At this point, we have out web-based configuration files (Struts XML,
Tiles, web.xml, etc) seperate from our source. These are divided by
directory for local, dev, and production environments. Individual ANT
scripts build source, copy HTML, JSP and the like, as well as the type of
configuration files required (whether for local or production builds).
To make a long story short, or current paradigm doesn't fit with the WTP
paradigm, and I don't know how (or if) I should try to squeeze the two
together. Since WTP creates and uses a WEB-INF directory directly within
the Web source, I don't know exactly how to proceed. Does the WTP team
believe these files should be checked in to CVS/SVN right along with the
HTML and JSP? If so, where should the production-level config files go,
since they are certainly different.
This, along with many other questions like it, have be a bit perplexed. I
don't want to blaze a new path of development tool integration glory if a
best-practices guide exists.
So, to bring this long post to a close, does one? I've read through the
documentation, but it only gives me the basics. I need a more in-depth
guide to the theory of development with WTP.
|Re: WTP Best Practices? [message #178973 is a reply to message #178836]
||Mon, 11 September 2006 22:12
| Hermann VoÃ?eler
Registered: July 2009
Lukas Bradley schrieb:|
> At this point, we have out web-based configuration files (Struts XML,
> Tiles, web.xml, etc) seperate from our source. These are divided by
> directory for local, dev, and production environments. Individual ANT
> scripts build source, copy HTML, JSP and the like, as well as the type
> of configuration files required (whether for local or production builds).
just another hint: in our team, we use a separate SVN branch for the
production builds. So, basically, before every new release, there will
be a merge from developement line to the production branch and the person
doing the merge will review the changes that are about to go to Live.
This means the production versions of all config files are located on
the production branch only and a normal dev. setup will never see this
hope this helps,
Powered by FUDForum
. Page generated in 0.04974 seconds