glassfish
  1. glassfish
  2. GLASSFISH-8772

Selective deployment in Eclipse plug-in

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 9.0pe
    • Fix Version/s: not determined
    • Component/s: other
    • Labels:
      None
    • Environment:

      Operating System: Windows Vista
      Platform: Other

    • Issuezilla Id:
      8,772

      Description

      My Eclipse workspace has three EARs, all of which are required in my GlassFish
      environment. Changing anything in a single EAR means that all three need to be
      published again. It would be nice to be able to publish a single EAR instead
      of all three.

        Activity

        Hide
        raccah added a comment -

        Take a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=270333 and see if
        that covers your issue. If so, please add comments there. If not, please file
        this in the issuetracker for the eclipse plugin at
        https://glassfishplugins.dev.java.net/issues/ and then this issue can be closed.

        Show
        raccah added a comment - Take a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=270333 and see if that covers your issue. If so, please add comments there. If not, please file this in the issuetracker for the eclipse plugin at https://glassfishplugins.dev.java.net/issues/ and then this issue can be closed.
        Hide
        Kevin Dean added a comment -

        Close, but not quite. The key is this sentence:

        "if the user wasn't changing the EAR there would be zero delta and it's up to
        the server adapter to optimize publishing in this case"

        That's the issue here: of the three EARs, I'm typically working on only one at
        a time and I have to republish all three to test my changes.

        The scenario in the Eclipse bug report would be nice to have as well (republish
        only the components of the EAR that have changed).

        Show
        Kevin Dean added a comment - Close, but not quite. The key is this sentence: "if the user wasn't changing the EAR there would be zero delta and it's up to the server adapter to optimize publishing in this case" That's the issue here: of the three EARs, I'm typically working on only one at a time and I have to republish all three to test my changes. The scenario in the Eclipse bug report would be nice to have as well (republish only the components of the EAR that have changed).
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

          • Assignee:
            kumara
            Reporter:
            Kevin Dean
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: