[JBoss JIRA] (JBTM-1313) Performance related work that involves other products should be in a separate repository
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1313?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1313:
----------------------------------------
Done (moved into the All tab)
> Performance related work that involves other products should be in a separate repository
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-1313
> URL: https://issues.jboss.org/browse/JBTM-1313
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, Performance Testing
> Affects Versions: 5.0.0.M1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Any performance related activities done by the dev team that require installation of other transaction managers should done a repo that is separate from the main narayana repo. Currently this includes:
> - some changes to the jts quickstart
> - the performance harness in qa/tests/product
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components
by Weinan Li (JIRA)
[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ]
Weinan Li commented on JBTM-1598:
---------------------------------
Hi Tom, because of EAP6 current policy, all the dependency management sections will be removed by VMan automatically (a EAP prod tool), so we have to refer ${project.version} explicitly in the poms. I have done that in EAP6 version, unfortunately I've tried but the patch could not be easily reused on upstream code. I believe we could first have a profile for EAP6, and then just add these version tags for the necessary components, wdyt?
> version tags missed for all the sub-components
> ----------------------------------------------
>
> Key: JBTM-1598
> URL: https://issues.jboss.org/browse/JBTM-1598
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Weinan Li
> Assignee: Tom Jenkinson
>
> Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example:
> {code}
> <dependencies>
> <dependency>
> <groupId>org.jboss.jbossts</groupId>
> <artifactId>common</artifactId>
> </dependency>
> </dependencies>
> {code}
> Should be:
> {code}
> <dependencies>
> <dependency>
> <groupId>org.jboss.jbossts</groupId>
> <artifactId>common</artifactId>
> <version>${project.version}</version>
> </dependency>
> </dependencies>
> {code}
> Could you please help to add these tags? Thanks!
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1598:
-------------------------------------
Hi Weinan,
I can do this, but is it not ok for these all to be in the root pom in a dependency management section? I thought that was the preferred route for jboss projects?
e.g. grep https://github.com/jbosstm/narayana/blob/master/pom.xml for "common<"
Tom
> version tags missed for all the sub-components
> ----------------------------------------------
>
> Key: JBTM-1598
> URL: https://issues.jboss.org/browse/JBTM-1598
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Weinan Li
> Assignee: Tom Jenkinson
>
> Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example:
> {code}
> <dependencies>
> <dependency>
> <groupId>org.jboss.jbossts</groupId>
> <artifactId>common</artifactId>
> </dependency>
> </dependencies>
> {code}
> Should be:
> {code}
> <dependencies>
> <dependency>
> <groupId>org.jboss.jbossts</groupId>
> <artifactId>common</artifactId>
> <version>${project.version}</version>
> </dependency>
> </dependencies>
> {code}
> Could you please help to add these tags? Thanks!
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components
by Weinan Li (JIRA)
Weinan Li created JBTM-1598:
-------------------------------
Summary: version tags missed for all the sub-components
Key: JBTM-1598
URL: https://issues.jboss.org/browse/JBTM-1598
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Weinan Li
Assignee: Tom Jenkinson
Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example:
{code}
<dependencies>
<dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>common</artifactId>
</dependency>
</dependencies>
{code}
Should be:
{code}
<dependencies>
<dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>common</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
{code}
Could you please help to add these tags? Thanks!
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1313) Performance related work that involves other products should be in a separate repository
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1313?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1313:
-------------------------------------
Actually, maybe we need that job? it might be worth renaming it as it looks like an old "unit test" repeat job named as it is?
> Performance related work that involves other products should be in a separate repository
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-1313
> URL: https://issues.jboss.org/browse/JBTM-1313
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, Performance Testing
> Affects Versions: 5.0.0.M1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Any performance related activities done by the dev team that require installation of other transaction managers should done a repo that is separate from the main narayana repo. Currently this includes:
> - some changes to the jts quickstart
> - the performance harness in qa/tests/product
--
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
11 years, 9 months