I guess. Keeping in mind that eventually extensions will (possibly) be
loaded by assembled module name, so they may have to change again at
On 04/29/2013 09:16 AM, Tomaž Cerar wrote:
probably same should also apply to module names.
so we would have org.wildfly.subsystem.<name>
On Mon, Apr 29, 2013 at 4:09 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com
probably having org.wildfly.extension.<>
that would too much :)
On Mon, Apr 29, 2013 at 4:07 PM, David M. Lloyd
<david.lloyd(a)redhat.com <mailto:email@example.com>> wrote:
because there will be wildfly stuff which isn't subsystems and which
might have names that conflict. I'd even suggest
"org.wildfly.as.subsystem..." but that might be too much.
On 04/29/2013 08:58 AM, Tomaž Cerar wrote:
> What should be package name for new stuff being added to WildFly?
> org.wildfly.as <http://org.wildfly.as>
> or something else?
> I would go for org.wildfly.<subsystem-name>
> this mostly applies to new subsystems and as we agreed we
> packages for existing code until it break compatibility.
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org <mailto:firstname.lastname@example.org>
wildfly-dev mailing list