Gets kind of messy. You'd actually need to separate
spring-orm-hibernate between spring-orm-hibernate2 and
spring-orm-hibernate3. You'd need to split (for now, until Spring 2,
I think) spring-hibernate into spring-hibernate2 and
spring-hibernate3. And then for Hibernate, you might have your
opti
If the dependencies are optional, my POM has to explicitly state the
dependencies
it wants. Kind of defeats the whole purpose of transitive dependencies, right?
There should simply be a seperate POM for each set of dependencies.
ex:
spring-orm-hibernate
spring-orm-jdo
spring-orm-toplink
etc...
Not sure I see what the problem is. Almost all the dependencies are
true, and therefore don't come through
transitively. Therefore you don't need to exclude them.
-Stephen
On 24 Jan 2006 04:40:00 -, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Why oh why is it so painful to setup a new pr
Just to followup, i've posted an issue on JIRA for this:
http://jira.codehaus.org/browse/MEV-313
And here's the corrected link:
http://jroller.com/page/wireframe/?anchor=seperate_artifacts_for_seperate_dependencies
-
To unsubscr