Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
tviegut authored Dec 14, 2024
1 parent 359e5f1 commit 5a1ce37
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ java [<jvm-parameter-1>]...[<jvm-parameter-n>] -jar cim-compare-1.3.0.jar <basel

*Parameter Details*:

**[\<jvm-parameter-x\>] (Optional)**: A JVM (Java Virtual Machine) parameter that you may need for your execution. JVM parameters are configurations used to control the behavior of the JVM at runtime and take a form such as `-mx1096m` or `-Dfile.encoding=UTF-8` for example. These parameters can influence memory usage, garbage collection, system properties, debugging, and performance tuning. JVM parameters are passed as command-line arguments when starting a Java application and if used should appear first in the sequence of command line arguments (before `cim-compare-1.3.0.jar`). This is necessary so that **cim-compare** does not try to process them as part of its command line arguments which should always appear after `cim-compare-1.3.0.jar`.
**[\<jvm-parameter-x\>] (Optional)**: A JVM (Java Virtual Machine) parameter that may need for execution. JVM parameters are configurations used to control the behavior of the JVM at runtime and take a form such as `-mx1096m` or `-Dfile.encoding=UTF-8` for example. These parameters can influence memory usage, garbage collection, system properties, debugging, and performance tuning. JVM parameters are passed as command-line arguments when starting a Java application and if used should appear first in the sequence of command line arguments (before `cim-compare-1.3.0.jar`). This is necessary so that **cim-compare** does not try to process them as part of its command line arguments which should always appear after `cim-compare-1.3.0.jar`.

**\<baseline-model-file\>** (**Required**): An Enterprise Architect baseline .eap or .qea model file. When not specified as an absolute file path the location is assumed to be the directory **cim-compare** is being executed from.

Expand Down Expand Up @@ -162,7 +162,7 @@ java [<jvm-parameter-1>]...[<jvm-parameter-n>] -jar cim-compare-1.3.0.jar <basel

*Parameter Details*:

**[\<jvm-parameter-x\>] (Optional)**: A JVM (Java Virtual Machine) parameter that you may need for your execution. JVM parameters are configurations used to control the behavior of the JVM at runtime and take a form such as `-mx1096m` or `-Dfile.encoding=UTF-8` for example. These parameters can influence memory usage, garbage collection, system properties, debugging, and performance tuning. JVM parameters are passed as command-line arguments when starting a Java application and if used should appear first in the sequence of command line arguments (before `cim-compare-1.3.0.jar`). This is necessary so that **cim-compare** does not try to process them as part of its command line arguments which should always appear after `cim-compare-1.3.0.jar`.
**[\<jvm-parameter-x\>] (Optional)**: A JVM (Java Virtual Machine) parameter that may need for execution. JVM parameters are configurations used to control the behavior of the JVM at runtime and take a form such as `-mx1096m` or `-Dfile.encoding=UTF-8` for example. These parameters can influence memory usage, garbage collection, system properties, debugging, and performance tuning. JVM parameters are passed as command-line arguments when starting a Java application and if used should appear first in the sequence of command line arguments (before `cim-compare-1.3.0.jar`). This is necessary so that **cim-compare** does not try to process them as part of its command line arguments which should always appear after `cim-compare-1.3.0.jar`.
**\<baseline-model-xmi-file\>** (**Required**): An XMI 1.1 compliant baseline model file exported from EA. When not specified as an absolute file path the location of the file is assumed to be the directory the utility is being executed from.

**\<destination-model-xmi-file\>** (**Required**): An XMI 1.1 compliant destination model file exported from EA. When not specified as an absolute file path the location of the file is assumed to be the directory the utility is being executed from.
Expand Down Expand Up @@ -207,7 +207,7 @@ java [<jvm-parameter-1>]...[<jvm-parameter-n>] -jar cim-compare-1.3.0.jar <compa

*Parameter Details*:

**[\<jvm-parameter-x\>] (Optional)**: A JVM (Java Virtual Machine) parameter that you may need for your execution. JVM parameters are configurations used to control the behavior of the JVM at runtime and take a form such as `-mx1096m` or `-Dfile.encoding=UTF-8` for example. These parameters can influence memory usage, garbage collection, system properties, debugging, and performance tuning. JVM parameters are passed as command-line arguments when starting a Java application and if used should appear first in the sequence of command line arguments (before `cim-compare-1.3.0.jar`). This is necessary so that **cim-compare** does not try to process them as part of its command line arguments which should always appear after `cim-compare-1.3.0.jar`.
**[\<jvm-parameter-x\>] (Optional)**: A JVM (Java Virtual Machine) parameter that may need for execution. JVM parameters are configurations used to control the behavior of the JVM at runtime and take a form such as `-mx1096m` or `-Dfile.encoding=UTF-8` for example. These parameters can influence memory usage, garbage collection, system properties, debugging, and performance tuning. JVM parameters are passed as command-line arguments when starting a Java application and if used should appear first in the sequence of command line arguments (before `cim-compare-1.3.0.jar`). This is necessary so that **cim-compare** does not try to process them as part of its command line arguments which should always appear after `cim-compare-1.3.0.jar`.

**\<comparison-results-xml-file\> (Required):** The model comparison file. When not specified as an absolute file path the location of the file is assumed to be the directory the utility is being executed in.

Expand Down

0 comments on commit 5a1ce37

Please sign in to comment.