Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copying a whole heirarchy of files & folders #156

Open
niteco-matt opened this issue Mar 25, 2015 · 3 comments
Open

Copying a whole heirarchy of files & folders #156

niteco-matt opened this issue Mar 25, 2015 · 3 comments
Labels

Comments

@niteco-matt
Copy link

Great tool, but there's one issue I am facing with certain packages: what sort of wildcard can I use to copy all sub-folders and the files in them in the same structure? For example, look at the tinymce package, it has 3 sub-folders: plugins, skins and themes each with multiple other sub-folders of their own.. and in some packages there might be quite a few levels worth of files. Nobody wants to manually specify each sub-folder and sub-sub-folder, etc.. Do you already have some way to do this? If so, please put it in the documentation. If not, please consider adding such a useful feature. Thanks

@coaster3000
Copy link

Wondering same thing, However I am searching through all the issues tickets for this.
However I like to reference this, #21 if it is not already known.

@jerroddixon
Copy link

Not sure it's the best way to handle this, but when I ran into this issue the best way I found out to handle it is in your Gruntfile.js, under the bower section, change layout to be 'byComponent'. Then when files get transferred over they'll follow the hierarchy of 'package/js' instead of 'js/package'. I still ran into the issue where not all needed files transferred over, so I had to do things like this:

"bootstrap": {
"css" : ["**/*.css","**/*.map"],
"js" : "**/*.js",
"less": "**/*.less",
"fonts" : ["**/*.eot", "**/*.svg", "**/*.tiff", "**/*.woff"]
}

To ensure all the files I needed got transferred. Still though, everything was in the correct 'hierarchy' so it works out.

@PallasDoesCode
Copy link
Collaborator

@niteco-matt did the suggestion by @robogen solve your problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants