[Fwd: Re: [jboss-dev] AS testsuite]

Tue Jun 17 16:07:35 EDT 2008

Fresh checkout:
[512][valkyrie: /tmp/1.4.1.CR1]$ ls -l
total 3592
-rw-r--r--  1 starksm  wheel   710582 Jun 17 07:58 
jboss-messaging-1.4.1.CR1-sources.jar
-rw-r--r--  1 starksm  wheel       32 Jun 17 07:58 
jboss-messaging-1.4.1.CR1-sources.jar.md5
-rw-r--r--  1 starksm  wheel       40 Jun 17 07:58 
jboss-messaging-1.4.1.CR1-sources.jar.sha1
-rw-r--r--  1 starksm  wheel  1096488 Jun 17 07:58 
jboss-messaging-1.4.1.CR1.jar
-rw-r--r--  1 starksm  wheel       32 Jun 17 07:58 
jboss-messaging-1.4.1.CR1.jar.md5
-rw-r--r--  1 starksm  wheel       40 Jun 17 07:58 
jboss-messaging-1.4.1.CR1.jar.sha1
-rw-r--r--  1 starksm  wheel      206 Jun 17 07:58 
jboss-messaging-1.4.1.CR1.pom
-rw-r--r--  1 starksm  wheel       32 Jun 17 07:58 
jboss-messaging-1.4.1.CR1.pom.md5
-rw-r--r--  1 starksm  wheel       40 Jun 17 07:58 
jboss-messaging-1.4.1.CR1.pom.sha1
[513][valkyrie: /tmp/1.4.1.CR1]$ cat jboss-messaging-1.4.1.CR1.jar.sha1
57c49fe78262034121d57f1dfd615f51a0280eb8
[517][valkyrie: /tmp/1.4.1.CR1]$ md5 jboss-messaging-1.4.1.CR1-sources.jar
MD5 (jboss-messaging-1.4.1.CR1-sources.jar) = 
4b583cc262ec88b827dae131cb8d9927
[520][valkyrie: /tmp/1.4.1.CR1]$ md5 jboss-messaging-1.4.1.CR1.jar
MD5 (jboss-messaging-1.4.1.CR1.jar) = 74b8d24e84d31d2fade4edf0f8e76d66

local repo:
-rw-r--r--  1 starksm  admin   710582 Apr 12 07:43 
jboss-messaging-1.4.1.CR1-sources.jar
-rw-r--r--  1 starksm  admin       40 Apr 12 07:43 
jboss-messaging-1.4.1.CR1-sources.jar.sha1
-rw-r--r--  1 starksm  admin  1096493 Apr 12 07:42 
jboss-messaging-1.4.1.CR1.jar
-rw-r--r--  1 starksm  admin       40 Apr 12 07:42 
jboss-messaging-1.4.1.CR1.jar.sha1
-rw-r--r--  1 starksm  admin      206 Apr 12 07:41 
jboss-messaging-1.4.1.CR1.pom
-rw-r--r--  1 starksm  admin       40 Apr 12 07:41 
jboss-messaging-1.4.1.CR1.pom.sha1
[548][valkyrie: 1.4.1.CR1]$ cat jboss-messaging-1.4.1.CR1.jar.sha1
094e4dbae701296f7ac1dfec62d40091260fd23e
[517][valkyrie: /tmp/1.4.1.CR1]$ md5 jboss-messaging-1.4.1.CR1-sources.jar
MD5 (jboss-messaging-1.4.1.CR1-sources.jar) = 
4b583cc262ec88b827dae131cb8d9927
[551][valkyrie: 1.4.1.CR1]$ md5 jboss-messaging-1.4.1.CR1.jar
MD5 (jboss-messaging-1.4.1.CR1.jar) = 74f24a33f013f08d09bf8c7265e6fbc7

So clearly the jboss-messaging-1.4.1.CR1.jars are different, and the 
source jars have to be incorrect as they are the same. The source jar 
must not have been updated for the jar change. Can't we just get a 
proper 1.4.1.CR2 release to fix this?

Clebert Suconic wrote:
> I've tried to compile trunk to validate this..
>
> and I get this:
>
> compile-classes:
>     [javac] Compiling 5 source files to 
> /work/projects/jboss5/cluster/output/classes
> /work/projects/jboss5/cluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.java:811: 
> type java.rmi.MarshalledObject does not take parameters
>             MarshalledObject<Naming> replyStub = new 
> MarshalledObject<Naming>(DetachedHANamingService.this.stub);
>                             ^
> /work/projects/jboss5/cluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.java:811: 
> type java.rmi.MarshalledObject does not take parameters
>             MarshalledObject<Naming> replyStub = new 
> MarshalledObject<Naming>(DetachedHANamingService.this.stub);
>
>
>
> I had a fresh checkout.. fresh Maven...
>
>
> Any ideas?
>
>
> /work/projects/jboss5$ svn info
> Path: .
> URL: https://svn.jboss.org/repos/jbossas/trunk
> Repository Root: https://svn.jboss.org/repos/jbossas
> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
> Revision: 74705
> Node Kind: directory
> Schedule: normal
> Last Changed Author: alesj
> Last Changed Rev: 74700
> Last Changed Date: 2008-06-17 11:05:19 -0500 (Tue, 17 Jun 2008)
>
>
>
> Ales Justin wrote:
>>> Maybe what you're seeing is just old caching of the JAR at your system?
>>
>> What exactly should I nuke to see the results/effect?
>> Since I don't wanna nuke my whole Maven repo ...
>>
>>> Ales Justin wrote:
>>>> Yeah, this also makes smoke-tests pass on my Winz box.
>>>>
>>>> Scott Stark wrote:
>>>>> Attached is an example 
>>>>> all/deploy/messaging/hsqldb-persistence-service.xml that allows 
>>>>> the all config to startup and the smoke-tests pass on my osx system.
>>>>>
>>>>> Scott Stark wrote:
>>>>>> Right, that is what I would like to understand. I know this can 
>>>>>> be fixed by updating the ds.xml config, but wanted to find out 
>>>>>> why the failure is not consistent. The current JBM version in 
>>>>>> jbossas trunk is 1.4.1.CR1
>>>>>>
>>>>>> Ales Justin wrote:
>>>>>>> > Workaround is simple just add the correct config to the file.
>>>>>>>
>>>>>>> What is the correct config? :-)
>>>>>>> Or why it works on Fedora9, but not on OSX and Winz?
>>>>>>>
>>>>>>> Tim Fox wrote:
>>>>>>>> This was a bug in the default HSQL config. I believe Clebert 
>>>>>>>> fixed it some time back - I'm not sure what version you are using?
>>>>>>>>
>>>>>>>> Sorry - didn't see this thread since don't read all of dev list.
>>>>>>>>
>>>>>>>> We don't test against HSQL since we don't support it (it 
>>>>>>>> doesn't have transactions etc).
>>>>>>>>
>>>>>>>> Apparently this one slipped through EAP testing too.
>>>>>>>>
>>>>>>>> Workaround is simple just add the correct config to the file.
>>>>>>>>
>>>>>>>> Ales Justin wrote:
>>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>
>>>
>>>
>