On 9/8/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Because the APIs will have to match (signature tests are part of the TCK), I agree that it should not matter which api jar you *compile* against ... but (at least in the Ant build) the same property is used to pick up the jar file used to build webapps with. Therefore, it seems simpler to adjust both pointers when you switch implementations.
Craig
From: "Matthias Wessendorf" <[EMAIL PROTECTED]>
> I think when you gals and guys compile Shale, then only against
> JSF-API. If not, Shale depends on RI or MyFaces. These api clazzes are
> inside of myfaces api jar file.
I'm reproducing the Ant build with Maven, and the Ant build does have the
option of compiling against either your myfaces-api.jar file or the
jsf-api.jar file. Craig must have thought it was important. :)
Because the APIs will have to match (signature tests are part of the TCK), I agree that it should not matter which api jar you *compile* against ... but (at least in the Ant build) the same property is used to pick up the jar file used to build webapps with. Therefore, it seems simpler to adjust both pointers when you switch implementations.
Craig
For the record, (since Matthias and I talked about it off-list,) I've placed
the .jar files from the MyFaces 20050904 nightly build in Apache's internal
Maven repository so I can have the Shale build depend on it. This does not
get mirrored to ibiblio, it's for internal dependencies among Apache
projects that are using Maven. There's a snapshot of Standalone Tiles there
as well, for the same reason.
--
Wendy Smoak
