[ https://issues.redhat.com/browse/JBTM-3293?page=com.atlassian.jira.plugin... ] Martin Stefanko edited comment on JBTM-3293 at 4/21/20 9:56 AM: ---------------------------------------------------------------- The jar artifact can still be consumed in other runtimes/user applications if they want to do so I would strongly suggest keeping publishing this artifact. The war module I proposed makes sense only for WFLY deployments. I haven't tested other similar runtimes. But this issue was about deploying this artifact to the wildfly server. A user can do the same add a lra-coordinator-jar dependency to their war archive together with narayana-lra dependency and a bunch of other dependencies they may need. In my experience I've never added war packaged maven dependency so I don't know what are the correct guidelines here but I personally would prefer to have both lra-coordinator-jar and lra-coodinator-war modules. was (Author: mstefank): The jar artifact can still be consumed in other runtimes/user applications if they want to so I would strongly suggest keeping publishing this artifact. The war module I proposed makes sense only for WFLY deployments. I haven't tested other similar runtimes. But this issue was about deploying this artifact to the wildfly server. A user can do the same add a lra-coordinator-jar dependency to their war archive together with narayana-lra dependency and a bunch of other dependencies they may need. In my experience I've never added war packaged maven dependency so I don't know what are the correct guidelines here but I personally would prefer to have both lra-coordinator-jar and lra-coodinator-war modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)