Hi Benoit,
> I would be carefull: the maven module "util" has a depedency to > javax.mail, causing some potential dependecy conflicts for users. I think it’s ok to have optional dependencies. Only those who want to use the functionality that requires javax.mail would have to provide it at runtime. Those who don’t need that functionality don’t need to worry about javax.mail. We would only have to document this. However (as per below) I think it would be better to have no dependencies than to have an optional dependency on javax.mail. > As such, your proposition makes sense to me if we remove > ScriptChecker & ScriptCheckMailAdapter. > > Maybe it can be moved as a usage example? Good idea! So here is what I could do: * Move what is relevant in utils to core * Rename “jsieve-core” to just “jsieve” * Rename “jsieve-util” to “jsieve-examples” Only jsieve would be deployed as a single-jar library with no dependencies: the ideal kind of library!! > From the few extensions I contributed to JSIEVE, I would consider it > stable thus would agree with a 1.0.0 release. Ok, cool. Let’s get back to this after we resolve the current issues. If you agree with this approach, then I will create a Jira Issue this time and work against that. :-) Cheers, =David --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
