The war itself deploys to a Tomcat instance on a testing machine just fine
- that Tomcat includes the javamail and activation in it's installation
hence they are declared as provided in our project's POM.
This boils down to not knowing if the extra dependencies within the maven
plugin are
What you wrote as a set of suggestions was my original attempt. Then I read
(possibly spuriously) that Tomcat ignored either mailx or activation when
shipped inside a WAR, and that if both Tomcat (via it's lib/) and the WAR
contained either of those then the duplicate JAR would result in an error.
Unless you're doing something unconventional, it shouldn't be painful. We
may getting off-topic, but if you would like to post your project pom and
any parents, I'll take a peek and see if there's anything that leaps out at
me.
My gut says your build is omitting dependencies that Maven expects to
Is there a way of getting this to work?
We have a Maven project that depends on Apache's commons-email. We use JNDI
to look up a mail Session. We use the following in our POM:
plugin
groupIdorg.apache.maven.plugins/groupId
A few things you might take a look at. I don't think the Tomcat plugin
requires javax.mail or activation by itself. That part of the plugin
definition probably isn't doing what you intended it to do. I think you
might want to remove the extraDependencies section.
By including
project
...
