Skip to content
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

Unable to use catalog file after update to always force remote schemas #71

Closed
jordanpadams opened this issue Aug 16, 2019 · 0 comments · Fixed by #73
Closed

Unable to use catalog file after update to always force remote schemas #71

jordanpadams opened this issue Aug 16, 2019 · 0 comments · Fixed by #73
Labels
bug Something isn't working

Comments

@jordanpadams
Copy link
Member

C:\aaa\pds4\schema\validation>validate -V
 
gov.nasa.pds:validate
Version 1.15.1
Release Date: 2019-08-15 22:45:07
Core Schema: PDS4_PDS_1C00.xsd
Core Schematron: PDS4_PDS_1C00.sch
 
Copyright 2019, by the California Institute of Technology ("Caltech").
All rights reserved.
 
C:\aaa\pds4\schema\validation>validate -D -v2 -C catalog_v01.xml -R pds4.folder -t R:\staff-folders\pds\MER_Conversion\PDS4_Staging\MI\EDR\MER2 -r mer2_mi_edr_noc.txt
Cannot specify user schemas, schematrons, and/or catalog files with the 'force' flag option
@jordanpadams jordanpadams added the bug Something isn't working label Aug 16, 2019
jordanpadams added a commit that referenced this issue Aug 17, 2019
* Update parameters handling to disable "force" when catalog is specified
* Throw an error whenever CLI or config doesn't pick up any targets
jordanpadams added a commit that referenced this issue Aug 19, 2019
jordanpadams added a commit that referenced this issue Aug 19, 2019
Issue #70 #71 #72: Update launcher and pom to better handle catalog files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant