Re: [JBoss-dev] What is up with the library available targets?

2002-09-27 Thread David Jencks

I can't get this to work.  I removed all the * patterns from libraries.ent,
removed all the conditional targets Dain put in, and when I try to use it
in the jmx mini-project I get

BUILD FAILED
jar:file:/usr/java/jboss/jbossmx-only/jboss-mx/tools/lib/buildmagic-tasks.jar!/org/jboss/tools/buildmagic/common.xml:68:
/usr/java/jboss/jbossmx-only/jboss-mx/thirdparty/apache/axis/lib not found.

just as I did with the *.jar patterns.  Any ideas?

thanks
david jencks


On 2002.09.20 16:34:23 -0400 Jason Dillon wrote:
 The only bits that are not lazy are the glob specs... like *.jar, so
 simply listing the jars explicitly will resolve this without needing to
 check for the availability of them.
 
 --jason
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:jboss-
  [EMAIL PROTECTED]] On Behalf Of David Jencks
  Sent: Friday, September 20, 2002 1:15 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] What is up with the library available
 targets?
  
  Juha didn't want all of thirdparty downloaded to build the jmx project
  (outside of jboss).  I wrote something with 2 chunks, roughly jmx-only
 and
  all.  Dain generalized this to only include libraries that actually
 are
  available.
  
  I don't completely understand why this is needed either, but
 apparently
  some part of the classpath definition has to be there when it is
 parsed.
  I
  thought everything was lazily evaluated, but apparently I was wrong.
  
  david jencks
  
  On 2002.09.20 15:56:40 -0400 Jason Dillon wrote:
   Please explain this to me... I don't get why this is needed.
  
   --jason
  
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] What is up with the library available targets?

2002-09-27 Thread Jason Dillon

What does the property and path definition looks like?

--jason


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:jboss-
 [EMAIL PROTECTED]] On Behalf Of David Jencks
 Sent: Friday, September 27, 2002 1:27 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] What is up with the library available
targets?
 
 I can't get this to work.  I removed all the * patterns from
 libraries.ent,
 removed all the conditional targets Dain put in, and when I try to use
it
 in the jmx mini-project I get
 
 BUILD FAILED
 jar:file:/usr/java/jboss/jbossmx-only/jboss-mx/tools/lib/buildmagic-
 tasks.jar!/org/jboss/tools/buildmagic/common.xml:68:
 /usr/java/jboss/jbossmx-only/jboss-mx/thirdparty/apache/axis/lib not
 found.
 
 just as I did with the *.jar patterns.  Any ideas?
 
 thanks
 david jencks
 
 
 On 2002.09.20 16:34:23 -0400 Jason Dillon wrote:
  The only bits that are not lazy are the glob specs... like *.jar, so
  simply listing the jars explicitly will resolve this without needing
to
  check for the availability of them.
 
  --jason
 
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:jboss-
   [EMAIL PROTECTED]] On Behalf Of David Jencks
   Sent: Friday, September 20, 2002 1:15 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [JBoss-dev] What is up with the library available
  targets?
  
   Juha didn't want all of thirdparty downloaded to build the jmx
project
   (outside of jboss).  I wrote something with 2 chunks, roughly
jmx-only
  and
   all.  Dain generalized this to only include libraries that
actually
  are
   available.
  
   I don't completely understand why this is needed either, but
  apparently
   some part of the classpath definition has to be there when it is
  parsed.
   I
   thought everything was lazily evaluated, but apparently I was
wrong.
  
   david jencks
  
   On 2002.09.20 15:56:40 -0400 Jason Dillon wrote:
Please explain this to me... I don't get why this is needed.
   
--jason
   
   
   
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
   
   
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] What is up with the library available targets?

2002-09-27 Thread David Jencks

Well, here's the file.

david

On 2002.09.27 18:13:55 -0400 Jason Dillon wrote:
 What does the property and path definition looks like?
 
 --jason
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:jboss-
  [EMAIL PROTECTED]] On Behalf Of David Jencks
  Sent: Friday, September 27, 2002 1:27 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] What is up with the library available
 targets?
  
  I can't get this to work.  I removed all the * patterns from
  libraries.ent,
  removed all the conditional targets Dain put in, and when I try to use
 it
  in the jmx mini-project I get
  
  BUILD FAILED
  jar:file:/usr/java/jboss/jbossmx-only/jboss-mx/tools/lib/buildmagic-
  tasks.jar!/org/jboss/tools/buildmagic/common.xml:68:
  /usr/java/jboss/jbossmx-only/jboss-mx/thirdparty/apache/axis/lib not
  found.
  
  just as I did with the *.jar patterns.  Any ideas?
  
  thanks
  david jencks
  
  
  On 2002.09.20 16:34:23 -0400 Jason Dillon wrote:
   The only bits that are not lazy are the glob specs... like *.jar, so
   simply listing the jars explicitly will resolve this without needing
 to
   check for the availability of them.
  
   --jason
  
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-
[EMAIL PROTECTED]] On Behalf Of David Jencks
Sent: Friday, September 20, 2002 1:15 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] What is up with the library available
   targets?
   
Juha didn't want all of thirdparty downloaded to build the jmx
 project
(outside of jboss).  I wrote something with 2 chunks, roughly
 jmx-only
   and
all.  Dain generalized this to only include libraries that
 actually
   are
available.
   
I don't completely understand why this is needed either, but
   apparently
some part of the classpath definition has to be there when it is
   parsed.
I
thought everything was lazily evaluated, but apparently I was
 wrong.
   
david jencks
   
On 2002.09.20 15:56:40 -0400 Jason Dillon wrote:
 Please explain this to me... I don't get why this is needed.

 --jason



 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development


   
   
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 



libraries.ent
Description: Binary data


RE: [JBoss-dev] What is up with the library available targets?

2002-09-27 Thread Jason Dillon

It is possible that the behavior has changed since ant 1.2.  You might
try using path location=/ instead.  Otherwise I don't know.  I am
working on some ideas for fixing all of this mess right now.  The build
system has grown and now there are a few more projects going on... so I
have bumped up this on my priorities.

--jason


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:jboss-
 [EMAIL PROTECTED]] On Behalf Of David Jencks
 Sent: Friday, September 27, 2002 5:39 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] What is up with the library available
targets?
 
 Well, here's the file.
 
 david
 
 On 2002.09.27 18:13:55 -0400 Jason Dillon wrote:
  What does the property and path definition looks like?
 
  --jason
 
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:jboss-
   [EMAIL PROTECTED]] On Behalf Of David Jencks
   Sent: Friday, September 27, 2002 1:27 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [JBoss-dev] What is up with the library available
  targets?
  
   I can't get this to work.  I removed all the * patterns from
   libraries.ent,
   removed all the conditional targets Dain put in, and when I try to
use
  it
   in the jmx mini-project I get
  
   BUILD FAILED
  
jar:file:/usr/java/jboss/jbossmx-only/jboss-mx/tools/lib/buildmagic-
   tasks.jar!/org/jboss/tools/buildmagic/common.xml:68:
   /usr/java/jboss/jbossmx-only/jboss-mx/thirdparty/apache/axis/lib
not
   found.
  
   just as I did with the *.jar patterns.  Any ideas?
  
   thanks
   david jencks
  
  
   On 2002.09.20 16:34:23 -0400 Jason Dillon wrote:
The only bits that are not lazy are the glob specs... like
*.jar, so
simply listing the jars explicitly will resolve this without
needing
  to
check for the availability of them.
   
--jason
   
   
 -Original Message-
 From: [EMAIL PROTECTED]
[mailto:jboss-
 [EMAIL PROTECTED]] On Behalf Of David
Jencks
 Sent: Friday, September 20, 2002 1:15 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] What is up with the library available
targets?

 Juha didn't want all of thirdparty downloaded to build the jmx
  project
 (outside of jboss).  I wrote something with 2 chunks, roughly
  jmx-only
and
 all.  Dain generalized this to only include libraries that
  actually
are
 available.

 I don't completely understand why this is needed either, but
apparently
 some part of the classpath definition has to be there when it
is
parsed.
 I
 thought everything was lazily evaluated, but apparently I was
  wrong.

 david jencks

 On 2002.09.20 15:56:40 -0400 Jason Dillon wrote:
  Please explain this to me... I don't get why this is needed.
 
  --jason
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
 
https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
   
   
   
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
   
   
  
  
   ---
   This sf.net email is sponsored by:ThinkGeek
   Welcome to geek heaven.
   http://thinkgeek.com/sf
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] What is up with the library available targets?

2002-09-20 Thread David Jencks

Juha didn't want all of thirdparty downloaded to build the jmx project
(outside of jboss).  I wrote something with 2 chunks, roughly jmx-only and
all.  Dain generalized this to only include libraries that actually are
available.

I don't completely understand why this is needed either, but apparently
some part of the classpath definition has to be there when it is parsed.  I
thought everything was lazily evaluated, but apparently I was wrong.

david jencks

On 2002.09.20 15:56:40 -0400 Jason Dillon wrote:
 Please explain this to me... I don't get why this is needed.
 
 --jason
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] What is up with the library available targets?

2002-09-20 Thread Jason Dillon

The only bits that are not lazy are the glob specs... like *.jar, so
simply listing the jars explicitly will resolve this without needing to
check for the availability of them.

--jason


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:jboss-
 [EMAIL PROTECTED]] On Behalf Of David Jencks
 Sent: Friday, September 20, 2002 1:15 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] What is up with the library available
targets?
 
 Juha didn't want all of thirdparty downloaded to build the jmx project
 (outside of jboss).  I wrote something with 2 chunks, roughly jmx-only
and
 all.  Dain generalized this to only include libraries that actually
are
 available.
 
 I don't completely understand why this is needed either, but
apparently
 some part of the classpath definition has to be there when it is
parsed.
 I
 thought everything was lazily evaluated, but apparently I was wrong.
 
 david jencks
 
 On 2002.09.20 15:56:40 -0400 Jason Dillon wrote:
  Please explain this to me... I don't get why this is needed.
 
  --jason
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] What is up with the library available targets?

2002-09-20 Thread Dain Sundstrom

I did not know that.

Do we care about all the library available tasks?  The take no time, but 
print a lot of stuff during build.

If we do care, do you want to make the change Jason?  Otherwise, I can.

-dain

Jason Dillon wrote:
 The only bits that are not lazy are the glob specs... like *.jar, so
 simply listing the jars explicitly will resolve this without needing to
 check for the availability of them.
 
 --jason
 
 
 
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-
[EMAIL PROTECTED]] On Behalf Of David Jencks
Sent: Friday, September 20, 2002 1:15 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] What is up with the library available
 
 targets?
 
Juha didn't want all of thirdparty downloaded to build the jmx project
(outside of jboss).  I wrote something with 2 chunks, roughly jmx-only
 
 and
 
all.  Dain generalized this to only include libraries that actually
 
 are
 
available.

I don't completely understand why this is needed either, but
 
 apparently
 
some part of the classpath definition has to be there when it is
 
 parsed.
 
I
thought everything was lazily evaluated, but apparently I was wrong.

david jencks

On 2002.09.20 15:56:40 -0400 Jason Dillon wrote:

Please explain this to me... I don't get why this is needed.

--jason



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development


-- 

Dain Sundstrom
Chief Architect JBossCMP
JBoss Group, LLC




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development