Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 7.1.5
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
After running into a minor problem with jetty-ant where it deploys a default connector listening on port 8080 while another application was listening on that port. Browsing in the sources shows that the default selector's port is hard coded for 8080. I proposed the an enhancement in IRC and was given a +1 to create this issue for tracking it. That being said, my plan is to enhance the JettyRunTask to allow for an optional attribute for the jetty XML element to configure the port that the built-in/default connector listens on.
I plan on performing the work for this effort and the work will include the appropriate unit test(s).
Attached is the patch I crafted to enable changing the default port Jetty listens on for the default connector deployed with jetty-ant. While I have proven that this works through test Ant build files, the attachment does not contain any unit tests due to me not having found a good way to unit test such a thing at this point. Without jetty-ant having any unit tests to this point, I wonder if further effort is necessary...