RATIS-2429. ratis-bom module fails to deploy due to missing distributionManagement configuration#1371
Conversation
|
|
||
| <properties> | ||
| <ratis.thirdparty.version>1.0.10</ratis.thirdparty.version> | ||
| <ratis.thirdparty.version>1.0.11</ratis.thirdparty.version> |
There was a problem hiding this comment.
Nice catch, I missed following my own comment:
Lines 185 to 186 in 1433b4c
There was a problem hiding this comment.
It was just an accidental discovery :)
| <distributionManagement> | ||
| <repository> | ||
| <id>apache.staging.https</id> | ||
| <name>Apache Release Distribution Repository</name> | ||
| <url>https://repository.apache.org/service/local/staging/deploy/maven2</url> | ||
| </repository> | ||
| <snapshotRepository> | ||
| <id>apache.snapshots.https</id> | ||
| <name>Apache Development Snapshot Repository</name> | ||
| <url>https://repository.apache.org/content/repositories/snapshots</url> | ||
| </snapshotRepository> | ||
| </distributionManagement> |
There was a problem hiding this comment.
Currently, there are no properties in the ratis-bom, so I think the current style is consistent. I think it's both OK whether to change it or not.
There was a problem hiding this comment.
My concern is that if someone builds the project with custom repo (-DdistMgmtStagingUrl=... or similar), ratis-bom might unexpectedly get deployed to Apache. Copying the properties would prevent it, custom value would be applied to ratis-bom lke all other modules.
There was a problem hiding this comment.
Make Sense! Fixed!
see https://issues.apache.org/jira/browse/RATIS-2429