Release custom ninja for v4.8.8

This custom ninja contains new export option --replaceOid which can replace OID with new UUID formatted OID while exporting all objects. You can use this option to migrate to new UUID formatted OID.

How to use

Create a mapping file:

your-current-oid1,11111111-1111-1111-1111-111111111111
your-current-oid2,22222222-2222-2222-2222-222222222222
...

Note: If the new OID has already been used in the repository, ninja will out error. You must set unused OID for new OID.

Run export command with replaceOid option:

java -jar ninja-4.8.8.p1.jar -m ./config export -o export.xml --replaceOid ./mapping.csv -r

Before import the exported file, you need to delete old OID objects manually. You can use delete command of ninja with -f option to delete all old objects.

First, create filter file contains old OID(s):

<inOid>
    <value>your-current-oid1</value>
    <value>your-current-oid2</value>
    ...
</inOid>

Then, run delete command:

java -jar ninja-4.8.8.p1.jar -m ./config delete -f @delete-filter.txt -r

Finally, you can import exported file. Use -O option to override current objects in the repository.

java -jar ninja-4.8.8.p1.jar -m ./config import -i export.xml -O -r

Release custom ninja for v4.8.5

This custom ninja contains new export option --replaceOid which can replace OID with new UUID formatted OID while exporting all objects. You can use this option to migrate to new UUID formatted OID.

How to use

Create a mapping file:

your-current-oid1,11111111-1111-1111-1111-111111111111
your-current-oid2,22222222-2222-2222-2222-222222222222
...

Note: If the new OID has already been used in the repository, ninja will out error. You must set unused OID for new OID.

Run export command with replaceOid option:

java -jar ninja-4.8.5.p1.jar -m ./config export -o export.xml --replaceOid ./mapping.csv -r

Before import the exported file, you need to delete old OID objects manually. You can use delete command of ninja with -f option to delete all old objects.

First, create filter file contains old OID(s):

<inOid>
    <value>your-current-oid1</value>
    <value>your-current-oid2</value>
    ...
</inOid>

Then, run delete command:

java -jar ninja-4.8.5.p1.jar -m ./config delete -f @delete-filter.txt -r

Finally, you can import exported file. Use -O option to override current objects in the repository.

java -jar ninja-4.8.5.p1.jar -m ./config import -i export.xml -O -r

Release custom ninja for v4.8.3

This custom ninja contains new export option --replaceOid which can replace OID with new UUID formatted OID while exporting all objects. You can use this option to migrate to new UUID formatted OID.

How to use

Create a mapping file:

your-current-oid1,11111111-1111-1111-1111-111111111111
your-current-oid2,22222222-2222-2222-2222-222222222222
...

Note: If the new OID has already been used in the repository, ninja will out error. You must set unused OID for new OID.

Run export command with replaceOid option:

java -jar ninja-4.8.3.p1.jar -m ./config export -o export.xml --replaceOid ./mapping.csv -r

Before import the exported file, you need to delete old OID objects manually. You can use delete command of ninja with -f option to delete all old objects.

First, create filter file contains old OID(s):

<inOid>
    <value>your-current-oid1</value>
    <value>your-current-oid2</value>
    ...
</inOid>

Then, run delete command:

java -jar ninja-4.8.3.p1.jar -m ./config delete -f @delete-filter.txt -r

Finally, you can import exported file. Use -O option to override current objects in the repository.

java -jar ninja-4.8.3.p1.jar -m ./config import -i export.xml -O -r

Release custom ninja for v4.4.8

This custom ninja contains new export option --replaceOid which can replace OID with new UUID formatted OID while exporting all objects. You can use this option to migrate to new UUID formatted OID.

How to use

Create a mapping file:

your-current-oid1,11111111-1111-1111-1111-111111111111
your-current-oid2,22222222-2222-2222-2222-222222222222
...

Note: If the new OID has already been used in the repository, ninja will out error. You must set unused OID for new OID.

Run export command with replaceOid option:

java -jar ninja-4.4.8.p1.jar -m ./config export -o export.xml --replaceOid ./mapping.csv -r

Before import the exported file, you need to delete old OID objects manually. You can use delete command of ninja with -f option to delete all old objects.

First, create filter file contains old OID(s):

<inOid>
    <value>your-current-oid1</value>
    <value>your-current-oid2</value>
    ...
</inOid>

Then, run delete command:

java -jar ninja-4.4.8.p1.jar -m ./config delete -f @delete-filter.txt -r

Finally, you can import exported file. Use -O option to override current objects in the repository.

java -jar ninja-4.4.8.p1.jar -m ./config import -i export.xml -O -r

Release custom ninja for v4.0.4

This custom ninja contains new export option --replaceOid which can replace OID with new UUID formatted OID while exporting all objects. You can use this option to migrate to new UUID formatted OID.

How to use

Create a mapping file:

your-current-oid1,11111111-1111-1111-1111-111111111111
your-current-oid2,22222222-2222-2222-2222-222222222222
...

Note: If the new OID has already been used in the repository, ninja will out error. You must set unused OID for new OID.

Run export command with replaceOid option:

java -jar ninja.jar -m ./config export -O export.xml --replaceOid ./mapping.csv -r

Before import the exported file, you need to delete old OID objects manually. You can use delete command of ninja with -f option to delete all old objects.

First, create filter file contains old OID(s):

<inOid>
    <value>your-current-oid1</value>
    <value>your-current-oid2</value>
    ...
</inOid>

Then, run delete command:

java -jar ninja.jar -m ./config delete -f @delete-filter.txt -r

Finally, you can import exported file. Use -O option to override current objects in the repository.

java -jar ninja.jar -m ./config import -i export.xml -O -r