I'm outta here - for your viewing pleasure, here's a picture of Abbie to make you smile throughout the weekend.
I haven't read it, but this JAAS Security in Action article at DevX.com looks like a good intro to JAAS. Hopefully it'll teach me something as soon as I take the 10 minutes to read it.
I don't think this is possible, but since a co-worker asked - I'm relaying the question to you, the experts. Using CVS, it is possible to "checkout" a file for editing, and to lock it on the CVS server, so no one else can check it in. If this feature exists, I'd love to use it. Also, if anyone knows how to hookup sending e-mails for commits on a barebones CVS install, enlighten me. SourceForge makes it easy using synchmail, but Google doesn't even know about this tool - must be a SF script.
Update: Anthony has given me some good tips in the comments of this post. I've had some success in getting e-mail notification setup, but I'm still having some issues. To configure it, I checked out CVSROOT, and edited the loginfo file, adding the following line:
^project /usr/bin/mailx -c $USER -s "[cvs-commit] %{sVv}" [email protected]
When I get in a file, I get:
Checking in build.properties;
/export/home/cvsr/project/build.properties,v <-- build.properties
new revision: 1.7; previous revision: 1.6
done
1.6... User unknown
1.7... User unknown
build.properties... User unknown
/export/home/mattra/dead.letter... Saved message in /export/home/mattra/dead.letter
I do receive the e-mail, but it's addressed to 1.6@cvsserver, 1.7@cvsserver, build.properties@cvsserver and [email protected]. I'm sure it's an easy fix, comments are appreciated.
Update 2: Our SysAdmin solved the e-mail issue with the following lines in loginfo:
^project /usr/bin/mailx -s '[cvs-commit] %{sVv}' [email protected]
^server_config /usr/bin/mailx -r [email protected] -s '[cvs-commit] %{sVv}' [email protected]
I'm no UNIX expert, so that's why I'm posting this here - that way I can use it the next time I need to set this up. Alternative approaches are welcome and encouraged!
If you're using Tomcat 4.1.x, did you know you can deploy using an Ant task that ships with Tomcat. You'll need to add $CATALINA_HOME/server/lib/catalina-ant.jar to your classpath, but then you can configure your ant task as follows:
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
<deploy url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="/${name}"
war="file:/${dist.dir}/${name}.war" />
I haven't tried it, but it looks cool. Right now I use a simple copy task that works pretty well for me, so no need to change at this point.
<target name="deploy" depends="package-web" if="tomcat.home"
description="unwar into the servlet container's deployment directory">
<unwar src="${webapp.dist}/${webapp.war}"
dest="${tomcat.home}/webapps/${webapp.name}"/>
</target>
If you know of any advantages to using Tomcat's deploy task, or you'd like to share your experience using it - please post a comment.
