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.

Sign up for GitHub

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

Jump to bottom

JRubyExec should not overwrite gems on every run #53

Closed
ysb33r opened this issue Aug 30, 2014 · 0 comments
Closed

JRubyExec should not overwrite gems on every run #53

ysb33r opened this issue Aug 30, 2014 · 0 comments
Milestone
0.1.3

Comments

@ysb33r
Copy link
Contributor

ysb33r commented Aug 30, 2014

First implementation was donig this, but retrospectively that it is not good solution. My suggestion is to only do this when --refresh-dependencies is specified on the command-line.

Obviously running the clean task will achieve this too, but that is a severe solution in many cases for the user. I don't believe adding specific gradle rules is worthwhile in the case
@rtyler rtyler closed this as completed in 1e04fd1 Sep 2, 2014
rtyler pushed a commit that referenced this issue Sep 2, 2014
Merge pull request #54 from ysb33r/master
3f5fe6c 
FIxes #53
@rtyler rtyler modified the milestone: 0.1.3 Oct 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
0.1.3
Development

No branches or pull requests
2 participants
@rtyler @ysb33r