Skip to content
Provides support for comparing changes, committing and other Git commands directly from Oxygen XML Editor.
Branch: master
Clone or download
sorincarbunaru EXM-43465: avoid IndexOutOfBoundsException
avoid IndexOutOfBoundsException when resolving conflict while having the
Diff dialog shown and then closing Diff
Latest commit 49d9389 May 23, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build New release - 1.4.0 Feb 21, 2019
i18n
license-config Add license for jakarta-regexp dependency in licenses.xml config file. Mar 6, 2018
src EXM-43465: avoid IndexOutOfBoundsException May 23, 2019
test_lib
travis
.gitignore
.travis.yml Update .travis.yml Jan 16, 2018
CODE_OF_CONDUCT.md
CONTRIBUTING.md Create CONTRIBUTING.md Oct 12, 2018
LICENSE
README.md
addon.xml Release notes for version 1.4.0. Feb 21, 2019
assembly-images.xml
assembly.xml
log4j.properties
plugin.xml
pom.xml EXM-43478: fixed TCs. Used unsigned JAR. May 22, 2019

README.md

Git Support Plugin

This add-on contributes a built-in Git client directly in Oxygen XML Editor/Author/Developer.

Installation

This add-on is compatible with Oxygen XML Editor/Author/Developer version 18.1 or higher.

To install the add-on, follow these instructions:

  1. Go to Help->Install new add-ons to open an add-on selection dialog box.
  2. Enter or paste https://raw.githubusercontent.com/oxygenxml/Oxygen-Git-Plugin/master/build/addon.xml in the Show add-ons from field.
  3. Select the Git Support add-on and click Next.
  4. Select the I accept all terms of the end user license agreement option and click Finish.
  5. Restart the application.

Result: A Git Staging view will now be available in Oxygen XML Editor/Author/Developer. If it is not visible, go to Window->Show View and select Get Staging. This view acts as a basic Git client integrated directly into Oxygen and it provides support for committing changes to a Git repository, comparing and merging changes, and other Git commands.

Cloning a repository

Click the Clone new repository button (it has a '+' sign as the icon) and provide the following:

  • Repository URL: The URL of the remote repository to be cloned.
  • Checkout branch: A specific branch of the repository to be cloned. The default branch will be cloned if another one is not specified.
  • Destination path: The local path were the repository will be cloned.

After cloning a repository, it will automatically be set as the current working copy.

Selecting a working copy

Click the Browse button to select a working copy from your file system. The selected folder must be a Git repository.

Switching between local branches

To switch between local branches, use the Change branch action from the toolbar of the Git Staging view and select the desired branch from the presented combo box.

Working with submodules

To open and work with a Git submodule, use the Submodules action from the toolbar and select the desired submodule from the presented combo box.

Unstaged resources area

In the unstaged resources area (the one on top), you will see all the modifications that have occurred since your last commit (files that have been modified, new files, and deleted files).

  • Various actions are available in the contextual menu (Open, Open in compare editor, Stage, Discard, etc.).
  • You can stage all the files by clicking the Stage All button or you can stage some of them by selecting and clicking the Stage Selected button.
  • You can switch between the flat (table) view and the tree view by clicking on the Switch to tree/flat view button positioned to the right of the staging buttons.

Staged resources area

In the staging area, you will see all the resources that are ready to be committed. Any files from this area can be unstaged and sent back to the unstaged resources area. The staging area has actions similar to the ones from the unstaged resources area.

Comparing changes and conflict resolution

At any time, if you want to see the differences between the last commit and your current modifications, you can double-click the file that appears either in the staged or unstaged area and the Oxygen's Diff window will appear and highlight the changes.

If the file has a conflict (has been modified both by you and another), Oxygen's Three Way Diff will show a comparison between the local change, the remote change, and the original base revision.

Committing

After staging the files, on the bottom of the view you can input a commit message and commit them into your local repository. For convenience, you can also select a previously entered message.

Push/Pull

To push your local repository changes to the remote repository, use the Push button from the view's toolbar. To bring the changes from the remote repository into your local repository, use the Pull button from the same toolbar.

To push or pull, you need to access the remote, and for that you need to provide some credentials. If no credentials are found, the add-on will ask for an account and password. If you have a two-factor authentication for GitHub, you must go to your Account Settings->Personal access tokens->Generate new token and back in the Git Staging view in Oxygen, you have to use the generated token as the password when you are asked to enter your credentials.

File conflicts solving flow

After editing a file, commiting it to the local repository and trying to push it to the remote repository, if a warning appears informing you about not being up-to-date with the repository, follow these steps:

  1. Pull the data from the repository using the Pull button.
  2. In the Unstaged area, select each conflicted file and open it the compare editor either by double-clicking or by using the contextual menu action. Choose what changes you want to keep/discard and save the document.
  3. After you close the compare editor, the file will be staged automatically and moved to the Staged area.
  4. When all the conflicts are resolved and no more files are left in the Unstaged area, the changes can be committed.
  5. Enter a message and commit. You will now have a new change to Push.
  6. Push the changes to the remote repository.

Copyright and License

Copyright 2018 Syncro Soft SRL.

This project is licensed under Apache License 2.0

You can’t perform that action at this time.