Hi.
You can either use and version range to
minimize constant update to your dependencies.
Regards,
Edward Yakop
Note:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
http://docs.codehaus.org
[ http://jira.codehaus.org/browse/MEV-103?page=comments#action_48198 ]
Edward Yakop commented on MEV-103:
--
How about making the dependency for both hibernate 2 and hibernate 3 as
provided. This way, if users use hibernate 2 part of the spring code, he can
Evangelism
Type: Bug
Reporter: Edward Yakop
IMHO, spring-hibernate pom.xml should not include both hibernate 2 and
hibernate 3 as its dependencies. Projects will generally use either hibernate 2
or hibernate 3 as its dependency but not both. By creating sub module for both
hibernate 2
Hibernate 2.1.8 pom dependency is empty
---
Key: MEV-77
URL: http://jira.codehaus.org/browse/MEV-77
Project: Maven Evangelism
Type: Bug
Reporter: Edward Yakop
Hibernate 2.1.8 contains no dependency:
4.0.0
hibernate
[ http://jira.codehaus.org/browse/MNG-826?page=comments#action_45751 ]
Edward Yakop commented on MNG-826:
--
Hi,
I'm sorry for the *assigneed* directly, I accidentally cloned a jira issued on
similar problem last night.
Now, in regards to the proble
[ http://jira.codehaus.org/browse/MNG-826?page=comments#action_45727 ]
Edward Yakop commented on MNG-826:
--
Hi,
Sorry for double posting:
* How about introducing a property that make all artifact with
jar iff artifacts packaging is
ejb-client
[ http://jira.codehaus.org/browse/MNG-826?page=comments#action_45726 ]
Edward Yakop commented on MNG-826:
--
1 Need a way to mark all transitive dependency of a java module to be marked
library *hence, added the module as class path item inside MANIFEST.MF
Improve the declaration of 3rd party library and exclusion
--
Key: MNG-826
URL: http://jira.codehaus.org/browse/MNG-826
Project: Maven 2
Type: Improvement
Components: maven-plugins
Reporter: Edward Yakop