[jboss-dev] JBoss AS Top10

[David M. Lloyd]

Makes sense, I suppose.  But if we do this, it really should tie in to both 
our notion of modules and our maven repository.  And since we really have 
no notion of the former yet, I'd say that should be the first step - 
modularizing the AS runtime, explicitly defining imports/exports etc.

Once that's done, the packaged modules could/should be put into maven as 
separate artifacts.  So instead of, say, including "trove.jar" (to use a 
random example), we'd have a module (under e.g. org.jboss.modules.6_0 or 
something; each AS minor rev would probably get its own groupId) for trove 
that includes trove.jar (via maven dep) plus the jboss-classloading.xml and 
any other relevant descriptors.  This would be the thing that we then 
include.  This way, random updates of packages from, say, maven central 
won't hork up the AS.

However, this whole issue unfortunately didn't even make the top 10 - it's 
#4 (and possibly #3) on the "other crap" list.

- DML

On 04/08/2009 04:40 AM, Andrew Lee Rubinger wrote:
> Something we discuss in EJB3 (related to the Plugin installer) is the 
> notion of a central installation/update mechanism, where each profile 
> (ie. EJB3, JPA, JMS, etc) has a set of imports/exports with proper 
> dependency chain and conflict resolution.  Carlo draws an analogy to 
> yum/aptitude package managers.
> 
> So from an AS base you could do:
> 
>>  install ejb3 rails
> 
> ...which would resolve dependencies upon metadata, jpa, rails-deployer, 
> etc, bring them in if necessary, and then install.
> 
> Currently the EJB3 Plugin overwrites whatever is there.
> 
> Big feature, useful for incremental upgrades to AS.  Worth the 
> investment...another issue. ;)
> 
> S,
> ALR
> 
> Dimitris Andreadis wrote:
>> Which should be the top JBossAS priorities going forward?
>>
>> http://www.jboss.org/community/wiki/JBossASTop10
>>
>> Feel free to propose areas and/or priority changes.
>>
>> Cheers
>> /D
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>