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

Bug 145168

Summary:	JSF projects are not shareable with a team provider
Product:	[WebTools] Java Server Faces	Reporter:	Panagiotis Korros <panagiotis.korros>
Component:	Core	Assignee:	Gerry Kessler <gerry.kessler>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	major
Priority:	P3	CC:	gerry.kessler
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Panagiotis Korros

2006-06-02 19:34:29 EDT

Using RC3 a jsf project contains links to the local filesystem and that makes the project hard to share using a team provider like CVS.

JSF libraries should utilize the library container mechanism provided by the eclipse jdt and not add individual files. You can copy the 'Java-Build Path-User Libraries' preference page and generaly the way 'user libraries' work in JDT.

A library container would also solve #142056.

Comment 1 Raghunathan Srinivasan

2006-06-05 13:05:36 EDT

Please review.

Comment 2 Gerry Kessler

2006-06-09 19:49:24 EDT

When the JSF Library feature was concieved we desired it to behave like the JDT User Libraries but have WTP specific features like deploy flags and other attributes like the ability to create through extension points.  We recognized the team usage issues at that time also.

What we discovered was:
  - User Library code is all internal and lacks any extensibilty
  - the WTP Server code had no hooks for us to be able to deal with the deployment side of things.

Unfortunately not enough time was allocated to working on this area for this release.  So, we have what we have, and we are very aware of the team issues.



*** This bug has been marked as a duplicate of 142056 ***

Comment 3 Gerry Kessler

2006-06-27 14:42:35 EDT

closed as dupe