Multiple WebApp Directories to run Maven Overlays. about run-jetty-run HOT 17 OPEN

Thanks, I wasn't familiar with that Jetty feature.

It will be the milestone of 1.2.2 .

Move the milestone to 1.3 or 1.3.1

I am not sure if we really need this or not.

If there's no any user provide reasonable usecase , 
I am thinking to leave this one first.

I think it's making things too complicated...

I would really appreciate this feature. My Usecase is that I am working with 
GWT and Tapestry in the same context. Therefore I have the GWT-Project as a WAR 
overlay to the Tapestry-Project. Currently this doesn't work with run-jetty-run 
which is a pity since run-jetty-run is recommended for Tapestry-Development.

[deleted comment]

This is now handled automatically by the Jetty Maven plugin. We are currently 
using this extensively between the 5 or so webapps in our product line. 
Unfortunately, we can no longer use Run-Jetty-Run due to this limitation.

Initial Maven Jetty Plugin ticket:
http://jira.codehaus.org/browse/JETTY-1027

Docs on the feature:
http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin#Using_Overlayed_WARs

We've now had to revert to using the old method of integrating the Maven Jetty 
Plugin into eclipse:
http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Plugin+ins
ide+Eclipse

Which isn't as nice as Run-Jetty-Run ;)

I think it's ok to be in next release,let me think about the UI part.

Just like to add my vote for this issue.  We have two projects with WAR files 
that we would like to run under the same Jetty instance.  One is a GWT war, and 
the other just a regular WAR (with Servlets etc.)

In the same boat as comments #10 & #12...looking fwd to seeing this soon!

Any chance of this being included in the near future? I could really use that 
feature.

Note that the following jetty.xml configuration can provide a workaround:
<Configure class="org.mortbay.jetty.Server">
  <Get name="handler">
    <Set name="baseResource">
      <New class="org.mortbay.resource.ResourceCollection">
        <Arg>
          <Array type="java.lang.String">
            <Item>src/main/webapp</Item>
            <Item>path/to/other/webapp</Item>
          </Array>
        </Arg>
      </New>
    </Set>
  </Get>
</Configure>

+1. I deploy my javascript files on a different source directory (default 
configuration imposed by jasmine-maven-plugin), so I could really use this 
feature either.

My scenario:
src/main/webapp/
src/main/javascript/

+1 from my side. I'm using it in a multi module project where final webapp is 
assembled with overlays. 
I can use jetty plugin from commandline with jetty:run (it works with no issue)
but I can not use run-jetty-run from within eclipse - it would be extremely 
useful for developing and debuging etc.