Added Gradle config to README, updated dep version#3699
Conversation
| DoNotSpamPls <7570108+DoNotSpamPls@users.noreply.github.com> | ||
| JRoy <joshroy126@gmail.com> | ||
| Robert Norman <spottedleaf@spottedleaf.dev>, <Spottedleaf@users.noreply.github.com> | ||
| Callum Seabrook <callum.seabrook@prevarinite.com> |
There was a problem hiding this comment.
Well, thought I might as well as I'm more than happy to license this under MIT
| <groupId>com.destroystokyo.paper</groupId> | ||
| <artifactId>paper-api</artifactId> | ||
| <version>1.15.2-R0.1-SNAPSHOT</version> | ||
| <version>1.16.1-R0.1-SNAPSHOT</version> |
There was a problem hiding this comment.
The master branch is not 1.16.1.
There was a problem hiding this comment.
Fixed, reverted back to 1.15.2-R0.1-SNAPSHOT, my bad.
| * Artifact: | ||
| ```groovy | ||
| dependencies { | ||
| compileOnly('com.destroystokyo.paper:paper-api:1.16.1-R0.1-SNAPSHOT') |
There was a problem hiding this comment.
Same as above.
|
Yeah you're right. Time for attempt 4? |
|
You know you don't need to keep creating new PRs, right? You can push new commits to existing PR branches and it will update the PR, and the Paper team can squash these commits down to a single commit if they decide to merge your PR. |
|
please stop closing and re-opening new pull requests. it creates unnecessary spam. you can continue adding commits to this PR, and squash if needed. edit: md ninja'd me |
JRoy
left a comment
There was a problem hiding this comment.
master isn't 1.16 yet, so targeting the master branch here is wrong. Also, you aren't providing patches so don't add your name to the LICENSE.md since the readme isn't code
| ```groovy | ||
| repositories { | ||
| maven { | ||
| url('https://papermc.io/repo/repository/maven-public/') |
There was a problem hiding this comment.
| url('https://papermc.io/repo/repository/maven-public/') | |
| url 'https://papermc.io/repo/repository/maven-public/' |
There was a problem hiding this comment.
Same as below
| * Artifact: | ||
| ```groovy | ||
| dependencies { | ||
| compileOnly('com.destroystokyo.paper:paper-api:1.16.1-R0.1-SNAPSHOT') |
There was a problem hiding this comment.
| compileOnly('com.destroystokyo.paper:paper-api:1.16.1-R0.1-SNAPSHOT') | |
| compileOnly 'com.destroystokyo.paper:paper-api:1.16.1-R0.1-SNAPSHOT' |
There was a problem hiding this comment.
That actually wasn't my idea, it was suggested by @Proximyst
| DoNotSpamPls <7570108+DoNotSpamPls@users.noreply.github.com> | ||
| JRoy <joshroy126@gmail.com> | ||
| Robert Norman <spottedleaf@spottedleaf.dev>, <Spottedleaf@users.noreply.github.com> | ||
| Callum Seabrook <callum.seabrook@prevarinite.com> |
There was a problem hiding this comment.
| Callum Seabrook <callum.seabrook@prevarinite.com> |
There was a problem hiding this comment.
What's the issue with that? I thought you just had to put your name in there to license your stuff under MIT... or am I missing something.
There was a problem hiding this comment.
YOU. CANNOT. LICENSE. YOUR. CHANGES. TO. THE. README. IT'S. ONLY. PATCHES.
There was a problem hiding this comment.
Yours truly licensing 10 lines of generic important statements
There was a problem hiding this comment.
Okay, okay, I'll change it hold on. Didn't know, my apologies.
Didn't know that until I googled it a minute ago, thanks |
|
Should all be fixed now, let me know if you guys find anything else 🙂 |
|
You're still targeting master, needs to target |
|
My apologies, how do I change the branch on existing commits? or do I have to revert and re-commit |
|
You can't change the branch a PR is targeting. You have to open a new PR. |
|
Apparently I was wrong. That's neat. |
|
I just changed the base, but you'll have to fix some of the conflicts that snuck in somehow? |
|
Okay thanks, yeah the commits are all over the place since I had to fix a couple of things I screwed up in the initial commit. Any idea how to change those commits? |
|
Search for resetting, rebasing, and force-pushing |
|
bruh moment |
|
Okay, so I've gotta reset the commits back to the latest commit from Aikar, then re-commit on the ver/1.16 branch. On it. The only problem with that is if I reset softly it seems to give me many patch files that just apparently don't count as having been committed any more. |
|
Hard reset and do a new commit with your changes then, shouldn't be too hard to copy paste a bunch of text again |
|
Still seems to give me like 6 locally changed files if I hard reset to the latest commit before mine. 🤔 |
|
Just me being stupid and trying to reset back to the ver/1.16 branch |
|
Sorted. Am I gonna need a new PR to change the merge branch? |
|
No, just make sure that it looks how you want locally and force push over this branch. |
|
Can't seem to change the branch it's merging from, since my commit is now on ver/1.16 on my fork. |
Okay I believe I've got everything right this time, or as one would say, I nailed it. I've added a section to the README that shows an example of how to depend on the Paper API with Gradle, to help developers who choose Gradle over Maven. I've also updated the
<version>tag in the Maven section and set the version in my new Gradle guide to1.16.1-R0.1-SNAPSHOT(as it should be), from1.15.2-R0.1-SNAPSHOT.Again, please let me know if I screwed something up.