Return-Path: 
 <users-return-55950-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 78722 invoked from network); 27 Sep 2003 11:43:21 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 27 Sep 2003 11:43:21 -0000
Received: (qmail 28795 invoked by uid 500); 27 Sep 2003 11:43:09 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 28759 invoked by uid 500); 27 Sep 2003 11:43:08 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
list-post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 28740 invoked from network); 27 Sep 2003 11:43:08 -0000
Received: from unknown (HELO host.leverageweb.com) (64.91.232.157)
  by daedalus.apache.org with SMTP; 27 Sep 2003 11:43:08 -0000
Received: from va-leesburg-cmts5c-90.chvlva.adelphia.net ([67.21.159.90]
 helo=leverageweb.com)
	by host.leverageweb.com with asmtp (Exim 3.36 #1)
	id 1A3DR5-0006V2-00
	for users@cocoon.apache.org; Sat, 27 Sep 2003 07:40:27 -0400
Message-ID: <3F757856.3000004@leverageweb.com>
Date: Sat, 27 Sep 2003 07:45:26 -0400
From: Geoff Howard <cocoon@leverageweb.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: 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> <3F7501DE.90209@virbus.de>
In-Reply-To: <3F7501DE.90209@virbus.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.leverageweb.com
X-AntiAbuse: Original Domain - cocoon.apache.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - leverageweb.com
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

Joerg Heinicke wrote:

> 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.
>>>
>>> I have tried both
>>>
>>> compiler=org.eclipse.jdt.core.JDTCompilerAdapter
>>> in local.build.properties and
>>>
>>> <target name="properties" if="eclipse.running">
>>>   <property name="build.compiler" 
>>> value="org.eclipse.jdt.core.JDTCompilerAdapter"/>
>>> </target>

...

>>> 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.

Ok, I've just confirmed -- if you get rid of both of those properties 
(at least on my version of eclipse which is using 1.5.2) you do get a 
different error about the compiler version.

>> 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.

:P

>> 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.

I get the expected org.eclipse.jdt.core.JDTCompilerAdapter at least when 
setting it in the ant properties screen in eclipse.

>> 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.

Ok, I stand corrected but...

I now think this has to do with the endorsed dir or is at least limited 
to the xpatch task itself.  If you comment out the xpatch command in 
compile-deprecated things sail along swimmingly until the end when the 
next call to xpatch happens.  Even all the xsl transforms for the blocks 
build seem to work, though I didn't do build clean first.  I tried 
setting another property in the ant dialog for java.endorsed.dirs but 
that had no effect.

Anyone have an idea?  How can I modify the xpatch code to spit out debug 
info about what version of the xml endorsed dirs it gets?

Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org