|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
28/Feb/09 03:10 PM
|
|
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."
|
|
Description
|
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."
|
Show » |
|
Improvement
Closed
Minor
James artifacts in the Maven repository
As you can see in our stage folder and in the current pom.xml dependencies we depend on "patched" versions of 3rd party (or other ASF projects) libraries:
cornerstone-socket-impl-2.1-patched.jar
cornerstone-datasources-impl-2.1-patched.jar
bcmail-jdk14-workaround-129.jar
You ask why we depend on patched cornerstone libraries? https://issues.apache.org/jira/browse/EXLBR-30
About bcmail I should check if the newest releases still have the problem I foound with the 129 (there was a missing class in bcmail: the workaround is needed to avoid dependencies on the full bouncycastle JCE).