james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Commented: (MIME4J-129) Split Up Core Module
Date Thu, 30 Apr 2009 19:54:30 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704764#action_12704764

Oleg Kalnichevski commented on MIME4J-129:

Robert, et al

I am not entirely sure there is anything to be gained from splitting parser and dom into separate
modules. I do not see any convincing reasons one would want to decouple dom classes. Save
20KB of disk space? Dom classes do not have any special external dependencies one might want
to get rid of. 

How about this?

mime4j-core: parser, dom, util, storage api, memory based storage impl
mime4j-file: file based storage impl
mime4j-db: jdbc based storage impl


> Split Up Core Module
> --------------------
>                 Key: MIME4J-129
>                 URL: https://issues.apache.org/jira/browse/MIME4J-129
>             Project: JAMES Mime4j
>          Issue Type: Task
>    Affects Versions: 0.7
>            Reporter: Robert Burrell Donkin
>             Fix For: 0.7
> ATM only example and benchmark code has been moved into separate modules. The core module
contains all substantial code.
> IIRC the plan was that core would be completely replaced by a number of separate modules.
This task has been created to track this work.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message