Message-ID: <979494496.5479.1414166958290.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5478_721721136.1414166958289" ------=_Part_5478_721721136.1414166958289 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In order to build/install/deploy an artifact, you must choose a = group id.=20
If the artifact comes from a public repository, the choice is easy-- use= the existing group id.=20
But if it is a jar from a commercial product or something you are buildi= ng internally, you'll have to make a decision.=20
Search repo1.maven.org/maven2 or mvnrepository for the artifact. If you = find an exact match, use that.=20
Look at the package structure within the jar. The groupId does not have = to exactly match the package. Define logical groups of artifacts-- com.ibm.= websphere is fine, you don't need com.ibm.websphere.util.proxy and com.ibm.= websphere.request (those are invented...)=20
For internal artifacts, again groupIds should be logical groups, not nec= essarily an exact match for the package structure.