Stefano Bagnara wrote:
Noel J. Bergman wrote:
Stefano Bagnara wrote:
Noel J. Bergman wrote:
2.3.0a4 time? :)
We should follow a different iter for this.
I don't want to tag the branch (and have an alpha number) for each bug
fixed ;-)
We already posted 2.3.0a3, even if unannounced, a
Noel J. Bergman wrote:
Stefano Bagnara wrote:
Noel J. Bergman wrote:
2.3.0a4 time? :)
We should follow a different iter for this.
I don't want to tag the branch (and have an alpha number) for each bug
fixed ;-)
We already posted 2.3.0a3, even if unannounced, and it has a critical bug.
We
Stefano Bagnara wrote:
> Noel J. Bergman wrote:
> > 2.3.0a4 time? :)
> We should follow a different iter for this.
> I don't want to tag the branch (and have an alpha number) for each bug
> fixed ;-)
We already posted 2.3.0a3, even if unannounced, and it has a critical bug.
We don't put out unt
Noel J. Bergman wrote:
Stefano Bagnara wrote:
Btw, tomorrow I'll apply the fixes (a+b+c2) to the branch (and trunk, of
course),
2.3.0a4 time? :)
--- Noel
We should follow a different iter for this.
I don't want to tag the branch (and have an alpha number) for each bug
fixed ;-)
Stefano Bagnara wrote:
> Btw, tomorrow I'll apply the fixes (a+b+c2) to the branch (and trunk, of
> course),
2.3.0a4 time? :)
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAI
Steve Brewin wrote:
My preference is to release the a3 anyway: if we never release we'll
always find similar bugs the day we vote for the following release :-(
Personally, I'ld say this is a rather critical bug as aliasing/forwarding is
one of the core usages of James. I don't think we should e
Norman Maurer wrote:
I can do this tonight or tomorrow but I don't know if we should stop the
a3 release or do it anyway letting users know it has critical bugs with
file based users repository.
My preference is to release the a3 anyway: if we never release we'll
always find similar bugs the
Stefano Bagnara wrote:
>
>
> I need more information.
>
> As far as I know aliasing and forwarding is available only
> when the user
> is a JamesUser.
>
> The "UsersRepositoryAliasingForwarding" mailet is a mailet
> that compose
> the "old" LocalDelivery mailet. I introduced it during a
> refactori
Am Freitag, den 19.05.2006, 20:01 +0200 schrieb Stefano Bagnara:
> I need more information.
>
> As far as I know aliasing and forwarding is available only when the user
> is a JamesUser.
>
> The "UsersRepositoryAliasingForwarding" mailet is a mailet that compose
> the "old" LocalDelivery mailet
I need more information.
As far as I know aliasing and forwarding is available only when the user
is a JamesUser.
The "UsersRepositoryAliasingForwarding" mailet is a mailet that compose
the "old" LocalDelivery mailet. I introduced it during a refactoring a
few months ago.
1) We should add
Noel J. Bergman wrote:
Bernd Fondermann wrote:
I set up vanilla james config and in the users-store section replaced
the default db-store with file.
java.lang.ClassCastException
UsersRepositoryAliasingForwarding.java:193)
That is: user = (JamesUser) usersRepository.getUserByName(username)
Bernd Fondermann wrote:
> I set up vanilla james config and in the users-store section replaced
> the default db-store with file.
> java.lang.ClassCastException
> UsersRepositoryAliasingForwarding.java:193)
That is: user = (JamesUser) usersRepository.getUserByName(username);
I'll check the cod
Hi,
I discovered a potential issue today. I could not yet do an in-depth
analysis of the problem, but maybe someone can reproduce.
I set up vanilla james config and in the users-store section replaced
the default db-store with file.
After that I get the following errors every time I send a
13 matches
Mail list logo
