You may take a look at http://jira.codehaus.org/browse/MEV-133
I've setup poms for spring 1.2.5 to make all the tools spring supports
optionnal and reduce transitive dependencies to expected ones.
Brian Bonner a écrit :
I'm working with Spring 1.2.5 and retrofitting an older application
that makes use of spring-jdbc and spring-dao. I'm curious how other
folks are using this because I have exclusions out the ying-yang.
I'd like to make some suggestions of jars that should be optional.
I'm even happy to post my dependencies in MEV if they would help.
It's my understanding that if we added <optional>true</optional> to
the poms makes the jars optional. But this only applies for projects
that are dependent upon that component, correct?
How are other people using this?
Here's what I have:
* xmlbeans-project
* service-project (uses spring)
* web-project (depends on service-project and xmlbeans-project) and
adds some other spring dependency as well as others.
Right now, when I war up the web-project, I get the needed
dependencies in the service-project for it to run, but there are a ton
of them defined (and it seems like most of them are exclusions) I
guess I'd rather add things as they fail rather than have 20 billion
jars.
Thoughts?
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
