I have project A which have module B. B is a maven plugin and compiles fine. When I however tries to compile project A, it complains at project B. Thus, failing. It is telling me that plugin.xml is not found. I googled it and most people saying that the packaging of a Maven plugin should use maven-plugin as packaging, which seems to solve the problem. However, mine is already set to that. So not sure how to resolve it.
Project A pom:
Project B pom:
Uncommenting code such as parent and executions in this pom will give the same results. Project B is located in the same directory as project A's pom.xml.
You need to take a step back and rethink your approach here. You are using maven the wrong way
First of all, your parent project shouldn't have anything to compile or build a war. A parent project is meant to have settings that child projects can inherit. parent projects shouldn;t build anything themselves
Second of all, a parent project cannot depend on a child project. That's like my dad saying that he wouldn't have sex with my mom unless I become old enough to take care of his expenses. It doesn;t work that way in real life, right? I have to be born first before I can take care of my dad, right? So, my dad cannot refuse to give birth to me until I take care of his expenses, because if he doesn't give birth to me, I won't be born. The point of that completely inappropriate analogy is Parents cannot depend on children
Third of all, you are trying to generate some scripts from your resource files. Looks like this is something that belongs in generate-resources phase not compile phase.
What you need to do is have a parent pom that is a real parent: Basically it compiles nothing on it's own: It just has the common libraries that you want to import. Your parent can also be a reactor project and have 2 submodules. First submodule can be the plugin. Second submodule can be the war project.
She's brilliant. She can see what can be and is not limited to what is. And she knows this tiny ad: