ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <gudnabr...@yahoo.com>
Subject Re: Reference access from imported build file (ant 1.6.2)
Date Thu, 22 Jul 2004 17:26:40 GMT
That does look suspect.  A workaround might be to use
a <pathconvert> in the imported file so that you can
pass a single path property or reference to <ant>.

-Matt

--- Doug Lochart <dlochart@capecomputing.com> wrote:
> Matt,
> 
> I was able to get around the problem for now but I
> will try and recreate my
> structure in a smaller set of build files.  But
> before I submit a bug
> repoirt I wanted to run this by you.  Given the same
> situation I mentioned
> before ... the imported build file target that uses
> the reference performs
> an <ant> call on another build file (I haven't been
> able to migrate
> everything to an import strategy yet).  In the ant
> call I explicitly pass
> the reference like this:
> 
> <ant target="generate-source-documentation"
> antfile="${some-build-file}">
>   <reference refid="build.main.classpath"
> torefid="build.classpath"/>
>   ... etc
> </ant>
> 
> I do not set inherit references to true.  My
> question is thus:  If a
> reference is made up of one or more other references
> and you are passing the
> composite reference in an <ant> call do you need to
> make explicitly list the
> other references in the composite reference
> additionally in the call.  This
> is the work-around I used to get my build to work
> for the time being.
> Before I submit a bug report I wanted to make sure
> what the proper semantics
> were for composite reference passing in <ant> calls.
> 
> Thanks a bunch
> 
> Doug
> 
> 
> Now I've gained some understanding
> Of the only world that we see.
> Things that I once dreamed of
> Have become reality.
> 
> These walls that still surround me
> Still contain the same old me,
> Just one more who's searching for
> A world that ought to be.
> ----- Original Message ----- 
> From: "Matt Benson" <gudnabrsam@yahoo.com>
> To: "Ant Users List" <user@ant.apache.org>
> Sent: Thursday, July 22, 2004 12:33 PM
> Subject: Re: Reference access from imported build
> file (ant 1.6.2)
> 
> 
> > Doug:  I have tried, unsuccessfully, to reproduce
> your
> > problem.  If you can get a pair of small
> buildfiles
> > together that demonstrate this behavior, open a
> > Bugzilla report and attach them.
> >
> > Thanks,
> > Matt
> >
> >
> > --- Doug Lochart <dlochart@capecomputing.com>
> wrote:
> > > Hello all,
> > >
> > > I am currently upgrading to ant1.6.2 and I have
> run
> > > into a situation that works in 1.6.1 but not in
> > > 1.6.2.  Hopefully someone can explain to me what
> is
> > > going on and if its a bug or a change that I
> need to
> > > accomodate for.
> > >
> > > In my base build.xml I define a path like so:
> > >
> > > <path id="build.interface.classpath">
> > >   < ... simple pathelements .../>
> > > </path>
> > >
> > > Then I define another one like this:
> > >
> > > <path id="build.main.classpath">
> > >   <path refid="build.interface.classpath"/>
> > >   <pathelement .../>
> > > </path>
> > >
> > > Then I import a common build file
> > >
> > > <import
> > > file="${common.build.home}/common-imports.xml"/>
> > >
> > > < more targets follow >
> > >
> > > There is a javadoc task in the imported build
> file
> > > that uses the "build.main.classpath" reference
> when
> > > calling other targets and tasks.
> > > In 1.6.1 this works fine.  In 1.6.2 I get an
> > > exception saying that "Reference
> > > build.interface.classpath not found".  I
> commented
> > > out the line under the "build.main.classpath"
> > > definition that includes reference to
> > > "build.interface.classpath" and the call worked
> > > (well it did not get hung up on any references
> > > missing).
> > >
> > > Can anyone tell me what is occurring now and if
> this
> > > is a bug or not.
> > >
> > > Thanks
> > >
> > > Doug
> > >
> > > Now I've gained some understanding
> > > Of the only world that we see.
> > > Things that I once dreamed of
> > > Have become reality.
> > >
> > > These walls that still surround me
> > > Still contain the same old me,
> > > Just one more who's searching for
> > > A world that ought to be.
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Vote for the stars of Yahoo!'s next ad campaign!
> >
>
http://advision.webevents.yahoo.com/yahoo/votelifeengine/
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> user-unsubscribe@ant.apache.org
> > For additional commands, e-mail:
> user-help@ant.apache.org
> >
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> user-unsubscribe@ant.apache.org
> For additional commands, e-mail:
> user-help@ant.apache.org
> 
> 



	
		
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message