En l'instant précis du 19/03/08 11:45, Stephen Connolly s'exprimait en
ces termes:
well I would have
jsf-api as scope=provided
I would not depend on jsf-impl
Indeed, i could add a provided rule at top of tree for both :) I bet i
didn't think enough about it :D Note that it didn't explicitly add
jst-api/impl to our tree, it's a transitive dependency that comes at
least with richfaces ^^, maybe with some other jsf components
You will be deploying this application to a container that provides the api
and it's impl. You should not be depending on any of the impl classes, so
that would be my logic.
If you then have customers that want to deploy to a container that does not
supply a JSF impl, you could have assembler produce two distributions for
these customers:
1. with the JSF-api and JSF-impl
2. with the myfaces-api and myfaces-impl
Generated artefact is for internal use only, and we need myfaces in it
(tomcat does not provide it ;) ). However, am curious. How do you ask
maven2 to produce several artefacts with different dependency
tree/different resources. I'm interrested in being able to generate
artefact for test and production at the same time (you send the war to
test, if it's ok, you already have it's corresponding production war,
which includes it's production configuration)
--
David Delbecq
Institut Royal Météorologique
Ext:557
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
