You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Pierce T. Wetter III" <pi...@paceap.com> on 2010/03/22 22:44:08 UTC

Silly port conflict


  So my Hudson build of Tapestry can't run the unit tests because I already have something running on port 8080. 

  Is there an easy way to change the port?

 Pierce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Silly port conflict

Posted by "Pierce T. Wetter III" <pi...@paceap.com>.
On Mar 22, 2010, at 4:57 PM, Pierce T. Wetter III wrote:

> 
> On Mar 22, 2010, at 3:22 PM, Michael Gentry wrote:
> 
>> I don't know what container you are using, but with Jetty, I do something like:
>> 
>> mvn -Djetty.port=5555 jetty:run
> 
>  It's the self tests in the tapestry T5.2 build, but I'll try that... Cool. my hudson build now builds and deploys into nexus again. 

  Doh! Spoke too soon. Mostly, jetty seems to run on port 9999, ignoring the above setting. But turns out I'm getting a conflict with selenium on port 4444 anyways. 

 Pierce


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Silly port conflict

Posted by "Pierce T. Wetter III" <pi...@paceap.com>.
On Mar 22, 2010, at 3:22 PM, Michael Gentry wrote:

> I don't know what container you are using, but with Jetty, I do something like:
> 
> mvn -Djetty.port=5555 jetty:run

  It's the self tests in the tapestry T5.2 build, but I'll try that... Cool. my hudson build now builds and deploys into nexus again. 

  Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Silly port conflict

Posted by Michael Gentry <mg...@masslight.net>.
I don't know what container you are using, but with Jetty, I do something like:

mvn -Djetty.port=5555 jetty:run

mrg


On Mon, Mar 22, 2010 at 4:44 PM, Pierce T. Wetter III <pi...@paceap.com> wrote:
>
>
>  So my Hudson build of Tapestry can't run the unit tests because I already have something running on port 8080.
>
>  Is there an easy way to change the port?
>
>  Pierce
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org