Skip to content
This repository has been archived by the owner on Oct 14, 2020. It is now read-only.

boost project versioning cleanup #366

Merged
merged 5 commits into from
Sep 12, 2019

Conversation

ajm01
Copy link
Member

@ajm01 ajm01 commented Sep 6, 2019

addressed items in task #339

@ajm01 ajm01 requested a review from scottkurz September 6, 2019 21:11
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't we mean to import the runtimes BOM?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missed this one, now importing the runtime bom

<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>boost.boosters</groupId>
<artifactId>ee8-bom</artifactId>
<version>0.1.3-SNAPSHOT</version>
<version>1.0-M1-SNAPSHOT</version>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You didn't cause this issue.. but MP 1.4 correlates to EE 7, not 8

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does it say about our IT coverage that we don't catch this? Is this actually not taking precedence and so is just harmless noise? Or do we not really care if we get EE 8 level features since they are back compatible with EE 7 test apps?

Those are kind of open-ended, so let me ask a simpler question: do we every use the mp14-bom in any IT? Might we at least add one IT to do that here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

switched to ee7 - and switched the mpHealth IT to use the mp14 bom

@@ -32,11 +32,21 @@

<dependencyManagement>
<dependencies>
<!--
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you comment this out as opposed to just deleting it? Had we talked about being unsure here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deleted commented out stanzas

<type>pom</type>
<scope>import</scope>
</dependency>
<!--
<dependency>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can just delete this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deleted

</dependency>
-->
<dependency>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indent

<groupId>org.eclipse.microprofile</groupId>
<artifactId>microprofile</artifactId>
<version>2.0</version>
<type>pom</type>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indent

@@ -11,7 +11,7 @@
<groupId>boost.boosters</groupId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We were going to make a new gid for the BOMs right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed boms groupids to boost.boms

@ajm01 ajm01 force-pushed the bom-versioning-cleanup-339 branch 2 times, most recently from 5cd71d5 to 3d620fe Compare September 11, 2019 14:35
@ajm01 ajm01 merged commit 65a47b6 into MicroShed:master Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants