[ https://issues.apache.org/jira/browse/IGNITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190817#comment-15190817 ]
Anton Vinogradov commented on IGNITE-642: ----------------------------------------- Yakov, classnames.properties generates automatically during project build (using org.apache.ignite.tools.classgen.ClassesGenerator), but to have correct list during testing developer should: 1) run maven command: mvn clean package -DskipTests 2) replace classnames.properties (at sources) with generated classnames.properties (at target/classes/META-INF). Manual addition of new classes to classnames.properties also possible but not recomended. P.s. It takes more that 20 minutes to investigate this but I have no clue where can I publish this knowledge. Yakov, can you suggest desired location of this knowledge? > Implement IgniteReentrantLock data structure > -------------------------------------------- > > Key: IGNITE-642 > URL: https://issues.apache.org/jira/browse/IGNITE-642 > Project: Ignite > Issue Type: Sub-task > Components: data structures > Reporter: Dmitriy Setrakyan > Assignee: Vladisav Jelisavcic > > We need to add {{IgniteReentrantLock}} data structure in addition to other > data structures provided by Ignite. {{IgniteReentrantLock}} should have > similar API to {{java.util.concurrent.locks.ReentrantLock}} class in JDK. > As an example, you can see how > [IgniteCountDownLatch|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteCountDownLatch.java] > is implemented in > [GridCacheCountDownLatchImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridCacheCountDownLatchImpl.java] > class. > In general we need to have an entity in ATOMIC cache storing lock-owner > identifier together with a queue of waiters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)