09:34:22,747 INFO [org.jboss.as.repository] (HttpManagementService-threads - 12) JBAS014900: Content added at location C:\camunda-bpm-ee-jboss-7.4.0-ee\server\jboss-as-7.2.0.Final\standalone\data\content\bf\263b6276bf61c69655191a4fb05499670f15a9\content
09:34:29,694 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015876: Starting deployment of "aotstm-ticket-service-1.0.0.war" (runtime-name: "aotstm-ticket-service-1.0.0.war")
09:34:30,183 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry activation.jar in /C:/camunda-bpm-ee-jboss-7.4.0-ee/server/jboss-as-7.2.0.Final/bin/content/aotstm-ticket-service-1.0.0.war/WEB-INF/lib/mail-1.4.1.jar does not point to a valid jar for a Class-Path reference.
09:34:30,232 INFO [org.jboss.web] (ServerService Thread Pool -- 92) JBAS018210: Register web context: /aotstm-ticket-service-1.0.0
09:34:30,289 INFO [org.jboss.as.server] (HttpManagementService-threads - 12) JBAS018559: Deployed "aotstm-ticket-service-1.0.0.war" (runtime-name : "aotstm-ticket-service-1.0.0.war")
The process does not show up on Camunda Cockpit. I have been able to deploy another process successfully, so I know the basic mechanism is working.
What I don't understand is that the WARN message is referencing a path that does not exist and I have no idea where it's getting it from. I've spent several hours trying to figure this out, now I'm hoping someone can point out my mistakes.
If additional information is needed, just ask.
Thank you.
I think I found the issue. I had switched the Maven compiler and target versions from 1.6 to 1.7. When I switched back to 1.6, the error went away.
Thank you for responding.
Michael