February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1357) Drop javax.sql.api module

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1357?page=com.atlassian.jira.plugi... ] David Lloyd reassigned WFCORE-1357: ----------------------------------- Assignee: David Lloyd > Drop javax.sql.api module > ------------------------- > > Key: WFCORE-1357 > URL: https://issues.jboss.org/browse/WFCORE-1357 > Project: WildFly Core > Issue Type: Task > Components: Modules > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 2.0.11.Final > > > In anticipation of dropping the {{javax.transaction.xa}} package out of the {{javax.transaction.api}} module, we can drop the {{javax.sql.api}} module and ensure that the {{.xa}} package is included in {{javax.api}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6117) Modify javax.transaction.api to exclude the .xa subpackage

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6117?page=com.atlassian.jira.plugin.... ] David Lloyd reassigned WFLY-6117: --------------------------------- Assignee: David Lloyd > Modify javax.transaction.api to exclude the .xa subpackage > ---------------------------------------------------------- > > Key: WFLY-6117 > URL: https://issues.jboss.org/browse/WFLY-6117 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 10.1.0.Final > > > Simultaneously with the core upgrade which includes WFCORE-1357, update the module definition for {{javax.transaction.api}} to exclude the {{javax/transaction/xa}} package from the artifact, instead re-exporting it from the JDK. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6117) Modify javax.transaction.api to exclude the .xa subpackage

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6117?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-6117: ------------------------------ Description: Simultaneously with the core upgrade which includes WFCORE-1357, update the module definition for {{javax.transaction.api}} to exclude the {{javax/transaction/xa}} package from the artifact, instead re-exporting it from the JDK. (was: The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it there, and then delete it from the main build.) > Modify javax.transaction.api to exclude the .xa subpackage > ---------------------------------------------------------- > > Key: WFLY-6117 > URL: https://issues.jboss.org/browse/WFLY-6117 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Fix For: 10.1.0.Final > > > Simultaneously with the core upgrade which includes WFCORE-1357, update the module definition for {{javax.transaction.api}} to exclude the {{javax/transaction/xa}} package from the artifact, instead re-exporting it from the JDK. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6117) Modify javax.transaction.api to exclude the .xa subpackage

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6117?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-6117: ------------------------------ Summary: Modify javax.transaction.api to exclude the .xa subpackage (was: Remove javax.transaction.api after it is moved to core) > Modify javax.transaction.api to exclude the .xa subpackage > ---------------------------------------------------------- > > Key: WFLY-6117 > URL: https://issues.jboss.org/browse/WFLY-6117 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Fix For: 10.1.0.Final > > > The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it there, and then delete it from the main build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1357) Drop javax.sql.api module

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1357?page=com.atlassian.jira.plugi... ] David Lloyd updated WFCORE-1357: -------------------------------- Summary: Drop javax.sql.api module (was: Move javax.transaction.api to core) > Drop javax.sql.api module > ------------------------- > > Key: WFCORE-1357 > URL: https://issues.jboss.org/browse/WFCORE-1357 > Project: WildFly Core > Issue Type: Task > Components: Modules > Reporter: David Lloyd > Fix For: 2.0.11.Final > > > The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1357) Drop javax.sql.api module

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1357?page=com.atlassian.jira.plugi... ] David Lloyd updated WFCORE-1357: -------------------------------- Description: In anticipation of dropping the {{javax.transaction.xa}} package out of the {{javax.transaction.api}} module, we can drop the {{javax.sql.api}} module and ensure that the {{.xa}} package is included in {{javax.api}}. (was: The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it here.) > Drop javax.sql.api module > ------------------------- > > Key: WFCORE-1357 > URL: https://issues.jboss.org/browse/WFCORE-1357 > Project: WildFly Core > Issue Type: Task > Components: Modules > Reporter: David Lloyd > Fix For: 2.0.11.Final > > > In anticipation of dropping the {{javax.transaction.xa}} package out of the {{javax.transaction.api}} module, we can drop the {{javax.sql.api}} module and ensure that the {{.xa}} package is included in {{javax.api}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-776) handleDeployment() not called for each sub-deployment

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-776?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed WFCORE-776. ------------------------------------ Resolution: Rejected > handleDeployment() not called for each sub-deployment > ----------------------------------------------------- > > Key: WFCORE-776 > URL: https://issues.jboss.org/browse/WFCORE-776 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 2.0.0.Alpha5 > Reporter: Brandon Gaisford > Assignee: Jason Greene > Attachments: test-ear.ear > > > When deploying an ear (test-ear.ear) with included jboss-deployment-structure.xml as shown below: > <jboss-deployment-structure> > <deployment> > <exclusions> > <module name="org.hibernate" slot="main" /> > </exclusions> > <dependencies> > <module name="org.apache.log4j" /> > </dependencies> > </deployment> > <sub-deployment name="test-war.war"> > <exclusions> > <module name="org.jdom" slot="main" /> > </exclusions> > <dependencies> > <module name="org.apache.commons.collections" /> > </dependencies> > </sub-deployment> > <sub-deployment name="test-war2.war"> > <dependencies> > <module name="org.apache.commons.collections" /> > </dependencies> > </sub-deployment> > </jboss-deployment-structure> > DeploymentStructureDescriptorParser.handleDeployment(...) only gets called for the ear deployment and for one of the war sub-deployments. The war sub-deployment that does get processed appears to be random. I would expect handleDeployment(...) to get called for the ear and each war. > I discovered this issue while working on WFCORE-648. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-427) CLI doesn't read alias from .jbossclirc

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-427?page=com.atlassian.jira.plugin... ] Ståle Pedersen edited comment on WFCORE-427 at 2/3/16 8:35 AM: --------------------------------------------------------------- Hi, so in Wildfly10 the cli uses a different file; ~/.aesh_aliases, it will be changed in a later version. e: Well, aesh have different files for aliases and export so this is not direct backwards compatible. was (Author: stalep): Hi, so in Wildfly10 the cli uses a different file; ~/.aesh_aliases, it will be changed in a later version. > CLI doesn't read alias from .jbossclirc > --------------------------------------- > > Key: WFCORE-427 > URL: https://issues.jboss.org/browse/WFCORE-427 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Osamu Nagano > Assignee: Alexey Loubyansky > > By WFLY-1063, a variable can be defined in .jbossclirc and preloaded by CLI. But aliases are not able to define with {{org.jboss.as.cli.CliInitializationException}}. > {code} > $ cat .jbossclirc > set prod_db=/subsystem=datasources/data-source=ExampleDS > alias ll=ls -l > $ $JBOSS_HOME/bin/jboss-cli.sh -c > Unexpected command 'alias ll=ls -l'. Type 'help --commands' for the list of supported commands. > org.jboss.as.cli.CliInitializationException: Failed to process /home/onagano/cases/01180422/wf810/.jbossclirc > at org.jboss.as.cli.impl.CliLauncher.runcom(CliLauncher.java:352) > at org.jboss.as.cli.impl.CommandContextImpl.<init>(CommandContextImpl.java:305) > at org.jboss.as.cli.impl.CommandContextFactoryImpl.newCommandContext(CommandContextFactoryImpl.java:76) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:273) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > {code} > Enclosing by single quote or double quote won't help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1359) Exiting the CLI after disabling and clearing history will clear content of .jboss-cli-history

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1359?page=com.atlassian.jira.plugi... ] Alexey Loubyansky moved JBEAP-3189 to WFCORE-1359: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1359 (was: JBEAP-3189) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Target Release: (was: 7.0.0.GA) Affects Version/s: 2.0.10.Final (was: 7.0.0.ER4) > Exiting the CLI after disabling and clearing history will clear content of .jboss-cli-history > --------------------------------------------------------------------------------------------- > > Key: WFCORE-1359 > URL: https://issues.jboss.org/browse/WFCORE-1359 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.10.Final > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > According to the history --help: > {noformat} > --disable - will disable history expansion (but will not clear the > previously recorded history); > --clear - will clear the in-memory history (but not the file one). > {noformat} > however following sequence of commands will clear the content ~/.jboss-cli-history file > {noformat} > [pkremens@dhcp-10-40-5-180 ~]$ wc ~/.jboss-cli-history > 4 6 44 /home/pkremens/.jboss-cli-history > {noformat} > {noformat} > [standalone@localhost:9990 /] history --disable > [standalone@localhost:9990 /] history --clear > [standalone@localhost:9990 /] exit > {noformat} > {noformat} > [pkremens@dhcp-10-40-5-180 ~]$ wc ~/.jboss-cli-history > 0 0 0 /home/pkremens/.jboss-cli-history > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-312) Taking thread dumps via HC

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-312?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-312: --------------------------------------- Assignee: (was: Brian Stansberry) > Taking thread dumps via HC > -------------------------- > > Key: WFCORE-312 > URL: https://issues.jboss.org/browse/WFCORE-312 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: James Livingston > > It would be useful to be able to gather low-level per-server information such as Java thread dumps. This would best be gathered from the Host Controllers, and be available via the management model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2016