Matthieu Brouillard

As the IDEs are not very friendly with jgitver, and in your case we are also talking about the tomcat integration, I would recommend to deactivate jgitver inside the IDE...

your sub project should define a parent relation ; please see https://github.com/jgitver/jgitver-samples/tree/master/multi-module. In standard maven you are also able to define: - parent:1.0 - child1:2.0 (with or without any relationship...

never thought of such use cases. I'll look at it.

@nbm after I have worked on #102, a workaround exists for your case in your sub project add an execution of flatten-maven-plugin like the following: ``` org.codehaus.mojo flatten-maven-plugin 1.0.1 jgitver-flatten-pom...

> It looks like jgitver traverses by parent-definitions, not by module definitions while changing versions. indeed, this is still a change that needs to be fixed.

It is the maven extension mechanism that works only at the main level. Did you tried with other core extensions to see if they are activated in sub-projects, my bet...

and I added some info on it to demo the problem, thanks.

Can you provide a reproducer ?

@igroeg the result looks correct. What is the problem you have? the `nonQualifierBranches` is a parameter telling jgitver not to introduce a qualifier for some branches. Here the computed version...

@igroeg that's not how it works, `nonQualifierBranches` just tell jgitver not to compute/add a qualifier from the branch name for the given branches. It does not prevent jgitver to operate...