Home » Language IDEs » AspectJ » PDE + AJDT = OMGBBQ
| PDE + AJDT = OMGBBQ [message #40950] |
Tue, 28 September 2004 19:17  |
Eclipse User |
|
|
|
Originally posted by: Ben.Youngdahl.gmail.com
I have a plugin, "X", which needs to be woven with an Aspect "Foo" defined
in plugin "A." All plugins have a dependency on AJDE. Plugin "X" depends on
plugin "A." "Foo" is defined such that its pointcuts will definitely select
joinpoints in "X."
It seems I have to get "Foo" onto the aspect path for plugin "X". I can only
do that by using a JAR. Therefore, I must have plugin "A" generate a JAR.
Generating a JAR in "A" means a "\bin" directory isn't updated, just the
JAR. This appears to have serious issues with self-hosting in Eclipse;
specifically, I can't seem to get Eclipse to use JAR-based rather than
"\bin" classpathes when running in a runtime workbench launch config.
Thanks for any suggestions you can give.
|
|
|
| Re: PDE + AJDT = OMGBBQ [message #41412 is a reply to message #40950] |
Fri, 01 October 2004 16:20  |
| Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
On Tue, 28 Sep 2004 14:17:49 -0500, Ben Youngdahl wrote:
> I have a plugin, "X", which needs to be woven with an Aspect "Foo"
> defined in plugin "A." All plugins have a dependency on AJDE. Plugin "X"
> depends on plugin "A." "Foo" is defined such that its pointcuts will
> definitely select joinpoints in "X."
>
> It seems I have to get "Foo" onto the aspect path for plugin "X". I can
> only do that by using a JAR. Therefore, I must have plugin "A" generate
> a JAR. Generating a JAR in "A" means a "\bin" directory isn't updated,
> just the JAR. This appears to have serious issues with self-hosting in
> Eclipse; specifically, I can't seem to get Eclipse to use JAR-based
> rather than
> "\bin" classpathes when running in a runtime workbench launch config.
>
> Thanks for any suggestions you can give.
Hi,
I think you just need to add your generated JAR as a runtime library for
plugin "A". In self-host mode Eclipse looks for libraries defined in
plugin.xml as well as bin directories.
So if your output jar for plugin "A" is called "out.jar", you need to add
that to the aspect path of plugin "X", and as a library in the
runtime section of the plugin.xml for plugin "A":
<runtime>
<library name="out.jar">
<export name="*"/>
</library>
</runtime>
Hope that reduces the "OMGBBQ" :)
Matt.
|
|
|
| Re: PDE + AJDT = OMGBBQ [message #42120 is a reply to message #41412] |
Mon, 04 October 2004 17:36 |
 Ben Youngdahl
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hey Matt,
I had tried what you have suggested prior to my original post and had had no
luck. I should note that I was using the OSGi manifests, which necessitated
a change to the manifest file rather than plugin.xml, but the result should
have been the same -- the JAR with the aspect defined in A should have been
visible to plugin X at runtime. I was still getting class not found
exceptions when running in PDE self-hosting mode. I made sure my run-time
launch configuration had the necessary plugins.
Some posts in parallel in this newsgroup by others appear to address similar
issues, and I have seen a few replies that the handling of the classpath has
changed a bit in the most recent dev builds. I'm going to try to use the
latest dev build and see if that doesnt' fix the issues. If not, I'll open
a bug report and attach the files that I think illustrate the problem.
And yes, the OMGBBQ is reduced; thanks for the reply.
Ben
"Matt Chapman" <mchapman@uk.ibm.com> wrote in message
news:pan.2004.10.01.16.20.56.546993@uk.ibm.com...
> Hi,
>
> I think you just need to add your generated JAR as a runtime library for
> plugin "A". In self-host mode Eclipse looks for libraries defined in
> plugin.xml as well as bin directories.
>
> So if your output jar for plugin "A" is called "out.jar", you need to add
> that to the aspect path of plugin "X", and as a library in the
> runtime section of the plugin.xml for plugin "A":
>
> <runtime>
> <library name="out.jar">
> <export name="*"/>
> </library>
> </runtime>
>
> Hope that reduces the "OMGBBQ" :)
>
> Matt.
>
|
|
|
| Re: PDE + AJDT = OMGBBQ [message #42365 is a reply to message #42120] |
Tue, 05 October 2004 10:21 |
| Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
Sounds good.
If you still have problems, I'd also ask you to try without using OSGi
manifest files directly - I've hit problems with those before.
Matt.
On Mon, 04 Oct 2004 12:36:35 -0500, Ben Youngdahl wrote:
> Hey Matt,
>
> I had tried what you have suggested prior to my original post and had had
> no luck. I should note that I was using the OSGi manifests, which
> necessitated a change to the manifest file rather than plugin.xml, but the
> result should have been the same -- the JAR with the aspect defined in A
> should have been visible to plugin X at runtime. I was still getting
> class not found exceptions when running in PDE self-hosting mode. I made
> sure my run-time launch configuration had the necessary plugins.
>
> Some posts in parallel in this newsgroup by others appear to address
> similar issues, and I have seen a few replies that the handling of the
> classpath has changed a bit in the most recent dev builds. I'm going to
> try to use the latest dev build and see if that doesnt' fix the issues.
> If not, I'll open a bug report and attach the files that I think
> illustrate the problem.
>
> And yes, the OMGBBQ is reduced; thanks for the reply.
>
> Ben
|
|
| |
| Re: PDE + AJDT = OMGBBQ [message #583471 is a reply to message #40950] |
Fri, 01 October 2004 16:20 |
Matt Chapman
Messages: 429
Registered: July 2009 |
Senior Member |
|
|
On Tue, 28 Sep 2004 14:17:49 -0500, Ben Youngdahl wrote:
> I have a plugin, "X", which needs to be woven with an Aspect "Foo"
> defined in plugin "A." All plugins have a dependency on AJDE. Plugin "X"
> depends on plugin "A." "Foo" is defined such that its pointcuts will
> definitely select joinpoints in "X."
>
> It seems I have to get "Foo" onto the aspect path for plugin "X". I can
> only do that by using a JAR. Therefore, I must have plugin "A" generate
> a JAR. Generating a JAR in "A" means a "\bin" directory isn't updated,
> just the JAR. This appears to have serious issues with self-hosting in
> Eclipse; specifically, I can't seem to get Eclipse to use JAR-based
> rather than
> "\bin" classpathes when running in a runtime workbench launch config.
>
> Thanks for any suggestions you can give.
Hi,
I think you just need to add your generated JAR as a runtime library for
plugin "A". In self-host mode Eclipse looks for libraries defined in
plugin.xml as well as bin directories.
So if your output jar for plugin "A" is called "out.jar", you need to add
that to the aspect path of plugin "X", and as a library in the
runtime section of the plugin.xml for plugin "A":
<runtime>
<library name="out.jar">
<export name="*"/>
</library>
</runtime>
Hope that reduces the "OMGBBQ" :)
Matt.
|
|
|
| Re: PDE + AJDT = OMGBBQ [message #583798 is a reply to message #41412] |
Mon, 04 October 2004 17:36 |
Ben Youngdahl
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hey Matt,
I had tried what you have suggested prior to my original post and had had no
luck. I should note that I was using the OSGi manifests, which necessitated
a change to the manifest file rather than plugin.xml, but the result should
have been the same -- the JAR with the aspect defined in A should have been
visible to plugin X at runtime. I was still getting class not found
exceptions when running in PDE self-hosting mode. I made sure my run-time
launch configuration had the necessary plugins.
Some posts in parallel in this newsgroup by others appear to address similar
issues, and I have seen a few replies that the handling of the classpath has
changed a bit in the most recent dev builds. I'm going to try to use the
latest dev build and see if that doesnt' fix the issues. If not, I'll open
a bug report and attach the files that I think illustrate the problem.
And yes, the OMGBBQ is reduced; thanks for the reply.
Ben
"Matt Chapman" <mchapman@uk.ibm.com> wrote in message
news:pan.2004.10.01.16.20.56.546993@uk.ibm.com...
> Hi,
>
> I think you just need to add your generated JAR as a runtime library for
> plugin "A". In self-host mode Eclipse looks for libraries defined in
> plugin.xml as well as bin directories.
>
> So if your output jar for plugin "A" is called "out.jar", you need to add
> that to the aspect path of plugin "X", and as a library in the
> runtime section of the plugin.xml for plugin "A":
>
> <runtime>
> <library name="out.jar">
> <export name="*"/>
> </library>
> </runtime>
>
> Hope that reduces the "OMGBBQ" :)
>
> Matt.
>
|
|
|
| Re: PDE + AJDT = OMGBBQ [message #583957 is a reply to message #42120] |
Tue, 05 October 2004 10:21 |
Matt Chapman
Messages: 429
Registered: July 2009 |
Senior Member |
|
|
Sounds good.
If you still have problems, I'd also ask you to try without using OSGi
manifest files directly - I've hit problems with those before.
Matt.
On Mon, 04 Oct 2004 12:36:35 -0500, Ben Youngdahl wrote:
> Hey Matt,
>
> I had tried what you have suggested prior to my original post and had had
> no luck. I should note that I was using the OSGi manifests, which
> necessitated a change to the manifest file rather than plugin.xml, but the
> result should have been the same -- the JAR with the aspect defined in A
> should have been visible to plugin X at runtime. I was still getting
> class not found exceptions when running in PDE self-hosting mode. I made
> sure my run-time launch configuration had the necessary plugins.
>
> Some posts in parallel in this newsgroup by others appear to address
> similar issues, and I have seen a few replies that the handling of the
> classpath has changed a bit in the most recent dev builds. I'm going to
> try to use the latest dev build and see if that doesnt' fix the issues.
> If not, I'll open a bug report and attach the files that I think
> illustrate the problem.
>
> And yes, the OMGBBQ is reduced; thanks for the reply.
>
> Ben
|
|
| |
Goto Forum:
Current Time: Thu Apr 25 22:52:55 GMT 2024
Powered by FUDForum. Page generated in 0.04013 seconds |
] 
Search
Help
Register
Login
Home
