Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Oct 12, 2020

No description provided.

projectDependencies.removeAll(collect.collect {it-".jar"})
// projectDependencies.removeAll(collect.collect {it-".jar"})
} catch (UnknownProjectException ignore) {
throw ignore
Copy link
Contributor

Choose a reason for hiding this comment

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

If we throw the exception again, without any action, why not take out the try/catch block?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that exception isn't possible there anyway. Pull it.

Copy link
Author

Choose a reason for hiding this comment

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

Because I forgot, while we were pairing.

projectDependencies.removeAll(collect.collect {it-".jar"})
// projectDependencies.removeAll(collect.collect {it-".jar"})
} catch (UnknownProjectException ignore) {
throw ignore
Copy link
Contributor

Choose a reason for hiding this comment

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

I think that exception isn't possible there anyway. Pull it.

def parentProject = project(":$geodeProject" - "-$version")
def parentProject = geodeProject
def collect = parentProject.configurations.runtimeClasspath.collect { it.name }
runtimeList.removeAll(collect)
Copy link
Contributor

Choose a reason for hiding this comment

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

I really think we don't want to be removing these dependencies. If we discovered them in the block above as direct dependencies they should be included. Because we aren't iterating over transitive dependencies we shouldn't have any to filter out.

Copy link
Author

Choose a reason for hiding this comment

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

@kohlmu-pivotal Can we get consensus on these remove statements before converting this draft to a final PR?

Copy link
Contributor

@kohlmu-pivotal kohlmu-pivotal Oct 15, 2020

Choose a reason for hiding this comment

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

I believe this to be correct for the state of the project at this stage. Until libraries are loaded as modules and ensures that there is ever only one copy of a class at a particular version, or at least not have some classes cross module boundaries, this should stay.

We can always change in the future, but for now, this is sufficient.

@ghost
Copy link
Author

ghost commented Oct 22, 2020

@pivotal-jbarrett Is that logic better?

@ghost
Copy link
Author

ghost commented Oct 23, 2020

Creating non-draft PR -> #5660

@ghost ghost closed this Oct 23, 2020
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants