You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Shorn Tolley <sh...@hotmail.com> on 2002/06/02 02:13:04 UTC
Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem with 'available' task for RegExp jar
Hi folks,
I am trying to build the Ant source code for 1.4.1.
(as an aside, are there any FAQs or anything I should be reading as a first
time Ant builder?)
I am able to build Ant 1.4.1 from the command line using a binary download
of Ant 1.4.1.
When I try to build Ant from within NetBeans (using the Ant project
build.xml file), the compile fails because the script tries to build the
org.apache.tools.ant.util.regexp.JakartaRegexpMatcher.java file.
This does not happen from the command line because I haven't got the
regexp.jar in my classpath or anywhere else for that matter. Which means
the 'available' task in the 'check_for_optional_packages' target doesn't set
the 'jakarta.regexp.present' property, which means the JakartaRegexpMatcher
class gets excluded from the build.
Unfortunately, when building from within NetBeans, the available task seems
to find the RE regexp class, which means it then sets the
'jakarta.regexp.present' property, which eventually causes the build to
fail. I /think/ the RE class is being picked up from the NetBeans
classpath. (regexp.jar /is/ in the 'netbeans.class.path').
I have gotten the build to work from within NetBeans by commenting out the
available task that sets the 'jakarta.regexp.present' property, but I was
wondering if anyone else is building Ant from NetBeans and have seen this
problem?
Platform:
Windows XP
JDK 1.3.1 (although netbeans is running on 1.4)
Ant 1.4.1 source code
NetBeans 3.3.1
Using Jikes as well (but it happens with ordinary javac too)
Thanks,
Shorn.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem with 'available' task for RegExp jar
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
I don't know what others are doing, but I only build Ant from the
command-line. There are too many moving pieces when tossing an IDE in the
middle. Sounds like you have that in your classpath through NetBeans
somehow - and whether you can disable that I don't know.
I bootstrap and then run the build, all through the scripts (bootstrap.bat
and build.bat, in my case).
Erik
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 8:13 PM
Subject: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem
with 'available' task for RegExp jar
> Hi folks,
>
> I am trying to build the Ant source code for 1.4.1.
> (as an aside, are there any FAQs or anything I should be reading as a
first
> time Ant builder?)
>
> I am able to build Ant 1.4.1 from the command line using a binary download
> of Ant 1.4.1.
>
> When I try to build Ant from within NetBeans (using the Ant project
> build.xml file), the compile fails because the script tries to build the
> org.apache.tools.ant.util.regexp.JakartaRegexpMatcher.java file.
>
> This does not happen from the command line because I haven't got the
> regexp.jar in my classpath or anywhere else for that matter. Which means
> the 'available' task in the 'check_for_optional_packages' target doesn't
set
> the 'jakarta.regexp.present' property, which means the
JakartaRegexpMatcher
> class gets excluded from the build.
>
> Unfortunately, when building from within NetBeans, the available task
seems
> to find the RE regexp class, which means it then sets the
> 'jakarta.regexp.present' property, which eventually causes the build to
> fail. I /think/ the RE class is being picked up from the NetBeans
> classpath. (regexp.jar /is/ in the 'netbeans.class.path').
>
> I have gotten the build to work from within NetBeans by commenting out the
> available task that sets the 'jakarta.regexp.present' property, but I was
> wondering if anyone else is building Ant from NetBeans and have seen this
> problem?
>
> Platform:
> Windows XP
> JDK 1.3.1 (although netbeans is running on 1.4)
> Ant 1.4.1 source code
> NetBeans 3.3.1
> Using Jikes as well (but it happens with ordinary javac too)
>
> Thanks,
> Shorn.
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I debug what's in a path?
Posted by Peter Donald <pe...@apache.org>.
Hi,
This is what you want
<path id="test.classpath"/>
<property name="X" refid="test.classpath"/>
<echo message="test.classpath=${test.classpath}"/>
On Mon, 3 Jun 2002 00:12, Shorn Tolley wrote:
> Hi,
>
> I'm trying to track down a build problem I'm having when building Ant from
> within NetBeans (I actually have it working via two different workarounds
> now, but I want to solve the problem).
> The problem appears to be NetBeans, not Ant or the Ant build file.
>
> I have a minimal project that works on the command line and doesn't work in
> NetBeans that I'm going to use to show the NB community what's going wrong.
>
> What I was wondering is: is there any way I can debug a path element?
> I want to print out to the console eveything that's in a particular
> classpath.
> (This will make it easier to show explicitly whats going wrong)
>
> The path element I want to debug (just like in the Ant build file) is
> declared:
> <path id="test.classpath">
> </path>
>
> What I'd like to do is something like:
> <echopath pathref="test.classpath"/>
>
> And that would print out all the elements of the classpath.
> Does anyone know of anyway I can do something like this with Ant 1.4.1?
>
> Thanks,
> Shorn.
--
Cheers,
Peter Donald
--------------------------------------------------
"An intellectual is someone who has been educated
beyond their intelligence."
--------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I debug what's in a path?
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
<property name="classpath.string" refid="test.classpath"/>
<echo>classpath = ${classpath.string}</echo>
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Sunday, June 02, 2002 10:12 AM
Subject: How do I debug what's in a path?
> Hi,
>
> I'm trying to track down a build problem I'm having when building Ant from
> within NetBeans (I actually have it working via two different workarounds
> now, but I want to solve the problem).
> The problem appears to be NetBeans, not Ant or the Ant build file.
>
> I have a minimal project that works on the command line and doesn't work
in
> NetBeans that I'm going to use to show the NB community what's going
wrong.
>
> What I was wondering is: is there any way I can debug a path element?
> I want to print out to the console eveything that's in a particular
> classpath.
> (This will make it easier to show explicitly whats going wrong)
>
> The path element I want to debug (just like in the Ant build file) is
> declared:
> <path id="test.classpath">
> </path>
>
> What I'd like to do is something like:
> <echopath pathref="test.classpath"/>
>
> And that would print out all the elements of the classpath.
> Does anyone know of anyway I can do something like this with Ant 1.4.1?
>
> Thanks,
> Shorn.
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I debug what's in a path?
Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
Shorn Tolley wrote:
> Hi,
>
> What I'd like to do is something like:
> <echopath pathref="test.classpath"/>
>
<property name="fubar" refid="test.classpath/>
<echo message="test.classpath is ${fubar}"/>
I think that should do what you want (although I wasn't sure if you wanted
to know what was on the path, which this won't do).
Conor
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
How do I debug what's in a path?
Posted by Shorn Tolley <sh...@hotmail.com>.
Hi,
I'm trying to track down a build problem I'm having when building Ant from
within NetBeans (I actually have it working via two different workarounds
now, but I want to solve the problem).
The problem appears to be NetBeans, not Ant or the Ant build file.
I have a minimal project that works on the command line and doesn't work in
NetBeans that I'm going to use to show the NB community what's going wrong.
What I was wondering is: is there any way I can debug a path element?
I want to print out to the console eveything that's in a particular
classpath.
(This will make it easier to show explicitly whats going wrong)
The path element I want to debug (just like in the Ant build file) is
declared:
<path id="test.classpath">
</path>
What I'd like to do is something like:
<echopath pathref="test.classpath"/>
And that would print out all the elements of the classpath.
Does anyone know of anyway I can do something like this with Ant 1.4.1?
Thanks,
Shorn.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem with 'available' task for RegExp jar
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 5:13 PM
Subject: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem
with 'available' task for RegExp jar
>
> I have gotten the build to work from within NetBeans by commenting out the
> available task that sets the 'jakarta.regexp.present' property, but I was
> wondering if anyone else is building Ant from NetBeans and have seen this
> problem?
>
> Platform:
> Windows XP
> JDK 1.3.1 (although netbeans is running on 1.4)
> Ant 1.4.1 source code
> NetBeans 3.3.1
> Using Jikes as well (but it happens with ordinary javac too)
>
we fixed some problems with JDK1.4 on XP in ant1.5; if your build crashes in
<property env>, that is why. Dunno about why it wont build, maybe the
netbeans regexp isnt complete. Actually, on a jdk1.4 build it should pick up
the java1.4 regexp set too.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>