maven icon indicating copy to clipboard operation
maven copied to clipboard

MNG-3525-maven-settings - settings.xml allowing mirror definitions inside profiles

Open nitram509 opened this issue 8 years ago • 11 comments

This improves user settings to have a mirrors list switched on/off via Maven profile. See commit messages for details.

Direct issue link: https://issues.apache.org/jira/browse/MNG-3525

Any feedback is welcome.

nitram509 avatar Nov 01 '15 12:11 nitram509

Looking through the changes, definitely useful. Just a suggestion for your for your Git commit messages: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

jvanzyl avatar Nov 01 '15 14:11 jvanzyl

Thank you for this fast feedback.

nitram509 avatar Nov 01 '15 14:11 nitram509

I've just rebased the latest commits from master.

nitram509 avatar Nov 15 '15 14:11 nitram509

Is there anything I miss, that this PR can be merged? Or is there a plan/roadmap when merge could happen?

nitram509 avatar Dec 10 '15 23:12 nitram509

I suggested the link on how to make comments so you would adjust them. Nothing is easy to read with the way they currently are. For example, I'm not sure why you introduced the CommandLineSettings and didn't use the existing classes.

jvanzyl avatar Dec 11 '15 00:12 jvanzyl

If you're around tomorrow I can spare an hour if you want to work together in a hangout to try and get this merged. It's a good feature, I just have some questions and we might need a small refactor.

jvanzyl avatar Dec 11 '15 02:12 jvanzyl

Sure. Btw.my timezone is UTC+1 ;)

nitram509 avatar Dec 11 '15 08:12 nitram509

@jvanzyl Without looking deeply into this, it looks like a massive commit with a model change. This should be in 3.4 or later.

@nitram509 You have refomatted some code to Maven guidelines which I appreciate but they are unrelated to this PR. Please create a separete PR for these kinds of improvements. PS: UTC+1 isn't a timezone, it's an offset. Europe/Berlin is ;-)

michael-o avatar Dec 11 '15 09:12 michael-o

@michael-o the model change will be all right provided the reader ignores fields it doesn't understand. So newer versions that understand the change can deal with it accordingly. Older versions will just ignore them. If this is not the case then I agree. I have no intention of breaking users with the change but not very concerned which version it goes into. We don't really follow anything reasonable yet insofar as how we change our versions with respect to features or apis or both together. I really only care that it doesn't surprise users.

jvanzyl avatar Dec 11 '15 15:12 jvanzyl

@nitram509 while i'm in California meeting up is a bit tough, but I will be back in Toronto tomorrow and then I'll email you and we'll figure out a time.

jvanzyl avatar Dec 11 '15 15:12 jvanzyl

@jvanzyl For me it's to late now, let's talk tomorrow.

nitram509 avatar Dec 12 '15 22:12 nitram509