Bug #1481
java.privateIncludes: changed libraries are not invalidated
Added by Udo Offermann over 10 years ago.
Updated over 10 years ago.
Description
Given a web-app zIncludingWebApp and a library zIncludableLib where zIncludingWebApp privately includes zIncludableLib.
Both projects are armed.
When a Java class in zIncludableLib is changed the module is not invalidated on the next sync.
- Category changed from z2-base to z2-core
- Status changed from New to In Progress
The problems are somewhat deeper, even without further requirements. The current include handling is simply broken.
See Revisiting_includes_for_2_3.
- Target version set to 2.3
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Feedback
- Assignee changed from Henning Blohm to Udo Offermann
Please retest with the Hippo case.
- Assignee changed from Udo Offermann to Henning Blohm
seems to be compiled with Java 1.7.
- Assignee changed from Henning Blohm to Udo Offermann
- Status changed from Feedback to In Progress
- Assignee changed from Udo Offermann to Henning Blohm
- Assignee changed from Henning Blohm to Udo Offermann
- Status changed from In Progress to New
- Status changed from New to Feedback
- Assignee changed from Udo Offermann to Henning Blohm
test successfully with my hippo project
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by