Home » Eclipse Projects » Eclipse Platform » ANT Builder and imported files
| ANT Builder and imported files [message #265213] |
Tue, 03 August 2004 07:25  |
Eclipse User |
|
|
|
Originally posted by: dcorbin.machturtle.com
The Ant editor/builder seems to create errors if I open a "fragment" of a
build file, such as one that might be imported into the main file (even if
the fragment is OK other than not being a full file).
Worse, once those errors show up in the Problems view, I can find no way to
get rid of them. Is there some way that I've missed?
David Corbin
|
|
| | | | | |
| Re: ANT Builder properties undefined during import [message #268465 is a reply to message #268428] |
Tue, 24 August 2004 13:57  |
| Eclipse User |
|
|
|
Thanks for the confidence to continue in the face of failure. I was able
to get a few things working and a few other things still seem to be
broken as originally reported.
Setting the Window->Preferences->Ant->Runtime->Properties value for
${VARIABLE} did seem to allow the Ant Build to _run_ correctly. Choosing
the Outline->"project name"->Run->Ant Build automatically built and ran
an external tools "Ant Build" configuration (nice!) and ran successfully.
However, the Ant build file editor and external tools configuration
editor still think that my buildfile is in error.
* The Ant build file editor does not locate the imported file and
appears to not use the defined property the same way the runtime did.
* The external tools editor won't let me run the build file from there
because it says one of my custom tasks is undefined. It is defined at
runtime. The problem just seems to be at editing time.
I think I may be able to resolve the second problem by hand registering
the tasks within Eclipse; even though this is a pain since my included
build files encapsulate this. However, I have less confidence in getting
the Ant build file editor to expand the ${VARIABLE} reference during the
import outside of runtime.
Darin Swanson wrote:
> It should work setting the property in
>
>>* setting the variable in Window->Preferences->Ant->Runtime->Properties
>
> and I can get a successful build with this setup but the property appears to
> not be applied when parsing so this result in errors in the editor.
>
> To specify "-DINCLUDES=c:/tmp/bar"
> go to the Main tab of your Ant launch configuration and place this argument
> in the Arguments pane.
> I had success using this for a successful build as well.
>
> For the errors in the Ant Editor, I have logged
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
>
> Thanks
> Darins
>
> "Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> news:cgfjp3$j2d$1@eclipse.org...
>
>>I am using the import in a similar way as the original post, except that
>>I am using a ${VARIABLE} reference to locate the imported file. Things
>>work correctly when using Ant stand-alone. However, within Eclipse, I
>>cannot locate a way to tell it how to resolve the variable. It fails in
>>both the Ant editor and the External Tools.
>>
>>I've tried:
>>* setting the variable in Window->Preferences->Ant->Runtime->Properties
>>* setting the variable in my external environment
>>
>>The following is a simple example of what I am doing. The build.xml file
>>is in a separate directory from the included file. When I edit this
>>within Eclipse it acts like the first runtime case where ${INCLUDES} was
>>not defined. I am looking for a way within Eclipse to get ${INCLUDES}
>>defined so it understands what is happening like in the last execution
>>below in the stand-alone case.
>>
>>$ pwd
>>/cygdrive/c/tmp
>>
>>$ more foo/build.xml bar/included.xml
>>::::::::::::::
>>foo/build.xml
>>::::::::::::::
>><project name="main" default="all">
>> <import file="${INCLUDES}/included.xml"/>
>></project>
>>::::::::::::::
>>bar/included.xml
>>::::::::::::::
>><project name="included">
>> <target name="all">
>> <echo>Hello World</echo>
>> </target>
>></project>
>>
>>$ ant -f foo/build.xml ### This fails as expected ###
>>Buildfile: foo\build.xml
>>
>>BUILD FAILED
>>C:\tmp\foo\build.xml:2: Cannot find ${INCLUDES}/included.xml imported
>>from C:\tmp\foo\build.xml
>>
>>Total time: 0 seconds
>>
>>$ ant -f foo/build.xml -DINCLUDES=c:/tmp/bar ### How do I get
>>
>> ### Eclipse/Ant
>> ### to work like this?
>>Buildfile: foo\build.xml
>>
>>all:
>> [echo] Hello World
>>
>>BUILD SUCCESSFUL
>>Total time: 0 seconds
>>
>>
>>
>>Darin Swanson wrote:
>>
>>>Thanks for reporting back.
>>>I was not expecting people to use <import> buildfiles that way but why
>
> not
>
>>>:-)
>>>So I have entered https://bugs.eclipse.org/bugs/show_bug.cgi?id=71347
>>>so we can track an enhancement to match how you work
>>>
>>>Thanks
>>>Darins
>>>
>>>"David Corbin" <dcorbin@machturtle.com> wrote in message
>>>news:cepaus$i4e$1@eclipse.org...
>>>
>>>
>>>>>In the final 3.0 if a fragment does not contain a top level project
>>>>>element it will not have problems added to the problems view.
>>>>>
>>>>
>>>>Although I didn't think it had a top level project, it does have one
>>>>(without the normal requried attributes).
>>>>
>>>>
>>>>
>>>>>Now are you using <import> or using the entity includes for adding the
>>>>>fragments in your buildfile?
>>>>
>>>>Definatley <import>.
>>>>
>>>>
>>>>
>>>>>Of course with the <import> these need to be full fledged build files
>
> so
>
>>>>>is that what is causing you the trouble?
>>>>
>>>>Probably. I suppose I can add the project attributes to the imported
>>>
>>>file,
>>>
>>>
>>>>even though it's not designed to be used directly.
>>>>
>>>>
>>>>
>>>>>What is an example of a problem you are getting?
>>>>>
>>>>
>>>>"No default target specified", "Target foo does not exist in this
>>>
>>>project".
>>>
>>>
>>>>"Default target list does not exist in this project".
>>>>
>>>>As mentioned above, the import file is not designed to be used alone.
>
> It
>
>>>>references targets that are supposed to be define by the importing file.
>>>>
>>>>
>>>>
>>>>>HTH
>>>>>Darins
>>>>
>>>>David
>>>>
>>>
>>>
>>>
>
>
|
|
|
| Re: ANT Builder properties undefined during import [message #268467 is a reply to message #268465] |
Tue, 24 August 2004 14:07 |
| Eclipse User |
|
|
|
"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
news:cgfvd2$8cb$1@eclipse.org...
> Thanks for the confidence to continue in the face of failure. I was able
> to get a few things working and a few other things still seem to be
> broken as originally reported.
>
> Setting the Window->Preferences->Ant->Runtime->Properties value for
> ${VARIABLE} did seem to allow the Ant Build to _run_ correctly. Choosing
> the Outline->"project name"->Run->Ant Build automatically built and ran
> an external tools "Ant Build" configuration (nice!) and ran successfully.
>
> However, the Ant build file editor and external tools configuration
> editor still think that my buildfile is in error.
> * The Ant build file editor does not locate the imported file and
> appears to not use the defined property the same way the runtime did.
>
I will work on fixing this up shortly via bug 72512. I do not believe there
is anything you as a user could do to fix this...but I'd be happy if you
proved me wrong :-)
> * The external tools editor won't let me run the build file from there
> because it says one of my custom tasks is undefined. It is defined at
> runtime. The problem just seems to be at editing time.
So your tasks are defined in the imported file?
>
> I think I may be able to resolve the second problem by hand registering
> the tasks within Eclipse; even though this is a pain since my included
> build files encapsulate this. However, I have less confidence in getting
> the Ant build file editor to expand the ${VARIABLE} reference during the
> import outside of runtime.
>
> Darin Swanson wrote:
>
> > It should work setting the property in
> >
> >>* setting the variable in Window->Preferences->Ant->Runtime->Properties
> >
> > and I can get a successful build with this setup but the property
appears to
> > not be applied when parsing so this result in errors in the editor.
> >
> > To specify "-DINCLUDES=c:/tmp/bar"
> > go to the Main tab of your Ant launch configuration and place this
argument
> > in the Arguments pane.
> > I had success using this for a successful build as well.
> >
> > For the errors in the Ant Editor, I have logged
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
> >
> > Thanks
> > Darins
> >
> > "Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> > news:cgfjp3$j2d$1@eclipse.org...
> >
> >>I am using the import in a similar way as the original post, except that
> >>I am using a ${VARIABLE} reference to locate the imported file. Things
> >>work correctly when using Ant stand-alone. However, within Eclipse, I
> >>cannot locate a way to tell it how to resolve the variable. It fails in
> >>both the Ant editor and the External Tools.
> >>
> >>I've tried:
> >>* setting the variable in Window->Preferences->Ant->Runtime->Properties
> >>* setting the variable in my external environment
> >>
> >>The following is a simple example of what I am doing. The build.xml file
> >>is in a separate directory from the included file. When I edit this
> >>within Eclipse it acts like the first runtime case where ${INCLUDES} was
> >>not defined. I am looking for a way within Eclipse to get ${INCLUDES}
> >>defined so it understands what is happening like in the last execution
> >>below in the stand-alone case.
> >>
> >>$ pwd
> >>/cygdrive/c/tmp
> >>
> >>$ more foo/build.xml bar/included.xml
> >>::::::::::::::
> >>foo/build.xml
> >>::::::::::::::
> >><project name="main" default="all">
> >> <import file="${INCLUDES}/included.xml"/>
> >></project>
> >>::::::::::::::
> >>bar/included.xml
> >>::::::::::::::
> >><project name="included">
> >> <target name="all">
> >> <echo>Hello World</echo>
> >> </target>
> >></project>
> >>
> >>$ ant -f foo/build.xml ### This fails as expected ###
> >>Buildfile: foo\build.xml
> >>
> >>BUILD FAILED
> >>C:\tmp\foo\build.xml:2: Cannot find ${INCLUDES}/included.xml imported
> >>from C:\tmp\foo\build.xml
> >>
> >>Total time: 0 seconds
> >>
> >>$ ant -f foo/build.xml -DINCLUDES=c:/tmp/bar ### How do I get
> >>
> >> ### Eclipse/Ant
> >> ### to work like this?
> >>Buildfile: foo\build.xml
> >>
> >>all:
> >> [echo] Hello World
> >>
> >>BUILD SUCCESSFUL
> >>Total time: 0 seconds
> >>
> >>
> >>
> >>Darin Swanson wrote:
> >>
> >>>Thanks for reporting back.
> >>>I was not expecting people to use <import> buildfiles that way but why
> >
> > not
> >
> >>>:-)
> >>>So I have entered https://bugs.eclipse.org/bugs/show_bug.cgi?id=71347
> >>>so we can track an enhancement to match how you work
> >>>
> >>>Thanks
> >>>Darins
> >>>
> >>>"David Corbin" <dcorbin@machturtle.com> wrote in message
> >>>news:cepaus$i4e$1@eclipse.org...
> >>>
> >>>
> >>>>>In the final 3.0 if a fragment does not contain a top level project
> >>>>>element it will not have problems added to the problems view.
> >>>>>
> >>>>
> >>>>Although I didn't think it had a top level project, it does have one
> >>>>(without the normal requried attributes).
> >>>>
> >>>>
> >>>>
> >>>>>Now are you using <import> or using the entity includes for adding
the
> >>>>>fragments in your buildfile?
> >>>>
> >>>>Definatley <import>.
> >>>>
> >>>>
> >>>>
> >>>>>Of course with the <import> these need to be full fledged build files
> >
> > so
> >
> >>>>>is that what is causing you the trouble?
> >>>>
> >>>>Probably. I suppose I can add the project attributes to the imported
> >>>
> >>>file,
> >>>
> >>>
> >>>>even though it's not designed to be used directly.
> >>>>
> >>>>
> >>>>
> >>>>>What is an example of a problem you are getting?
> >>>>>
> >>>>
> >>>>"No default target specified", "Target foo does not exist in this
> >>>
> >>>project".
> >>>
> >>>
> >>>>"Default target list does not exist in this project".
> >>>>
> >>>>As mentioned above, the import file is not designed to be used alone.
> >
> > It
> >
> >>>>references targets that are supposed to be define by the importing
file.
> >>>>
> >>>>
> >>>>
> >>>>>HTH
> >>>>>Darins
> >>>>
> >>>>David
> >>>>
> >>>
> >>>
> >>>
> >
> >
>
|
|
|
| Re: ANT Builder properties undefined during import [message #268471 is a reply to message #268467] |
Tue, 24 August 2004 14:27 |
| Eclipse User |
|
|
|
Okay, I'll relax on the editor.
Yes. I have custom tasks defined within the imported file. My main
build.xml files are extremely sparse.
<project name="corebuild_properties">
<taskdef resource="net/sf/antcontrib/antcontrib.properties"/>
<osfamily property="osFamily"/>
Any insight as to how I can get Eclipse better configured to recognize
the custom tasks would be appreciated. Right now, I have osfamily
defined under Window->preferences->Ant->Runtime->Tasks, but comes up
undefined on the external tools editor.
Although it does run under the external tools run button and Outline,
I've just started playing with the Ant view where I can seach and
execute various build.xml files. In this view, the executation fails
because osfamiliy could not be instantiated.
Still plugging away...
Darin Swanson wrote:
> "Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> news:cgfvd2$8cb$1@eclipse.org...
>
>>Thanks for the confidence to continue in the face of failure. I was able
>>to get a few things working and a few other things still seem to be
>>broken as originally reported.
>>
>>Setting the Window->Preferences->Ant->Runtime->Properties value for
>>${VARIABLE} did seem to allow the Ant Build to _run_ correctly. Choosing
>>the Outline->"project name"->Run->Ant Build automatically built and ran
>>an external tools "Ant Build" configuration (nice!) and ran successfully.
>>
>>However, the Ant build file editor and external tools configuration
>>editor still think that my buildfile is in error.
>
>
>>* The Ant build file editor does not locate the imported file and
>>appears to not use the defined property the same way the runtime did.
>>
>
>
> I will work on fixing this up shortly via bug 72512. I do not believe there
> is anything you as a user could do to fix this...but I'd be happy if you
> proved me wrong :-)
>
>
>>* The external tools editor won't let me run the build file from there
>>because it says one of my custom tasks is undefined. It is defined at
>>runtime. The problem just seems to be at editing time.
>
>
> So your tasks are defined in the imported file?
>
>
>>I think I may be able to resolve the second problem by hand registering
>>the tasks within Eclipse; even though this is a pain since my included
>>build files encapsulate this. However, I have less confidence in getting
>>the Ant build file editor to expand the ${VARIABLE} reference during the
>>import outside of runtime.
>>
>>Darin Swanson wrote:
>>
>>
>>>It should work setting the property in
>>>
>>>
>>>>* setting the variable in Window->Preferences->Ant->Runtime->Properties
>>>
>>>and I can get a successful build with this setup but the property
>
> appears to
>
>>>not be applied when parsing so this result in errors in the editor.
>>>
>>>To specify "-DINCLUDES=c:/tmp/bar"
>>>go to the Main tab of your Ant launch configuration and place this
>
> argument
>
>>>in the Arguments pane.
>>>I had success using this for a successful build as well.
>>>
>>>For the errors in the Ant Editor, I have logged
>>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
>>>
>>>Thanks
>>>Darins
>>>
>>>"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
>>>news:cgfjp3$j2d$1@eclipse.org...
>>>
>>>
>>>>I am using the import in a similar way as the original post, except that
>>>>I am using a ${VARIABLE} reference to locate the imported file. Things
>>>>work correctly when using Ant stand-alone. However, within Eclipse, I
>>>>cannot locate a way to tell it how to resolve the variable. It fails in
>>>>both the Ant editor and the External Tools.
>>>>
>>>>I've tried:
>>>>* setting the variable in Window->Preferences->Ant->Runtime->Properties
>>>>* setting the variable in my external environment
>>>>
>>>>The following is a simple example of what I am doing. The build.xml file
>>>>is in a separate directory from the included file. When I edit this
>>>>within Eclipse it acts like the first runtime case where ${INCLUDES} was
>>>>not defined. I am looking for a way within Eclipse to get ${INCLUDES}
>>>>defined so it understands what is happening like in the last execution
>>>>below in the stand-alone case.
>>>>
>>>>$ pwd
>>>>/cygdrive/c/tmp
>>>>
>>>>$ more foo/build.xml bar/included.xml
>>>>::::::::::::::
>>>>foo/build.xml
>>>>::::::::::::::
>>>><project name="main" default="all">
>>>> <import file="${INCLUDES}/included.xml"/>
>>>></project>
>>>>::::::::::::::
>>>>bar/included.xml
>>>>::::::::::::::
>>>><project name="included">
>>>> <target name="all">
>>>> <echo>Hello World</echo>
>>>> </target>
>>>></project>
>>>>
>>>>$ ant -f foo/build.xml ### This fails as expected ###
>>>>Buildfile: foo\build.xml
>>>>
>>>>BUILD FAILED
>>>>C:\tmp\foo\build.xml:2: Cannot find ${INCLUDES}/included.xml imported
>>>
>>>>from C:\tmp\foo\build.xml
>>>
>>>>Total time: 0 seconds
>>>>
>>>>$ ant -f foo/build.xml -DINCLUDES=c:/tmp/bar ### How do I get
>>>>
>>>> ### Eclipse/Ant
>>>> ### to work like this?
>>>>Buildfile: foo\build.xml
>>>>
>>>>all:
>>>> [echo] Hello World
>>>>
>>>>BUILD SUCCESSFUL
>>>>Total time: 0 seconds
>>>>
>>>>
>>>>
>>>>Darin Swanson wrote:
>>>>
>>>>
>>>>>Thanks for reporting back.
>>>>>I was not expecting people to use <import> buildfiles that way but why
>>>
>>>not
>>>
>>>
>>>>>:-)
>>>>>So I have entered https://bugs.eclipse.org/bugs/show_bug.cgi?id=71347
>>>>>so we can track an enhancement to match how you work
>>>>>
>>>>>Thanks
>>>>>Darins
>>>>>
>>>>>"David Corbin" <dcorbin@machturtle.com> wrote in message
>>>>>news:cepaus$i4e$1@eclipse.org...
>>>>>
>>>>>
>>>>>
>>>>>>>In the final 3.0 if a fragment does not contain a top level project
>>>>>>>element it will not have problems added to the problems view.
>>>>>>>
>>>>>>
>>>>>>Although I didn't think it had a top level project, it does have one
>>>>>>(without the normal requried attributes).
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Now are you using <import> or using the entity includes for adding
>
> the
>
>>>>>>>fragments in your buildfile?
>>>>>>
>>>>>>Definatley <import>.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Of course with the <import> these need to be full fledged build files
>>>
>>>so
>>>
>>>
>>>>>>>is that what is causing you the trouble?
>>>>>>
>>>>>>Probably. I suppose I can add the project attributes to the imported
>>>>>
>>>>>file,
>>>>>
>>>>>
>>>>>
>>>>>>even though it's not designed to be used directly.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>What is an example of a problem you are getting?
>>>>>>>
>>>>>>
>>>>>>"No default target specified", "Target foo does not exist in this
>>>>>
>>>>>project".
>>>>>
>>>>>
>>>>>
>>>>>>"Default target list does not exist in this project".
>>>>>>
>>>>>>As mentioned above, the import file is not designed to be used alone.
>>>
>>>It
>>>
>>>
>>>>>>references targets that are supposed to be define by the importing
>
> file.
>
>>>>>>
>>>>>>
>>>>>>>HTH
>>>>>>>Darins
>>>>>>
>>>>>>David
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>
>
|
|
|
| Re: ANT Builder properties undefined during import [message #268474 is a reply to message #268471] |
Tue, 24 August 2004 14:31 |
| Eclipse User |
|
|
|
You have hit the same problem as:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=68373
As indicated in that bug report you can turn off the "incomplete classpath"
errors for the editor as another workaround.
If you have the time to add your details to the bug report, that would be
great. If you don't get to it...I will eventually :-)
Thanks for your help in diagnosing the problem
Darins
"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
news:cgg13u$bbj$1@eclipse.org...
> Okay, I'll relax on the editor.
>
> Yes. I have custom tasks defined within the imported file. My main
> build.xml files are extremely sparse.
>
> <project name="corebuild_properties">
> <taskdef resource="net/sf/antcontrib/antcontrib.properties"/>
> <osfamily property="osFamily"/>
>
> Any insight as to how I can get Eclipse better configured to recognize
> the custom tasks would be appreciated. Right now, I have osfamily
> defined under Window->preferences->Ant->Runtime->Tasks, but comes up
> undefined on the external tools editor.
>
> Although it does run under the external tools run button and Outline,
> I've just started playing with the Ant view where I can seach and
> execute various build.xml files. In this view, the executation fails
> because osfamiliy could not be instantiated.
>
> Still plugging away...
>
> Darin Swanson wrote:
>
> > "Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> > news:cgfvd2$8cb$1@eclipse.org...
> >
> >>Thanks for the confidence to continue in the face of failure. I was able
> >>to get a few things working and a few other things still seem to be
> >>broken as originally reported.
> >>
> >>Setting the Window->Preferences->Ant->Runtime->Properties value for
> >>${VARIABLE} did seem to allow the Ant Build to _run_ correctly. Choosing
> >>the Outline->"project name"->Run->Ant Build automatically built and ran
> >>an external tools "Ant Build" configuration (nice!) and ran
successfully.
> >>
> >>However, the Ant build file editor and external tools configuration
> >>editor still think that my buildfile is in error.
> >
> >
> >>* The Ant build file editor does not locate the imported file and
> >>appears to not use the defined property the same way the runtime did.
> >>
> >
> >
> > I will work on fixing this up shortly via bug 72512. I do not believe
there
> > is anything you as a user could do to fix this...but I'd be happy if you
> > proved me wrong :-)
> >
> >
> >>* The external tools editor won't let me run the build file from there
> >>because it says one of my custom tasks is undefined. It is defined at
> >>runtime. The problem just seems to be at editing time.
> >
> >
> > So your tasks are defined in the imported file?
> >
> >
> >>I think I may be able to resolve the second problem by hand registering
> >>the tasks within Eclipse; even though this is a pain since my included
> >>build files encapsulate this. However, I have less confidence in getting
> >>the Ant build file editor to expand the ${VARIABLE} reference during the
> >>import outside of runtime.
> >>
> >>Darin Swanson wrote:
> >>
> >>
> >>>It should work setting the property in
> >>>
> >>>
> >>>>* setting the variable in
Window->Preferences->Ant->Runtime->Properties
> >>>
> >>>and I can get a successful build with this setup but the property
> >
> > appears to
> >
> >>>not be applied when parsing so this result in errors in the editor.
> >>>
> >>>To specify "-DINCLUDES=c:/tmp/bar"
> >>>go to the Main tab of your Ant launch configuration and place this
> >
> > argument
> >
> >>>in the Arguments pane.
> >>>I had success using this for a successful build as well.
> >>>
> >>>For the errors in the Ant Editor, I have logged
> >>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
> >>>
> >>>Thanks
> >>>Darins
> >>>
> >>>"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> >>>news:cgfjp3$j2d$1@eclipse.org...
> >>>
> >>>
> >>>>I am using the import in a similar way as the original post, except
that
> >>>>I am using a ${VARIABLE} reference to locate the imported file. Things
> >>>>work correctly when using Ant stand-alone. However, within Eclipse, I
> >>>>cannot locate a way to tell it how to resolve the variable. It fails
in
> >>>>both the Ant editor and the External Tools.
> >>>>
> >>>>I've tried:
> >>>>* setting the variable in
Window->Preferences->Ant->Runtime->Properties
> >>>>* setting the variable in my external environment
> >>>>
> >>>>The following is a simple example of what I am doing. The build.xml
file
> >>>>is in a separate directory from the included file. When I edit this
> >>>>within Eclipse it acts like the first runtime case where ${INCLUDES}
was
> >>>>not defined. I am looking for a way within Eclipse to get ${INCLUDES}
> >>>>defined so it understands what is happening like in the last execution
> >>>>below in the stand-alone case.
> >>>>
> >>>>$ pwd
> >>>>/cygdrive/c/tmp
> >>>>
> >>>>$ more foo/build.xml bar/included.xml
> >>>>::::::::::::::
> >>>>foo/build.xml
> >>>>::::::::::::::
> >>>><project name="main" default="all">
> >>>> <import file="${INCLUDES}/included.xml"/>
> >>>></project>
> >>>>::::::::::::::
> >>>>bar/included.xml
> >>>>::::::::::::::
> >>>><project name="included">
> >>>> <target name="all">
> >>>> <echo>Hello World</echo>
> >>>> </target>
> >>>></project>
> >>>>
> >>>>$ ant -f foo/build.xml ### This fails as expected ###
> >>>>Buildfile: foo\build.xml
> >>>>
> >>>>BUILD FAILED
> >>>>C:\tmp\foo\build.xml:2: Cannot find ${INCLUDES}/included.xml imported
> >>>
> >>>>from C:\tmp\foo\build.xml
> >>>
> >>>>Total time: 0 seconds
> >>>>
> >>>>$ ant -f foo/build.xml -DINCLUDES=c:/tmp/bar ### How do I get
> >>>>
> >>>> ### Eclipse/Ant
> >>>> ### to work like this?
> >>>>Buildfile: foo\build.xml
> >>>>
> >>>>all:
> >>>> [echo] Hello World
> >>>>
> >>>>BUILD SUCCESSFUL
> >>>>Total time: 0 seconds
> >>>>
> >>>>
> >>>>
> >>>>Darin Swanson wrote:
> >>>>
> >>>>
> >>>>>Thanks for reporting back.
> >>>>>I was not expecting people to use <import> buildfiles that way but
why
> >>>
> >>>not
> >>>
> >>>
> >>>>>:-)
> >>>>>So I have entered https://bugs.eclipse.org/bugs/show_bug.cgi?id=71347
> >>>>>so we can track an enhancement to match how you work
> >>>>>
> >>>>>Thanks
> >>>>>Darins
> >>>>>
> >>>>>"David Corbin" <dcorbin@machturtle.com> wrote in message
> >>>>>news:cepaus$i4e$1@eclipse.org...
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>In the final 3.0 if a fragment does not contain a top level project
> >>>>>>>element it will not have problems added to the problems view.
> >>>>>>>
> >>>>>>
> >>>>>>Although I didn't think it had a top level project, it does have one
> >>>>>>(without the normal requried attributes).
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Now are you using <import> or using the entity includes for adding
> >
> > the
> >
> >>>>>>>fragments in your buildfile?
> >>>>>>
> >>>>>>Definatley <import>.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Of course with the <import> these need to be full fledged build
files
> >>>
> >>>so
> >>>
> >>>
> >>>>>>>is that what is causing you the trouble?
> >>>>>>
> >>>>>>Probably. I suppose I can add the project attributes to the
imported
> >>>>>
> >>>>>file,
> >>>>>
> >>>>>
> >>>>>
> >>>>>>even though it's not designed to be used directly.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>What is an example of a problem you are getting?
> >>>>>>>
> >>>>>>
> >>>>>>"No default target specified", "Target foo does not exist in this
> >>>>>
> >>>>>project".
> >>>>>
> >>>>>
> >>>>>
> >>>>>>"Default target list does not exist in this project".
> >>>>>>
> >>>>>>As mentioned above, the import file is not designed to be used
alone.
> >>>
> >>>It
> >>>
> >>>
> >>>>>>references targets that are supposed to be define by the importing
> >
> > file.
> >
> >>>>>>
> >>>>>>
> >>>>>>>HTH
> >>>>>>>Darins
> >>>>>>
> >>>>>>David
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >
> >
>
|
|
|
| Re: ANT Builder properties undefined during import [message #268669 is a reply to message #268474] |
Wed, 25 August 2004 09:56 |
| Eclipse User |
|
|
|
Darin,
You are right in that I am hitting two separate errors.
The taskdef issues are the same whether I am using the imports or not. I
have added the details you have requested to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=68373 .
The problems with the variable expansion and imports within the Ant
Editor seem covered by your entry in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
Note that in our development environment we try to generalize and
centralize the details of the build system as much as possible away from
the individual components and applications they are building. The build
files within the source trees of the individual projects simply identify
what kind of component it is by importing the correct generalized build
file and supplying a couple of component/application specific
properties. It is rare that a user of the imported build files has any
clue as to how what he/she has imported actually work. That is one
reason why individually registering each ant task within the Ant
preferences is not attractive.
The Ant changes in 3.0 look very promising.
thanks,
jim
Darin Swanson wrote:
> You have hit the same problem as:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=68373
>
> As indicated in that bug report you can turn off the "incomplete classpath"
> errors for the editor as another workaround.
> If you have the time to add your details to the bug report, that would be
> great. If you don't get to it...I will eventually :-)
>
> Thanks for your help in diagnosing the problem
> Darins
>
> "Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> news:cgg13u$bbj$1@eclipse.org...
>
>>Okay, I'll relax on the editor.
>>
>>Yes. I have custom tasks defined within the imported file. My main
>>build.xml files are extremely sparse.
>>
>><project name="corebuild_properties">
>> <taskdef resource="net/sf/antcontrib/antcontrib.properties"/>
>> <osfamily property="osFamily"/>
>>
>>Any insight as to how I can get Eclipse better configured to recognize
>>the custom tasks would be appreciated. Right now, I have osfamily
>>defined under Window->preferences->Ant->Runtime->Tasks, but comes up
>>undefined on the external tools editor.
>>
>>Although it does run under the external tools run button and Outline,
>>I've just started playing with the Ant view where I can seach and
>>execute various build.xml files. In this view, the executation fails
>>because osfamiliy could not be instantiated.
>>
>>Still plugging away...
>>
>>Darin Swanson wrote:
>>
>>
>>>"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
>>>news:cgfvd2$8cb$1@eclipse.org...
>>>
>>>
>>>>Thanks for the confidence to continue in the face of failure. I was able
>>>>to get a few things working and a few other things still seem to be
>>>>broken as originally reported.
>>>>
>>>>Setting the Window->Preferences->Ant->Runtime->Properties value for
>>>>${VARIABLE} did seem to allow the Ant Build to _run_ correctly. Choosing
>>>>the Outline->"project name"->Run->Ant Build automatically built and ran
>>>>an external tools "Ant Build" configuration (nice!) and ran
>
> successfully.
>
>>>>However, the Ant build file editor and external tools configuration
>>>>editor still think that my buildfile is in error.
>>>
>>>
>>>>* The Ant build file editor does not locate the imported file and
>>>>appears to not use the defined property the same way the runtime did.
>>>>
>>>
>>>
>>>I will work on fixing this up shortly via bug 72512. I do not believe
>
> there
>
>>>is anything you as a user could do to fix this...but I'd be happy if you
>>>proved me wrong :-)
>>>
>>>
>>>
>>>>* The external tools editor won't let me run the build file from there
>>>>because it says one of my custom tasks is undefined. It is defined at
>>>>runtime. The problem just seems to be at editing time.
>>>
>>>
>>>So your tasks are defined in the imported file?
>>>
>>>
>>>
>>>>I think I may be able to resolve the second problem by hand registering
>>>>the tasks within Eclipse; even though this is a pain since my included
>>>>build files encapsulate this. However, I have less confidence in getting
>>>>the Ant build file editor to expand the ${VARIABLE} reference during the
>>>>import outside of runtime.
>>>>
>>>>Darin Swanson wrote:
>>>>
>>>>
>>>>
>>>>>It should work setting the property in
>>>>>
>>>>>
>>>>>
>>>>>>* setting the variable in
>
> Window->Preferences->Ant->Runtime->Properties
>
>>>>>and I can get a successful build with this setup but the property
>>>
>>>appears to
>>>
>>>
>>>>>not be applied when parsing so this result in errors in the editor.
>>>>>
>>>>>To specify "-DINCLUDES=c:/tmp/bar"
>>>>>go to the Main tab of your Ant launch configuration and place this
>>>
>>>argument
>>>
>>>
>>>>>in the Arguments pane.
>>>>>I had success using this for a successful build as well.
>>>>>
>>>>>For the errors in the Ant Editor, I have logged
>>>>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
>>>>>
>>>>>Thanks
>>>>>Darins
>>>>>
>>>>>"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
>>>>>news:cgfjp3$j2d$1@eclipse.org...
>>>>>
>>>>>
>>>>>
>>>>>>I am using the import in a similar way as the original post, except
>
> that
>
>>>>>>I am using a ${VARIABLE} reference to locate the imported file. Things
>>>>>>work correctly when using Ant stand-alone. However, within Eclipse, I
>>>>>>cannot locate a way to tell it how to resolve the variable. It fails
>
> in
>
>>>>>>both the Ant editor and the External Tools.
>>>>>>
>>>>>>I've tried:
>>>>>>* setting the variable in
>
> Window->Preferences->Ant->Runtime->Properties
>
>>>>>>* setting the variable in my external environment
>>>>>>
>>>>>>The following is a simple example of what I am doing. The build.xml
>
> file
>
>>>>>>is in a separate directory from the included file. When I edit this
>>>>>>within Eclipse it acts like the first runtime case where ${INCLUDES}
>
> was
>
>>>>>>not defined. I am looking for a way within Eclipse to get ${INCLUDES}
>>>>>>defined so it understands what is happening like in the last execution
>>>>>>below in the stand-alone case.
>>>>>>
>>>>>>$ pwd
>>>>>>/cygdrive/c/tmp
>>>>>>
>>>>>>$ more foo/build.xml bar/included.xml
>>>>>>::::::::::::::
>>>>>>foo/build.xml
>>>>>>::::::::::::::
>>>>>><project name="main" default="all">
>>>>>> <import file="${INCLUDES}/included.xml"/>
>>>>>></project>
>>>>>>::::::::::::::
>>>>>>bar/included.xml
>>>>>>::::::::::::::
>>>>>><project name="included">
>>>>>> <target name="all">
>>>>>> <echo>Hello World</echo>
>>>>>> </target>
>>>>>></project>
>>>>>>
>>>>>>$ ant -f foo/build.xml ### This fails as expected ###
>>>>>>Buildfile: foo\build.xml
>>>>>>
>>>>>>BUILD FAILED
>>>>>>C:\tmp\foo\build.xml:2: Cannot find ${INCLUDES}/included.xml imported
>>>>>
>>>>>>from C:\tmp\foo\build.xml
>>>>>
>>>>>
>>>>>>Total time: 0 seconds
>>>>>>
>>>>>>$ ant -f foo/build.xml -DINCLUDES=c:/tmp/bar ### How do I get
>>>>>>
>>>>>> ### Eclipse/Ant
>>>>>> ### to work like this?
>>>>>>Buildfile: foo\build.xml
>>>>>>
>>>>>>all:
>>>>>> [echo] Hello World
>>>>>>
>>>>>>BUILD SUCCESSFUL
>>>>>>Total time: 0 seconds
>>>>>>
>>>>>>
>>>>>>
>>>>>>Darin Swanson wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Thanks for reporting back.
>>>>>>>I was not expecting people to use <import> buildfiles that way but
>
> why
>
>>>>>not
>>>>>
>>>>>
>>>>>
>>>>>>>:-)
>>>>>>>So I have entered https://bugs.eclipse.org/bugs/show_bug.cgi?id=71347
>>>>>>>so we can track an enhancement to match how you work
>>>>>>>
>>>>>>>Thanks
>>>>>>>Darins
>>>>>>>
>>>>>>>"David Corbin" <dcorbin@machturtle.com> wrote in message
>>>>>>>news:cepaus$i4e$1@eclipse.org...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>In the final 3.0 if a fragment does not contain a top level project
>>>>>>>>>element it will not have problems added to the problems view.
>>>>>>>>>
>>>>>>>>
>>>>>>>>Although I didn't think it had a top level project, it does have one
>>>>>>>>(without the normal requried attributes).
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Now are you using <import> or using the entity includes for adding
>>>
>>>the
>>>
>>>
>>>>>>>>>fragments in your buildfile?
>>>>>>>>
>>>>>>>>Definatley <import>.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Of course with the <import> these need to be full fledged build
>
> files
>
>>>>>so
>>>>>
>>>>>
>>>>>
>>>>>>>>>is that what is causing you the trouble?
>>>>>>>>
>>>>>>>>Probably. I suppose I can add the project attributes to the
>
> imported
>
>>>>>>>file,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>even though it's not designed to be used directly.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>What is an example of a problem you are getting?
>>>>>>>>>
>>>>>>>>
>>>>>>>>"No default target specified", "Target foo does not exist in this
>>>>>>>
>>>>>>>project".
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>"Default target list does not exist in this project".
>>>>>>>>
>>>>>>>>As mentioned above, the import file is not designed to be used
>
> alone.
>
>>>>>It
>>>>>
>>>>>
>>>>>
>>>>>>>>references targets that are supposed to be define by the importing
>>>
>>>file.
>>>
>>>
>>>>>>>>
>>>>>>>>>HTH
>>>>>>>>>Darins
>>>>>>>>
>>>>>>>>David
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>
>
>
|
|
|
| Re: ANT Builder properties undefined during import [message #268691 is a reply to message #268669] |
Wed, 25 August 2004 11:58 |
| Eclipse User |
|
|
|
Thanks for reporting back Jim.
I will work to resolving these issues.
I have a fix for the variable expansion that I will likely release today.
I hope the workaround of launching from the Ant editor outline is not too
cumbersome.
As well you can use the launch history and favorites once you performed the
build.
Please keep up the reporting of the problems / enhancements you would like
to see in the Ant integration.
Darins
"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
news:cgi5k1$j2m$1@eclipse.org...
> Darin,
>
> You are right in that I am hitting two separate errors.
>
> The taskdef issues are the same whether I am using the imports or not. I
> have added the details you have requested to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=68373 .
>
> The problems with the variable expansion and imports within the Ant
> Editor seem covered by your entry in
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
>
> Note that in our development environment we try to generalize and
> centralize the details of the build system as much as possible away from
> the individual components and applications they are building. The build
> files within the source trees of the individual projects simply identify
> what kind of component it is by importing the correct generalized build
> file and supplying a couple of component/application specific
> properties. It is rare that a user of the imported build files has any
> clue as to how what he/she has imported actually work. That is one
> reason why individually registering each ant task within the Ant
> preferences is not attractive.
>
> The Ant changes in 3.0 look very promising.
>
> thanks,
> jim
>
> Darin Swanson wrote:
> > You have hit the same problem as:
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=68373
> >
> > As indicated in that bug report you can turn off the "incomplete
classpath"
> > errors for the editor as another workaround.
> > If you have the time to add your details to the bug report, that would
be
> > great. If you don't get to it...I will eventually :-)
> >
> > Thanks for your help in diagnosing the problem
> > Darins
> >
> > "Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> > news:cgg13u$bbj$1@eclipse.org...
> >
> >>Okay, I'll relax on the editor.
> >>
> >>Yes. I have custom tasks defined within the imported file. My main
> >>build.xml files are extremely sparse.
> >>
> >><project name="corebuild_properties">
> >> <taskdef resource="net/sf/antcontrib/antcontrib.properties"/>
> >> <osfamily property="osFamily"/>
> >>
> >>Any insight as to how I can get Eclipse better configured to recognize
> >>the custom tasks would be appreciated. Right now, I have osfamily
> >>defined under Window->preferences->Ant->Runtime->Tasks, but comes up
> >>undefined on the external tools editor.
> >>
> >>Although it does run under the external tools run button and Outline,
> >>I've just started playing with the Ant view where I can seach and
> >>execute various build.xml files. In this view, the executation fails
> >>because osfamiliy could not be instantiated.
> >>
> >>Still plugging away...
> >>
> >>Darin Swanson wrote:
> >>
> >>
> >>>"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> >>>news:cgfvd2$8cb$1@eclipse.org...
> >>>
> >>>
> >>>>Thanks for the confidence to continue in the face of failure. I was
able
> >>>>to get a few things working and a few other things still seem to be
> >>>>broken as originally reported.
> >>>>
> >>>>Setting the Window->Preferences->Ant->Runtime->Properties value for
> >>>>${VARIABLE} did seem to allow the Ant Build to _run_ correctly.
Choosing
> >>>>the Outline->"project name"->Run->Ant Build automatically built and
ran
> >>>>an external tools "Ant Build" configuration (nice!) and ran
> >
> > successfully.
> >
> >>>>However, the Ant build file editor and external tools configuration
> >>>>editor still think that my buildfile is in error.
> >>>
> >>>
> >>>>* The Ant build file editor does not locate the imported file and
> >>>>appears to not use the defined property the same way the runtime did.
> >>>>
> >>>
> >>>
> >>>I will work on fixing this up shortly via bug 72512. I do not believe
> >
> > there
> >
> >>>is anything you as a user could do to fix this...but I'd be happy if
you
> >>>proved me wrong :-)
> >>>
> >>>
> >>>
> >>>>* The external tools editor won't let me run the build file from there
> >>>>because it says one of my custom tasks is undefined. It is defined at
> >>>>runtime. The problem just seems to be at editing time.
> >>>
> >>>
> >>>So your tasks are defined in the imported file?
> >>>
> >>>
> >>>
> >>>>I think I may be able to resolve the second problem by hand
registering
> >>>>the tasks within Eclipse; even though this is a pain since my included
> >>>>build files encapsulate this. However, I have less confidence in
getting
> >>>>the Ant build file editor to expand the ${VARIABLE} reference during
the
> >>>>import outside of runtime.
> >>>>
> >>>>Darin Swanson wrote:
> >>>>
> >>>>
> >>>>
> >>>>>It should work setting the property in
> >>>>>
> >>>>>
> >>>>>
> >>>>>>* setting the variable in
> >
> > Window->Preferences->Ant->Runtime->Properties
> >
> >>>>>and I can get a successful build with this setup but the property
> >>>
> >>>appears to
> >>>
> >>>
> >>>>>not be applied when parsing so this result in errors in the editor.
> >>>>>
> >>>>>To specify "-DINCLUDES=c:/tmp/bar"
> >>>>>go to the Main tab of your Ant launch configuration and place this
> >>>
> >>>argument
> >>>
> >>>
> >>>>>in the Arguments pane.
> >>>>>I had success using this for a successful build as well.
> >>>>>
> >>>>>For the errors in the Ant Editor, I have logged
> >>>>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=72512
> >>>>>
> >>>>>Thanks
> >>>>>Darins
> >>>>>
> >>>>>"Jim Stafford" <jcstaff@apl.jhu.edu> wrote in message
> >>>>>news:cgfjp3$j2d$1@eclipse.org...
> >>>>>
> >>>>>
> >>>>>
> >>>>>>I am using the import in a similar way as the original post, except
> >
> > that
> >
> >>>>>>I am using a ${VARIABLE} reference to locate the imported file.
Things
> >>>>>>work correctly when using Ant stand-alone. However, within Eclipse,
I
> >>>>>>cannot locate a way to tell it how to resolve the variable. It fails
> >
> > in
> >
> >>>>>>both the Ant editor and the External Tools.
> >>>>>>
> >>>>>>I've tried:
> >>>>>>* setting the variable in
> >
> > Window->Preferences->Ant->Runtime->Properties
> >
> >>>>>>* setting the variable in my external environment
> >>>>>>
> >>>>>>The following is a simple example of what I am doing. The build.xml
> >
> > file
> >
> >>>>>>is in a separate directory from the included file. When I edit this
> >>>>>>within Eclipse it acts like the first runtime case where ${INCLUDES}
> >
> > was
> >
> >>>>>>not defined. I am looking for a way within Eclipse to get
${INCLUDES}
> >>>>>>defined so it understands what is happening like in the last
execution
> >>>>>>below in the stand-alone case.
> >>>>>>
> >>>>>>$ pwd
> >>>>>>/cygdrive/c/tmp
> >>>>>>
> >>>>>>$ more foo/build.xml bar/included.xml
> >>>>>>::::::::::::::
> >>>>>>foo/build.xml
> >>>>>>::::::::::::::
> >>>>>><project name="main" default="all">
> >>>>>> <import file="${INCLUDES}/included.xml"/>
> >>>>>></project>
> >>>>>>::::::::::::::
> >>>>>>bar/included.xml
> >>>>>>::::::::::::::
> >>>>>><project name="included">
> >>>>>> <target name="all">
> >>>>>> <echo>Hello World</echo>
> >>>>>> </target>
> >>>>>></project>
> >>>>>>
> >>>>>>$ ant -f foo/build.xml ### This fails as expected ###
> >>>>>>Buildfile: foo\build.xml
> >>>>>>
> >>>>>>BUILD FAILED
> >>>>>>C:\tmp\foo\build.xml:2: Cannot find ${INCLUDES}/included.xml
imported
> >>>>>
> >>>>>>from C:\tmp\foo\build.xml
> >>>>>
> >>>>>
> >>>>>>Total time: 0 seconds
> >>>>>>
> >>>>>>$ ant -f foo/build.xml -DINCLUDES=c:/tmp/bar ### How do I get
> >>>>>>
> >>>>>> ### Eclipse/Ant
> >>>>>> ### to work like this?
> >>>>>>Buildfile: foo\build.xml
> >>>>>>
> >>>>>>all:
> >>>>>> [echo] Hello World
> >>>>>>
> >>>>>>BUILD SUCCESSFUL
> >>>>>>Total time: 0 seconds
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>Darin Swanson wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Thanks for reporting back.
> >>>>>>>I was not expecting people to use <import> buildfiles that way but
> >
> > why
> >
> >>>>>not
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>:-)
> >>>>>>>So I have entered
https://bugs.eclipse.org/bugs/show_bug.cgi?id=71347
> >>>>>>>so we can track an enhancement to match how you work
> >>>>>>>
> >>>>>>>Thanks
> >>>>>>>Darins
> >>>>>>>
> >>>>>>>"David Corbin" <dcorbin@machturtle.com> wrote in message
> >>>>>>>news:cepaus$i4e$1@eclipse.org...
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>>In the final 3.0 if a fragment does not contain a top level
project
> >>>>>>>>>element it will not have problems added to the problems view.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>Although I didn't think it had a top level project, it does have
one
> >>>>>>>>(without the normal requried attributes).
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>Now are you using <import> or using the entity includes for
adding
> >>>
> >>>the
> >>>
> >>>
> >>>>>>>>>fragments in your buildfile?
> >>>>>>>>
> >>>>>>>>Definatley <import>.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>Of course with the <import> these need to be full fledged build
> >
> > files
> >
> >>>>>so
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>>>is that what is causing you the trouble?
> >>>>>>>>
> >>>>>>>>Probably. I suppose I can add the project attributes to the
> >
> > imported
> >
> >>>>>>>file,
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>even though it's not designed to be used directly.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>What is an example of a problem you are getting?
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>"No default target specified", "Target foo does not exist in this
> >>>>>>>
> >>>>>>>project".
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>"Default target list does not exist in this project".
> >>>>>>>>
> >>>>>>>>As mentioned above, the import file is not designed to be used
> >
> > alone.
> >
> >>>>>It
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>>references targets that are supposed to be define by the importing
> >>>
> >>>file.
> >>>
> >>>
> >>>>>>>>
> >>>>>>>>>HTH
> >>>>>>>>>Darins
> >>>>>>>>
> >>>>>>>>David
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>
> >
> >
>
|
|
|
Goto Forum:
Current Time: Wed Nov 05 17:00:25 EST 2025
Powered by FUDForum. Page generated in 0.06271 seconds |
Home