[ 
https://issues.apache.org/jira/browse/IGNITE-23679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Daschinsky updated IGNITE-23679:
-------------------------------------
    Fix Version/s: 2.17

> [ducktests] Make sure dependencies from the target release are used in 
> classpath
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-23679
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23679
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Sergey Korotkov
>            Assignee: Sergey Korotkov
>            Priority: Minor
>              Labels: ise
>             Fix For: 2.17
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently all dependencies of ignite-* modules build along with ducktests 
> module are copied to ducktests/target/libs. This directory is added into the 
> classpath for ignite nodes via the USER_LIBS variable. Value of USER_LIBS is 
> prepended to the IGNITE_LIBS one which in turn is passed as *_-cp_* parameter 
> to java.  So jars from ducktests/target/libs are loaded and used before ones 
> from the ignite instance under test.
> This creates problem if most current ducktests (from master branch) are run 
> against some old release and versions of dependencies in master and old 
> release are different.
> ***
> In such case the correct way is to use dependencies from old release, so 
> solution is to not copy them to ducktests/target/libs.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to