[JBoss JIRA] (WFLY-13713) Bootable jar support for MicroProfile Quickstarts
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13713?page=com.atlassian.jira.plugi... ]
Eduardo Martins reopened WFLY-13713:
------------------------------------
Reopening so [~jdenise] may do any further enhancement wrt the maven plugins
> Bootable jar support for MicroProfile Quickstarts
> -------------------------------------------------
>
> Key: WFLY-13713
> URL: https://issues.redhat.com/browse/WFLY-13713
> Project: WildFly
> Issue Type: Feature Request
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
> Fix For: 21.0.0.Final
>
>
> Provides support for running the MicroProfile Quickstarts applications without the need to archive it as a deployment, and without the need to deploy it in a running application server, leveraging the bootable functionality provided by EAP7-1385.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFCORE-5147) Unable to obtain logs to debug
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5147?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-5147:
-------------------------------------
Summary: Unable to obtain logs to debug (was: Add TRACE / DEBUG logging for git integration)
> Unable to obtain logs to debug
> -------------------------------
>
> Key: WFCORE-5147
> URL: https://issues.redhat.com/browse/WFCORE-5147
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 14.0.0.Beta1
>
>
> The initial load can likely be at DEBUG level but ongoing persist calls should likely be at TRACE as they would be per model update.
> Trying to debug some failures in the test case org.jboss.as.test.manualmode.management.persistence.RemoteSshGitRepositoryTestCase when executed using GitHub actions some messages from jgit seem missing but as there is no debug or trace logging around our use of jgit it is not clear if that logging is missing because jgit is not being called or if the messages are not getting flushed to the logs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFCORE-5147) Unable to obtain logs to debug RemoteSshGitRepositoryTestCase failure.
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5147?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-5147:
-------------------------------------
Summary: Unable to obtain logs to debug RemoteSshGitRepositoryTestCase failure. (was: Unable to obtain logs to debug )
> Unable to obtain logs to debug RemoteSshGitRepositoryTestCase failure.
> ----------------------------------------------------------------------
>
> Key: WFCORE-5147
> URL: https://issues.redhat.com/browse/WFCORE-5147
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 14.0.0.Beta1
>
>
> The initial load can likely be at DEBUG level but ongoing persist calls should likely be at TRACE as they would be per model update.
> Trying to debug some failures in the test case org.jboss.as.test.manualmode.management.persistence.RemoteSshGitRepositoryTestCase when executed using GitHub actions some messages from jgit seem missing but as there is no debug or trace logging around our use of jgit it is not clear if that logging is missing because jgit is not being called or if the messages are not getting flushed to the logs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months