Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-1224

Setting the Jetty HTTP port via system property and Gradle property

    Details

    • Type: Improvement
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 0.9
    • Fix Version/s: None

      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

        Issue Links

          Activity

          Hide
          bmuschko Benjamin Muschko added a comment -

          I sent a pull request for this on GitHub.

          Show
          bmuschko Benjamin Muschko added a comment - I sent a pull request for this on GitHub.
          Hide
          pniederw Peter Niederwieser added a comment - - edited

          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.

          Show
          pniederw Peter Niederwieser added a comment - - edited 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.
          Hide
          bmuschko Benjamin Muschko added a comment -

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

          Show
          bmuschko Benjamin Muschko added a comment - I would be OK with enriching convention objects also. Actually, that's better. Do you want me to open another ticket for that?
          Hide
          pniederw Peter Niederwieser added a comment -

          Someone already created GRADLE-1365.

          Show
          pniederw Peter Niederwieser added a comment - Someone already created GRADLE-1365 .
          Hide
          bmuschko Benjamin Muschko added a comment -

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

          Show
          bmuschko Benjamin Muschko added a comment - Great, thanks. If you want you can mark this ticket as a duplicate.
          Hide
          pniederw Peter Niederwieser added a comment -

          I've already marked it as dependent.

          Show
          pniederw Peter Niederwieser added a comment - I've already marked it as dependent.
          Hide
          bmuschko Benjamin Muschko added a comment -

          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!

          Show
          bmuschko Benjamin Muschko added a comment - 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!

            People

            • Assignee:
              Unassigned
              Reporter:
              bmuschko Benjamin Muschko
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Development