Hybrid View

  1. #1
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,229
    Vote Rating
    114
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default Sencha Cmd - Future Java Version Requirements

    Sencha Cmd - Future Java Version Requirements


    Hi All -

    We are evaluating Java 7 API's for some of the upcoming new features of Sencha Cmd and wanted to get some feedback from you, the community, about the potential impact of requiring JRE 7. We realize many or maybe most of you have current JRE's but this is not always the case in some corporate contexts.

    The release of JRE 7u4 is most important to Sencha Cmd due to the inclusion of Java FX 2.1 with its Webview based on WebKit (see http://www.drdobbs.com/jvm/java-7u4-...-712/232901064).

    In general, however, Java 7's new FileSystem API is also potentially very useful for things like file system monitoring.

    Your feedback is most welcome.

    Best,
    Don
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  2. #2
    Sencha Premium Member
    Join Date
    Dec 2009
    Location
    Rhode Island
    Posts
    202
    Vote Rating
    19
    dmulcahey will become famous soon enough dmulcahey will become famous soon enough

      0  

    Default


    My 2 cents on this...

    I work for an Insurance Co. And we're pretty far behind. 1.6 U30 is our standard at the moment. That being said, I say go for it. I am running Jenkins, Artifactory and some other tools off of custom build servers and we are keeping those up to date (newest release of 1.7). The version Cmd uses shouldn't concern many people seeing as its a build time requirement and not a runtime requirement.

  3. #3
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,229
    Vote Rating
    114
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Thanks for the feedback. Indeed the nature of Sencha Cmd does give it some latitude there.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  4. #4
    Sencha Premium Member sonata82's Avatar
    Join Date
    Aug 2011
    Posts
    17
    Vote Rating
    6
    sonata82 is on a distinguished road

      1  

    Default


    Imho 1.6 would be the way to go.

    We are deploying our application for Java 1.6.x and for consistency reasons, compiling and building is done using the same Java version. Requiring 1.7 just for Sencha Cmd would be a showstopper for us.

  5. #5
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,229
    Vote Rating
    114
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Quote Originally Posted by sonata82 View Post
    Imho 1.6 would be the way to go.

    We are deploying our application for Java 1.6.x and for consistency reasons, compiling and building is done using the same Java version. Requiring 1.7 just for Sencha Cmd would be a showstopper for us.
    Not to debate your reasons, but I am curious why 1.6 was chosen.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  6. #6
    Sencha Premium Member sonata82's Avatar
    Join Date
    Aug 2011
    Posts
    17
    Vote Rating
    6
    sonata82 is on a distinguished road

      0  

    Default


    Quote Originally Posted by dongryphon View Post
    Not to debate your reasons, but I am curious why 1.6 was chosen.
    When the project started two years ago, Java 1.6 looked like a version which was in a stable enough state to use it (we are developing for IBM i). Originally we even started on Java 1.5, to keep the requirements for our customers as low as possible, but pretty soon moved to 1.6, primarly to get support for JAXB 2.0 and StAX.

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar