Community
Participate
Working Groups
Build Identifier: WTP 3.2.3 This bug is to add limited support for project classpath entries included in classpath containers. This support would allow classpath containers tagged as classpath dependencies to include project classpath entries (only faceted projects) Reproducible: Always
Created attachment 192155 [details] Proposed patch Summary of the changes: - AddClasspathLibReferencesParticipant.java: Add logic to gather project classpath entries provided by child module to parent. - J2EEModuleVirtualComponent.java: Create virtual references to project classpath entries - ClasspathDependencyValidator.java: Do not signal an error when adding a project classpath entry that refers to a faceted project - ClasspathDependencyUtil.java: Include project classpath entries - IFlattenParticipant.java: Add method to get child modules that participant thinks should be added to virtual component - AbstractFlattenParticipant.java: Default implementation for new method - FlatVirtualComponent.java: Include child modules from participants
I ran the entire Java EE JUnit bucket against this patch. I believe that this adds in minimal, required support for this scenario- something that many adopters and users are asking for. I do have concerns about this behavioral change in a maintenance stream, but weighing that concern against the desires of the community and the minimal nature of this change, I agree to its inclusion.
I also have investigated these changes, and have run tests. The behavior change is simply "including" referenced projects from within a mapped classpath container, where they were ignored before. This is an important incremental step in this maintenance release, and will revisit for inclusion in later releases.
Committed to R3_2_maintenance and HEAD for WTP 3.2.4 and WTP 3.3 M7
