i really like the RFC excerpts included as comments in the IMAP
commands but i wonder whether we need to do stuff like attribution.
has anyone asked on legal discuss about this?
- robert
-
To unsubscribe, e-mail: [EMAIL PROTECTE
I believe that the isoc / ietf are pretty relaxed about the use of
those documents in derivative works, they are copyright, and as such
we should attribute them. I would suggest that in the Class comment we
put "Extracts from rfc's (C) ISOC" or whomever. It may also be polite
to check this with th
On 2/3/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Where should we add documentation?
Good question, some where in
here:http://james.apache.org/server/2.3.0/index.html and possibly as
an FAQ.
I'll do this, perhaps you could raise a jira issue and assign it to me
so I don't forget.
d.
-
On 2/3/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> with the need to modularise, i think that there's now more convergence
> towards this
>
> given a little initial restructuring (moving code around), it should
> be possible to gradually move code out from the phe
On 2/3/07, David Woldrich <[EMAIL PROTECTED]> wrote:
Robert,
>
>>
>> their systems. Is there anything screwy about picking the Spring
>> framework as the official container into which James is poured?
>> Couldn't that just be how James is shipped from the core team?
>
> experienced has proved t
On 2/3/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Where should we add documentation?
Good question, some where in
here:http://james.apache.org/server/2.3.0/index.html and possibly as
an FAQ.
I'll do this, perhaps you could raise a jira issue and assign it to me
so I don't forget.
d.
-
Author: rdonkin
Date: Sun Feb 4 05:13:36 2007
New Revision: 503403
URL: http://svn.apache.org/viewvc?view=rev&rev=503403
Log:
Dependency diagram for modular server
Added:
james/server/sandbox/design-doodles/modules/
james/server/sandbox/design-doodles/modules/dependencies.dia (with pro
there seems to be a rough consensus in favour of modularising james.
i've pulled together a document about one possible design
(http://wiki.apache.org/james/Development/Modularisation). this is
just one possible direction but this proposal is only about the first
step towards modularization. pleas
Added:
james/server/sandbox/seda-imap/src/test/org/apache/james/imapserver/MockImapResponseWriter.java
URL:
http://svn.apache.org/viewvc/james/server/sandbox/seda-imap/src/test/org/apache/james/imapserver/MockImapResponseWriter.java?view=auto&rev=503406
===
robert burrell donkin wrote:
PROPOSAL:
1.1 move server/trunk -> server/trunk/pheonix-deployment
1.2 create top level build which delegates to build.xml
--8<-
[X] +1 cool
[ ] +0
[ ] -0
[ ] -1 uncool
--
On 2/4/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> PROPOSAL:
> 1.1 move server/trunk -> server/trunk/pheonix-deployment
> 1.2 create top level build which delegates to build.xml
>
> --8<-
> [X] +1 cool
>
robert burrell donkin wrote:
On 2/3/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I prefer maven2 for modular builds. Imho make things more clear.
On the other side I think that who *does* stuff have a special choice on
how to do this, so I'm +1 *if* you'll take care of this.
a reorganisatio
robert burrell donkin wrote:
how does the mavenized website build work ATM?
the pom.xml you see in the root should be able to make a full build of
james core. It does not bundle the phoenix stuff in the generated
artifact, but it builds the classes, run the tests and build the website
(src/s
robert burrell donkin schrieb:
> there seems to be a rough consensus in favour of modularising james.
> i've pulled together a document about one possible design
> (http://wiki.apache.org/james/Development/Modularisation). this is
> just one possible direction but this proposal is only about the fi
Danny Angus schrieb:
> On 2/3/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
>
>> Where should we add documentation?
>
> Good question, some where in
> here:http://james.apache.org/server/2.3.0/index.html and possibly as
> an FAQ.
>
>
> I'll do this, perhaps you could raise a jira issue and assign
Norman Maurer wrote:
Danny Angus schrieb:
On 2/3/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Where should we add documentation?
Good question, some where in
here:http://james.apache.org/server/2.3.0/index.html and possibly as
an FAQ.
I'll do this, perhaps you could raise a jira issue an
Add documentation for the dns ttl issue
---
Key: JAMES-774
URL: https://issues.apache.org/jira/browse/JAMES-774
Project: James
Issue Type: Task
Affects Versions: 2.3.1-dev, Next Major
Repor
[EMAIL PROTECTED] wrote:
>
>
> On 2/1/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
>
> > Unfortunately I think that hot redeployable mailets are far away,
>
> the biggest issue is that you would have to move all "in process"
> messages to a save point that you know will allow them to continue
> a
Author: rdonkin
Date: Sun Feb 4 12:16:21 2007
New Revision: 503471
URL: http://svn.apache.org/viewvc?view=rev&rev=503471
Log:
Added ability to register custom commands through the configuration.
Added:
james/server/trunk/src/java/org/apache/james/remotemanager/Command.java
james/server/
[
https://issues.apache.org/jira/browse/JAMES-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Burrell Donkin closed JAMES-656.
---
Resolution: Fixed
Committed
> Remote Manager Command Plugins
> --
On 2/4/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
On 2/3/07, David Woldrich <[EMAIL PROTECTED]> wrote:
> So, Spring would be the officially supported platform -
> the only one that the core James team needs to be savvy with, but by no
> means would Spring be the only container that cou
Steve,
On 2/4/07, Steve Brewin <[EMAIL PROTECTED]> wrote:
With these two issues resolved a simple script could be used to bring up the
new server with a new and already tested configuration, switch the IP
redirection to point to this server, then "drain and close" the old server.
If you could
On 2/4/07, Steve Brewin <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
>
>
> On 2/1/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
>
> > Unfortunately I think that hot redeployable mailets are far away,
>
> the biggest issue is that you would have to move all "in process"
> messages to a sav
On 2/4/07, Danny Angus <[EMAIL PROTECTED]> wrote:
It might also make sense to divide up the config of James into
distinct component configurations.
+1
the monolithic configuration is one of my main PITAs ATM so this is
something i've been thinking about today :-)
but it might be solved by
On 2/4/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
in this case, it seems unreasonable to stop
serving corporate emails just so because some enterprise application
needs to reconfigure their mailets.
This is kind-of my point, you can re-deploy or reconfigure the
server's behaviour wit
On 2/4/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
but it might be solved by moving into the world of mail applications...
Yeah, but at some point there will have to be a "vendor specific"
container config, even if the bulk of the behaviour is in the std. app
config. For a long while n
[
https://issues.apache.org/jira/browse/JAMES-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470089
]
Bernd Fondermann commented on JAMES-767:
As far as I remember, previous versions of James did not show excepti
Danny Angus schrieb:
> On 2/4/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
>> but it might be solved by moving into the world of mail applications...
>
> Yeah, but at some point there will have to be a "vendor specific"
> container config, even if the bulk of the behaviour is in the std. ap
[EMAIL PROTECTED] wrote:
> Steve,
>
> On 2/4/07, Steve Brewin <[EMAIL PROTECTED]> wrote:
>
> > With these two issues resolved a simple script could be
> used to bring up the
> > new server with a new and already tested configuration,
> switch the IP
> > redirection to point to this server, then "dr
Author: rdonkin
Date: Sun Feb 4 13:35:34 2007
New Revision: 503489
URL: http://svn.apache.org/viewvc?view=rev&rev=503489
Log:
Fixed versions are useful for testing.#
Added:
james/server/sandbox/tags/
-
To unsubscribe, e-ma
Author: rdonkin
Date: Sun Feb 4 13:37:20 2007
New Revision: 503490
URL: http://svn.apache.org/viewvc?view=rev&rev=503490
Log:
First milestone in IMAP refactoring.
Added:
james/server/sandbox/tags/seda-imap_M1/
- copied from r503489, james/server/sandbox/seda-imap/
---
i've tagged a first milestone for the IMAP refactoring. the code runs
ok on my local IMAP server (but i will continue testing):
http://svn.apache.org/repos/asf/james/server/sandbox/tags/seda-imap_M1
if anyone else fancies giving it a try that would be really great: i'd
like to move this code into
32 matches
Mail list logo