[JBoss JIRA] (JBTM-3179) Release of narayana-jts-idlj does not contain source files in the -source artifact
by Ondrej Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3179?page=com.atlassian.jira.plugin.... ]
Ondrej Chaloupka commented on JBTM-3179:
----------------------------------------
Yes, but just partially. It's because of they are uber jars - composed with other jars compiled prior them - but the main point is the setup in {{pom.xml}}. With using {{-Pcommunity}} profile there is added one more file under compiled java classes (in difference to non-community build). But for the source code maven plugin the setup was not transffered from non-community build to the community build.
> Release of narayana-jts-idlj does not contain source files in the -source artifact
> ----------------------------------------------------------------------------------
>
> Key: JBTM-3179
> URL: https://issues.jboss.org/browse/JBTM-3179
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Release Process
> Affects Versions: 5.9.5.Final, 5.9.6.Final
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Major
>
> From time the {{-Pcommunity}} tag is used during the Narayana release the {{-source.jar}} artifact of {{narayana-jts-idlj}} and {{narayana-jts-ibmorb}} do not contain java source files.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (JBTM-3116) Temporarily disable LRA quickstarts until the MP LRA spec is more stable
by Michael Musgrove (Jira)
[ https://issues.jboss.org/browse/JBTM-3116?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-3116:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Temporarily disable LRA quickstarts until the MP LRA spec is more stable
> ------------------------------------------------------------------------
>
> Key: JBTM-3116
> URL: https://issues.jboss.org/browse/JBTM-3116
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Demonstrator, LRA
> Affects Versions: 5.9.3.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Major
> Fix For: 5.next
>
>
> The MP LRA draft spec has recently undergone a lot of churn and we need to bring both the narayana implementation and the quickstarts into line with those changes. While that work is being undertaken the quickstarts should be disabled so that users and CI do not use non-working examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (JBTM-3177) Rename lra-filters to narayana-lra
by Michael Musgrove (Jira)
[ https://issues.jboss.org/browse/JBTM-3177?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-3177:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Rename lra-filters to narayana-lra
> ----------------------------------
>
> Key: JBTM-3177
> URL: https://issues.jboss.org/browse/JBTM-3177
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.9.6.Final
> Reporter: Martin Stefanko
> Assignee: Martin Stefanko
> Priority: Major
> Fix For: 5.next
>
>
> As lra-filters is the main (and only) dependency that users will typically come in contact with, it would be beneficial for it to have a generic name to avoid questions like why do I need to include lra-filters and not lra-client? It's easier to explain and read:
> {code:xml}
> <dependency>
> <groupId>org.eclipse.microprofile.lra</groupId>
> <artifactId>microprofile-lra-api</artifactId>
> <version>1.0-RC1</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.narayana.rts</groupId>
> <artifactId>narayana-lra</artifactId>
> <version>5.9.6.Final</version>
> </dependency>
> {code}
> While this can lead to unwanted questions:
> {code:xml}
> <dependency>
> <groupId>org.eclipse.microprofile.lra</groupId>
> <artifactId>microprofile-lra-api</artifactId>
> <version>1.0-RC1</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.narayana.rts</groupId>
> <artifactId>lra-filters</artifactId>
> <version>5.9.6.Final</version>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (JBTM-3177) Rename lra-filters to narayana-lra
by Michael Musgrove (Jira)
[ https://issues.jboss.org/browse/JBTM-3177?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-3177:
-----------------------------------
Fix Version/s: 5.next
> Rename lra-filters to narayana-lra
> ----------------------------------
>
> Key: JBTM-3177
> URL: https://issues.jboss.org/browse/JBTM-3177
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.9.6.Final
> Reporter: Martin Stefanko
> Assignee: Martin Stefanko
> Priority: Major
> Fix For: 5.next
>
>
> As lra-filters is the main (and only) dependency that users will typically come in contact with, it would be beneficial for it to have a generic name to avoid questions like why do I need to include lra-filters and not lra-client? It's easier to explain and read:
> {code:xml}
> <dependency>
> <groupId>org.eclipse.microprofile.lra</groupId>
> <artifactId>microprofile-lra-api</artifactId>
> <version>1.0-RC1</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.narayana.rts</groupId>
> <artifactId>narayana-lra</artifactId>
> <version>5.9.6.Final</version>
> </dependency>
> {code}
> While this can lead to unwanted questions:
> {code:xml}
> <dependency>
> <groupId>org.eclipse.microprofile.lra</groupId>
> <artifactId>microprofile-lra-api</artifactId>
> <version>1.0-RC1</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.narayana.rts</groupId>
> <artifactId>lra-filters</artifactId>
> <version>5.9.6.Final</version>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months