You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2003/06/24 05:07:32 UTC

NOTICE: *IMPORTANT* CVS MODULES ARE MOVING

Folks,

This is a notice to let you know that the James CVS modules will be
changing.

The current jakarta-james module will become james-server.  Initially,
everything will be in there, but we're going to separate out the web-site
into a new module (probably james-site), and eventually other modules, e.g.,
james-mailet.

Once the change has been made, you can edit cvs/Repository, and change it to
read james-server instead of jakarta-james.

	--- Noel


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


Re: NOTICE: *IMPORTANT* CVS MODULES ARE MOVING

Posted by Stephen McConnell <mc...@apache.org>.

Noel J. Bergman wrote:

>Stephen,
>
>We've been talking about it for quite some time.  This is just an opportune
>point to do it.
>
>  
>
>>Personally I would really love to see a breakout of the different
>>components in James as seperate subprojects (i.e. going beyond
>>james/mailet separation and into the seperation of the basic building
>>blocks - smtp, dns, remote, pop3, nntp, etc.
>>    
>>
>
>I don't believe that is going to happen.  We do not need a CVS module per
>service, IMO.
>

Actually I wasn't thinking about seperate cvs repos - instead I was 
thinking more along the lines of seperating component builds as 
sub-projects within the james module.  I've been doing a lot of playing 
around with James in the past few days (linked to the cornerstone 
component builds) - and I've got to the point where the individaul 
components are just plugged together.  It would be really nice to be 
able to do the same thing with the assorted James components. 

In fact I'll probably be posting a detailed email on this sometime soon 
because I preparing a writup on James as a composite component example 
and there are a few questions I have concerning dynamic usage of the 
mailet services (but that's for later).

>>Is this a good time to be thinking about migration to Maven as well?
>>    
>>
>
>One step at a time, but yes.  Didn't you see my comment in dev@avalon asking
>if we could borrow Leo?  :-)  
>

Yep :-)

>Also, Dion Gillard had done some work on it,
>but he felt a bit stymied, IIRC, by the lack of a proper Avalon release.  As
>you know, that's changing.
>

Sure is - excalibur releases are complete, the cornerstone candidates 
are in place, and its all been tested (James HEAD + cornerstone 
candidates + excalibur releases + framework 4.1.4 or 4.1.5-dev).  The 
cornerstone suite is ready to incorporate into a maven build and all of 
the required resources are available under the ibiblio server (with the 
exception of mail_1_3.jar and activation.jar).

Cheers, Steve.

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




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


RE: NOTICE: *IMPORTANT* CVS MODULES ARE MOVING

Posted by "Noel J. Bergman" <no...@devtech.com>.
Stephen,

We've been talking about it for quite some time.  This is just an opportune
point to do it.

> Personally I would really love to see a breakout of the different
> components in James as seperate subprojects (i.e. going beyond
> james/mailet separation and into the seperation of the basic building
> blocks - smtp, dns, remote, pop3, nntp, etc.

I don't believe that is going to happen.  We do not need a CVS module per
service, IMO.

> Is this a good time to be thinking about migration to Maven as well?

One step at a time, but yes.  Didn't you see my comment in dev@avalon asking
if we could borrow Leo?  :-)  Also, Dion Gillard had done some work on it,
but he felt a bit stymied, IIRC, by the lack of a proper Avalon release.  As
you know, that's changing.

	--- Noel


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


Re: NOTICE: *IMPORTANT* CVS MODULES ARE MOVING

Posted by Stephen McConnell <mc...@apache.org>.
Noel:

Suprise, surprise - I was thinking about the very same thing just 
yesterday.  Personally I would really love to see a breakout of the 
different components in James as seperate subprojects (i.e. going beyond 
james/mailet separation and into the seperation of the basic building 
blocks - smtp, dns, remote, pop3, nntp, etc.

Is this a good time to be thinking about migration to Maven as well?

Steve.


Noel J. Bergman wrote:

>Folks,
>
>This is a notice to let you know that the James CVS modules will be
>changing.
>
>The current jakarta-james module will become james-server.  Initially,
>everything will be in there, but we're going to separate out the web-site
>into a new module (probably james-site), and eventually other modules, e.g.,
>james-mailet.
>
>Once the change has been made, you can edit cvs/Repository, and change it to
>read james-server instead of jakarta-james.
>
>	--- Noel
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: james-dev-help@jakarta.apache.org
>
>
>
>  
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




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