Sounds ok,

probably having org.wildfly.extension.<>

that would too much :)

On Mon, Apr 29, 2013 at 4:07 PM, David M. Lloyd <david.lloyd@redhat.com> wrote:

Maybe do:

   org.wildfly.subsystem.<blah>

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:
> Hi,
>
> What should be package name for new stuff being added to WildFly?
>
> org.wildfly.<subsystem-name>
> or

> org.wildfly.as <http://org.wildfly.as>.<subsystem-name>

> 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.
>
>
>
> --
> tomaz
>
>

> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


--
- DML
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev