Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    Success! Looks like we've fixed this one. According to our records the fix was applied for SDKTOOLS-171 in a recent build.
  1. #1
    Sencha Premium Member
    Join Date
    Dec 2009
    Location
    Rhode Island
    Posts
    223
    Vote Rating
    21
    dmulcahey will become famous soon enough dmulcahey will become famous soon enough

      0  

    Default Sencha ant build can no longer find compass after switching to build 181

    Sencha ant build can no longer find compass after switching to build 181


    Background information:
    Win7x64
    Sencha Cmd 181
    Command Executed: sencha ant build

    I had everything working before switching to build 181. After installing the new version I am getting this error:

    Code:
    [INFO ]         [shellscript] (path removed)>compass compile --boring (path removed)\resources\sass\default --css-dir (path removed)\resources\css/default --force
    [INFO ]
    [ERROR]         The following error occurred while executing this line:
    (path removed)\.sencha\app\build-impl.xml:93: The following error occurred while executing this line:
    (path removed)\.sencha\app\build-impl.xml:117: The following error occurred while executing this line:
    jar:file:/C:/Users/(username)/bin/Sencha/Cmd/3.0.0.181/sencha.jar!/com/sencha/ant/antlib.xml:322: shellscript returned: 1
    (path removed) is the path on my hd to the project folder.

    here is the output from compass -v
    Code:
    (path removed)>compass -v
    Compass 0.12.2 (Alnilam)
    Copyright (c) 2008-2012 Chris Eppstein
    Released under the MIT License.
    Compass is charityware.
    Please make a tax deductable donation for a worthy cause: http://umdf.org/compass

  2. #2
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,294
    Vote Rating
    121
    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 report! I have opened a bug in our bug tracker.

  3. #3
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,294
    Vote Rating
    121
    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


    The problem is caused by the x-shell custom task not getting the right PATH variable.

    Thanks for the bug report - we'll try to get a refresh out early/mid next week.
    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
    Join Date
    Dec 2009
    Location
    Rhode Island
    Posts
    223
    Vote Rating
    21
    dmulcahey will become famous soon enough dmulcahey will become famous soon enough

      0  

    Default


    Thanks! You guys are cranking info and fixes out lightning fast! Much appreciated.

  5. #5
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,294
    Vote Rating
    121
    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


    Couple possible workarounds in the current build:
    • add "skip.sass=1" to local.properties in your app or workspace folder. That file will not exist in either location but is designed to contain local (as in per-individual) build overrides that apply to the app or all apps in the workspace. This will allow the overall build to run but obviously skips compass.
    • tweak the body of the "-sass" target in .sencha/app/build-impl.xml to either use the full path to compass or something more general (like a new property) depending on if you are trying to share the project with others.

      <x-shell>
      ${compass.dir}/compass compile --boring @{sass} --css-dir ${app-css-dir}/${sass.name} --force
      </x-shell>

      And define "compass.dir=<some-local-path>" in your local.properties

    Of course this will not be needed for long.
    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!"

Thread Participants: 1