[teiid-issues] [JBoss JIRA] (TEIID-5818) separate the wildfly build/repo

Steven Hawkins (Jira) issues at jboss.org
Wed Dec 11 09:00:00 EST 2019


    [ https://issues.redhat.com/browse/TEIID-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823897#comment-13823897 ] 

Steven Hawkins commented on TEIID-5818:
---------------------------------------

After running the release, I realized that we still need to reference the wildfly module in the release and final-release profiles as well.  core-release will still exclude wildfly.

> separate the wildfly build/repo
> -------------------------------
>
>                 Key: TEIID-5818
>                 URL: https://issues.redhat.com/browse/TEIID-5818
>             Project: Teiid
>          Issue Type: Task
>          Components: Server
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Major
>             Fix For: 13.0
>
>
> The wildfly build should be further decoupled from the Teiid build.  Initially this could be as simple as removing the module references from the parent pom.  We also need to update the wildfly logic poms to start referencing teiid artifacts via a distinct version (rather than project.version).
> From there we can decide how to promote it into its own repository.  As it doesn't seem likely that we'll invest in a mechanism to update teiid-wildly using some kind of teiid core overlay, we'll likely just do a teiid-wildfly release with every teiid release.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the teiid-issues mailing list