12:17 p.m.
The org.jboss.metadata main module has gone away in WildFly 9. This
used to include all the jboss metadata resources but has now been broken up.
However, this breaks the Keycloak subsystem and any other module that
used to reference it as a dependency. Should we restore this module
for backward compatibility?
Stan
12:19 p.m.
BTW, I don't mean put the resources back. I just mean should we have an
aggregation module?
On 8/29/2014 1:17 PM, Stan Silvert wrote:
The org.jboss.metadata main module has gone away in WildFly 9. This
used to include all the jboss metadata resources but has now been broken up.
However, this breaks the Keycloak subsystem and any other module that
used to reference it as a dependency. Should we restore this module
for backward compatibility?
Stan
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
3:38 p.m.
No objections here.
Stuart
Stan Silvert wrote:
BTW, I don't mean put the resources back. I just mean should we
have an
aggregation module?
On 8/29/2014 1:17 PM, Stan Silvert wrote:
> The org.jboss.metadata main module has gone away in WildFly 9. This
> used to include all the jboss metadata resources but has now been broken up.
>
> However, this breaks the Keycloak subsystem and any other module that
> used to reference it as a dependency. Should we restore this module
> for backward compatibility?
>
> Stan
> _______________________________________________
> 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
12:30 p.m.
Stuart,
This is what I'm thinking for the main module. Does this look correct?
What feature pack should it live in?
<module xmlns="urn:jboss:module:1.3" name="org.jboss.metadata">
<dependencies>
<module name="org.jboss.metadata.appclient"
optional="true"
export="true"/>
<module name="org.jboss.metadata.common" optional="true"
export="true"/>
<module name="org.jboss.metadata.ear" optional="true"
export="true"/>
<module name="org.jboss.metadata.ejb" optional="true"
export="true"/>
<module name="org.jboss.metadata.web" optional="true"
export="true"/>
</dependencies>
</module>
On 8/29/2014 4:38 PM, Stuart Douglas wrote:
No objections here.
Stuart
Stan Silvert wrote:
> BTW, I don't mean put the resources back. I just mean should we have an
> aggregation module?
>
> On 8/29/2014 1:17 PM, Stan Silvert wrote:
>> The org.jboss.metadata main module has gone away in WildFly 9. This
>> used to include all the jboss metadata resources but has now been
>> broken up.
>>
>> However, this breaks the Keycloak subsystem and any other module that
>> used to reference it as a dependency. Should we restore this module
>> for backward compatibility?
>>
>> Stan
>> _______________________________________________
>> 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
3:52 p.m.
It looks ok, and should be part of the main feature pack.
Stuart
Stan Silvert wrote:
Stuart,
This is what I'm thinking for the main module. Does this look correct?
What feature pack should it live in?
<module xmlns="urn:jboss:module:1.3"
name="org.jboss.metadata">
<dependencies>
<module name="org.jboss.metadata.appclient" optional="true"
export="true"/>
<module name="org.jboss.metadata.common" optional="true"
export="true"/>
<module name="org.jboss.metadata.ear" optional="true"
export="true"/>
<module name="org.jboss.metadata.ejb" optional="true"
export="true"/>
<module name="org.jboss.metadata.web" optional="true"
export="true"/>
</dependencies>
</module>
On 8/29/2014 4:38 PM, Stuart Douglas wrote:
> No objections here.
>
> Stuart
>
> Stan Silvert wrote:
>> BTW, I don't mean put the resources back. I just mean should we have an
>> aggregation module?
>>
>> On 8/29/2014 1:17 PM, Stan Silvert wrote:
>>> The org.jboss.metadata main module has gone away in WildFly 9. This
>>> used to include all the jboss metadata resources but has now been
>>> broken up.
>>>
>>> However, this breaks the Keycloak subsystem and any other module that
>>> used to reference it as a dependency. Should we restore this module
>>> for backward compatibility?
>>>
>>> Stan
>>> _______________________________________________
>>> 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
3745
days inactive
3749
days old
4 comments
2 participants
participants (2)
-
Stan Silvert -
Stuart Douglas