-
Notifications
You must be signed in to change notification settings - Fork 49
[MSITE-1033] Improve heuristics to detect inheritance for SCM site URLs #227
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
base: master
Are you sure you want to change the base?
Conversation
730b1d9 to
a254952
Compare
|
I still need to look into the failing IT: Update: Debugging revealed the following
So in fact those are siblings not nested, seems that the inheritance works a bit differently than outlined in https://maven.apache.org/ref/3-LATEST/maven-model-builder/ (compare with https://maven.apache.org/ref/3-LATEST/maven-model-builder/xref/org/apache/maven/model/inheritance/DefaultInheritanceAssembler.html#L95). I would argue the expected behaviour is wrong and submodule should not end up below module but next to it! |
| public class AbstractDeployMojoTest { | ||
|
|
||
| @Test | ||
| public void testIsSameSite() { |
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.
Should be the same for?
scm:git:ssh://abc.abc
scm:git:https://abc.abc
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.
yes, protocol does no longer matter (just host and path), just look at https://github.com/apache/maven-site-plugin/pull/227/files#diff-e967f8d1e887966730304348491381424f68a0271dfc27e23ccf278d6158efaaR37.
a254952 to
3a7f305
Compare
3a7f305 to
7251576
Compare
|
Resolve #1159 |
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MSITE-XXX] - Fixes bug in ApproximateQuantiles,where you replace
MSITE-XXXwith the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verifyto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean verify).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.