-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason,

On 8/25/2010 4:06 PM, Jason Britton wrote:
> We have a separate department
> that is more marketing/static content than it is anything, they'll put
> their own stuff up on the website that for the most part is not under
> revision control

Any reason not to have this under revision control?

> All our tag libraries,
> main web workflows (ecommerce), search functionality, page templates
> etc. are under revision control, we are happy subversion users after
> escaping from starteam some time ago.

Sounds good.

> Our classes, web.xml, libs are
> deployed in one war file for our main site, deployment configuration
> managed by JDeveloper project, I'm not proud of this but we are
> migrating off of Oracle app server and I plan to take a look at
> Eclipse for ide and change our project builds to use maven or ant.  We
> have other traditional web apps whose content/config/classes/libs are
> all traditionally packed up and deployed in a war.

So it's just the static content that needs to be modified by the
designers? Okay, how do they typically place their files after they're
ready? Samba? WebDAV? FTP? Do they drop them straight into production,
or is there a staging area? I'm wondering if you can integrate staging
with subversion and then always build from subversion.

I highly recommend always building from your repository... that way, you
always know what versions of files are out there.

> As for my previous problem separating config/lib/classes from content.
> I ended up using a symlink on WEB-INF directory on ROOT context, I've
> got app called foo, ROOT/WEB-INF is symlinked to FOO's WEB-INF
> directory.  I can redeploy FOO and ROOT gets new config/classes/lib
> via symlink and I don't have to worry about docBase of ROOT getting
> undeployed.

Be careful: some versions of Tomcat will effectively do an 'rm -rf'
/across/ symlinks that live within deployment directories. Make sure
Tomcat's euid doesn't have rights to delete your stuff.

Good luck,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkx2eCEACgkQ9CaO5/Lv0PAX/QCfU9r4lXbHcEnYHyqAYopuXjwb
aiMAoKgw6iSoPB/3t4YZEsHfTxvKXqdi
=VfWA
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to