Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 35375 invoked from network); 7 Mar 2002 12:38:50 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 Mar 2002 12:38:50 -0000 Received: (qmail 11022 invoked by uid 97); 7 Mar 2002 12:38:46 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 11002 invoked by uid 97); 7 Mar 2002 12:38:45 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 10991 invoked from network); 7 Mar 2002 12:38:45 -0000 Message-ID: <006701c1c5d5$0227e740$6601a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Developers List" References: <20020307121629.65483.qmail@web10808.mail.yahoo.com> Subject: Re: jspc and magic compiler attribute Date: Thu, 7 Mar 2002 07:38:38 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Jose Alberto Fernandez" > --- Erik Hatcher > wrote: > +1 on removing the magic property and making > it a > > attribute. > > > > The main reason the javac magic property exists is > > so that you don't have to > > specify the compiler for every , right? Its > > unlikely that someone > > would have a whole lot of tasks in their > > build file so it shouldn't > > be too big of an issue, and besides, they can always > > do > > compiler="${jspc.compiler}". > > > > So, how do I write a buildfile that can deploy JSPs in > weblogic or websphere or jboss etc etc without needing > to change the buildfile? Your question is not at all clear that you are referring to . "Deploying" JSP's would work no matter which container you're going to and is container-specific (and painful for some containers - WebSphere, for example - unless someone has some tricks that they'd like to share for it!). But if you're talking about using a different JSP compiler, why does the magic property make any difference? Then compiler="${jspc.compiler}" (which would be in jspc-websphere.properties, jspc-weblogic.properties.....). Just set "container" to your desired one. > Magic-properties are the equivalent in ANT to > environment variables. They are usefull when the you > want different users to execute the same buildfile in > different execution environements. Huh? I don't quite see the dilemma here. Magic properties are something I thought we were shying away from if at all possible. They are confusing and not well documented. And would the technique I showed above not cover the different execution environments you speak of? > Just with OS environemnet variables, what we need is a > more consistent naming convension and to spell them > out clearly in the documentation (xdoclet hint hint). Yes, this is a good suggestion for XDoclet, thanks! Erik -- To unsubscribe, e-mail: For additional commands, e-mail: