[jira] [Commented] (JAMES-3189) Document Javadoc for all 144 Guice Modules

[ https://issues.apache.org/jira/browse/JAMES-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110906#comment-17110906 ] David Leangen commented on JAMES-3189: -- I am not able to assign this issue to myself

[jira] [Created] (JAMES-3189) Document Javadoc for all 144 Guice Modules

David Leangen created JAMES-3189: Summary: Document Javadoc for all 144 Guice Modules Key: JAMES-3189 URL: https://issues.apache.org/jira/browse/JAMES-3189 Project: James Server Issue Type: T

[jira] [Commented] (JAMES-3188) [jsieve] Merge into a single module

[ https://issues.apache.org/jira/browse/JAMES-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110826#comment-17110826 ] Benoit Tellier commented on JAMES-3188: --- See JSIEVE-114 > [jsieve] Merge into a si

[jira] [Commented] (JAMES-3168) Integration tests with echo method

[ https://issues.apache.org/jira/browse/JAMES-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110814#comment-17110814 ] Benoit Tellier commented on JAMES-3168: --- https://github.com/linagora/james-project/

[james-project] branch master updated: JAMES-3168: distributed echomethod integration test

This is an automated email from the ASF dual-hosted git repository. btellier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git The following commit(s) were added to refs/heads/master by this push: new 80cdb69 JAMES-3168: distributed echome

[jira] [Created] (JSIEVE-114) Merge into a single module

David Leangen created JSIEVE-114: Summary: Merge into a single module Key: JSIEVE-114 URL: https://issues.apache.org/jira/browse/JSIEVE-114 Project: James jSieve Issue Type: Improvement

[jira] [Resolved] (JAMES-3188) [jsieve] Merge into a single module

[ https://issues.apache.org/jira/browse/JAMES-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen resolved JAMES-3188. -- Resolution: Invalid Wrong issue tracking system > [jsieve] Merge into a single module > --

[jira] [Commented] (JAMES-3188) [jsieve] Merge into a single module

[ https://issues.apache.org/jira/browse/JAMES-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110809#comment-17110809 ] David Leangen commented on JAMES-3188: -- No problem! I didn't know there was a separa

[jira] [Closed] (JAMES-3188) [jsieve] Merge into a single module

[ https://issues.apache.org/jira/browse/JAMES-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen closed JAMES-3188. > [jsieve] Merge into a single module > --- > > Key: JA

[jira] [Commented] (JAMES-3188) [jsieve] Merge into a single module

[ https://issues.apache.org/jira/browse/JAMES-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110807#comment-17110807 ] Benoit Tellier commented on JAMES-3188: --- Sorry to ask you this, but the relevance o

Re: [jsieve] API vs implementation

On 19/05/2020 09:14, David Leangen wrote: > Hi, > > I am having a bit of trouble distinguishing the jsieve API from its > implementation. It is my intention to document this project, but I find it > more difficult to understand than it ought to be because of this problem. > > If the library is

Re: [jseive] Folding into a single module

>> If you agree with this approach, then I will create a Jira Issue this time >> and work against that. :-) > > :+1: Created https://issues.apache.org/jira/browse/JAMES-3188 - To unsubscribe, e-mail: server-dev-unsubscr...@jam

[jira] [Commented] (JAMES-3188) [jsieve] Merge into a single module

[ https://issues.apache.org/jira/browse/JAMES-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110792#comment-17110792 ] David Leangen commented on JAMES-3188: -- Note: there is no "jsieve" module. Should so

[jira] [Created] (JAMES-3188) [jsieve] Merge into a single module

David Leangen created JAMES-3188: Summary: [jsieve] Merge into a single module Key: JAMES-3188 URL: https://issues.apache.org/jira/browse/JAMES-3188 Project: James Server Issue Type: Improvem

Re: [jseive] Folding into a single module

On 19/05/2020 08:59, David Leangen wrote: [...] > Ok, cool. Let’s get back to this after we resolve the current issues. > > If you agree with this approach, then I will create a Jira Issue this time > and work against that. :-) :+1: Thanks for taking care about this. Best regards, Benoit > C

[jira] [Commented] (JAMES-3187) Update the User Manual

[ https://issues.apache.org/jira/browse/JAMES-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110777#comment-17110777 ] Benoit Tellier commented on JAMES-3187: --- In an effort to simplify the *try james de

[jsieve] API vs implementation

Hi, I am having a bit of trouble distinguishing the jsieve API from its implementation. It is my intention to document this project, but I find it more difficult to understand than it ought to be because of this problem. If the library is small enough and the integration simple enough, then per

[james-project] branch master updated: [JAMES-3187] Updates to the "Try James" Section of the User Manual

This is an automated email from the ASF dual-hosted git repository. btellier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git The following commit(s) were added to refs/heads/master by this push: new bac9b13 [JAMES-3187] Updates to the "T

[jira] [Commented] (JAMES-2997) hasAttachment SHOULD be metadata read level

[ https://issues.apache.org/jira/browse/JAMES-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110773#comment-17110773 ] Benoit Tellier commented on JAMES-2997: --- https://github.com/linagora/james-project/

Re: [jseive] Folding into a single module

Hi Benoit, > I would be carefull: the maven module "util" has a depedency to > javax.mail, causing some potential dependecy conflicts for users. I think it’s ok to have optional dependencies. Only those who want to use the functionality that requires javax.mail would have to provide it at runt

[jira] [Commented] (JAMES-1541) James won't start when Tarpit is active - TarpitHandler not found

[ https://issues.apache.org/jira/browse/JAMES-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110762#comment-17110762 ] Benoit Tellier commented on JAMES-1541: --- See https://github.com/apache/james-projec

[jira] [Commented] (JAMES-1541) James won't start when Tarpit is active - TarpitHandler not found

[ https://issues.apache.org/jira/browse/JAMES-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110760#comment-17110760 ] Benoit Tellier commented on JAMES-1541: --- Hello [~chris1k] I was not aware of this

[james-project] branch master updated: JAMES-2997 MIMEMessageConverter should override blob contentType with attachment contentType

This is an automated email from the ASF dual-hosted git repository. btellier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git The following commit(s) were added to refs/heads/master by this push: new 0156583 JAMES-2997 MIMEMessageConverte

[jira] [Closed] (JAMES-3185) Update gitignore to ignore jenv and Eclipse configuration files

[ https://issues.apache.org/jira/browse/JAMES-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen closed JAMES-3185. > Update gitignore to ignore jenv and Eclipse configuration files > ---

[jira] [Resolved] (JAMES-3185) Update gitignore to ignore jenv and Eclipse configuration files

[ https://issues.apache.org/jira/browse/JAMES-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Leangen resolved JAMES-3185. -- Resolution: Won't Fix We should not enfoirce as a project which tool people are using to contri

[jira] [Created] (JAMES-3187) Update the User Manual

David Leangen created JAMES-3187: Summary: Update the User Manual Key: JAMES-3187 URL: https://issues.apache.org/jira/browse/JAMES-3187 Project: James Server Issue Type: Improvement

[jira] [Created] (JAMES-3186) Add a Basic auth mechanism based on administratorId for webadmin

Benoit Tellier created JAMES-3186: - Summary: Add a Basic auth mechanism based on administratorId for webadmin Key: JAMES-3186 URL: https://issues.apache.org/jira/browse/JAMES-3186 Project: James Serve

[jira] [Commented] (JAMES-3185) Update gitignore to ignore jenv and Eclipse configuration files

[ https://issues.apache.org/jira/browse/JAMES-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110169#comment-17110169 ] David Leangen commented on JAMES-3185: -- Submitted [PR #191|[https://github.com/apach

[jira] [Created] (JAMES-3185) Update gitignore to ignore jenv and Eclipse configuration files

David Leangen created JAMES-3185: Summary: Update gitignore to ignore jenv and Eclipse configuration files Key: JAMES-3185 URL: https://issues.apache.org/jira/browse/JAMES-3185 Project: James Server

Re: Guice vs. Spring

On 18/05/2020 16:23, David Leangen wrote: >> But maybe all of this should be discussed in a separate thread as a >> "Guice roadmap"… > > These all seem like great ideas to me. > > I just had a wild thought based on your ideas. Just like there is a concept > out there of “headless CMS”, maybe

Re: Questions about Guice design

On 18/05/2020 16:16, David Leangen wrote: > > Thank you for the explanations. I now understand much better the migration > from Spring to Guice, and the intent behind Guice. > > Instead of directly answering the questions you posed, I will make a proposal > that I think goes in the same dire

Re: Guice vs. Spring

> But maybe all of this should be discussed in a separate thread as a > "Guice roadmap"… Good idea to discuss this in a separate thread. In the meantime, I will continue down the path I mentioned here: https://www.mail-archive.com/server-dev@james.apache.org/msg65771.html

Re: Guice vs. Spring

> But maybe all of this should be discussed in a separate thread as a > "Guice roadmap"… These all seem like great ideas to me. I just had a wild thought based on your ideas. Just like there is a concept out there of “headless CMS”, maybe we could have some concept of a “headless enterprise ema

Re: Questions about Guice design

Thank you for the explanations. I now understand much better the migration from Spring to Guice, and the intent behind Guice. Instead of directly answering the questions you posed, I will make a proposal that I think goes in the same direction as your comments. > This documentation effort wou

Re: Guice vs. Spring

On 18/05/2020 14:35, Matthieu Baechler wrote: > On Sun, 2020-05-17 at 14:32 +0900, David Leangen wrote: >> Hello, [...] >> I think Guice is easy enough that it would be worthwhile for me to >> learn it, even if it’s just for James. >> >> On that note, what are the plans going forward regardin

Re: Guice vs. Spring

Thank you very much for the reply. >> Should I even bother learnings about Spring? > > No. Ok, in that case I think it is clear that I should just ignore Spring while developing the documentation. Honestly, I think we should just avoid all mention of it all together. All it will do is requ

Re: Questions about Guice design

Hi David! A pretty long and interesting email! On 17/05/2020 13:01, David Leangen wrote: > > Hi! > > As I just mentioned in a different email: > >> As part of my documentation project, I am starting to turn my attention >> towards the code itself. I am trying to understand how the system work

Re: [jseive] Folding into a single module

Hi David, Answers inlined. Cheers, On 16/05/2020 14:36, David Leangen wrote: > Hi! > > I noticed that there is a “util” module that is released as a separate jar. > > Given that the size of the jsieve project is so small, is it really necessary > to release it as two separate jar files? Would

Re: Guice vs. Spring

On Sun, 2020-05-17 at 14:32 +0900, David Leangen wrote: > Hello, > > [...] > Why are there two frameworks (both Guice AND Spring) instead of just > one? Don’t they basically accomplish the same thing? Of course, they even share annotations with `javax.inject`. It's two implementations for a sa