james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Commented: (MIME4J-101) Convert Mime4J into a project with multiple modules
Date Wed, 25 Feb 2009 12:34:02 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676626#action_12676626
] 

Robert Burrell Donkin commented on MIME4J-101:
----------------------------------------------

I have a plan that would allow work to begin on this before the 0.6 release is finalised.

My proposal is to create a peer directory in subversion next to tags, branchs and trunk called
'future'. svn:externals would be used to import the current trunk as a subdirectory. This
would allow work to start on the top level components as work continues on the 0.6 release.


Once 0.6 is released, the svn:externals would be removed, trunk moved to future/main and future
renamed to trunk. 

> Convert Mime4J into a project with multiple modules
> ---------------------------------------------------
>
>                 Key: MIME4J-101
>                 URL: https://issues.apache.org/jira/browse/MIME4J-101
>             Project: JAMES Mime4j
>          Issue Type: Task
>    Affects Versions: 0.6
>            Reporter: Markus Wiederkehr
>             Fix For: 0.7
>
>
> Initially there should be modules for examples, benchmarks and main source. At a later
point there could also be modules for parser, storage and DOM.

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


Mime
View raw message