-
Notifications
You must be signed in to change notification settings - Fork 13
Copy a file in, with correct permissions #13
Comments
There are other methods to get files out of the .atomist/ folder on the ProjectMutableView - such as copyEditorBackingFileOrFail etc. At least you're not having to pretend they are Velocity templates! No idea if this has the same issue though... |
@alankstewart I think this is related to https://github.com/atomist/artifact-source Currently FileArtifact doesn't model permissions, so I think this'll need to be added before we can do much more on this. correction: FileArtifact has a mode field representing the unix permissions mask as an int. |
@kipz does copyEditorBackingFile pull one from the generator's files? like the top-level project directory? |
I use it pull files from .atomist/templates/ that are not Velocity templates. In my editor, I have all possible OSS license file types, and copy the appropriate one using that method, rather than the VM. If you want to generate an entirely new file, you can do that too via the ProjectMutableView. I'm not sure if that answers your question? |
I created a test that does not manage to recreate this issue. Any chance you could point us at the offending editor @jessitron? |
After chatting to @cdupuis and @alankstewart, which think the problem is here: |
@jessitron can you confirm this is working for you now please? |
it is! |
Currently to inject a file into a project using an editor, the contents come from a velocity template.
I've been adding ".vm" to filenames and using this as a way to copy files in. However, when the script.vm file is executable, the resulting file in the project is still not.
A "copy file from rug archive to project" (without that file being in the generated project) would be nice.
The text was updated successfully, but these errors were encountered: