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?
or something else?
I would go for org.wildfly.<subsystem-name>
this mostly applies to new subsystems and as we agreed we won't rename
packages for existing code until it break compatibility.
wildfly-dev mailing list