Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 17871 invoked by uid 500); 28 Oct 2002 15:51:07 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 17859 invoked from network); 28 Oct 2002 15:51:06 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Torsten Curdt Organization: dff internet & medien To: cocoon-dev@xml.apache.org Subject: Re: scratchpad blocks Date: Mon, 28 Oct 2002 16:53:26 +0100 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200210281653.26877.tcurdt@dff.st> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Monday 28 October 2002 16:41, Morrison, John wrote: > > From: Torsten Curdt [mailto:tcurdt@dff.st] > > > > What about having blocks inside the scratchpad? I just wanted > > to package the > > precept stuff but it should not go into the maintrunk. so... > > > > I think scratchpad blocks would unify the pattern of creating > > new stuff... it > > also would be a piece of cake to move things out of the > > scratchpad then. > > > > On the other hand we could also just create blocks and mark > > them appropriatly > > and exclude them from the standard build. > > > > So we could: > > > > 1) leave everything like it is :-( > > 2) have another blocks directory under scratchpad > > 3) have a single blocks directory and mark and exclude > > scratchpad stuff > > > > What do you guys think? > > How/where would you mark them as such? AFAIU in the properties file: and we could also introduce an attribute marking it as unstable/scratchpa= d -=20 whatever. this could give a warning on build then... -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org