We have 2 weeks to fix whatever is broken (including the TCK). We can
produce a new common 1.0.4 release, or a CR1, unless there is any other
fix we want to include with it.
Scott M Stark wrote:
This change has been made on the
https://svn.jboss.org/repos/common/common-old/branches/Branch_1_0/ as
well for whenever this is updated to a jboss common version for 4.2. The
eclipse classpath was broken in this project so I updated it.
Scott M Stark wrote:
> I have made the change in the common trunk so it will be picked up for
> jboss5.
>
> Dimitris, what is the status of the changes for 4.2? Are we pushing
> out the CR and will need to delay the common changes till after that?
>
> Scott M Stark wrote:
>> These would be two different common version updates. 1.0.3.GA ->
>> 1.0.4.GA for jboss4.2, and 2.0.4.Alpha something heading towards
>> 2.0.4.GA in jboss5.
>>
>> Darran Lofthouse wrote:
>>> To get the following Jira issue fixed for JBoss 4.2.0 and JBoss 5.0 is
>>> going to require a (small) fix in JBoss Common, will it be possible to
>>> get both branches of JBossAS to the next common version before their
>>> next release dates?
>>>
>>>
http://jira.jboss.com/jira/browse/JBAS-3691
>>>
>>> Regards,
>>> Darran Lofthouse.
>>>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development