-
Notifications
You must be signed in to change notification settings - Fork 18
[MSHARED-1010] Allow to set dedicated Maven home directory #4
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
Conversation
d609e64 to
73d7d70
Compare
73d7d70 to
ec18db8
Compare
|
@michael-o or @rfscholte : Can you have a look? |
| .settings/ | ||
| .svn/ | ||
| bin/ | ||
| /bin/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a bin folder is included in the test resources as this is part of the layout below maven home (https://github.com/apache/maven-verifier/pull/4/files#diff-770f62c0c49568f6bdd2aaabe732e084a54c6646756e823382668d9b888563cfR1)! The intent here is to only exclude compiled classes which will only ever end up in the to-level directory /bin (if at all)!
michael-o
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change confuses me, it seems that it contains unrelated changes. If so, move them to a separate preceeding PR.
which changes are you referring to exactly? |
I am fine with your explanations. |
|
Resolve #149 |
No description provided.