Results 1 to 2 of 2

Thread: No more cmd.jvm.* in sencha.cfg leads to Team City Issues

  1. #1

    Default No more cmd.jvm.* in sencha.cfg leads to Team City Issues

    I am getting java heap size and GC errors when building apps with complex themes.

    As of cmd 6.5 according to the sencha.cfg located inte Sencha Cmd install folder, the possibility to send jvm arguments to the jvm is now gone. This is a major break.!!

    # On previous versions, this file provided a way to specify the cmd.jvm.* properties
    # to control the execution of the JVM. To accommodate all possible execution scenarios
    # support for these properties has been removed in favor of using the _JAVA_OPTIONS
    # environment variable.

    The proposed way is to set the os environmnet variable _JAVA_OPTIONS instead.

    As this works in most scenarios, this create sproblems in Team City java agents.

    Is there any other way of setting the jvm memory configs on the command line in Sencha Cmd . Or possibility to activate the cmd.jvm.* in sencha cfg again?

  2. #2
    Sencha Premium User westy's Avatar
    Join Date
    Feb 2009
    Bath, UK


    Just run into this too, although not with TeamCity.

    It seems that Cmd outputs "Picked up _JAVA_OPTIONS" to stderr, and so breaks our build.
    Haven't found a way around it yet... did you?
    Product Architect
    Altus Ltd.

Similar Threads

    By YomeKitsuma in forum Sencha Cmd
    Replies: 3
    Last Post: 12 Oct 2012, 6:34 AM
  2. New ExtJS doc - thanks Sencha team!
    By ssamayoa in forum Ext: Discussion
    Replies: 0
    Last Post: 22 Aug 2011, 8:24 AM
  3. Well done Sencha Team!
    By SimonFlack in forum Sencha Touch 1.x: Discussion
    Replies: 0
    Last Post: 31 Mar 2011, 10:35 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts