Uploaded image for project: 'Apache Tomcat Maven Plugin'
  1. Apache Tomcat Maven Plugin
  2. MTOMCAT-91

tomcat-maven-plugin hard codes INITIAL_CONTEXT

Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.1
    • backlog
    • None
    • None

    Description

      Hi guys,

      Thanks for a great Maven plugin in tomcat-maven-plugin. I am using it in my Open Source project and it works really well.

      I recently tried getting tomcat-maven-plugin to coexist with jetty-maven-plugin. There is a problem that appears to sit somewhere in the middle of the two projects, and requires both of you to agree on a solution

      Basically tomcat-maven-plugin appears to be setting INITIAL_CONTEXT at the VM level (whereas Jetty does not) and this means that Jetty ends up trying to use Tomcat's JNDI implementation. It would be great if Tomcat/Jetty could live together in a build process, so that I could run my integration tests against multiple appservers.

      Please see JETTY-1370 for an example pom.xml and an error log, and also discussion from the jetty-maven-plugin guys about what might be 'wrong'.

      Regards,

      Richard.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            kennardconsulting Kennard Consulting

            Dates

              Created:
              Updated:

              Slack

                Issue deployment