Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AspectJ » Any way to abstract weaver.jar version in run configurations
Any way to abstract weaver.jar version in run configurations [message #65867] Wed, 21 June 2006 12:46 Go to next message
Barry Kaplan is currently offline Barry KaplanFriend
Messages: 230
Registered: July 2009
Senior Member
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 #65900 is a reply to message #65867] Wed, 21 June 2006 14:29 Go to previous messageGo to next message
Eugene Kuleshov is currently offline Eugene KuleshovFriend
Messages: 504
Registered: July 2009
Senior Member
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 #65921 is a reply to message #65900] Wed, 21 June 2006 17:21 Go to previous messageGo to next message
Barry Kaplan is currently offline Barry KaplanFriend
Messages: 230
Registered: July 2009
Senior Member
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 #65947 is a reply to message #65921] Wed, 21 June 2006 17:34 Go to previous messageGo to next message
Eugene Kuleshov is currently offline Eugene KuleshovFriend
Messages: 504
Registered: July 2009
Senior Member
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!
Re: Any way to abstract weaver.jar version in run configurations [message #65967 is a reply to message #65947] Wed, 21 June 2006 17:38 Go to previous message
Barry Kaplan is currently offline Barry KaplanFriend
Messages: 230
Registered: July 2009
Senior Member
Eugene Kuleshov wrote:
>
> I guess you would have to fill a report against JDT/Debug component
> to add classpath variables to the variables used by launch configs.

Yes, it looks that way. Thanks.
Re: Any way to abstract weaver.jar version in run configurations [message #594211 is a reply to message #65867] Wed, 21 June 2006 14:29 Go to previous message
Eugene Kuleshov is currently offline Eugene KuleshovFriend
Messages: 504
Registered: July 2009
Senior Member
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 17:21 Go to previous message
Barry Kaplan is currently offline Barry KaplanFriend
Messages: 230
Registered: July 2009
Senior Member
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 17:34 Go to previous message
Eugene Kuleshov is currently offline Eugene KuleshovFriend
Messages: 504
Registered: July 2009
Senior Member
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!
Re: Any way to abstract weaver.jar version in run configurations [message #594238 is a reply to message #65947] Wed, 21 June 2006 17:38 Go to previous message
Barry Kaplan is currently offline Barry KaplanFriend
Messages: 230
Registered: July 2009
Senior Member
Eugene Kuleshov wrote:
>
> I guess you would have to fill a report against JDT/Debug component
> to add classpath variables to the variables used by launch configs.

Yes, it looks that way. Thanks.
Previous Topic:Any way to abstract weaver.jar version in run configurations
Next Topic:AJDT 1.4 RC1
Goto Forum:
  


Current Time: Tue Apr 16 12:19:57 GMT 2024

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

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

Back to the top