[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)
6 years
[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)
6 years
[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)
6 years
[JBoss JIRA] (WFWIP-4) Unexpected element: color-output
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFWIP-4?page=com.atlassian.jira.plugin.sy... ]
Ingo Weiss resolved WFWIP-4.
----------------------------
Resolution: Done
> Unexpected element: color-output
> --------------------------------
>
> Key: WFWIP-4
> URL: https://issues.jboss.org/browse/WFWIP-4
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Erich Duda
> Assignee: Ingo Weiss
> Priority: Blocker
> Labels: WFCORE-3577
>
> When I uncommented {{color-output}} configuration in {{jboss-cli.xml}} and run {{jboss-cli.sh}}, I got {{Unexpected element: color-output}} error.
> {code:xml}
> <!-- Uncomment to display CLI output in colour and configure each of the available responses. -->
> <!-- Available colors: black, red, green, yellow, blue, magenta, cyan, white and default, which is the terminal's default foreground color-->
> <color-output>
> <enabled>true</enabled>
> <error-color>red</error-color>
> <warn-color>yellow</warn-color>
> <success-color>default</success-color>
> <required-color>magenta</required-color>
> <workflow-color>green</workflow-color>
> <prompt-color>blue</prompt-color>
> </color-output>
> We should also investigate why tests did not discover this issue.
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ELY-1571) Increment WildFly Elytron schema version
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1571?page=com.atlassian.jira.plugin.s... ]
Jan Kalina updated ELY-1571:
----------------------------
Description: As schema {{urn:elytron:client:1.1}} is already released so cannot be modified, new schema needs to be added to add new elements, like masked-password. (was: New schema needs to be added to add new elements, like masked-password.)
> Increment WildFly Elytron schema version
> ----------------------------------------
>
> Key: ELY-1571
> URL: https://issues.jboss.org/browse/ELY-1571
> Project: WildFly Elytron
> Issue Type: Task
> Components: Authentication Client
> Affects Versions: 1.3.0.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> As schema {{urn:elytron:client:1.1}} is already released so cannot be modified, new schema needs to be added to add new elements, like masked-password.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years