Skip to main content


Eclipse Community Forums

      Home
Home » Language IDEs » Java Development Tools (JDT) » External Tool/Ant Builders
External Tool/Ant Builders [message #141540] Thu, 12 February 2004 15:51 Go to next message
Eclipse UserFriend
Originally posted by: mbrozowski.nc.rr.com

I was wondering if there is a good reason why the 'wizard' for the Ant
Builder in a Java Project is not the same as the Ant/Runtime
preferences page which in turn is not the same as the External
Tools.. ->Ant Builder..

An example is why can't I set the Classpath in the Ant Builder for my
Java Project

Also the External Program Builders are also different...
Why can't I set environment variables for the Java Project builder
when I can other places

Is there a reason for the additional limitations on the builders?

Do you need someone to help make it more consistent?

Matt Brozowski
Re: External Tool/Ant Builders [message #141552 is a reply to message #141540] Thu, 12 February 2004 16:18 Go to previous messageGo to next message
Eclipse UserFriend
> An example is why can't I set the Classpath in the Ant Builder for my
> Java Project
Possible for 3.0
https://bugs.eclipse.org/bugs/show_bug.cgi?id=50986

> Why can't I set environment variables for the Java Project builder
> when I can other places
Fixed in M7
https://bugs.eclipse.org/bugs/show_bug.cgi?id=51298

> Is there a reason for the additional limitations on the builders?
Time :-)
We are trying but help is always appreciated.

Thanks for the feedback
Darins
Re: External Tool/Ant Builders [message #141595 is a reply to message #141552] Thu, 12 February 2004 17:17 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mbrozowski.nc.rr.com

Thank you so much for the info... I'm really looking forward to M7 (I
guess I've gotten used to the once per month milestones... )

Are the behaviors for these different Tabbed collection all
different... It seems like it would be a lot easier for all of you.. I
this code was all common (with only a few special case tabs such as
'common' and 'build options') Is it necessary to maintain two or
three completely different sets?

Also a related question... Does the environment tab support eclipse
variables like ${workspace:/project} as a value and are there variable
for thinks like JAVA_HOME?

Thanks for the great help. I'll start learning that code and see if
there is any way I can help in this area.

Matt Brozowski

"Darin Swanson" <Darin_Swanson@us.ibm.com> wrote in message
news:c0gq54$lda$1@eclipse.org...
> > An example is why can't I set the Classpath in the Ant Builder for
my
> > Java Project
> Possible for 3.0
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=50986
>
> > Why can't I set environment variables for the Java Project builder
> > when I can other places
> Fixed in M7
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=51298
>
> > Is there a reason for the additional limitations on the builders?
> Time :-)
> We are trying but help is always appreciated.
>
> Thanks for the feedback
> Darins
>
>
Re: External Tool/Ant Builders [message #141675 is a reply to message #141595] Fri, 13 February 2004 00:31 Go to previous messageGo to next message
Eclipse UserFriend
"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
news:c0gtt7$q7n$1@eclipse.org...
> Thank you so much for the info... I'm really looking forward to M7 (I
> guess I've gotten used to the once per month milestones... )

I wish I could get used to them :-)

>
> Are the behaviors for these different Tabbed collection all
> different... It seems like it would be a lot easier for all of you.. I
> this code was all common (with only a few special case tabs such as
> 'common' and 'build options') Is it necessary to maintain two or
> three completely different sets?

The code is really common among the different groups it is just the time to
do the "wiring" behind the UI...minimal but it still takes time

>
> Also a related question... Does the environment tab support eclipse
> variables like ${workspace:/project} as a value and are there variable
> for thinks like JAVA_HOME?
>
Yes you can use variables that get expanded.
For your case you would use ${workspace_loc:/project}
For example, if you set to append to the native environment, you can set
PATH to be ${workspace_loc:/project} and this will be appended to the value
of the PATH variable.

We should make this easier and more appearant to the user that you can use
variables.
I logged:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=51935

For a listing of possible variables check out the selection available by
hitting the Variables button on the Main tab of a builder.
To use JAVA_HOME, you would make use of the env_var variable with the name
JAVA_HOME:
${env_var:JAVA_HOME}

> Thanks for the great help. I'll start learning that code and see if
> there is any way I can help in this area.
>

Let me know if there is any way I can help. Don't hesitate to ask
development questions on the platform-ant-dev mailing list.

Darins
Re: External Tool/Ant Builders [message #145209 is a reply to message #141675] Wed, 25 February 2004 10:01 Go to previous messageGo to next message
Eclipse UserFriend
I'm using M7 now and don't see an Environment tab in the dialog that
appears when I select Run/External Tools/External Tools.../Ant Build/{my
ant config}. I could really use such a thing, but just don't know how to
access it. Did this feature really make M7 in the end?

Chris DiGiano

Darin Swanson wrote:
> "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> news:c0gtt7$q7n$1@eclipse.org...
>
>>Thank you so much for the info... I'm really looking forward to M7 (I
>>guess I've gotten used to the once per month milestones... )
>
>
> I wish I could get used to them :-)
>
>
>>Are the behaviors for these different Tabbed collection all
>>different... It seems like it would be a lot easier for all of you.. I
>>this code was all common (with only a few special case tabs such as
>>'common' and 'build options') Is it necessary to maintain two or
>>three completely different sets?
>
>
> The code is really common among the different groups it is just the time to
> do the "wiring" behind the UI...minimal but it still takes time
>
>
>>Also a related question... Does the environment tab support eclipse
>>variables like ${workspace:/project} as a value and are there variable
>>for thinks like JAVA_HOME?
>>
>
> Yes you can use variables that get expanded.
> For your case you would use ${workspace_loc:/project}
> For example, if you set to append to the native environment, you can set
> PATH to be ${workspace_loc:/project} and this will be appended to the value
> of the PATH variable.
>
> We should make this easier and more appearant to the user that you can use
> variables.
> I logged:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=51935
>
> For a listing of possible variables check out the selection available by
> hitting the Variables button on the Main tab of a builder.
> To use JAVA_HOME, you would make use of the env_var variable with the name
> JAVA_HOME:
> ${env_var:JAVA_HOME}
>
>
>>Thanks for the great help. I'll start learning that code and see if
>>there is any way I can help in this area.
>>
>
>
> Let me know if there is any way I can help. Don't hesitate to ask
> development questions on the platform-ant-dev mailing list.
>
> Darins
>
>
Re: External Tool/Ant Builders [message #145391 is a reply to message #145209] Wed, 25 February 2004 12:08 Go to previous messageGo to next message
Eclipse UserFriend
Chris there is no Environment Tab for the Ant builds...only the Program
external tools.
We are working out what it means to have the environment tab for the Ant
builds.
If the build is launched in the same VM as Eclipse it has no meaning.
I would be interested in your use case as we currently do not intend to add
the environment tab for the Ant builds...but we can change :-)

Thanks
Darins

"Chris DiGiano" <chris.digiano@sri.com> wrote in message
news:c1id6o$nho$1@eclipse.org...
> I'm using M7 now and don't see an Environment tab in the dialog that
> appears when I select Run/External Tools/External Tools.../Ant Build/{my
> ant config}. I could really use such a thing, but just don't know how to
> access it. Did this feature really make M7 in the end?
>
> Chris DiGiano
>
> Darin Swanson wrote:
> > "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> > news:c0gtt7$q7n$1@eclipse.org...
> >
> >>Thank you so much for the info... I'm really looking forward to M7 (I
> >>guess I've gotten used to the once per month milestones... )
> >
> >
> > I wish I could get used to them :-)
> >
> >
> >>Are the behaviors for these different Tabbed collection all
> >>different... It seems like it would be a lot easier for all of you.. I
> >>this code was all common (with only a few special case tabs such as
> >>'common' and 'build options') Is it necessary to maintain two or
> >>three completely different sets?
> >
> >
> > The code is really common among the different groups it is just the time
to
> > do the "wiring" behind the UI...minimal but it still takes time
> >
> >
> >>Also a related question... Does the environment tab support eclipse
> >>variables like ${workspace:/project} as a value and are there variable
> >>for thinks like JAVA_HOME?
> >>
> >
> > Yes you can use variables that get expanded.
> > For your case you would use ${workspace_loc:/project}
> > For example, if you set to append to the native environment, you can
set
> > PATH to be ${workspace_loc:/project} and this will be appended to the
value
> > of the PATH variable.
> >
> > We should make this easier and more appearant to the user that you can
use
> > variables.
> > I logged:
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=51935
> >
> > For a listing of possible variables check out the selection available by
> > hitting the Variables button on the Main tab of a builder.
> > To use JAVA_HOME, you would make use of the env_var variable with the
name
> > JAVA_HOME:
> > ${env_var:JAVA_HOME}
> >
> >
> >>Thanks for the great help. I'll start learning that code and see if
> >>there is any way I can help in this area.
> >>
> >
> >
> > Let me know if there is any way I can help. Don't hesitate to ask
> > development questions on the platform-ant-dev mailing list.
> >
> > Darins
> >
> >
Re: External Tool/Ant Builders [message #145400 is a reply to message #145391] Wed, 25 February 2004 12:23 Go to previous messageGo to next message
Eclipse UserFriend
Here's my case: I have an ant target that needs
${env.JAVA_HOME}/tools.jar in the classpath. I would like my environment
variable JAVA_HOME to be available when I run this ant target from
within Eclipse.

Chris

Darin Swanson wrote:
> Chris there is no Environment Tab for the Ant builds...only the Program
> external tools.
> We are working out what it means to have the environment tab for the Ant
> builds.
> If the build is launched in the same VM as Eclipse it has no meaning.
> I would be interested in your use case as we currently do not intend to add
> the environment tab for the Ant builds...but we can change :-)
>
> Thanks
> Darins
>
> "Chris DiGiano" <chris.digiano@sri.com> wrote in message
> news:c1id6o$nho$1@eclipse.org...
>
>>I'm using M7 now and don't see an Environment tab in the dialog that
>>appears when I select Run/External Tools/External Tools.../Ant Build/{my
>>ant config}. I could really use such a thing, but just don't know how to
>>access it. Did this feature really make M7 in the end?
>>
>>Chris DiGiano
>>
>>Darin Swanson wrote:
>>
>>>"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
>>>news:c0gtt7$q7n$1@eclipse.org...
>>>
>>>
>>>>Thank you so much for the info... I'm really looking forward to M7 (I
>>>>guess I've gotten used to the once per month milestones... )
>>>
>>>
>>>I wish I could get used to them :-)
>>>
>>>
>>>
>>>>Are the behaviors for these different Tabbed collection all
>>>>different... It seems like it would be a lot easier for all of you.. I
>>>>this code was all common (with only a few special case tabs such as
>>>>'common' and 'build options') Is it necessary to maintain two or
>>>>three completely different sets?
>>>
>>>
>>>The code is really common among the different groups it is just the time
>
> to
>
>>>do the "wiring" behind the UI...minimal but it still takes time
>>>
>>>
>>>
>>>>Also a related question... Does the environment tab support eclipse
>>>>variables like ${workspace:/project} as a value and are there variable
>>>>for thinks like JAVA_HOME?
>>>>
>>>
>>>Yes you can use variables that get expanded.
>>>For your case you would use ${workspace_loc:/project}
>>>For example, if you set to append to the native environment, you can
>
> set
>
>>>PATH to be ${workspace_loc:/project} and this will be appended to the
>
> value
>
>>>of the PATH variable.
>>>
>>>We should make this easier and more appearant to the user that you can
>
> use
>
>>>variables.
>>>I logged:
>>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=51935
>>>
>>>For a listing of possible variables check out the selection available by
>>>hitting the Variables button on the Main tab of a builder.
>>>To use JAVA_HOME, you would make use of the env_var variable with the
>
> name
>
>>>JAVA_HOME:
>>>${env_var:JAVA_HOME}
>>>
>>>
>>>
>>>>Thanks for the great help. I'll start learning that code and see if
>>>>there is any way I can help in this area.
>>>>
>>>
>>>
>>>Let me know if there is any way I can help. Don't hesitate to ask
>>>development questions on the platform-ant-dev mailing list.
>>>
>>>Darins
>>>
>>>
>
>
>
Re: External Tool/Ant Builders [message #145428 is a reply to message #145400] Wed, 25 February 2004 12:53 Go to previous messageGo to next message
Eclipse UserFriend
By default (with no environment tab) you will inherit the environment
variables.

My quick test
<project default="environ">
<target name="environ">
<property environment="env"></property>
<echo>${env.JAVA_HOME}</echo>
</target>
</project>

Produces the expected effect for both same and separate VM.
So with no additional support it would seem you can do what you need?

Thanks
Darins

"Chris DiGiano" <chris.digiano@sri.com> wrote in message
news:c1ilfr$4p5$1@eclipse.org...
> Here's my case: I have an ant target that needs
> ${env.JAVA_HOME}/tools.jar in the classpath. I would like my environment
> variable JAVA_HOME to be available when I run this ant target from
> within Eclipse.
>
> Chris
>
> Darin Swanson wrote:
> > Chris there is no Environment Tab for the Ant builds...only the Program
> > external tools.
> > We are working out what it means to have the environment tab for the Ant
> > builds.
> > If the build is launched in the same VM as Eclipse it has no meaning.
> > I would be interested in your use case as we currently do not intend to
add
> > the environment tab for the Ant builds...but we can change :-)
> >
> > Thanks
> > Darins
> >
> > "Chris DiGiano" <chris.digiano@sri.com> wrote in message
> > news:c1id6o$nho$1@eclipse.org...
> >
> >>I'm using M7 now and don't see an Environment tab in the dialog that
> >>appears when I select Run/External Tools/External Tools.../Ant Build/{my
> >>ant config}. I could really use such a thing, but just don't know how to
> >>access it. Did this feature really make M7 in the end?
> >>
> >>Chris DiGiano
> >>
> >>Darin Swanson wrote:
> >>
> >>>"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> >>>news:c0gtt7$q7n$1@eclipse.org...
> >>>
> >>>
> >>>>Thank you so much for the info... I'm really looking forward to M7 (I
> >>>>guess I've gotten used to the once per month milestones... )
> >>>
> >>>
> >>>I wish I could get used to them :-)
> >>>
> >>>
> >>>
> >>>>Are the behaviors for these different Tabbed collection all
> >>>>different... It seems like it would be a lot easier for all of you.. I
> >>>>this code was all common (with only a few special case tabs such as
> >>>>'common' and 'build options') Is it necessary to maintain two or
> >>>>three completely different sets?
> >>>
> >>>
> >>>The code is really common among the different groups it is just the
time
> >
> > to
> >
> >>>do the "wiring" behind the UI...minimal but it still takes time
> >>>
> >>>
> >>>
> >>>>Also a related question... Does the environment tab support eclipse
> >>>>variables like ${workspace:/project} as a value and are there variable
> >>>>for thinks like JAVA_HOME?
> >>>>
> >>>
> >>>Yes you can use variables that get expanded.
> >>>For your case you would use ${workspace_loc:/project}
> >>>For example, if you set to append to the native environment, you can
> >
> > set
> >
> >>>PATH to be ${workspace_loc:/project} and this will be appended to the
> >
> > value
> >
> >>>of the PATH variable.
> >>>
> >>>We should make this easier and more appearant to the user that you can
> >
> > use
> >
> >>>variables.
> >>>I logged:
> >>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=51935
> >>>
> >>>For a listing of possible variables check out the selection available
by
> >>>hitting the Variables button on the Main tab of a builder.
> >>>To use JAVA_HOME, you would make use of the env_var variable with the
> >
> > name
> >
> >>>JAVA_HOME:
> >>>${env_var:JAVA_HOME}
> >>>
> >>>
> >>>
> >>>>Thanks for the great help. I'll start learning that code and see if
> >>>>there is any way I can help in this area.
> >>>>
> >>>
> >>>
> >>>Let me know if there is any way I can help. Don't hesitate to ask
> >>>development questions on the platform-ant-dev mailing list.
> >>>
> >>>Darins
> >>>
> >>>
> >
> >
> >
Re: External Tool/Ant Builders [message #145437 is a reply to message #145428] Wed, 25 February 2004 13:14 Go to previous messageGo to next message
Eclipse UserFriend
That does not work for me under M7. Here's the output--
environ:
[echo] ${env.JAVA_HOME}
BUILD SUCCESSFUL

....and yes, I checked that JAVA_HOME is defined by using printenv on the
command line.

Chris

Darin Swanson wrote:

> By default (with no environment tab) you will inherit the environment
> variables.
>
> My quick test
> <project default="environ">
> <target name="environ">
> <property environment="env"></property>
> <echo>${env.JAVA_HOME}</echo>
> </target>
> </project>
>
> Produces the expected effect for both same and separate VM.
> So with no additional support it would seem you can do what you need?
>
> Thanks
> Darins
>
> "Chris DiGiano" <chris.digiano@sri.com> wrote in message
> news:c1ilfr$4p5$1@eclipse.org...
>
>>Here's my case: I have an ant target that needs
>>${env.JAVA_HOME}/tools.jar in the classpath. I would like my environment
>> variable JAVA_HOME to be available when I run this ant target from
>>within Eclipse.
>>
>>Chris
>>
>>Darin Swanson wrote:
>>
>>>Chris there is no Environment Tab for the Ant builds...only the Program
>>>external tools.
>>>We are working out what it means to have the environment tab for the Ant
>>>builds.
>>>If the build is launched in the same VM as Eclipse it has no meaning.
>>>I would be interested in your use case as we currently do not intend to
>
> add
>
>>>the environment tab for the Ant builds...but we can change :-)
>>>
>>>Thanks
>>>Darins
>>>
>>>"Chris DiGiano" <chris.digiano@sri.com> wrote in message
>>>news:c1id6o$nho$1@eclipse.org...
>>>
>>>
>>>>I'm using M7 now and don't see an Environment tab in the dialog that
>>>>appears when I select Run/External Tools/External Tools.../Ant Build/{my
>>>>ant config}. I could really use such a thing, but just don't know how to
>>>>access it. Did this feature really make M7 in the end?
>>>>
>>>>Chris DiGiano
>>>>
>>>>Darin Swanson wrote:
>>>>
>>>>
>>>>>"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
>>>>>news:c0gtt7$q7n$1@eclipse.org...
>>>>>
>>>>>
>>>>>
>>>>>>Thank you so much for the info... I'm really looking forward to M7 (I
>>>>>>guess I've gotten used to the once per month milestones... )
>>>>>
>>>>>
>>>>>I wish I could get used to them :-)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Are the behaviors for these different Tabbed collection all
>>>>>>different... It seems like it would be a lot easier for all of you.. I
>>>>>>this code was all common (with only a few special case tabs such as
>>>>>>'common' and 'build options') Is it necessary to maintain two or
>>>>>>three completely different sets?
>>>>>
>>>>>
>>>>>The code is really common among the different groups it is just the
>
> time
>
>>>to
>>>
>>>
>>>>>do the "wiring" behind the UI...minimal but it still takes time
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Also a related question... Does the environment tab support eclipse
>>>>>>variables like ${workspace:/project} as a value and are there variable
>>>>>>for thinks like JAVA_HOME?
>>>>>>
>>>>>
>>>>>Yes you can use variables that get expanded.
>>>>>For your case you would use ${workspace_loc:/project}
>>>>>For example, if you set to append to the native environment, you can
>>>
>>>set
>>>
>>>
>>>>>PATH to be ${workspace_loc:/project} and this will be appended to the
>>>
>>>value
>>>
>>>
>>>>>of the PATH variable.
>>>>>
>>>>>We should make this easier and more appearant to the user that you can
>>>
>>>use
>>>
>>>
>>>>>variables.
>>>>>I logged:
>>>>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=51935
>>>>>
>>>>>For a listing of possible variables check out the selection available
>
> by
>
>>>>>hitting the Variables button on the Main tab of a builder.
>>>>>To use JAVA_HOME, you would make use of the env_var variable with the
>>>
>>>name
>>>
>>>
>>>>>JAVA_HOME:
>>>>>${env_var:JAVA_HOME}
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Thanks for the great help. I'll start learning that code and see if
>>>>>>there is any way I can help in this area.
>>>>>>
>>>>>
>>>>>
>>>>>Let me know if there is any way I can help. Don't hesitate to ask
>>>>>development questions on the platform-ant-dev mailing list.
>>>>>
>>>>>Darins
>>>>>
>>>>>
>>>
>>>
>>>
>
>
Re: External Tool/Ant Builders [message #145463 is a reply to message #145437] Wed, 25 February 2004 13:54 Go to previous message
Eclipse UserFriend
So it would appear that we have a bug on our *nix support as this works fine
on Windows.

I have logged
https://bugs.eclipse.org/bugs/show_bug.cgi?id=53097
to investigate as I only have Windows at my current location.

Thanks
Darins

"Chris DiGiano" <chris.digiano@sri.com> wrote in message
news:c1iog2$9dp$1@eclipse.org...
> That does not work for me under M7. Here's the output--
> environ:
> [echo] ${env.JAVA_HOME}
> BUILD SUCCESSFUL
>
> ...and yes, I checked that JAVA_HOME is defined by using printenv on the
> command line.
>
> Chris
>
> Darin Swanson wrote:
>
> > By default (with no environment tab) you will inherit the environment
> > variables.
> >
> > My quick test
> > <project default="environ">
> > <target name="environ">
> > <property environment="env"></property>
> > <echo>${env.JAVA_HOME}</echo>
> > </target>
> > </project>
> >
> > Produces the expected effect for both same and separate VM.
> > So with no additional support it would seem you can do what you need?
> >
> > Thanks
> > Darins
> >
> > "Chris DiGiano" <chris.digiano@sri.com> wrote in message
> > news:c1ilfr$4p5$1@eclipse.org...
> >
> >>Here's my case: I have an ant target that needs
> >>${env.JAVA_HOME}/tools.jar in the classpath. I would like my environment
> >> variable JAVA_HOME to be available when I run this ant target from
> >>within Eclipse.
> >>
> >>Chris
> >>
> >>Darin Swanson wrote:
> >>
> >>>Chris there is no Environment Tab for the Ant builds...only the Program
> >>>external tools.
> >>>We are working out what it means to have the environment tab for the
Ant
> >>>builds.
> >>>If the build is launched in the same VM as Eclipse it has no meaning.
> >>>I would be interested in your use case as we currently do not intend to
> >
> > add
> >
> >>>the environment tab for the Ant builds...but we can change :-)
> >>>
> >>>Thanks
> >>>Darins
> >>>
> >>>"Chris DiGiano" <chris.digiano@sri.com> wrote in message
> >>>news:c1id6o$nho$1@eclipse.org...
> >>>
> >>>
> >>>>I'm using M7 now and don't see an Environment tab in the dialog that
> >>>>appears when I select Run/External Tools/External Tools.../Ant
Build/{my
> >>>>ant config}. I could really use such a thing, but just don't know how
to
> >>>>access it. Did this feature really make M7 in the end?
> >>>>
> >>>>Chris DiGiano
> >>>>
> >>>>Darin Swanson wrote:
> >>>>
> >>>>
> >>>>>"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> >>>>>news:c0gtt7$q7n$1@eclipse.org...
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Thank you so much for the info... I'm really looking forward to M7
(I
> >>>>>>guess I've gotten used to the once per month milestones... )
> >>>>>
> >>>>>
> >>>>>I wish I could get used to them :-)
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Are the behaviors for these different Tabbed collection all
> >>>>>>different... It seems like it would be a lot easier for all of you..
I
> >>>>>>this code was all common (with only a few special case tabs such as
> >>>>>>'common' and 'build options') Is it necessary to maintain two or
> >>>>>>three completely different sets?
> >>>>>
> >>>>>
> >>>>>The code is really common among the different groups it is just the
> >
> > time
> >
> >>>to
> >>>
> >>>
> >>>>>do the "wiring" behind the UI...minimal but it still takes time
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Also a related question... Does the environment tab support eclipse
> >>>>>>variables like ${workspace:/project} as a value and are there
variable
> >>>>>>for thinks like JAVA_HOME?
> >>>>>>
> >>>>>
> >>>>>Yes you can use variables that get expanded.
> >>>>>For your case you would use ${workspace_loc:/project}
> >>>>>For example, if you set to append to the native environment, you can
> >>>
> >>>set
> >>>
> >>>
> >>>>>PATH to be ${workspace_loc:/project} and this will be appended to the
> >>>
> >>>value
> >>>
> >>>
> >>>>>of the PATH variable.
> >>>>>
> >>>>>We should make this easier and more appearant to the user that you
can
> >>>
> >>>use
> >>>
> >>>
> >>>>>variables.
> >>>>>I logged:
> >>>>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=51935
> >>>>>
> >>>>>For a listing of possible variables check out the selection available
> >
> > by
> >
> >>>>>hitting the Variables button on the Main tab of a builder.
> >>>>>To use JAVA_HOME, you would make use of the env_var variable with the
> >>>
> >>>name
> >>>
> >>>
> >>>>>JAVA_HOME:
> >>>>>${env_var:JAVA_HOME}
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Thanks for the great help. I'll start learning that code and see if
> >>>>>>there is any way I can help in this area.
> >>>>>>
> >>>>>
> >>>>>
> >>>>>Let me know if there is any way I can help. Don't hesitate to ask
> >>>>>development questions on the platform-ant-dev mailing list.
> >>>>>
> >>>>>Darins
> >>>>>
> >>>>>
> >>>
> >>>
> >>>
> >
> >
Previous Topic:Announce: new plug-in for continuous testing
Next Topic:AdapterFactory IAdaptable without changing model objects
Goto Forum:
  


Current Time: Wed May 07 19:53:21 EDT 2025

Powered by FUDForum. Page generated in 0.03959 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly