We had a bug so adding to conf/lib was not working. This bug is not solved, but not in any release.
As temporary workaround, adding to wrapper.conf can be an option (works for the wrapper, but not if you start with the shell).
Thx, Eric On 12/09/2012 22:32, Michael J. Hammel wrote:
According to Writing a Custom Mailet (http://james.apache.org/server/3/dev-extend-mailet.html), the deployment process for 3.0 is to copy the JAR file to <james>/conf/lib. However, this alone doesn't appear to be enough. I added a wrapper.java.classpath.<num> entry to <james>/conf/wrapper.conf that references the JAR file and that seemed to do that trick. Is use of the wrapper.conf the correct manner of deployment or is this still a work in progress for 3.0?
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
