[forge-dev] forge on osgi

[Dan Allen]

On Fri, Jun 17, 2011 at 11:59, Lincoln Baxter, III
<lincolnbaxter at gmail.com>wrote:

> The reason I want to go toward JBoss Modules is because I think that we can
> get things working with absolutely 0 code changes required for plugin
> developers, and yes, also because it's a jboss project.
>
>
I have complete confidence that JBoss Modules [1] is the right way to go. It
may be young, but it has been very carefully designed by someone who has
crystal clear understanding of the problem. I'm not just saying that because
David's my respected colleague, it's backed up with proof in the form of AS
7, his blogs about modularity [2] [3] and the JBoss Modules presentation.
I've heard the JavaDoc are very good as well. [4]

If you haven't yet, I strongly recommend all of you to watch the
presentation on JBoss Modules from JUDCon [5], which was given by David by
his proxy, Jason Greene. It gives an overview of JBoss Modules, but more
importantly it explains how it relates to OSGi and Maven.

JBoss Modules truly is a good fit. Plus, Forge could really help get the
word out about the benefit of modularity in general.

-Dan

[1] https://github.com/jbossas/jboss-modules
[2] http://in.relation.to/Bloggers/ModularizedJavaWithJBossModules
[3]
http://in.relation.to/Bloggers/ModulesInJDK8AndProjectJigsawRequirementsReviewPart1
[4]
https://github.com/jbossas/jboss-modules/blob/master/src/main/java/org/jboss/modules/ConcurrentClassLoader.java
[5] http://vimeo.com/24776447

-- 
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20110617/75377bc9/attachment.html