[jboss-dev] Committing to jbossas/trunk
Carlo de Wolf
cdewolf at redhat.com
Tue Aug 31 10:04:11 EDT 2010
On 08/31/2010 09:37 AM, Remy Maucherat wrote:
> On Tue, Aug 31, 2010 at 5:24 AM, Shelly McGowan<smcgowan at redhat.com> wrote:
>> The JBoss AS integration test suite is now running to completion after a week of instability.
> Cool.
>
>> http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSuite-sun16/
>>
>> All commits to jbossas/trunk should have an associated JBAS JIRA and run the smoke-tests target
>> (minimally) before committing.
>>
>> For component upgrades targeted for the 6.0.0.CR1 release, be sure to add a sub-task to:
>> https://jira.jboss.org/browse/JBAS-8253
>>
>> For 6.0.0.Final:
>> https://jira.jboss.org/browse/JBAS-8086
> Right now there's a smoke-test failure on the shared-jndi test, where
> apparently two deployments (shared-jndi.sar and shared-jndi.war) get
> assigned the same component name for the naming reloaded stuff, and it
> causes a conflict.
>
> Rémy
>
I've modified the test to comply with EE 6 specs.
Carlo
More information about the jboss-development
mailing list