[
https://issues.apache.org/jira/browse/MAILET-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527157#comment-13527157
]
Ioan Eugen Stan edited comment on MAILET-41 at 12/8/12 3:01 PM:
----------------------------------------------------------------
The changes have been discussed and voted on the mailing list:
http://www.mail-archive.com/[email protected]/msg40264.html
----
Further proposed changes TBD - will go on JIRA:
* change directory names to mailets-<current-name> (not strong opinion) -
abandoned
* clean-up 1: agggregate all project info, dependencies and other
stuff to parent apache-mailets and remove duplication -- A MUST DO
* move site related content under site -- A MUST DO IMHO
* aggregate JIRA tracking under the same project - going through the
project I noticed each mailet has it's own JIRA project, mailinglist,
etc. I think it's a lot of overhead and not worth it. The community is
not that big. I also think less is more. -- also a MUST DO IMHO
* move code to java 1.6 (which will be end-of-life in spring 2013) -
like all other James code
* make a release and publish site
was (Author: ieugen):
The changes have been discussed and voted on the mailing list:
http://www.mail-archive.com/[email protected]/msg40264.html
> Mailet OSGi, git TLC
> ---------------------
>
> Key: MAILET-41
> URL: https://issues.apache.org/jira/browse/MAILET-41
> Project: James Mailet
> Issue Type: Task
> Components: Core API
> Affects Versions: 2.5
> Reporter: Ioan Eugen Stan
> Fix For: 2.5
>
>
> Mailets have not received attention for a while and fallen behind. We need to
> pump new blood into the project.
> Proposed changes:
> 1. change directory structure and move all components under one directory
> with separate parent, aggregator and maybe site - easy to clone the proejct
> in git/git-svn
> 2. update artifact versions to be compatible with http://semver.org/ and OSGi
> friendly
> 3. update artifact names for better uniformity
> 4. new release to include changes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
