From users-return-55945-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org Sat Sep 27 03:20:27 2003 Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 60366 invoked from network); 27 Sep 2003 03:20:27 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 27 Sep 2003 03:20:27 -0000 Received: (qmail 70228 invoked by uid 500); 27 Sep 2003 03:19:56 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 69771 invoked by uid 500); 27 Sep 2003 03:19:52 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 69757 invoked from network); 27 Sep 2003 03:19:51 -0000 Received: from unknown (HELO sati.virbus.de) (145.253.246.81) by daedalus.apache.org with SMTP; 27 Sep 2003 03:19:51 -0000 Received: from sati.virbus.de (localhost [127.0.0.1]) by localhost (SMTP Server) with ESMTP id 8E417166A80 for ; Sat, 27 Sep 2003 05:20:00 +0200 (MEST) Received: from virbus.de (a183069.studnetz.uni-leipzig.de [139.18.183.69]) by sati.virbus.de (SMTP Server) with ESMTP id E9C6C166A73 for ; Sat, 27 Sep 2003 05:19:59 +0200 (MEST) Message-ID: <3F7501DE.90209@virbus.de> Date: Sat, 27 Sep 2003 05:19:58 +0200 From: Joerg Heinicke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: de-de, de, en-gb, en-us, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: Cocoon and eclipse References: <001001c3838b$f6af9220$1601a8c0@D7FH5S0J> <3F7329E9.4060200@leverageweb.com> <3F74D4FA.2040903@virbus.de> <3F74FAA2.3000102@leverageweb.com> In-Reply-To: <3F74FAA2.3000102@leverageweb.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Geoff Howard wrote: > Joerg Heinicke wrote: > >> Geoff Howard wrote: >> >>>> compiler=org.eclipse.jdt.core.JDTCompilerAdapter >>> >>> That's the one. You can also set that property in the project directly. >> >> Hello Geoff, >> >> I have tried both >> >> compiler=org.eclipse.jdt.core.JDTCompilerAdapter >> >> in local.build.properties and >> >> >> > value="org.eclipse.jdt.core.JDTCompilerAdapter"/> >> >> >> in build.xml (as described at >> http://wiki.cocoondev.org/Wiki.jsp?page=LoadInEclipse). >> >> Both don't work: >> >> compile-core: >> >> compile-deprecated: >> [xpatch] BUILD FAILED: java.lang.IllegalArgumentException: No >> attributes are implemented >> >> Don't know what I'm doing wrong. > > > Hmmm. I think that's a different error than if you don't have the > property set at all. There is no difference between having the property set or not. > I have never gotten (or tried very hard) the full > _cocoon_ build running within eclipse. I simply tried it because of this thread. I didn't expect it to work. > I have four or five other > eclipse projects where ant works fine with that property set. I'll dig > in a little more. If you get rid of the property do you get the error > about the compiler (I forget what it says)? As mentioned above. Echoing it immediately before the failure returns the property value 'modern' set in build.properties. > The error you mention above does look familiar and I'm suspicious it has > to do with ant revision level. IIRC eclipse comes with a lower version > than Cocoon and we may need it - possibly for the custom task xpatch > which is mentioned there. Only since Antonio's update to 1.5.4, Eclipse comes with 1.5.3 (at least my 2.1.1). I have changed the classpath for the Ant task to Cocoon's 1.5.4 (which is then also mentioned on the Eclipse console: "Building with Apache Ant version 1.5.4 compiled on August 12 2003") and added D:\cocoon-2.1\tools\anttasks to the classpath for Cocoon's Ant tasks. > Any ant gurus know if there's a difference > between 1.5 (isn't that what eclipse has?) and 1.6 (isn't that what we > use) which could cause that error? We switched back to 1.5.3 some time ago, Antonio updated it to 1.5.4 in the last days. > Sounds like the setXXX() method that > custom tasks expect for attributes on custom tasks is not set for > something. Hmmmm.... > > Geoff Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org