May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1572) japicmp force source compatibility, but only binary compatibility is required

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1572?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1572: ---------------------------- Description: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Japicmp currently reports adding default method into interface as source incompatible change (see https://github.com/siom79/japicmp/issues/201) -> blocks adding IV into MaskedPassword in ELY-867 was: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes new method in interface with default implementation is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-876 > japicmp force source compatibility, but only binary compatibility is required > ----------------------------------------------------------------------------- > > Key: ELY-1572 > URL: https://issues.jboss.org/browse/ELY-1572 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.3.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > As part of ELY-1523 japicmp was configured to force binary and source compatibility. > By last discussion, only binary compatibility is required. > {panel} > *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... > *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people > {panel} > Japicmp currently reports adding default method into interface as source incompatible change (see https://github.com/siom79/japicmp/issues/201) -> blocks adding IV into MaskedPassword in ELY-867 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1572) japicmp force source compatibility, but only binary compatibility is required

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1572?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1572: ---------------------------- Description: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes new method in interface with default implementation is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-876 was: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-867 > japicmp force source compatibility, but only binary compatibility is required > ----------------------------------------------------------------------------- > > Key: ELY-1572 > URL: https://issues.jboss.org/browse/ELY-1572 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.3.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > As part of ELY-1523 japicmp was configured to force binary and source compatibility. > By last discussion, only binary compatibility is required. > {panel} > *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... > *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people > {panel} > Also because of probably bug in japicmp, which causes new method in interface with default implementation is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-876 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1572) japicmp force source compatibility, but only binary compatibility is required

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1572?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1572: ---------------------------- Description: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-867 was: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-876 > japicmp force source compatibility, but only binary compatibility is required > ----------------------------------------------------------------------------- > > Key: ELY-1572 > URL: https://issues.jboss.org/browse/ELY-1572 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.3.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > As part of ELY-1523 japicmp was configured to force binary and source compatibility. > By last discussion, only binary compatibility is required. > {panel} > *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... > *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people > {panel} > Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-867 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-197) QE needs to sign off of productized Jaeger builds

by Kevin Earls (JIRA)

[ https://issues.jboss.org/browse/SWSQE-197?page=com.atlassian.jira.plugin.... ] Kevin Earls commented on SWSQE-197: ----------------------------------- I've created a Jenkins job to run this on one of our QE OpenShift instances: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... . The Jenkinsfile can be found here: https://github.com/Hawkular-QE/jaeger-java-test/blob/master/Jenkinsfile.R... This Jenkinsfile permits specifying the URL for the maven repo and the Jaeger client version. It will then create an all-in-one instance of Jaeger and run our standard smoke tests twice, once using the collector and once using the agent. It will also do a mvn dependency:tree to show versions actually used. > QE needs to sign off of productized Jaeger builds > ------------------------------------------------- > > Key: SWSQE-197 > URL: https://issues.jboss.org/browse/SWSQE-197 > Project: Kiali QE > Issue Type: Epic > Reporter: Kevin Earls > Assignee: Kevin Earls > > This Epic is to track QE signoffs of productized Jaeger Builds -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1572) japicmp force source compatibility, but only binary compatibility is required

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1572?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1572: ---------------------------- Description: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-876 was: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. > japicmp force source compatibility, but only binary compatibility is required > ----------------------------------------------------------------------------- > > Key: ELY-1572 > URL: https://issues.jboss.org/browse/ELY-1572 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.3.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > As part of ELY-1523 japicmp was configured to force binary and source compatibility. > By last discussion, only binary compatibility is required. > {panel} > *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... > *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people > {panel} > Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. -> blocks adding IV into masked password in ELY-876 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1572) japicmp force source compatibility, but only binary compatibility is required

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1572?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1572: ---------------------------- Description: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. was: As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} > japicmp force source compatibility, but only binary compatibility is required > ----------------------------------------------------------------------------- > > Key: ELY-1572 > URL: https://issues.jboss.org/browse/ELY-1572 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.3.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > As part of ELY-1523 japicmp was configured to force binary and source compatibility. > By last discussion, only binary compatibility is required. > {panel} > *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... > *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people > {panel} > Also because of probably bug in japicmp, which causes adding method into interface, even through default implementation is provided, is reported as source compatibility issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-198) QE sign-off for Jaeger build 0.27.0

by Kevin Earls (JIRA)

Kevin Earls created SWSQE-198: --------------------------------- Summary: QE sign-off for Jaeger build 0.27.0 Key: SWSQE-198 URL: https://issues.jboss.org/browse/SWSQE-198 Project: Kiali QE Issue Type: QE Task Reporter: Kevin Earls Assignee: Kevin Earls See KIALI-640 for more details -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-197) QE needs to sign off of productized Jaeger builds

by Kevin Earls (JIRA)

Kevin Earls created SWSQE-197: --------------------------------- Summary: QE needs to sign off of productized Jaeger builds Key: SWSQE-197 URL: https://issues.jboss.org/browse/SWSQE-197 Project: Kiali QE Issue Type: Epic Reporter: Kevin Earls Assignee: Kevin Earls This Epic is to track QE signoffs of productized Jaeger Builds -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1572) japicmp force source compatibility, but only binary compatibility is required

by Jan Kalina (JIRA)

Jan Kalina created ELY-1572: ------------------------------- Summary: japicmp force source compatibility, but only binary compatibility is required Key: ELY-1572 URL: https://issues.jboss.org/browse/ELY-1572 Project: WildFly Elytron Issue Type: Bug Components: Build Affects Versions: 1.3.0.Final Reporter: Jan Kalina Assignee: Jan Kalina As part of ELY-1523 japicmp was configured to force binary and source compatibility. By last discussion, only binary compatibility is required. {panel} *Honza Kalina* jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible... *Darran Lofthouse* Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people {panel} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3776) Deprecate attribute "show-model" in jmx subsystem

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3776?page=com.atlassian.jira.plugi... ] Yeray Borges updated WFCORE-3776: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3242 > Deprecate attribute "show-model" in jmx subsystem > -------------------------------------------------- > > Key: WFCORE-3776 > URL: https://issues.jboss.org/browse/WFCORE-3776 > Project: WildFly Core > Issue Type: Task > Components: JMX > Affects Versions: 5.0.0.Alpha5 > Reporter: Yeray Borges > Assignee: Yeray Borges > > The attribute show-model is used as a switch which selects which model is exposed in the MBean server. > If it is false, the model is exposed under {{jboss.as.exprs}} domain, which could return expressions on reads, if true the model is exposed under {{jboss.as}} domain, which returns the expression resolved on reads, otherwise both models are exposed. > This attribute will be removed in future versions -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2018