Mailet sub-project is alive :-)

[Danny Angus <da...@apache.org>]

Hi,

I've created the sub-project structure for mailet in /james/mailet/trunk

Noel has kindly moved the source from server/trunk mailet and
mailet-api into this.
(N.B. *not* james/transport/mailets)

I still have to:

1/ create a snapshot jar to fix the broken server/trunk
2/ generate the website
3/ call a vote and cut a release of mailet 2.3
4/ get the commit mails directed to the mailet-api list


d.

Re: Mailet sub-project is alive :-)

[Danny Angus <da...@apache.org>]

On 5/3/07, Norman Maurer <no...@apache.org> wrote:
> Hi Danny,
>
> nice to see you found the time :-)

Sorry I didn't fix server before the nightly build, I'm doing it now though.

d.

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: Mailet sub-project is alive :-)

[Norman Maurer <no...@apache.org>]

Hi Danny,

nice to see you found the time :-)
IF you need any help just call me ..

bye
Norman


Danny Angus schrieb:
> Hi,
>
> I've created the sub-project structure for mailet in /james/mailet/trunk
>
> Noel has kindly moved the source from server/trunk mailet and
> mailet-api into this.
> (N.B. *not* james/transport/mailets)
>
> I still have to:
>
> 1/ create a snapshot jar to fix the broken server/trunk
> 2/ generate the website
> 3/ call a vote and cut a release of mailet 2.3
> 4/ get the commit mails directed to the mailet-api list
>
>
> d.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Mailet sub-project is alive :-)

[Danny Angus <da...@apache.org>]

Hi,

I've created the sub-project structure for mailet in /james/mailet/trunk

Noel has kindly moved the source from server/trunk mailet and
mailet-api into this.
(N.B. *not* james/transport/mailets)

I still have to:

1/ create a snapshot jar to fix the broken server/trunk
2/ generate the website
3/ call a vote and cut a release of mailet 2.3
4/ get the commit mails directed to the mailet-api list


d.

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: Mailet sub-project is alive :-)

[Stefano Bagnara <ap...@bago.org>]

Danny Angus ha scritto:
> On 5/3/07, Stefano Bagnara <ap...@bago.org> wrote:
>> I would have preferred if the mailet project was created by COPYING
>> instead of MOVING from trunk so that trunk would have been fully working
>> and functional during this transition.
> 
> I hope it will be OK *before* the next nightly build.

Cool.

>> I have a couple of requests:
>>
>> 1) Please give me the time to fix the m2 pom stuff before trying to call
>> a release for mailet 2.3.
> 
> OK.
> 
>> 2) Maybe we should use 2.3.1 or 2.4 as the version number as the 2.3
>> release is the jar we bundled in the official james 2.3.0. On the other
>> side it is true that the api has not changed since james 2.3.0 release,
>> so it would only be a repackage of the same version (is there a best
>> practice in ASF for this?)
> 
> I think we should use 2.3.1 if it is identical to the jar in server
> 2.3.1, that way no one will be confused.

I don't think we can make anything "identical": we have to at least add
the NOTICE and LICENSE to the jar to make it redistributable as a
"standalone" artifact.

IIRC the sourcecode for the mailet in JAMES Server 2.3.0 and JAMES
Server 2.3.1 had not changed.

In the sourcecode for mailet we have some "@since Mailet API v2.3" so
I'm fine with anything >= 2.3

>> PS: weird choice to write this to private and mailet-api ;-)
> 
> We'll I sent it to mailet-api because thats the list for the project,
> and cc'ed the PMC because they (we?) should know about it.

They (we) should monitor all of the project mailing list ;-)
Btw it was only a joke because you looked too much susceptible to the
use of the private list :-)

> I'll fw it to server-dev too. I didn't want to cross post, but I guess
> this does affect them all.

+1
Thank you again,
Stefano

Re: Mailet sub-project is alive :-)

[Danny Angus <da...@apache.org>]

On 5/3/07, Stefano Bagnara <ap...@bago.org> wrote:
> I would have preferred if the mailet project was created by COPYING
> instead of MOVING from trunk so that trunk would have been fully working
> and functional during this transition.

I hope it will be OK *before* the next nightly build.

> I have a couple of requests:
>
> 1) Please give me the time to fix the m2 pom stuff before trying to call
> a release for mailet 2.3.

OK.


> 2) Maybe we should use 2.3.1 or 2.4 as the version number as the 2.3
> release is the jar we bundled in the official james 2.3.0. On the other
> side it is true that the api has not changed since james 2.3.0 release,
> so it would only be a repackage of the same version (is there a best
> practice in ASF for this?)

I think we should use 2.3.1 if it is identical to the jar in server
2.3.1, that way no one will be confused.

> PS: weird choice to write this to private and mailet-api ;-)

We'll I sent it to mailet-api because thats the list for the project,
and cc'ed the PMC because they (we?) should know about it.

I'll fw it to server-dev too. I didn't want to cross post, but I guess
this does affect them all.

Re: Mailet sub-project is alive :-)

[Stefano Bagnara <ap...@bago.org>]

I would have preferred if the mailet project was created by COPYING
instead of MOVING from trunk so that trunk would have been fully working
and functional during this transition.

Apart from this issue, that I hope will have a short life, thank you for
taking care of this!

I have a couple of requests:

1) Please give me the time to fix the m2 pom stuff before trying to call
a release for mailet 2.3.

2) Maybe we should use 2.3.1 or 2.4 as the version number as the 2.3
release is the jar we bundled in the official james 2.3.0. On the other
side it is true that the api has not changed since james 2.3.0 release,
so it would only be a repackage of the same version (is there a best
practice in ASF for this?)

Stefano

PS: weird choice to write this to private and mailet-api ;-)

Danny Angus ha scritto:
> Hi,
> 
> I've created the sub-project structure for mailet in /james/mailet/trunk
> 
> Noel has kindly moved the source from server/trunk mailet and
> mailet-api into this.
> (N.B. *not* james/transport/mailets)
> 
> I still have to:
> 
> 1/ create a snapshot jar to fix the broken server/trunk
> 2/ generate the website
> 3/ call a vote and cut a release of mailet 2.3
> 4/ get the commit mails directed to the mailet-api list
> 
> 
> d.

Re: Mailet sub-project is alive :-)

[Danny Angus <da...@apache.org>]

On 5/3/07, Stefano Bagnara <ap...@bago.org> wrote:
> I see that you "rejoined" the 2 modules into a single source tree.
>
> Do you plan to release a single jar?

Yes. At least until we make some decisions on this list.

d.

Re: Mailet sub-project is alive :-)

[Stefano Bagnara <ap...@bago.org>]

I see that you "rejoined" the 2 modules into a single source tree.

Do you plan to release a single jar?

Otherwise I would prefer to keep the source trees for the 2 modules
separated. If we plan to publish separate artifacts into maven
repositories it is much more easy/clean if we have separate source tree,
separate module declaration, separate artifactId (separate pom.xml).

Given there are so few files at all I would probably choose to create a
single output artifact (a single JAR) by now.

Stefano

Danny Angus ha scritto:
> Hi,
> 
> I've created the sub-project structure for mailet in /james/mailet/trunk
> 
> Noel has kindly moved the source from server/trunk mailet and
> mailet-api into this.
> (N.B. *not* james/transport/mailets)
> 
> I still have to:
> 
> 1/ create a snapshot jar to fix the broken server/trunk
> 2/ generate the website
> 3/ call a vote and cut a release of mailet 2.3
> 4/ get the commit mails directed to the mailet-api list
> 
> 
> d.
>