Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] class missing from eclipse deployment

OK...for now, remove the output jar and let it build to disk.

Open up the .project file.  You should see an entry for ajBuilder, but
*no* entry for javaBuilder.

Now, open the AJDT Event Trace vew and ensure that the default filters
are selected.  Do a full build of project B.  Do you see messages
about Project A?  Do you see messages about weaving classes from
project A?

On Thu, May 14, 2009 at 11:14 AM, Wade Girard <wade.girard@xxxxxxxxx> wrote:
> okay, so here is a breakdown of the setup in eclipse
>
> - project A is a regular java project that is built into a jar and has
> several classes.
> - project B is an aspectJ project that has aspects for project A
>
> in project B's->properties->AspectJ Build Inpath tab I added "Project A"
> in project B's->properties->AspectJ Build Aspect Path tab I have nothing
> (should I add something here, if so what)
> in project B's->properties->AspectJ Build Output jar tab I typed in the name
> of the jar file that the maven build creates
>
> We do use the m2eclipse plugin to create the eclipse projects, that was used
> to create this project.
>
> On May 13, 2009, at 3:14 PM, Andrew Eisenberg wrote:
>
>> Assuming that there *should* be something on you in/aspect path, this
>> might be caused by a bug in the maven-eclpse-plugin in that it doesn't
>> properly configure aspect paths on an eclipse project.
>>
>> See bug 270554 for a way to specify in path and aspect path through maven.
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270554
>>
>> Alternatively, you can use a plugin like m2eclipse that manages it for
>> you.
>>
>> Let me know if this works for you.
>>
>> On Wed, May 13, 2009 at 11:51 AM, Wade Girard <wade.girard@xxxxxxxxx>
>> wrote:
>>>
>>> If it matters...
>>>
>>> When I open up the properties for the project, under the "AspectJ Build",
>>> Inpath and Aspect Path are empty, and in the Output Jar tab the Output
>>> jar
>>> is an empty field.
>>>
>>> AspectJ Compile does not have "Enable project specific settings enabled.
>>>
>>>
>>> On May 12, 2009, at 9:57 PM, Andrew Eisenberg wrote:
>>>
>>>> On Tue, May 12, 2009 at 4:22 PM, Wade Girard <wade.girard@xxxxxxxxx>
>>>> wrote:
>>>>>
>>>>> On May 12, 2009, at 5:28 PM, Andrew Eisenberg wrote:
>>>>>
>>>>>> How is the jar file being created in Eclipse?
>>>>>
>>>>> How should the jar file be created? I can take a peek at the settings.
>>>>
>>>> Well, there are many ways that it could be created: through ant,
>>>> through pde, through eclipse exporting, and there may be others.
>>>>
>>>> I think you said that the compiled aspect class files do not appear in
>>>> the jar that is created through Eclipse.  This means that ajc is not
>>>> being invoked and instead the jdt compiler (or javac) is being
>>>> invoked.
>>>>
>>>> If you can tell me what mechanism is creating the jar, perhaps we can
>>>> figure out why ajc is not being invoked.
>>>>
>>>> --a
>>>
>>> Wade Girard
>>> wade.girard@xxxxxxxxx
>>>
>>>
>>>
>>>
>
> Wade Girard
> wade.girard@xxxxxxxxx
>
>
>
>


Back to the top