I think we should have Facelts in the
component name because the incubator project works on the current Facelets implementation
and we would like the current Facelets users to use the incubator project and
log issues against it. JSF2 will not make sense for the target user community. The
connection to JSF2 is that once the spec is released, the work in the incubator
project can be used to run a js2-facelts application. I could call the component
jsf2-facelts, but it’s not my first choice.
Also, we now have an inbox called wtp.inc.facelets-inbox@xxxxxxxxxxx
to match ‘Facelts’ as the component name.
-Raghu
From: David M Williams [mailto:david_williams@xxxxxxxxxx]
Sent: Wednesday, June 04, 2008
9:36 PM
To: WTP Incubator Dev list
Subject: [wtp-incubator-dev]
faclets ==> jsf2 ?
Now that I think about it, shouldn't the name of this
component be jsf2? Or similar?
That
seems to be what was in the original incubating component proposal.
I
know that the facelet part of that as-yet-not-standard-and-not-published 2.0
specification is your main interest,
but
I think that might help avoid confusion with the current non-standard facelet
implementations.
So,
let's call it, jsf2 or something, ok?
Thanks,
|
From:
|
David M Williams/Raleigh/IBM@IBMUS
|
|
To:
|
wtp-incubator-dev@xxxxxxxxxxx
|
|
Date:
|
06/05/2008 12:07 AM
|
|
Subject:
|
[wtp-incubator-dev] FYI: new XSL Bugzilla component:
wtp.inc.xsl
|
I think it might make XSL team's life a tiny bit easier if they had their own
component in bugzilla,
so I have created it. It's named simply to "follow" the
project-subproject-component structure, if you are wondering.
So, I suggest interested parties subscribe themselves to the inbox.
I've set Doug as QA contact ... as far as I know, absolutely no one uses that
... but, looks better to have a person
named there, and since Doug is technically the component lead, picked him. But,
there's not reason it _has_ to be
that way, if you all decide amongst yourselves you'd prefer it otherwise, let
me know.
name: wtp.inc.xsl
default assignee: wtp.inc.xsl-inbox@xxxxxxxxxxx
default QA contact: doug.satchwell@xxxxxxxxxxxxxx
= = = = = =
I think Raghu will be doing some thing similar for the faclets incubator.
Raghu, I suggest you follow the same project-subproject-component structure,
which would make it
wtp.inc.facelets
which is a little different than what we discussed before, so thought I'd be
explicit here.
= = = = = =
In both case, once these components graduate, if ever :)
then we can rename or create another component name at that time.
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
