December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5829) jboss-cli.sh ignoring invalid attribute when used in batch mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5829?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-5829: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1289467 Bugzilla Update: Perform > jboss-cli.sh ignoring invalid attribute when used in batch mode > --------------------------------------------------------------- > > Key: WFLY-5829 > URL: https://issues.jboss.org/browse/WFLY-5829 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 10.0.0.CR4 > Reporter: Abhijit Humbe > Assignee: Alexey Loubyansky > > CLI did not throw any error message and just ignored the invalid attribute while using in batch mode.If we use same CLI command in non-batch mode it throws exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5829) jboss-cli.sh ignoring invalid attribute when used in batch mode

by Abhijit Humbe (JIRA)

Abhijit Humbe created WFLY-5829: ----------------------------------- Summary: jboss-cli.sh ignoring invalid attribute when used in batch mode Key: WFLY-5829 URL: https://issues.jboss.org/browse/WFLY-5829 Project: WildFly Issue Type: Bug Components: CLI Affects Versions: 10.0.0.CR4 Reporter: Abhijit Humbe Assignee: Alexey Loubyansky CLI did not throw any error message and just ignored the invalid attribute while using in batch mode.If we use same CLI command in non-batch mode it throws exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-723) Guice error resolving implementation for RepositorySystem in shaded jar

