1:49 p.m.
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
2:08 p.m.
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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:19 p.m.
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(a)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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:32 p.m.
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(a)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(a)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(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
2:43 p.m.
On 4 May 2016 at 13:32, Tomaž Cerar <tomaz.cerar(a)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(a)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(a)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(a)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(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >
> >
2:44 p.m.
You can't add properties to alias modules IIRC.
If you want to have deprecated/unsupported/etc. for a module, then
instead of an alias, create an empty module with the old name that
imports and re-exports the desired target module. Then put the
properties on this empty module.
On 05/04/2016 07:32 AM, Tomaž Cerar wrote:
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(a)hibernate.org
<mailto:sanne@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(a)gmail.com
<mailto:tomaz.cerar@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(a)hibernate.org
<mailto:sanne@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(a)lists.jboss.org <mailto:wildfly-dev@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
--
- DML
10:36 a.m.
On 4 May 2016 at 13:44, David M. Lloyd <david.lloyd(a)redhat.com> wrote:
You can't add properties to alias modules IIRC.
If you want to have deprecated/unsupported/etc. for a module, then
instead of an alias, create an empty module with the old name that
imports and re-exports the desired target module. Then put the
properties on this empty module.
Thanks David, that was very helpful!
On 05/04/2016 07:32 AM, Tomaž Cerar wrote:
> 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(a)hibernate.org
> <mailto:sanne@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(a)gmail.com
> <mailto:tomaz.cerar@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(a)hibernate.org
<mailto:sanne@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(a)lists.jboss.org <mailto:wildfly-dev@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
>
--
- DML
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2903
days inactive
2915
days old
6 comments
3 participants
participants (3)
-
David M. Lloyd -
Sanne Grinovero -
Tomaž Cerar