Re: [wtp-jsf-dev] Sharing JSF Projects

[David M Williams <david_williams@xxxxxxxxxx>]

Seems valid to me. all system files
in a project, even classpaths, are intended to be shared in a repository,
and, if there is a part of that 
that is "machine specific",
such as were JREs are installed, then they'd be prepresented in the system
file by a variable. So, as long as team members had 
that same variable defined the right
way, or in compatible ways, then all should work fine. 

And, from the stack trace, even if it
was not defined or not defined correctly, the tools should handle it gracefully
with a "configuration error" 
to the log (at least) ... not a Null
Pointer Exception! 

Hope this helps,

Raghu Srinivasan <raghunathan.srinivasan@xxxxxxxxxx>
Sent by: wtp-jsf-dev-bounces@xxxxxxxxxxx

06/02/2006 05:44 PM

Please respond to
Java Server Faces Tools developer discussion <wtp-jsf-dev@xxxxxxxxxxx>

To	Java Server Faces Tools developer discussion <wtp-jsf-dev@xxxxxxxxxxx>
cc
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