|
| Re: AspectJ Runtime in its own feature? [message #73852 is a reply to message #73817] |
Wed, 06 May 2009 17:32  |
Eclipse User |
|
|
|
Originally posted by: andrew.eisenberg.springsource.com
I would recommend adding the aspectj runtime plugin as a required plugin in
your feature. I would also package the plugin within your own update site.
There are ways to point to third party update sites so that you don't have
to host your own version of the ajrt plugin, but this is complicated and
brittle in my experience. The ajrt plugin has not changed significantly in
years and is unlikely to change in the near future, so you are safe hosting
your own version.
On 05/05/09 11:18 PM, in article
096c4588bcad99b4cbdb5772f0431f3f$1@www.eclipse.org, "Larry Edelstein"
<ribs@acm.org> wrote:
> How can I specify that my non-AspectJ-specific Eclipse feature (which
> nonetheless uses AspectJ internally) depends on the AspectJ runtime,
> without specifying that it depends on the AJDT feature?
>
> There is an AJDT feature that includes the AspectJ runtime, but it's not
> what I need. Because I don't want to reference that from my feature; I
> don't want consumers of my feature to have to install the AspectJ runtime.
> Instead, I really just want a feature that contains just the runtime.
>
> What should I do?
>
> - I could include the runtime plugin(s) (org.aspect.runtime, other?) in my
> feature.
> - I could package my own feature that includes that.
> - I could reference an existing feature that I haven't heard of yet, but
> it is out there somewhere...?
>
> Larry Edelstein
> Senior Member of Technical Staff
> Salesforce.com
>
>
|
|
|
| Re: AspectJ Runtime in its own feature? [message #599927 is a reply to message #73817] |
Wed, 06 May 2009 17:32 |
 Andrew Eisenberg
Messages: 77
Registered: July 2009 |
Member |
|
|
I would recommend adding the aspectj runtime plugin as a required plugin in
your feature. I would also package the plugin within your own update site.
There are ways to point to third party update sites so that you don't have
to host your own version of the ajrt plugin, but this is complicated and
brittle in my experience. The ajrt plugin has not changed significantly in
years and is unlikely to change in the near future, so you are safe hosting
your own version.
On 05/05/09 11:18 PM, in article
096c4588bcad99b4cbdb5772f0431f3f$1@www.eclipse.org, "Larry Edelstein"
<ribs@acm.org> wrote:
> How can I specify that my non-AspectJ-specific Eclipse feature (which
> nonetheless uses AspectJ internally) depends on the AspectJ runtime,
> without specifying that it depends on the AJDT feature?
>
> There is an AJDT feature that includes the AspectJ runtime, but it's not
> what I need. Because I don't want to reference that from my feature; I
> don't want consumers of my feature to have to install the AspectJ runtime.
> Instead, I really just want a feature that contains just the runtime.
>
> What should I do?
>
> - I could include the runtime plugin(s) (org.aspect.runtime, other?) in my
> feature.
> - I could package my own feature that includes that.
> - I could reference an existing feature that I haven't heard of yet, but
> it is out there somewhere...?
>
> Larry Edelstein
> Senior Member of Technical Staff
> Salesforce.com
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02754 seconds
] 
Search
Help
Register
Login
Home
