I am using Maven in a project that contains several modules when we are staying, we Module is deployed in our own Mewen repository The project module is derived from an original project that defines common properties such as tool reporting, SCM space, repository, etc. to use. ./ pom.xml ./ module / pom.xml It has been discovered that there is a problem with this setup: When someone joins the project and tries to create a module, it will fail. The reason for this is that parent section, add a
& lt; Project & gt; & Lt; Group & gt; Com.example & lt; / Group & gt; & Lt; ArtifactId & gt; Parents & lt; / ArtifactId> & Lt; Version & gt; 1.0 & lt; / Version & lt; Repository & gt; & Lt; Stores & gt; & Lt; URL & gt; Repo.example.com & lt; / URL & gt; ... & lt; / Repository & gt; & Lt; / Treasures & gt; ... & lt; / Project & gt;
& lt; Project & gt; & Lt; Group & gt; Com.example & lt; / Group & gt; & Lt; ArtifactId & gt; Module & lt; / ArtifactId> & Lt; Parents & gt; & Lt; Group & gt; Com.example & lt; / Group & gt; & Lt; ArtifactId & gt; Parents & lt; / ArtifactId> & Lt; Version & gt; 1.0 & lt; / Edition & gt; & Lt; / Parent & gt; ... & lt; / Project & gt;
guardian will not be available in their local Mewen repository , and can not be obtained because
repo.example.com < Strong> only
relativePath element with the content
.. .
& lt; Parents & gt; ... & lt; Relative Path & gt; .. & lt; / Relative paths & gt; & Lt; / Parent & gt;
Comments
Post a Comment