[
https://jira.jboss.org/browse/ISPN-456?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani commented on ISPN-456:
------------------------------------
+1. When doing this though, please test carefully to ensure that all existing test suites
don't break.
Also, for the sake of versioning, it makes sense for the parent POM to declare all
versions used. E.g.,
parent/pom.xml:
<properties>
...
<version.jgroups>2.10.0.Beta2</version.jgroups>
...
</properties>
module/my_sub_module/pom.xml:
<dependency>
<groupId>jgroups</groupId>
<artifactId>jgroups</artifactId>
<version>${version.jgroups}</version>
</dependency>
otherwise we end up with having to update versions across several POMs.
Minimize dependencies for Lucene modules
----------------------------------------
Key: ISPN-456
URL:
https://jira.jboss.org/browse/ISPN-456
Project: Infinispan
Issue Type: Task
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 4.1.0.CR1
there are way too much unused jars defined as Maven dependencies, mostly in test scope
but not only.
This is confusing for the best, some people is scared off.
The main goal is to reduce the dependencies for the Lucene Modules, but this will also
unblock the possibility to reduce dependencies for other sub-modules.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira