August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFBUILD-25) Unable to specify feature pack's contents and modules to include

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-25?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFBUILD-25: ----------------------------------- Description: The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": {code} <server-provisioning> <feature-packs> <feature-pack> <contents include="false"> <filter pattern="include.me" include="true"/> </contents> </feature-pack> </feature-packs> </server-provisioning> {code} The issue is that whenever "include" attribute in <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but "?!" is not considered and the "?" is replaced by ".". was: The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": {code} <server-provisioning> <feature-packs> <feature-pack> <contents include="false"> <filter pattern="include.me" include="true"/> </contents> </feature-pack> </feature-packs> </server-provisioning> {code} The issue is that whenever "include" attribute in <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but "?!" is not considered and the "?" is replaced by ".". > Unable to specify feature pack's contents and modules to include > ---------------------------------------------------------------- > > Key: WFBUILD-25 > URL: https://issues.jboss.org/browse/WFBUILD-25 > Project: WildFly Build Tools > Issue Type: Bug > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": > {code} > <server-provisioning> > <feature-packs> > <feature-pack> > > <contents include="false"> > <filter pattern="include.me" include="true"/> > </contents> > </feature-pack> > </feature-packs> > </server-provisioning> > {code} > The issue is that whenever "include" attribute in <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... > A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but "?!" is not considered and the "?" is replaced by ".". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9215) Upgrade to Hibernate Search 5.5.8.Final : compatibility with Hibernate ORM 5.1

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-9215?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated WFLY-9215: ---------------------------------- Priority: Blocker (was: Major) > Upgrade to Hibernate Search 5.5.8.Final : compatibility with Hibernate ORM 5.1 > ------------------------------------------------------------------------------ > > Key: WFLY-9215 > URL: https://issues.jboss.org/browse/WFLY-9215 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Blocker > Fix For: 11.0.0.CR1 > > > upgrading from version {{5.5.5.Final}} to {{5.5.8.Final}}. > Changelog for 5.5.6: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... > Changelog for 5.5.7: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... > Changelog for 5.5.8: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9215) Upgrade to Hibernate Search 5.5.8.Final : compatibility with Hibernate ORM 5.1

by Gail Badner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9215?page=com.atlassian.jira.plugin.... ] Gail Badner edited comment on WFLY-9215 at 8/18/17 9:10 PM: ------------------------------------------------------------ [~sannegrinovero], is the commit [1] that you released in 5.5.8 the important one that is really needed? AFAICT, that commit has updates in: 1) integrationtest/osgi/karaf-it/pom.xml 2) orm/pom.xml 3) pom.xml 4) various test files [~kabirkhan] or [~brian.stansberry], would it be possible to just make these updates to a productized version of these files, rather than doing the upgrade to 5.5.8? [1] https://github.com/hibernate/hibernate-search/commit/311018cd2bdc070784da... was (Author: gbadner): Is the commit [1] that you released in 5.5.8 the important one that is really needed? AFAICT, that commit has updates in: 1) integrationtest/osgi/karaf-it/pom.xml 2) orm/pom.xml 3) pom.xml 4) various test files [~kabirkhan] or [~brian.stansberry], would it be possible to just make these updates to a productized version of these files, rather than doing the upgrade to 5.5.8? [1] https://github.com/hibernate/hibernate-search/commit/311018cd2bdc070784da... > Upgrade to Hibernate Search 5.5.8.Final : compatibility with Hibernate ORM 5.1 > ------------------------------------------------------------------------------ > > Key: WFLY-9215 > URL: https://issues.jboss.org/browse/WFLY-9215 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 11.0.0.CR1 > > > upgrading from version {{5.5.5.Final}} to {{5.5.8.Final}}. > Changelog for 5.5.6: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... > Changelog for 5.5.7: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... > Changelog for 5.5.8: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9215) Upgrade to Hibernate Search 5.5.8.Final : compatibility with Hibernate ORM 5.1

by Gail Badner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9215?page=com.atlassian.jira.plugin.... ] Gail Badner commented on WFLY-9215: ----------------------------------- Is the commit [1] that you released in 5.5.8 the important one that is really needed? AFAICT, that commit has updates in: 1) integrationtest/osgi/karaf-it/pom.xml 2) orm/pom.xml 3) pom.xml 4) various test files [~kabirkhan] or [~brian.stansberry], would it be possible to just make these updates to a productized version of these files, rather than doing the upgrade to 5.5.8? [1] https://github.com/hibernate/hibernate-search/commit/311018cd2bdc070784da... > Upgrade to Hibernate Search 5.5.8.Final : compatibility with Hibernate ORM 5.1 > ------------------------------------------------------------------------------ > > Key: WFLY-9215 > URL: https://issues.jboss.org/browse/WFLY-9215 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 11.0.0.CR1 > > > upgrading from version {{5.5.5.Final}} to {{5.5.8.Final}}. > Changelog for 5.5.6: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... > Changelog for 5.5.7: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... > Changelog for 5.5.8: > - https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HSEARCH%20AND... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-26) Add ability to filter feature pack's dependencies when provisioning.

