New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version could be properties which defined in project gav #69
Comments
Thanks for your input, I am not really sure if I get you right. Do you mean something as the following:
child
|
You got it. I found this scene in a real project. |
But |
It seems to me that an interpolation is required here so that the version resolves to what is defined in the parent (or wherever it was defined). Is that your actual problem? |
Yes. In fact the program try to compare version and "${parent.version}" , so it is the same that the version equals |
Ok, I think now we are getting to the point 😄 |
Ok,I would like to try it. Is the logic right to solve this problem ?
|
add test cases where a project with a parent has properties as version
I think that's more or less it. The good thing though, there is already logic for this |
Got it. I will try to finish it. |
Sorry, I only pushed the regression test to my fork but not to this repo. It is now inlcuded here as well: #70 |
pom-explorer/pom-explorer-core/src/main/java/fr/lteconsulting/pomexplorer/Project.java
Line 96 in db4246c
parent -->
child1 (g - a -v)
child2 (groupId - artifactId - ${xxx.version})
xxx.version is the property in parent artifactId
The text was updated successfully, but these errors were encountered: