Results 1 to 4 of 4

Thread: Failed to resolve package classic and other package build errors

  1. #1
    Sencha User
    Join Date
    Mar 2011
    Location
    Arvada, CO
    Posts
    404

    Default Failed to resolve package classic and other package build errors

    I have a repository where I keep all of my packages, which were created and built on my machine. These changes are committed to an SVN repo for others to checkout and commit to. Up until this point, I've been the only developer working in this repo, and because these packages were built on my machine, I haven't had an issue, but if I make a clean checkout of this repository, I get errors:
    Failed to resolve package classic
    Failed to resolve package theme-crisp
    Toolkit "classic" not found
    ...
    package.json
    Code:
    {
      "framework": "ext",
      "theme": "theme-crisp",
      "toolkit": "classic",
      "name": "Viewer",
      "namespace": "Viewer",
      "type": "code",
      "creator": "Me",
      "summary": "Viewer",
      "detailedDescription": "Viewer",
      "version": "1.0.9",
      "compatVersion": "1.0.0",
      "format": "1",
      "slicer": {
        "js": [{
          "path": "${package.dir}/sass/example/custom.js",
          "isWidgetManifest": true
        }]
      },
      "output": "${package.dir}/build",
      "local": true,
      "sass": {
        "namespace": "Viewer",
        "etc": ["${package.dir}/sass/etc/all.scss", "${package.dir}/${toolkit.name}/sass/etc/all.scss"],
        "var": ["${package.dir}/sass/var", "${package.dir}/${toolkit.name}/sass/var"],
        "src": ["${package.dir}/sass/src", "${package.dir}/${toolkit.name}/sass/src"]
      },
      "classpath": ["${package.dir}/src", "${package.dir}/${toolkit.name}/src"],
      "overrides": ["${package.dir}/overrides", "${package.dir}/${toolkit.name}/overrides"],
      "requires": []
    }
    It feels like the build cannot find the ext dir, which is odd, as it builds just fine on the original directory. However, I was able to generate a log running sencha -sd, which showed me all of the environment variables, and there are a couple that look suspicious (mainly framework.classpath):
    ext.dir : C:\Sencha\Controls/ext
    framework.build.dir : ${package.output.base}
    framework.classpath : C:\Sencha\Controls\packages\Viewer/src
    framework.dir : C:\Sencha\Controls\ext
    A couple of notes:
    • Minimized the full path being displayed here... Sencha dir contains my Controls workspace, which contains my packages, ext dirs
    • These paths are all valid, but I figured the framework.classpath would point to somewhere in the ext dir?


    Not really sure what the problem is here... like I said, originating directory builds just fine, but once I checkout into another directory or on a different machine, I get these errors. Anyone have an idea of what's going on here? Is my classpath set up incorrectly? If so, how do I change Sencha Cmd environment variables?

    Other information:
    • Sencha Cmd 6.1.2.15
    • Ext JS 6.0.2
    • packages were generated by running sencha generate package packageName

  2. #2
    Sencha User
    Join Date
    Mar 2011
    Location
    Arvada, CO
    Posts
    404

    Default

    I was doing something dumb... please delete this thread.

  3. #3
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    Glad to hear you've sorted it out, and thanks for following up here.

  4. #4
    Sencha Premium User jvandemerwe's Avatar
    Join Date
    Apr 2009
    Location
    Raalte, Netherlands
    Posts
    260

    Default

    I have also spent some time finding out why it was not working (and I have done quite a lot of packages).
    Here a small resumé:

    Sencha CMD 6.2.1.5 (early build)

    Ext in folder /ext621 (of the workspace, created after a sencha workspace add framework)

    Kind of package to build:
    -framework: ext
    - toolkit: classic

    Code:
    sencha generate package --framework ext621 --toolkit classic --name YourPackageName

    Source code goes in:

    Code:
    /classic/src
    If it is only code then you can change your .sencha.cfg:

    Code:
    #==============================================================================
    # Custom Properties - Place customizations below this line to avoid merge
    # conflicts with newer versions
    
    skip.style=1
    
    package.cmd.version=6.2.1.5
    to avoid sass compilation errors.


    After this my Ext.grid.Panel dependency problems where over.

Similar Threads

  1. Failed to resolve package
    By raminbp in forum Sencha Cmd
    Replies: 4
    Last Post: 26 Dec 2015, 10:30 PM
  2. Failed to resolve package [email protected]
    By olakara in forum Ext JS 6.x Q&A
    Replies: 5
    Last Post: 24 Apr 2015, 6:59 AM
  3. Failed to resolve package during refresh
    By iamcootis in forum Ext 5: Q&A
    Replies: 1
    Last Post: 17 Feb 2015, 5:30 AM
  4. Build Problem! Failed to resolve package!
    By Landish in forum Sencha Architect 3.x: Q&A
    Replies: 6
    Last Post: 31 Mar 2014, 10:38 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
  •