Leonardo Uribe schrieb:
On Thu, Jul 31, 2008 at 6:57 AM, [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hazem Saleh schrieb:
Hi Team,
I would like to know whether there are pending tasks on the
next Tomahawk release.
So that I can help.
I think that one thing that needs doing is restructuring the
Tomahawk website.
There used to be just one Tomahawk version, but Leonardo has now
created a separate "tomahawk 1.2.x" project that has increased
JSF1.2 compatibility. I split the "myfaces core" website into
separate JSF1.1 and JSF1.2 parts a while ago; maybe the same needs
to be done for tomahawk, so that people can find the right mvn
reports, javadoc, etc for the different releases?
At the minimum, the existing website would need to be updated to
mention the existence of the two separate lines...
The idea could be do something like Trinidad: a link to 12 version
site inside 11 site, so the user enters first to trinidad and then to
trinidad 1.2.x. It is not as difficult but it takes a lot of time
compiling and testing.
I don't particularly like this structure. I bet 80% of trinidad 1.2.x
users don't notice this extra link and go to pages with wrong
information for their version. It's also makes trinidad 1.2.x a "second
class citizen", with trinidad 1.1.x appearing to be the "main" product.
Which seems backwards to me; shouldn't the emphasis be on the most
recent version? And the more time goes by, the less appropriate this
website structure will be....
I suppose as a temporary measure, Tomahawk could be set up the same. It
is certainly the least work. But it doesn't seem right long-term.
If people don't like having the 1.x and 2.x lines as top-level entries
in the myfaces.apache.org page, then how about creating a new "site"
module at
http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/
which can then hold info common to both the tomahawk subprojects?
Have the "site" module link to the two tomahawk variants (presumably 3
variants when jsf2.0 is released). And then link the main site to that.
Whatever gets done, it would be nice not to break existing
links/bookmarks unless there is a good reason to...
Regards, Simon
