-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Dependency management setup #2876
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
Changes from 21 commits
d5a0156
1f581dd
1a261ee
14fc829
be2720b
ac7cee0
5255d2a
480dc31
cd7863f
22eb952
4dc9623
6533193
920e715
a9bf0e2
9af045b
6a2edf0
4350fd5
5b09fd7
e76cf4b
38e7897
0fc25de
9a3446b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,6 +12,7 @@ | |
| <relativePath>../pom.xml</relativePath> | ||
| </parent> | ||
|
|
||
| <groupId>com.microsoft.azure</groupId> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Isn't this defaulted from the parent POM? Is there any reason to duplicated in the individual projects?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should default the other properties like versioning and developer, etc in the parent POM as well to avoid needing them in all the individual projects.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The group Ids were introduced to improve readability. Other properties already existed.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It might help with some local views of the project but it adds more harm then good in my opinion as it enables more projects to stay in sync, in particular for the version number, the fewer places we have to edit that the better. So I still suggest that a number of common properties should be lifted into one of the parent POM's in the structure. Of course that can happen as a clean-up PR and not block this PR.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm fine to centralise versions where it makes sense. I would rather not centralise group ID for now though. I would say this should be done subsequently so that it does not hold merging. We should get this merged ASAP
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree. |
||
| <artifactId>azure-keyvault-core</artifactId> | ||
| <version>1.2.0</version> | ||
| <packaging>jar</packaging> | ||
|
|
@@ -42,7 +43,7 @@ | |
| <developers> | ||
| <developer> | ||
| <id>microsoft</id> | ||
| <name>Microsoft</name> | ||
| <name>Microsoft Corporation</name> | ||
| </developer> | ||
| </developers> | ||
|
|
||
|
|
@@ -64,7 +65,6 @@ | |
| <plugin> | ||
| <groupId>org.apache.maven.plugins</groupId> | ||
| <artifactId>maven-jar-plugin</artifactId> | ||
| <version>3.0.2</version> | ||
| <configuration> | ||
| <archive> | ||
| <manifest> | ||
|
|
@@ -74,36 +74,12 @@ | |
| </archive> | ||
| </configuration> | ||
| </plugin> | ||
|
|
||
| <plugin> | ||
| <groupId>org.codehaus.mojo</groupId> | ||
| <artifactId>build-helper-maven-plugin</artifactId> | ||
| <version>1.12</version> | ||
|
|
||
| </plugin> | ||
|
|
||
| <plugin> | ||
| <groupId>org.apache.maven.plugins</groupId> | ||
| <artifactId>maven-compiler-plugin</artifactId> | ||
| <version>3.1</version> | ||
| <configuration> | ||
| <source>1.7</source> | ||
| <target>1.7</target> | ||
| </configuration> | ||
| </plugin> | ||
|
|
||
| <plugin> | ||
| <groupId>org.apache.maven.plugins</groupId> | ||
| <artifactId>maven-javadoc-plugin</artifactId> | ||
| <version>2.8</version> | ||
| <configuration> | ||
| <excludePackageNames>com.microsoft.schemas._2003._10.serialization</excludePackageNames> | ||
| <bottom><![CDATA[<code>/** | ||
| <br />* Copyright (c) Microsoft Corporation. All rights reserved. | ||
| <br />* Licensed under the MIT License. See License.txt in the project root for | ||
| <br />* license information. | ||
| <br />*/</code>]]></bottom> | ||
| </configuration> | ||
| </plugin> | ||
| </plugins> | ||
| </build> | ||
| </project> | ||
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.
What about the client.yml? Is the plan to update the pipeline variable after this merges? We should consider adding a variable for this project file as well.
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.
updated the client.test.live.yml file to have pomFile variable.