Hi all,
I've just noticed the web module's pom got a jetty plugin config to run on por
80:
<connectors>
<connector
implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>80</port>
<maxIdleTime>10000</maxIdleTime>
</connector>
</connectors>
This is not allowed in linux afaik, as the port has to be > 1024 or well run
the process as root.
Am I the only not being able of mvn jetty:run or trying to do so on linux? If
not, how could I do that? Or should we revert to the default port 8080?
cheers,
Gabriel
Gabriel Roldán ha scritto:
Hi all,
I've just noticed the web module's pom got a jetty plugin config to run on por 80:
<connectors>
<connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>80</port>
<maxIdleTime>10000</maxIdleTime>
</connector>
</connectors>
This is not allowed in linux afaik, as the port has to be > 1024 or well run the process as root.
Am I the only not being able of mvn jetty:run or trying to do so on linux? If not, how could I do that? Or should we revert to the default port 8080?
Absolutely. I think that change was made by Jody (and by mistake, too).
Cheers
Andrea
Thanks Andrea,
I've set it to 8080 and let maxIdleTime as it was since I'm sure Jody had good
reasons to add it.
Cheers,
Gabriel
On Thursday 17 May 2007 17:13:52 Andrea Aime wrote:
Gabriel Roldán ha scritto:
> Hi all,
> I've just noticed the web module's pom got a jetty plugin config to run
> on por 80:
>
> <connectors>
> <connector
> implementation="org.mortbay.jetty.nio.SelectChannelConnector">
> <port>80</port>
> <maxIdleTime>10000</maxIdleTime>
> </connector>
> </connectors>
>
> This is not allowed in linux afaik, as the port has to be > 1024 or well
> run the process as root.
>
> Am I the only not being able of mvn jetty:run or trying to do so on
> linux? If not, how could I do that? Or should we revert to the default
> port 8080?
Absolutely. I think that change was made by Jody (and by mistake, too).
Cheers
Andrea