July 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-106: --------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/73 > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. > This is already leading to failures in Infinispan https://ci.infinispan.org/job/Infinispan/job/master/1304/consoleFull#1277... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Work on IPROTO-106 started by Nistor Adrian. -------------------------------------------- > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. > This is already leading to failures in Infinispan https://ci.infinispan.org/job/Infinispan/job/master/1304/consoleFull#1277... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-106: --------------------------------- Description: The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. This is already leading to failures in Infinispan https://ci.infinispan.org/job/Infinispan/job/master/1304/consoleFull#1277... was:The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. > This is already leading to failures in Infinispan https://ci.infinispan.org/job/Infinispan/job/master/1304/consoleFull#1277... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-106: --------------------------------- Sprint: DataGrid Sprint #31 > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-106: --------------------------------- Status: Open (was: New) > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Nistor Adrian reassigned IPROTO-106: ------------------------------------ Assignee: Nistor Adrian > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-106: --------------------------------- Fix Version/s: 4.3.0.Alpha9 > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.jboss.org/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Nistor Adrian (Jira)

Nistor Adrian created IPROTO-106: ------------------------------------ Summary: OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar Key: IPROTO-106 URL: https://issues.jboss.org/browse/IPROTO-106 Project: Infinispan ProtoStream Issue Type: Enhancement Reporter: Nistor Adrian The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10430) Fix JdbcStringBasedStoreFunctionalTest thread leak

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10430?page=com.atlassian.jira.plugin... ] Katia Aresti reassigned ISPN-10430: ----------------------------------- Assignee: Katia Aresti > Fix JdbcStringBasedStoreFunctionalTest thread leak > -------------------------------------------------- > > Key: ISPN-10430 > URL: https://issues.jboss.org/browse/ISPN-10430 > Project: Infinispan > Issue Type: Bug > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > java.lang.RuntimeException: Leaked threads: {Agroal_756431211: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamAltMapperTest]}, {Agroal_18676467981: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedSegmentedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest]} at org.infinispan.commons.test.ThreadLeakChecker.performCheck(ThreadLeakChecker.java:200) at org.infinispan.commons.test.ThreadLeakChecker.checkForLeaks(ThreadLeakChecker.java:165) at org.infinispan.commons.test.TestNGSuiteChecksTest.afterSuite(TestNGSuiteChecksTest.java:46) ... Removed 25 stack frames -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10430) Fix JdbcStringBasedStoreFunctionalTest thread leak

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10430?page=com.atlassian.jira.plugin... ] Katia Aresti updated ISPN-10430: -------------------------------- Status: Open (was: New) > Fix JdbcStringBasedStoreFunctionalTest thread leak > -------------------------------------------------- > > Key: ISPN-10430 > URL: https://issues.jboss.org/browse/ISPN-10430 > Project: Infinispan > Issue Type: Bug > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > java.lang.RuntimeException: Leaked threads: {Agroal_756431211: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamAltMapperTest]}, {Agroal_18676467981: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedSegmentedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest]} at org.infinispan.commons.test.ThreadLeakChecker.performCheck(ThreadLeakChecker.java:200) at org.infinispan.commons.test.ThreadLeakChecker.checkForLeaks(ThreadLeakChecker.java:165) at org.infinispan.commons.test.TestNGSuiteChecksTest.afterSuite(TestNGSuiteChecksTest.java:46) ... Removed 25 stack frames -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2019