March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6398) Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6398?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6398: ------------------------------- Description: {noformat} [WARNING] Some problems were encountered while building the effective model for org.infinispan.server:infinispan-server-infinispan:jar:9.0.0-SNAPSHOT [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.infinispan:infinispan-tasks:jar -> version (?) vs ${version.org.infinispan} @ org.infinispan.server:infinispan-server-infinispan:[unknown-version], /tmp/privatebuild/infinispan/server/integration/infinispan/pom.xml, line 137, column 21 {noformat} {noformat} <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-tasks</artifactId> </dependency> ... <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-tasks</artifactId> <version>${version.org.infinispan}</version> </dependency> {noformat} The version should be specified in the infinispan-server-versions POM. was: {noformat} <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-tasks</artifactId> </dependency> ... <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-tasks</artifactId> <version>${version.org.infinispan}</version> </dependency> {noformat} The version should be specified in the infinispan-server-versions POM. > Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM > ------------------------------------------------------------------------- > > Key: ISPN-6398 > URL: https://issues.jboss.org/browse/ISPN-6398 > Project: Infinispan > Issue Type: Bug > Components: Build process, Server > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Trivial > Fix For: 9.0.0.Alpha1 > > > {noformat} > [WARNING] Some problems were encountered while building the effective model for org.infinispan.server:infinispan-server-infinispan:jar:9.0.0-SNAPSHOT > [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.infinispan:infinispan-tasks:jar -> version (?) vs ${version.org.infinispan} @ org.infinispan.server:infinispan-server-infinispan:[unknown-version], /tmp/privatebuild/infinispan/server/integration/infinispan/pom.xml, line 137, column 21 > {noformat} > {noformat} > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-tasks</artifactId> > </dependency> > ... > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-tasks</artifactId> > <version>${version.org.infinispan}</version> > </dependency> > {noformat} > The version should be specified in the infinispan-server-versions POM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6398) Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6398?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6398: ------------------------------- Status: Open (was: New) > Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM > ------------------------------------------------------------------------- > > Key: ISPN-6398 > URL: https://issues.jboss.org/browse/ISPN-6398 > Project: Infinispan > Issue Type: Bug > Components: Build process, Server > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Trivial > Fix For: 9.0.0.Alpha1 > > > {noformat} > [WARNING] Some problems were encountered while building the effective model for org.infinispan.server:infinispan-server-infinispan:jar:9.0.0-SNAPSHOT > [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.infinispan:infinispan-tasks:jar -> version (?) vs ${version.org.infinispan} @ org.infinispan.server:infinispan-server-infinispan:[unknown-version], /tmp/privatebuild/infinispan/server/integration/infinispan/pom.xml, line 137, column 21 > {noformat} > {noformat} > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-tasks</artifactId> > </dependency> > ... > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-tasks</artifactId> > <version>${version.org.infinispan}</version> > </dependency> > {noformat} > The version should be specified in the infinispan-server-versions POM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6398) Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6398: ---------------------------------- Summary: Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM Key: ISPN-6398 URL: https://issues.jboss.org/browse/ISPN-6398 Project: Infinispan Issue Type: Bug Components: Build process, Server Affects Versions: 8.2.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Alpha1 {noformat} <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-tasks</artifactId> </dependency> ... <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-tasks</artifactId> <version>${version.org.infinispan}</version> </dependency> {noformat} The version should be specified in the infinispan-server-versions POM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6398) Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6398?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6398: ------------------------------- Priority: Trivial (was: Major) > Duplicate infinispan-tasks dependency in infinispan-server-infinispan POM > ------------------------------------------------------------------------- > > Key: ISPN-6398 > URL: https://issues.jboss.org/browse/ISPN-6398 > Project: Infinispan > Issue Type: Bug > Components: Build process, Server > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Trivial > Fix For: 9.0.0.Alpha1 > > > {noformat} > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-tasks</artifactId> > </dependency> > ... > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-tasks</artifactId> > <version>${version.org.infinispan}</version> > </dependency> > {noformat} > The version should be specified in the infinispan-server-versions POM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6354) Remove Map/Reduce

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6354?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6354: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Remove Map/Reduce > ----------------- > > Key: ISPN-6354 > URL: https://issues.jboss.org/browse/ISPN-6354 > Project: Infinispan > Issue Type: Task > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > Now that map reduce has been deprecated in favor of distributed streams we can remove it in the major version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6397) Expose DMR operation that returns caches using a certain template

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6397?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-6397: ----------------------------------------- Assignee: Tristan Tarrant (was: Vladimir Blagojevic) > Expose DMR operation that returns caches using a certain template > ----------------------------------------------------------------- > > Key: ISPN-6397 > URL: https://issues.jboss.org/browse/ISPN-6397 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Tristan Tarrant > > In order to trigger server restart we need to know not only if a certain template field requires a restart or not (in conf metadata) but we also need to know if a certain template is being used to configure caches or not. We could do this with a series of DMR calls from Admin console but it would be simpler to add DMR op that given a template returns caches it configures. In the case when the list of caches is empty we can safely conclude that changing the template does not require server restart even if some fields requiring restart are changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6397) Expose DMR operation that returns caches using a certain template

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6397?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6397: -------------------------------------- Description: In order to trigger server restart we need to know not only if a certain template field requires a restart or not (in conf metadata) but we also need to know if a certain template is being used to configure caches or not. We could do this with a series of DMR calls from Admin console but it would be simpler to add DMR op that given a template returns caches it configures. In the case when the list of caches is empty we can safely conclude that changing the template does not require server restart even if some fields requiring restart are changed. (was: In order to trigger server restart we need to know not only that a certain template field requires a restart or not (in conf metadata) but we also need to know that a certain template is being used to configure caches or not. We could do this with a series of DMR calls from Admin console but it would be simpler to add DMR op that given a template returns caches it configures. In the case when the list of caches is empty we can safely conclude that changing the template does not require server restart even if some fields requiring restart are changed. ) > Expose DMR operation that returns caches using a certain template > ----------------------------------------------------------------- > > Key: ISPN-6397 > URL: https://issues.jboss.org/browse/ISPN-6397 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > In order to trigger server restart we need to know not only if a certain template field requires a restart or not (in conf metadata) but we also need to know if a certain template is being used to configure caches or not. We could do this with a series of DMR calls from Admin console but it would be simpler to add DMR op that given a template returns caches it configures. In the case when the list of caches is empty we can safely conclude that changing the template does not require server restart even if some fields requiring restart are changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6397) Expose DMR operation that returns caches using a certain template

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6397?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-6397: ----------------------------------------- Assignee: Vladimir Blagojevic (was: Tristan Tarrant) > Expose DMR operation that returns caches using a certain template > ----------------------------------------------------------------- > > Key: ISPN-6397 > URL: https://issues.jboss.org/browse/ISPN-6397 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > In order to trigger server restart we need to know not only that a certain template field requires a restart or not (in conf metadata) but we also need to know that a certain template is being used to configure caches or not. We could do this with a series of DMR calls from Admin console but it would be simpler to add DMR op that given a template returns caches it configures. In the case when the list of caches is empty we can safely conclude that changing the template does not require server restart even if some fields requiring restart are changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6397) Expose DMR operation that returns caches using a certain template

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-6397: ----------------------------------------- Summary: Expose DMR operation that returns caches using a certain template Key: ISPN-6397 URL: https://issues.jboss.org/browse/ISPN-6397 Project: Infinispan Issue Type: Feature Request Components: Console Affects Versions: 8.2.0.Final Reporter: Vladimir Blagojevic Assignee: Tristan Tarrant In order to trigger server restart we need to know not only that a certain template field requires a restart or not (in conf metadata) but we also need to know that a certain template is being used to configure caches or not. We could do this with a series of DMR calls from Admin console but it would be simpler to add DMR op that given a template returns caches it configures. In the case when the list of caches is empty we can safely conclude that changing the template does not require server restart even if some fields requiring restart are changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6397) Expose DMR operation that returns caches using a certain template

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6397?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6397: ------------------------------------------- [~NadirX] Please delegate so we can have this one in soon - if possible. Much appreciated! > Expose DMR operation that returns caches using a certain template > ----------------------------------------------------------------- > > Key: ISPN-6397 > URL: https://issues.jboss.org/browse/ISPN-6397 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Tristan Tarrant > > In order to trigger server restart we need to know not only that a certain template field requires a restart or not (in conf metadata) but we also need to know that a certain template is being used to configure caches or not. We could do this with a series of DMR calls from Admin console but it would be simpler to add DMR op that given a template returns caches it configures. In the case when the list of caches is empty we can safely conclude that changing the template does not require server restart even if some fields requiring restart are changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016