Hello aavramov
I tried to recreate the scenarios you mentioned, although I'm still not quite sure I understand you correctly.
In the first scenario, I have 2 PMVs of the project deployed and want to override PMV version 1
while the same maven version is present in the project (1.0.0-SNAPSHOT
):
Simply deploying a project with the same maven version (1.0.0-SNAPSHOT
) present in the pom.xml
works for me. However, if i try to use a deploy.options.yaml
file and add the property target: version: 1.0.0-SNAPSHOT
the deployment actually fails for me. We will look into this, it might be a bug.
In the second scenario, I have the same 2 PMVs of the project deployed. This time, I want to override PMV version 2
. I want to do this without having to mention its specific maven version (1.0.1-SNAPSHOT
) but simply replace it because it is the currently RELEASED
PMV version. Also, the maven version of the project to be deployed has been updated in the pom.xml
to 1.0.2-SNAPSHOT
. I was able to achieve this with a deploy.options.yaml
that looks as follows:
target:
version: RELEASED # [AUTO], RELEASED, (version values, e.g. 2.5 or (2.0,3.0])
state: ACTIVE_AND_RELEASED # [ACTIVE_AND_RELEASED], ACTIVE, INACTIVE
fileFormat: AUTO # [AUTO], PACKED, EXPANDED
This looks exactly the same as the one you already mentioned in your first post and works fine for me:
Here you can find some more info about how the deployTargetVersion property works.
Maybe you changed the groupId
or artifactId
of the project at some point? In all cases the library identifier of the deployed PMVs and the project to be deployed has to be equal.
Did this help to answer your questions?