search

laudukang / run-jetty-run

Automatically exported from code.google.com/p/run-jetty-run
0 stars 0 forks source link

Multiple WebApp Directories to run Maven Overlays. #38

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I've made a minor change to RJR to allow me to easily specify Multiple WebApp 
Directories (as a 
comma separated list). This is really useful when using Maven Overlays:

http://docs.codehaus.org/display/JETTY/Multiple+WebApp+Source+Directory

I'd be happy to make this change in SVN if it's useful to others. 

Dan.

Original issue reported on code.google.com by daniel.w...@gmail.com on 23 Oct 2009 at 1:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks, I wasn't familiar with that Jetty feature.

Original comment by James.Sy...@gmail.com on 23 Oct 2009 at 2:20

GoogleCodeExporter commented 9 years ago 
It will be the milestone of 1.2.2 .

Original comment by tonylovejava on 11 Mar 2011 at 9:18

GoogleCodeExporter commented 9 years ago

Original comment by tonylovejava on 18 May 2011 at 6:06

GoogleCodeExporter commented 9 years ago 
Move the milestone to 1.3 or 1.3.1

Original comment by tonylovejava on 30 Jun 2011 at 1:30

GoogleCodeExporter commented 9 years ago

Original comment by tonylovejava on 1 Jul 2011 at 6:23

GoogleCodeExporter commented 9 years ago

Original comment by tonylovejava on 21 Jul 2011 at 4:32

GoogleCodeExporter commented 9 years ago 
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...

Original comment by tonylovejava on 15 Dec 2011 at 12:56

GoogleCodeExporter commented 9 years ago 
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.

Original comment by scara...@gmail.com on 27 Jan 2012 at 6:35

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
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 ;)

Original comment by brent.fr...@gmail.com on 4 May 2012 at 8:40

GoogleCodeExporter commented 9 years ago 
I think it's ok to be in next release,let me think about the UI part.

Original comment by tonylovejava on 5 May 2012 at 12:48

GoogleCodeExporter commented 9 years ago 
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.)

Original comment by brett.wo...@gmail.com on 4 Jul 2012 at 9:44

GoogleCodeExporter commented 9 years ago 
In the same boat as comments #10 & #12...looking fwd to seeing this soon!

Original comment by mdhil...@gmail.com on 20 Nov 2012 at 7:58

GoogleCodeExporter commented 9 years ago 
Any chance of this being included in the near future? I could really use that 
feature.

Original comment by pascal.g...@gmail.com on 9 May 2013 at 4:56

GoogleCodeExporter commented 9 years ago 
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>

Original comment by pascal.g...@gmail.com on 9 May 2013 at 6:16

GoogleCodeExporter commented 9 years ago 
+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/

Original comment by marlonjb...@gmail.com on 24 Jul 2013 at 10:59

GoogleCodeExporter commented 9 years ago 
+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.

Original comment by szy...@sindicetech.com on 23 May 2014 at 10:37