Yes, I will run the tests again.
On 11/9/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 11/8/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
> Hmmm ... but shared will be copied into the core (or tomahawk)
> distribution - there is no shared.jar, so I see no advantage of *not*
> upgrading to the latest shared. This should not introduce a
> incompatibility with any other release. At least this was the idea.
>
> IMHO every release of tomahawk or core should always use the actual
> shared, in the worst case, shared should be released at the same time as
> core or tomahawk respectively.
Up until yesterday, Core 1.1.5 was using Shared 2.0.4, and it was fine.
Thomas, did you run the TCK before or after Martin's change? You
might need to re-do it against Core 1.1.5 + Shared 2.0.5 if that's
what we're going with.
I'm vaguely concerned that there is code in Shared 2.0.5 that goes
with the new Tomahawk code and possibly doesn't belong with Core
1.1.5. But I haven't been paying that much attention to commits, and
it may not even be an issue.
It's slightly less work all around if Core 1.1.5 and Tomahawk 1.1.4
can use the same branch of Shared.
It doesn't matter to me either way, I was just surprised to see the
dependency version change with an explanation of "fixed", since as far
as I know it wasn't a problem.
Once it's decided, please update the Core 1.1.5 release plan and the
project status document.
--
Wendy
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
