[ 
https://issues.apache.org/jira/browse/JAMES-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058027#comment-13058027
 ] 

Norman Maurer edited comment on JAMES-1286 at 6/30/11 7:35 PM:
---------------------------------------------------------------

This was also one of my concerns. And I'm still not 100% sure its a good idea 
but as robert wanted to work on it I thought that maybe I missed something and 
just planned to review it once something was done..

      was (Author: norman):
    This was also one of my concerns. And I'm still not 100% sure its a good 
idea but as robert wanted to work I it I thought that I maybe missed something 
and just planned to review it once something was done..
  
> Factor Out Application Assembly
> -------------------------------
>
>                 Key: JAMES-1286
>                 URL: https://issues.apache.org/jira/browse/JAMES-1286
>             Project: JAMES Server
>          Issue Type: Task
>          Components: Build System
>    Affects Versions: 3.0-beta1
>            Reporter: Robert Burrell Donkin
>            Assignee: Robert Burrell Donkin
>            Priority: Blocker
>
> Assembling the final james application from the server components from which 
> it is composed. Integrating these builds necessitates that application and 
> server components are released together. Until maintenance of license and 
> notice information can be automated, this creates a bottleneck and any 
> problem with either server components or application assembly stops both 
> releases. Application assembly is logical downstream of the server component 
> build. This bottleneck can be eliminated by releasing the server components 
> first and then the assembled application. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to