According to the established ModuleAnatomy guidelines in the ModuleHandbook, we should be using the following strategy for naming our artifacts:<br><a href="http://seamframework.org/Seam3/ModuleAnatomy#H-Subprojects">http://seamframework.org/Seam3/ModuleAnatomy#H-Subprojects</a><br>
<br><div style="margin-left: 40px;"><b>IMPL</b> (has compile dependency on API):<br><br>org.jboss.seam.<u>[module]</u><br><b>seam-<u>[module]</u></b><br><br><b>API</b>:<br><br>
org.jboss.seam.<u>[module]</u><br><b>seam-<u>[module]</u>-api</b><br clear="all"></div>
<br>But I see some modules that aren&#39;t following this. (Not going to call anyone out.) I think it&#39;s a good idea that for the upcoming beta, we all try to standardize our artifacts on this strategy to prevent confusion. I&#39;d say the folder structure can vary for now (should eventually be standardized if we can manage it,) but the artifact IDs are very important to have together.<br>
<br>The key here is to make sure your impl is just the name of the seam-module. That&#39;s what people will be consuming.<br><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>
&quot;Keep it Simple&quot;<br>