by Alejo Jara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-723?page=com.atlassian.jira.plugin... ] Alejo Jara commented on DROOLS-723: ----------------------------------- Not work if I use kiescanner in the project reproducer :( > Guice error resolving implementation for RepositorySystem in shaded jar > ----------------------------------------------------------------------- > > Key: DROOLS-723 > URL: https://issues.jboss.org/browse/DROOLS-723 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.0.1.Final > Reporter: Salem Elrahal > Assignee: Mario Fusco > Fix For: 6.3.0.CR1 > > Attachments: guice-error.tar.gz > > > I have included drools in a shaded jar and when trying to resolve a kjar from a releaseId I get the following exception. I have attached a simple reproducer that will show the error. Build the project then run > {code:shell} > java -jar target/guice-error-1.0-SNAPSHOT.jar > {code} > Exception: > {code} > Exception in thread "main" java.lang.RuntimeException: org.kie.scanner.embedder.MavenEmbedderException: com.google.inject.ProvisionException: Guice provision errors: > 1) No implementation for org.apache.maven.repository.RepositorySystem was bound. > while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > while locating org.apache.maven.execution.MavenExecutionRequestPopulator > 1 error > role: org.apache.maven.execution.MavenExecutionRequestPopulator > roleHint: > at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:21) > at org.kie.scanner.embedder.MavenProjectLoader.loadMavenProject(MavenProjectLoader.java:48) > at org.kie.scanner.Aether.<init>(Aether.java:44) > at org.kie.scanner.Aether.getAether(Aether.java:54) > at org.kie.scanner.MavenRepository.getMavenRepository(MavenRepository.java:45) > at org.kie.scanner.ArtifactResolver.<init>(ArtifactResolver.java:25) > at org.kie.scanner.KieRepositoryScannerImpl.getArtifactResolver(KieRepositoryScannerImpl.java:67) > at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:88) > at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:83) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:113) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:99) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:76) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:84) > at com.redhat.KnowledgeBaseService.getRuleBase(KnowledgeBaseService.java:28) > at com.redhat.Main.main(Main.java:11) > Caused by: org.kie.scanner.embedder.MavenEmbedderException: com.google.inject.ProvisionException: Guice provision errors: > 1) No implementation for org.apache.maven.repository.RepositorySystem was bound. > while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > while locating org.apache.maven.execution.MavenExecutionRequestPopulator > 1 error > role: org.apache.maven.execution.MavenExecutionRequestPopulator > roleHint: > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:125) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:104) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:131) > at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:18) > ... 14 more > Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: com.google.inject.ProvisionException: Guice provision errors: > 1) No implementation for org.apache.maven.repository.RepositorySystem was bound. > while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > while locating org.apache.maven.execution.MavenExecutionRequestPopulator > 1 error > role: org.apache.maven.execution.MavenExecutionRequestPopulator > roleHint: > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:257) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:245) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:239) > at org.kie.scanner.embedder.MavenEmbedder.lookup(MavenEmbedder.java:527) > at org.kie.scanner.embedder.MavenEmbedder.buildMavenExecutionRequest(MavenEmbedder.java:152) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:115) > ... 17 more > Caused by: com.google.inject.ProvisionException: Guice provision errors: > 1) No implementation for org.apache.maven.repository.RepositorySystem was bound. > while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] > while locating org.apache.maven.execution.MavenExecutionRequestPopulator > 1 error > at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:974) > at org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:83) > at org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:49) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:253) > ... 22 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5461) Getting "Attribute 'enabled' in the resource at address ... is deprecated" when creating a datasource

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5461?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-5461: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1266010 Bugzilla Update: Perform > Getting "Attribute 'enabled' in the resource at address ... is deprecated" when creating a datasource > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-5461 > URL: https://issues.jboss.org/browse/WFLY-5461 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 10.0.0.CR2 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 10.0.0.CR3 > > > Following message's are seen while adding datasource via Management console: > ~~~ > INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 25) JBAS014627: Attribute 'enabled' in the resource at address '/subsystem=datasources/xa-data-source=xyz' is deprecated > , and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > ~~~ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-756) Run AS 7 testsuite on OpenShift

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-756?page=com.atlassian.jira.plugin.s... ] James Perkins closed WFLY-756. ------------------------------ Resolution: Out of Date Please reopen if you feel this should be reconsidered. > Run AS 7 testsuite on OpenShift > ------------------------------- > > Key: WFLY-756 > URL: https://issues.jboss.org/browse/WFLY-756 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Minor > Fix For: No Release > > > What steps OpenShift does: > 1) Calls the pre-build hook > 2) Calls the build hook > 3) Builds the project, with quite low timeout, using {{mvn -e clean package -Popenshift -DskipTests}} > 4) Calls the deploy hook > 5) Deploys > 6) Calls the post-deploy hook > * Want to test the OpenShift's AS instance. > * Running the AS build will download the dependencies. > * The question is, whether during post-deploy we have the local repo at hand. > * In the post-deploy hook, we will run the testsuite against the AS instance. > * To do that, we will use the {{allowConnectingToRunningServer}} Arquillian param. > * We will need to override the {{-DskipTests}}. > Things to use: > * Configure AS: {{.openshift/config/standalone.xml}} > * Deploy pre-built app: {{git add deployments/my-app.war}} > Vojta suggested we could connect the OS AS server as a Jenkins cartridge slave, and run the tests against it while having it as local, i.e. managed, AS instance. > BZ: https://bugzilla.redhat.com/show_bug.cgi?id=810946 > Our OpenShift contact: Bill DeCoste, bdecoste @ #libra IRC -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-983) Arquillian managed container does not allow logging configuration

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-983?page=com.atlassian.jira.plugin.s... ] James Perkins closed WFLY-983. ------------------------------ Resolution: Done This should be fixed in at least {{org.wildfly.arquillian:wildfly-arquillian-container-managed:1.0.0.Final}}. > Arquillian managed container does not allow logging configuration > ----------------------------------------------------------------- > > Key: WFLY-983 > URL: https://issues.jboss.org/browse/WFLY-983 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Karel Piwko > Assignee: Ondrej Zizka > Priority: Minor > > Config path is hardcoded in ManagedDeployableContainer. > It is not possible to set the "logging.configuration" and the "org.jboss.boot.log.file" relative to the "jboss.server.base.dir" ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-721) Add a Deployment Exception Transformer for the Arquillian container

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-721?page=com.atlassian.jira.plugin.s... ] James Perkins closed WFLY-721. ------------------------------ Resolution: Out of Date If you feel this is still an issue please reopen. > Add a Deployment Exception Transformer for the Arquillian container > ------------------------------------------------------------------- > > Key: WFLY-721 > URL: https://issues.jboss.org/browse/WFLY-721 > Project: WildFly > Issue Type: Feature Request > Reporter: Jason Porter > Fix For: Awaiting Volunteers > > > A discussion on IRC: http://echelog.matzon.dk/logs/browse/jbosstesting/1309903200 > We're not reporting back to ARQ users the actual error during deployment, just whatever the app server gives us. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1182) @RestoreASConfigAfterTest to make a snapshot before test and reload it after.

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1182?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-1182. ------------------------------- Resolution: Out of Date Please reopen if you feel this should still be considered. > @RestoreASConfigAfterTest to make a snapshot before test and reload it after. > ----------------------------------------------------------------------------- > > Key: WFLY-1182 > URL: https://issues.jboss.org/browse/WFLY-1182 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > > Having a possibility to restore server configuration after the test is run, or similar principle, would be very cool. > For example, there are some tests which change datasource config quite dramatically. > And getting it back to the original state afterwards requires a lot of coding. > So instead, the test would have {{@RestoreASConfigAfterTest}} > and Arq would re-load a snapshot it made before the test was run. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1299) Arquillian AS 7 managed container: Different source and work dir (copy AS for each config)

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1299?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-1299. ------------------------------- Resolution: Out of Date Please re-open this if it's still requested. > Arquillian AS 7 managed container: Different source and work dir (copy AS for each config) > ------------------------------------------------------------------------------------------ > > Key: WFLY-1299 > URL: https://issues.jboss.org/browse/WFLY-1299 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > In my project (AS config migration), I need to keep the results of every config I run with (one per test). > This could be handled in Maven or Ant by creating copies in advance. > But much more ellegant would be to use [multiple containers|https://docs.jboss.org/author/display/ARQ/Multiple+Containers] and to let Arq copy some source dir and run AS from there. > For this purpose, I propose to add a config property {{jbossAsDist}} and copy it to {{jbossHome}} before launching it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1198) Arq: @CleanContainerDataDirsAfterTest - Delete data/ and /tmp after test is run.

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1198?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-1198. ------------------------------- Resolution: Out of Date > Arq: @CleanContainerDataDirsAfterTest - Delete data/ and /tmp after test is run. > -------------------------------------------------------------------------------- > > Key: WFLY-1198 > URL: https://issues.jboss.org/browse/WFLY-1198 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > > Some tests leave files in AS /data dir. > And the tested modules bypass their configuration from standalone.xml and rather rely on these data. > This prevents running multiple tests within a single AS instance run; therefore, multiple AS instances, Surefire executions or Maven modules are needed. > Having something like {{@CleanContainerDataDirsAfterTest}} per method would make writing these tests much easier and faster to run. > Further, sometimes these tests run with multiple instances (clustering, messaging, ...). > Not all of them may loose data in some scenarios - some of them must keep the data (e.g. for failover testing). > Therefore, the annotation should have parameters - a list of container config names (matching arquillian.xml). Only those instances would be cleaned. > {code:java} > @CleanContainerDataDirsAfterTest({"InstanceFoo", "InstanceBar"}) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 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 December 2015