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

[Dimitris Andreadis]

That's because Paul broke the build. I reverted the change (do an update in cluster dir).

Anil Saldhana wrote:
> For one of my workspaces, I was getting this "type XXX does not take 
> parameters " issue using the mvn release plugin (but mvn clean install 
> would go fine).
> 
> You have to look at the dependencies and fix them accordingly.
> 
> 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