Hi,
I see Leonard is currently doing a lot of work on something called tomahawk
1.2, which surprised me a little.
I have checked the mail archives, and see some discussions happening around
june 2007 regarding having a version of tomahawk specifically for JSF1.2.
But since then, we have
I think that Leonardo is working on generating the components classes
tlds, facelet-taglibs with the maven-faces-plugin - I'm pretty sure
this makes sense.
As this will then mean there is a switch to either use JSF1.2 or 1.1
in the generation (hopefully this will work) both 1.1.7 and a 1.2
based
Hi,
On Jan 30, 2008 9:53 AM, Simon Kitching [EMAIL PROTECTED] wrote:
Hi,
I see Leonard is currently doing a lot of work on something called tomahawk
1.2, which surprised me a little.
I have checked the mail archives, and see some discussions happening around
june 2007 regarding having a
Hi,
As being the guy who has created the tomahawk 1.2 branch and spent a lot of
time with it, upgrading to 1.2 is not an easy task because as Simon
mentioned the code is old and crusty.
I agree that non rendering stuff should be moved to commons, I've some
candidates on my own from sandbox and
If tomahawk is going to be split into pieces, then it really does not make
sense to completely change the build approach. It currently works, so let's
just stay with what is already there.
Regards, Simon
Martin Marinschek [EMAIL PROTECTED] schrieb:
I think that Leonardo is working on
For me, it would be important that this new build-system could
generate 1.1.7 and 1.2 - Leonardo, would this be possible?
regards,
Martin
On 1/30/08, Simon Kitching [EMAIL PROTECTED] wrote:
Hi,
Well, the first question to ask is: what do we want to release in the near
future?
I think the
I think if something simplifies the maintenance of tomahawk I welcome
it. Moving stuff to commons and all that is an early idea and I have
not read specific plans about how we could do that, who could do that,
so I guess it will take a while to go. In the meanwhile, if we can
just remove some of
Hi,
Well, the first question to ask is: what do we want to release in the near
future?
I think the next Tomahawk release should be 1.1.7, containing bugfixes and a
few promotions from sandbox. It should not contain radical refactoring of the
build process.
In the longer term, I believe we
Simplify???
This code generation stuff does make code more *consistent* between the various
bits (taglib, faces-config, java) but definitely does not make it simpler to
work with. IMO, it introduces a whole new set of concepts that will make it
harder for new developers to get into this code.
Hi!
This code generation stuff does make code more *consistent* between the
various bits (taglib, faces-config, java) but definitely does not make it
simpler to work with. IMO, it introduces a whole new set of concepts that
will make it harder for new developers to get into this code.
I
Paul Spencer [EMAIL PROTECTED] schrieb:
I am very invested in Tomahawk. I agree we need to simplify things, but
we MUST maintain Tomahawk. If we do not, then who will use ANY of the
MyFaces component libraries if we let libraries die.
Absolutely nobody is suggesting that Tomahawk
I am very invested in Tomahawk. I agree we need to simplify things, but
we MUST maintain Tomahawk. If we do not, then who will use ANY of the
MyFaces component libraries if we let libraries die.
Paul Spencer
Martin Marinschek wrote:
Simon,
is your conclusion then that Tomahawk should
My thoughts:
1. Release 1.1.7 with moving some of the non-render components from
sandbox (I think the PPR would be better in a new library personally)
2. (Rest are post 1.1.7) move any components that work with any render
kit, and are graphical into a new project (or make this
On Jan 30, 2008 7:16 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
we could add a runtime dependency to commons
and the t:validateEmail tag points to the TAG-CLASS from commons
(no double code )
Yes, This is my intention. For avoid generation on tomahawk I use
On Jan 30, 2008 7:18 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
looks like Tobago and Tomahawk might be interested in
sharing a dojo-based common jar ?
We can use the same as with validators:
component-class-excludedtrue/component-class-excluded
tag-class-excludedtrue/tag-class-excluded
15 matches
Mail list logo
