Yes, TilesResult is dependent on the snapshot (the published snapshot).
The struts2 build will fail, if and only if, you build tiles locally
against the trunk and then build struts2 against the trunk. I have a
patch ready to apply to struts2, but in order to do that, I need to be
able to publish the new tiles snapshot so that it's available for those
people that don't built tiles. I just got unix permissions to do so
yesterday, and hope to get to it today.
Since we are changing tiles and flushing out the 2.0 api, I don't think
we can prevent this type of failure for people that use snapshots. The
current failure comes from 2 things: the view preparer changes that were
made and the tiles context changes that were made.
I really don't see it as a big deal, because that's precisely what a
snapshot is, an instable artifact that captures the state of the code
base at a certain point of time.
This is a great reason to drive towards an initial release :)
David
Greg Reddin wrote:
On Oct 27, 2006, at 6:40 AM, David H. DeWolf wrote:
Correct, I've got a patch prepared and will commit it once I deploy
the new tiles snapshot - just got my unix perms yesterday.
What happened? Is the TilesResult dependent on a snapshot or nightly
build or what? I would hope we could make changes like this without
breaking people until the changes are done.
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
