[
https://issues.apache.org/jira/browse/JAMES-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Kvokacka updated JAMES-1313:
--
Attachment: ReadOnlyUsersLDAPRepository.java.patch
I checked out trunk version of server/ldap a
>>
>> Hi Ioan,
>>
>> I already did something similar, but it doesn't work.
>> Finally, I have created by hand the target/classes and target/test-classes.
>>
>> Now it generates the site with javadoc, but with standard pages, although
>> org.jboss.apiviz.APIviz is taken in the pom (looking in .m2 ca
[
https://issues.apache.org/jira/browse/JAMES-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer resolved JAMES-1312.
--
Resolution: Fixed
Assignee: Norman Maurer
fixed.. The NPE was harmless as it was just thr
Author: norman
Date: Mon Sep 12 14:02:41 2011
New Revision: 1169750
URL: http://svn.apache.org/viewvc?rev=1169750&view=rev
Log:
Fix harmless NPE when there are still bytes in the buffer but the connection
was closed already. See JAMES-1312
Modified:
james/server/trunk/imapserver/src/main/j
[
https://issues.apache.org/jira/browse/JSPF-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer updated JSPF-93:
--
Priority: Minor (was: Major)
> FutureSPFResult.isReady() MUST be synchronized
> -
[
https://issues.apache.org/jira/browse/JSPF-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer resolved JSPF-93.
---
Resolution: Fixed
> FutureSPFResult.isReady() MUST be synchronized
> ---
Author: norman
Date: Mon Sep 12 13:34:29 2011
New Revision: 1169740
URL: http://svn.apache.org/viewvc?rev=1169740&view=rev
Log:
Synchronize FutureSPFResult.isReady() to avoid race-conditions. See JSPF-93
Modified:
james/jspf/trunk/resolver/src/main/java/org/apache/james/jspf/executor/FutureS
FutureSPFResult.isReady() MUST be synchronized
--
Key: JSPF-93
URL: https://issues.apache.org/jira/browse/JSPF-93
Project: JAMES jSPF
Issue Type: Bug
Components: Core
Affects Versions
[
https://issues.apache.org/jira/browse/JAMES-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102640#comment-13102640
]
Norman Maurer commented on JAMES-1313:
--
Could you upload the patch as diff and check
[
https://issues.apache.org/jira/browse/JAMES-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Kvokacka updated JAMES-1313:
--
Description:
Hello
I'd like to use james in my current project, but I find LDAP implementatio
@Deprecate FutureSPFResult
--
Key: JSPF-92
URL: https://issues.apache.org/jira/browse/JSPF-92
Project: JAMES jSPF
Issue Type: Improvement
Components: Core
Affects Versions: 0.9.9
Reporter: No
more effective getUserByName(String name) in
org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository
Key: JAMES-1313
URL: https://issues.apache.org/jira/browse/JA
On Mon, Sep 12, 2011 at 12:07, Norman Maurer
wrote:
> Hi Bernd,
>
> I'm currently thinking about it, yeah. Github was the quickest way for
> me to get started and also learn a bit more about git so I started it
> there. But I agree it would make sense to move it to james sometimes
> as it is reall
Hi Bernd,
I'm currently thinking about it, yeah. Github was the quickest way for
me to get started and also learn a bit more about git so I started it
there. But I agree it would make sense to move it to james sometimes
as it is really related..
Bye,
Norman
2011/9/12 Bernd Fondermann :
> On Sun
On Sun, Sep 11, 2011 at 19:44, Norman Maurer
wrote:
> Hi there,
>
> I think its time to finally get rid of javamail for sending emails via
> SMTP / SMTPS and use something more performant / better suited for
> heavy usage. javamail just sucks in many ways for SMTP Delivery in a
> way that a real s
15 matches
Mail list logo