[
https://issues.apache.org/jira/browse/JAMES-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Burrell Donkin closed JAMES-792.
---------------------------------------
Resolution: Fixed
I think that this has been resolved by the factoring out of the mailet stuff
into separate products.
For example:
http://james.apache.org/mailet/api/ has been released
http://james.apache.org/mailet/base/ is being released
More releases are expected in due course
> James artifacts in the Maven repository
> ---------------------------------------
>
> Key: JAMES-792
> URL: https://issues.apache.org/jira/browse/JAMES-792
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 3.0
> Reporter: Jukka Zitting
> Assignee: Robert Burrell Donkin
> Priority: Minor
> Fix For: 3.0
>
>
> The James artifacts should be deployed on the central Maven repository for
> easy access by external projects that want to implement custom mailets or
> embed individual James components. The NOTICE/LICENSE files should be
> included in the jar files, and at least simple POM files with correct
> dependencies should be maintained. Additionally, as mentioned by Stefano
> Bagnara on the server-dev mailing list: "[...] it is not only a matter of gpg
> signing, adding a pom and submit the package to the repository: we should
> first VOTE to release the JARs alone."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
