Hopefully not. Else we'll be back to "JBoss is not just JBoss AS"
situation.
I think leaving out the ".as" part from the package name might be a good
idea, since it's redundant given that wildfly itself represents the AS.
-Jaikiran
On Monday 29 April 2013 07:49 PM, Darran Lofthouse wrote:
Are we going to have other things that use 'org.wildfly' that
are not a
part of the application server?
Regards,
Darran Lofthouse.
On 29/04/13 15:17, Spolti wrote:
> I think that org.wildfly.as <
http://org.wildfly.as> sounds good..
>
>
> 2013/4/29 Tomaž Cerar <tomaz.cerar(a)gmail.com
<mailto:tomaz.cerar@gmail.com>>
>
> 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(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
>
> --
> Atenciosamente,
> ______________________________________
> Filippe Costa Spolti
> Bacharel em Sistemas de Informação
> Linux User n°515639 -
http://counter.li.org/
> filippespolti(a)gmail.com <mailto:filippespolti@gmail.com>
> (34)9679-2388
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev