You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently evaluating the pom-explorer, if we could manage our multi-repository, multi-module project with it. So far I'm very pleased.
Currently I'm stuck with changing dependency versions of a managed dependency, where the version is set as property.
Imagine the following dependency declaration:
(The junit dependency is just an example to get the point. in the case of our project, this would be an internal dependency, where the dependency management POM is imported within a parent project.)
I would expect the current value of the dependency version to be ${junit.version}, which would then be processed by the FollowVariableProcessor. Please find attached an IntegrationTest and the according POM. (Those have to be contained within the same package, so that the test finds the POM.)
The actual value seems to be null, as the managed dependencies are not evaluated by the ProjectChange.
So my question is: is this kind of Dependency Change supported by pom-explorer so far?
Hi,
I'm currently evaluating the pom-explorer, if we could manage our multi-repository, multi-module project with it. So far I'm very pleased.
Currently I'm stuck with changing dependency versions of a managed dependency, where the version is set as property.
Imagine the following dependency declaration:
(The junit dependency is just an example to get the point. in the case of our project, this would be an internal dependency, where the dependency management POM is imported within a parent project.)
Now I'd like to change the version of the dependency using the a
ProjectChange
:I would expect the current value of the dependency version to be
${junit.version}
, which would then be processed by theFollowVariableProcessor
. Please find attached an IntegrationTest and the according POM. (Those have to be contained within the same package, so that the test finds the POM.)The actual value seems to be
null
, as the managed dependencies are not evaluated by the ProjectChange.So my question is: is this kind of Dependency Change supported by pom-explorer so far?
Thanks in advance for your support.
ProjectWithDependencyManagementIT.java.txt
project-with-dependency-management-pom.xml.txt
The text was updated successfully, but these errors were encountered: