Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <3F770A43.7050006@apache.org>
Date: Sun, 28 Sep 2003 18:20:19 +0200
From: Remy Maucherat <remm@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [PROCRUN] reorganization
References: <000201c385db$22a5f760$7487bfd5@GISDATA.ZG>
In-Reply-To: <000201c385db$22a5f760$7487bfd5@GISDATA.ZG>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Mladen Turk wrote:

> Hi,
> 
> Since the procrun is fairly generic application that might have it's
> usage beyond the Tomcat5 scope, after some consultations with remm, I
> propose the following reorganization:
> 
> 1. All the TC specific code and resources will be moved to
> j-t-c/procrun.
> 2. There will be no build files in the bin neither they will be
> maintained.
> 3. The binaries will be in the j-t-c/procrun/bin so that we can use them
> in the installation build.
> 4. Make the needed callback mechanism to enable the separation.

+1.

> There is another approach; that we make the subfolder 'tomcat' in the
> procrun and keep all the tomcat specific code in there.
> It could have its purpose too, cause it will show how to customize the
> procrun to a specific application look and feel, without the need to
> download from j-t-c.

I see the point, but IMO even examples should be rather generic. Also, 
if thay are production components, they shouldn't be labelled as examples.
The TC branding modifications should be mentioned in the docs, however.

Remy


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