search

jazz-community / dng-type-system-management

Commandline tool to support managing Doors Next Type Systems.
4 stars 2 forks source link

deliverTypeSystemByDescription fails on 6.0.6.1 #2

Closed glyncostello closed 5 years ago

glyncostello commented 5 years ago

Annotation 2019-09-09 171234

See attached error message. Tool reports success but with an error. However the type system change is not propagated.

The two streams are in different Project Areas but the streams have the correct source/target tags in the descriptions (the tool finds the correct streams).

Some more info: I created a PA and a stream in a component. Called this "Template". Populated it was a type system for the component (Artifacts types, attributes etc.). Then I created a new test prohect with a component and gave it the same type system (import component properties). I then made a change in the "Template" PA (created an artifact type called "lessons learned". But running the cmd-line tool does not propagate the change.

I tried running the manual process of making a CSV file with source and target. This gave a slightly different error:

Annotation 2019-09-09 174510

glyncostello commented 5 years ago

Does the tool 'require' that each type system item has a defined RDF URI?

glyncostello commented 5 years ago

Ok, I went through and assigned every element in my source type system with a URI. I created a new component in a new PA and tried to run the tool again, but the same problem. Reports a success but no change to the attributes.

glyncostello commented 5 years ago

Ok, not sure what the difference between "import" and "Deliver" is, but "import" seems to be working as I expect.

rsjazz commented 5 years ago

No, there is no need for the URI with respect to the tool. Import imports a type system from one stream for one component to one stream in another component. Deliver, delivers the type system changes from one stream in one component to another stream in the same component.

rsjazz commented 5 years ago

Annotation 2019-09-09 171234

See attached error message. Tool reports success but with an error. However the type system change is not propagated.

The two streams are in different Project Areas but the streams have the correct source/target tags in the descriptions (the tool finds the correct streams).

Some more info: I created a PA and a stream in a component. Called this "Template". Populated it was a type system for the component (Artifacts types, attributes etc.). Then I created a new test prohect with a component and gave it the same type system (import component properties). I then made a change in the "Template" PA (created an artifact type called "lessons learned". But running the cmd-line tool does not propagate the change.

I tried running the manual process of making a CSV file with source and target. This gave a slightly different error:

Annotation 2019-09-09 174510

You can not deliver the type system change across multiple components (and thus not across project areas).

Maybe you try to figure out how import and delivery of type systems work manually, before trying to use automation?