Details
Description
In my particular case, $
{packageInPathFormat} is used in all generated files when ${package} should have been. In my XML and java files, ${packageInPathFormat}did not make sense. Maybe there are other cases where it would work. Just seems like $
{package}should either be the default, or there should be an option to specify. I attached a few generated files to illustrate the issue.
I just hit the same issue, caused by the fact that the initial project had a one-level-only package name
then package == packageInPathFormat, and the archetype creation replaces the packageInPathFormat variable before package
FYI, I just fixed my case by having the sample project in foo.bar package instead of foo: see r1073199
BTW, I'll have a look at the code to try to detect this cas and force $
{package}instead of ${packageInPathFormat] when their value is the same