[GRADLE-1224] Setting the Jetty HTTP port via system property and Gradle property Created: 17/Nov/10  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Improvement
Reporter: Benjamin Muschko Assignee: Unassigned
Resolution: Won't Fix Votes: 2

Issue Links:
dependent
dependent on GRADLE-1365 Allow override of plugin convention p... Resolved

 Description   

Hi,

it would be great to be able to set the Jetty httpPort property via a system property and/or Gradle property. Right now you have to make a change to your Gradle build script (like adding a configuration task) to make this work. The plugin could predefine a property name (e.g. jettyHttpPort) that replaces the default port value.

Examples:

  • System property: gradle jettyRun -DjettyHttpPort=9090
  • Gradle property (gradle.properties): jettyHttpPort=9090

 Comments   
Comment by Benjamin Muschko [ 11/Dec/10 ]

I sent a pull request for this on GitHub.

Comment by Peter Niederwieser [ 02/Feb/11 ]

I understand the need for this feature. But I wonder if instead of manually checking system properties, we could improve the way convention objects work so that "gradle jettyRun -PhttpPort=7070" works out of the box.

Comment by Benjamin Muschko [ 03/Feb/11 ]

I would be OK with enriching convention objects also. Actually, that's better. Do you want me to open another ticket for that?

Comment by Peter Niederwieser [ 03/Feb/11 ]

Someone already created GRADLE-1365.

Comment by Benjamin Muschko [ 04/Feb/11 ]

Great, thanks. If you want you can mark this ticket as a duplicate.

Comment by Peter Niederwieser [ 04/Feb/11 ]

I've already marked it as dependent.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 16/Jan/17 ]

The Jetty plugin has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore.

Generated at Wed Jun 30 11:50:08 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.