One way to solve this issue is to host the source code of the project in a subversion repository and utilize version control to manage changes. “How do I host a subversion repository?” you ask, please review these two blogs on subversion and google.code repositories Show me your .slnk and I will show you mine (1of2) and Show me your .slnk and I will show you mine (2of2) Here we will discuss two scenarios: first, the open sourced code repository belongs to you, second the repository belongs to someone else. Pretty simple right? Lets get started! Here is a screen shot of the simple little program I wrote..nothing fancy, just enough to demonstrate the point. This is what the original XML or slinkee looks like generated via SAPlink. After I modify the source code, for whatever reason, I need to download a new slinkee to the same location I have the original file. Here is what my new program looks like: This is the slinkee: The file should look like this: If this is your repository, just commit the new file to the repository and you are finished. If this is not your repository, you need to create a patch and send it to the owner. You can do this by following the following steps: To make sure your patch is useable, look at the properies of the File: The dialog should look like this: If it doesn’t, just highlight the attribute and click Remove: Now you are set to create the patch!!! Right click on the file and you will select “Create patch” from the context menu: Choose the directory and patch file name you desire and add the .patch extension to the file name. When you open the patch file in any text reader, like notepad you should see something like this: Now you have to get the patch to the owner of the repository. Go to the project on Google and select the “Issues” tab. Create a new issue if this is a new bug or the existing issue if it was reported by someone else. If this is a new issue, you can attach your patch file to the issue when you create it. If it is an existing issue you are submitting a patch for, click on the Add a Comment and make Changes text box to reveal the “Attach a file” link. Attach your patch file, change the status from new or accepted to fixed and click the submit changees button. The owner can download the patch and test the changes. If you are the owner and someone else has reported they fixed an issue and supplied the patch you can download the patch and do the following. Once again, right click on the file and choose “Apply patch” You should be presented with a large blank window with two frames and a floating window for choosing the source file to be modified. Double click on the file you desire patched. Once retrieved, the large window in the back ground should be populated with three frames, Your file, the original file, and a copy of the merged files combined. Review the changes submitted and finalize the changes by right clicking on the file name in the floating window and choosing to apply the patch. Now all you have to do is commit the changed source file in your working directory back to the supository. Update the issue to “Verified” and you are done. Congratulations…you have submitted your first patch.
As with any development project, once the software is released, many times a bug is found or an enhancement requirement is identified. With an open sourced software development project the fixing of the bug gets a little complicated. In this blog I will discuss the changes to ABAP code shared during a collaborative open source project via SAPLink.