[
https://issues.apache.org/jira/browse/MIME4J-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495869
]
Niklas Therning commented on MIME4J-5:
--
Please move to 0.4. IMO, even if it gets fixed soon it will require a lot
[
https://issues.apache.org/jira/browse/MIME4J-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495830
]
Stefano Bagnara commented on MIME4J-5:
--
What's the status of this issue? Can we move this to 0.4 or should we wait
[
https://issues.apache.org/jira/browse/MIME4J-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-7.
--
Resolution: Fixed
Assignee: Stefano Bagnara
I don't have an Ubuntu to test this, but I thin
Author: bago
Date: Mon May 14 18:11:59 2007
New Revision: 538032
URL: http://svn.apache.org/viewvc?view=rev&rev=538032
Log:
Changed non-ascii chars in string to unicode literals "\u" (MIME4J-7)
Modified:
james/mime4j/trunk/src/test/java/org/apache/james/mime4j/decoder/QuotedPrintableInpu
[
https://issues.apache.org/jira/browse/MIME4J-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-11.
---
Resolution: Fixed
As an improvement it would be cool to have brand new test messages created f
[
https://issues.apache.org/jira/browse/MIME4J-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-1.
--
Resolution: Fixed
I hope the current solution is enough.
We now use a local stage repository whe
[
https://issues.apache.org/jira/browse/MIME4J-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-10.
---
Resolution: Fixed
Scripts have been removed.
The example java file has been fixed.
The poms ha
[
https://issues.apache.org/jira/browse/MIME4J-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-13.
---
Resolution: Fixed
> Add implementation/specification versions to Manifest
> --
[
https://issues.apache.org/jira/browse/MIME4J-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-14.
---
Resolution: Fixed
> Prefix generated artifacts with "apache-"
> --
[
https://issues.apache.org/jira/browse/MIME4J-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-15.
---
Resolution: Fixed
> Create a BUILDING.txt file
> --
>
>
Update on this issue.
robert burrell donkin ha scritto:
> On 5/11/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I just deployed snapshot builds for mime4j here:
>> http://people.apache.org/~bago/mime4j/
>
> it's best to prefix the jar names with 'apache' (eg
> apache-james-mime4
if you have 10 minutes to waste feel free to read all, otherwise search
for "" ;-)
robert burrell donkin ha scritto:
> On 5/13/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
>> robert burrell donkin ha scritto:
>> > not sure how critical it really is. apache tends to be loathed to take
>> > legal
Norman Maurer ha scritto:
> Stefano Bagnara schrieb:
>> Norman Maurer (JIRA) ha scritto:
>>
>>> This is the diff for backporting to 2.3 branch . Any thoughts ?
>
>> Considering this "weird behavior" is there since 2.2.0 and that it was a
>> known issue at release time I'm -0 on backporting this
Norman Maurer ha scritto:
> Hi Stefano,
>
> thx for takin care, but I think maven 2.0.5 should be enough for
> building ;-)
I tested only 2.0.6, so I've been conservative.
If you tested 2.0.5 and it worked fine then I can write 2.0.5, or better
you can do this directly before releasing :-)
Ste
Danny Angus ha scritto:
> On 5/14/07, Steve Brewin <[EMAIL PROTECTED]> wrote:
>
>> Just to be clear, for the .jar filenames we are really talking about no
>> spaces, either camelCased or hyphenated aren't we? Those pesky spaces
>> cause
>> more trouble than they are worth!
>
> OMG I hope so!
I
Jukka Zitting ha scritto:
> Hi,
>
> I'm working on the JCR mail repository for James, and I'd like to
> better understand the Mail and MailRepository interfaces.
>
> a) Should implementations of the MailRepository class be thread-safe?
YES
> b) Should the Avalon lifecycle interfaces be used whe
On 5/14/07, Steve Brewin <[EMAIL PROTECTED]> wrote:
Just to be clear, for the .jar filenames we are really talking about no
spaces, either camelCased or hyphenated aren't we? Those pesky spaces cause
more trouble than they are worth!
OMG I hope so!
Author: rdonkin
Date: Mon May 14 14:34:05 2007
New Revision: 537986
URL: http://svn.apache.org/viewvc?view=rev&rev=537986
Log:
Remove unnecessary coupling.
Modified:
james/server/sandbox/seda-imap-modular/experimental-seda-imap-function/src/main/java/org/apache/james/experimental/imapserver/
Hi,
I'm working on the JCR mail repository for James, and I'd like to
better understand the Mail and MailRepository interfaces.
a) Should implementations of the MailRepository class be thread-safe?
b) Should the Avalon lifecycle interfaces be used when implementing
MailRepository?
c) What part
Modified:
james/server/sandbox/seda-imap-modular/experimental-seda-imap-function/src/main/java/org/apache/james/experimental/imapserver/processor/imap4rev1/ExamineAndSelectProcessor.java
URL:
http://svn.apache.org/viewvc/james/server/sandbox/seda-imap-modular/experimental-seda-imap-function/src/m
Norman Maurer wrote:
>
>
> Danny Angus schrieb:
> > On 5/14/07, Bernd Fondermann
> <[EMAIL PROTECTED]> wrote:
> >> I'd prefer
> >> Apache James Server, Apache mime4j, Apache jspf, as they constitute
> >> products on their own.
> >
> > +1.
> >
> > d.
> >
>
> +1
> Norman
Just to be clear, for the .j
Danny Angus schrieb:
> On 5/14/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
>> I'd prefer
>> Apache James Server, Apache mime4j, Apache jspf, as they constitute
>> products on their own.
>
> +1.
>
> d.
>
+1
Norman
-
To unsubs
Hi Stefano,
more comments inline ..
Stefano Bagnara schrieb:
> Norman Maurer (JIRA) ha scritto:
>
>> [
>> https://issues.apache.org/jira/browse/JAMES-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Norman Maurer updated JAMES-787:
>>
On 5/13/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
robert burrell donkin ha scritto:
> not sure how critical it really is. apache tends to be loathed to take
> legal action. IIRC this arose around 5 years ago but i can't remember
> why. it can't have been that important or it would have been
Hi Stefano,
thx for takin care, but I think maven 2.0.5 should be enough for
building ;-)
bye
Norman
[EMAIL PROTECTED] schrieb:
> Author: bago
> Date: Mon May 14 10:37:39 2007
> New Revision: 537923
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=537923
> Log:
> Created a simple BUILDING.txt
Author: bago
Date: Mon May 14 10:38:10 2007
New Revision: 537924
URL: http://svn.apache.org/viewvc?view=rev&rev=537924
Log:
Changed artifactId to apache-mime4j (MIME4J-14)
Added more informations to MANIFEST.MF (MIME4J-13)
Modified:
james/mime4j/trunk/pom.xml
Modified: james/mime4j/trunk/pom
Author: bago
Date: Mon May 14 10:37:39 2007
New Revision: 537923
URL: http://svn.apache.org/viewvc?view=rev&rev=537923
Log:
Created a simple BUILDING.txt file (MIME4J-15)
Added:
james/mime4j/trunk/BUILDING.txt
Added: james/mime4j/trunk/BUILDING.txt
URL:
http://svn.apache.org/viewvc/james/mi
+1
Vincenzo
Danny Angus wrote:
On 5/14/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
I'd prefer
Apache James Server, Apache mime4j, Apache jspf, as they constitute
products on their own.
+1.
d.
-
To unsubscribe, e-mail:
Norman Maurer (JIRA) ha scritto:
> [
> https://issues.apache.org/jira/browse/JAMES-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Norman Maurer updated JAMES-787:
>
>
> Attachment: localResolv-2.3.diff
>
> This is the dif
On 5/14/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
I'd prefer
Apache James Server, Apache mime4j, Apache jspf, as they constitute
products on their own.
+1.
d.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional c
Create a BUILDING.txt file
--
Key: MIME4J-15
URL: https://issues.apache.org/jira/browse/MIME4J-15
Project: Mime4j
Issue Type: Task
Affects Versions: 0.3
Reporter: Stefano Bagnara
Assigned To:
Prefix generated artifacts with "apache-"
-
Key: MIME4J-14
URL: https://issues.apache.org/jira/browse/MIME4J-14
Project: Mime4j
Issue Type: Task
Affects Versions: 0.3
Reporter: Stefano
Add implementation/specification versions to Manifest
-
Key: MIME4J-13
URL: https://issues.apache.org/jira/browse/MIME4J-13
Project: Mime4j
Issue Type: Improvement
Affects Versions: 0.3
On 5/14/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Do you prefer "apache-james-mime4j-0.3.jar" or "apache-mime4j-0.3.jar" ?
In practice: when the project name is already in the james namespace
(server alone does not identify a james product, but jspf, jsieve,
mime4j, postage and mailet do) s
+1
On 5/14/07, Danny Angus <[EMAIL PROTECTED]> wrote:
Irrespective of whether or not this is an ASF wide "policy", I would
say that that putting "apache" in James jar names is a practice which
a) we could easily adopt, and b) makes a fair amount of sense, and
therefore I would propose that we do
Do you prefer "apache-james-mime4j-0.3.jar" or "apache-mime4j-0.3.jar" ?
In practice: when the project name is already in the james namespace
(server alone does not identify a james product, but jspf, jsieve,
mime4j, postage and mailet do) should we use "apache-" instead of
"james" or should we us
Danny Angus ha scritto:
> Irrespective of whether or not this is an ASF wide "policy", I would
> say that that putting "apache" in James jar names is a practice which
> a) we could easily adopt, and b) makes a fair amount of sense, and
> therefore I would propose that we do so.
>
> d.
I was alrea
Irrespective of whether or not this is an ASF wide "policy", I would
say that that putting "apache" in James jar names is a practice which
a) we could easily adopt, and b) makes a fair amount of sense, and
therefore I would propose that we do so.
d.
--
38 matches
Mail list logo
