I'm ok either way. By explicitly stating the dependency we have a
chance to override the Graphene transitive dependency. OTOH we haven't
had a requirement yet to do so.
If it makes things easier for QE, then go ahead an consolidate the deps.
Brian
On 14-10-07 11:39 PM, Matej Novotny wrote:
Hi,
while I was going through some test dependencies I found out that RF have the following
dependencies:
<version.arquillian.graphene>2.1.0.Alpha1</version.arquillian.graphene>
<version.arquillian.drone>1.3.1.Final</version.arquillian.drone>
But graphene itself has dependency on drone in exactly the same version. And I presume
new versions of Graphene will try to use latest (Final) releases of Drone.
Same goes for arquillian core.
Is there a reason why we need to declare these dependencies specifically? Could/Should we
remove them?
Posted by forums
Original post:
https://developer.jboss.org/message/906306#906306
_______________________________________________
richfaces-dev mailing list
richfaces-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/richfaces-dev