Backstory:
Our application is using a custom theme that we've extended from Neptune. We're integrating the workspace/theme build process now into our own build system.
Part of the workspace generation copies ExtJS into the workspace directory, which is something we want to avoid in our source repository.
Problem:
To avoid having a copy of the ExtJS framework in our source, we're generating our theme passing in the -sdk parameter to point to an existing directory containing ExtJS.
sencha -sdk ../../path/to/ExtJS/ generate theme --extend ext-theme-neptune our-neptune-theme
I've created a local.properties to assign the package.base.names and package.base.packages properties so that inherit-resources knows where to look to copy image assets. This works well if we only rely on sencha ant build.
Then when building the theme using sencha package build the image assets are not found. Examining the debug output, the inherit-resources target doesn't copy the resources. Does anyone know why the package command would be dropping the custom build properties, but the ant build command would be working just fine?
It's not a deal break for our project to integrate sencha cmd into our build process, but I would like to have a better understanding of how that delegation works between sencha package and the ant build targets.
Our goal is to have as little as possible added to our source repository(i.e. only one copy of the framework) and still integrate the theme build into our build process.
Our application is using a custom theme that we've extended from Neptune. We're integrating the workspace/theme build process now into our own build system.
Part of the workspace generation copies ExtJS into the workspace directory, which is something we want to avoid in our source repository.
Problem:
To avoid having a copy of the ExtJS framework in our source, we're generating our theme passing in the -sdk parameter to point to an existing directory containing ExtJS.
sencha -sdk ../../path/to/ExtJS/ generate theme --extend ext-theme-neptune our-neptune-theme
I've created a local.properties to assign the package.base.names and package.base.packages properties so that inherit-resources knows where to look to copy image assets. This works well if we only rely on sencha ant build.
Then when building the theme using sencha package build the image assets are not found. Examining the debug output, the inherit-resources target doesn't copy the resources. Does anyone know why the package command would be dropping the custom build properties, but the ant build command would be working just fine?
It's not a deal break for our project to integrate sencha cmd into our build process, but I would like to have a better understanding of how that delegation works between sencha package and the ant build targets.
Our goal is to have as little as possible added to our source repository(i.e. only one copy of the framework) and still integrate the theme build into our build process.
Aucun commentaire:
Enregistrer un commentaire