Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360331

Summary:	Changes in aop.xml ignored by build process
Product:	[Tools] AspectJ	Reporter:	Grzegorz Abramczyk <gapage>
Component:	Build	Assignee:	aspectj inbox <aspectj-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	P3	CC:	aclement, gapage
Version:	1.6.12
Target Milestone:	1.6.12
Hardware:	PC
OS:	Windows Vista
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=329126
Whiteboard:

Description Grzegorz Abramczyk

2011-10-08 15:07:20 EDT

Build Identifier: 20110916-0149

When using AspectJ Bulider customized by aop.xml file changes in the file are not reflected in build process.

It looks like it is caused by fix for Bug 329126 introducing caching of configuration. 

I have found two workarounds:
* To restart IDE
* To add -Dorg.aspectj.weaver.loadtime.configuration.cache=false into eclipse.ini
Nevertheless bug is annoying and second fix may cause bug 329126 to reappear.

Moreover it would be nice if saving aop.xml would cause rebuild without manual request by user. 

Reproducible: Always

Steps to Reproduce:
1. Create "Bean Example" from AspectJ Examples
2. Add to project aop.xml with content:
<!DOCTYPE aspectj PUBLIC
        "-//AspectJ//DTD//EN" "http://www.eclipse.org/aspectj/dtd/aspectj.dtd">
<aspectj>
	<weaver>
		<exclude within="bean.*" />		
	</weaver>
	<aspects>
		<aspect name="bean.BoundPoint"/>
	</aspects>
</aspectj>
3. Add aop.xml to aop.xml management
4. Rebuild project
5. Change exclude to include in aop.xml
4. Rebuild project

Comment 1 Andrew Clement

2011-10-11 12:16:44 EDT

Raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=360559 to cover your request for auto builds on aop.xml changes.

Switched off cache when incremental builds can occur (so under AJDT).