[JBoss JIRA] (WFLY-9659) Upgrade Ironjacamar to 1.4.7
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-9659?page=com.atlassian.jira.plugin.... ]
Ivo Studensky moved JBEAP-14069 to WFLY-9659:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9659 (was: JBEAP-14069)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JCA
(was: Build System)
Affects Version/s: (was: 7.1.0.CR1)
Fix Version/s: (was: 7.1.1.GA)
> Upgrade Ironjacamar to 1.4.7
> ----------------------------
>
> Key: WFLY-9659
> URL: https://issues.jboss.org/browse/WFLY-9659
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JCA
> Reporter: Ivo Studensky
> Assignee: Petr Sakař
> Labels: downstream_dependency
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3503) Duplicate commands in Help
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3503?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-3503:
----------------------------------------------
Thank-you for reporting the issue. I fixed in the PR branch.
> Duplicate commands in Help
> --------------------------
>
> Key: WFCORE-3503
> URL: https://issues.jboss.org/browse/WFCORE-3503
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Jean-Francois Denise
>
> I found duplicate command in CLI help
> For example twice commands:
> * attachment
> * if
> * undeploy
> * command
> I see this issue in this [pull request|https://github.com/wildfly/wildfly-core/pull/2946/commits/3eae7f7...]
> {noformat}
> [standalone@localhost:9990 /] help --commands
> Commands available in the current context:
> attachment connection-info deployment undeploy help pwd set
> attachment connection-info deployment undeploy-cli-archive history pwd shutdown
> batch deploy deployment-info history quit shutdown
> batch deploy deployment-info if quit try
> cd deployment deploy-cli-archive deployment-overlay if read-attribute try
> cd deployment deploy-file deployment-overlay ls read-attribute undeploy
> clear deployment deploy-url echo ls read-operation undeploy
> clear deployment disable echo module read-operation unset
> command deployment disable-all echo-dmr module reload unset
> command deployment enable echo-dmr patch apply reload version
> command-timeout deployment enable-all for patch history run-batch
> command-timeout deployment info for patch info run-batch
> connect deployment list grep patch inspect set
> To read a description of a specific command execute 'help <command name>'.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-7085) Server should verify EJB business methods during deployment and reject
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-7085?page=com.atlassian.jira.plugin.... ]
Ivo Studensky updated WFLY-7085:
--------------------------------
Labels: downstream_dependency (was: )
> Server should verify EJB business methods during deployment and reject
> ----------------------------------------------------------------------
>
> Key: WFLY-7085
> URL: https://issues.jboss.org/browse/WFLY-7085
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Tomasz Adamski
> Labels: downstream_dependency
> Fix For: 12.0.0.Alpha1
>
>
> The ejb 3.2 core specification state in chapter 4.9.6 that business methods should not be declared as final or static.
> But a Bean with a business method declared in the local or remote interface can be correct deployed and is accesible under some circumstances.
> To ensure that the Bean is according to the spec and avoid runtime or injection issues the methods should be checked and a VerifyError should be thrown at deployment time.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3503) Duplicate commands in Help
by Vratislav Marek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3503?page=com.atlassian.jira.plugi... ]
Vratislav Marek updated WFCORE-3503:
------------------------------------
Description:
I found duplicate command in CLI help
For example twice commands:
* attachment
* if
* undeploy
* command
I see this issue in this [pull request|https://github.com/wildfly/wildfly-core/pull/2946/commits/3eae7f7...]
{noformat}
[standalone@localhost:9990 /] help --commands
Commands available in the current context:
attachment connection-info deployment undeploy help pwd set
attachment connection-info deployment undeploy-cli-archive history pwd shutdown
batch deploy deployment-info history quit shutdown
batch deploy deployment-info if quit try
cd deployment deploy-cli-archive deployment-overlay if read-attribute try
cd deployment deploy-file deployment-overlay ls read-attribute undeploy
clear deployment deploy-url echo ls read-operation undeploy
clear deployment disable echo module read-operation unset
command deployment disable-all echo-dmr module reload unset
command deployment enable echo-dmr patch apply reload version
command-timeout deployment enable-all for patch history run-batch
command-timeout deployment info for patch info run-batch
connect deployment list grep patch inspect set
To read a description of a specific command execute 'help <command name>'.
{noformat}
was:
I found duplicate command in CLI help
For example twice commands:
* attachment
* if
* undeploy
* command
{noformat}
[standalone@localhost:9990 /] help --commands
Commands available in the current context:
attachment connection-info deployment undeploy help pwd set
attachment connection-info deployment undeploy-cli-archive history pwd shutdown
batch deploy deployment-info history quit shutdown
batch deploy deployment-info if quit try
cd deployment deploy-cli-archive deployment-overlay if read-attribute try
cd deployment deploy-file deployment-overlay ls read-attribute undeploy
clear deployment deploy-url echo ls read-operation undeploy
clear deployment disable echo module read-operation unset
command deployment disable-all echo-dmr module reload unset
command deployment enable echo-dmr patch apply reload version
command-timeout deployment enable-all for patch history run-batch
command-timeout deployment info for patch info run-batch
connect deployment list grep patch inspect set
To read a description of a specific command execute 'help <command name>'.
{noformat}
> Duplicate commands in Help
> --------------------------
>
> Key: WFCORE-3503
> URL: https://issues.jboss.org/browse/WFCORE-3503
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Jean-Francois Denise
>
> I found duplicate command in CLI help
> For example twice commands:
> * attachment
> * if
> * undeploy
> * command
> I see this issue in this [pull request|https://github.com/wildfly/wildfly-core/pull/2946/commits/3eae7f7...]
> {noformat}
> [standalone@localhost:9990 /] help --commands
> Commands available in the current context:
> attachment connection-info deployment undeploy help pwd set
> attachment connection-info deployment undeploy-cli-archive history pwd shutdown
> batch deploy deployment-info history quit shutdown
> batch deploy deployment-info if quit try
> cd deployment deploy-cli-archive deployment-overlay if read-attribute try
> cd deployment deploy-file deployment-overlay ls read-attribute undeploy
> clear deployment deploy-url echo ls read-operation undeploy
> clear deployment disable echo module read-operation unset
> command deployment disable-all echo-dmr module reload unset
> command deployment enable echo-dmr patch apply reload version
> command-timeout deployment enable-all for patch history run-batch
> command-timeout deployment info for patch info run-batch
> connect deployment list grep patch inspect set
> To read a description of a specific command execute 'help <command name>'.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3503) Duplicate commands in Help
by Vratislav Marek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3503?page=com.atlassian.jira.plugi... ]
Vratislav Marek updated WFCORE-3503:
------------------------------------
Affects Version/s: (was: 4.0.0.Alpha5)
> Duplicate commands in Help
> --------------------------
>
> Key: WFCORE-3503
> URL: https://issues.jboss.org/browse/WFCORE-3503
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Jean-Francois Denise
>
> I found duplicate command in CLI help
> For example twice commands:
> * attachment
> * if
> * undeploy
> * command
> {noformat}
> [standalone@localhost:9990 /] help --commands
> Commands available in the current context:
> attachment connection-info deployment undeploy help pwd set
> attachment connection-info deployment undeploy-cli-archive history pwd shutdown
> batch deploy deployment-info history quit shutdown
> batch deploy deployment-info if quit try
> cd deployment deploy-cli-archive deployment-overlay if read-attribute try
> cd deployment deploy-file deployment-overlay ls read-attribute undeploy
> clear deployment deploy-url echo ls read-operation undeploy
> clear deployment disable echo module read-operation unset
> command deployment disable-all echo-dmr module reload unset
> command deployment enable echo-dmr patch apply reload version
> command-timeout deployment enable-all for patch history run-batch
> command-timeout deployment info for patch info run-batch
> connect deployment list grep patch inspect set
> To read a description of a specific command execute 'help <command name>'.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3503) Duplicate commands in Help
by Vratislav Marek (JIRA)
Vratislav Marek created WFCORE-3503:
---------------------------------------
Summary: Duplicate commands in Help
Key: WFCORE-3503
URL: https://issues.jboss.org/browse/WFCORE-3503
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 4.0.0.Alpha5
Reporter: Vratislav Marek
Assignee: Jean-Francois Denise
I found duplicate command in CLI help
For example twice commands:
* attachment
* if
* undeploy
* command
{noformat}
[standalone@localhost:9990 /] help --commands
Commands available in the current context:
attachment connection-info deployment undeploy help pwd set
attachment connection-info deployment undeploy-cli-archive history pwd shutdown
batch deploy deployment-info history quit shutdown
batch deploy deployment-info if quit try
cd deployment deploy-cli-archive deployment-overlay if read-attribute try
cd deployment deploy-file deployment-overlay ls read-attribute undeploy
clear deployment deploy-url echo ls read-operation undeploy
clear deployment disable echo module read-operation unset
command deployment disable-all echo-dmr module reload unset
command deployment enable echo-dmr patch apply reload version
command-timeout deployment enable-all for patch history run-batch
command-timeout deployment info for patch info run-batch
connect deployment list grep patch inspect set
To read a description of a specific command execute 'help <command name>'.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3502) Fix debug options in test-runner
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3502?page=com.atlassian.jira.plugi... ]
Marek Kopecký updated WFCORE-3502:
----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3029
> Fix debug options in test-runner
> --------------------------------
>
> Key: WFCORE-3502
> URL: https://issues.jboss.org/browse/WFCORE-3502
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 4.0.0.Alpha5
> Reporter: Marek Kopecký
> Assignee: Marek Kopecký
>
> Test-runner doesn't handle debug options correctly.
> If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}.
> The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, user uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails:
> {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}}
> {noformat}
> ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.
> Error occurred during initialization of VM
> agent library failed to init: jdwp
> Running null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months