If alchemy is already written, then we'll need to complete IP clearance.
Scott
Gerhard Petracek wrote:
hello,
i had just a very quick look at it.
do you plan to support existing jsf artifacts (e.g. converters,
validators,...)?
@subproject and name:
for each topic you have to start at least a vote.
what's about the following idea:
let's start a subproject for component libs like alchemy.
in the future it might be nice to have also a component lib for e.g.
javafx,...
[new subproject]
|_ [alchemy]
|_[...]
regards,
gerhard
2008/5/13 Jihoon Kim <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
> I would suggest that the best place would be as a new
subproject, like
> "orchestra" or "portlet bridge" are. It would definitely belong
in the
> MyFaces family (rather than anywhere else in Apache) but I
don't think
> it fits as part of Tomahawk. As I noted earlier, people who use
tomahawk
> won't always want Flex, and people who want Flex won't always
want the
> other tomahawk components.
>
> It could also be a new "myfaces commons" module, but we haven't
really
> figured out how to structure those anyway. And it isn't really
a "common
> module", but a component library just like tomahawk is.
So is there any documentation in regards to how a code becomes a
subproject of MyFaces? I would like to possibly look into that area,
since if that is the path that might be taken; I would like to know of
the process ahead of time.
I did previously read through the process within the incubator, but
wasn't sure if that was solely for a standalone project or applies to
subproject as well.
In the case that the contribution does get accepted and does become a
subproject, I even have a name that I would like to propose, which is
alchemy.
Thanks!!!
--
Sincerely,
Ji Hoon Kim
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