by Eduardo Martins (JIRA)

Eduardo Martins created WFBUILD-26: -------------------------------------- Summary: Add ability to filter feature pack's dependencies when provisioning. Key: WFBUILD-26 URL: https://issues.jboss.org/browse/WFBUILD-26 Project: WildFly Build Tools Issue Type: Feature Request Reporter: Eduardo Martins Assignee: Eduardo Martins Currently when doing server provisioning it's only possible to do lower level filtering of a feature pack's modules, contents, configs, etc... The proposed feature is to add a <dependencies /> element to filter which dependency feature packs are pulled and provisioned, this would help scenarios when more than one feature packs have a common dependency, or it's desirable to customise such dependency by adding it to the server provisioning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9244) Component upgrade of Hibernate ORM to 5.1.10.Final

by Gail Badner (JIRA)

Gail Badner created WFLY-9244: --------------------------------- Summary: Component upgrade of Hibernate ORM to 5.1.10.Final Key: WFLY-9244 URL: https://issues.jboss.org/browse/WFLY-9244 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Gail Badner Assignee: Scott Marlow Fix For: 11.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-25) Unable to specify a feature pack content to include

by Eduardo Martins (JIRA)

Eduardo Martins created WFBUILD-25: -------------------------------------- Summary: Unable to specify a feature pack content to include Key: WFBUILD-25 URL: https://issues.jboss.org/browse/WFBUILD-25 Project: WildFly Build Tools Issue Type: Bug Reporter: Eduardo Martins Assignee: Eduardo Martins The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": {code} <server-provisioning> <feature-packs> <feature-pack> <contents include="false"> <filter pattern="include.me" include="true"/> </contents> </feature-pack> </feature-packs> </server-provisioning> {code} The issue is that whenever "include" attribute in <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but "?!" is not considered and the "?" is replaced by ".". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3197) jboss-cli.sh - The RESOLVED_JBOSS_HOME strategy is not robust - Unable to access jarfile jboss-modules.jar

