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.

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Sep 2012
    Posts
    8
    Vote Rating
    1
    cburgdorf is on a distinguished road

      0  

    Default Trying to build app with command line tools raises exception

    Trying to build app with command line tools raises exception


    When I try to build my app with the Sencha SDK Commandline Tools I constantly get a "not a directory" exception. I opened a posting on Stack Overflow that also has a screenshot of the error.

    http://stackoverflow.com/questions/12423308/why-does-sencha-build-app-fail

    A
    ny help would be appreciated

    UPDATE
    I figured out it has something to do with the fact that I want my buildPath to be outside of the app directory. My section in the app.json looks like this:

    Code:
    "buildPaths": { 
        "production": "../deploy/frontenddemo/production", 
        "testing": "../deploy/frontenddemo/testing", 
        "package": "../deploy/frontenddemo/package", 
        "native": "../deploy/frontenddemo/native"
    },

    If I change it to:


    Code:
    "buildPaths": { 
        "production": "build/production", 
        ...
    },

    Everything works as expected. I don't know why. It should be possible to have the builds outside the app directory I guess.

  2. #2
    Sencha User
    Join Date
    Sep 2012
    Posts
    8
    Vote Rating
    1
    cburgdorf is on a distinguished road

      0  

    Default


    Ok, after a lot of try and error. I found the root cause of this issue.

    My app.json looked like this:

    Code:
        "archivePath": "../deploy/frontenddemo/archive/",
        "buildPaths": {
            "testing": "../deploy/frontenddemo/testing",
            "production": "../deploy/frontenddemo/production",
            "package": "../deploy/frontenddemo/package",
            "native": "../deploy/frontenddemo/native"
        },
    The problem with this structure is that both archive and builds produce a directory "sencha" outside of the configured path. Meaning they both create

    Code:
    ../deploy/frontenddemo/sencha
    with different contents. I wonder if that is documented somewhere?

    The fix was easy. I just changed the paths to this:

    Code:
        "archivePath": "../deploy/frontenddemo/archive/",
        "buildPaths": {
            "testing": "../deploy/frontenddemo/builds/testing",
            "production": "../deploy/frontenddemo/builds/production",
            "package": "../deploy/frontenddemo/builds/package",
            "native": "../deploy/frontenddemo/builds/native"
        },

  3. #3
    Sencha User
    Join Date
    Sep 2012
    Posts
    8
    Vote Rating
    1
    cburgdorf is on a distinguished road

      0  

    Default


    Would be great to have someone confirm what I figured out and maybe point out if its documented.

    Thanks,

    Christoph

Tags for this Thread