Apache Tomcat Maven Plugin
  1. Apache Tomcat Maven Plugin
  2. MTOMCAT-101

Add the ability to deploy to a Tomcat instance on the filesystem rather than via HTTP

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: tomcat6, tomcat7
    • Labels:
      None

      Description

      It would be great to have the ability to deploy a webapp to Tomcat without using HTTP and the Tomcat Manager, by simply doing a filesystem copy of the built war file to the location specified.

      We currently use an ant profile to do this, but want to replace this with a proper plugin.

      We will be looking at contributing this feature in the near future.

        Activity

        Steve Swinsburg created issue -
        Olivier Lamy (*$^¨%`£) made changes -
        Field Original Value New Value
        Fix Version/s 2.0 [ 12317943 ]
        Olivier Lamy (*$^¨%`£) made changes -
        Fix Version/s 2.1 [ 12319450 ]
        Fix Version/s 2.0 [ 12317943 ]
        Olivier Lamy (*$^¨%`£) made changes -
        Fix Version/s 2.1 [ 12320767 ]
        Fix Version/s 2.0 [ 12319450 ]
        Hide
        Glen Mazza added a comment -

        What's wrong with using HTTP? It's not that hard to configure: http://www.jroller.com/gmazza/entry/web_service_tutorial#maventomcat, and is the proper, Tomcat-defined way to deploy a webapp remotely that takes into account permissions and whatever lifecycle steps Tomcat needs to do to deploy/undeploy/redeploy a web application. I think what you're asking for should be done via the Maven Antrun plugin, if you're still inclined to go that route. But to provide a formal method for copying files to Tomcat's remote directory would be like endorsing that method of deployment as well as needlessly duplicating the Antrun plugin, things nobody should be doing and also something that can also raise many other JIRAs of subsequent problems that occur with this alternative route.

        Show
        Glen Mazza added a comment - What's wrong with using HTTP? It's not that hard to configure: http://www.jroller.com/gmazza/entry/web_service_tutorial#maventomcat , and is the proper, Tomcat-defined way to deploy a webapp remotely that takes into account permissions and whatever lifecycle steps Tomcat needs to do to deploy/undeploy/redeploy a web application. I think what you're asking for should be done via the Maven Antrun plugin, if you're still inclined to go that route. But to provide a formal method for copying files to Tomcat's remote directory would be like endorsing that method of deployment as well as needlessly duplicating the Antrun plugin, things nobody should be doing and also something that can also raise many other JIRAs of subsequent problems that occur with this alternative route.
        Olivier Lamy (*$^¨%`£) made changes -
        Fix Version/s backlog [ 12317944 ]
        Fix Version/s 2.1 [ 12320767 ]
        Hide
        Olivier Lamy (*$^¨%`£) added a comment -

        There are plenty of maven plugins to copy a file to a file system structure.
        So you can certainly one of those.

        Show
        Olivier Lamy (*$^¨%`£) added a comment - There are plenty of maven plugins to copy a file to a file system structure. So you can certainly one of those.
        Olivier Lamy (*$^¨%`£) made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s backlog [ 12317944 ]
        Resolution Won't Fix [ 2 ]

          People

          • Assignee:
            Olivier Lamy (*$^¨%`£)
            Reporter:
            Steve Swinsburg
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development