[jbossts-issues] [JBoss JIRA] (JBTM-3146) Better support for Quarkus

[Michael Musgrove (Jira)]

     [ https://issues.jboss.org/browse/JBTM-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-3146:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


The reviewer left an interesting note on the PR which requires following up:

{quote}
related: Whilst JBTM-3146 is clearly a tactical fix for Quarkus, is there a wider discussion of how default properties will work going forwards? With injection available, does it make sense to do away with the default properties file in a build in favor of injecting those defaults directly to the beans at build time? The stumbling block may be beans that exist in one module/jar but get their value from another (e.g. core configured by jta/jts) so it may lead to a messy hybrid approach that still needs files for some properties.
{quote}

> Better support for Quarkus
> --------------------------
>
>                 Key: JBTM-3146
>                 URL: https://issues.jboss.org/browse/JBTM-3146
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Common
>    Affects Versions: 5.9.5.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> To facilitate use of Narayana with containers such as Quarkus we want to minimise things like XML parsing and java archive parsing. The two main enhancements that would be useful in this respect are:
>  * to inject build information into a java class (via the org.jboss.maven.plugins:maven-injection-plugin plugin);
>  * to avoid the need for runtime parsing of XML properties it would be useful to allow the properties factory delegate to be supplied externally



--
This message was sent by Atlassian Jira
(v7.12.1#712002)