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

Relocate ivy cache directory #2

Open
matthughes opened this issue Nov 5, 2013 · 5 comments
Open

Relocate ivy cache directory #2

matthughes opened this issue Nov 5, 2013 · 5 comments

Comments

@matthughes
Copy link

By default SBT will put ivy resolution files in ${projectRoot}/target. This can be quite painful in mixed Maven/SBT projects as you run "mvn clean install" and blow away your Ivy cache inadvertently. With my project, resolution can take a LONG time, so I really don't want to blow that away.

Ideally this plugin would put the sbt resources in a different folder, 'sbtTarget' to prevent this collision. Or give an example of how to configure an individual project.

This post (http://stackoverflow.com/questions/17190755/why-sbt-runs-dependency-resolution-every-time-after-clean) describes how one can configure SBT to change that directory but I don't know how that fits into projects using PomReader

@jsuereth
Copy link
Member

jsuereth commented Nov 5, 2013

Great point. Probably in that instance, you'll just want the whole target directory to be different. Maven + sbt's target directories just don't get along in general.

@mpilquist
Copy link

+1 for overriding whole target directory

@metasim
Copy link
Member

metasim commented May 2, 2015

@jsuereth Should the target directory be changed in this plugin by default? I've run into problems where I've run sbt and then mvn accidentally.

@jsuereth
Copy link
Member

@metasim I don't feel I have enough data points to make a cogent guess if it should be on by default.... Gut reaction says "no" for now.

@metasim
Copy link
Member

metasim commented May 21, 2015

@jsuereth Might be something that can be addressed via the docs with existing settings. Will investigate further.

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

No branches or pull requests

4 participants