[wildfly-dev] Module aliases and deprecation

[Sanne Grinovero]

On 4 May 2016 at 13:32, Tomaž Cerar <tomaz.cerar at gmail.com> wrote:
> I understand that, so just add that property to alias module.

Ok, I tried that but then it fails parsing the alias module.
Apparently the schema for a module-alias doesn't allow properties.

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

Our need is only short lived, so no big deal to not have such a thing.

Although I would think others might need such a mechanism too?

Let me know if it's worth opening a feature request.

Thanks,
Sanne

>
> 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.
>>
>> Thanks,
>> Sanne
>>
>>
>> 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>
>> > wrote:
>> >>
>> >> 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
>> >
>> >
>
>