[infinispan-dev] 4.2.ALPHA4 contains errors in schema

[Manik Surtani]

On 25 Oct 2010, at 13:48, Mircea Markus wrote:

> You're right, it has to do with the actual release :(
> 
> Short story:
> - 4.2.ALPHA4 is released from trunk. Commit 2533 (containing XSD element change) was not migrated from 4.2 to trunk -> hence the incorrect XSD.

We should make sure this is on trunk as well.

> 
> Long(er) story:
> - bin/release.py besides the release version also receives the *branch* param which wasn't supplied. 
> I *assumed* that released branch is the same branch from where the script is run - couldn't be more wrong! (note to self: RTFM!!!!)

Yup.  :-)

> 
> Suggested solutions:
> - re-run the release correctly?

Naha, lets wait for BETA1.

> -  wait until beta which should come this week
> 
> In both situations I'll send an email to the mailing list clarifying the situation.
> 
> Cheers,
> Mircea
> 
> 
> On 25 Oct 2010, at 12:01, Sanne Grinovero wrote:
>> Hi,
>> I can confirm that the currently created schema is fine, working from
>> branch 4.2.
>> Not sure what happened during the release process.
>> 
>> Cheers,
>> Sanne
>> 
>> 2010/10/25 Manik Surtani <manik at jboss.org>:
>>> Vladimir,
>>> 
>>> Can you confirm that building off the branch generates the correct schema?
>>> 
>>> Cheers
>>> Manik
>>> 
>>> On 25 Oct 2010, at 06:46, Vladimir Blagojevic wrote:
>>> 
>>>> Proper schema is the one that contains strictPeerToPeer as an attribute. StrictPerToPeer was annotated with @XMLElement but I corrected it a few days before the release to @XMLAttribute. And it built fine just as it is now. Not sure how it ended up in the release!!!
>>>> On 2010-10-24, at 6:49 PM, Sanne Grinovero wrote:
>>>> 
>>>>> Hello all,
>>>>> I was successfully using 4.2.0-SNAPSHOT before the ALPHA4, and I'm
>>>>> also successful in using it just after the release,
>>>>> but if I try pinning the version to 4.2.0-ALPHA4 my builds fail with
>>>>> "Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2:
>>>>> Attribute 'strictPeerToPeer' is not allowed to appear in element
>>>>> 'transport'."
>>>>> 
>>>>> Indeed the schema included in the release doesn't include the new
>>>>> "strictPeerToPeer" attribute, but lists it in the sequence, as the
>>>>> properties (see below).
>>>>> 
>>>>> Strange thing is that versions I tested just before the release where
>>>>> fine, and the schema I get when building it now from 4.2 branch are
>>>>> also correct.
>>>>> 
>>>>> 4.2.0-ALPHA4 contains:
>>>>> 
>>>>> <xs:complexType name="transportType">
>>>>>  <xs:complexContent>
>>>>>    <xs:extension base="tns:abstractConfigurationBeanWithGCR">
>>>>>      <xs:sequence>
>>>>>        <xs:element name="properties" type="tns:propertiesType"
>>>>> minOccurs="0"/>
>>>>>        <xs:element name="strictPeerToPeer" type="xs:boolean" minOccurs="0"/>
>>>>>      </xs:sequence>
>>>>>      <xs:attribute name="clusterName" type="xs:string"/>
>>>>>      <xs:attribute name="distributedSyncTimeout" type="xs:long"/>
>>>>>      <xs:attribute name="nodeName" type="xs:string"/>
>>>>>      <xs:attribute name="transportClass" type="xs:string"/>
>>>>>    </xs:extension>
>>>>>  </xs:complexContent>
>>>>> </xs:complexType>
>>>>> 
>>>>> 4.2.0-SNAPSHOT (correct):
>>>>> 
>>>>> <xs:complexType name="transportType">
>>>>>  <xs:complexContent>
>>>>>    <xs:extension base="tns:abstractConfigurationBeanWithGCR">
>>>>>      <xs:sequence>
>>>>>        <xs:element name="properties" type="tns:propertiesType"
>>>>> minOccurs="0"/>
>>>>>      </xs:sequence>
>>>>>      <xs:attribute name="clusterName" type="xs:string"/>
>>>>>      <xs:attribute name="distributedSyncTimeout" type="xs:long"/>
>>>>>      <xs:attribute name="nodeName" type="xs:string"/>
>>>>>      <xs:attribute name="strictPeerToPeer" type="xs:boolean"/>
>>>>>      <xs:attribute name="transportClass" type="xs:string"/>
>>>>>    </xs:extension>
>>>>>  </xs:complexContent>
>>>>> </xs:complexType>
>>>>> 
>>>>> any idea of how this could happen?
>>>>> Having this schema makes Alpha4 unusable for me.
>>>>> 
>>>>> Cheers,
>>>>> Sanne
>>>>> _______________________________________________
>>>>> infinispan-dev mailing list
>>>>> infinispan-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>>> 
>>>> --
>>>> Vladimir Blagojevic
>>>> JBoss Clustering Team
>>>> JBoss, by Red Hat
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> infinispan-dev mailing list
>>>> infinispan-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>> 
>>> --
>>> Manik Surtani
>>> manik at jboss.org
>>> Lead, Infinispan
>>> Lead, JBoss Cache
>>> http://www.infinispan.org
>>> http://www.jbosscache.org
>>> 
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>> 
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org