I took MyFaces 1.2.0 and stripped somewhere around 80% of the classes.
Pretty much ripped out everything but org.apache.myfaces.config package.
Doing this gives you just enough to parse versions 1.0, 1.1 and 1.2 of
faces-config files using two lines of code.
ByteArrayInputStream bais = new ByteArrayInputStream(
Here are the costs of going this route. This introduces a dependency on
digestor, commons logging, beanutils and commons collections. It also means
we have to maintain the myfaces-stripped jar until the config stuff gets
moved into the new myfaces commons project (which probably won't be released
before JSFUnit). It also means we have to ping a lawyer because I have
never done this before (change ASF artifact, release under LGPL).
Let me know your thoughts. I timeboxed this at an hour so I don't have a
lot of emotions behind going this route. Part of me feels like just
benching this until after the release.
I'm setting a date for our first beta release of November 30th. There
are a couple of reasons we need to release on that date:
1) It is one week before I'll talk about JSFUnit at Javapolis, so we
need to have a release before then.
2) Part of my bonus depends on a November release. (Nothing like full
Looking ahead at the calendar, Dennis and I will miss a couple of weeks
of development in November due to ApacheCon and the Thanksgiving
holiday. So I think it is wise to declare a feature freeze at the end
of next week, Sunday November 4th. Then we can concentrate on
documentation and bug fixes.
Does that sound reasonable to everyone? Any thoughts?
Hey guys. I'm getting real tired of parsing XML. I'd like to point a
marshaling framework at these faces-config files. Does anyone have any
objections? If not, preferences? My preference is to just extract the
digester code from MyFaces rather than go all out with JAXB.
I'm pretty new to Hudson too, but I like it so far. It's really easy to
set up automated builds.
As far as I can tell, "S" stands for success. You get a blue ball for
success, red for failure, and yellow for unstable.
I think "W" must stand for weather. I'm not sure how it decides what
the weather is, but it seems to depend on the last few builds. If you
hover over the weather icon you get some stats about the last 5 builds.
It looks like JBossSeam-sun15 even has some code coverage stats as
part of the calculation.
Dennis Byrne wrote:
> Cool. What do the "S" and "W" column headers stand for? (Have not used
> Hudson before).
> Dennis Byrne
> On 10/5/07, *Stan Silvert* <ssilvert(a)redhat.com
> <mailto:email@example.com>> wrote:
> You can now view builds at http://hudson.jboss.org/hudson/job/JSFUnit/
> A build including checkout, compile, and all unit tests is kicked off
> within one hour of any commit. Keep it sunny.
> jsfunit-dev mailing list
> jsfunit-dev(a)lists.jboss.org <mailto:firstname.lastname@example.org>
> Dennis Byrne