Skip to content
This repository has been archived by the owner on Aug 7, 2019. It is now read-only.

Make .jamrc location more flexible #43

Closed
pieterv opened this issue Jul 18, 2012 · 5 comments
Closed

Make .jamrc location more flexible #43

pieterv opened this issue Jul 18, 2012 · 5 comments

Comments

@pieterv
Copy link
Contributor

pieterv commented Jul 18, 2012

It would be nice if the .jamrc file could be put inside your project directory or your home directory.

Maybe when making a jam call it should look into the current directory for the .jamrc file and if not found recursively look into the parent directories until the file is found or defaults used.

This would be similar to how grunt.js works for finding it's grunt config files.

@ghost
Copy link

ghost commented Jul 24, 2012

It's already there in lib/jamrc.js in exports.PATHS.

This solves this problem (maybe it should be there by default):

exports.PATHS = [
    env.home + '/.jamrc',
    process.cwd() + '/.jamrc' //or just './.jamrc'
];

Jam is not looking into parent directories now, though.

@pieterv
Copy link
Contributor Author

pieterv commented Jul 24, 2012

Doesn't look like its in lib/jamrc.js anymore, this would be helpful though.

I think recursively looking in parent directories would be ideal, but this is a good first step if it's easy enough to implement.

@shyiko
Copy link
Contributor

shyiko commented Jul 27, 2012

Voting +1. It would be great to have behavior like this by default.

@pieterv
Copy link
Contributor Author

pieterv commented Aug 13, 2012

I dont think this functionality is necessary now that Jam is using the package.json file to set project specific properties like packageDir. My experience with 0.2.x this seems to be working very well so far.

Feel free to close the issue.

@caolan
Copy link
Owner

caolan commented Aug 13, 2012

@pieter-vanderwerff glad the new system seems to be working out for you. I'll close this issue for now.

@caolan caolan closed this as completed Aug 13, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants