mvn import matches on packageName so exports more than expected

EdSp — Thu, 17 May 2018 09:04:49 GMT

Hi,

Does mvn import do pattern matching on the packageName? Or does it do an exact match query? I get xml files of components that are in a package with a similar name (but has a further extention in the name). Let me give an example...

We have 2 packages, say: "com.test.ed" and "com.test.ed.ext". In the pom file of the project I set packageName to: <packageName>com.ed.test</packageName>

When doing a mvn import of package "com.test.ed" (to get the components from this vRO package into XML files), I noticed that I also get the content of package "com.test.ed.ext"!

After renaming "com.test.ed.ext" to a non-matching name (e.g. "com.test.myext") it was correct again and the mvn import of "com.test.ed" would only give me the xml files for that package.

So... it seems that the plugin does a filename match on the packageName?!

Has anyone seen this? It is easy to reproduce.

Suggestions welcome

Many thanks,

topic mvn import *matches* on packageName so exports more than expected in vCenter Orchestrator Plug-in SDK Discussions

mvn import *matches* on packageName so exports more than expected

topic mvn import matches on packageName so exports more than expected in vCenter Orchestrator Plug-in SDK Discussions

mvn import matches on packageName so exports more than expected