Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <462876D9.7020200@apache.org>
Date: Fri, 20 Apr 2007 10:16:25 +0200
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Cocoon Maven plugin - Merging deployer & rcl
References: <4624EA31.3070709@outerthought.org> <f05k4h$5oe$1@sea.gmane.org>
 <46273441.9030907@outerthought.org> <f08m7c$d25$1@sea.gmane.org>
 <46286141.3090002@apache.org>
In-Reply-To: <46286141.3090002@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Giacomo Pati wrote:
> BTW: Can we have a released deployer plugin as well.

I think that Cocoon should only have one Maven plugin with as many goals as 
needed. Hence I propose that we merge the deployer and the reloading classloader 
plugin into a single one:

  cocoon:deploy ..... provides shielding and *.xpatch support for "war"
                      proejcts
  cocoon:rcl ........ provides a minimal web environment for blocks
                      ("jar") amd complete reloading of all resources
                      (Cocoon resources, Java files, Spring context)

I'm sure that other goals will follow in the future (scaffolding, upgrade 
support, etc.).

WDYT?

-- 
Reinhard P�tz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------