Skip to content
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

chore(build): clean up gradle deprecations #46

Merged
merged 7 commits into from
Aug 26, 2021
Merged

Conversation

keturn
Copy link
Member

@keturn keturn commented Aug 15, 2021

These are mostly straightforward replacements for new names or syntax.

One thing that has more of an impact is replacing the compile dependencies. The right answer is usually implementation.

Terasology compiles with this after MovingBlocks/Terasology#4845, and I successfully uploaded a log with it.

@keturn keturn requested a review from jdrueckert August 15, 2021 20:21
Comment on lines +8 to +9
id "eclipse"
id "idea"
Copy link
Member

Choose a reason for hiding this comment

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

I know those are just here because they were present before - but do we still need them?

Copy link
Member Author

Choose a reason for hiding this comment

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

eclipse: no idea. it does seem like it's been years since any of us have tried to support an eclipse workspace.

idea: given we don't have any idea { } customizations in this file, maybe not? haven't checked.

Comment on lines -10 to -15
// Using the parent's path here to allow the CR to be embedded deeper in a Terasology workspace
String crCorePath = parent.path + ":cr-core"
// If we're in a standalone workspace we'll end up with "::cr-core" so fix real quick
crCorePath = crCorePath.replaceAll('::', ':')
println "cr-destsol is setting its cr-core dependency using path " + crCorePath
compile project(crCorePath)
Copy link
Member

Choose a reason for hiding this comment

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

Is this just no longer necessary?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think it was trying to do path-manipulation hijinks so it could work like an included build does, before included builds were an official gradle feature.

@skaldarnar skaldarnar merged commit 69a0fdf into master Aug 26, 2021
@skaldarnar skaldarnar deleted the fix/deprecated-gradle branch August 26, 2021 20:03
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.

2 participants