-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Add more stuff about debugging #661
Conversation
This is a good start on how to prepare for debugging, but it does not yet cover the actual debugging process. Things I would like to see are:
|
Addresses: #356 (Fill "Debugging Sponge from IDE" page) |
@liach Any updates on this? |
Unfortunately nope. I am currently in china and cannot even log into discord (it asks me to check email while i cannot log on to my email service in china) |
This is gathering dust @liach - will you be able to complete it soon? |
Unfortunately no. I cannot find big chunks of time to devote on stuff. |
@liach Is the current part complete enough to be merged - so that we have at least this instead of nothing? |
i'd get a developer to confirm the validity of this portion. |
SpongeCommon fork. You want to test it against the corresponding SpongeForge (or the ``bleeding`` branch of it). The | ||
procedure is as follows: | ||
|
||
1. Clone SpongeForge repository from GitHub: Find a clean workspace, run |
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.
I wonder if ReST will interpret this as three lists and start each one at 1.
. We shall see...
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.
I recall @Spongy builds prs automatically. Doesn't it?
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.
Hmm. appears spongy doesn't like me (no branch 661
)
that seems like a rather complicated way of doing this all, why would you have a SC branch without already having a SF or SV workspace? what I think most here do, setup SF or SV as usual, then cd into the SpongeCommon folder and create a new branch.. really I don't see the point of anything you added here this page if anything should simply have the sf/sv setup instructions that are also in the main repo readmes followed by what is already covered in the plugin debugging page https://docs.spongepowered.org/stable/en/plugin/debugging.html#running-the-configuration |
A preview for this pull request is available at https://cdn.rawgit.com/Spongy/SpongeDocs-PRs/2a7e549/. Here are some links to the pages that were modified:
Since the preview frequently changes, please link to this comment, not to the direct url to the preview. |
Closing in favor of #784 as suggested by inscrutable |
No description provided.