[wildfly-dev] Blockers for WildFly 10 Final

[Darran Lofthouse]

On 29/01/16 02:07, Renann Prado wrote:
> I'm pretty sure I reported same issue as yours.
>
> See:
> https://issues.jboss.org/browse/WFLY-6015
>
> Seems to be fixed, but it's not clear to me whether it will be part of
> Wildfly 10 Final or not.

Apart from the occasional mistake in Jira if the status is 'Resolved' 
the 'Fix Version/s' field shows the release the fix is or will be 
included in.

> However you can easily work around: just add the datasource with with
> your driver && config and DO NOT CLICK IN TEST CONNECTION, then while
> EDITING the datasource you can test the connection as many times as you
> want. I did that in Wildfly 10.0.0.CR5 and it worked just fine.
>
> I wouldn't call that a blocker as there are couple of ways to create a
> datasource.
>
> Hope it helps.
>
> Renann Prado
>
> On Thu, Jan 28, 2016 at 11:58 PM, Danilo Cominotti Marques
> <dcominottim at gmail.com <mailto:dcominottim at gmail.com>> wrote:
>
>     Hello there,
>
>     I have seen the e-mail that listed the following issues as blockers
>     for WildFly 10 Final,
>
>     1. https://issues.jboss.org/browse/WFLY-5480
>     2. https://issues.jboss.org/browse/WFCORE-1277
>
>     but I would clearly add the following one to that list,
>
>     3. https://issues.jboss.org/browse/HAL-1030
>
>     because my company certainly wouldn't deploy WildFly 10 Final before
>     this issue is solved.
>
>     Any chances of having somebody look into it before the final release?
>
>     Thanks.
>
>     Danilo Cominotti Marques
>
>
>     _______________________________________________
>     wildfly-dev mailing list
>     wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>