[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: Re: [aspectj-dev] RCP Application working through eclipse but not as an exported application
|
On Nov 27, 2009 3:45pm, Martin Lippert <lippert@xxxxxxx> wrote:
> Hi Mikkel,
>
>
>
> I am not sure what the problem really is but there are several things you could check here:
>
>
>
> - Your aspect bundle defines a require-bundle on the several weaving bundles. This is not necessary and should not be the case for aspect bundles.
My aspect bundle also has alot of UI code in it, should I create a pure aspect plugin?
Is there anything I can put in my config.ini to get even more debug details?
>
>
>
> - Is the aop.xml file copied in your exported plugin? So is it really contained in the JAR file of your bundle in the META-INF directory?
I tripple checked that :) it is in there when exported... I also tried not having the plugin it as a jar-file but a folder-plugin... still no luck... should that matter ?
>
>
>
> - Try to change the start level of weaving.asepctj from 4 to 2 (in your config.ini).
I did that but then it complains about
!ENTRY org.eclipse.equinox.weaving.aspectj 4 0 2009-11-27 20:10:10.985
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.aspectj.weaver; bundle-version="0.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)
[org.aspectj.osgi.service.weaving] info Starting AspectJ weaving service ...
I tried adding start in config.ini - (org.aspectj.weaver@2\:start ) but that gave exception on org.aspecj.runtime not resolved... so I added that aswell... then it started up with no exceptions, but still no weaving....
Do you have an exported demo.zip with a application that runs with aspects?
I run Ubuntu should that matter?
Any other suggestions are very much appriciated!
>
>
> HTH,
>
> Martin
>
>
>
>
>
>
>
> On 27.11.09 07:59, Mikkel Andersen wrote:
>
>
> I exported as a AspectJ supported product, I even checked that the .aj file
>
> is a .class file in the plugin...
>
>
>
> This is my AOP file that is in the META-INF folder...
>
>
>
>
>
>
>
>
>
>
> name="org.plugination.clubadmin.ui.aspects.PropertyChangeSupportAspect"/>
>
>
>
>
>
>
>
> And thats the manifest for the plugin with the aspect in...
>
>
>
> Manifest-Version: 1.0
>
> Bundle-RequiredExecutionEnvironment: JavaSE-1.6
>
> Bundle-ManifestVersion: 2
>
> Bundle-Name: Club Admin UI Plug-in
>
> Bundle-SymbolicName: org.plugination.clubadmin.ui;singleton:=true
>
> Bundle-Version: 1.0.0
>
> Bundle-Activator: org.plugination.clubadmin.ui.UiPlugin
>
> Bundle-Vendor: plugination.org
>
> Eclipse-SupplementBundle: org.plugination.clubadmin.core
>
> Require-Bundle: org.plugination.clubadmin.core,org.eclipse.core.runtim
>
> e,org.eclipse.ui,org.eclipse.jface.databinding,org.eclipse.ui.forms,o
>
> rg.plugination.transactionsystem,org.plugination.undosystem,org.plugi
>
> nation.reportsystem,org.plugination.persistencesystem,com.ibm.icu,org
>
> .eclipse.core.databinding,org.eclipse.core.databinding.beans,org.plug
>
> ination.ui,org.apache.log4j,org.aspectj.runtime;visibility:=reexport,
>
> org.aspectj.weaver;visibility:=reexport,org.eclipse.equinox.weaving.a
>
> spectj;bundle-version="1.0.0",org.eclipse.equinox.weaving.caching;bun
>
> dle-version="1.0.0",org.eclipse.equinox.weaving.caching.j9;bundle-ver
>
> sion="1.0.0",org.eclipse.nebula.widgets.datechooser;bundle-version="1
>
> .0.0",org.eclipse.nebula.widgets.formattedtext;bundle-version="1.0.0"
>
> Bundle-ActivationPolicy: lazy
>
> Export-Package: org.plugination.clubadmin.ui,org.plugination.clubadmin
>
> .ui.aspects
>
>
>
> I cannot see what is wrong? it seems like this line:
>
> info AspectJ Weaver Version 1.6.6 built on Wednesday Sep 30, 2009 at
>
> 18:55:14 GMT
>
> is the first line I am missing in the log file when running outside
>
> eclipse.... any thoughts on why that is not displayed or when it should be
>
> displayed?
>
> Does the plugins exported need to be folders rather then .jar files ? (does
>
> that matter for the weaver)
>
>
>
>
>
> On Fri, Nov 27, 2009 at 2:28 AM, Andrew Eisenbergandrew@xxxxxxxxxxxx>wrote:
>
>
>
>
> It looks like your aspects have not been compiled properly. How did
>
> you export your product? Did you use the Export Product with AspectJ
>
> support?
>
>
>
> On Thu, Nov 26, 2009 at 11:41 AM, Mikkel Andersen
>
> mikkel.t.andersen@xxxxxxxxx> wrote:
>
>
> I followed this example
>
>
>
>
> http://www.eclipse.org/equinox/incubator/aspects/equinox-aspects-quick-start.php
>
>
> and created my own RCP app with a bundle that need weaving, and a bundle
>
> that weaves the aspect in, through LTW.
>
>
>
> This all works when running inside eclipse, but when I export the product
>
>
> it
>
>
> does not work.
>
>
>
> Here is the info I get when running inside eclipse
>
> [org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ...
>
> [org.eclipse.equinox.weaving.
>
> aspectj] info Starting AspectJ weaving service ...
>
> [org.plugination.clubadmin.ui] info AspectJ Weaver Version 1.6.6 built on
>
> Wednesday Sep 30, 2009 at 18:55:14 GMT
>
> [org.plugination.clubadmin.ui] info register aspect
>
> org.plugination.clubadmin.ui.aspects.PropertyChangeSupportAspect
>
> [org.eclipse.equinox.weaving.aspectj] info weaving bundle
>
> 'org.plugination.clubadmin.ui'
>
> [org.plugination.clubadmin.core] info AspectJ Weaver Version 1.6.6 built
>
>
> on
>
>
> Wednesday Sep 30, 2009 at 18:55:14 GMT
>
> [org.plugination.clubadmin.core] info register aspect
>
> org.plugination.clubadmin.ui.aspects.PropertyChangeSupportAspect
>
> [org.eclipse.equinox.weaving.aspectj] info weaving bundle
>
> 'org.plugination.clubadmin.core'
>
> ....
>
>
>
> And here is it when I run outside eclipse
>
> [org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ...
>
> [org.aspectj.osgi.service.weaving] info Starting AspectJ weaving service
>
>
> ...
>
>
> and nothing else...
>
>
>
> This is the config.ini I use
>
>
>
> osgi.bundles=org.eclipse.equinox.common@2
>
>
> :start,org.eclipse.update.configurator@3
>
> :start,org.eclipse.equinox.weaving.aspectj@4
>
> :start,org.eclipse.core.runtime@start
>
>
> osgi.framework.extensions=org.eclipse.equinox.weaving.hook
>
> aj.weaving.verbose=true
>
> org.aspectj.weaver.showWeaveInfo=true
>
> osgi.clean=true
>
> org.aspectj.osgi.verbose=true
>
> eclipse.product=org.plugination.clubadmin.ui.product
>
>
>
>
>
> Any help is appriciated I am kindof lost right now... I am using the
>
>
> 1.6.6
>
>
> version with eclipse 3.5
>
>
>
> _______________________________________________
>
> aspectj-dev mailing list
>
> aspectj-dev@xxxxxxxxxxx
>
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> aspectj-dev mailing list
>
> aspectj-dev@xxxxxxxxxxx
>
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>
>
