in mailets project which I was
not able to resolve myself. I would ask for assistance when there is a
broader consensus about my proposal.
Please comment.
Best,
gazda
On Wed, Jun 27, 2012 at 6:55 PM, Jochen Gazda gazdahims...@gmail.com wrote:
Gentlemen,
I have finally managed it to publish my
/compare/master...MAILBOX-175
to see the relevant diffs.
On 06/27/2012 06:55 PM, Jochen Gazda wrote:
Gentlemen,
I have finally managed it to publish my changeset on GitHub:
https://github.com/gazdahimself/current/tree/MAILBOX-175
The state of my brach MAILBOX-175 is in sync
to MailboxPath in mailets project.
Unfortunatelly I was not able to grasp the purpose of those refs and I
was not able to fix them.
Thx again,
Eric
On 06/28/2012 11:21 AM, Jochen Gazda wrote:
Gentlemen,
I have fixed some minor issues in my proposal so please consider my
update from 2012-06
Hi Eric,
see inline.
Best,
gazda
On Thu, Jun 28, 2012 at 4:57 PM, Eric Charles e...@apache.org wrote:
On 06/28/2012 04:00 PM, Jochen Gazda wrote:
1.- profile noTest on mailbox-integration-tester: ok
2.- LocalAndVirtualMailboxLocatorChain: what's the goal?
MailDir is a file system based
to your personal github. It offers nice ui to show
diffs.
Thx, Eric
On 06/13/2012 10:32 AM, Jochen Gazda wrote:
Gentlemen,
I could invest about 6 weeks of my time into solving
https://issues.apache.org/jira/browse/MAILBOX-175 and
https://issues.apache.org/jira/browse/MAILBOX-167
Gentlemen,
is there anybody here who has managed it to create a working dir with git-svn?
I am trying to apply Git for Apache committers as decribed here
http://wiki.apache.org/general/GitAtApache . This is what I am doing:
---8
#!/bin/bash
set -x
set -e
# put your ASF
time and can give you surprises...
Of course, the james multi-project nature will not help you...
Thx, Eric
On 06/14/2012 10:40 AM, Jochen Gazda wrote:
Gentlemen,
is there anybody here who has managed it to create a working dir with
git-svn?
I am trying to apply Git for Apache
Gentlemen,
I could invest about 6 weeks of my time into solving
https://issues.apache.org/jira/browse/MAILBOX-175 and
https://issues.apache.org/jira/browse/MAILBOX-167.
The result is quite a huge and deep changeset. There is a de facto
replacement for MailboxPath - so you can imagine, how many
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260641#comment-13260641
]
Jochen Gazda commented on MAILBOX-175:
--
The ability of the current James code
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260869#comment-13260869
]
Jochen Gazda commented on MAILBOX-175:
--
Ioan, I see only http://www.apps.ietf.org
Gentlemen,
I would like to set myself as Assignee in Jira (e.g. for MAILBOX-167).
How can I do that? Am I missing some permission?
Best,
gazda
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional
[
https://issues.apache.org/jira/browse/MAILBOX-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256260#comment-13256260
]
Jochen Gazda commented on MAILBOX-167:
--
As there are no protests, I am starting
Thank you for your prompt reaction, Stefano.
On Wed, Apr 18, 2012 at 9:25 AM, Stefano Bagnara apa...@bago.org wrote:
2012/4/18 Jochen Gazda gazdahims...@gmail.com:
Gentlemen,
I would like to set myself as Assignee in Jira (e.g. for MAILBOX-167).
How can I do that? Am I missing some
[
https://issues.apache.org/jira/browse/MAILBOX-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated MAILBOX-167:
-
Assignee: Jochen Gazda (was: Norman Maurer)
Assigning to me.
Make
Components: api
Reporter: Jochen Gazda
Assignee: Norman Maurer
Make the contract of org.apache.james.mailbox.model.MailboxPath explicit and
documented.
Points to consider:
(1) Make all attributes immutable - can be done quite easily, no discussion
expected.
(2) Null
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda reassigned MAILBOX-175:
Assignee: Jochen Gazda (was: Norman Maurer)
Make the contract of MailboxPath
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated MAILBOX-175:
-
Issue Type: Sub-task (was: Task)
Parent: MAILBOX-167
Make the contract
[
https://issues.apache.org/jira/browse/MAILBOX-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256432#comment-13256432
]
Jochen Gazda commented on MAILBOX-167:
--
Eric,
(1) does the rfc describe
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256435#comment-13256435
]
Jochen Gazda commented on MAILBOX-175:
--
Eric,
what does the rfc says regarding
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256491#comment-13256491
]
Jochen Gazda commented on MAILBOX-175:
--
Thanks for your comments, Ioan.
I have
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256567#comment-13256567
]
Jochen Gazda commented on MAILBOX-175:
--
not sure, but is the caller gives a null
[
https://issues.apache.org/jira/browse/MAILBOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256644#comment-13256644
]
Jochen Gazda commented on MAILBOX-175:
--
what does the rfc says regarding
Reporter: Jochen Gazda
Assignee: Jochen Gazda
Ensure that the use of MailboxConstants.USER_NAMESPACE is not too blind. Some
occurences may come from times when there was no alternative.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please
[
https://issues.apache.org/jira/browse/MAILBOX-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated MAILBOX-176:
-
Description:
Ensure that the use of MailboxConstants.USER_NAMESPACE is not too blind. Some
[
https://issues.apache.org/jira/browse/PROTOCOLS-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255397#comment-13255397
]
Jochen Gazda commented on PROTOCOLS-95:
---
Ioan,
the way how Cyrus IMAP Server
is done.
Thx,
Eric
On 16/03/12 08:42, Jochen Gazda wrote:
Eric,
I just wanted to merge the ACL code from apache-james-imap to
protocols-imap, but I am still seeing the default build run to use
the apache-james-imap code. Is there some simple way how I could tell
James to switch
)
with a few mails (list mailbox, move mails, search,...).
Maybe we could further talk and let evolve (3).
Thx,
Eric
On 04/17/2012 04:48 PM, Jochen Gazda wrote:
Eric,
In my wokspace, I have:
(1) changed the pom's in that way that that the protocols-imap code is
used instead of apache-james
Eric,
I just wanted to merge the ACL code from apache-james-imap to
protocols-imap, but I am still seeing the default build run to use
the apache-james-imap code. Is there some simple way how I could tell
James to switch to the protocols-imap code?
Thank you,
gazda
On Fri, Mar 9, 2012 at 2:14
Gentlemen,
In accordance with what has been said in this thread and with Stefano
Bagnara's we should always try to build with the latest available
released parent (not even a snapshot), may I commit following two
changes?
(1) change parent.version from 1.9-SNAPSHOT 1.8.1 in hupa/pom.xml
(2)
Gentlemen,
just reposting my old questions.
I would like to proceed with
https://issues.apache.org/jira/browse/IMAP-358 Enforce rights required
to perform different IMAP4rev1 Commands in IMAP processors.
(1) Is there something new with protocols-imap vs. apache-james-imap?
(2) Tests: Is there a
Eric,
please see inline.
(1) I would love to see the current activity in protocols-imap. I had to
postpone my contribution on the integration (b4 release and many other
stuff), but next week should be a good week for me to work on this. I
propose you continue your implementations in
Sai,
from my experience, I can say that the plain http svn access ceased to
work a couple of weeks
ago. Try the same URL with https.
Best,
gazda
On Fri, Feb 24, 2012 at 12:22 PM, Saibabu Vallurupalli
saibabu.vallurupa...@gmail.com wrote:
Hi Eric,
I am following the steps given in this page:
out so
much of code. I need only the latest development version to do some
development.
Thanks,
Sai
On Fri, Feb 24, 2012 at 8:25 AM, Jochen Gazda gazdahims...@gmail.comwrote:
Sai,
from my experience, I can say that the plain http svn access ceased to
work a couple of weeks
ago. Try
[ ] +0 insufficient insight
Just a single point: there is [MAILBOX-154] - Add ACL support in
release notes. It could cause a false impression that mailbox 0.4 is
going to support ACLs which is not the case.
-
To unsubscribe,
[ ] +0 insufficient insight
Best,
gazda
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
update
mvn clean install -DskipTests
Best,
gazda
On Fri, Jan 13, 2012 at 10:23 AM, Jochen Gazda gazdahims...@gmail.com wrote:
Thanks for the tips, Eric and Ioan. Maven seems to work as expected now.
Gazda
On Thu, Jan 12, 2012 at 8:13 AM, Ioan Eugen Stan stan.ieu...@gmail.com
wrote:
Pe
[
https://issues.apache.org/jira/browse/HUPA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda resolved HUPA-84.
--
Resolution: Fixed
Make web.xml dtd compliant
--
Key: HUPA
[
https://issues.apache.org/jira/browse/HUPA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda closed HUPA-84.
Make web.xml dtd compliant
--
Key: HUPA-84
URL
Gentlemen,
On the way to usable group folders and ACL, I found that namespaces
are not handled consistently.
(1) in StoreMessageManager.isGroupFolder(MailboxSession), if the
present folder is the current user's INBOX, mailbox.getNamespace() and
session.getPersonalSpace() should return the same
Eric,
may I commit now? Or should I do it after the upcoming mailbox release?
I have changes in:
- apache-james-imap-api
- apache-james-imap-message
- apache-james-imap-processor
- apache-james-mailbox-api
- apache-james-mailbox-store
Best,
gazda
Thank your replies, Stefano and Eric.
See inline.
Best,
gazda
On Tue, Feb 21, 2012 at 3:31 PM, Stefano Bagnara apa...@bago.org wrote:
2012/2/21 Jochen Gazda gazdahims...@gmail.com:
(1) []
But as for parent references I am asking myself what can be the reason
for distinct versions
[
https://issues.apache.org/jira/browse/IMAP-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated IMAP-359:
--
Summary: Implement missing ACL commands SETACL, LISTRIGHTS, MYRIGHTS and
DELETERIGHTS (was: Implement
I have filled this in Jira under
https://issues.apache.org/jira/browse/MAILBOX-167
On Tue, Feb 21, 2012 at 8:31 PM, Jochen Gazda gazdahims...@gmail.com wrote:
Gentlemen,
On the way to usable group folders and ACL, I found that namespaces
are not handled consistently.
(1
Reporter: Jochen Gazda
Assignee: Norman Maurer
(1) in StoreMessageManager.isGroupFolder(MailboxSession), if the
present folder is the current user's INBOX, mailbox.getNamespace() and
session.getPersonalSpace() should return the same value, which they do
not. This makes some ACL commands
[
https://issues.apache.org/jira/browse/IMAP-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212961#comment-13212961
]
Jochen Gazda commented on IMAP-359:
---
The changes were committed but I am leaving this open
[
https://issues.apache.org/jira/browse/MAILBOX-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda closed MAILBOX-160.
Resolution: Fixed
Mapping of ACL to to READ-WRITE and READ-ONLY response codes
[
https://issues.apache.org/jira/browse/MAILBOX-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda closed MAILBOX-157.
Resolution: Fixed
Review the ACL persistence in MaildirFolder
Gentlemen,
In the next weeks, I would like to proceed with
https://issues.apache.org/jira/browse/IMAP-358 Enforce rights required
to perform different IMAP4rev1 Commands in IMAP processors.
Just two questions:
(1) Is it still OK if I further work under apache-james-imap and not
under
Make web.xml dtd compliant
--
Key: HUPA-84
URL: https://issues.apache.org/jira/browse/HUPA-84
Project: JAMES Hupa
Issue Type: Bug
Components: client
Reporter: Jochen Gazda
Assignee
[
https://issues.apache.org/jira/browse/HUPA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated HUPA-84:
-
Attachment: HUPA-84-patch.txt
The patch should be applied against /hupa-client/src/main/webapp/WEB-INF
Gentlemen,
could please somebody review and commit the
https://issues.apache.org/jira/browse/MAILBOX-160 patch so that I can
diff for https://issues.apache.org/jira/browse/IMAP-359?
Thank you,
gazda
-
To unsubscribe, e-mail:
ACL persistence in HBaseMailbox
---
Key: MAILBOX-161
URL: https://issues.apache.org/jira/browse/MAILBOX-161
Project: James Mailbox
Issue Type: Task
Components: hbase
Reporter: Jochen Gazda
ACL persistence in JPAMailbox
-
Key: MAILBOX-163
URL: https://issues.apache.org/jira/browse/MAILBOX-163
Project: James Mailbox
Issue Type: Task
Components: jpa mailbox
Reporter: Jochen Gazda
ACL persistence in JCRMailbox
-
Key: MAILBOX-162
URL: https://issues.apache.org/jira/browse/MAILBOX-162
Project: James Mailbox
Issue Type: Task
Components: jcr mailbox
Reporter: Jochen Gazda
Imap
Issue Type: Improvement
Components: Processor
Reporter: Jochen Gazda
RFC 4314 section 4. Write tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org
Components: api
Reporter: Jochen Gazda
Assignee: Norman Maurer
See org.apache.james.mailbox.MailboxListener.MailboxACLUpdated
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https
Components: Processor
Reporter: Jochen Gazda
GETACL implemented already
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more
[
https://issues.apache.org/jira/browse/IMAP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13205302#comment-13205302
]
Jochen Gazda commented on IMAP-351:
---
Just to sum up the state of the tasks mentioned
@Norman:
as we store the flags with each message I guess we also would share all flags
modifications. Is this not allowed as per rfc ?
RFC 4314 If the ACL server implements some flags as shared for a
mailbox... implies that it is OK to share *some* flags and I was not
able to find any
Components: store
Reporter: Jochen Gazda
Assignee: Norman Maurer
Patch follows
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure
[
https://issues.apache.org/jira/browse/MAILBOX-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated MAILBOX-160:
-
Attachment: MAILBOX-160-patch.txt
The patch applies against current project
Gentlemen,
I am working on the mapping of ACL to to READ-WRITE and READ-ONLY
response codes. The mapping is defined in RFC 4314 section 5.2. The
definition uses the term shared flags:
If the ACL server implements some flags as shared for a mailbox
(i.e., the ACL for the mailbox MAY be set up
[
https://issues.apache.org/jira/browse/MAILBOX-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203493#comment-13203493
]
Jochen Gazda commented on MAILBOX-156:
--
Eric,
GroupMembershipResolver
[
https://issues.apache.org/jira/browse/MAILBOX-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203498#comment-13203498
]
Jochen Gazda commented on MAILBOX-157:
--
Eric,
I am OK with that locking, but I know
[
https://issues.apache.org/jira/browse/IMAP-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated IMAP-354:
--
Attachment: IMAP-354-patch.txt
The patch centralizes the mailbox name encoding
[
https://issues.apache.org/jira/browse/IMAP-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202334#comment-13202334
]
Jochen Gazda commented on IMAP-354:
---
The patch needs to be applied against the root
: Processor
Reporter: Jochen Gazda
The patch follows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see
[
https://issues.apache.org/jira/browse/IMAP-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated IMAP-355:
--
Attachment: IMAP-355-patch.txt
The patch adds one ACL-specific human readable text.
As the text contains
[
https://issues.apache.org/jira/browse/IMAP-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated IMAP-355:
--
Attachment: (was: IMAP-355-patch.txt)
Improve human readable messages in GetACLProcessor
[
https://issues.apache.org/jira/browse/IMAP-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated IMAP-354:
--
Attachment: (was: IMAP-354-patch.txt)
Move all CharsetUtil.encodeModifiedUTF7 invocations
[
https://issues.apache.org/jira/browse/IMAP-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated IMAP-355:
--
Attachment: IMAP-355.1-patch.txt
Improved patch. Apply against apache-james-imap project
Issue Type: Task
Components: Processor
Reporter: Jochen Gazda
There is an anonymous MessageManager returned from
org.apache.james.imap.processor.base.MailboxEventAnalyserTest.mockManager.new
MailboxManager() {...}.getMailbox(MailboxPath, MailboxSession). Somebody should
: Task
Components: api
Reporter: Jochen Gazda
Assignee: Norman Maurer
Currently the GroupMembershipResolver is located within
org.apache.james.mailbox.MailboxACLResolver. Please move it to an appropriate
place or leave it where it is now. Then remove the FIXME tag
Reporter: Jochen Gazda
Assignee: Norman Maurer
There are two FIXMEs in org.apache.james.mailbox.maildir.MaildirFolder. Further
the ACL persistence should be tested.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your
Issue Type: Improvement
Components: store
Reporter: Jochen Gazda
Assignee: Norman Maurer
Patch follows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https
[
https://issues.apache.org/jira/browse/MAILBOX-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated MAILBOX-158:
-
Attachment: MAILBOX-158-patch.txt
Removes two FIXMEs. Is necessary so that user names and group
[
https://issues.apache.org/jira/browse/IMAP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13201538#comment-13201538
]
Jochen Gazda commented on IMAP-351:
---
Thanks for committing, Norman.
I noticed
Issue Type: Improvement
Reporter: Jochen Gazda
Priority: Minor
All CharsetUtil.encodeModifiedUTF7 invocations should be moved to
org.apache.james.imap.encode.ImapResponseComposer analogically to
org.apache.james.imap.decode.ImapRequestLineReader.mailbox()
--
This message
it into our
code-base. Please open a jira and attach the patch there (don't forget
to check the ASL2 box). Once its there I will pull the changes in.
Thanks,
Norman
2012/1/17 Jochen Gazda gazdahims...@gmail.com:
Gentlemen,
could please somebody have a look at the attached patch?
It should
Affects Versions: 0.3
Reporter: Jochen Gazda
Fix For: 0.3
Support for RFC 4314 IMAP4 Access Control List (ACL) Extension
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https
[
https://issues.apache.org/jira/browse/IMAP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Gazda updated IMAP-351:
--
Attachment: ImapGetACLTest.java
IMAP-GETACL.txt
The patch adds very basic support
Thanks for the tips, Eric and Ioan. Maven seems to work as expected now.
Gazda
On Thu, Jan 12, 2012 at 8:13 AM, Ioan Eugen Stan stan.ieu...@gmail.com wrote:
Pe 11.01.2012 21:40, Eric Charles a scris:
Hi Jochen,
Your settings.xml seems ok.
'mvn package' (or even compile) from a toplevel
to
apache-james-server-imap-* with
groupIdorg.apache.james.protocols/groupId
artifactIdprotocols-imap/artifactId
As said earlier, this copy of imap is less stable.
Thx,
Eric
On 10/01/12 19:52, Jochen Gazda wrote:
Eric,
On Fri, Jan 6, 2012 at 6:34 PM, Eric Charlese
Norman,
org.apache.james.pop3server.core.PassCmdHandler is not compilable
since your r1230560
org.apache.james.pop3server.core.PassCmdHandler.auth(POP3Session, String)
is not compatible with
org.apache.james.protocols.pop3.core.AbstractPassCmdHandler.auth(POP3Session,
String, String)
Best
Gentlemen,
I am quite new to maven, so maybe I am missing something obvious.
Issuing
cd james/current
svn update
mvn package -DskipTests -e
has brought a compilation error in james-server-protocols-library
saying that org.apache.james.protocols.api.logger.Logger could not be
resolved. From
On Tue, Jan 10, 2012 at 10:20 AM, Ioan Eugen Stan stan.ieu...@gmail.com wrote:
Pe 10.01.2012 11:14, Jochen Gazda a scris:
Gentlemen,
I am quite new to maven, so maybe I am missing something obvious.
Issuing
cd james/current
svn update
mvn package -DskipTests -e
has brought
there is something weird in your maven settings.xml?
Thx,
Eric
On 10/01/12 11:04, Jochen Gazda wrote:
On Tue, Jan 10, 2012 at 10:20 AM, Ioan Eugen Stanstan.ieu...@gmail.com
wrote:
Pe 10.01.2012 11:14, Jochen Gazda a scris:
Gentlemen,
I am quite new to maven, so maybe I am missing
Eric,
On Fri, Jan 6, 2012 at 6:34 PM, Eric Charles e...@apache.org wrote:
As a side note, we are moving IMAP code from
https://svn.apache.org/repos/asf/james/imap/trunk/
to
https://svn.apache.org/repos/asf/james/protocols/trunk/imap/
I would be better that you code in the latter.
I have
Gentlemen,
Please read and comment.
I have started to implement the ACL support. In the very first phase I
would like to
- add support for IMAP GETACL command and
- add support for storing ACL at least for one storage backend.
During this first phase I would like to learn how to do things in
Norman,
8. Interpretation of ACLs:
To have ACL stored on every mailbox is far from being able to tell if
the given user can perform the given operation for the given
mailbox(es when copying/moving).
A new service responsible for resolving of ACLs is necessary. I
propose to call it
leave such small stuff to fix to see if you
guys follow trunk :)
You can svn up, it should be fixed now.
Don't hesitate to come back if you like more information on any of the James
project.
Cheers,
Eric
On 03/01/12 15:03, Jochen Gazda wrote:
Ladies Gentlemen,
My Eclipse is showing
Eric,
thank you for your effort. Everything is as expected after your r1227116.
Best,
Gazda
On Wed, Jan 4, 2012 at 11:35 AM, Jochen Gazda gazdahims...@gmail.com wrote:
Thank you for your promt reaction, Eric.
however, after updating the following two are still missing the svn:ignore
Ladies Gentlemen,
My Eclipse is showing me changed or unversioned decorations on the
following resources, which should IMHO have svn:ignore prop set on
them (should they not?):
/maven-mpt-plugin/.settings
/protocols-imap/.classpath
/protocols-imap/.project
Best,
Gazda
93 matches
Mail list logo
