<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><tt>On Friday 24 May 2013 06:50 PM,
Thomas Diesler wrote:</tt><tt><br>
</tt></div>
<blockquote
cite="mid:12FB7BE7-1F5F-4BC1-AA6B-2E1BB8DDC5FE@jboss.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div><tt><br>
</tt></div>
<div><tt>A module alias should be unique, if a deployment defines
an alias of an already existing module it should fail. System
modules cannot have dependencies on deployment modules.</tt><tt><br>
</tt></div>
<div><tt><br>
</tt></div>
<tt><br>
</tt></blockquote>
<tt>That looks like a (unnecessary) complexity. Assume, there's a
foo.bar static module and then some deployment configures a module
named foo.bar within it's jboss-deployment-structure.xml. I
haven't looked at JBoss Modules implementation and how it
interacts with the module loaders, but how would it know that
foo.bar "already exists" as a static module?</tt><tt><br>
</tt><tt><br>
</tt><tt>By the way, why do we need this? I read up the JIRA and the
comments in the PR but I am not sure what the real requirement is.</tt><tt><br>
</tt><tt><br>
</tt><tt>-Jaikiran</tt><tt><br>
</tt>
</body>
</html>