by Nuno Godinho de Matos (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3197?page=com.atlassian.jira.plugi... ] Nuno Godinho de Matos commented on WFCORE-3197: ----------------------------------------------- Hi, nope. That I have not tried. We would not be using betas normally, and to be mixing compnents from here and there is maintenance hell. I am fine with reviewing the linux scripts once there is a final release. In any case, for the scripts that need to pass over variables that are set tynamically by the domain creator... e.g. at the time of domain creation someone decides he wants a heap of 3 GB... That stuff would now be export JAVA_OPTS, and then the call to /bin/bash /some/path/to/stanadlone.sh would work properly. The export can work like a clean work around. But I do hope the scripts are reviewed to ensure that the caller can be in whatever working directory he wishes to be, and perhaps use other caller scripts to call the vanilla wildfly /bin scripts. that is always a good thing, I believe. Kindest regards. > jboss-cli.sh - The RESOLVED_JBOSS_HOME strategy is not robust - Unable to access jarfile jboss-modules.jar > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3197 > URL: https://issues.jboss.org/browse/WFCORE-3197 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.2.0.Final > Environment: centOs > Reporter: Nuno Godinho de Matos > Assignee: Tomaz Cerar > Priority: Trivial > > Hi, I am currently migrating some windows batch scripts associated to an automated create domain/stanadlone process. > One of these scripts, consists on faclitating the user to invoke the jboss cli to run a cli file. > While on windows the script is natrually working. > On linux centOs, the script immediately broke with the error: > {panel} > [johnDoe@localhost bin]$ sh 01_invoke_cli_file_script.sh "file99.sh" > ********************************************************** > SETUP CORE ENV VARIABLES > ********************************************************** > SET_CORE_ENV_VARS_SCRIPT_PATH=/home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain/bin > CURRENT_WILDFLY_DOMAIN_DIR=/home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain/bin/.. > WILDFLY_DOMAINS_DIR=/home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain/bin/../.. > WILDFLY_USER_PROJECTS_DIR=/home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain/bin/../../.. > WILDFLY_BASE_DIRECTORY=/home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain/bin/../../../.. > WILDFLY_BIN_DIRECTORY=/home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain/bin/../../../../bin > ********************************************************** > INVOKE jboss-cli.bat with script file: "file99.sh" > ********************************************************** > Error: Unable to access jarfile /home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain/jboss-modules.jar > <----- this some additional informaiton I am printing to make the point > RESOLVED_JBOSS_HOME: /home/johnDoe/AppServer/wildfly-10.1.0.Final/user_projects/domains/someStandAloneDomain > {panel} > What the above panel shows is that the RESOLVED_JBOSS_HOME is not being properly set. > This clearly constrasts with the windows behavior, where my base script can correctly invoke a : > call jboss-cli.bat -f someFilepath > and not break. > The reason for this seems that that while on windows, the script correctly makes no assumption on where the current working directory of the user is. > And only cares about the current location of the jboss-cli.bat script itself. > {panel} > if "%OS%" == "Windows_NT" ( > set "DIRNAME=%~dp0%" <-------- This here is a good approach > ) else ( > set DIRNAME=.\ > ) > {panel} > On linux, the same is not being done: > {panel} > # Setup JBOSS_HOME > RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd` <-------- This is not a good approach if dirname is calculated based on the command line DIRNAME=`dirname "$0"` > if [ "x$JBOSS_HOME" = "x" ]; then > # get the full path (without any relative bits) > JBOSS_HOME=$RESOLVED_JBOSS_HOME > else > SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd` > if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then > echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." > echo "" > fi > fi > export JBOSS_HOME > {panel} > I would suggest that linux scripts shouild cross cuttingly assume nothing about current working directory and do something like: > {code} > #DIRNAME=`dirname "$0"` > DIRNAME="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" > {code} > Since I do not want to be corrupting my wildfly installation and I want to leave all scripts completely untouched, I will be changing my script invocation from: > {panel} > # source "$WILDFLY_BIN_DIRECTORY/jboss-cli.sh" --file="$fileNameWithoutPrefixSuffixQuotes" > /bin/bash "$WILDFLY_BIN_DIRECTORY/jboss-cli.sh" --file="$fileNameWithoutPrefixSuffixQuotes" > {panel} > Which is not Ideal, since in some scripts I may want to set in my run time environment variables like JAVA_OPTS to override the default ones used on start up of an app server. > So for me, in the ideal case, I would like to be able to use the source command to run any arbitrary script in the /bin folder without my current directory location playing any relevant role. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3179) Add Elytron Kerberos tests for native management interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3179?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3179: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2728 (was: https://github.com/wildfly/wildfly-core/pull/2709) > Add Elytron Kerberos tests for native management interface > ---------------------------------------------------------- > > Key: WFCORE-3179 > URL: https://issues.jboss.org/browse/WFCORE-3179 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Critical > > Add Kerberos SASL mechanisms (GSSAPI, GS2-KRB5*) tests into AS TS. > This is follow-up task for JBEAP-11194/WFCORE-2881. As the ApacheDS is only used in the TS of full WildFly, the new tests won't be placed into core, but into full ({{testsuite/integration/elytron}}). > This task relates to RFE EAP7-142. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-92) [tests] LoggerTests.testResourceBundle fails on german windows

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-92?page=com.atlassian.jira.plugin.... ] James Perkins closed LOGMGR-92. ------------------------------- Resolution: Out of Date I can't reproduce this on the 1.4+ branch. Since it's just a test failure on 1.3 (maybe lower too) I don't think we need to worry too much about it as that branch is quite old now. If you think this issue is more than just a test issue please feel free to reopen. > [tests] LoggerTests.testResourceBundle fails on german windows > -------------------------------------------------------------- > > Key: LOGMGR-92 > URL: https://issues.jboss.org/browse/LOGMGR-92 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 1.3.2.Final, 2.0.0.Beta1 > Environment: maven 3.0.2 on Win7x64 cygwin > Reporter: Bernd Eckenfels > Priority: Minor > Labels: i18n > > When I run "mvn test" for the logmanager build (various branches) on german Win7 it fails with > Tests run: 42, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.834 sec <<< FAILURE! > Results: Failed tests: testResourceBundle(org.jboss.logmanager.LoggerTests): Can't find org.jboss.logmanager.LoggerTests bundle > Tests run:42 ,Failures:1, Errors:0,Skipped:0 > ava.util.MissingResourceException: Can't find org.jboss.logmanager.LoggerTests bundle > at java.util.logging.Logger.setupResourceInfo(Logger.java:1335) > at java.util.logging.Logger.getLogger(Logger.java:335) > at org.jboss.logmanager.Logger.getLogger(Logger.java:75) > at org.jboss.logmanager.LoggerTests.testResourceBundle(LoggerTests.java:149) > It helps to copy src/test/resources/org/jboss/logmanager/LoggerTests_en.properties to LoggerTests.properties, however strangely enough it does not help to manually specify user.language=en in the surefire configuration. The test should at least skip itself if the locale is not specified correctly (or ship locale independend translation). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 August 2017