Am 31.07.2006 um 13:13 schrieb Barrie Treloar:
It would be nice for convenience
to have
a kind of maven project, which for example could be called
'application-x-ejb-client',
that bundles the dependencies for a client and might help deliver
them all
by providing a single dependency declaration on application-x-ejb-
client
in thw web client's POM.
I'm not doing web development.
I have no notion of how many ejb-clients you would normally have.
Unless you can get some regular expression magic to help import things
you would need to declare your dependencies in your
"application-x-ejb-client" project and these exact ones would be
needed in your client as well. Whether you declare them in
application-x-ejb-client or in your client pom they still need to be
declared. The only benefit I could see would be if you had more than
one client and by creating this extra project you can apply DRY (don't
repeat yourself). Otherwise I can't see any benefit.
Indeed, DRY is one benefit I want to get and we have several clients.
But think of a typical scenario, where client and middleware is
developed by separate
teams. You get decoupling of client dependency from client artifact
naming, versioning and partitioning,
which is controlled by the middleware team, if you use an
intermediate 'application-x-ejb-client' project.
-
Roland
I think it is important to explicit list your dependencies, otherwise
you pull in cruft and the kitchen sink unnecessarily.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
______________________________________________________________
Roland Förther 100world.com AG
[EMAIL PROTECTED] www.100world.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
