Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: eclipse-plugin
    • Labels:
      None

      Description

      Users of Geronimo 1.1 are not able to develop on recent versions of Eclipse. I don't think this was understood when we decided not to include 1.1 support in recent versions of GEP. I'm interested in adding this support

        Activity

        Hide
        Delos Dai added a comment -

        I have integrated 1.1 server adapter into GEP 2.2. Mark it as resolved. Any bugs found, please create a new JIRA.

        Thanks!

        Show
        Delos Dai added a comment - I have integrated 1.1 server adapter into GEP 2.2. Mark it as resolved. Any bugs found, please create a new JIRA. Thanks!
        Hide
        Delos Dai added a comment -

        In general, I think there are two major change for the JIRA
        1) Old 1.1 server adapter use EMF as a modeling tool to handle deployment plan, but in GEP 2.1 and 2.2, EMF has been replaced with JAXB. So the first change is to handle deployment plan with JAXB instead of EMF.

        2) Deployment plan editor enhancement. Since GEP 2.1&2.2 has enhance the usability of deployment plan editor, 1.1 server adapter has to use the new editor for consistency.

        But I have another concern about this JIRA. If it's implemented in GEP 2.2, the final release of GEP 2.2 contain four server adapters - 1.1, 2.0,2.1,2.2 . Seems it's a all-in-one release. But not all users need four server adapters, is it necessary to bundle four server adapters into one distribution?

        Any comments?

        Show
        Delos Dai added a comment - In general, I think there are two major change for the JIRA 1) Old 1.1 server adapter use EMF as a modeling tool to handle deployment plan, but in GEP 2.1 and 2.2, EMF has been replaced with JAXB. So the first change is to handle deployment plan with JAXB instead of EMF. 2) Deployment plan editor enhancement. Since GEP 2.1&2.2 has enhance the usability of deployment plan editor, 1.1 server adapter has to use the new editor for consistency. But I have another concern about this JIRA. If it's implemented in GEP 2.2, the final release of GEP 2.2 contain four server adapters - 1.1, 2.0,2.1,2.2 . Seems it's a all-in-one release. But not all users need four server adapters, is it necessary to bundle four server adapters into one distribution? Any comments?
        Hide
        Donald Woods added a comment -

        Just looking for a rationale to why this was being looked at again, as the original issue description didn't point out the Eclipse incompatibilities....
        I assume this would allow users to run Eclipse and GEP with Java SE 6, but Geronimo 1.1 did not officially support JDK 6 (even though it should work for Little-G but may not for the full JavaEE server), so that may need to be mentioned in the updated GEP 2.2 docs.

        Minimal support for 1.1 seems okay, but I worry about the server status polling that we had to do for 1.1.x and if we'll be reintroducing all those old usability issues again....

        Show
        Donald Woods added a comment - Just looking for a rationale to why this was being looked at again, as the original issue description didn't point out the Eclipse incompatibilities.... I assume this would allow users to run Eclipse and GEP with Java SE 6, but Geronimo 1.1 did not officially support JDK 6 (even though it should work for Little-G but may not for the full JavaEE server), so that may need to be mentioned in the updated GEP 2.2 docs. Minimal support for 1.1 seems okay, but I worry about the server status polling that we had to do for 1.1.x and if we'll be reintroducing all those old usability issues again....
        Hide
        Kevan Miller added a comment -

        IIRC, we didn't support 1.1 servers, because we didn't have any motivation to do the work. And older GEP server adapters could support 1.1 servers. However, if older GEP server adapters won't work on recent versions of Eclipse, then there may have been a gap in our reasoning...

        If Delos or Tim want to add this support (and test it), I don't see why that would be a problem. Unless you feel that it is detrimental to the functionality of GEP or is unsupportable, then I don't see why this would be an issue.

        Show
        Kevan Miller added a comment - IIRC, we didn't support 1.1 servers, because we didn't have any motivation to do the work. And older GEP server adapters could support 1.1 servers. However, if older GEP server adapters won't work on recent versions of Eclipse, then there may have been a gap in our reasoning... If Delos or Tim want to add this support (and test it), I don't see why that would be a problem. Unless you feel that it is detrimental to the functionality of GEP or is unsupportable, then I don't see why this would be an issue.
        Hide
        Donald Woods added a comment -

        Why? We decided long ago that we would drop the 1.1 server support from GEP 2.x. Are we seeing enough users in the community asking for this to warrant the extra development and test overhead? Having to support 1.1.x, 2.0.x, 2.1.x and 2.2.x servers in the same GEP is asking a lot, considering there are no plans to release another 1.1.x or 2.0.x release.

        Show
        Donald Woods added a comment - Why? We decided long ago that we would drop the 1.1 server support from GEP 2.x. Are we seeing enough users in the community asking for this to warrant the extra development and test overhead? Having to support 1.1.x, 2.0.x, 2.1.x and 2.2.x servers in the same GEP is asking a lot, considering there are no plans to release another 1.1.x or 2.0.x release.

          People

          • Assignee:
            Delos Dai
            Reporter:
            Delos Dai
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development