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

Bug 323176

Summary: Classpath dependency enablement should be limited to legacy projects
Product: [WebTools] WTP Java EE Tools Reporter: Jason Peterson <jasonpet>
Component: jst.j2eeAssignee: Jason Peterson <jasonpet>
Status: RESOLVED FIXED QA Contact: Chuck Bridgham <cbridgha>
Severity: enhancement    
Priority: P3 CC: ccc, jsholl
Version: 3.2Flags: cbridgha: review+
Target Milestone: 3.2.2   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
patch
none
updated_patch
none
enablement_patch none

Description Jason Peterson CLA 2010-08-19 13:14:44 EDT 
ClasspathDependencyEnablement has a flag used to control the enablement of the classpath dependency functionality.  The default value is true which enables this functionality.  When set to false it is only enabled for web projects and disabled for all others.  This flag is only used by one specific adopter that now requires the flag control to be more relaxed.  It is desired that now it would only control the enablement for legacy projects.  The new requirement would still have a default value of true.  However, when set to false, it would now be enabled for all JEE projects(EE 5 and above) and disabled for all legacy projects (pre-EE 5).
Comment 1 Jason Peterson CLA 2010-08-23 14:07:16 EDT 
Created attachment 177244 [details]
patch
Comment 2 Jason Peterson CLA 2010-08-23 14:50:21 EDT 
Created attachment 177252 [details]
updated_patch
Comment 3 Jason Peterson CLA 2010-08-23 15:58:40 EDT 
Created attachment 177259 [details]
enablement_patch
Comment 4 Jason Peterson CLA 2010-08-23 15:59:59 EDT 
latest patch removes the restrictions on the deploy path for classpath dependencies.
Comment 5 Jason Sholl CLA 2010-08-24 13:49:58 EDT 
Code checked into head for WTP 3.2.2.
Comment 6 Chuck Bridgham CLA 2010-08-25 13:22:57 EDT 
Please test this thoroughly - and possibly add a junit or two changing the preferences