I am working on a project where a number of different groups are writing Mule
applications that are being managed by Maven. So we have created a large
parent POM with all of the Mule dependencies that each project POM is
supposed to inherit from. So far so good.
I am writing a new Maven plugin that automates part of the deployment to
production process. Each Mule project is supposed to use this plugin, so I
have put it as a dependency in the large parent POM. This also works, and
the projects can use the plugin.
The problem I have run into is that now that I have put the plugin
dependency in the parent POM, I can not longer build my plugin. The plugin
POM also refers to the parent POM, and I end up with a cyclic reference:
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='com.travelport.esb.esb-p.maven-plugins:maven-store-plugin'}'
and
'Vertex{label='com.travelport.esb.esb-p.maven-plugins:maven-store-plugin'}'
introduces to cycle in the graph
com.travelport.esb.esb-p.maven-plugins:maven-store-plugin -->
com.travelport.esb.esb-p.maven-plugins:maven-store-plugin
I have checked the documentation and online posts, and cannot find a way to
remove the plugin dependency in my plugin POM. The docs seem to imply that
this can be done, but I cannot see how.
Does anyone know of a way to do this, or do I just need to remove the plugin
dependency from the parent POM, and have each project add it to their own?
Thanks
Chris Pabst
--
View this message in context:
http://www.nabble.com/Cyclic-reference-error-when-building-my-plugin-tp25298551p25298551.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
