We really appreciate your effort, Jesse ;-)
Thanks... After all I should profit as well, getting maybe one or two
components that I can reuse in our applications ;-)
And feel free to help out:
- ask for components
- test components as they become available
- write your own components and make them available
Any guidelines regardring the package names for the components, how
the components can be sent in etc...?
None so far.
What are our options?
c) whatever.you.want.... (almost whatever...)
- I believe a) is out of discussion, because of org.apache rules
- b) and c) remain valid options
2) a) all component-parts in one package-branch
b) all similar artifacts for all components in the same package-branch
c) all components of one committer in one package-branch
Here I have no preference at all. So describe your ideas.
I would be interested as well, to be able to commit, to start dumping
code by tomorrow (gotta pack it up for the jar distribution first, which
in case of JSF is new to me, I have to find out what has to go in there,
and make a small webapp
which uses them)
Well that distribution format:
- in "JSF in Action" there is a description in chapter 15.7 "Packaging
UI extensions" (page 660/661).
- the class- and property-files (as usual)
- in the META-INF directory
- put the tld file for your tags
- write the "partial" faces-config into a well-formed faces-config.xml
That's it. Your "customer" just has to drop the jar-file into WEB-INF/lib,
restart his web-container and your components are available.
forgot to mention, my sourceforge name is werpu12
done. Welcome on board.