1:25 p.m.
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Beta1
In order to test Messaging within the AS testsuite, we need a scoped deployment of
Messaging (as Messaging currently uses modified versions of Remoting and other jars). We
also want to use release-admin.xml to create the Messaging configuration for the
application server. (NOTE: All of this assumes a JMX-based deployment and testing context,
as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow, for
each release of Messaging which is to be tested. This means placing copies in
repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml
to create a Messaging configuration which can be used to start the AS with and run
integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those
separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named
jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each
version in the repository. At present, the repository supports two versions of Messaging:
1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:28 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-601) Place Messaging artifacts in the repository
[ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=all ]
Ovidiu Feodorov updated JBMESSAGING-601:
----------------------------------------
Fix Version/s: 1.2.0.Alpha2
(was: 1.2.0.Beta1)
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Alpha2
In order to test Messaging within the AS testsuite, we need a scoped deployment of
Messaging (as Messaging currently uses modified versions of Remoting and other jars). We
also want to use release-admin.xml to create the Messaging configuration for the
application server. (NOTE: All of this assumes a JMX-based deployment and testing context,
as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow,
for each release of Messaging which is to be tested. This means placing copies in
repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml
to create a Messaging configuration which can be used to start the AS with and run
integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those
separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named
jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each
version in the repository. At present, the repository supports two versions of Messaging:
1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:31 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-601) Place Messaging artifacts in the repository
[ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-601:
-------------------------------------------------
Ovidiu
Could you please set this up today if possible. I would like to commit changes to get the
messaging configuration running tomorrow, so I can start testing my refactored test cases
tomorrow as well.
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Alpha2
In order to test Messaging within the AS testsuite, we need a scoped deployment of
Messaging (as Messaging currently uses modified versions of Remoting and other jars). We
also want to use release-admin.xml to create the Messaging configuration for the
application server. (NOTE: All of this assumes a JMX-based deployment and testing context,
as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow,
for each release of Messaging which is to be tested. This means placing copies in
repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml
to create a Messaging configuration which can be used to start the AS with and run
integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those
separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named
jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each
version in the repository. At present, the repository supports two versions of Messaging:
1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:58 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-601) Place Messaging artifacts in the repository
[ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=all ]
Ovidiu Feodorov closed JBMESSAGING-601.
---------------------------------------
Resolution: Done
Done.
cvs ci command didn't finish yet, and I have no feedback whether the cvs client is
uploading the artifacts or it is just stuck (it happened before). If you don't find
the artifacts in repostiory by tomorrow
(http://repository.jboss.com/jboss/messaging/1.0.1.GA), I will need to open a ticket with
IT.
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Alpha2
In order to test Messaging within the AS testsuite, we need a scoped deployment of
Messaging (as Messaging currently uses modified versions of Remoting and other jars). We
also want to use release-admin.xml to create the Messaging configuration for the
application server. (NOTE: All of this assumes a JMX-based deployment and testing context,
as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow,
for each release of Messaging which is to be tested. This means placing copies in
repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml
to create a Messaging configuration which can be used to start the AS with and run
integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those
separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named
jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each
version in the repository. At present, the repository supports two versions of Messaging:
1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:21 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-601) Place Messaging artifacts in the repository
[ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-601:
-------------------------------------------------
Hi Ovidiu
The artifacts did end up in the repository, however, a couple of problems:
1. you forgot to update the component-info.xml file with the new artifacts which were
added in version 1.0.1.GA - I added these this morning. If the artifacts aren't listed
in component-info.xml, they don't get processed by the buildthirdparty mechanism (if
my understanding is correct)
By the way, until I saw in fisheye that you made a change to the version number, I thought
I was going crazy - I noticed the incorrect CR5 after I had comitted my change (and missed
the CR5 mistake), and after you had corrected it, but before it made it back into the
repository - the versions were different and I couldn't understand why!
2. I mentioned in the JIRA issue that these new artifacts need to be added for each
version of Messaging which we want to test. I should have been more clear on this.
The main problem is that it's not so easy to work with two versions of Messaging in
the same build/testsuite, which is the situation we have at the moment. At present, the
snapshot version of Messaging is being pulled in to the AS build, for Prabhat's TCK
testing. This has the effect of setting the jboss.messaging.classpath path element, among
other things, which is used in the tests.classpath path element in the testsuite. If you
then want to run the testsuite against a different version of Messaging, say 1.0.1.GA,
this becomes difficult, as we need to define a different path element (different from
jboss.messaging.classpath) and adjust the classpath accordingly.
Can we :
(i) assume that we will run TCK tests and integration tests against the same version of
Messaging (if not in the long term, then at least in the short term)
(ii) add the additional artifacts into the snapshot directory in the repository
Richard
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Alpha2
In order to test Messaging within the AS testsuite, we need a scoped deployment of
Messaging (as Messaging currently uses modified versions of Remoting and other jars). We
also want to use release-admin.xml to create the Messaging configuration for the
application server. (NOTE: All of this assumes a JMX-based deployment and testing context,
as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow,
for each release of Messaging which is to be tested. This means placing copies in
repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml
to create a Messaging configuration which can be used to start the AS with and run
integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those
separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named
jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each
version in the repository. At present, the repository supports two versions of Messaging:
1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:04 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-601) Place Messaging artifacts in the repository
[ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-601:
---------------------------------------------
Have Prabhat modify his TCK setup to use 1.0.1.GA. I've just run the full JMS test set
and it passes 100% (minus the tests confirmed broken by Sun).
The snapshot directory is rendered irrelevant by this.
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Alpha2
In order to test Messaging within the AS testsuite, we need a scoped deployment of
Messaging (as Messaging currently uses modified versions of Remoting and other jars). We
also want to use release-admin.xml to create the Messaging configuration for the
application server. (NOTE: All of this assumes a JMX-based deployment and testing context,
as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow,
for each release of Messaging which is to be tested. This means placing copies in
repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml
to create a Messaging configuration which can be used to start the AS with and run
integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those
separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named
jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each
version in the repository. At present, the repository supports two versions of Messaging:
1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-601) Place Messaging artifacts in the repository
[ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-601:
-------------------------------------------------
I noticed a build problem when trying to use 1.0.1.GA with the AS build earlier this
morning (i.e. I changed the version of Messaging from snapshot to 1.0.1.GA in
build-thirdparty.xml). Specifically, in the component-info for Messaging, 1.0.1.GA
requires serialization 1.0.2.GA or 1.0.3.GA, but serialization 1.0.1.GA is getting pulled
in to the build, and the build is failing.
What is the approach to resolving these sorts of tangled dependencies (as changing the
version of serialization which gets pulled in may upset some other component)? Trial and
error? Or should these types of changes only be made with consent of the owner?
Richard
Place Messaging artifacts in the repository
-------------------------------------------
Key: JBMESSAGING-601
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Richard Achmatowicz
Assigned To: Ovidiu Feodorov
Priority: Critical
Fix For: 1.2.0.Alpha2
In order to test Messaging within the AS testsuite, we need a scoped deployment of
Messaging (as Messaging currently uses modified versions of Remoting and other jars). We
also want to use release-admin.xml to create the Messaging configuration for the
application server. (NOTE: All of this assumes a JMX-based deployment and testing context,
as discussed in our recent conversion concerning JMX vs MC based-deployments.)
I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow,
for each release of Messaging which is to be tested. This means placing copies in
repository.jboss.com.
As for the contents of the scoped sar, I need a version which includes the following:
(i) all the Messaging classes
(ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
(iii) service descriptors for deployment of the Messaging MBeans via JMX
The contents reflect the fact that this sar will be used together with release-admin,xml
to create a Messaging configuration which can be used to start the AS with and run
integration tests against Messaging.
This sar need not contain any test-related deployments, as the testsuite can manage those
separately.
Because we may want to test differing versions of Messaging, such a sar (e.g. named
jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each
version in the repository. At present, the repository supports two versions of Messaging:
1.0.1.CR4, and snapshot.
I suppose these could be placed in a resources subdirectory on the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6667
days inactive
6671
days old
6 comments
2 participants
participants (2)
-
Ovidiu Feodorov (JIRA) -
Richard Achmatowicz (JIRA)