Skip to content
This repository was archived by the owner on Apr 17, 2024. It is now read-only.

Commit 0b1351c

Browse files
authored
Fix broken link & correct notes
1 parent 21fac25 commit 0b1351c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,10 +25,10 @@ The below will regenerate/update the ORCID Java API stored in the `src/main/java
2525
3. Copy the necessary ORCID XSD folders into this repo's `src/main/resources/xsd/` folder. Check the POM `<schemaIncludes>` list for the XSDs we need.
2626
_Be sure not to overwrite the `.gitignore` already in the "empty" `xsd` folder, as we do NOT want to keep the XSDs in this repo!_
2727
```
28-
# Copy over common_2.1 XSDs
28+
# Copy over common XSDs
2929
cp -r [ORCID-model]/src/main/resources/common_3.0 [orcid-jaxb-api]/src/main/resources/xsd/
3030
31-
# Copy over record_2.1 XSDs
31+
# Copy over record XSDs
3232
cp -r [ORCID-model]/src/main/resources/record_3.0 [orcid-jaxb-api]/src/main/resources/xsd/
3333
```
3434
4. Build project (with profile `generate-sources-from-jaxb` enabled)
@@ -38,7 +38,7 @@ The below will regenerate/update the ORCID Java API stored in the `src/main/java
3838
# WARNING This next line overwrites Java source in ./src/main/java/
3939
mvn -U clean package -Pgenerate-sources-from-jaxb
4040
```
41-
5. Double check the source code generated. If any class names or package names need to be updated, you may need to modify our custom [`orcid-2.1.xjb`](https://github.com/DSpace/orcid-jaxb-api/blob/master/src/main/resources/binding/orcid-2.1.xjb), as this is the JAXB Binding file used in the code generation process.
41+
5. Double check the source code generated. If any class names or package names need to be updated, you may need to modify our custom [`orcid-3.0.xjb`](https://github.com/DSpace/orcid-jaxb-api/blob/master/src/main/resources/binding/orcid-3.0.xjb), as this is the JAXB Binding file used in the code generation process.
4242
1. Keep an eye out especially for any source code generated under an `ns` package path, as this means a specific XSD was not assigned a package name.
4343
6. If everything looks good, create a PR, noting which version of the ORCID XSDs you used to update the Java source code (e.g. either a specific release number or `master` of a given date)
4444

0 commit comments

Comments
 (0)