[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-jsf-dev] Sharing JSF Projects
|
The dependencies can be cleaned up using J2EE Module Dependencies
property page.
However, I didn't find dependencies got cleaned up all the time when
deselecting a/all JARs.
Hence, I entered a comment to clean up dependencies manually instead of
using J2EE Module
Dependencies since I am unable to reproduce deselecting dependency error
in a consistent way yet.
Justin
Ian Trimble wrote:
I agree that this is a similar case to classpath variables, since both variables and the JSF Library Registry are specific to the workspace.
However, I don't feel it's an ideal solution to ask the user to perform manual cleanup by editing the org.eclipse.wst.common.component file.
Can we not allow the user to cleanup via UI? Detecting the condition, automating cleanup, and then prompting for a new JSF Library may not be doable, but that'd be even better if it were possible.
- Ian
-----Original Message-----
From: wtp-jsf-dev-bounces@xxxxxxxxxxx
[mailto:wtp-jsf-dev-bounces@xxxxxxxxxxx]On Behalf Of Raghu Srinivasan
Sent: Friday, June 02, 2006 2:44 PM
To: Java Server Faces Tools developer discussion
Subject: [wtp-jsf-dev] Sharing JSF Projects
Hi,
Don't think this is a valid bug since the JSF registry, like other
classpath containers are local to the workspace. comment?
-Raghu
https://bugs.eclipse.org/bugs/show_bug.cgi?id=142456
_______________________________________________
wtp-jsf-dev mailing list
wtp-jsf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-jsf-dev
_______________________________________________
wtp-jsf-dev mailing list
wtp-jsf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-jsf-dev
