[JBoss JIRA] (AS7-6119) Logging Message of datasource bound/unbound
by Benjamin Graf (JIRA)
Benjamin Graf created AS7-6119:
----------------------------------
Summary: Logging Message of datasource bound/unbound
Key: AS7-6119
URL: https://issues.jboss.org/browse/AS7-6119
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.1.Final
Environment: Windows 7 x64
Reporter: Benjamin Graf
Assignee: Jesper Pedersen
Priority: Minor
I'm using Jboss 7.1.1 in standalone mode running into a strange behaviour. If I add a new datasource over websonsole or cli I got a "bound data source" output into server.log, but if I disable or remove it, nothing happens into log. As I can see in jndi-view or config file the datasource seems to get removed or disabled properly only the logging output is missing. It seems that the connector module does expect a START_REQUESTED_to_DOWN transition which is never or seldom reached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4388) Provide clustering management use cases
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/AS7-4388?page=com.atlassian.jira.plugin.s... ]
Bela Ban commented on AS7-4388:
-------------------------------
Re probe and security: yes I agree there should only be a subset of operations that are exposed. The more important question to me though is how we execute operation invocation, and attribute querying and setting across a cluster. It we restrict ourselves to domain mode, then we could use a server group to do that. However, this excludes standalone instances and makes a cluster always a subset of a server group. Not sure I like that (I'm sure Brian does) :-)
If we do it that way, there is no need to use multicasting to send requests (operations and attribute gets/sets), as done with probe, but we'd use the mechanism used within domain management that a master uses to talk to the slaves.
> Provide clustering management use cases
> ---------------------------------------
>
> Key: AS7-4388
> URL: https://issues.jboss.org/browse/AS7-4388
> Project: Application Server 7
> Issue Type: Task
> Components: Console
> Reporter: Heiko Braun
> Assignee: Bela Ban
> Fix For: 7.3.0.Alpha1
>
>
> In order to prep the UI, we would need a list of typical clustering management use cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4693) Implement Trust for users requesting to run as a different user.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-4693?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated AS7-4693:
----------------------------------
Summary: Implement Trust for users requesting to run as a different user. (was: Revisit authenticated user / authorized user split)
Description:
Where SASL is used for authentication users can request to authenticate as themselves but to be authorized to connect to the server as a different user.
A couple of examples where this could be used: -
- A user granting access to another user to log into their account.
- A user with two levels of access e.g. normal and admin and requesting they have admin level access.
Another area we are looking to use this feature is where one server connects to another server but want to be able to run requests on the remote server using the identity of a specified user.
This Jira issue is to enhance the security realms to allow for trust permissions to be defined - initially this will be local to a single realm but will subsequently be opened up to work across different realms.
was:
When establishing a connection a remote user can specify the user they want to be authorized as which can be different to the user they authenticate as, e.g. a user with appropriate permissions may want to connect as an administrator or a user given access to someone elses account may want to connect as them.
We need to re-visit this including validation that they can connect as the user they are asking to.
> Implement Trust for users requesting to run as a different user.
> ----------------------------------------------------------------
>
> Key: AS7-4693
> URL: https://issues.jboss.org/browse/AS7-4693
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Remoting, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 7.2.0.Alpha1
>
>
> Where SASL is used for authentication users can request to authenticate as themselves but to be authorized to connect to the server as a different user.
> A couple of examples where this could be used: -
> - A user granting access to another user to log into their account.
> - A user with two levels of access e.g. normal and admin and requesting they have admin level access.
> Another area we are looking to use this feature is where one server connects to another server but want to be able to run requests on the remote server using the identity of a specified user.
> This Jira issue is to enhance the security realms to allow for trust permissions to be defined - initially this will be local to a single realm but will subsequently be opened up to work across different realms.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4065) TS: Migrate from Surefire to Failsafe maven plugin.
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka updated AS7-4065:
------------------------------
Attachment: AS7-failsafe-surefire.html.zip
I have compared runs using Surefire and Failsafe with current upstream/master.
See the attached .zip.
One test is missing:
org.jboss.as.test.integration.weld.interceptor.ordering.SessionBeanInterceptorOrderingTest
However in the Surefire run, it's SKIPPED.
Jakube, could you pls have look at that?
> TS: Migrate from Surefire to Failsafe maven plugin.
> ---------------------------------------------------
>
> Key: AS7-4065
> URL: https://issues.jboss.org/browse/AS7-4065
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Ondrej Zizka
> Assignee: Jakub Senko
> Fix For: 7.2.0.Alpha1
>
> Attachments: AS7-failsafe-surefire.html.zip
>
>
> Surefire aims at unit testing.
> Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify.
> That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae).
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6104) jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove()
by Raymond Naseef (JIRA)
[ https://issues.jboss.org/browse/AS7-6104?page=com.atlassian.jira.plugin.s... ]
Raymond Naseef commented on AS7-6104:
-------------------------------------
Below are steps to fix the problem (this is workaround), and was able to add and remove the module after that.
I still think there is a bug, and hope this will help you to find it. Let me know if you need any more information on this (I still have the broken version zipped, and have confirmed it is still broken when extracted).
*** Steps Leading to Problem ***
Before I added PostgreSQL module I did:
1. Added postgresql-9.1-901-1.jdbc4.jar to standalone/deployments
2. Created DataSource for this via JBoss Administration Console
3. Did the following two, not sure which one I did first:
- removed postgresql-9.1-901-1.jdbc4.jar from standalone/deployments
- Added main.xml & postgresql-9.1-901-1.jdbc4.jar to modules/org/postgresql/main
4. Added module using jboss-cli
5. Attempted and failed to remove the module (as explained in this issue)
*** Work Around ***
1. Removed PostgreSQL module from standalone.xml (done using Notepad++):
<driver name="postgresql-driver" module="org.postgresql">
<driver-class>org.postgresql.Driver</driver-class>
</driver>
! Adding and removing the module worked fine after this
> jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove()
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6104
> URL: https://issues.jboss.org/browse/AS7-6104
> Project: Application Server 7
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.1.1.Final
> Environment: Windows 7 Professional SP1
> Reporter: Raymond Naseef
> Assignee: Jason Greene
> Labels: jboss-as7, modules, postgresql
>
> NullPointerException during jboss-cli remove with commands:
> jboss-cli --connect command="/subsystem=datasources/jdbc-driver=postgresql-driver:add(driver-name=postgresql-driver, driver-class-name=org.postgresql.Driver, driver-module-name=org.postgresql"
> * this works
> jboss-cli --connect command="/subsystem=datasources/jdbc-driver=postgresql-driver:remove"
> MS-DOS Console:
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: null",
> "rolled-back" => true
> }
> Server Log:
> 23:17:42,627 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 19) JBAS014612: Operation ("remove") failed - address: ([
> ("subsystem" => "datasources"),
> ("jdbc-driver" => "postgresql-driver")
> ]): java.lang.NullPointerException
> at org.jboss.as.controller.OperationContextImpl.doRemove(OperationContextImpl.java:298) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.OperationContextImpl.removeService(OperationContextImpl.java:293) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.connector.subsystems.datasources.JdbcDriverRemove.performRuntime(JdbcDriverRemove.java:66)
> at org.jboss.as.controller.AbstractRemoveStepHandler$1.execute(AbstractRemoveStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4018) Large amount of open files for jsf-impl on AS 7
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ]
Cody Lerum closed AS7-4018.
---------------------------
Resolution: Cannot Reproduce Bug
This looks to be a non-issue. May have been JRE specific
> Large amount of open files for jsf-impl on AS 7
> -----------------------------------------------
>
> Key: AS7-4018
> URL: https://issues.jboss.org/browse/AS7-4018
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: 7.1.0.Final
> Reporter: Cody Lerum
> Fix For: Open To Community
>
>
> Basically what I am seeing is the amount of open files for the jsf-impl increasing steadily the longer the app server is running.
> /usr/local/jboss-as-7.1.0.Final/modules/com/sun/jsf-impl/main/jsf-impl-2.1.5-jbossorg-1.jar
> watching via
> ls -lha /proc/xxxx/fd | grep jsf-impl | wc
> I can see the file count increase with every page load.
> What info is needed to dig into this deeper?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4065) TS: Migrate from Surefire to Failsafe maven plugin.
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka edited comment on AS7-4065 at 12/7/12 9:51 PM:
------------------------------------------------------------
I've tried it with current upstream/master. Needs to disable the 'default' execution in smoke and basic.
{code}
$ grep -E '\[INFO\] ---( .*(surefire|failsafe)|---)' TS-fs.txt
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (smoke-full.surefire) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (smoke-web.surefire) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-smoke ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-default-full.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-default-web.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-2nd.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-ldap.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-basic ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-osgi ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-osgi.surefire) @ jboss-as-ts-integ-osgi ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-osgi ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.multinode-manual-tcp-sync) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.single-node) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.jdbc-store) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-clust ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-iiop ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-iiop-multi-node.surefire) @ jboss-as-ts-integ-iiop ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-iiop ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-xts ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-xts.surefire) @ jboss-as-ts-integ-xts ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-xts ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-multinode ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (multinode.surefire) @ jboss-as-ts-integ-multinode ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-multinode ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-manualmode ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (manualmode.surefire) @ jboss-as-ts-integ-manualmode ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-manualmode ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite-compat ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite-compat ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite-integration-domain ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite-integration-domain ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
{code}
was (Author: ozizka):
I've tried it with current upstream/master. Seems fine:
{code}
$ grep -E '\[INFO\] ---( .*(surefire|failsafe)|---)' TS-fs.txt
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (smoke-full.surefire) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (smoke-web.surefire) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-smoke ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-default-full.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-default-web.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-2nd.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-ldap.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-basic ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-osgi ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-osgi.surefire) @ jboss-as-ts-integ-osgi ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-osgi ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.multinode-manual-tcp-sync) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.single-node) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.jdbc-store) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-clust ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-iiop ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-iiop-multi-node.surefire) @ jboss-as-ts-integ-iiop ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-iiop ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-xts ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-xts.surefire) @ jboss-as-ts-integ-xts ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-xts ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-multinode ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (multinode.surefire) @ jboss-as-ts-integ-multinode ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-multinode ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-manualmode ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (manualmode.surefire) @ jboss-as-ts-integ-manualmode ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-manualmode ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite-compat ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite-compat ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite-integration-domain ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite-integration-domain ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
{code}
> TS: Migrate from Surefire to Failsafe maven plugin.
> ---------------------------------------------------
>
> Key: AS7-4065
> URL: https://issues.jboss.org/browse/AS7-4065
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Ondrej Zizka
> Assignee: Jakub Senko
> Fix For: 7.2.0.Alpha1
>
>
> Surefire aims at unit testing.
> Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify.
> That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae).
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4065) TS: Migrate from Surefire to Failsafe maven plugin.
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka commented on AS7-4065:
-----------------------------------
I've tried it with current upstream/master. Seems fine:
{code}
$ grep -E '\[INFO\] ---( .*(surefire|failsafe)|---)' TS-fs.txt
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (smoke-full.surefire) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (smoke-web.surefire) @ jboss-as-ts-integ-smoke ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-smoke ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-default-full.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-default-web.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-2nd.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (basic-integration-ldap.surefire) @ jboss-as-ts-integ-basic ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-basic ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-osgi ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-osgi.surefire) @ jboss-as-ts-integ-osgi ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-osgi ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.multinode-manual-tcp-sync) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.single-node) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (ts.surefire.clust.jdbc-store) @ jboss-as-ts-integ-clust ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-clust ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-iiop ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-iiop-multi-node.surefire) @ jboss-as-ts-integ-iiop ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-iiop ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-xts ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (tests-xts.surefire) @ jboss-as-ts-integ-xts ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-xts ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-multinode ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (multinode.surefire) @ jboss-as-ts-integ-multinode ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-multinode ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-ts-integ-manualmode ---
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (manualmode.surefire) @ jboss-as-ts-integ-manualmode ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-ts-integ-manualmode ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite-compat ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite-compat ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ jboss-as-testsuite-integration-domain ---
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ jboss-as-testsuite-integration-domain ---
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
{code}
> TS: Migrate from Surefire to Failsafe maven plugin.
> ---------------------------------------------------
>
> Key: AS7-4065
> URL: https://issues.jboss.org/browse/AS7-4065
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Ondrej Zizka
> Assignee: Jakub Senko
> Fix For: 7.2.0.Alpha1
>
>
> Surefire aims at unit testing.
> Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify.
> That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae).
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months