Hi Kaelin,
it seems to be a problem with the WOLips classpath container and
aspectj. Please add a bug report:
Thanks
Ulrich
Am 23.12.2003 um 10:37 schrieb Kaelin Colclasure:
> Replying to my own post (yes, it's late), I came across the StepWise
> article that shows how to patch Project Builder's JAM files to work
> with an older version of AspectJ. This is encouraging, but not exactly
> what I need, as WOLips is my WebObjects environment of choice.
>
> I did manage to get some methods advised by compiling with ajc from
> the command line -- tres cool! But of course, this misses out on all
> the Eclipse integration features (the most useful being annotations in
> the gutter of the editor panes as to which aspects advise which
> methods). Still, this looks to be a very useful trick to have up one's
> sleeve, so long as aspects are being used only in development.
>
> This AspectJ stuff is pretty exciting. It reminds me of when I first
> picked up Brad Cox's book almost two decades ago... (1986! Sheesh,
> that's scary.)
>
> -- Kaelin
>
> On Dec 22, 2003, at 11:53 PM, Kaelin Colclasure wrote:
>
>> It has occurred to me on several occasions that AspectJ might be an
>> invaluable tool for learning the ins and outs of WebObjects. Has
>> anyone on these lists experimented with this? I've just tried
>> installing the latest (1.1.4) AJDT Eclipse plugin, but it
>> unfortunately does not seem to play well with WOLips.:
>>
>> !ENTRY org.eclipse.ajdt.ui 4 0 Dec 22, 2003 21:22:08.892
>> !MESSAGE Compile failed.
>> !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ajdt.internal.ui.ajde.ProjectProperties.getClasspath(Proje
>> ctProperties.java:206)
>> at org.eclipse.ajdt.internal.builder.Builder.build(Builder.java:150)
>> at
>> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:
>> 427)
>> at
>> org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatfor
>> m.java:1006)
>> at org.eclipse.core.runtime.Platform.run(Platform.java:413)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.
>> java:125)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.
>> java:181)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.
>> java:191)
>> at
>> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:
>> 151)
>> at
>> org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatfor
>> m.java:1006)
>> at org.eclipse.core.runtime.Platform.run(Platform.java:413)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.
>> java:165)
>> at
>> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:
>> 265)
>> at org.eclipse.core.internal.resources.Project.build(Project.java:85)
>> at
>> org.eclipse.ajdt.internal.ui.PulldownBuildselectorMenu$1.run(PulldownB
>> uildselectorMenu.java:295)
>> at
>> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalC
>> ontext.java:101)
>>
>> I suspect that this is because WOLips has its own Builder classes (I
>> believe) which (presumably) handle classpath metadata differently
>> from the standard Eclipse Builder.
>>
>> Using the AspectJ Ant tasks also seems to be a non-starter. It's
>> designed as essentially a drop-in replacement for the javac Ant task
>> -- but again, WOProject Ant build files do not use the javac task.
>> Compiling is apparently all handled in the bowels of the
>> woapplication or woframework tasks instead. While this does make the
>> build files substantially more concise, it would appear to also make
>> it impossible to use alternative Java compilers in conjunction with
>> WOProject... Or is there (hopefully) something I'm missing?
>>
>> -- Kaelin
>>
>
This archive was generated by hypermail 2.0.0 : Tue Dec 23 2003 - 05:13:15 EST