[rules-dev] Beta3 sanity check

[Michael Anstis]

Hi Michael,

Now Beta3 is released, I assume we can we push to masters again?

Thanks,

Mike


On 4 June 2013 12:30, Kris Verlaenen <kris.verlaenen at gmail.com> wrote:

> Ok, did some last sanity checks of kie-wb on eap, and that seems ok.
>
> The only thing that didn't work for me was the single sign on between
> kie-wb and dashbuilder (but I might not have configured that correctly),
> but I don't think this should hold back the release.
>
> So as far as I'm concerned, it's good to go.
>
> Kris
>
>
> On Tue, Jun 4, 2013 at 11:21 AM, Michael Biarnes Kiefer <
> mbiarnes at redhat.com> wrote:
>
>> ... sounds good.
>> I saw Rikkola tested as well and it seems to be OK.
>> I am waiting now for Kris decision if we can close the release.
>>
>> Michael
>>
>>
>> ----- Ursprüngliche Mail -----
>> Von: "Michael Anstis" <michael.anstis at gmail.com>
>> An: "Rules Dev List" <rules-dev at lists.jboss.org>, "Michael Biarnes
>> Kiefer" <mbiarnes at redhat.com>
>> CC: "Kris Verlaenen" <kris.verlaenen at gmail.com>, "Mark Proctor" <
>> mproctor at codehaus.org>
>> Gesendet: Dienstag, 4. Juni 2013 10:54:05
>> Betreff: Beta3 sanity check
>>
>> Hello,
>>
>> I've tested Beta3 kie-drools-wb and kie-wb on AS7. These are my findings:-
>>
>> *kie-drools-wb
>> *1) Generally looked OK to me
>> 2) The JGIT daemon is not terminated when the webapp is removed/disabled
>> (I've emailed Alexandre).
>>
>> *kie-wb
>> *
>> 1) dom4j.jar needs deleting from WEB-INF/lib
>> 2) I did not test any jBPM related screens (Task List, Designer etc)
>> 3) The JGIT daemon is not terminated when the webapp is removed/disabled
>> (I've emailed Alexandre).
>> 4 I encountered the following error:-
>>
>> 09:46:19,545 ERROR [stderr] (http--127.0.0.1-8080-2)
>> java.lang.NullPointerException
>> 09:46:19,547 ERROR [stderr] (http--127.0.0.1-8080-2)     at
>>
>> org.jbpm.kie.services.impl.KModuleDeploymentService.deploy(KModuleDeploymentService.java:68)
>> 09:46:19,548 ERROR [stderr] (http--127.0.0.1-8080-2)     at
>>
>> org.jbpm.kie.services.impl.KModuleDeploymentService$Proxy$_$$_WeldClientProxy.deploy(KModuleDeploymentService$Proxy$_$$_WeldClientProxy.java)
>> 09:46:19,548 ERROR [stderr] (http--127.0.0.1-8080-2)     at
>>
>> org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.deploy(DeploymentManagerEntryPointImpl.java:77)
>> 09:46:19,549 ERROR [stderr] (http--127.0.0.1-8080-2)     at
>>
>> org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.autoDeploy(DeploymentManagerEntryPointImpl.java:165)
>> 09:46:19,568 ERROR [stderr] (http--127.0.0.1-8080-2)     at
>>
>> org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl$Proxy$_$$_WeldClientProxy.autoDeploy(DeploymentManagerEntryPointImpl$Proxy$_$$_WeldClientProxy.java)
>>
>>
>> This came about by creating a "New Project" and "Build & Deploying" it.
>> The
>> project did not contain any jBMP assets (only a dependency on a JAR
>> uploaded to Guvnor's M2 Repository and a simple rule).
>>
>> It didn't throw any errors to the UI so I don't think it's serious.
>> Otherwise both were OK.
>>
>> I've asked Toni and Jervis to perform a sanity check too.
>>
>> With kind regards,
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20130604/4dafb13c/attachment.html