[wildfly-dev] Module aliases and deprecation
tomaz.cerar at gmail.com
Wed May 4 08:32:00 EDT 2016
I understand that, so just add that property to alias module.
But I think that adding that metadata to alias will *not* result in WARN
message at boot time if anyone is using the module.
AFAIR doing ModuleLoader.loadModule(aliasModule)
will return the module to which alias is pointing to, as result we cannot
read metadata of the alias directly.
David can correct me about this.
On Wed, May 4, 2016 at 2:19 PM, Sanne Grinovero <sanne at hibernate.org> wrote:
> Hi Tomaz,
> the module is not deprecated: the module-alias is.
> In other words, I wish to deprecate the "old name" only.
> On 4 May 2016 at 13:08, Tomaž Cerar <tomaz.cerar at gmail.com> wrote:
> > add extra properties to module.xml
> > for deprecated
> > <properties>
> > <property name="jboss.api" value="deprecated"/>
> > </properties>
> > should do it.
> > On Wed, May 4, 2016 at 1:49 PM, Sanne Grinovero <sanne at hibernate.org>
> >> Hello,
> >> I'm renaming some modules intended for WildFly users. To minimize
> >> impact on existing users, I'm including module-aliases using the old
> >> name, to resolve to the new module ids.
> >> Is there a way to mark such an alias as "deprecated" to encourage
> >> people moving to the new naming scheme?
> >> Thanks,
> >> Sanne
> >> _______________________________________________
> >> wildfly-dev mailing list
> >> wildfly-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wildfly-dev