james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: avalon-spring-library (Was: [jira] Commented: (JAMES-842) Inconsistencies in spring integration)
Date Thu, 03 Jul 2008 08:59:16 GMT
Bernd Fondermann ha scritto:
> On Wed, Jul 2, 2008 at 10:57 AM, Stefano Bagnara <apache@bago.org> wrote:
>> Bernd Fondermann (JIRA) ha scritto:
>>>    [
>>> https://issues.apache.org/jira/browse/JAMES-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609623#action_12609623
>>> ]
>>> Bernd Fondermann commented on JAMES-842:
>>> ----------------------------------------
>>> Great work, Stefano! Thanks for taking care (also for 841 & 840).
>> Thank you :-)
>> Should we move the "non-james-specific" spring-avalon bridge to an
>> "avalon-spring-library" and just keep the FileSystemBridge+configurations in
>> the spring-deployment module?
> I see the motivation for this and think its very worthwhile from an
> architectural POV.

I just realized that I didn't explain well what I meant.

I was proposing only to create a james server submodule (like the 
core-library module) to host the non-james-specific code. This way the 
code would be part of the main james tree (we would have 1 more module, 
of course) but it would be cleaner what is the bridge and would be 
easier to allow people to just get the bridge and build it (with m2 is 
already possible to build a module without the whole project checked out).

> And I'd support it, if I'd have the time for it. But I haven't. :-/
> Maybe people from springframework.org want to adopt it and develop it
> independent from James.

*IF* people will have interests in that code or we find that we need to 
release it indipendently then (and only then) we could move it outside 
from the james tree (as its own james product or in excalibur, or in 

And if people agree it is a positive change I would offer myself for the 
task (not a big issue, if I don't miss something).


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message