Skip to content

Update exist-db package #1

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

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

duncdrum
Copy link

@duncdrum duncdrum commented Feb 22, 2020

!! This is a breaking change !!

I am still looking into why the library can't be used in exist v5 and up, but i strongly suspect some bugs in exist. In the meantime I would recommend publishing an updated package that is tests and runs in exist v3 and v4.

this PR includes a number of functional updates:

  • it uses the latest released xslt2 version of iso-schematron files
  • it adds integration tests and runs them on CI to see if the library is working as expected on different versions of exist, to run them locally ant test with a running instance with empty admin password, and the library installed.
  • it adds deployment of the .xar to GitHUb releases. Simple create and push a tag to GitHub. I use my own GH_Token to publish it here, this would need to be adjusted.

Some typos were fixed, the readme made prettier, and code was refactored to be more inline with exist-db community conventions.

feat(expath): add max supported version

feat(expath): breaking change bump requirement

just for testing, will likely need another 5.0.0 bump

fix(expath): set semver max
ignore(xpr): ignore and add oxygen project
ci(travis): check test-results

ci(travis): ensure proper xar is tested

ci(travis): disable v5 and up, add v3 for testing
make paths dry
adjust tests to new paths
@tgraham-antenna
Copy link
Member

@vincentml, do you have time to look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants