September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9317) Fix dist and servlet-dist module to use jboss.as.release.version

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9317?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated WFLY-9317: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/10487 > Fix dist and servlet-dist module to use jboss.as.release.version > ---------------------------------------------------------------- > > Key: WFLY-9317 > URL: https://issues.jboss.org/browse/WFLY-9317 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 11.0.0.CR1 > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > > https://developer.jboss.org/thread/224262 announced availability of WildFly nightly builds. > Current status is that you must know the URL based on current version in master > At this moment it is https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la..., root dir of the zip is wildfly-11.0.0.Final-SNAPSHOT > '11.0.0.Final-SNAPSHOT' is the changing part and when you want to consume nightly build in CI (e.g. Travis) you end up doing unnecessary changes to .travis.yml (Alpha1-SNAPSHOT ==> Beta1-SNAPSHOT ==> Final-SNAPSHOT) when PRs fail because of unavailable nightly bits > Proposal 1 - expose latest bits under the same URL + keep the same root dir name > URL: https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la... > root dir of the zip: wildfly-latest-SNAPSHOT > Automation would be prepared just once and "work forever". > Usage of project.version in dist and servlet-dist module prevents to use {{mvn clean install -Djboss.as.release.version=latest-SNAPSHOT}} to adjust final zip & root dir name. > Discussion starting point: http://lists.jboss.org/pipermail/wildfly-dev/2017-September/006052.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9317) Fix dist and servlet-dist module to use jboss.as.release.version

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFLY-9317: --------------------------------------- Summary: Fix dist and servlet-dist module to use jboss.as.release.version Key: WFLY-9317 URL: https://issues.jboss.org/browse/WFLY-9317 Project: WildFly Issue Type: Bug Components: Build System Affects Versions: 11.0.0.CR1 Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda https://developer.jboss.org/thread/224262 announced availability of WildFly nightly builds. Current status is that you must know the URL based on current version in master At this moment it is https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la..., root dir of the zip is wildfly-11.0.0.Final-SNAPSHOT '11.0.0.Final-SNAPSHOT' is the changing part and when you want to consume nightly build in CI (e.g. Travis) you end up doing unnecessary changes to .travis.yml (Alpha1-SNAPSHOT ==> Beta1-SNAPSHOT ==> Final-SNAPSHOT) when PRs fail because of unavailable nightly bits Proposal 1 - expose latest bits under the same URL + keep the same root dir name URL: https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la... root dir of the zip: wildfly-latest-SNAPSHOT Automation would be prepared just once and "work forever". Usage of project.version in dist and servlet-dist module prevents to use {{mvn clean install -Djboss.as.release.version=latest-SNAPSHOT}} to adjust final zip & root dir name. Discussion starting point: http://lists.jboss.org/pipermail/wildfly-dev/2017-September/006052.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9316) Fix/unignore EarDeploymentTestCase

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9316?page=com.atlassian.jira.plugin.... ] Jan Martiska moved JBEAP-13062 to WFLY-9316: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9316 (was: JBEAP-13062) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > Fix/unignore EarDeploymentTestCase > ---------------------------------- > > Key: WFLY-9316 > URL: https://issues.jboss.org/browse/WFLY-9316 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9315) Fix/unignore SarTestCase

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-9315?page=com.atlassian.jira.plugin.... ] Jan Martiska moved JBEAP-13057 to WFLY-9315: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9315 (was: JBEAP-13057) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > Fix/unignore SarTestCase > ------------------------ > > Key: WFLY-9315 > URL: https://issues.jboss.org/browse/WFLY-9315 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3260) ObjectTypeValidator should not reject unknown fields

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3260: ---------------------------------------- Summary: ObjectTypeValidator should not reject unknown fields Key: WFCORE-3260 URL: https://issues.jboss.org/browse/WFCORE-3260 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry As previously discussed on WFCORE-2249, ObjectTypeValidator is being more strict than our basic standard by rejecting unknown fields. When I did WFCORE-2249 I decided not to fix that. But now after working on some transformation stuff with complex attributes, I've changed my mind. If we don't relax this, transformers for complex attributes will have to remove even undefined fields from the attribute, which is fussy code. Transformers will have to do that anyway for hosts running versions prior to when this is fix is implemented but fixing this will help reduce how much that is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9311) Creating infinispan security cache w/o default cache doesn't use auth-cache settings

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9311?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-9311: ---------------------------------- Assignee: Paul Ferraro (was: Bartosz Spyrko-Śmietanko) > Creating infinispan security cache w/o default cache doesn't use auth-cache settings > ------------------------------------------------------------------------------------ > > Key: WFLY-9311 > URL: https://issues.jboss.org/browse/WFLY-9311 > Project: WildFly > Issue Type: Bug > Components: Clustering, Security > Affects Versions: 11.0.0.CR1 > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Paul Ferraro > > If a default cache is not defined on security cache container, cache configuration named 'auth-cache' should be used (based on [1]). However the created cache has default values instead of ones specified on the auth-cache. > [1] https://issues.jboss.org/browse/WFLY-9206 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3259) ModelTestUtils isn't confirming the transformed boot ops work on the legacy slave

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3259?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-3259: ----------------------------------- Is this currently hiding some failures? > ModelTestUtils isn't confirming the transformed boot ops work on the legacy slave > --------------------------------------------------------------------------------- > > Key: WFCORE-3259 > URL: https://issues.jboss.org/browse/WFCORE-3259 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > In checkFailedTransformedBootOperations: > {code} > if (config.isTransformComposite()) { > //Transform and execute the composite > TransformedOperation transformedComposite = mainServices.transformOperation(modelVersion, legacyComposite); > if (transformedComposite.rejectOperation(successResult())) { > Assert.fail(transformedComposite.getFailureDescription()); > } > mainServices.executeOperation(modelVersion, transformedComposite); > } > {code} > The outcome of that "mainServices.executeOperation" is ignored, so if the transformation isn't actually producing good ops, we don't know that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9311) Creating infinispan security cache w/o default cache doesn't use auth-cache settings

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9311?page=com.atlassian.jira.plugin.... ] Paul Ferraro edited comment on WFLY-9311 at 9/7/17 10:47 PM: ------------------------------------------------------------- Additionally, the /subsystem=security/security-domain=test:remove()\{allow-resource-service-restart=true\} operation fails to both stop the "test" cache and remove the associated "test" cache configuration that was created by the add operation. was (Author: pferraro): Additionally, the /subsystem=security/security-domain=test:remove(){allow-resource-service-restart=true} operation fails to both stop the "test" cache and remove the associated "test" cache configuration that was created by the add operation. > Creating infinispan security cache w/o default cache doesn't use auth-cache settings > ------------------------------------------------------------------------------------ > > Key: WFLY-9311 > URL: https://issues.jboss.org/browse/WFLY-9311 > Project: WildFly > Issue Type: Bug > Components: Clustering, Security > Affects Versions: 11.0.0.CR1 > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > > If a default cache is not defined on security cache container, cache configuration named 'auth-cache' should be used (based on [1]). However the created cache has default values instead of ones specified on the auth-cache. > [1] https://issues.jboss.org/browse/WFLY-9206 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9311) Creating infinispan security cache w/o default cache doesn't use auth-cache settings

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9311?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-9311: ------------------------------------ Additionally, the /subsystem=security/security-domain=test:remove(){allow-resource-service-restart=true} operation fails to both stop the "test" cache and remove the associated "test" cache configuration that was created by the add operation. > Creating infinispan security cache w/o default cache doesn't use auth-cache settings > ------------------------------------------------------------------------------------ > > Key: WFLY-9311 > URL: https://issues.jboss.org/browse/WFLY-9311 > Project: WildFly > Issue Type: Bug > Components: Clustering, Security > Affects Versions: 11.0.0.CR1 > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > > If a default cache is not defined on security cache container, cache configuration named 'auth-cache' should be used (based on [1]). However the created cache has default values instead of ones specified on the auth-cache. > [1] https://issues.jboss.org/browse/WFLY-9206 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3259) ModelTestUtils isn't confirming the transformed boot ops work on the legacy slave

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3259?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3259: ------------------------------------- Description: In checkFailedTransformedBootOperations: {code} if (config.isTransformComposite()) { //Transform and execute the composite TransformedOperation transformedComposite = mainServices.transformOperation(modelVersion, legacyComposite); if (transformedComposite.rejectOperation(successResult())) { Assert.fail(transformedComposite.getFailureDescription()); } mainServices.executeOperation(modelVersion, transformedComposite); } {code} The outcome of that "mainServices.executeOperation" is ignored, so if the transformation isn't actually producing good ops, we don't know that. was: In checkFailedTransformedBootOperations: {code} if (config.isTransformComposite()) { //Transform and execute the composite TransformedOperation transformedComposite = mainServices.transformOperation(modelVersion, legacyComposite); if (transformedComposite.rejectOperation(successResult())) { Assert.fail(transformedComposite.getFailureDescription()); } mainServices.executeOperation(modelVersion, transformedComposite); } {code} The result of that "mainServices.executeOperation" is ignored, so if the transformation isn't actually producing good ops, we don't know that. > ModelTestUtils isn't confirming the transformed boot ops work on the legacy slave > --------------------------------------------------------------------------------- > > Key: WFCORE-3259 > URL: https://issues.jboss.org/browse/WFCORE-3259 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > In checkFailedTransformedBootOperations: > {code} > if (config.isTransformComposite()) { > //Transform and execute the composite > TransformedOperation transformedComposite = mainServices.transformOperation(modelVersion, legacyComposite); > if (transformedComposite.rejectOperation(successResult())) { > Assert.fail(transformedComposite.getFailureDescription()); > } > mainServices.executeOperation(modelVersion, transformedComposite); > } > {code} > The outcome of that "mainServices.executeOperation" is ignored, so if the transformation isn't actually producing good ops, we don't know that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2017