| Any way to abstract weaver.jar version in run configurations [message #65867] |
Wed, 21 June 2006 08:46  |
Eclipse User |
|
|
|
Every time I upgrade AJDT/AspectJ, I need to go thru my dozens of
eclipse run configurations and change the vm arguments, eg:
-javaagent:${resource_loc:/tp_core/lib/aspectjweaver-1.5.2.2 0060619065212.jar}
Note, I can't simply use the aspectj specific run configurations because
I often need to use other types of run configurations (eg, junit,
fixture, tomcat), and eclipse does not (even yet) have any way to mix
run configuration features.
I can't seem to find any type of variable that I can use to define the
version specific jar just once in eclipse. Has anybody solved this?
thanks!
-barry
|
|
|
|
|
|
|
| Re: Any way to abstract weaver.jar version in run configurations [message #594211 is a reply to message #65867] |
Wed, 21 June 2006 10:29  |
| Eclipse User |
|
|
|
How about ${env_var} or ${system_property} ?
regards,
Eugene
Barry Kaplan wrote:
> Every time I upgrade AJDT/AspectJ, I need to go thru my dozens of
> eclipse run configurations and change the vm arguments, eg:
>
> -javaagent:${resource_loc:/tp_core/lib/aspectjweaver-1.5.2.2 0060619065212.jar}
>
>
> Note, I can't simply use the aspectj specific run configurations
> because I often need to use other types of run configurations (eg,
> junit, fixture, tomcat), and eclipse does not (even yet) have any way
> to mix run configuration features.
>
> I can't seem to find any type of variable that I can use to define the
> version specific jar just once in eclipse. Has anybody solved this?
>
> thanks!
>
> -barry
|
|
|
| Re: Any way to abstract weaver.jar version in run configurations [message #594223 is a reply to message #65900] |
Wed, 21 June 2006 13:21 |
| Eclipse User |
|
|
|
Eugene Kuleshov wrote:
>
> How about ${env_var} or ${system_property} ?
I could use ${env_var}, but that requires I define an OS environment
variable and keep it in sync with the plugin. Same for system_property.
When AJDT is installed, it sets a classpath variable pointing to the
aspectj weaver jar, but that is not available in run configurations.
I really don't want to have to duplicate information already contained
by the ajdt plugin, but at least I would like to be able to define the
variable from within eclipse -- not the OS.
Oh well, thanks for the suggestions!
|
|
|
| Re: Any way to abstract weaver.jar version in run configurations [message #594230 is a reply to message #65921] |
Wed, 21 June 2006 13:34 |
| Eclipse User |
|
|
|
I guess you would have to fill a report against JDT/Debug component
to add classpath variables to the variables used by launch configs.
regards,
Eugene
Barry Kaplan wrote:
> Eugene Kuleshov wrote:
>>
>> How about ${env_var} or ${system_property} ?
>
> I could use ${env_var}, but that requires I define an OS environment
> variable and keep it in sync with the plugin. Same for system_property.
> When AJDT is installed, it sets a classpath variable pointing to the
> aspectj weaver jar, but that is not available in run configurations.
>
> I really don't want to have to duplicate information already contained
> by the ajdt plugin, but at least I would like to be able to define the
> variable from within eclipse -- not the OS.
>
> Oh well, thanks for the suggestions!
|
|
|
|
Powered by
FUDForum. Page generated in 0.04843 seconds
Home