It's a simple matter to create a self-executable war, either with Jetty or Winstone. I'd remove Maven from the equation and just give an url to the repository. If you want, you could also publish a jnlp file with the war so he really wouldn't need to do anything else but click on the link to start the app.
Kalle On Tue, Jun 16, 2009 at 6:57 PM, Clifton<[email protected]> wrote: > > Skinny pom is a hack. What I'd like to do is have him run my project > directly. Sharing a pom requires too many steps. You have to detach the pom > from the email, save it sin an empty folder such that it doesn't conflict > with other things (conflicts are not likely the first few times but possible > when I get happy and start using the idea more often with more advanced > people), run the command, then diagnose why it didn't work on the first > attempt. (Was there corruption in the detached email? Is there an XSD in the > pom trying to resolve to a absolute path on my machine? Did I mis-type a > dependency in the pom or forget to close a tag?) I'm leaning towards using > an assembly which describes the Tomcat structure since there's likely two > war apps involved but even then there's no straight forward way to unpack a > tomcat tar and launch on a single command. I'm looking for something like an > executable war or a jar in a war or something. Maybe I'll whip up something > quick/dirty in Groovy that embodies the idea and release it. I was just > checking to see if it had been done or if there was an alternate approach. > > > Stephen Connolly-2 wrote: >> >> you could give him a skinny pom that has the deployed war as a dependency. >> >> war packaging will pull down the dependency and merge it with your >> (empty) skinny pom >> >> in which case you just need to give him the skinny pom file. this is >> extra nice as you can configure jetty defaults in the skinny pom and >> define a default goal so all he needs to do is run "mvn" >> >> On 16/06/2009, Clifton <[email protected]> wrote: >>> >>> I gotta believe by now there is a slick way to run a war file released to >>> an >>> internal repository under a plugin like jetty or cargo. I'd like to be >>> able >>> to share a set of web-apps I created with a colleague without him needing >>> to >>> download my source. Something like "Just run 'mvn >>> -DreleasedWar=com.mycompany:mywarproj:1.2 jetty:run' from the command >>> line" >>> would be a nice way to share work I've done. The idea would be the plugin >>> resolves the war dependency using typical dependency resolve logic and >>> spins >>> up the container pointing to the war file in the local repo. Maybe it >>> would >>> copy from the local repo into the default build 'targeet' dir or >>> something. >>> has there ever been something like this done? \ >>> >>> ----- >>> Cliff >>> http://codeforfun.wordpress.com >>> http://www.nabble.com/file/u156847/Cliff-in-the-lab.png >>> -- >>> View this message in context: >>> http://www.nabble.com/Run-a-war-set-of-wars-released-in-internal-repo-tp24061123p24061123.html >>> Sent from the Maven - Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > > ----- > Cliff > http://codeforfun.wordpress.com > http://www.nabble.com/file/u156847/Cliff-in-the-lab.png > -- > View this message in context: > http://www.nabble.com/Run-a-war-set-of-wars-released-in-internal-repo-tp24061123p24065719.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
