[wildfly-dev] JBoss MSC Plans

[David Lloyd]

JBoss Modules is not the same as JBoss MSC, but your idea is a good
one.  I've opened https://issues.jboss.org/browse/MODULES-325 to track
it.

On Mon, Jan 29, 2018 at 7:31 AM, Philippe Marschall <kustos at gmx.net> wrote:
>
>
> On 04.01.2018 14:56, Richard Opalka wrote:
>> Hi everyone,
>>
>>     I would like to outline a brief JBoss MSC Plans for Year 2018.
>>
>> Goals defined below address both:
>>   * Cloud First Effort
>>     - Reduce WildFly memory footprint
>
> I would like to throw something in here, are there any plans to no
> longer reference the JAR manifest? We use quite a few JARs that have
> large manifests and because JBoss modules strongly references the
> java.util.jar.Manifest instance that actually becomes noticeable.
>
> Our JAR manifests are so large because they contain large OSGi headers.
> We don't run OSGi, the JARs are simply OSGi capable.
>
> Cheers
> Philippe
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev



-- 
- DML