As such, it may not be as stable, but it includes the latest & greatest code which is being prepared for the next major release. The branch named master is roughly equivalent to the old SVN Trunk.As such, we recommend most developers use the appropriate Bug Fix / Maintenance branch for their local development. This code tends to be more stable overall. So, the latest code in that bug-fix or maintenance release will be available on that branch. dspace-1_8_x) are Bug Fix / Maintenance branches. Next, select the "Remote Branch" you wish to develop on. ![]() For more information, see the GitHub help page on "Forking a Repo". You can then checkout your own forked repository to work from and commit local changes to (push changes to). This will create your own copy of the DSpace source code under your GitHub account (e.g. IMPORTANT NOTE: If you plan to do a larger amount of DSpace development or local changes, you may wish to first "fork" the DSpace GitHub Repository ( ) to your own GitHub account.if you have your own fork: \/DSpace.git), optionally enter in a GitHub username/password, and click on the "Next" button. (In Git terminology, "clone" just means you are downloading an exact copy of the remote code repository to your local machine.) Enter the URL for the DSpace Repository in GitHub which you wish to work with (e.g. Under the ' Team' menu, go to ' Git' -> ' Clone'.NetBeans makes the checkout and configure process easy, as it does nearly everything for you. If you need help/tips/resources on DSpace development with Git/GitHub, or just tutorials on Git in general, you may want to check out our DSpace Development with Git page. All the other Maven settings should be fine as their defaults.On Windows, it should be located at C:\Documents and Settings\username\.m2 (Windows XP) or C:\Users\username\.m2 (Windows 7). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |